Need help passing a public IP address to a Unifi Phone on a Netgate 4100
-
I have a Unifi phone that I can call out on perfectly fine. However, when I I call the Unifi phone, it fails over and calls my cellphone. I worked with Unifi and according to their techs I have to pass a pubic IP address to the phone. I'm using this in my house with a Netgate 4100. How do I pass the public IP address to the phone to get it to work correctly. Everything I have tried has failed but I can always call out using the phone. Any help would be greatly appreciated.
Thank You,
Mike -
You need a STUN server. This is one of the things NAT breaks. Since your phone doesn't have a public address, STUN is used to tell callers where to find your phone and then pfSense has to pass them to your LAN. You don't need STUN on pfSense. You just have to configure your phone with a public one.
-
@mvitello Is this a phone system with an extension? It’s kind of crazy they’d suggest a public IP. One per phone? There’s 1:1 NAT but I wouldn’t really want the Internet to connect to a device like that. Port forwarding from the server IP?
-
@JKnott Thank You! I will have to look into STUN server.
-
@SteveITS No, the phone doesn't have an extension. I initially thought is was something with my Unifi controller that wasn't set up correctly. But, after the Unifi tech had me record some logs and send it to them, they told me I needed a public IP address for the phone.
-
I realize people love their Unify systems. But it is completely crazy to use a proprietary phone system that requires you purchase hardware that cannot be used with any other system and pay a subscription fee for the system to actually work. I would 1000% recommend that you return those phones and look into one of the many Asterisk/FreePBX based phone systems out there. These systems can be set up in the cloud, or on local hardware. They use regular SIP phones (which can be used across a wide range of phone systems) and if you run your own local server, there is no fee except for the IP Phone service itself. Again, there are TONS of service providers, so you can find one that meets your needs - both capacity wise and budget wise. For my home phone system, I pay less than $4 per month for unlimited incoming and outgoing calls (on a single DID number) and it includes E911 service. At that price it's worth it just for the E911 service which is why we have kept the service going (no one actually calls us on our home number).
To lock yourself into using the Unify phone service is a terrible financial decision IMHO.
That being said, it seems that pages 16-17 of the Unify phone manual talk about the networking requirements. https://nuxeo.unify.com/nuxeo/site/proxy/nxdoc/view/pdf/2f598aaf-e25c-4a1a-a80b-827b0c0d52c6
-
@sic0048 Skimmed it out of curiosity. It says "In particular, Unify Phone signaling, and media connections are always established in the outbound direction from the corporate network to the cloud." Don't see anything about a public IP...? The only firewall rules mentioned are outgoing.
I think this is that case of "say thank you, hang up, and call back to get another tech."
FWIW we're 3CX partners. They have a concept of an SBC or router phone that tunnels/proxies connections out to a remote 3CX server.