No subject

Thu Jul 12 09:23:04 CDT 2007

Leg/Transaction Does Not Exist" and obviously not taken into account as
endpoint GUI remains unchanged.

Looking deeper into this here are :

NOTIFY message accepted by S450IP

NOTIFY sip:7531 at 192.168.100.197:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.100.254:5060;branch=z9hG4bK06adc48b;rport
From: "asterisk" <sip:asterisk at asterisk>;tag=as4ea953db
To: <sip:sip:7531 at 192.168.100.197:5060>;tag=2580238520
Contact: <sip:asterisk at 192.168.100.254 <sip%3Aasterisk at 192.168.100.254>>
Call-ID: 3026028457 at 192_168_100_197
CSeq: 102 NOTIFY
User-Agent: Asterisk PBX
Max-Forwards: 70
Event: message-summary
Content-Type: application/simple-message-summary
Subscription-State: active
Content-Length: 89

Messages-Waiting: yes
Message-Account: sip:asterisk at asterisk
Voice-Message: 2/0 (0/0)

NOTIFY message rejected by S450IP (rejected means 481 reply)

NOTIFY sip:7531 at 192.168.100.197:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.100.254:5060;branch=z9hG4bK3d83e7f6;rport
From: "asterisk" <sip:asterisk at 192.168.100.254<sip%3Aasterisk at 192.168.100.254>
>;tag=as5e574490
To: <sip:7531 at 192.168.100.197:5060>
Contact: <sip:asterisk at 192.168.100.254 <sip%3Aasterisk at 192.168.100.254>>
Call-ID: 4b53acd64813650c3077f2372dd146d7 at 192.168.100.254
CSeq: 102 NOTIFY
User-Agent: Asterisk PBX
Max-Forwards: 70
Event: message-summary
Content-Type: application/simple-message-summary
Content-Length: 96

Messages-Waiting: yes
Message-Account: sip:asterisk at 192.168.100.254<sip%3Aasterisk at 192.168.100.254>
Voice-Message: 3/0 (0/0)

The only difference I see between both is that new NOTIFY don't include :
Subscription-State: active

Do you see something else ?
Is it possible to easily add this Subscription-State field without patching
Asterisk source (I'm unable to do that) ?
Your thoughts ?

Regards

------=_Part_26817_5548286.1223283029736
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div dir="ltr"> <div class="gmail_quote">2008/10/3 Olivier &lt;<a href="mailto:oza-4h07 at myamail.com">oza-4h07 at myamail.com</a>&gt; <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div dir="ltr">Hi, 1. Here <a href="http://www.voip-info.org/wiki/view/Siemens+Gigaset+S450IP" target="_blank">http://www.voip-info.org/wiki/view/Siemens+Gigaset+S450IP</a>&nbsp; it is mentioned MWI is now working. 
In my testings with lastest 02123 firmware, MWI is blinking when missed calls but not when a message in present in voicemail. 
With SIP debug I can see &quot;481 Call Leg/Transaction Does Not Exist&quot; replies to NOTIFY announcing new messages. With previous firmware, I had &quot;415 Unsupported Media&quot; if my memory is correct. Has anyone been any further ? 
Regards </div></blockquote><div> Replying to myself, for an unknown reason, MWI is weirdly working&nbsp; : - Phone icon inconsistently shows awaiting voicemails, - NOTIFY message from Asterisk are still replied with &quot;481 Call Leg/Transaction Does Not Exist&quot; 
 When base station is restarted, it will SUBSCRIBE its endpoints to Voicemail Notifications : - you can see SUBSCRIBE message - you can see NOTIFY answer - you can&#39;t see any &quot;481 Call Leg/Transaction Does Not Exist&quot; reply to this NOTIFY message 
 From then on, further NOTIFY messages are replied with &quot;481 Call Leg/Transaction Does Not Exist&quot; and obviously not taken into account as endpoint GUI remains unchanged. Looking deeper into this here are : 
 NOTIFY message accepted by S450IP NOTIFY <a href="http://sip:7531@192.168.100.197:5060">sip:7531 at 192.168.100.197:5060</a> SIP/2.0 Via: SIP/2.0/UDP 192.168.100.254:5060;branch=z9hG4bK06adc48b;rport From: &quot;asterisk&quot; &lt;sip:asterisk at asterisk&gt;;tag=as4ea953db 
To: &lt;<a href="http://sip:sip:7531@192.168.100.197:5060">sip:sip:7531 at 192.168.100.197:5060</a>&gt;;tag=2580238520 Contact: &lt;<a href="mailto:sip%3Aasterisk at 192.168.100.254">sip:asterisk at 192.168.100.254</a>&gt; Call-ID: 3026028457 at 192_168_100_197 
CSeq: 102 NOTIFY User-Agent: Asterisk PBX Max-Forwards: 70 Event: message-summary Content-Type: application/simple-message-summary Subscription-State: active Content-Length: 89 Messages-Waiting: yes 
Message-Account: sip:asterisk at asterisk Voice-Message: 2/0 (0/0) NOTIFY message rejected by S450IP (rejected means 481 reply) NOTIFY <a href="http://sip:7531@192.168.100.197:5060">sip:7531 at 192.168.100.197:5060</a> SIP/2.0 
Via: SIP/2.0/UDP 192.168.100.254:5060;branch=z9hG4bK3d83e7f6;rport From: &quot;asterisk&quot; &lt;<a href="mailto:sip%3Aasterisk at 192.168.100.254">sip:asterisk at 192.168.100.254</a>&gt;;tag=as5e574490 To: &lt;<a href="http://sip:7531@192.168.100.197:5060">sip:7531 at 192.168.100.197:5060</a>&gt; 
Contact: &lt;<a href="mailto:sip%3Aasterisk at 192.168.100.254">sip:asterisk at 192.168.100.254</a>&gt; Call-ID: <a href="mailto:4b53acd64813650c3077f2372dd146d7 at 192.168.100.254">4b53acd64813650c3077f2372dd146d7 at 192.168.100.254</a> 
CSeq: 102 NOTIFY User-Agent: Asterisk PBX Max-Forwards: 70 Event: message-summary Content-Type: application/simple-message-summary Content-Length: 96 Messages-Waiting: yes Message-Account: <a href="mailto:sip%3Aasterisk at 192.168.100.254">sip:asterisk at 192.168.100.254</a> 
Voice-Message: 3/0 (0/0) The only difference I see between both is that new NOTIFY don&#39;t include : Subscription-State: active 
 Do you see something else ? Is it possible to easily add this Subscription-State field without patching Asterisk source (I&#39;m unable to do that) ? Your thoughts ? Regards </div></div></div>

------=_Part_26817_5548286.1223283029736--