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

    4 IP phones behind PFSense, only 1 can connect to PBX

    2.0-RC Snapshot Feedback and Problems - RETIRED
    3
    6
    3.6k
    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.
    • R
      rugby
      last edited by

      We have a hosted PBX that we connect to with 3 SPA-942's and one Aastra 57i CT and with the newest release for PFSense 2.0 (today's release) we cannot connect more than 1 IP phone to the PBX at a time.

      1 Reply Last reply Reply Quote 0
      • C
        cmb
        last edited by

        Probably #1 here, or you may need siproxd if the provider breaks when rewriting source port on SIP.
        http://doc.pfsense.org/index.php/VoIP_Configuration

        1 Reply Last reply Reply Quote 0
        • S
          Supermule Banned
          last edited by

          Do the SIP phones have seperat port forward rules in the firewall???

          In my setup, the SIP phones connect to the same pbx, but on different fixed LAN addresses. I just forward the incoming IP address to the standalone SIP phone.

          1 Reply Last reply Reply Quote 0
          • R
            rugby
            last edited by

            Thanks for the ideas, I'm back in the office tomorrow (Wednesday) and will try those two ideas.  I REALLY like 2.0 so far, I'm running it at my home and it's great.

            1 Reply Last reply Reply Quote 0
            • S
              Supermule Banned
              last edited by

              I havent tested it yet…. All the menus on the left side i missing. Pretty weird....

              1 Reply Last reply Reply Quote 0
              • R
                rugby
                last edited by

                Simply installing and enabling siproxd did not fix the issue.  I had to turn off the static port map for port 5060 and everything works now.

                Firewall->NAT->Manual Outbound NAT rule generation and then click on the rule for port 5060 and uncheck Static Port.

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