I have been giving the Server Redundancy on Yealink IP Phones_V82_21.pdf a good read to try and understand better how the phones handle this. right now by default my Yealink endpoints register to both primary and secondary PBX's which is the default config; however I am trying to better understand how it detects an issue and fails over.
for testing I am blocking my primary PBX IP (TCP&UDP) on my firewall to see what the phone will do, the answer is nothing, it doesn't switch over to the secondary, all that happens is the audio no longer works on an echo test, and in fact the echo test call shows on the Active calls on the primary pbx which I dont understand. If I reboot the phone it will come back and register right away to the secondary pbx and route calls there, and if I remove the firewall rule, pretty quickly it will revert back to the primary.
I am a bit stumped as to how it can detect the primary failing and flip over, because I cant seem to get it to happen with a firewall rule, even trying to place calls while its blocked. any ideas ?
UPDATE: I guess a part of it was my firewall; I tried a different approach, blocking it at the server end, and the phone switched over pretty quickly to the failover pbx, then back once I removed the block
I guess a better question is, is anyone doing any other configuration of the yealink handsets with regards to this, the document is pretty extensive with lots of options to set
for testing I am blocking my primary PBX IP (TCP&UDP) on my firewall to see what the phone will do, the answer is nothing, it doesn't switch over to the secondary, all that happens is the audio no longer works on an echo test, and in fact the echo test call shows on the Active calls on the primary pbx which I dont understand. If I reboot the phone it will come back and register right away to the secondary pbx and route calls there, and if I remove the firewall rule, pretty quickly it will revert back to the primary.
I am a bit stumped as to how it can detect the primary failing and flip over, because I cant seem to get it to happen with a firewall rule, even trying to place calls while its blocked. any ideas ?
UPDATE: I guess a part of it was my firewall; I tried a different approach, blocking it at the server end, and the phone switched over pretty quickly to the failover pbx, then back once I removed the block
I guess a better question is, is anyone doing any other configuration of the yealink handsets with regards to this, the document is pretty extensive with lots of options to set
Last edited:
