Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Yealink Phones will not register to cloud PBX behind pfense

    Scheduled Pinned Locked Moved NAT
    6 Posts 4 Posters 573 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • E
      EARDELaN
      last edited by

      Hey everyone,

      We're in the process of replacing our SonicWall with a Netgate 2100, and we've hit a bit of a snag with our VoIP setup. On the SonicWall, we had a NAT setting called "consistent NAT" checked, which allowed all our phones to register to our PBX hosted in the cloud seamlessly.

      However, after setting up the Netgate 2100 in a hybrid configuration and configuring NAT to use a static port on 5060, we're encountering issues. Our Yealink T23g phones don't seem to be able to reach the PBX. We've already opened a case with Netgate, and they've assured us that the configuration is correct. But if that's the case, why did the SonicWall work without any issues?

      We're at a bit of a loss here and would greatly appreciate any insights or assistance from the community. Has anyone else encountered similar challenges when migrating from SonicWall to Netgate for VoIP setups? Any advice or troubleshooting tips would be immensely helpful.

      Thanks in advance for your support!

      S S 2 Replies Last reply Reply Quote 0
      • S
        SteveITS Galactic Empire @EARDELaN
        last edited by

        @EARDELaN What PBX?

        We've set up several clients with Yealink phones using 3CX. 3CX has a way to have either a software program or even phone tunnel to the 3CX server "in the cloud." However it does require a correct firmware version or it will half-connect and can cause the server to blacklist the phone's public IP.

        There is a list of things at https://docs.netgate.com/pfsense/en/latest/recipes/nat-voip-phones.html

        Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
        When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
        Upvote ๐Ÿ‘ helpful posts!

        E 1 Reply Last reply Reply Quote 0
        • E
          EARDELaN @SteveITS
          last edited by EARDELaN

          @SteveITS said in Yealink Phones will not register to cloud PBX behind pfense:

          https://docs.netgate.com/pfsense/en/latest/recipes/nat-voip-phones.html

          Interesting because some devices register. What FW version do they require? We are testing with Freepbx not 3CX and the cloud PBX simply whitelists the end user IP

          S 1 Reply Last reply Reply Quote 0
          • S
            SteveITS Galactic Empire @EARDELaN
            last edited by

            @EARDELaN Well 3CX has its own firmware list at https://www.3cx.com/docs/phone-firmwares/ but that may not be relevant for you.

            Haven't used FreeBPX. I would check that doc page and maybe change the post title to include FreeBPX if you can.

            Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
            When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
            Upvote ๐Ÿ‘ helpful posts!

            1 Reply Last reply Reply Quote 0
            • planedropP
              planedrop
              last edited by

              I definitely haven't ever had issues registering Yealinks phones, we aren't using FreePBX though, I think maybe change the post title to be about 3CX? Doesn't sound like a Yealink specific issue to me.

              As for why it worked on the Sonicwall, this is one of the reasons I don't like sonicwall and most other "enterprise" firewalls, they do too much for you "automagically" so then when things don't work it's hard to know why; since we can't always know why it worked in the first place lol.

              Anyway, anti-Sonicwall rant over.

              So some devices register fine, do they make calls OK or just register? Same subnet and all that I presume?

              If you do a pcap, can you see the Yealinks trying to reach out on 5060 and just not getting a response?

              1 Reply Last reply Reply Quote 0
              • S
                sentinelace @EARDELaN
                last edited by

                This post is deleted!
                1 Reply Last reply Reply Quote 0
                • First post
                  Last post
                Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.