Yealink Forums
BLF: unavailable state shown as idle - Printable Version

+- Yealink Forums (http://forum.yealink.com/forum)
+-- Forum: IP Phone Series (/forumdisplay.php?fid=4)
+--- Forum: T4x Series (/forumdisplay.php?fid=31)
+--- Thread: BLF: unavailable state shown as idle (/showthread.php?tid=894)

Pages: 1 2 3 4

RE: BLF: unavailable state shown as idle - mariovoip - 06-29-2015 09:45 AM

Hi all,

I have a T48G (FW 35.73.0.50) and have noticed that the BLF marks an extension as available even if the "show core hints" in asterisk shows the extension is unavailable.
Everything works great when the extension is on a call or ringing but I do not understand why the BLF is the same for idle and unavailable.
Asterisk is obviously reporting different things as the state changes yet the phone marks the same for unavailable and for idle.

I guess this was a question a few years back... any updates.

Thanks,

Mario

RE: BLF: unavailable state shown as idle - fire555 - 06-30-2015 03:01 PM

Hi,

Yes this is definitely frustrating. Asterisk "show core hints" displays the following
204@ext-local : SIP/204&Custom:DND20 State:Unavailable Watchers 1

However the BLF key shows the status with a green LED. All other phones I have used (Snom, Linksys) would display this with an orange LED.

Hopefully this is being work on?

Thanks

RE: BLF: unavailable state shown as idle - mariovoip - 07-01-2015 05:59 AM

I would hope so, especially since there is supposed to be an upcoming firmware update from what I hear

RE: BLF: unavailable state shown as idle - baobcs - 01-26-2016 07:23 AM

2016 now . I've just bought 10 t48g phones for my small business to make a total of 25phones in our office now and updated with latest firmware Version 35.80.0.80 . If this issue is not going to be fixed soon , I will have to return all 25phones and looking into other brand that can fully support this . Yealink please provide an update for this

Server: FreePBX 13.0.51
Yealink T48G: Version 35.80.0.80
Asterisk State:Unavailable

RE: BLF: unavailable state shown as idle - Dalton - 08-23-2016 11:13 PM

2016 almost done and the same issue is still present Sad.

I am using T4X series phones with Asterisk 13...

RE: BLF: unavailable state shown as idle - TrustT - 09-06-2016 09:52 PM

Same issue here. On Asterisk 13 with T46's.
Even on the newest firmware an UNAVAILABLE extension still shows as idle on the BLFs.

RE: BLF: unavailable state shown as idle - SteveDavies - 09-29-2017 04:04 PM

FYI this is still an issue.

'unavailable' is a valid NOTIFY / BLF state on all other SIP phones that we use, and indicates that a BLF points to a currently disconnected, disabled or otherwise inaccessible device.

The BLF subscription should not be terminated, it should be kept active so that the handset can be sent an update if the handset is made available again.

RE: BLF: unavailable state shown as idle - siny - 10-27-2017 09:50 AM

Asterisk 15.0, Yealink firmware 82, still the same problem.

This looks like "not willing to fix"!

Seems that other phone manufacturers know something more?


PLEASE Yealink, fix this, because that's the only reason I don't recoment your phones to everyone...

RE: BLF: unavailable state shown as idle - SteveDavies - 10-27-2017 11:00 AM

(10-27-2017 09:50 AM)siny Wrote:  Asterisk 15.0, Yealink firmware 82, still the same problem.

This looks like "not willing to fix"!

Seems that other phone manufacturers know something more?


PLEASE Yealink, fix this, because that's the only reason I don't recoment your phones to everyone...

For people who follow this thread in future, I have done a whole bunch or research, and it appears that Yealink are actually doing nothing especially wrong Sad But nor is asterisk.

1) The XML Notify message being sent does not have an obvious value for "cannot call" available to it in the RFC. It can only really indicate call states, and uncallable is the same as not-on-a-call.

2) The "Subscription-State" header is nothing to do with this issue (except as a way to make the button red), it simply indicates that the handset has an active subscription for the BLF line in question. Subscription-State: terminated indicates that the BLF subscription is no longer active so no state will be sent.

3) If someone can demonstrate this working as we all want it to on a different handset type, and grab a trace of the packets sent, I would be VERY interested in the difference. What I think you might find is that they use an alternative XML standard for the NOTIFY, which does not handle call-state properly Sad

RE: BLF: unavailable state shown as idle - siny - 10-27-2017 11:58 AM

(10-27-2017 11:00 AM)SteveDavies Wrote:  
(10-27-2017 09:50 AM)siny Wrote:  Asterisk 15.0, Yealink firmware 82, still the same problem.

This looks like "not willing to fix"!

Seems that other phone manufacturers know something more?


PLEASE Yealink, fix this, because that's the only reason I don't recoment your phones to everyone...

For people who follow this thread in future, I have done a whole bunch or research, and it appears that Yealink are actually doing nothing especially wrong Sad But nor is asterisk.

1) The XML Notify message being sent does not have an obvious value for "cannot call" available to it in the RFC. It can only really indicate call states, and uncallable is the same as not-on-a-call.

2) The "Subscription-State" header is nothing to do with this issue (except as a way to make the button red), it simply indicates that the handset has an active subscription for the BLF line in question. Subscription-State: terminated indicates that the BLF subscription is no longer active so no state will be sent.

3) If someone can demonstrate this working as we all want it to on a different handset type, and grab a trace of the packets sent, I would be VERY interested in the difference. What I think you might find is that they use an alternative XML standard for the NOTIFY, which does not handle call-state properly Sad

Well, I see that Yealink is using "application/dialog-info+xml", while others are using "application/pidf+xml".

What is preventing Yealink to use both, in some kind of AND fashion, like: if "pidf+xml" says ext is online, then report status of "dialog-info+xml", otherwise turn off the LED?
Or let us (users) select which one to use? I would rather have presence working correctly than be able to see if extension is ringing, and if I understand correctly both can display if ext. is in use.

I am waiting for a Linksys and a Grandstream to arrive, then I'll try to compare their capabilities, and dump/analyze some traffic... hopefully during next week