Call remains in "conferenced" state after the call is released
We have a scenario where a lengthy recorded message is set up through a ICM call routing script. If we call the number we assigned to the script using our hard phones the call is disconnected as soon as the recorded message is finished playing.
When we use Cisco Administrator Desktop and the conference feature, the call remains in the "conferenced" state after the call has been released.
My assumption was that our reports would be smarter than CAD and would get it right. However, reporting agrees with CAD, it thinks the call remained on a conference call for the whole time.
In the script we set some variables for the call, play the message through "RunExtScript" node, set a call type, than use the "ReleaseCall" node to disconnect the call. Any ideas how we can configure the script other than this?
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...
[toc:faq]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 discusse...