I want an external app (built in-house, integrated with CCX) to change prompt variable and have it updated on CCX. However, when I update the variable using CCX application API and try to store it, the CCX API saves it as "P[prompt.wav]" instead of plain string "prompt.wav". Due to this, I'm not able to reflect this change on my CCX IVR.
This is very critical. Does anyone know how to fix it?
If the variable is changed from CCX, the API returns the correct file format, i.e. "prompt.wav"; however, updating it from my app returns it as "P[prompt.wav]".
The version of CCX is 10.6 or 11.5.
When I update the scriptParams(which have the Prompt type) from the CCX value automatically add the value in P array but when I update it from the CCX interface, it does not add the value in the P array.
Because of this, When I make a call to my application my application does not respond.
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...