Re: [asterisk-users] MWI problem with Siemens Gigaset S675 IP
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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 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 '[EMAIL PROTECTED]'. 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 [EMAIL PROTECTED] .)..NOTIFY sip:[EMAIL PROTECTED]: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. ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] MWI problem with Siemens Gigaset S675 IP
Quoting Steve Langstaff [EMAIL PROTECTED]: 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? Yeah, sure. And there are some error messages mixed in too: == 14:01:23.425955 IP gigaset.umrk.to.sip bitis.umrk.to.sip: SIP, length: 473 ... SUBSCRIBE sip:[EMAIL PROTECTED] SIP/2.0 Via: SIP/2.0/UDP 1 14:01:23.426075 IP bitis.umrk.to.sip gigaset.umrk.to.sip: SIP, length: 509 [EMAIL PROTECTED] ...vSIP/2.0 401 Unauthorized Via: SIP/2.0/UDP 192.168.10.5 14:01:23.480238 IP gigaset.umrk.to.sip bitis.umrk.to.sip: SIP, length: 634 E..k... ..F.SUBSCRIBE sip:[EMAIL PROTECTED] SIP/2.0 Via: SIP/2.0/UDP 1 14:01:23.480375 IP bitis.umrk.to.sip gigaset.umrk.to.sip: SIP, length: 432 [EMAIL PROTECTED] ...)SIP/2.0 404 Not Found Via: SIP/2.0/UDP 192.168.10.5:50 14:01:23.918830 arp who-has gigaset.umrk.to tell bitis.umrk.to ../.E .. 14:01:23.921726 arp reply gigaset.umrk.to is-at 00:01:e3:77:f8:67 (oui Unknown) ...w.g../.E .. 14:01:24.539636 IP gigaset.umrk.to.sip bitis.umrk.to.sip: SIP, length: 476 E.. ..2gSUBSCRIBE sip:[EMAIL PROTECTED] SIP/2.0 Via: SIP/2.0/UDP 1 14:01:24.539816 IP bitis.umrk.to.sip gigaset.umrk.to.sip: SIP, length: 512 [EMAIL PROTECTED] ...ySIP/2.0 401 Unauthorized Via: SIP/2.0/UDP 192.168.10.5 14:01:24.594442 IP gigaset.umrk.to.sip bitis.umrk.to.sip: SIP, length: 634 E..i... SUBSCRIBE sip:[EMAIL PROTECTED] SIP/2.0 Via: SIP/2.0/UDP 1 14:01:24.594557 IP bitis.umrk.to.sip gigaset.umrk.to.sip: SIP, length: 432 E...- [EMAIL PROTECTED] ...)SIP/2.0 404 Not Found Via: SIP/2.0/UDP 192.168.10.5:50 == Before this was a series of REGISTER messages, and afterwards a series of OPTIONS messages. However, no errors there. Also, this is without having set 'mailbox=1000' or '[EMAIL PROTECTED]' in /etc/asterisk/sip.conf. And, now that I look at it again, the network mailbox settings for the Siemens phone won't have anything to do with these errors either, since it simply makes it possible to associate a button on each handset with an extension used to access a voicemail account. Thanks, Jaap ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] MWI problem with Siemens Gigaset S675 IP
Try adding [EMAIL PROTECTED] (or what ever your voicemail contexxt is) I've had to add the voicemail context to get MWI to work correctly in the past. - Original Message - From: Jaap Winius [EMAIL PROTECTED] To: asterisk-users@lists.digium.com Sent: Wednesday, February 13, 2008 12:45 PM Subject: [asterisk-users] MWI problem with Siemens Gigaset S675 IP 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 '[EMAIL PROTECTED]'. 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 [EMAIL PROTECTED] .)..NOTIFY sip:[EMAIL PROTECTED]: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. Thanks, Jaap ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] MWI problem with Siemens Gigaset S675 IP
Quoting Henry Devito [EMAIL PROTECTED]: Try adding [EMAIL PROTECTED] (or what ever your voicemail contexxt is) I've had to add the voicemail context to get MWI to work correctly in the past. According to the documentation, you shouldn't have to add @context if the context is 'default'. But, I went ahead and tried it out anyway. I even tried using some other context names, but it makes no difference: the error remains the same. Thanks anyway, Jaap ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
