ingenium

I tried to edit my last post to include a quote I found on the forum that relates to this but I think I messed up the edit.  

Sorry for the misinformation then.  My mistake.  I've tried multiple sim cards out of phones using the x.ispsn apn on my LTE modem and it never assigns an ipv4 address.   Are you sure it's not just a local ipv4 address assigned by the phone and tunneled over ipv6?

Perhaps they are using the Clearwire PLMN because it is B2 rather than B25.

Sent from my LG-LS997 using Tapatalk

X.ispsn is ipv6 only.  No ipv4.  On phones using this apn 3g takes care of ipv4 and lte takes the ipv6. 

I myself thought this roaming wouldn't kick in until a certain amount of miles outside of city limits... But I guess the roaming also exists withing city limits...

Sent from my SM-G965U using Tapatalk

Interesting! So it would seem TMobile may be broadcasting the Clear PLMN? Maybe it's part of the roaming/integration plan? Also interesting that it still shows as roaming, even though it's using a "native" PLMN. I would have assumed that was used to determine if the R indicator should be shown, but apparently not.

Sent from my Pixel 2 XL using Tapatalk

I appear to be roaming on T-Mobile. 
http://imgur.com/a/kxLrRqz
Data works and everything. Odd that it's using a Clear PLMN.
- Trip

It never rings.. I use Google Voice for my voicemail, so I get missed call notifications from that service even if the phone never realizes a call was coming in. The solution I've found that works best is to disable BC10 and disable LTE when I get home.. that typically gets the Pixel to grab onto the Airave within a few minutes of arriving home, but still not immediate. Seems odd that it doesn't search quicker when it's camped on a 1X connection from the macro site that is usually around -108 dB.
I've talked to Sprint numerous times and all they want to do is have me update my profile and PRL, then they say my Pixel must be broken. When I was trying to work through the Airave/1X800 issue I was never really able to get anyone on the phone who understood what I was trying to say.
One thing I noticed playing around with NSG was that the macro 1X uses channel 650, and the Airave is on channel 500. Are they intentionally different? I'm guessing channel assignment varies by region; would it make more sense for them to use the same channel, theoretically allowing for quicker discovery of the Airave? Or does that have no bearing on anything?
-Mike

Swapping back to a 2.5 has crossed my mind.. for my needs it was great. No camping on fringe 1X800 mostly. I only dumped my 2.5 because it died and I had to wait for a 3. If they would get some flavor of WiFi calling going on the Pixel, I wouldn't need anything..
-Mike

Anyone know how to force this damn phone onto my mb? The s8+ in the house automatically connects to the mb before we even enter the apartment but my s9+ will take anywhere from 15 minutes to several hours befure it realizes there's a blazing fast and infinitely faster b41 connection available for use instead of mostly useless b25 or 26. 
At times, airplane mode cycling helps but usually it does not. Again, all the while the s8+ is happily connected to b41 from the MB. 
What gives? 

You can probably do it if you block access to the ipsec VPN server that the LTE side uses. I did a packet capture on my router when I powered on the Airave. The CDMA side seems to do a DNS lookup for either segw01.femto.sprint.net, segw02.femto.sprint.net, ....,  or segw10.femto.sprint.net (10 possibilities, not sure how it picks one each time it boots up). And then establishes an IKEv2 VPN tunnel to it.

The LTE side does not seem to do a DNS lookup (maybe the it does it via the first tunnel?), however in my case it established a second IKEv2 tunnel to 68.31.0.1. That IP address seems to "neat", so maybe it's hard coded. You can try blocking access to that IP at your router, which would prevent the LTE side from working.

Interesting tidbit, the AIrave also looks up its assigned hostname (via DHCP) in DNS for some reason. And also first does an NTP check for time.localdomainname (where localdomainname is whatever your local domain is set as in your DHCP server). If that fails, it then queries the ntp pool. After these two things, it proceeds to the CDMA DNS lookups and establishing that ipsec tunnel.

The aggressive roaming seems to have mostly stopped for me. I've been dropping to 3G (or just 1x) in Sprint dead spots where I know AT&T has a good LTE signal.

Sent from my Pixel 2 XL using Tapatalk

