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

    Telephone exchange behind pfSense

    Scheduled Pinned Locked Moved NAT
    4 Posts 3 Posters 1.6k 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.
    • M Offline
      MuadDib
      last edited by

      Hi!

      I searched the whole day about the solution on google and found out noone has the sam problem?!?

      Lets explain the situation:

      I have a telephone exchange (Aastra 470) wich was located just behind the router and worked fine! Now I'm putting the company on vlans and in meanwhile as not all devices are switched over we have a Linksys router (RV082), behind it is pfSense on a supermicro entry server (atom D525) and behind pfSense is in a seperate vlan our exchange.

      Phone exchange is registering with registrar, I can call out and the calls can get in BUT I have no audio!

      I just got the forwardings over from my router (SIP 5060 and RTP 5005) but it seems not going through. As in the exchange were more ports stated I just forwarded all of them (5004-5043). Still nothing! Here are my settings:

      The outbounds are set to static, but as I can see they are given dynamicaly?!?

      Please help me!

      Kind Regards,
      BB

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

        The NO_TRAFFIC:SINGLE is the reason, that means the RTP was sent out and got nothing in response. Why is impossible to tell from that. There's something upstream of that system doing NAT obviously since you're NATing to a private IP there. It's probable it's related in some way to whatever is upstream from there.

        1 Reply Last reply Reply Quote 0
        • S Offline
          Syntax42
          last edited by

          Change the source ports on the NAT Port Forwarding rules to allow any port.  That should update the firewall rules as well, but if it doesn't you will need to change those.

          The sender may be randomizing their source port, just like pfSense tries to do for outgoing traffic.  It is normal network behavior.

          1 Reply Last reply Reply Quote 0
          • M Offline
            MuadDib
            last edited by

            Sorry to answer that late!

            Thank you for your possible solution. As I had no time yet to get into the problem again (changed back to the old system), I'll do some research later (probably tomorrow as it's Friday).

            Regards, Bostjan

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