I have some call handlers setup with "blank" greetings and then route (depending on the schedule) to additional call handlers. I've set this up to automatically handle a very specific business hours schedule, and it works to accomplish the task except that there is a delay (about 1.5-1.75 seconds) before routing to the next call handler. Can this be adjusted? It's critical for my application that I buzz thru 4 "blank" call handlers to make the decision of what greeting to play, but the delays are about 7 seconds and that won't fly.<br><br>
I did some testing on this today and there does appear to be a problem. My first thought was you needed to turn the allow caller input check box off for all these handlers since with that on the conversations will still enter the collect digits conversation even if the greeting is blank. However, even with my system configured with that off, a chain of 5 call handlers still took around 8 seconds to get through all 5 handlers when it should have ripped through them in a second or two.
Looking at the traces, the conversations are always entering the collect digits routine which has a minimum of about a 1.5 second wait time regardless. Ill enter a Track defect for this today and see what can be done about it. I think the simplest thing to do is to check to see if the allow caller input value is set to false to not initiate the digit collection at all.
I tested it again this morning on build 101 (2.4.6) and it's working fine. I was able to rip through 5 call handler setup with "blank" greetings (except for the 5th one) and it went through the list and played the greeting in less than 1 second pretty consistently.
2.4.6 will be available soon (RTP is tentatively schedule for end of this month).
As an aside... I'm kinda confused as to WHY you need to go through 4 blank call handlers to decide which greeting to play. Can you explain your application to me? Maybe there's a better way to approach this...
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...