NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
T Mobile Wifi calling issues
Upgraded from Nighthawk RAE500 6E router because of new home. Using the new Orbi 6E Mesh system. On T mobile. Wifi calling worked great before the switch but now it is intermediate at best. Most times, people cant hear me. Someone said you need to open ports on the system. Does anyone know which ports need to be open?
TIA
8 Replies
What Firmware version is currently loaded?
What is the Mfr and model# of the Internet Service Providers modem/ONT the NG router is connected too?
Be sure your using a good quality LAN cable between the modem and router. CAT6 is recommended.What is the size of your home? Sq Ft?
What is the distance between the router and 📡 satellite(s)? 30 feet or more is recommended in between RBR and RBS📡 to begin with depending upon building materials when wirelessly connected.What channels are you using? Auto? Try Auto and 48 on 5Ghz. Or try setting manual channel 1, 6 or 11 on 2.4Ghz and 40 to 48 channel on 5Ghz.
Any Wifi Neighbors near by? If so, how many?Enable SIP ALG on the RBR and try.
Also review this as well:
https://www.surveymonkey.com/r/G32BGFF
Any progress on this?
sbatchik wrote:
Upgraded from Nighthawk RAE500 6E router because of new home. Using the new Orbi 6E Mesh system. On T mobile. Wifi calling worked great before the switch but now it is intermediate at best. Most times, people cant hear me. Someone said you need to open ports on the system. Does anyone know which ports need to be open?
TIA
WiFi calling ports are 500 and 4500. I had the same problem, opening both of those allowed WiFi calling to work perfectly on both Android and iPhone.
I would try and enable SIP ALG on the RBR. It's disabled by default. Been testing with it enabled along with some others. Working with it enabled.
WiFi Calling does (and must) work without any port forwarding (how should it - considering there can be >250 LAN clients?) or any kind of SIP ALG.
To get some ideas what in involved, here is what T-Mobile (US) does unveil e.g. for business firewall deployments: Wi-Fi Calling on a corporate network
I agree with you that it SHOULD work without port forwarding, but I just tested it by disabling my firewall rules for ports 500 and 4500, and WiFi calling fails. As soon as I reenable the rule on those ports, my phones can make a connection on those ports and it works again. To be clear I'm using a dedicated firewall, not some settings within the Orbi.
F_V wrote:
... I just tested it by disabling my firewall rules for ports 500 and 4500, and WiFi calling fails. As soon as I reenable the rule on those ports, my phones can make a connection on those ports and it works again. To be clear I'm using a dedicated firewall, not some settings within the Orbi.
Great - so it's not the Orbi system in our case!
Off topic then: Whatever unknown firewall (or other Internet security garbage on the end point) you might have in place, some have default policies blocking virtually everything, including IPsec - IKE Authentication (udp, port 500) and IPsec NAT traversal handling Encrypted voice traffic (udp, port 4500), in both directions, incoming and outgoing.
That all does not help the OP, unless sbatchik does also operate an in-band firewall device, or some "block everything" default end point security.
