Is there a reason for using a separate trigger for the CS_Queue App?
I would recommended implementing the logic of the script associated to APP2 to the same main script:
Go To CS_Queue (which is a label)
Logic of the CS_Queue
Trigger Redirect will cause the call to be transferred to the trigger and it will use the same logic of REDIRECT to a CTI port that is selected by the UCCX under the Call Control Group associated to the trigger.
Besides the Parameter exposure and the easiness of debugging that the trigger redirect provides are there any other reasons to use this method?
Reporting. Some customers want to know what percentage of caller chose option 1 vs. 2 for example. There is no native way to accomplish this and one of the more common is to have a bunch of Triggers on the same applicatiion with Call Redirects at the various menu choices to other triggers. The beginning of the script has a Switch statement allowing the script to jump forward to where it left off (or some other way to continue on). The Application Summary report then shows how many contacts hit the various triggers.
The rule of thumb I use is this: if it's roughly a function (programming term) where I can pass in a few variables, have it do a thing, and then get a result AND it will be used across multiple scripts AND it's a fair amount of code (i.e. not three steps), then I use a subflow. ELSE I put it in the original script or do a redirect to another trigger. Subflows are a PITA to troubleshoot though. You *will* lose some hair before realizing that your subflow is why something isn't working.
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...