McDewey

Multi-vendor documentation library · semantic search · MCP endpoint at /mcp

Page 604

↗ View in doc context
page
604
source
unity-connection/rest-api/cupi/cupi.md
chunk_id
unity-connection::rest-api::cupi::cupi::570

{ "RoutingRule": [ { "ObjectId": "d083fa0b-76ec-4bec-add3-c54aae6033df" }, { "ObjectId": "983efa07-ccb2-4b61-a1e5-083e16ca7513" }, { "ObjectId": "bd8b8092-1c08-4d25-8d35-116d7a677bf4" }, { "ObjectId": "7ee01b59-a619-42f9-9311-5df0f27763ac" } ] } The following is the response from the above PUT request and the actual response will depend upon the information given by you: Response Code: 204 Routing Rule Conditions Each Routing Rule can have a collection of Routing Rule Conditions. The Routing Rule Conditions that belong to a specified Routing Rule can be accessed at /vmrest/routingrules/<routingruleobjectid>/routingruleconditions. When first created, a Routing Rule does not have any Routing Rule Conditions, which means that every call matches it and is routed to its destination. Listing and Viewing The following is an example of a GET that lists all Routing Rule Conditions that belong to a specified Routing Rule: GET https://<connection-server>/vmrest/routingrules/<routingruleobjectid>/routingruleconditions The following is the response from the above GET request: Cisco Unity Connection Provisioning Interface (CUPI) API 572 Cisco Unity Connection Provisioning Interface (CUPI) API--Call Routing Routing Rule Conditions