Jump to content

ingenium

S4GRU Premier Sponsor
  • Content Count

    1,382
  • Joined

  • Last visited

  • Days Won

    8

Everything posted by ingenium

  1. It could be region based, sort of like T-Mobile roaming. Or set that if it sees a certain network to always prefer it. I know Movistar is definitely a preferred partner is all countries, but I've roamed off of them before. Maybe in more rural areas there is more roaming flexibility. At least in Barcelona, Movistar does have a more dense network it seems, and has 50% of subscribers, so it's fine. I'm using an Orange SIM now, and despite 20+20+10 (sometimes 20+20+10+10) FDD CA, it feels congested often. Sent from my Pixel 3 XL using Tapatalk
  2. You'll need root and Network Signal Guru (NSG) for that. I don't believe that information is available via the Android API, and you'll have to interface directly with the modem's engineering interface to get it. NSG is one option, or if you can find carrier grade analysis software for Windows (TEMS, Actix, etc), then you don't need root and can plug your phone into your computer to retrieve modem engineering data. Sent from my Pixel 3 XL using Tapatalk
  3. You can sometimes force it to use a different carrier. It worked for me in January in Costa Rica, but I'm in Spain now and while Sprint has roaming agreements with all 4 carriers here, it will only use the biggest one (Movistar). I can auth onto the others, but as soon as data tries to pass it overrides the manual network selection, goes back to automatic, and switches to Movistar. So they may have changed something recently, or it could just be country specific, but you can sometimes pick a different carrier. https://www.sprint.com/en/support/solutions/international/international-roaming-partners.html#S Sent from my Pixel 3 XL using Tapatalk
  4. It seemed fine, but it wasn't on a site that I connected to very often, and I didn't do a lot of testing. There are only a handful of sites that I've seen with the third carrier. If I remember correctly it seemed to load balance as expected, but it still preferred to use the 2 contig carriers if I did a speed test. Light web usage would allow me to stay on the third carrier. It wasn't wasn't very loaded at the time I tested (covered a major highway interchange that is very congested during rush hour), so I'm not sure how it would perform under load. Sent from my Pixel 3 XL using Tapatalk
  5. On my Pixel 3 XL, there was CA on the first 2 carriers as usual, but no CA at all with the third. It was a non contig 20 MHz carrier. Sent from my Pixel 3 XL using Tapatalk
  6. Is it contig? In SF some higher usage sites got a third, non-contig carrier to presumably help with load. Sent from my Pixel 3 XL using Tapatalk
  7. I would be really curious to see your packet captures. 68.28.x.x is CDMA on my Airave 3 and 4, and 68.31.x.x is LTE (and wifi calling). It seems like yours doesn't fit that in CDMA nor LTE. Definitely report back the IPs that you discover. You can also let it power on and dump the state table on your firewall. Look for the two connections on UDP port 4500. That's a quick and easy way to grab the IPs. Sent from my Pixel 3 XL using Tapatalk
  8. I don't believe so. None of the Airaves have. I also heard that 1x HD Voice does not work on any device which supports VoLTE (including devices which support it but don't have it enabled yet, such as the S9). It has something to do with the way calls are routed in the backend, VoLTE capable devices are routed differently than non-VoLTE ones. Sent from my Pixel 3 XL using Tapatalk
  9. For mine it took about 1-2 days before phones would even see it in neighbors. Then they started connecting to it about a day later. Basically, I think there's some sort of automatic integration that has to go occur at the network level. I say this because when it was finished, my MB had changed PCIs. I think anytime a device like this comes online, all the others like it in an area change PCIs. Small cells behave the same way. Sent from my Pixel 3 XL using Tapatalk
  10. I think dd-wrt may actually be one of the firmwares that does restrict it, or at least has an option to. I haven't used dd-wrt in 10+ years though so I'm not sure where it would be in the settings. If your mom has Chrome, you can use Chrome remote desktop to remotely connect to her computer and browse through the router settings yourself. Sent from my Pixel 3 XL using Tapatalk
  11. You shouldn't need to change anything on your router. It's just saying that those ports shouldn't be blocked. The Airave uses UDP encapsulated IPsec, so it should just work out of the box for most people. The Airave 4 to does not provide wifi. The 3 did. Sent from my Pixel 3 XL using Tapatalk
  12. CDMA likely needs GPS to come online. Are there any obstructions outside the window that might block the signal? If so, she might want to try a different window. I'd also have her unplug it and plug it back in to make sure it's in securely. When I plugged my antenna in, it got a GPS lock within a minute. Worst case, have her power cycle it and let it sit overnight. New satellites will pass overhead that it might have better luck locking onto. Once it gets a lock, I don't think it needs to get it again until it's power cycled. Edit: is LTE up? If so, there's also a possibility that your router is only allowing each MAC address to have a single IP. I think I've seen a few routers configured that way before
  13. I'm guessing that it's using 5G as a secondary/tertiary carrier, and that LTE is PCC (so it can use it for upload). Sent from my Pixel 3 XL using Tapatalk
  14. It is. Macro 1x is garbage in most areas and has been for years. They've cut CDMA carriers so much that they're too overloaded. As a result, quality is dropped to support more calls rather than dropping them or having them fail. The more calls there are on a macro, the worse it gets. I switched to Google Voice when possible for calls about 4-5 years ago because the robo garble and poor quality made it unusable. 1x800 seems to be worse than 1x1900. That's the only reason I have an Airave actually. Pixels (before the 3) didn't support wifi calling, and even though my macro 1x signal is -75, I needed an Airave to use 1x for calls. The difference is night and day. Sent from my Pixel 3 XL using Tapatalk
  15. It does work with VoLTE actually, but it's likely not on the whitelist yet, so it needs to be forced. Unlike the Airave 3, it actually works. The 3 would work for a bit, then break all calls and SMS. I'm guessing Sprint won't "allow" it (by whitelisting it on phones) until they launch it network wide, but it does work. Sent from my Pixel 3 XL using Tapatalk
  16. I can confirm that you can't edit the site notes for it in the most recent beta. I receive the same error. Sent from my Pixel 3 XL using Tapatalk
  17. Yes, no one needs that speed on their phone. But I see it as a proxy for how much capacity is available, since the network is currently unloaded. So in that sense, 800+ Mbps means that a site can handle a lot of traffic without getting congested, vs 400 Mbps means it can absorb about half as much traffic before becoming congested. Sent from my Pixel 3 XL using Tapatalk
  18. Got my Airave 4 and have it setup. It uses the same earfcn as my Magic Box, 39874. CDMA 1x uses channel 1125, which is right in the middle of the 15x15 B25 carrier, so I'm guessing it's misconfigured. I ran a packet capture on it during setup. It requests 2 IP addresses, one for the CDMA side and one for LTE. This is in contrast to the Airave 3 which used a single IP. So the internals are very much completely separated on the 4, much more so than on the 3. Both IPs are for the same MAC address (ie, the Airave 4 ethernet port has a single MAC, but 2 IPs assigned). At startup, the CDMA side does an NTP query to the hardcoded, private address 10.1.2.40 for some reason, before falling back to querying the NTP pool. The LTE side also queries the pool, but does not try the hardcoded address first. The CDMA side then looks up SEGW-Airspan-Combo-3G-GLOBAL.SPCSDNS.NET and opens an IPsec tunnel to it. It then looks up segw06.femto.sprint.net and establishes an IPsec tunnel to that address. This is the same domain range as the Airave 3. Valid options seem to be segw01.femto.sprint.net through segw10.femto.sprint.net. This tunnel is what is used for CDMA, so I'm guessing the first tunnel was used for configuration? The LTE side looks up SEGW-Airspan-Combo-GLOBAL.SPCSDNS.NET and establishes an IPsec tunnel to it. It then looks up SEGWAKR-PUBL.sc.spcsdns.net and establishes an IPsec tunnel to that address. I believe the latter is the tunnel for LTE, and the first is the configuration tunnel. The LTE side is similar to what is seen on the MB Gold. The Gold first establishes an IPsec tunnel to SEGW-AIRSPAN-IFUR-GLOBAL.SPCSDNS.NET, and then a tunnel to SEGWSKT-PUBL.sc.spcsdns.net. Note the similarities in the addresses. It's also interesting that the Airave 4 uses hardcoded DNS servers, querying 3 of them at the same time for the final IPsec tunnel.
  19. Nothing besides doing an airplane toggle Sent from my Pixel 3 XL using Tapatalk
  20. Either there was a super low signal, or B41 LTE was very congested. While 5G was empty. Not really impressed with the 5G speed seeing as no one else was on it. Maybe the site doesn't have enough backhaul? And that definitely looks like B41 LTE for upload on 5G. Sent from my Pixel 3 XL using Tapatalk
  21. What shows up on your account? Does it work? Sent from my Pixel 3 XL using Tapatalk
  22. They don't even provision the backhaul at many sites to fully utilize the B41 on air. There's no point in putting even more on air if they don't give it enough backhaul. Sent from my Pixel 3 XL using Tapatalk
  23. Now that's interesting, and could be the issue. On Verizon my Pixel 3 will turn off CDMA, but on Sprint with VoLTE it keeps CDMA on and maintains SRLTE. So if I start to roam, presumably it will quickly drop to CDMA. For some reason it sounds like that isn't happening on your Samsung phone. I'm surprised it turns off CDMA actually. Sent from my Pixel 3 XL using Tapatalk
  24. In that case I'm not sure. I won't have mine until the end of the week, so I can't do a packet capture to analyze. I'd say just leave it overnight and see if it's working in the morning. Sent from my Pixel 3 XL using Tapatalk
×
×
  • Create New...