Just last week came up on this config. Since that time, we have a CTI port (and associated DNs) that route to voicemail (non-Unity) -- but only for a while. Then the DN goes busy (not the whole route point) and will only reset with a stop/start of CM service on the call processor. This config has worked for 2 years, so it appears to be a 3.3 issue.
The CTI port is non-registered; it only exists to establish DNs that are then Route Patterned out the voicemail gateway for SMDI integration. Our dial plan includes some Centrex lines that forward to these DNs for voicemail; however it also includes this one non-Centrex number that is giving us fits. All the Centrex forwarding to the CTI appears okay, only this non-Centrex line forwarding will hang the DN. This line typically will handle 200+ calls per day.
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...