I have a new implementation, when I call the IVR the agent goes to Reserved state then back to Ready. The MIVR logs:
308529: Aug 07 11:21:59.210 EDT %MIVR-SS_TEL-7-UNK:CallID:157 MediaId:3995/4 Task:28000000164 Got CiscoTermConnSelectChangedEv CTI_10160, events on the AddressCallObserver.
308530: Aug 07 11:21:59.232 EDT %MIVR-SS_TEL-3-CONSULT_FAILED:Consult failed : All Call ids=CallID:157 MediaId:3995/4 Task:28000000164,Extension=10810,Exception=com.cisco.jtapi.PlatformExceptionImpl: Transfer failed (probable cause is one of the call legs was hung up or disconnected from the far end),Failure reason=Transfer Violates Logical Partitioning Policy. Aborting CallCTIERR_TRANSFERFAILED=0x8ccc000e::Transfer failed (probable cause is one of the call legs was hung up or disconnected from the far end)
308531: Aug 07 11:21:59.233 EDT %MIVR-SS_TEL-3-EXCEPTION:com.cisco.jtapi.PlatformExceptionImpl: Transfer failed (probable cause is one of the call legs was hung up or disconnected from the far end)
CSS and Partition are OK. calling party CSS has access to CTI RP, RP CSS has access to the CTI ports and CTI CSS has access to the Agent DN partition.
I looked also at the Enterprise parameter for the Logical Partitioning param and is Disabled ( False)
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...