<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<div class="moz-cite-prefix">On 31-07-14 12:13, Joshua Colp wrote:<br>
</div>
<blockquote cite="mid:53DA16E7.5040208@digium.com" type="cite">Jonas
Kellens wrote:
<br>
<br>
<blockquote type="cite">I notice that Asterisk always sends
Subscription-State: active, even
<br>
when the SIP-peer is offline (IP-phone cut from power) :
<br>
<br>
<br>
/[Jul 31 11:56:58] NOTICE[32273]: chan_sip.c:26194
sip_poke_noanswer:
<br>
Peer 'testacc77000' is now UNREACHABLE! Last qualify: 49//
<br>
//[Jul 31 11:56:58] Really destroying SIP dialog
<br>
'78b0d1701d3694b1494a0c4b55344d57@ip-sip-server:5060' Method:
OPTIONS//
<br>
//[Jul 31 11:56:58] set_destination: Parsing
<br>
<a class="moz-txt-link-rfc2396E" href="mailto:sip:testacc77003@192.168.1.109:1024"><sip:testacc77003@192.168.1.109:1024></a> for address/port to
send to//
<br>
//[Jul 31 11:56:58] set_destination: set destination to
192.168.1.109:1024//
<br>
//[Jul 31 11:56:58] Reliably Transmitting (NAT) to
my-public-ip:1024://
<br>
//NOTIFY <a class="moz-txt-link-abbreviated" href="mailto:sip:testacc77003@192.168.1.109:1024">sip:testacc77003@192.168.1.109:1024</a> SIP/2.0//
<br>
//Via: SIP/2.0/UDP
ip-sip-server:5060;branch=z9hG4bK3afa3dd6;rport//
<br>
//Max-Forwards: 70//
<br>
//From: <sip:10@ip-sip-server;user=phone>;tag=as00df4bee//
<br>
//To: <sip:testacc77003@ip-sip-server>;tag=9wdraz254n//
<br>
//Contact: <sip:10@ip-sip-server:5060>//
<br>
//Call-ID: 3c267066aeb1-bv3r703hb93x//
<br>
//CSeq: 109 NOTIFY//
<br>
//User-Agent: myasterisk//
<br>
//Subscription-State: active//
<br>
//Event: dialog//
<br>
//Content-Type: application/dialog-info+xml//
<br>
//Content-Length: 202//
<br>
//
<br>
//<?xml version="1.0"?>//
<br>
//<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info"
version="7"
<br>
state="full" entity="sip:10@ip-sip-server">//
<br>
//<dialog id="10">//
<br>
//<state>terminated</state>//
<br>
//</dialog>//
<br>
//</dialog-info>/
<br>
<br>
<br>
It seems to me that this information is not correct. Is this
some
<br>
setting I need to tweak ?
<br>
</blockquote>
<br>
It is correct. The subscription setup by the subscribing device
remains active. The body itself (the XML) conveys the information
about the device that has been subscribed to. In the case of the
above the "<state>terminated</state>" means that it is
unavailable. There's a few different body types that
implementations use.<font face="Helvetica, Arial, sans-serif"><br>
</font></blockquote>
<font face="Helvetica, Arial, sans-serif"><br>
Hello,<br>
<br>
I read on Yealink support that Yealink IP-phones expect
"Subscription-State:terminated" for there
Presence/BLF-functionality.<br>
<br>
So how can I get "Subscription-State:terminated" on Asterisk ?<br>
<br>
<br>
Kind regards,<br>
<br>
Jonas.</font><br>
<br>
</body>
</html>