View Single Post
  #13 (permalink)  
Old 08-06-2012, 05:35 AM
k8e's Avatar
k8e
Lurker
Offline
Threadstarter
 
Join Date: May 2012
Posts: 6
Reputation: 0
k8e is a n00b
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: Perplexed: troubleshooting dropped calls at home

Thanks - though now I'm even more perplexed. I couldn't find out how to trace the cell tower I'm connecting to, but I tried the IP address lookup you suggested, using Tracemyip/Maxmind/Whatismyip. Results:

Sprint Automatic: 246.23.244.x - Sprint PCS, no other data found
Roaming Only: 184.215.140.x - Sprint PCS, location Wichita KS (I'm in California!)
Sprint Only: 107.37.164.x - Sprint PCS, location Concord, CA (60 mi away but makes more sense than Wichita)
Roaming Only: 183.140.38.x - Sprint PCS, location Mission, KS (near Kansas City, KS)
Roaming only:173.140.38.x - Sprint PCS, Mission, KS
Roaming only:174.154.32.x - Sprint PCS, Wichita, KS
Sprint only: 107.39.83.84 - Sprint PCS, Vallejo, CA (70 mi away)
Sprint only: 107.32.58.x - Sprint PCS, Oakland, CA (40 mi away)
Roaming only: 173.154.182.x - Sprint PCS, Overland Park, KS
Sprint (automatic): 107.38.131.x - Sprint PCS, San Francisco, CA (50 miles away)

Is the "location" referring to a specific tower that I'm connected to, or the physical location of a server somewhere or something like that?

And does it make any sense that when I force Roaming, I still always get a Sprint IP address? Does it make sense that on Roaming, the "locations" are in Kansas, when I'm in California?

Maybe these tables are not kept up to date?

.

Last edited by k8e; 08-06-2012 at 07:58 PM.
Reply With Quote