I had a similar issue today with a 4.2(1)sr1a Installation that was running well for months.
A handful of lines could not be CFAed anymore. If you forced it through the GUI, outside callers received fast busy (unallocated number).
DB Layer was fine (DBLHelper showed OK, DBL Service and eventually Server restarts did not help either). The solution was to fully remove the lines in question from the system (not just from the phone). After re-adding them to the phones, everything was fine.
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...