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