Cingular Connection Points

Greetings...

After searching resultless, thought I might try here.

Working with a customer who is insistent that wap.cingularXXXX.com vs.
isp.cingularXXXX.com (e.g. wap.cingularEDGE.com and isp.cingularEDGE.com, or
fill in your technology, e.g. UMTS, HSDPA, etc for XXXX) are different
connection paths. Meaning wap.x.com brings you into a MPLS type of
environment where as isp.x.com brings you directly to the Internet, with NO
NAT.

Any thoughts on this?

Cheers,
ChrisDo

---

› See More: Cingular Connection Points

On Fri, 12 Oct 2007 21:38:29 GMT, [email protected] (Chris
Douglas) wrote:

>Greetings...
>
>After searching resultless, thought I might try here.
>
>Working with a customer who is insistent that wap.cingularXXXX.com vs.
>isp.cingularXXXX.com (e.g. wap.cingularEDGE.com and isp.cingularEDGE.com, or
>fill in your technology, e.g. UMTS, HSDPA, etc for XXXX) are different
>connection paths. Meaning wap.x.com brings you into a MPLS type of
>environment where as isp.x.com brings you directly to the Internet, with NO
>NAT.
>
>Any thoughts on this?
>
>Cheers,
>ChrisDo
>

This is actually one area of Navas expertise. What say you John?

On 2007-10-12, Chris Douglas <[email protected]> wrote:
> Working with a customer who is insistent that wap.cingularXXXX.com vs.
> isp.cingularXXXX.com (e.g. wap.cingularEDGE.com and isp.cingularEDGE.com, or
> fill in your technology, e.g. UMTS, HSDPA, etc for XXXX) are different
> connection paths. Meaning wap.x.com brings you into a MPLS type of
> environment where as isp.x.com brings you directly to the Internet, with NO
> NAT.

I could be wrong, but somehow all that sounds a bit confused.

