Re: SIP Notify Unsolicited and CUCME Ephone - 481 Does Not Exist
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.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...