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

    VoIP with Auerswald 5020 and 1&1 + Sipgate behind pfSense

    Scheduled Pinned Locked Moved NAT
    12 Posts 3 Posters 3.5k 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.
    • P
      pftdm007
      last edited by

      Good luck, until yesterday when I upgraded to 2.1 my VoIP immediately stop registering with the services provider…  I created a new thread at the same time as yours!

      1 Reply Last reply Reply Quote 0
      • D
        derh2
        last edited by

        From now my COMfortel 3500 also have an issue to register Sipgate-Account. Hit deactivate/activate several times an it is online at the moment. Problem with dynamic IP???

        Any idea?

        1 Reply Last reply Reply Quote 0
        • P
          pftdm007
          last edited by

          2 tyhings come to my mind:

          A package (or many) are blocking or redirecting packets from/tp the SIP server , if its the case, you have to do some testing, deactivate certain firewall rules and packages, and see when things comes back to normal.

          Otherwise, do you have Snort installed?  Snort works fairly well, but can also be a major PITA.  Look in Snort's alerts at the moment someone tries to use the VoIP system.

          For me, it was mainly Snort.  The problem was crystal clear:  Someone would call, the phone would ring once or twice, then stop.  At first I thought they hung up on me before I had a chance to pick up the phone, then I realized Snort was blocking the communication packets.  Same was true when I made a call.

          I see you use squid.  I personally got rid of this package.  I am still not sure if I have a hardware limitation on my current pfsense box, or is it squid that has MAJOR issues, but the package kills everything.  It worked back around 2010 but after that, it became a nightmare.

          1 Reply Last reply Reply Quote 0
          • D
            derh2
            last edited by

            ok, no Snort. Try that to untick the LAN interface in Squid config screen.
            Please look at my firewall screenshot nr. 2, port 10000 is blocked but I do not know why? Neccessary for STUN?

            1 Reply Last reply Reply Quote 0
            • D
              derh2
              last edited by

              So far I'm not familiar with pfSense. If it don't work as expected and there is no solution I have to to go back to my old Fritzbox.

              Please help!!

              Best regards
              derh2

              1 Reply Last reply Reply Quote 0
              • D
                derh2
                last edited by

                Not even ONE answer in 7 days???

                Why? Pleas help, I have no idea…

                This is open source and I probably know anybody here has the answer. I'm very disappointed.

                1 Reply Last reply Reply Quote 0
                • D
                  derh2
                  last edited by

                  Any idea?

                  1 Reply Last reply Reply Quote 0
                  • -flo- 0-
                    -flo- 0
                    last edited by

                    Is this still open? I cannot see the pictures in your original post. Can you post these again here in the forum?

                    1 Reply Last reply Reply Quote 0
                    • D
                      derh2
                      last edited by

                      Yes, problem is still there.

                      Sorry, I can't edit my post. Here is a link where you can see the pictures:

                      http://www.administrator.de/forum/pfsense-voip-mit-auerswald-5020-und-1und1-u-sipgate-223819.html

                      1 Reply Last reply Reply Quote 0
                      • -flo- 0-
                        -flo- 0
                        last edited by

                        Ok, got it. I would recommend to change your second Outbound NAT rules: make this valid for ports from 5060 through 5067 and disable STUN.

                        Also I second lpallard. Get rid of squid / snort at least until your phones work.

                        1 Reply Last reply Reply Quote 0
                        • D
                          derh2
                          last edited by

                          Thank you for your message. I will test that when I have enough time and give feedback.

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