Yealink Forums

(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 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

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

So, this is a few years later... Is this still an issue? Did anyone ever figure out a workaround?

I have several phones that are remote extensions that may or may not be plugged in at any time. When they are plugged and working and accepting calls, the BLF is green so that everyone knows. But when they are not even plugged in or connected anywhere and therefore "unavailable", the BLF is still green and everyone THINKS that they are available.

There has to be a solution for this, right?