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

    SIP register Problem

    Scheduled Pinned Locked Moved General pfSense Questions
    4 Posts 3 Posters 597 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.
    • A
      admins
      last edited by

      Hi all
      I hope that someone could help me.
      Env.:
      PFSense 2.4.2 without additional packages. 1 Yealink W52P in LAN 1. The VOIP telephone connect to a swiss sip Provider outside of the pfsense to port 5060.
      The Registration failed. If I sniff, I see, that the phone makes a dns query and receive the correct IP. May it couldn't connect to the Provider.

      Checks:

      • I've tested with an other SIP phone, same
      • Sipproxy (only Change the outbound/inbound Interface), set outboundproxy in the sipphone to the pfsense gw ip, same

      Has anyone an idea?

      admins

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

        Step 1: Uninstall siproxd. It will almost certainly only hurt, not help.

        Step 2: What else is in the capture after the phone obtains the IP address to connect to?

        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
        • A
          AndrewZ
          last edited by

          Not related to pfSense yet.
          Remove all your customization - Sipproxy, outboundproxy, etc., then speak to your provider.
          If you want to find a root cause yourself - look into your SIP traffic on both LAN and WAN.

          1 Reply Last reply Reply Quote 0
          • A
            admins
            last edited by

            Helo all
            I've found the Problem. It wasn't on the pfsense.
            It was a DOS-Prevention on a Zyxel Switch.

            admins

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