<br><br><div class="gmail_quote">2008/10/28 Robert Boardman <span dir="ltr"><<a href="mailto:robb@boardman.me.uk">robb@boardman.me.uk</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;">
Olivier wrote:<br>
><br>
><br>
> 2008/10/3 Olivier <<a href="mailto:oza-4h07@myamail.com">oza-4h07@myamail.com</a> <mailto:<a href="mailto:oza-4h07@myamail.com">oza-4h07@myamail.com</a>>><br>
><br>
> 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><br>
> it is mentioned MWI is now working.<br>
><br>
> In my testings with lastest 02123 firmware, MWI is blinking when<br>
> 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"<br>
> replies to NOTIFY announcing new messages.<br>
> With previous firmware, I had "415 Unsupported Media" if my memory<br>
> is correct.<br>
><br>
> Has anyone been any further ?<br>
> Regards<br>
><br>
><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<br>
> Leg/Transaction Does Not Exist"<br>
><br>
> When base station is restarted, it will SUBSCRIBE its endpoints to<br>
> 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<br>
> this NOTIFY message<br>
><br>
> From then on, further NOTIFY messages are replied with "481 Call<br>
> Leg/Transaction Does Not Exist" and obviously not taken into account<br>
> 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@192.168.100.197:5060" target="_blank">sip:7531@192.168.100.197:5060</a><br>
> <<a href="http://sip:7531@192.168.100.197:5060" target="_blank">http://sip:7531@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@asterisk>;tag=as4ea953db<br>
> To: <<a href="http://sip:sip:7531@192.168.100.197:5060" target="_blank">sip:sip:7531@192.168.100.197:5060</a><br>
> <<a href="http://sip:sip:7531@192.168.100.197:5060" target="_blank">http://sip:sip:7531@192.168.100.197:5060</a>>>;tag=2580238520<br>
> Contact: <<a href="mailto:sip%3Aasterisk@192.168.100.254">sip:asterisk@192.168.100.254</a><br>
> <mailto:<a href="mailto:sip%253Aasterisk@192.168.100.254">sip%3Aasterisk@192.168.100.254</a>>><br>
> Call-ID: 3026028457@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@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@192.168.100.197:5060" target="_blank">sip:7531@192.168.100.197:5060</a><br>
> <<a href="http://sip:7531@192.168.100.197:5060" target="_blank">http://sip:7531@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@192.168.100.254">sip:asterisk@192.168.100.254</a><br>
> <mailto:<a href="mailto:sip%253Aasterisk@192.168.100.254">sip%3Aasterisk@192.168.100.254</a>>>;tag=as5e574490<br>
> To: <<a href="http://sip:7531@192.168.100.197:5060" target="_blank">sip:7531@192.168.100.197:5060</a> <<a href="http://sip:7531@192.168.100.197:5060" target="_blank">http://sip:7531@192.168.100.197:5060</a>>><br>
> Contact: <<a href="mailto:sip%3Aasterisk@192.168.100.254">sip:asterisk@192.168.100.254</a><br>
> <mailto:<a href="mailto:sip%253Aasterisk@192.168.100.254">sip%3Aasterisk@192.168.100.254</a>>><br>
> Call-ID: <a href="mailto:4b53acd64813650c3077f2372dd146d7@192.168.100.254">4b53acd64813650c3077f2372dd146d7@192.168.100.254</a><br>
> <mailto:<a href="mailto:4b53acd64813650c3077f2372dd146d7@192.168.100.254">4b53acd64813650c3077f2372dd146d7@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@192.168.100.254">sip:asterisk@192.168.100.254</a><br>
> <mailto:<a href="mailto:sip%253Aasterisk@192.168.100.254">sip%3Aasterisk@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<br>
> patching Asterisk source (I'm unable to do that) ?<br>
> Your thoughts ?<br>
><br>
> Regards<br>
><br>
> ------------------------------------------------------------------------<br>
><br>
> _______________________________________________<br>
> -- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
><br>
> AstriCon 2008 - September 22 - 25 Phoenix, Arizona<br>
> Register Now: <a href="http://www.astricon.net" target="_blank">http://www.astricon.net</a><br>
><br>
> asterisk-users mailing list<br>
> To UNSUBSCRIBE or update options visit:<br>
> <a href="http://lists.digium.com/mailman/listinfo/asterisk-users" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br>
Just worked out a good way of getting transfer working<br>
<br>
Using features .conf<br>
<br>
[featuremap]<br>
blindxfer => ## ; Blind transfer<br>
;disconnect => *0 ; Disconnect<br>
;automon => *1 ; One Touch Record<br>
atxfer => A ; Attended transfer<br>
<br>
DTMF A-D are valid DTMF signals but are not usually shown on standard<br>
phones<br>
<br>
so set atxfer to 'A' and DTMF relay Application signal on the Gigaset to<br>
'A' (without quotes)<br>
<br>
and transfer works as expected<br>
<br>
Robb<br>
<br></blockquote><div><br>Hi,<br><br>What about MWI and Subscription-State: active ?<br>I can see that Asterisk sends NOTIFY messages with and without this "Subscription-State: active" statement in header.<br>
I can see that NOTIFY messages without "Subscription-State: active" are rejected by Gigaset base station.<br><br>Is it possible to either configure :<br>1. Gigaset to accept NOTIFY messages without "Subscription-State: active"<br>
2. Asterisk to send NOTIFY messages with "Subscription-State: active"<br><br>Cheers<br></div></div>