Peripheral Variables Not Written on IP IVR Abandon
We have an IPCC environment and are using a Cisco IP IVR to do both queueing and self-service. In the self-service IVR application, we set ICM data throughout the call. If the caller opts out to an agent, the peripheral variables appear in the Route Call Detail and TCD tables. However, if the caller is satisfied with the self-service IVR and hangs up while in the IVR, the call is considered abandoned and the Route Call Detail and TCD tables have NULLs in the peripheral variable fields.
We've tried trapping the hang up in the IVR script so that we can still send a success or fail to ICM, but the data is still not written to those tables.
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...