[asterisk-users] MWI problem with Siemens Gigaset S675 IP

[Steve Langstaff]

The "481 Call Leg/Transaction Does Not Exist" response to the
NOTIFY makes me think that you might need to configure the
phone to SUBSCRIBE to MWI - do you see any SUBSCRIBE messages
from the phone when it is booted?


> -----Original Message-----
> From: asterisk-users-bounces at lists.digium.com 
> [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of 
> Jaap Winius
> Sent: 13 February 2008 18:46
> 
> Hi list,
> 
> Before purchasing a number of Siemens DECT SIP phones, the Gigaset
> S675 IP, I read that the problems with MWI had been fixed 
> with the latest firmware version (see 
> http://www.voip-info.org/wiki/view/Siemens+Gigaset+S675IP). 
> Now I'm not so sure that's the case.
> 
> After setting up a network mailbox for one of these phones, 
> as well as an Asterisk voicemail account (ext. 1000) in 
> voicemail.conf's default context, I added the following line 
> to my phone's context in sip.conf:
> 
>    mailbox=1000
> 
> However, soon after executing a 'sip reload' on the console, 
> the following error message will appear every three minutes:
> 
>    [Feb 13 19:18:22] WARNING[14171]: chan_sip.c:12621 handle_response:
>     Remote host can't match request NOTIFY to call
>    '1742fb0c598dc6ec444a5ea64a2103ae at 192.168.10.10'. Giving up.
> 
> The IP address belongs to my server. At the same time, I used 
> tcpdump to see what else might be going on. I found the following:
> 
>    19:18:22.540113 IP bitis.umrk.to.sip > 
> gigaset.umrk.to.sip: SIP, length: 545
>    E..=.... at ......
>    .........)..NOTIFY sip:1000 at 192.168.10.5:5060 SIP/2.0
>    Via: SIP/2.0
>    19:18:22.571452 IP gigaset.umrk.to.sip > 
> bitis.umrk.to.sip: SIP, length: 308
>    E..P.......f.......
>    .....<a_SIP/2.0 481 Call Leg/Transaction Does Not Exist
>    Via:
> 
> The latest comment on the voip-info.org page above outlines 
> the same problem. Can anyone here confirm that this is indeed 
> a Siemens problem, or might it be an Asterisk problem after all?
> 
> I'm running Asterisk v1.4.14 on a Debian etch server.