<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
On 31-07-14 14:28, Joshua Colp wrote:<br>
<blockquote cite="mid:53DA3659.1080202@digium.com" type="cite">Jonas
Kellens wrote:
<br>
<blockquote type="cite">
<br>
Hello,
<br>
<br>
I read on Yealink support that Yealink IP-phones expect
<br>
"Subscription-State:terminated" for there
Presence/BLF-functionality.
<br>
<br>
So how can I get "Subscription-State:terminated" on Asterisk ?
<br>
</blockquote>
<br>
That would be a bit strange as the subscription would then be
terminated, no more NOTIFY messages would go to it which would
defeat the purpose of subscribing to something. The only way to
achieve that would be to have the phone unsubscribe or to change
the code to force it to terminate the subscription under certain
circumstances. This would require knowing the exact specifications
and details of what they expect and when. Is there currently a
problem you are facing with subscription support?
<br>
<br>
</blockquote>
<font face="Helvetica, Arial, sans-serif"><br>
Hello,<br>
<br>
this "Subscription-State:terminated" is expected when the IP-phone
goes offline (Unregister or cut off from power).<br>
<br>
At that moment indeed the IP-phone no longer sends NOTIFY
messages. Also, Asterisk knows very well the SIP peer becomes
unreachable (see my first post). But still Asterisk replies
"Subscription-State: active" to the IP-phones that request the
state of the offline SIP peer.<br>
<br>
<br>
Yealink expects "Subscription-State:terminated" so the Yealink
IP-phone can put out the BLF light (in stead of staying in a green
mode, which indicates that the SIP peer is still online but not in
a call).<br>
<br>
So I can follow the Yealink logic. Can you ?<br>
<br>
<br>
<br>
Kind regards,<br>
<br>
Jonas.</font><br>
</body>
</html>