Yealink Forums

Full Version: BLF\CallPark Subscriptions Fail after several days.
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Hello,

We are seeing some consistent behavior in both the T2x series and T-4x series of phones(T-3x possibly, but we don't have many in production), where working BLF\CallPark subscriptions to the asterisk server stop working after a long(few days) period of time.

From packet captures, I can see that the phones simply stop sending the SUBSCRIBE requests to the server. Sending a force reboot notify restarts the phone, and SUBSCRIBE requests resume normally.

During the time when the BLF\CallPark SUBSCRIBE messages are not being sent, I am still seeing SUBSCRIBE requests for MWI, so not all SUBSCRIBE functionality is broken.

I am unable to see anything obvious in the phone's logs that indicate why they stop sending the SUBSCRIBE, and the last thing on our server is a successful NOTIFY send to the phone for a state update.

So, I was wondering if anyone else was experiencing this, or if anyone knows of behavior in the phone firmware that would blacklist a BLF SUBSCRIBE from being used after a certain number of failures(for whatever reason). We do require authentication for BLF, so every SUBSCRIBE is initially rejected with a challenge to provide password authentication. This process normally works fine, but I'm wondering if there is an internal counter for 401 messages....

--Bryan
Please send your trace to your distributor or support@yealink.com. They can help you to deal with issues.
(05-13-2014 03:28 AM)bnelson Wrote: [ -> ]Hello,

We are seeing some consistent behavior in both the T2x series and T-4x series of phones(T-3x possibly, but we don't have many in production), where working BLF\CallPark subscriptions to the asterisk server stop working after a long(few days) period of time.

From packet captures, I can see that the phones simply stop sending the SUBSCRIBE requests to the server. Sending a force reboot notify restarts the phone, and SUBSCRIBE requests resume normally.

During the time when the BLF\CallPark SUBSCRIBE messages are not being sent, I am still seeing SUBSCRIBE requests for MWI, so not all SUBSCRIBE functionality is broken.

I am unable to see anything obvious in the phone's logs that indicate why they stop sending the SUBSCRIBE, and the last thing on our server is a successful NOTIFY send to the phone for a state update.

So, I was wondering if anyone else was experiencing this, or if anyone knows of behavior in the phone firmware that would blacklist a BLF SUBSCRIBE from being used after a certain number of failures(for whatever reason). We do require authentication for BLF, so every SUBSCRIBE is initially rejected with a challenge to provide password authentication. This process normally works fine, but I'm wondering if there is an internal counter for 401 messages....

--Bryan

All I can say is that with my T48 (35.72.0.10) and Asterisk (11.something) I do not see this issue.

What is Subscribe Period(seconds) set to in Account->Advanced? Does asterisk show the subscriptions in 'sip show subscriptions' ?

C.
Reference URL's