When a message is received on an extension that a snom m9 phone is registered, a vm soft button appears on the screen. When I press this button, the phone dials extension rather than 101. After doing further research, snom seems to claim that the number behind vm button is extracted from notify message. If it is not supplied, it uses the mailbox extension specified in phone's configuration. Is there a setting on sipx or on the phone that needs changing? Below, is the trace...
SIP/2.0 200 Ok Via: SIP/2.0/UDP 192.168.35.26;branch=z9hG4bK-XX-2510IB6v7d959ax4`8R149vOdQ Via: SIP/2.0/UDP 192.168.35.26:5110;branch=z9hG4bK-XX-086b33lTBVxYQRoegQo8Tcb6mw From: "User" <sip:2...@sipdomain.com>;tag=a2xbyg To: "User" <sip:2...@sipdomain.com>;tag=uvqe3g Call-ID: aml19zox@snom CSeq: 3 NOTIFY Content-Length: 0 2012/02/08 11:16:07 [SIP-Other:5]: SIP Rx udp:192.168.35.26:5060: NOTIFY sip:201@192.168.35.248:2149;transport=udp;x-sipX-nonat SIP/2.0 Content-Type: application/simple-message-summary Content-Length: 88 Event: message-summary Subscription-State: active;expires=617 From: "User" <sip:2...@sipdomain.com>;tag=a2xbyg To: "User" <sip:2...@sipdomain.com>;tag=uvqe3g Call-Id: aml19zox@snom Cseq: 3 NOTIFY Contact: <sip:2...@sipdomain.com;x-sipX-nonat> User-Agent: sipXecs/4.4.0 sipXecs/publisher (Linux) Date: Wed, 08 Feb 2012 16:16:06 GMT Max-Forwards: 19 Accept-Language: en Supported: sip-cc-01, timer Via: SIP/2.0/UDP 192.168.35.26;branch=z9hG4bK-XX-2510IB6v7d959ax4`8R149vOdQ Via: SIP/2.0/UDP 192.168.35.26:5110;branch=z9hG4bK-XX-086b33lTBVxYQRoegQo8Tcb6mw Messages-Waiting: yes Message-Account: sip:2...@sipdomain.com Voice-Message: 1/0 (0/0) 2012/02/08 11:16:07 [SIP-Other:5]: SIP Tx udp:192.168.35.26:5060: SIP/2.0 200 Ok Via: SIP/2.0/UDP 192.168.35.26;branch=z9hG4bK-XX-250esBAVY`CstuaT30NhT2jPfw Via: SIP/2.0/UDP 192.168.35.26:5110;branch=z9hG4bK-XX-0868bekaNjNZY96HkYBSIhLWQA From: "User" <sip:2...@sipdomain.com>;tag=NG8hfr To: "User" <sip:2...@sipdomain.com>;tag=vzql02 Call-ID: 3w8ev33r@snom CSeq: 3 NOTIFY Content-Length: 0 2012/02/08 11:16:07 [SIP-Other:5]: SIP Rx udp:192.168.35.26:5060: NOTIFY sip:201@192.168.35.248:2149;transport=udp;x-sipX-nonat SIP/2.0 Content-Type: application/simple-message-summary Content-Length: 88 Event: message-summary Subscription-State: active;expires=1504 From: "User" <sip:2...@sipdomain.com>;tag=NG8hfr To: "User" <sip:2...@sipdomain.com>;tag=vzql02 Call-Id: 3w8ev33r@snom Cseq: 3 NOTIFY Contact: <sip:2...@sipdomain.com;x-sipX-nonat> User-Agent: sipXecs/4.4.0 sipXecs/publisher (Linux) Date: Wed, 08 Feb 2012 16:16:06 GMT Max-Forwards: 19 Accept-Language: en Supported: sip-cc-01, timer Via: SIP/2.0/UDP 192.168.35.26;branch=z9hG4bK-XX-250esBAVY`CstuaT30NhT2jPfw Via: SIP/2.0/UDP 192.168.35.26:5110;branch=z9hG4bK-XX-0868bekaNjNZY96HkYBSIhLWQA Messages-Waiting: yes Message-Account: sip:2...@sipdomain.com Voice-Message: 1/0 (0/0) Thanks in advance _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
