This is a longshot but perhaps someone here has had the same problems.
I have an application that works fine on other GPRS networks, but on
t-mobile no
packets are ever received by the device.
We use UDP for communications, the device sends a packet and the server will
reply. But the packet never replies. (although trying to connect to the
device via TCP doesn't work either)
The customer care machine is hard to get through (although I have trouble
tickets out there)
I am wondering if perhaps someone here can give any insight - do you need a
special apn for that? Perhaps some range of ports is blocked? Maybe you
need to ask for somehting special in the configuration of the sim?
Thanks for any help.
Ralph
Toad68 - 29 Jul 2003 04:55 GMT
Probably you should change you APN to internet2.voicestream.com. I have
trouble with "real" data over wap.voicestream.com. If you have an
appropriate plan then you either already have access or you can request
access.
Good luck.
Later,
Rob
> This is a longshot but perhaps someone here has had the same problems.
>
[quoted text clipped - 15 lines]
> Thanks for any help.
> Ralph
gopi - 30 Jul 2003 07:24 GMT
> This is a longshot but perhaps someone here has had the same problems.
>
[quoted text clipped - 5 lines]
> reply. But the packet never replies. (although trying to connect to the
> device via TCP doesn't work either)
When I use the APN "internet3.voicestream.com" (the 'VPN' one), I get
a real IP, but I can't do incoming TCP connections to the device. I
haven't tried any UDP-based apps.
When I use the APN "wap.voicestream.com", I get a fake IP (10.x.x.x)
and, obviously, can't connect to the device either. Devices using the
same APN can connect to each other - my phone can telnet to my laptop.
I haven't yet provisioned internet2.voicestream.com on any of my
phones so I can't comment on it.
I have found no serious performance or behavioural differences using
wap.voicestream.com vs. internet3.voicestream.com using my laptop.