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