/mcpResponse Code: 204 Changing Routing Rule Indices As noted in previous sections, a Routing Rule's RuleIndex field cannot be modified when creating or updating a Routing Rule. Instead, you can change a Routing Rule's RuleIndex only in the context of ordering all of the Routing Rules in a collection. The following is an example of a PUT request that modifies the RuleIndices of a collection of Routing Rules: PUT https://<connection-server>/vmrest/routingrules <RoutingRules> <RoutingRule> <ObjectId>aabbccdd-1111-2222-3333-1234567890ab</ObjectId> </RoutingRule> <RoutingRule> <ObjectId>12345678-abcd-abcd-abcd-123412341234</ObjectId> </RoutingRule> <RoutingRule> <ObjectId>99990000-1234-1234-1234-abcdef012345</ObjectId> </RoutingRule> </RoutingRules> The following is a response from the above PUT request: 204 No Content After this PUT request is processed, the Routing Rule with ObjectId aabbccdd-1111-2222-3333-1234567890ab would have RuleIndex 0, the Routing Rule with ObjectId 12345678-abcd-abcd-abcd-123412341234 would have RuleIndex 1, and the Routing Rule with ObjectId 99990000-1234-1234-1234-abcdef012345 would have RuleIndex 2. JSON Example To update the order of routing rule, do the following: Request URI: PUT https://<connection-server>/vmrest/routingrules Accept: application/json Content-Type: application/json Connection: keep-alive Request Body: Cisco Unity Connection Provisioning Interface (CUPI) API 571 Cisco Unity Connection Provisioning Interface (CUPI) API--Call Routing Changing Routing Rule Indices