I am trying to troubleshoot why the MWI is not working in my CCME/CUE box. I am reading a very good document on cco that talks about how to enable trave on cue and see sip debugs.
trace ccn stacksip dbug
mwi refresh telephonenumber 0655
show trace buffer long
How ever, when i execute these commands, i do not see any output, do i need to enable logging or something on cue for me to see output??? i tried everything but no output, it is just like when you telnet and enable debuging, but you do not have term monitor on. please help.
I don't see all of your dial-peers in the configuration you posted. Without that I can only guess that the inbound MWI messaging from CUE is matching an inbound H.323 instead of a SIP dial-peer. This will cause MWI to break. Try adding this to dial-peer voice 84:
incoming called-number 9[7-8]00....
This will cause calls to numbers 9700.... or 9800.... to match dial-peer 84 inbound, thus picking the proper SIP dial-peer.
If it still doesn't work, appropriate debugs to run are:
debug voip ccapi inout
debug ccsip message
Note the extension of the phone where you are trying to light the MWI.
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...