A routing rule created through CUPI cannot be given a RuleIndex. It is created at RuleIndex 0, and every other rule's RuleIndex goes up by 1.
Checked 2026-09-23
- Vendor
- Cisco
- Product
- Cisco Unity Connection
- Subsystem
- CUPI REST API
- Deployment
- on-premises
- Region
- not restricted
- Release range
- not version-scoped on page
- Checked
- 2026-09-23
Sources
- Cisco Unity Connection Provisioning Interface (CUPI) API--Call Routing — Cisco Systems · tier 2 current vendor documentation · Rule ordering note (RuleIndex)
Cite this note
APA
WarmTransfer. (2026, September 23). Unity Connection call handler configuration and how to obtain it: source note unity-connection-call-handler-config-cupi-ruleindex. WarmTransfer. https://warmtransfer.net/knowledge/claims/unity-connection-call-handler-config-cupi-ruleindex
BibTeX
@misc{warmtransfer-claim-unity-connection-call-handler-config-cupi-ruleindex,
title = {Unity Connection call handler configuration and how to obtain it: source note unity-connection-call-handler-config-cupi-ruleindex},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/unity-connection-call-handler-config-cupi-ruleindex},
note = {Source note unity-connection-call-handler-config-cupi-ruleindex, checked 2026-09-23}
}