I have a weird problem. There are 32 ports on my Unity server. The version is 4.0(3). The customer's call into the main call handler and if they hit 6, they are transferred to the route point extension (5800)for the ACD. It seems that whenever Unity tries to transfer to this number on port 29 through 32 it busies out. It only happens with the transfers. The voicemail ports are all configured the same. Has anyone ever seen this? Even viewer alarm is as follows.
Event Type: Warning
Event Source: CiscoUnity_TSP
Event Category: None
Event ID: 109
Time: 9:41:54 AM
Cisco Unity-CM TSP device 6 (Unity port 30): Failed blind transfer to extension 5800. Busy tone detected. If this is a persistent problem, it may indicate a problem on the Cisco Unity and/or Cisco Call Manager. Verify that transfers are working, and contact TAC if the problem persists.
Re: Busy Unity ports when trying to transfer to ACD
Follow up on the cause of this for me: the transfer to operator ch was the cause. We have multiple 0 extensions setup for different sites. Some ch's were incorrectly configure to reoute to the default operator ch instead of the custom operator ch's. Correcting where the calls route fixed it.
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...