APN's and new device activation

**dalbers** · 09-19-2011, 06:19 PM

I recently switched from a Torch 9800 to a Torch 9810. I have tethering on my account and it used to work fine with the APN isp.cingular and I generally got decent performance.

When I first got my 9810 I just swapped SIM's and isp.cingular worked fine but today I went back and activated the phone properly with the SIM they shipped, since then when I use isp.cingular it fails to connect but using the APN wap.cingular works fine.

Is it possible that something on my account is blocking me from using isp.cingular vs wap.cingular? For what it is worth this is on a Linux system connecting over Bluetooth.

**Mister Xiado** · 09-20-2011, 10:50 AM

May have something to do with recent APN changes. I believe isp.cingular is now limited to data-only devices, and BROADBAND was created for tethering, but still operates through wap.cingular.

Good luck with getting anybody on the phone who is able to explain it, though.

**dalbers** · 09-20-2011, 01:59 PM

Originally Posted by Mister Xiado

May have something to do with recent APN changes. I believe isp.cingular is now limited to data-only devices, and BROADBAND was created for tethering, but still operates through wap.cingular.

Good luck with getting anybody on the phone who is able to explain it, though.

That was it exactly, I spoke to a rep last night who spent about 45 minutes troubleshooting with me. Eventually he went to solicit from others who suggested the use of the Braodband APN and all was well!

What is interesting about this APN is that I no longer get a public IP when tethering but instead get a private address. It isn't the end of the world but it was nice to have a public IP when I needed it.