McDewey

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

Page 515

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

{ "URI": "/vmrest/handlers/callhandlers/b2d3d56a-f0c2-4839-98c5- 48770690244a/callhandlerowners/ac6dda36-798d-4eea-9055-db5a31eb5599", "ObjectId": "ac6dda36-798d-4eea-9055-db5a31eb5599", "UserObjectId": "5aeb75a4-14c2-474d-bec9-90aa731ee4cc", "UserURI": "/vmrest/users/5aeb75a4-14c2-474d-bec9-90aa731ee4cc", "TargetHandlerObjectId": "b2d3d56a-f0c2-4839-98c5-48770690244a" } Response Code:200 2. For a distribution list as a call handler owner: { "URI": "/vmrest/handlers/callhandlers/b2d3d56a-f0c2-4839-98c5- 48770690244a/callhandlerowners/ac6dda36-798d-4eea-9055-db5a31eb5599", "ObjectId": "4e35ed6c-6aed-42e4-9723-b859706ac749", "DistributionListObjectId": "988630fa-313a-4f0c-980f-f6dc78add3ca", "DistributionListURI": "/vmrest/users/988630fa-313a-4f0c-980f-f6dc78add3ca", "TargetHandlerObjectId": "b2d3d56a-f0c2-4839-98c5-48770690244a" } Response Code:200 Delete a Call Handler Owner The following is an example of the DELETE request that can be used to delete a call handler owner: DELETE https://<connection-server>/vmrest/callhandlers/<callhandlerId>/callhandlerowners/<callhandlerowner-objectid> The following is the response from the above DELETE request and the actual response will depend upon the information given by you: Response Code: 204 JSON Example To delete a call handler owner, do the following: DELETE https://<connection-server>/vmrest/callhandlers/<callhandler-objectid>/callhandlerowners/<callhandlerowner-objectid> Accept: application/json Connection: keep_alive The following is the response from the above DELETE request and the actual response will depend upon the information given by you: Response Code: 204 Cisco Unity Connection Provisioning Interface (CUPI) API 483 Cisco Unity Connection Provisioning Interface (CUPI) API -- Call Handler Delete a Call Handler Owner