Jump to content


S4GRU Premier Sponsor
  • Content Count

  • Joined

  • Last visited

  • Days Won


ingenium last won the day on March 6

ingenium had the most liked content!

Community Reputation

1,384 Wireless Expert


About ingenium

  • Rank
    Member Level: 4G WiMax

Profile Information

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

Recent Profile Visitors

7,134 profile views
  1. 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
  2. Block the DNS lookups (return NX or something like 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 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 w
  3. Is it easy to put back together in a way where they wouldn't know that you look it apart?
  4. 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
  5. 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.
  6. 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.
  7. 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.
  8. 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.
  9. 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.
  10. 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.
  11. 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/
  12. On the Pixel 4 at least, the MVNO profile that's loaded for the SIM disables the ability to turn on VoLTE. Same for red Pocket T-Mobile. I used root to set a prop that forces the toggle to always be present in settings and VoLTE works fine on GSMA and GSMT. AT&T is now at least allowing VoLTE on MVNOs on their network. But devices need updated to allow it to be turned on.
  13. Turn off wifi and make a call. Does your phone still display LTE? If so, then VoLTE is enabled. If not, and your phone is connected to it (you can use an app like Signal Check to confirm), then it's not enabled.
  14. Generally I don't think it matters which you connect to. I haven't seen a difference between them. It seems 310-120 might be used to regular data, and 312-530 is used for the IMS session for text and VoLTE. Or at least on VoLTE capable devices, some Android APIs report 310-120, and some report 312-530, so they're both likely being used somehow. Signal Check and CellMapper seem to always report 310-120, but Network Signal Guru always reports 312-530. 311-490 is only used for T-Mobile or ROAMAHOME. It's likely sticky and persists for a bit, but there should be no practical difference. 312-
  15. Sprint has 5-6 that they broadcast: 312-120 is seemingly non-VoLTE. 312-530 is VoLTE. 310-830 is for Magic Boxes and small cells to connect to (note that it's marked as "reserved". This means it needs a special SIM to access it). 311-882 I think is prepaid? 311-490 is for T-Mobile roaming, and 312-250 on some sites for T-Mobile native. The others are on all sites. Magic Boxes broadcast 3. 310-120, 312-530, and 311-490.
  • Create New...