[bemobile]

We started to port our mobile fleet management solution to the BB 7230. We use the prosumer produkt. Unfortunately our midlet ist not able to run http-connections. RIM told us, that using a prosumer product the service book IPPP is not required and that APN-Settings and further stuff is encoded in J2ME's connector.open(...) call. We tried:
"myURL;WAPGatewayIP=139.7.29.1;WapGatewayAPN=rim.n et.gprs";
as well as
"myURL;WAPGatewayAPN=wap.vodafone.de;TunnelAuthUse rname=d2;TunnelAuthPassword=wap

A test application throws an exception. The logging information looks like this:
VM:-DA
Unused radio message 1585
Unused radio message 1629
Starting httppost
Started httppost(60)
Foreground httppost(60)
URL:http://myURL;WAPGatewayIP=139.7.29.1...N=rim.net.gprs
CMM: httppost-1 no sig from 0x33
Exception!
java.io.IOException
Permission denied

We have no idea of what is going wrong. Email communication works finde, so the basic settings should be okay.

Any ideas welcome,

Harald

[eradis]

Are you using BES or carrier WAP gateway?

[bemobile]

We are using the carrier's WAP gateway

[eradis]

Couple of things to look out for.

1. If you tried connecting with an empty string ( i.e. no WAPGatewayIP etc.) and then tried using WAPGatewapIP, it won't work because the OS locks the first type of connection used for a 3rd party APP ( i.e. BES or WAP ). You need to do a fresh install of the app.

2. Make sure the connection string is correct and the carrier has a WAP gateway.

---> The second looks reasonable except you are missing the WAPGatewayIP.

myURL;WAPGatewayIP="x.x.x.x";WAPGatewayAPN=wap.vod afone.de;TunnelAuthUsername=d2;TunnelAuthPassword= wap

I think you need to contact Vodafone to get the correct settings.

[eradis]

Did it work in the RIM simulator?

[Mark Rejhon]

Yep -- try testing in the RIM's own emulator (simulator). That should help determine whether this is caused by a lack of BES/MDS.

If you end up requiring BES/MDS, then you could obtain it for a monthly fee (i.e. MailStreet.com or MyBlackberry.us) or wait for carrier deployment of 4.0.

However, you can definitely do a number of (limited) things through the carrier's WAP gateway -- if that's all you need to do!