Navigation

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

    VOIP works on old firewall, broken under pfsense

    NAT
    3
    3
    557
    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.
    • D
      dsterlingfes last edited by

      Greetings Forum:

      I'm upgrading from untangle (no applause necessary).  My problem is that my VOIP IP-PBX (sipXecs) stopped working.

      All my ip phones correctly register with the existing untangle configuration.

      When i swap from untangle to pfsense, all the phones drop off and fail to register with the voip server - EXCEPT for one phone for some inexplicable reason.  This one phone is capable of making and receiving calls to the outside world using a sip trunk i have with voip.ms.

      All the phones are on the same subnet with the voip server (192.168.10.0/24).  The voip server is static on 192.168.10.15.

      The second i switch the patch cord back to the untangle router, the phones find the server and register and everything works normally.

      I'm fairly experience with networking, but it feels like pfsesne is doing something behind the scenes that i don't understand.  Any hope would be VERY MUCH APPRECIATED.

      I've already followed the articles at the following links:
      https://doc.pfsense.org/index.php/VoIP_Configuration
      https://doc.pfsense.org/index.php/PBX_VoIP_NAT_How-to
      https://forum.pfsense.org/index.php?topic=108318.0
      and various others.

      THANKYOU!

      1 Reply Last reply Reply Quote 0
      • A
        Alex Atkin UK last edited by

        I assume the phones are using pfSense as the DHCP server?  If so it might be worth looking in Status -> DHCP Leases to see if they are being given an IP address.

        Also, have they been rebooted to make sure they are not retaining their old addresses?

        How are they physically connected?  Because it seems odd that a change of firewall would make any difference when from what you say they are talking directly to the PBX on the LAN.

        Surely only the PBX itself is actually talking to the firewall (apart from DHCP)?

        1 Reply Last reply Reply Quote 0
        • Derelict
          Derelict LAYER 8 Netgate last edited by

          All the phones are on the same subnet with the voip server (192.168.10.0/24).  The voip server is static on 192.168.10.15.

          That is same-subnet traffic. The firewall is not involved other than, perhaps, as a DNS and DHCP server. Probably going to have to be more specific about what is or is not working.

          1 Reply Last reply Reply Quote 0
          • First post
            Last post

          Products

          • Platform Overview
          • TNSR
          • pfSense Plus
          • Appliances

          Services

          • Training
          • Professional Services

          Support

          • Subscription Plans
          • Contact Support
          • Product Lifecycle
          • Documentation

          News

          • Media Coverage
          • Press
          • Events

          Resources

          • Blog
          • FAQ
          • Find a Partner
          • Resource Library
          • Security Information

          Company

          • About Us
          • Careers
          • Partners
          • Contact Us
          • Legal
          Our Mission

          We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.

          Subscribe to our Newsletter

          Product information, software announcements, and special offers. See our newsletter archive to sign up for future newsletters and to read past announcements.

          © 2021 Rubicon Communications, LLC | Privacy Policy