[joshrl]

I'm working on an app that uses the tcp sockets layer of the MIDP connection framework. I read in this post: http://www.blackberryforums.com/viewtopic.php?t=678 that tmobile is now supporting sockets for BWC enabled clients. I've tested my app with a 7100t and I get the following exception:

java.io.Exception: could not open tunnel - failed

the connection string is something like:

socket://somedomain.com:143

Has anybody had any success getting sockets to work on t-mobile sans BES?

[joshrl]

I also tried:

socket://somedomain.com:143;deviceside=true

And got the following message:

The application SocketTest has attempted to open a connection to a location inside the firewall and outside the firewall which is not allowed by your IT policy.

in the Java app an IOException is thrown with the message "Permission denied"

[bfrye]

Originally Posted by joshrl

I also tried:

socket://somedomain.com:143;deviceside=true

And got the following message:

The application SocketTest has attempted to open a connection to a location inside the firewall and outside the firewall which is not allowed by your IT policy.

in the Java app an IOException is thrown with the message "Permission denied"

I haven't had a lot of experience in development when it comes to opening sockets... but that's the same error you get when trying to open a socket connection with WebMessenger w/o BES/MDS. Probably related? You would need MDS to open the connection or TMO hasn't fully upgraded their BWC to support socket connections yet...

[Mark Rejhon]

To the best of my knowledge, you need BlackBerryOS 4.x in order to open TCP/IP sockets on TMobile and Rogers without using BES/MDS.

What version of BlackBerryOS are you using?

[joshrl]

It's v3.8.0.112 running on a Blackberry 7100t. Are there any devices out that have the OS 4.0 on them? I've downloaded what I thought was the latest software update from t-mobile and this what it installed.

Anyway, I thought the issue was that the carrier wasn't allowing tcp socket traffic over their gateway. How would the OS make a difference?

I've talked to at least one person over at t-mobile that says that they do support raw tcp sockets with BWC subscribers, but maybe they were mistaken. If anyone has a definitive answer on this issue I would love to hear it -- my boss is getting a little frustrated with me...

thanks,
josh

[Mark Rejhon]

It's only to the best of my knowledge. Even some 4.0 users are having problems with TCP/IP even under BlackBerryOS 4.0.

The only easiest way to do this is to use BES/MDS.

It will take time before BlackBerry TCP/IP is reliable without a BES and widespread enough on BlackBerries because this is a very new and bleeding edge feature still under beta testing. Some of the software needs to be modified to actually work over TCP/IP. Maybe not till 2005.

[bfrye]

Definately not widespread until 2005. I'm sure BES 4 and BBOS4 won't even be out of beta until then.

[Dev2100]

Hey try one thing Ask T Mobile to unlock the device. They will send device unlock code. Then unlock the device and try the same code.
It may help.

[joshrl]

Sorry for my ignorance, but what exactly do mean by "unlock". If I call T-mobile and say "unlock my device" they'll know what I mean?

thanks,

-josh

[bfrye]

When you get devices (aside from cingular), they are "SIM locked" to that carrier. Meaning you can't take the device from TMO to ATT without unlocking it. TMO will unlock them usually if you've been a customer in good standing. ATT has never been known to give out unlock codes.

[berryapps]

I'm pretty sure unlocking a device will have nothing to do with if it runs sockets code.

Just my $0.02

Cheers,
Andrew

[bfrye]

Originally Posted by berryapps

I'm pretty sure unlocking a device will have nothing to do with if it runs sockets code.

Just my $0.02

Cheers,
Andrew

No I suppose not... lol maybe I'll read a few more posts up next time :D

[headtailgrep]

You need OS 4, simple...

or a hosted BES/MDS solution, for now , until OS 4 officially comes out.

[sumorai]

Does this mean I can't use something like ssh unless I use the enterprise service?

[berryapps]

that would be correct