I don't think that's the case. For me, SCP will correctly show WCDMA, HSPA, and EDGE (didn't have a WCDMA screenshot easily accessible).





Sent from my Pixel 2 XL using Tapatalk

That's true, they could deploy 1.4 MHz b26 and reserve it basically just for VoLTE.

Sent from my Pixel 2 XL using Tapatalk

8T8Rs can only broadcast 3 carriers at 8x8 MIMO. Dual antennas/RRUs will allow them to broadcast up to 6 carriers at 8x8 MIMO. 
Physical split sectors are also a possibility although I don’t know if that’s something Sprint is actively pursuing...

Future proofing.
Since 800 is just now rolling out in the Seattle market, all sites are in the process of being upgraded, and all sites capable of supporting the weight are getting a hexadecaport antenna along with an 8T8R. Also, from my observations, in these setups, the 8T8R antenna is only actually hooked up to a radio about half the time. The other half of the time, the antenna is installed but remains inactive and radio-less (with L2500 only broadcasting from the hexadecaport antenna). 

I was out today near Kutztown, PA, and this particular area is a Sprint dead zone (was on a back road). I noticed I had the R icon, and the signal meter had an H next to it instead of 3G or LTE. Signal Check said I was on GSM. The about phone menu said HSPA+ roaming. I couldn't make a phone call and I don't think data was working either. I have a Pixel 2. It eventually went to 3G and then Sprint LTE.

Sent from my Pixel 2 using Tapatalk

One click firmware update smoked my nice, new Sierra Wireless card. Programming is hard I suppose, at Sierra Wireless. 

I just did a packet capture on my Airave (which should use the same servers as wifi calling), and it connected to segw06.femto.sprint.net for the ipsec tunnel (ports 500 and 4500). It established two tunnels (one for LTE, and one for CDMA) to IP addresses 68.28.116.127 and 68.31.0.1

So you can likely try to explore their DNS records to build an IP list.

Sent from my Pixel 2 XL using Tapatalk

Well because we block as many things as we can on our network to prevent _______ fill in the blank.  

You could add the entire subnet 68.31.0.0 but then you may be adding addresses to... who knows.   There are a lot of vpn's that run on port 4500 so we block that to prevent students from skirting around our firewalls and content filters.

All I know is the packet capture showed my phone attempting to connect to that IP over 4500. Allowing 4500 out to that IP instantly connected my phone to Sprint WiFi.   So sprint is not even honest and forthcoming with their information as that address is nowhere on their network firewall instructions.

 

 

I don't think you'll be able to get an IP list from Sprint. They probably have a domain name that is used, and likely has many A records (or may only return 1 for load balancing reasons, preventing you from getting a list. Amazon Alexa does this for example). You could maybe sniff DNS lookups from an Airave when it's powered on, or when WiFi calling is toggled, to see if that's one way to get all the IPs.

I suppose you could allow port 4500 to any IP in Sprint's allocation (should be public somewhere). It's possible that someone might have a routed IP (hotspot plan) and decide to host an ipsec tunnel to bypass your filters, but I'd say the odds are fairly low. Regular plans have non-routable IPs so can't host servers.

Sent from my Pixel 2 XL using Tapatalk

I mean until I added  68.31.20.2 with ports 4500 Sprint Wifi Would not work.  So add 68.31.20.2 as well to your firewall rules.

I read somewhere that T-Mobile roaming was supposed to kick in when you lost Sprint LTE, and not when you fully lost Sprint signal like with other roaming. Perhaps this was an attempt at that but accidentally pushed to AT&T instead of T-Mobile. 
Also, T-Mobile is supposed to be Extended LTE, meaning counts as native data, no hard roaming cap.

I noticed a bit over a week ago that I briefly switched to att LTE roaming in Berkeley, CA in a weak area. I thought it was just an odd fluke.

It would make sense that this is a way to make VoLTE much more reliable. And perhaps they'll prioritize T-Mobile roaming (and maybe not have it count towards roaming allotment?). Ideally they'd be able to make it skip Sprint 3G only if on a call rather than all the time, to avoid using up your roaming allowance needlessly (and since LTE roaming is throttled slower than 3G).

Sent from my Pixel 2 XL using Tapatalk

Because public WiFi has an ongoing maintance cost, plus the cost to set it up and properly isolate it from your network. The magic box is just easier. You aren't responsible for it. The magic box (via LTE) also has vastly superior QoS so that one person won't bog it down.

My parents house is one place where a magic box works amazingly. Their only internet option is 3 mbps DSL. B26 only on phones, and that's upstairs only. The magic box latches on to b25 and provides 15-30 Mbps consistently. They actually use it now with a Sprint mobile broadband plan. For some people, the magic box is a better solution than an Airave or wifi calling (which won't work well on 3 mbps DSL if someone is using the internet). For businesses, it's a $0 cost, easy deployment to help customers. And they aren't responsible for what people do on it.

Sent from my Pixel 2 XL using Tapatalk

Thinking about getting a Pixel 2 to replace my HTC 10.  Still love the 10, best phone I ever had, and it's still just as snappy as ever, but the battery doesn't last anymore.  Now that I'm on summer break (teacher here!) I have to put it on the charger at least 2 times a day.  This morning, unplugged around 11AM and by 12:30 it was already at 77% and all I did was some texting.
 
I've read that you can't use Visual Voicemail with the Pixel 2, is that true?