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...
- Rebooted the firewall.
- Removed SIP-ALG, but this appears to have had no effect.
- Updated the firmware on each phone.
- Went to static DNS rather than DHCP set.
- DNS to CloudFlare instead of AD.
- Ensures STUN was on and set correctly.
- 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:
- Updated the firmware on each phone.
- Went to static DNS rather than DHCP set.
- 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.
-
@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...
- Rebooted the firewall.
- Removed SIP-ALG, but this appears to have had no effect.
- Updated the firmware on each phone.
- Went to static DNS rather than DHCP set.
- DNS to CloudFlare instead of AD.
- Ensures STUN was on and set correctly.
- 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?
-
@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...
- Rebooted the firewall.
- Removed SIP-ALG, but this appears to have had no effect.
- Updated the firmware on each phone.
- Went to static DNS rather than DHCP set.
- DNS to CloudFlare instead of AD.
- Ensures STUN was on and set correctly.
- 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.
