Also posted here http://www.pocketgpsworld.com/modules.php?name=Forums&file=viewtopic&p=163665#163665
All,
I’m not sure if this is the right section to post or that it is possible but I believe that a 3rd party app could be produced to integrate and supply Tomtom traffic data from another source. I’ve made certain assumptions as I don’t have a working Traffic account but I do have quite a lot of knowledge I have brought with me from the PC aspects of other programs.
I also don’t know if what I am proposing is right or acceptable by the mods so if it is not please delete – as far as I can see it stretches what should be done but does not go over that line… just I think.
Ok – my theory of how Tomtom gets its data ( and this comes from looking at the data files included ) is that it connects to a server on the net and grabs the latest copy of the TMC stream data from it. This is then held locally in a file and used until it is updated and replaced.
Through using a number of tools including a HTTP sniffer it may be possible ( again I know this can be done on a PC ) to trick the system that its looking at a particular server but redirect it. In PC terms this is via the hosts file.
This sever could be local on the PDA or on the net but effectively would replicate the way the Tomtom one would work – ie user id / pw / file.
Now I believe that as it downloads the TMC stream three things –
1) that this file can be located on the PDA and will probably follow the documented TMC data format which is freely available.
2) If it is the TMC format this will work as the TMC location codes are part of the Map data – ie the License is covered from that aspect – all we are doing is going to an alt source.
3) TMC / TPEG data streams are freely available from the BBC either in XML format or binary so the data is there
So to confirm this info – a HTTP sniffer needs to be run on a PDA using a live Traffic ( or weather for that matter ) account to see where it comes from, a server ( or local client ) replicating their server needs to be created , this server could take the data from server sources and convert it if needed, a redirect locally to this server would be needed, confirmation of the local TMC file / content probably will also be needed.
Now I can’t write programs my self so I hope some one may find this of use but I am more than happy to help where I can.
Terran
Did you ever get anywhere with this? It's exactly what I was thinking of just today.
I know from poking around at the files on my phone, the server address for TT Traffic is stored in a file on the memory card.
I had trouble getting rid of the traffic feature on TT6 when the free period ran out, so I cant go back to it now cos its gone.
The thing that gets me, is the fact that £££ orientated Tomtom charge for this, yet on Route 66 ,its a free service.
I too would be interested if anyone has any ideas of how to utilise other sources such as BBC for either TT5.21 or TT6
I've been busy with this issue and looked for the information send to the website of tomtom. I've got some results but i don't have a valid username and password because i'm from the Netherlands. In the netherlands this feature isn't anymore to buy. With a valid username and password i can get the information that tomtom send to you as a respons. Hopefully it's not encrypted.
If someone could help it would be great
I've looked with Wireshark and got the following information.
Code:
GET /proxy/directory.php?u=T5701046275800050bf3f517301083557 HTTP/1.1
Accept: */*
User-Agent: PDA:6.32:240x320
Host: t.tt1.nl
Connection: Keep-Alive
HTTP/1.1 200 OK
Date: Mon, 25 Aug 2008 15:38:26 GMT
Server: Apache/2.0.52 (Red Hat)
X-Powered-By: PHP/5.1.6
Content-Length: 3138
Connection: close
Content-Type: text/html; charset=UTF-8
NAVTRAFFIC
NTna2|http://t.tt1.nl/proxy/na2.php
NTna3|http://t.tt1.nl/proxy/na3.php
NTnl|http://t.tt1.nl/proxy/nl.php
NTnl2|http://t.tt1.nl/proxy/nl2.php
NTnl_hd3|http://t.tt1.nl/proxy/nl_hd3.php
NTnl_hd4|http://t.tt1.nl/proxy/nl_hd4.php
NTms_t1|http://t.tt1.nl/proxy/ms_t1.php
NTbenllu|http://t.tt1.nl/proxy/benllu.php
NTbelufritespt|http://t.tt1.nl/proxy/belufritespt.php
NTde|http://t.tt1.nl/proxy/de.php
NTdeatch|http://t.tt1.nl/proxy/deatch.php
NTdeatchplczhusk|http://t.tt1.nl/proxy/deatchplczhusk.php
NTdeatchczpl|http://t.tt1.nl/proxy/deatchczpl.php
NTdeatchitplczskhusihrlvltee|http://t.tt1.nl/proxy/deatchitplczskhusihrlvltee.php
NTfr|http://t.tt1.nl/proxy/fr.php
NTgb|http://t.tt1.nl/proxy/gb.php
NTgb2|http://t.tt1.nl/proxy/gb2.php
NTgb3|http://t.tt1.nl/proxy/gb3.php
NTgb4|http://t.tt1.nl/proxy/gb4.php
NTgb_pp1|http://t.tt1.nl/proxy/gb_pp1.php
NTgbir|http://t.tt1.nl/proxy/gbir.php
NTat|http://t.tt1.nl/proxy/at.php
NTbe|http://t.tt1.nl/proxy/be.php
NTms_t2|http://t.tt1.nl/proxy/ms_t2.php
NTch|http://t.tt1.nl/proxy/ch.php
NTes|http://t.tt1.nl/proxy/es.php
NTesad|http://t.tt1.nl/proxy/esad.php
NTadespt|http://t.tt1.nl/proxy/adespt.php
NTit|http://t.tt1.nl/proxy/it.php
NTse|http://t.tt1.nl/proxy/se.php
NTsedkno|http://t.tt1.nl/proxy/sedkno.php
NTsedknofi|http://t.tt1.nl/proxy/sedknofi.php
NTweu|http://t.tt1.nl/proxy/weu.php
NTdefake|http://t.tt1.nl/proxy/defake.php
NTnlfake|http://t.tt1.nl/proxy/nlfake.php
NTdeatchitfrcz|http://t.tt1.nl/proxy/deatchitfrcz.php
NTna4|http://t.tt1.nl/proxy/na4.php
ROUTER
ROUTER|ist-router.tt1.nl:8910
PORTLAND|http://t.tt1.nl/proxy/portland.php
ROUTER2
ROUTER|ist-router.tt1.nl:8910
PORTLAND|http://t.tt1.nl/proxy/portland.php
WEATHER
METAR|http://t.tt1.nl/proxy/weather.php
WEATHER2
WEATHER|http://t.tt1.nl/proxy/weather2.php
LOGON
LOGON|http://t.tt1.nl/proxy/logon.php
SVCACT
SVCACT|http://plus.tomtom.com/cens/psa/public/GetServiceActivationCodeForDevice.php
APN
APN_LOG|http://www.ttcode.com/apn/log_apn.php
TEST_BIN|http://www.ttcode.com/apn/bin_test.php
PRODACT
PRODACT|http://www.ttcode.com/ttcode/GetActivationCode.php
MESSAGE
MESSAGE|http://t.tt1.nl/proxy/message.php
BUDDY
BUDDY|http://t.tt1.nl/proxy/buddy.php
ROADCONDITIONS
ROADCONDITIONS|http://t.tt1.nl/proxy/roadconditions.php
DYNSC
DYNSC|http://t.tt1.nl/proxy/cams.php
FUELPRICES
FUELPRICES|http://t.tt1.nl/proxy/fuelprices.php
FUELPRICESEUROPE|http://t.tt1.nl/proxy/fuelpricesEU.php
SPD_MD
MD|http://plus.tomtom.com/cens/spd/proxy/md.php
SPD_PD
PD|http://plus.tomtom.com/cens/spd/proxy/pd.php
SPD_VD
VD|http://plus.tomtom.com/cens/spd/proxy/vd.php
SPD_CD
CD|http://plus.tomtom.com/cens/spd/proxy/cd.php
SPD_NV
NV|http://plus.tomtom.com/cens/spd/proxy/nv.php
SPD_DD
DD|http://plus.tomtom.com/cens/colibri/proxy/proxyColibri.php
SPD_SD
SD|http://plus.tomtom.com/cens/satdata/proxy/sd.php
SPD_CU
CU|http://plus.tomtom.com/cens/spd/proxy/cu.php
ACCOUNT
ACCOUNT|http://plus.tomtom.com/cens/psa/public/GetAccountInfoForDevice.php
MISC
MB|http://plus.tomtom.com/cens/colibri/proxy/proxyMailback.php
ACCOUNT2
ACCOUNT|http://jplus.tomtom.com/cens/sam/webservice/tomtom/sam/getAccountInfo2ForDevice.jsp
GET /cens/psa/public/GetServiceActivationCodeForDevice.php?uid=TKNJ%40IIJ%2eNL&pw=206e71777664&svc=NAVTRAFFIC&body=AB5HLCV3QE&lid=NL&pn=PDA%3a6%2e32%3a240x320&vnr=6032&muid=T5701046275800050bf3f517301083557&dn=Kaiser&rect=-1100000x3450000x4500001x7150001&tr=NTweu&z=031950 HTTP/1.1
Accept: */*
User-Agent: PDA:6.32:240x320
Host: plus.tomtom.com
Connection: Keep-Alive
Cookie: __utma=219866524.1293524131.1214428014.1214428014.1214428014.1; __utmz=219866524.1214428014.1.1.utmccn=(direct)|utmcsr=(direct)|utmcmd=(none); tt_locale=5
HTTP/1.1 200 OK
Date: Mon, 25 Aug 2008 15:38:28 GMT
Server: Apache/2.0.52 (Red Hat)
X-Powered-By: PHP/5.1.6
Content-Length: 164
Connection: close
Content-Type: text/html; charset=UTF-8
156 200 6 211 [email protected] 278 Onbekende combinatie van gebruikersnaam en wachtwoord. Voer a.u.b. opnieuw in.216 Error code: 20241401 00
I see that some people have had problems with connecting to GPRS with XDAs, but haven't found any posts with anyone successfully finding the settings that work.
I have an original XDA.
Does anyone have working GPRS settings for easymobile (in the UK) please?
Many thanks
The settings are actually on the easymobile site!
For the lazy though...
GPRS access point – data.uk
Authentication type – Normal
User name – user
Password - one2one
How much does it cost?
Connecting to the Mobile Internet via GPRS will cost just £3 to send/receive 1 Megabyte of Data.
thanks alan,
I had looked on their site and seen the list, and even contacted the customer services (who weren't any help), I saw all the settings but didn't know where to put them, I was adding the IP address which obviously isn't needed.
Anyway, it works!!!!!!!!!!!!!!
And I'm not lazy
If you fancy a job on the easymobile help chatroom I'm sure they'll take you on.
I wish I could get WLM to work on my phone. I've asked around a few times and only Nitro has replied saying: WLM doesn't work with proxy. But I can't get pocket MSN to work either.
I've tried intalling Pocket MSN as well as Live MSN. None of both work via GPRS[E]. Live works over Wi-Fi. I read around that someone else had been having a similar problem since installing latest radio?? Don't know if I should go back(if its posible?) to an older radio, or if there is a newer one, or even if that would really have an impact. On my other SDAII(with OEM TMO rom, WM5) I can use pocket msn w/o problems. I don't have a problem using 3rd party as PalRingo for chat, but I need the Hotmail email and their Web version don't allow me to follow links, view images, etc. Could anyone please help with this?
Additional info:
I've tried WM6-SP1 Platinum by NiTroGen and WM6.1-Clean by GnatGoSplat.
I've tried just about every WLM version that I've found, even some downloaded directly from Windows.
I've tried various Pocket MSN found on here and one downloaded from Windows.
Device Info:
Radio: 4.1.13.28_02.61.01
Operator: 10.0.0.15341
Thank You all in advance for reading. A very special thanks to all ROM cookers and those who generously help us. I would apreciate any help I can get.
Note: I have posted this Thread in General as per Moderator recomendation. Perhaps, maybe this problem has happened to others, all though it might be specific to my SDAII(Tornado).
Help with Windows Live Messenger
Has anyone found a solution or options to this?
Suncom GPRS MSN IM
Same problem here man . I'm also with Suncom using an (unlocked htc 8125 wm5)
I've been using various IM clients such as :
Agile Messenger
IM+
WLM
PocketMSN
in order to see if anything works.
All have failed through GPRS.
The only IM client that works on my HTC Wizard cingular's 8125 is Ebuddy...(java client witch IMO surely sucks )
My GPRS settings are utilizing suncom's APN witch is :mobileinternet
I'm also able to connect using wifi with all the clients but that really is just like having a motorcycle with training wheels . Just plain retarded...
I found out with [email protected] that I can establish a link when docked with ActiveSync as it uses the current connection in the computer to connect.
A really interesting fact is that i tried to run PocketIRC using GPRS but was also unsuccessfull to connect. This triggered me to start further research and so I did.
I d/l -vxUtil- and learned that the Wizard (phone) was succesfully retrieving names from the DNS server (66.150.38.11 is a suncom dns server ) using GPRS and converting them into IP addresses but then the oddest thing happend with the hops . it showed what I believe its a private default VPN address 10.32.51.1
1 10.32.51.1 RTT = 718 ms TTL=0
2 10.32.51.254 RTT = 1008 ms TTL =0
3 *Request time out
4 *Request time out
5 *Request time out
Trace Route Canceled
Trace Complete
Out of pure curiosity I decided to run the trace through my computer that uses a wifi connection and the output was different :
Tracing route to tcp.mws.mobile.live.com [65.55.161.252]
over a maximum of 30 hops:
1 4 ms 3 ms 3 ms 192.168.1.1
2 29 ms 29 ms * 12.192.56.33
3 134 ms 215 ms 121 ms 12.118.166.189
4 93 ms 90 ms 91 ms gbr1.ormfl.ip.att.net [12.123.32.74]
5 92 ms 95 ms 88 ms tbr1.ormfl.ip.att.net [12.122.1.70]
6 92 ms 92 ms 94 ms cr1.ormfl.ip.att.net [12.122.21.33]
7 88 ms 93 ms 95 ms cr2.attga.ip.att.net [12.122.31.29]
8 94 ms 94 ms 94 ms cr1.attga.ip.att.net [12.122.2.133]
9 104 ms 87 ms 94 ms cr2.wswdc.ip.att.net [12.122.1.174]
10 96 ms 96 ms 97 ms tbr2.wswdc.ip.att.net [12.122.16.118]
11 94 ms 93 ms 99 ms gar1.ascva.ip.att.net [12.122.80.197]
12 96 ms 88 ms 87 ms 12.118.44.62
13 90 ms 144 ms 92 ms ge-0-3-0-57.ash-64cb-1b.ntwk.msn.net [207.46.41.57]
14 91 ms 91 ms 92 ms ge-0-1-0-0.bl2-64c-1b.ntwk.msn.net [207.46.37.41]
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
Witch makes me believe that the route is not actually passing through from internal servers of suncom aka FILTERING. (correct me if I'm wrong gurus)
And finally the whole twist about this whole post is that if its utilized as a modem (8125) with the modem link program ... the output if you trace comes back as :
Tracing route to tcp.mws.mobile.live.com [65.55.161.252]
over a maximum of 30 hops:
1 718 ms 1175 ms 641 ms 10.32.51.1
2 720 ms 916 ms 659 ms 10.32.51.254
3 * * * Request timed out.
4 * * * Request timed out.
But I'm still able connect to MSN messenger and other Windows XP IMS
In conclusion IMO believe that Suncom is restricting access to servers like tcp.mws.mobile.live.com in order to gain revenue with Internal Packeges... I'll continue to report more information any help to solve this issue will be appreciated by many.
While all this data is confusing at 3AM LOL, you are getting close the point where I just about got to. Concluding that Suncom is blocking the M$ Server. However, why was it working with TMO WM5 Ship Rom? Now, to make this even more crazy, my 2nd phone was untouched. I finally Application Unlocked it, SuperCID'd and installed WM6... Decided to try to flash back to ShipRom and guess what? Now Pocket MSN don't work even with Ship Rom and Radio...
Meanwhile, You can use Palringo for instant messenging, its free and works pretty nice, but, what about Hotmail? The web version $nks. Can see attachments, images or click on links, can't copy paste, etc. So thats why I keep trying.
I've been going crazy playing with Connection Settings believing it had something to do with them. But I've just about tried every combination posible, have even made some crazy ones, that work for everything else, but for MSN, which again brings us to the thought that its Suncom blocking MSN.
Now, have you tried using the phone as modem? Well guess what, if you use phone as modem for your PC, MSN on the PC works... Please enlighten me!
BTW, I tried to reply to your mail, but you have it blocked on your settings.
EDIT: I just re-flashed TMO WM5 Ship Rom and Pocket MSN works. I tried to download VXutil, but it won't install on phone. I thought I could figure what server its connecting and with some registry entries we could solve this problem.
cellphone89 said:
Same problem here man . I'm also with Suncom using an (unlocked htc 8125 wm5)
I've been using various IM clients such as :
Agile Messenger
IM+
WLM
PocketMSN
in order to see if anything works.
All have failed through GPRS.
The only IM client that works on my HTC Wizard cingular's 8125 is Ebuddy...(java client witch IMO surely sucks )
My GPRS settings are utilizing suncom's APN witch is :mobileinternet
I'm also able to connect using wifi with all the clients but that really is just like having a motorcycle with training wheels . Just plain retarded...
I found out with [email protected] that I can establish a link when docked with ActiveSync as it uses the current connection in the computer to connect.
A really interesting fact is that i tried to run PocketIRC using GPRS but was also unsuccessfull to connect. This triggered me to start further research and so I did.
I d/l -vxUtil- and learned that the Wizard (phone) was succesfully retrieving names from the DNS server (66.150.38.11 is a suncom dns server ) using GPRS and converting them into IP addresses but then the oddest thing happend with the hops . it showed what I believe its a private default VPN address 10.32.51.1
1 10.32.51.1 RTT = 718 ms TTL=0
2 10.32.51.254 RTT = 1008 ms TTL =0
3 *Request time out
4 *Request time out
5 *Request time out
Trace Route Canceled
Trace Complete
Out of pure curiosity I decided to run the trace through my computer that uses a wifi connection and the output was different :
Tracing route to tcp.mws.mobile.live.com [65.55.161.252]
over a maximum of 30 hops:
1 4 ms 3 ms 3 ms 192.168.1.1
2 29 ms 29 ms * 12.192.56.33
3 134 ms 215 ms 121 ms 12.118.166.189
4 93 ms 90 ms 91 ms gbr1.ormfl.ip.att.net [12.123.32.74]
5 92 ms 95 ms 88 ms tbr1.ormfl.ip.att.net [12.122.1.70]
6 92 ms 92 ms 94 ms cr1.ormfl.ip.att.net [12.122.21.33]
7 88 ms 93 ms 95 ms cr2.attga.ip.att.net [12.122.31.29]
8 94 ms 94 ms 94 ms cr1.attga.ip.att.net [12.122.2.133]
9 104 ms 87 ms 94 ms cr2.wswdc.ip.att.net [12.122.1.174]
10 96 ms 96 ms 97 ms tbr2.wswdc.ip.att.net [12.122.16.118]
11 94 ms 93 ms 99 ms gar1.ascva.ip.att.net [12.122.80.197]
12 96 ms 88 ms 87 ms 12.118.44.62
13 90 ms 144 ms 92 ms ge-0-3-0-57.ash-64cb-1b.ntwk.msn.net [207.46.41.57]
14 91 ms 91 ms 92 ms ge-0-1-0-0.bl2-64c-1b.ntwk.msn.net [207.46.37.41]
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
Witch makes me believe that the route is not actually passing through from internal servers of suncom aka FILTERING. (correct me if I'm wrong gurus)
And finally the whole twist about this whole post is that if its utilized as a modem (8125) with the modem link program ... the output if you trace comes back as :
Tracing route to tcp.mws.mobile.live.com [65.55.161.252]
over a maximum of 30 hops:
1 718 ms 1175 ms 641 ms 10.32.51.1
2 720 ms 916 ms 659 ms 10.32.51.254
3 * * * Request timed out.
4 * * * Request timed out.
But I'm still able connect to MSN messenger and other Windows XP IMS
In conclusion IMO believe that Suncom is restricting access to servers like tcp.mws.mobile.live.com in order to gain revenue with Internal Packeges... I'll continue to report more information any help to solve this issue will be appreciated by many.
Click to expand...
Click to collapse
Suncom Proxy Blocking
Yeah I also noticed that Modem link Is currently working fine opening ports to MSN Messenger in my computer but! the servers aren't the same actually take a look:
PocketMSN connects to tcp.mws.mobile.live.com [65.55.161.252] Doesn't connect using GRPS
Palringo uses echo.palringo.com [192.97.243.227] CONNECTS!!!
Agile Messeneger dp.msnmessenger.akadns.net [65.54.239.210]Doesn't connect using GRPS
They are all using proxies to connect to the MSN the only difference withing them is that Palringo seems to be using a private proxy in order [that has not been blacklisted].
Also I believe that the reason that your wm5 phone connected was because the server that MSN Messenger was using was not yet blacklisted. Still I can't say for certain . What ROM where you exactly using ? Do you still have it?
When was the last time it worked with msn?
I'm almost convinced now that Suncom is actually blocking ports and servers.
BTW thanks for Palringo I really needed it
cellphone89 said:
Yeah I also noticed that Modem link Is currently working fine opening ports to MSN Messenger in my computer but! the servers aren't the same actually take a look:
PocketMSN connects to tcp.mws.mobile.live.com [65.55.161.252] Doesn't connect using GRPS
Palringo uses echo.palringo.com [192.97.243.227] CONNECTS!!!
Agile Messeneger dp.msnmessenger.akadns.net [65.54.239.210]Doesn't connect using GRPS
They are all using proxies to connect to the MSN the only difference withing them is that Palringo seems to be using a private proxy in order [that has not been blacklisted].
Also I believe that the reason that your wm5 phone connected was because the server that MSN Messenger was using was not yet blacklisted. Still I can't say for certain . What ROM where you exactly using ? Do you still have it?
When was the last time it worked with msn?
I'm almost convinced now that Suncom is actually blocking ports and servers.
BTW thanks for Palringo I really needed it
Click to expand...
Click to collapse
More facts: I just installed WML on the phone, and It gives me the same error that it gave me with WM6.0 ROM's and Updated Radio. So that forsure, takes away my believe's that it had something to do with upgrading to WM6.x and Radio.
Yes I still have the ShipRom. This is the file name: Tor_TMOUS_10140_191916_10900_SHIP.exe I downloaded it but don't have the site I got it from. I'll search and see if I can find it and will edit this post and add. Or I can send to you, would have to be on a DC through AOL or Yahoo, its too large to send over email. But, its for TMO SDAII(HTC-Tornado) not for the 8125Cingular. Now, what if we can figure what file does the connection? Would a backup of that file moved onto another mobile, force pmsn to work?
markanthonypr said:
More facts: I just installed WML on the phone, and It gives me the same error that it gave me with WM6.0 ROM's and Updated Radio. So that forsure, takes away my believe's that it had something to do with upgrading to WM6.x and Radio.
Yes I still have the ShipRom. This is the file name: Tor_TMOUS_10140_191916_10900_SHIP.exe I downloaded it but don't have the site I got it from. I'll search and see if I can find it and will edit this post and add. Or I can send to you, would have to be on a DC through AOL or Yahoo, its too large to send over email. But, its for TMO SDAII(HTC-Tornado) not for the 8125Cingular. Now, what if we can figure what file does the connection? Would a backup of that file moved onto another mobile, force pmsn to work?
Click to expand...
Click to collapse
Humm... how about running wireshark in your pc in order to find out where exactly is it communicating to ?
If its not too much could you send me zipped copy the Pocket MSN that works I would like to see what I could do about it.
Also try to:
1) Install wireshark
2) connect activesync
3) run wireshark
4) connect and see where it goes.
If you need help just send me an email
Hello, I hope someone can help!
We have an application running on a variety of Windows Mobile devices linking to an office program via UDP over the 02 GPRS network. This has been running fine on over 1000 devices for the past 3 years until 20/09/08 when the data reception has become intermittent/unreliable. 02 claim not to have changed anything at their end and we know of other companies still running on 02 so it must be possible!
What we need is for someone on a voluntary / one-off fee basis to look at our code and identify the issue so that we can make any necessary changes.
Hopefully someone out there can help us? Obviously time is really of the essence too
Matthew Bradford
[email protected]
All sorted now - thanks for looking!
This might need to be combined with henrybravo as his post really was the primer for this research.
Get a drink this is going to take a while.
What does default,admin,hipri,agps mean? Its actually really important.
Look here for a start. http://developer.android.com/reference/android/net/ConnectivityManager.html#TYPE_MOBILE
wireless.cingular.com is IP 67.215.65.132 which is owned by open DNS. Interesting I thought, Because this is the proxy that has a username and password to allow traffic through and I'm guessing to also record that traffic too. But what really interests me if the range that is owned by OPENDNS/AT&T its HUGE! So we are all trying to use 67.215.65.132 port 80 and port 8080 works too. So if you ping wireless.cingular.com:80 or wireless.cingular.com:8080 you get the address 67.215.65.132. I do not know if switching the IP is against the terms of service. So I'm going to check around and see if I need 67.215.65.132 at all or can I use my own opendns?
NetRange: 67.215.64.0 - 67.215.95.255
CIDR: 67.215.64.0/19
OriginAS: AS36692
NetName: OPENDNS-NET-3
NetHandle: NET-67-215-64-0-1
Parent: NET-67-0-0-0-0
NetType: Direct Assignment
RegDate: 2007-10-12
Updated: 2008-05-05
Ref: http://whois.arin.net/rest/net/NET-67-215-64-0-1
I've been going some serious searching and I found these new addresses for Mmsc.cingular.com
The usual address 166.216.166.19
and these
166.216.198.19
166.216.230.19
198.228.238.58
166.216.198.0/23
An AT&T Mobility Network
GPS
Lets talk about our favorite issue AGPS. (GPS) 209.183.32.11 and 209.183.32.10
http://www.robtex.com/route/209.183.32.0-23---a-cingular-stc-network.html
Here is the server AGPS IP: 18:24:35 [D:GPS] GPS: [SetupGPSConfigForGetPosition] NEW ServerIP = 209.183.32.11
(Above taken from window build)
Perhaps this is a NEW GPS APN for XDA Family.
If you found this interesting say thank you. I'm getting dinner now and I'll try the APN GPS when I'm done with dinner. It might be better if it has its own APN.
Thanks, Jason
Why not post this in the apn thread, why start a new one?
Sent from my Inspire 4G using xda premium
Thread closed by OP request.