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

    Routing SIP traffic over OpenVPN using different gateways

    Scheduled Pinned Locked Moved NAT
    3 Posts 3 Posters 876 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.
    • N
      NickyDoes
      last edited by

      I am unable to route SIP audio over a point-to-point OpenVPN connection between home and work. The home network is on its own subnet (10.71.73.0/24). The work network is on a different subnet (10.0.0.0/8). Most internet traffic passes beautifully over the VPN. SIP calls do not.

      Calls from work (10.0.0.0/8, where the PBX server is) to home (10.71.73.0/24) ring the phone but do not include audio.

      Calls from home (10.71.73.0/24) will not establish (the phone gateway reports no connection).

      This link is the closest I found to my situation. I generally understand my troubles may be because I am spanning two gateways. I do not understand how to fix the problem.

      My home subnet (10.71.73.0/24) is easily changed. I cannot modify my work subnet. I do have essentially full control over both VPN endpoint configurations.

      1 Reply Last reply Reply Quote 0
      • L
        lmartinez073
        last edited by

        Hi

        Just checking if you found the solution to the SIP configuration, Also, what client are you using for smart phones?

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

          Your problem is probably that 10.0.0.0/8 and 10.71.73.0/24 are conflicting networks.

          Nothing special needs to be done to SIP over OpenVPN.  There's usually no NAT so it's easy.

          Chattanooga, Tennessee, USA
          A comprehensive network diagram is worth 10,000 words and 15 conference calls.
          DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
          Do Not Chat For Help! NO_WAN_EGRESS(TM)

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