Trigger to Trigger
Trigger to trigger
In Cisco's terminology "trigger to trigger" is defined as a situation in which an application in UCCX forwards a call to another application (trigger) in UCCX.
This is not supported by Cisco and will always result in a failure of the call. The caller will experience being disconnected or hear music on hold infinite.
In a Farlon context, this scenario arises in combination with the use of 'wait on busy' to transfer calls to local extensions or hunt groups.
If extension or hunt group redirects back to a UCCX queue there will be 'trigger to trigger' and the call will fail.
Trigger to trigger could also arise if a UCCX script redirects to an extension/huntpilot that redirects back to a UCCX queue.
- Route calls to linegroups directly to HuntPilot bypassing UCCX
- Do not use 'Wait On Busy'
Please refer to Farlon best practice