I'm trying to use the forward on failure of my cti route point to go to unity on failure and vice versa but the call go always to the forward no answer. (I closed the crs server,the engine, I also tried to close the cti manager...)Has anyone succeed to use the forward on failure of the cti route point (witch is my Jtapi trigger)? One more question. In witch situation does the forward on failure is use for the cti port? Thanks.
Hi Andy. I read the document, done some testing and never been able to get the failure. I even retrieve the no answer on cti rp and the call got thru the busy. So what I understand is that I must consider the no answer as a failure when defined. What about the CTI port? I never been able to go thru the no answer and/or failure. Normal??? Is it ever looked at? Thanks.
Forward on Failure is when the call manager is trying to place a call and the CTI Route point itself is failing, it will follow the CFF. This does not happen as often and is typically related to a failure on the CallManager side. When the IVR is down or a PG is down it treats that as a busy call, not a failure. I have some documentation from Cisco when they were doing tests and basically it points to the fact that you need to configure CFB, CFNA, CFF on a Route Point to guaruntee you will catch all failures. As for CTI Ports it isn't typically necessary to set it on the ports, the Route Point is sufficient.
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...