Jump to content

ingenium

S4GRU Premier Sponsor
  • Posts

    1,715
  • Joined

  • Last visited

  • Days Won

    17

ingenium last won the day on March 6

ingenium had the most liked content!

2 Followers

Profile Information

  • Phones/Devices
    Google Pixel 4 XL
  • Gender
    Male
  • Location
    San Francisco, CA & Pittsburgh, PA
  • Here for...
    4G Information

Recent Profile Visitors

7,959 profile views

ingenium's Achievements

Member Level: 4G WiMax

Member Level: 4G WiMax (10/12)

1.4k

Reputation

  1. Sprint sites broadcast 5-6 PLMNs typically. All have 310-120 and 311-490 (and 312-530). Which your phone connects to depends on a few things, but honestly I wouldn't read too much into it. The Android API will also return a mixture of the PLMNs depending on which API method is used, if you have TNA, etc. Sometimes it will report the SIMs native PLMN, sometimes it'll report the PLMN that the cell is broadcasting, etc. On Sprint these are often different. For example, with TNA, it will report 311-490 for the SIM's native PLMN, but the LTE17 API (what the connected cell is broadcasting itself as) will be 310-120.
  2. They're limited to 40 MHz carriers in SF due to a squatter. Sprint had the same issue which was why they deployed only 2 B41 carriers. There were a few sites that had a third non contiguous carrier, but it was pretty rare.
  3. ingenium

    Pixel 4/4XL

    With a Sprint account (ie, as TNX)? It so, it's not possible yet. Pixel 3 and newer can't be TNX'd yet, regardless of whether you use eSIM or physical SIM.
  4. These are the NR CA combos that it supports
  5. I'm assuming that Unifi voice also maintains a connection to a remote server, rather than relying solely on port forwarding and the server initiating a connection for a call? If so, see if you can decrease the keep alive interval. It's possible that T-Mobile's NAT kills the connection due to inactivity. Some NAT implementations are aggressive at closing connections if they haven't seen a packet in a certain period of time. Otherwise, you'll never get a public IPv4 address on an LTE network. They're all CGNAT. Sprint had the option, but they were the only one
  6. Block the DNS lookups (return NX or something like 127.0.0.1) for epdg.epc.mnc260mcc310.pub.3gppnetwork.org and epdg.epc.mnc120.mcc310.pub.3gppnetwork.org and epdg.epc.mnc530.mcc312.pub.3gppnetwork.org And/or block UDP outbound to 208.54.0.0/16 port 4500. You could probably just block all outbound to that subnet, but if you want to be sure it just blocks wifi calling, also restrict to that UDP port. The latter is probably preferred, but the DNS block should work if you don't have the ability to set outbound firewall rules on your router. Regarding the handoffs, that has always worked reliably for me. But you might have to make sure that "always on mobile data" is enabled under developer options.
  7. Is it easy to put back together in a way where they wouldn't know that you look it apart?
  8. It depends on the device, and what the carrier_policy file from the ROM dictates. On devices still receiving updates, they'll probably enable it. Older ones not. For example, the Pixel 1 has b41 disabled entirely with a T-mobile SIM. No way to enable it without a software update, which won't come. On newer devices, they typically leave all bands enabled, but limit the carrier aggregation combos that a device will use/report based on the SIM and PLMN. Since T-mobile didn't use B41 before, they probably don't enable those CA combos. But they should get enabled with an Android update for the device at some point. They still don't have all the CA combos correct on my Pixel 4 XL, but thankfully I can enable them all with EFS Explorer until then. The reason why they limit CA combos reported by the device is because the LTE signaling message where the device reports it's capabilities has a max size. With modern devices, the number of supported combos exceeds the message size, and gets truncated, resulting in your device potentially not using supported combos on the network. So instead they limit the device to report only a subset of combos based on the PLMN. The downside to this is if a new band is deployed, the devices needs a software update to enable it for that PLMN.
  9. It's probably a 1 gbps circuit. But you have ipsec overhead, and they likely reserve some percentage of the bandwidth so that it's not saturated completely (admin functions, inter eNB communication for CA between different sites, allowing QoS to function properly for VoLTE, etc). So 700 Mbps is probably about right for 1 gbps of backhaul.
  10. You could try forcing wifi calling preferred. I started doing this before my phone got VoLTE since the call quality was so much better than CDMA. And now I keep it since VoLTE on my magic box cuts out a lot. At the very least it should prevent it from dropping calls, since it should handoff to and from VoLTE.
  11. If the closest site is a keep site, then TNX will readily use it. It's seen as native T-mobile (equivalent to 310-260 PLMN), and will be equal priority as any other T-mobile site. Basically keep sites are literally T-mobile native sites now.
  12. Same here. It seems to have happened when there was an issue that took the site down for a bit. Once that was corrected, Tapatalk integration was gone. I guess it got removed with the restore or whatever was done to fix the site.
  13. Yes. Switching to TNX will cause you to lose all Sprint roaming partners. You would only have access to T-mobile roaming, and whoever their partners are. I know there is some att roaming but it's more restrictive than Sprint. And you also lose high speed international roaming.
  14. Yes, sorry, the RRUs. Antennas (looking straight on) are 12/71 on the left, 41 middle, 2/25/66 on the right. Interestingly, there was a lot of interference around it. The video feed was really laggy. And when the drone was directly in front of the MMIMO unit it started reporting strong interference warnings. The video feed is 2.4 Gh so I guess it's close enough to 2.5 to cause issues.
  15. Got some drone pics of a recently upgraded T-Mobile site: B66/N66 + B25/N25 AHFIG center. AHBOA B71/ N71 right. Nokia Flexi Zone B12 left. Behind AHFIG is network converging box where the hybrid flex splits output and fiber to the RRUs. Gen 2 Nokia M-MIMO (courtesy of lilotimz). More pics: https://www.joshuajhill.com/s4gru/img/PT43XC804/
×
×
  • Create New...