[asterisk-users] MWI with Siemens Gigaset S450IP

[Robert Boardman]

Olivier wrote:
>
>
> 2008/10/3 Olivier <oza-4h07 at myamail.com <mailto:oza-4h07 at myamail.com>>
>
>     Hi,
>
>     1. Here http://www.voip-info.org/wiki/view/Siemens+Gigaset+S450IP 
>     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 "481 Call Leg/Transaction Does Not Exist"
>     replies to NOTIFY announcing new messages.
>     With previous firmware, I had "415 Unsupported Media" if my memory
>     is correct.
>
>     Has anyone been any further ?
>     Regards
>
>
> Replying to myself, for an unknown reason, MWI is weirdly working  :
> - Phone icon inconsistently shows awaiting voicemails,
> - NOTIFY message from Asterisk are still replied with "481 Call 
> Leg/Transaction Does Not Exist"
>
> 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't see any "481 Call Leg/Transaction Does Not Exist" reply to 
> this NOTIFY message
>
> 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.
>
> Looking deeper into this here are :
>
> NOTIFY message accepted by S450IP
>
> NOTIFY sip:7531 at 192.168.100.197:5060 
> <http://sip:7531@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 
> <http://sip:sip:7531@192.168.100.197:5060>>;tag=2580238520
> Contact: <sip:asterisk at 192.168.100.254 
> <mailto: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 
> <http://sip:7531@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 
> <mailto:sip%3Aasterisk at 192.168.100.254>>;tag=as5e574490
> To: <sip:7531 at 192.168.100.197:5060 <http://sip:7531@192.168.100.197:5060>>
> Contact: <sip:asterisk at 192.168.100.254 
> <mailto:sip%3Aasterisk at 192.168.100.254>>
> Call-ID: 4b53acd64813650c3077f2372dd146d7 at 192.168.100.254 
> <mailto: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 
> <mailto: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
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> AstriCon 2008 - September 22 - 25 Phoenix, Arizona
> Register Now: http://www.astricon.net
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users
Just worked out a good way of getting transfer working

Using features .conf

[featuremap]
blindxfer => ##         ; Blind transfer
;disconnect => *0               ; Disconnect
;automon => *1                  ; One Touch Record
atxfer => A                     ; Attended transfer

DTMF A-D are valid DTMF signals but are not usually shown on standard 
phones

so set atxfer to 'A' and DTMF relay Application signal on the Gigaset to 
'A' (without quotes)

and transfer works as expected

Robb