AD HOC Conferencing. Customer gets dropped when Agent leaves call.
We have the conferencing setup so that the conference only ends when Onnet agents leave the conference. For some reason an agent conferences in a supervisor and then leaves the call which then drops the customer. It is not with every call. DSP resources are hardware and very plentiful. The phones being used are 7942's. The BiB is turned on and no MRGL are associated to the phone level. I am not sure why a customer is getting dropped.. RTMT shows plenty of DSP resources and CM has the correct service parameter. Can anybody lead me the right way?
AD HOC Conferencing. Customer gets dropped when Agent leaves ca
So I think this has to do with CVP warm transfers. The script has network transfer set to 0 and a send to vru node in it. This is clearly a signalling problem. Probably going to have to start a TAC case.
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...