VM and analog phones <--> DPNSS PBX <--> QSIG-DPNSS Converter <--> MGCP gateway <--> CUCM cluster <--> voip phones
In CUCM I have a VM pilot number and a route pattern pointing to the gateway. The VM number and the phones DNs are in the same partition and this partition is in the gateway's CSS. MWI works for the users.
I've recently added a new cluster member and some new users with new user device profiles and directory numbers (they are all in the above partition). The service parameters on the new CUCM server related to MWI are the same as on the other cluster members. For these new users the MWI doesn't work, although the new DNs are reachable from behind the PBX from the analog phones and also the VM is reachable from the new voip phones. The issue must be with the new DNs or the device profiles, because if I use one of the old device profiles to log in into the new phone, the WMI works OK. I also checked the settings on the VM system are the same for old and new users.
Any advise how to troubleshoot the MWI messages would be greatly appreciated.
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...