There is a chance this might not belong on a blackberry development message board, but my guess is, it does belong here.
My connection the Blackberry Bold appears to have trouble with setting the APN from the blackberry settings menu.
1) Trouble specifically means that the RadioStatusListener interface returns PDP_CAUSE_AUTHENTICATION_FAILED as cause in the pdpStateChange callback (with state being PDP_STATE_REJECTED).
2) If I incorporate the APN information in the connectionstring when opening a connection, this trouble does not appear.
3) This problem also does not appear on other devices than the Bold.
4) In addition,the problem seems to only surface on Vodafone,
5) TMobile and KPN (in Holland) do not appear to have this problem, but I could not test this latter assumption enough, as we switched to Vodafone recently.
Some more information. I've encountered this about two weeks ago when I thought development of our product was nearing completion, all I needed to do was test the Bold. We develop our application on JDE 4.2.1, so our users do not need to fill in which platform they run on when they want to download our client. Opening a connection on the Bold appeared to be haphazard. I constructed a debug log to see what was happening behind the scenes on the radio. It appears that, on the Bold, after an initially successful APN resolving / PDP context session (which leads to transmission of data to our UDP/TCP server) the PDP context times out (which I assume is natural behaviour), and moments later is rejected (I assume unnaturally), with the PDP state mentioned above, which is 'authentication failed'.All this happens only when inputting the APN via the Settings -> Advanced -> Tcp route. If we try to enter the very same APN information directly into the connectionstring (e.g. using: udp://server:port;listenport/live.vodafone.com;TunnelAuthUsername=vodafone;TunnelAuthPassword=vodafone), the connection will succeed.
This leads me to believe that the Blackberry Bold does not correctly pick up the APN information on subsequent connection calls. One remote possibility is that the problem is related to us using Bold's which were sim-locked to Roger, but unlocked using the mechanism provided by Rogers.
Does anyone have any info, or any hints and / or suggestions about this?
