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

    Multi-WAN and SIP UDP Session Closure

    Routing and Multi WAN
    2
    3
    1.7k
    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
      mevans336
      last edited by

      Hello Everyone,

      I'm using pfSense 1.2.3-RC1 with 2 x DHCP multi-wan connections. Everything is working great, but my SIP session continually times out. I have to force it over OPT1 as my WAN1 provider has a weird SIP proxy in my fiber ONT that breaks SIP. I can establish a connection, but after a short period of time, less than 1 hour, nothing shows in the states table for my SIP phone at all.

      Here is what should normally show:

      udp  207.x.x.x:5060 <- 192.168.1.245:5060  MULTIPLE:MULTIPLE 
      udp 192.168.1.245:5060 -> 75.x.x.x:5060 -> 207.x.x.x:5060 MULTIPLE:MULTIPLE

      When my SIP phone stops working, nothing is shown for the phone (192.168.1.245, static) at all. I have a LAN firewall rule that sends everything from 192.168.1.245 out OPT1, although I've tried using the FailOver OPT1toWAN1 pool as well without any different results.

      I thought perhaps I should increase the State Timeout in the firewall rule for the LAN VoIP rule, but since it's UDP I don't think session state applies, correct? Here is my LAN Rule:

      *  192.168.1.245  *  *  *  OPT1      VoIP

      1 Reply Last reply Reply Quote 0
      • F
        foxtrop
        last edited by

        Hi, I solved this by increasing the waiting time, registration of the phone was 3600 seconds and the waiting time in the rule that applied was 3700 seconds, and so far I have had more problems.

        1 Reply Last reply Reply Quote 0
        • M
          mevans336
          last edited by

          @foxtrop:

          Hi, I solved this by increasing the waiting time, registration of the phone was 3600 seconds and the waiting time in the rule that applied was 3700 seconds, and so far I have had more problems.

          My problem turned out to be some type of SIP proxy my fiber ONT has enabled.

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