SIP Notify Unsolicited and CUCME Ephone - 481 Does Not Exist

Kris Thompson · ‎07-25-2012

Customer is trying to use an external voicemail system with CUCME 7.1 (IOS 12.4(24)T3).

We cannot get Message Waiting Indicator (MWI) to work based on SIP Notify Unsolicited.

When the unsolicited notify comes in, the IOS router returns "481 Call Leg/Transaction Does Not Exist". Why?

Relevant config includes:

sip-ua

mwi-server dns:sipconnect.somwhere.com expires 3600 port 5060 transport udp unsolicited

registrar dns:sipconnect.somewhere.com expires 3600

sip-server dns:sipconnect.somewhere.com

host-registrar

ephone-dn 15 dual-line

number 2115 no-reg both

mwi sip ! is this only needed for SIP Notify Solicited?

The output of "show sip-ua mwi" is odd. It lists the SIP MWI server 3 times. Once in HEX, twice in decimal dotted. Never does it list the "endpoints" as shown in the documentation.

I have reviewed all possible documentation, and this should work. Am I missing something? Perhaps this is a defect?

Any recommendations would be much appreciated.

--------------SIP Trace--------------------

Jul 24 2012 02:03:20.932 BST: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

NOTIFY sip:441224XX2115@141.0.49.226:5060 SIP/2.0

Via: SIP/2.0/UDP 85.Z.X.Y:5060;branch=z9hG4bKq2rr9h3098sgfpc064d1.1

From: <sip:sipconnect.somewhere.com>;tag=SDide1999-188508444-1343091800918-

To: <sip:441224XX2115@sipconnect.somewhere.com>

Call-ID: SDide1901-1c8dded5e96da6240f3a5caafc54e296-c550fv2

CSeq: 457260459 NOTIFY

Contact: <sip:85.119.X.Y:5060;transport=udp>

Event: message-summary

Subscription-State: terminated

Max-Forwards: 69

Content-Type: application/simple-message-summary

Content-Length: 43

Messages-Waiting: yes

voice-message: 7/0

CWL-ABZ-RTR01#

Jul 24 2012 02:03:20.936 BST: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 481 Call Leg/Transaction Does Not Exist

Via: SIP/2.0/UDP 85.Z.X.Y:5060;branch=z9hG4bKq2rr9h3098sgfpc064d1.1

From: <sip:sipconnect.somewhere.com>;tag=SDide1999-188508444-1343091800918-

To: <sip:441224XX2115@sipconnect.somewhere.com>;tag=E95B994C-15B8

Date: Tue, 24 Jul 2012 01:03:20 GMT

Call-ID: SDide1901-1c8dded5e96da6240f3a5caafc54e296-c550fv2

CSeq: 457260459 NOTIFY

Content-Length: 0

--------- show sip-ua mwi -------------

CWL-ABZ-RTR01#sh sip-ua mwi

MWI type: 2

MWI server: dns:sipconnect.somwhere.com

MWI expires: 3600

MWI port: 5060

MWI transport type: UDP

MWI unsolicited

MWI server IP address:

55XXYYZZ

0

MWI ipaddr cnt 1:

MWI ipaddr idx 0:

MWI server: 85.X.Y.Z, port 5060, transport 1

MWI server dns lookup retry cnt: 0

SIP CME

=======

MWI type: 2

MWI server: dns:sipconnect.somwhere.com

MWI expires: 3600

MWI port: 5060

MWI transport type: UDP

MWI unsolicited

MWI server IP address:

85.X.Y.Z

0.0.0.0

MWI ipaddr cnt 1

MWI ipaddr idx 0

MWI server: 85.X.Y.Z, port 5060, transport 1

MWI server dns lookup retry cnt: 0

SIP CME

=======

MWI type: 2

MWI server: dns:sipconnect.somwhere.com

MWI expires: 3600

MWI port: 5060

MWI transport type: UDP

MWI unsolicited

MWI server IP address:

85.X.Y.Z

0.0.0.0

MWI ipaddr cnt 1

MWI ipaddr idx 0

MWI server: 85.X.Y.Z, port 5060, transport 1

MWI server dns lookup retry cnt: 0

paolo bevilacqua · ‎07-25-2012

You config seems fine except that you don't need 'mwi sip'.

I seen that the notify message comes for a very long number. In CUE, just configure the extension number '2115' for the mailbox, and everything should work fine then.

Kris Thompson · ‎07-26-2012

There is no CUE in this solution. The voicemail is from the SIP provider.

For inboudn calls, the SIP provider sends the full number in the SIP Invite, we then can see "voice ccapi inout" matching an inbound dial-peer, thereby routing the call and using Voice Translation Rules to map to the internal number.

However, when the SIP Notify (more Message Waiting) is received, there is NO matching of dial-peer that takes place to match in the inbound dial-peer. How can we debug why the received "SIP Notify" is not being processed?

Shouldn't the SIP Notify message also matched for processing by an inbound dial-peer?

I modified the Number on the ephone-dn to include the longer phone number as Secondary. The "mwi sip" command was removed. No change in system behaviour. It just seems that the SIP Notify is essentially NOT being processed by the router.

paolo bevilacqua · ‎07-26-2012

Try adding the full number as secondary number under ephone-dn.

Alternatively, you can use sip-profile to strip the prefix from notify message.