ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    All Yealink Phones Down at One Site

    IT Discussion
    pbx voip sip yealink yealink t42s freepbx 14 freepbx asterisk 15 asterisk
    10
    23
    2.0k
    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.
    • JoelJ
      Joel
      last edited by

      I had this issue with a small office network but Polycom phones. I upgraded all firmware on the switches and router, rebooted everything to no prevail. It only started working when I factory re-set the main router and re-deployed from scratch! so strange!

      1 Reply Last reply Reply Quote 0
      • scottalanmillerS
        scottalanmiller @coliver
        last edited by

        @coliver said in All Yealink Phones Down at One Site:

        Did fail2ban block that entire subnet? That wouldn't explain why a single polycom device was working correctly though.

        No, that's the IDS and we turned it off to test.

        1 Reply Last reply Reply Quote 0
        • scottalanmillerS
          scottalanmiller @AdamF
          last edited by

          @fuznutz04 said in All Yealink Phones Down at One Site:

          @momurda said in All Yealink Phones Down at One Site:

          sometimes here. Come in and all the phones will not be working, but everythign else is. Usually this is because the firewall/IPS/IDS has been triggered due to lots of SIP attemtps at once, like if many of the phones want to try an reregister at once. I just go and look for blocked sites in the firewall/utm/whatever, and usually it is our voip/sip provider's ip listed there. Remove i

          @scottalanmiller Have you rebooted the PBX yet?

          Yes, we did early on. No change.

          1 Reply Last reply Reply Quote 0
          • scottalanmillerS
            scottalanmiller @i3
            last edited by

            @i3 said in All Yealink Phones Down at One Site:

            Factory reset a phone and try manually programming? How about a packet capture at the site firewall, do you see attempts from that IP phone to where? I am assuming that the PBX is hosted elsewhere.

            This is basically where we went. We did this series of events and it appears to be fixed...

            1. Rebooted the firewall.
            2. Removed SIP-ALG, but this appears to have had no effect.
            3. Updated the firmware on each phone.
            4. Went to static DNS rather than DHCP set.
            5. DNS to CloudFlare instead of AD.
            6. Ensures STUN was on and set correctly.
            7. Added the PBX as a Proxy, manually enabled STUN for the proxy.

            After those seven steps, all phones are now registered. Couldn't find any step there that individually made a difference.

            AdamFA dbeatoD 2 Replies Last reply Reply Quote 2
            • AdamFA
              AdamF @scottalanmiller
              last edited by

              @scottalanmiller said in All Yealink Phones Down at One Site:

              @i3 said in All Yealink Phones Down at One Site:

              Factory reset a phone and try manually programming? How about a packet capture at the site firewall, do you see attempts from that IP phone to where? I am assuming that the PBX is hosted elsewhere.

              This is basically where we went. We did this series of events and it appears to be fixed...

              1. Rebooted the firewall.
              2. Removed SIP-ALG, but this appears to have had no effect.
              3. Updated the firmware on each phone.
              4. Went to static DNS rather than DHCP set.
              5. DNS to CloudFlare instead of AD.
              6. Ensures STUN was on and set correctly.
              7. Added the PBX as a Proxy, manually enabled STUN for the proxy.

              After those seven steps, all phones are now registered. Couldn't find any step there that individually made a difference.

              Ah yes, I love it when the solution is unknown. Been there plenty of times.

              1 Reply Last reply Reply Quote 0
              • scottalanmillerS
                scottalanmiller
                last edited by

                At least the fix was repeatable.

                JaredBuschJ 1 Reply Last reply Reply Quote 0
                • JaredBuschJ
                  JaredBusch @scottalanmiller
                  last edited by

                  @scottalanmiller said in All Yealink Phones Down at One Site:

                  At least the fix was repeatable.

                  I think that is silly.

                  Was a packet capture not possible?

                  1 Reply Last reply Reply Quote 0
                  • dbeatoD
                    dbeato @scottalanmiller
                    last edited by

                    @scottalanmiller said in All Yealink Phones Down at One Site:

                    @i3 said in All Yealink Phones Down at One Site:

                    Factory reset a phone and try manually programming? How about a packet capture at the site firewall, do you see attempts from that IP phone to where? I am assuming that the PBX is hosted elsewhere.

                    This is basically where we went. We did this series of events and it appears to be fixed...

                    1. Rebooted the firewall.
                    2. Removed SIP-ALG, but this appears to have had no effect.
                    3. Updated the firmware on each phone.
                    4. Went to static DNS rather than DHCP set.
                    5. DNS to CloudFlare instead of AD.
                    6. Ensures STUN was on and set correctly.
                    7. Added the PBX as a Proxy, manually enabled STUN for the proxy.

                    After those seven steps, all phones are now registered. Couldn't find any step there that individually made a difference.

                    To me looks like the DNS was caching something for the devices to get to. That's my theory.

                    @scottalanmiller said in All Yealink Phones Down at One Site:

                    1. Updated the firmware on each phone.
                    2. Went to static DNS rather than DHCP set.
                    3. DNS to CloudFlare instead of AD.

                    After those seven steps, all phones are now registered. Couldn't find any step there that individually made a difference.

                    scottalanmillerS 1 Reply Last reply Reply Quote 0
                    • scottalanmillerS
                      scottalanmiller @dbeato
                      last edited by

                      @dbeato said in All Yealink Phones Down at One Site:

                      @scottalanmiller said in All Yealink Phones Down at One Site:

                      @i3 said in All Yealink Phones Down at One Site:

                      Factory reset a phone and try manually programming? How about a packet capture at the site firewall, do you see attempts from that IP phone to where? I am assuming that the PBX is hosted elsewhere.

                      This is basically where we went. We did this series of events and it appears to be fixed...

                      1. Rebooted the firewall.
                      2. Removed SIP-ALG, but this appears to have had no effect.
                      3. Updated the firmware on each phone.
                      4. Went to static DNS rather than DHCP set.
                      5. DNS to CloudFlare instead of AD.
                      6. Ensures STUN was on and set correctly.
                      7. Added the PBX as a Proxy, manually enabled STUN for the proxy.

                      After those seven steps, all phones are now registered. Couldn't find any step there that individually made a difference.

                      To me looks like the DNS was caching something for the devices to get to. That's my theory.

                      If so, why did changing the DNS alone not fix it?

                      dbeatoD 1 Reply Last reply Reply Quote 0
                      • dbeatoD
                        dbeato @scottalanmiller
                        last edited by

                        @scottalanmiller said in All Yealink Phones Down at One Site:

                        @dbeato said in All Yealink Phones Down at One Site:

                        @scottalanmiller said in All Yealink Phones Down at One Site:

                        @i3 said in All Yealink Phones Down at One Site:

                        Factory reset a phone and try manually programming? How about a packet capture at the site firewall, do you see attempts from that IP phone to where? I am assuming that the PBX is hosted elsewhere.

                        This is basically where we went. We did this series of events and it appears to be fixed...

                        1. Rebooted the firewall.
                        2. Removed SIP-ALG, but this appears to have had no effect.
                        3. Updated the firmware on each phone.
                        4. Went to static DNS rather than DHCP set.
                        5. DNS to CloudFlare instead of AD.
                        6. Ensures STUN was on and set correctly.
                        7. Added the PBX as a Proxy, manually enabled STUN for the proxy.

                        After those seven steps, all phones are now registered. Couldn't find any step there that individually made a difference.

                        To me looks like the DNS was caching something for the devices to get to. That's my theory.

                        If so, why did changing the DNS alone not fix it?

                        Not sure, I am just going by what you said. Basically very strange.

                        1 Reply Last reply Reply Quote 0
                        • 1
                        • 2
                        • 2 / 2
                        • First post
                          Last post