SOAP connection problem on device.
 

Hi
i am able to connect to a .net webservice through ksoap connection on simulator but while testing on device nothing is coming. i tried to log through EventLogger but its just an error is coming
e net.rim.tcp -TNLF 0

What device? What carrier? What connection parameters are you appending to your URL?

Oh sorry i missed to mention those.
m trying on 8700, 8530, 9530
Carrier is Airtel
m not appending anything to the url. just trying to run that BlackberryFieldDemo sample

OK, that will not work.

ON the Blackberry, not appending any connection parameter means "give me the default transport". This will work on some devices, but not on most. On the simulator, this works because the MDS emulates a BES-connected device (carrier agnostic).

So, you'll need to obtain the APN info from Airtel, and append ";deviceside=true", along with the APN information to your URL.

See these articles:

Different ways to make an HTTP or socket connectio... - BlackBerry Support Community Forums

Specify APN information for a direct TCP connectio... - BlackBerry Support Community Forums

oh thnx for the reply and those links.
but if i will use any Carrier specific APN along with the url then do i hv to maintain a list for all available for carrier so that user of any carrier can use my app?

My suggestion is that you use the API's to determine what transport(s) are available to you, then craft your connection parameters accordingly.

BES
BIS-B (Alliance member)
WiFi
WAP2
Direct TCP
WAP1.1

You always want to use BES or WiFi if available.

If you are not an alliance member, the next best choice is WAP2, since you can find the parameters in the service book (see the attached article above).

Failing that, Direct TCP is a good fallback. You can either detect the network name and store the APN data internally, or you can make your customer add the APN info in the device TCP options.

oh thnx a lot. i will try to implement that.

You might want to check with Airtel and make sure they support WAP2 before you go down that path. Not all carriers do.

You should be able to open your service book and locate the WAP2 entry.