*Resolved* BLF Failback to Primary Server - DNS-SRV

[Bryan Nelson]

---Original Message bounced back form support@yealink.com-----

Hello,

We are having an issue with BLF status subscriptions when combined with the DNS-SRV functionality. The BLF keys will work fine until the phone utilizes the secondary server listed in the DNS-SRV record. After registering to the secondary server, all 200 ok responses to notify events are sent to the secondary server, even if the phone has reverted back to its primary registration.

Without the 200 ok responses, our server will queue up further notify events to avoid a "notify storm" on the phones end(the server assumes the phone is lagging behind the notify events.)

Is there any way to lock the BLF subscription to a specific server address, rather than use the line registration SRV record? Polycom phones had a similar issue, and we were able to specify an a-record lookup for the BLF subscription separately from the line registration server address.

I have attached the pcap\config\logs from the phone -- A T-26. Let me know if you need anything else from me to help identify this problem.