Source note · Troubleshooting Unified CCX scripts and call flows
When a UCCX number does not reach the script at all, checking trigger and call control group state in RTMT before debugging the script is the efficient order, because a trigger that is out of service never invokes the application.
inferred · Checked 2026-10-02
- Vendor
- Cisco
- Product
- Unified Contact Center Express
- Subsystem
- Unified CM Telephony subsystem
- Deployment
- on-premises
- Region
- not restricted
- Release range
- 15.0
- Status
- inferred
- Checked
- 2026-10-02
Sources
- Cisco Unified Contact Center Express Administration and Operations Guide, Release 15.0 - Real-Time Monitoring — Cisco Systems · tier 2 current vendor documentation · Real-Time Monitoring > Triggers Page (combined with Add Application Triggers in cisco-uccx-1501-aog-cisco-applications-config)
Cite this note
APA
WarmTransfer. (2026, October 2). Troubleshooting Unified CCX scripts and call flows: source note uccx-script-troubleshooting-inf-trigger-before-script. WarmTransfer. https://warmtransfer.net/knowledge/claims/uccx-script-troubleshooting-inf-trigger-before-script
BibTeX
@misc{warmtransfer-claim-uccx-script-troubleshooting-inf-trigger-before-script,
title = {Troubleshooting Unified CCX scripts and call flows: source note uccx-script-troubleshooting-inf-trigger-before-script},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/uccx-script-troubleshooting-inf-trigger-before-script},
note = {Source note uccx-script-troubleshooting-inf-trigger-before-script, checked 2026-10-02}
}