I have similar problem with my Unity. The problem was that when people would call into Unity they would get a busy. A check of the status page showed that only the first port was busy, all others were free.
The problem for me was this: When a call is forwarded CallMaanger checks a table to make sure there are now forward loops. By default the max number of forward loops allowed is 12. When the call is forwarded the first time the forward loop
counter for the DN is incremented. When the call is disconnected the forward loop counter for that DN is decremented. From time to time we run into an issue where the counter is not decremented. This detection
is to prevent the issue where phone a forwards to b and phone b forwards to a. A call to either a or b would cause a major forwarding loop and spike the CPU in the CallManager.
When I set port one to forward to higher port instead of the next then the busies went away. The problem is with CM and there is a fix but you have to contact TAC to get it.
From the trace he sent I can see that the call is getting extended to the port OK -- it wasn't getting terminated as a forwarding loop. What I can't see was why the call was getting torn down. We needed to get an additional trace for that.
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...