We're having difficulty with getting Translation Routing to work properly with an Avaya ACD. The PG always properly instructs the Avaya to route the call to the appropriate destination, but the associated call data never makes it to the agent desktop. The call data usually appears in the CALL UPDATE EVENT instead of the BEGIN CALL EVENT, and the PG always sets the Call Type to 'ACD In Call' instead of 'Trans Route.' Our CTI client code always checks for call type and call data in the BEGIN CALL EVENT. Seems like the PG is confused about the call being a Translation Routed call...but yet it still directs the call properly on the Avaya. Any ideas as to what's wrong? Config problem in Avaya? Config problem within ICM?? Thanks for any help!!
What are you doing on this message board? When I did the CTI for Avaya, the callvariables were being populated fine on the Begin call event? Right now, there seems to be a timing issue. The data is getting merged with the voice only after the begin call event. I have experienced the problem before but cannot remember the solution though.
For the call Type not being populated properly, are you explicity specifying the calltype as Trans Route?
From Avaya's standpoint, all it needs configured are the few DNIS's for translation route. From the ICM side, the translation route labels need to be present for the corresponding Avaya DNIS's
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...