I do know that Cingular uses two different Access Point Names
for internet service, "wap.cingular" and "isp.cingular" (these
aren't domain names). The only difference between them that
I've been able to figure out is that "isp.cingular" gives out
real Internet addresses (and is only available with a higher
priced plan) while "wap.cingular" gives out net 10 addresses that
need to be NATed. The Internet service is perfectly ordinary
on either, other than this difference.

Dennis Ferguson

On Sat, 13 Oct 2007 03:33:36 GMT, Dennis Ferguson
<[email protected]> wrote in
<[email protected]>:

>On 2007-10-12, Chris Douglas <[email protected]> wrote:
>> Working with a customer who is insistent that wap.cingularXXXX.com vs.
>> isp.cingularXXXX.com (e.g. wap.cingularEDGE.com and isp.cingularEDGE.com, or
>> fill in your technology, e.g. UMTS, HSDPA, etc for XXXX) are different
>> connection paths. Meaning wap.x.com brings you into a MPLS type of
>> environment where as isp.x.com brings you directly to the Internet, with NO
>> NAT.
>
>I could be wrong, but somehow all that sounds a bit confused.
>
>I do know that Cingular uses two different Access Point Names
>for internet service, "wap.cingular" and "isp.cingular" (these
>aren't domain names). The only difference between them that
>I've been able to figure out is that "isp.cingular" gives out
>real Internet addresses (and is only available with a higher
>priced plan) while "wap.cingular" gives out net 10 addresses that
>need to be NATed. The Internet service is perfectly ordinary
>on either, other than this difference.

Data compression is available on isp.cingular, but not on wap.cingular,
which can make a substantial difference in effective speed. Also,
certain types of VPN only work through isp.cingular.

--
Best regards, FAQ FOR CINGULAR WIRELESS:
John Navas <http://en.wikibooks.org/wiki/Cingular_Wireless_FAQ>

Dennis Ferguson wrote:
> I do know that Cingular uses two different Access Point Names
> for internet service, "wap.cingular" and "isp.cingular" (these
> aren't domain names). The only difference between them that
> I've been able to figure out is that "isp.cingular" gives out
> real Internet addresses (and is only available with a higher
> priced plan) while "wap.cingular" gives out net 10 addresses that
> need to be NATed. The Internet service is perfectly ordinary
> on either, other than this difference.

I'm not sure what you mean by "real Internet addresses" and "gives out net
10 addresses that need to be NATed."

For example, if you use a tethered handset or aircard and run
whatismyip.com, you may see you've been given a dynamically assigned IP
address of 32.135.118.99.

Now lets say you run a web server and try to go to that address.

If someone else is on another Cingular aircard, then you could see your web
pages; but if you are using some other internet connection, you can't get
to that address.

If you want a public viewable address, you need one of these options:
http://www.wireless.att.com/business...ddressing1.jsp

On 2007-10-13, DTC <no_spam@move_along_folks.foob> wrote:
> Dennis Ferguson wrote:
>> I do know that Cingular uses two different Access Point Names
>> for internet service, "wap.cingular" and "isp.cingular" (these
>> aren't domain names). The only difference between them that
>> I've been able to figure out is that "isp.cingular" gives out
>> real Internet addresses (and is only available with a higher
>> priced plan) while "wap.cingular" gives out net 10 addresses that
>> need to be NATed. The Internet service is perfectly ordinary
>> on either, other than this difference.
>
> I'm not sure what you mean by "real Internet addresses" and "gives out net
> 10 addresses that need to be NATed."

I mean "public IP address" and "private IP address", respectively,
as the terms are defined by the AT&T web page you linked to. The
private IP addresses they give out have been 10.x.x.x addresses
when I've looked.

> For example, if you use a tethered handset or aircard and run
> whatismyip.com, you may see you've been given a dynamically assigned IP
> address of 32.135.118.99.

Sure. The distinction is that, with a public address, your PC or
handset will also know its assigned address is 32.135.118.99, so
the packets you send are routed unchanged, while with a private address
the PC will have been assigned a different address (probably 10.x.x.x
for AT&T) and a Network Address Translation (NAT) router will be
converting the net 10 address into the public address and back in
the packets you send and receive on the fly.

For many applications the distinction doesn't matter much. If you
want to be able to terminate incoming connections you generally need
a public address assigned to you, and a few applications (e.g. some
kinds of VPNs) don't work right through a NAT box.

Dennis Ferguson

Well, I actually find the following:
isp.cingular.com - doesn't resolve
wap.cingular.com - 72.246.171.173 but translates to e873.p.akamaiEDGE.net

isp.cingularedge.com - 64.124.14.82
wap.cingularedge.com - 64.124.14.82

isp.cingularumts.com - doesn't resolve
wap.cingularumts.com - doesn't resolve

isp.cingularhsdpa.com - 68.178.232.99
wap.cingularhsdpa.com - 68.178.232.99
----------------------------------------
Both of these last two are bogus - dont seem to be affliated to
Cingular/AWE, but worth mentioning.

So in reading all of the responses, may I summarize the following:

isp.cingularXXXX.com provides PUBLIC IPs
wap.cingularXXXX.com provides PRIVATE IPs 10.x.x.x range

So my lat question then is around the WAP.x.x connection. Are you guys aware
of this residing in an MPLS enviornment within cingular's APN environment?

Thanks for the assistance, I do appreciate the help. I was AWE for 11 years,
back when we were McCaw actually, but left as we were becoming Cingular.
Once you're out of the loop on these things, it really does change fast!

Best Regards,
Chris



"Dennis Ferguson" <[email protected] <mailto:[email protected]>>
wrote in message
<news:[email protected]>...
> On 2007-10-12, Chris Douglas <[email protected]
<mailto:[email protected]>> wrote:
>> Working with a customer who is insistent that wap.cingularXXXX.com vs.
>> isp.cingularXXXX.com (e.g. wap.cingularEDGE.com and isp.cingularEDGE.com,
>> or
>> fill in your technology, e.g. UMTS, HSDPA, etc for XXXX) are different
>> connection paths. Meaning wap.x.com brings you into a MPLS type of
>> environment where as isp.x.com brings you directly to the Internet, with
>> NO
>> NAT.
>
> I could be wrong, but somehow all that sounds a bit confused.
>
> I do know that Cingular uses two different Access Point Names
> for internet service, "wap.cingular" and "isp.cingular" (these
> aren't domain names). The only difference between them that
> I've been able to figure out is that "isp.cingular" gives out
> real Internet addresses (and is only available with a higher
> priced plan) while "wap.cingular" gives out net 10 addresses that
> need to be NATed. The Internet service is perfectly ordinary
> on either, other than this difference.
>
> Dennis Ferguson




Dennis Ferguson <[email protected]> wrote:
>On 2007-10-12, Chris Douglas <[email protected]> wrote:
>> Working with a customer who is insistent that wap.cingularXXXX.com vs.
>> isp.cingularXXXX.com (e.g. wap.cingularEDGE.com and isp.cingularEDGE.com,
or
>> fill in your technology, e.g. UMTS, HSDPA, etc for XXXX) are different
>> connection paths. Meaning wap.x.com brings you into a MPLS type of
>> environment where as isp.x.com brings you directly to the Internet, with NO
>> NAT.
>
>I could be wrong, but somehow all that sounds a bit confused.
>
>I do know that Cingular uses two different Access Point Names
>for internet service, "wap.cingular" and "isp.cingular" (these
>aren't domain names). The only difference between them that
>I've been able to figure out is that "isp.cingular" gives out
>real Internet addresses (and is only available with a higher
>priced plan) while "wap.cingular" gives out net 10 addresses that
>need to be NATed. The Internet service is perfectly ordinary
>on either, other than this difference.
>
>Dennis Ferguson