McDewey

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

Page 568

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

• ZeroTargetHandlerObjectId The following are the URLs to fetch the call handlers, directory handlers, and interview handlers: • Call Handlers: /vmrest/handlers/callhandlers • Directory Handlers: /vmrest/handlers/directoryhandlers • InterviewHandler : /vmrest/handlers/interviewhandlers The following sections give some examples of how to specify different types of destinations by using these fields when caller exits the directory handler. Example 1: Call should hang up on exit action. Request URI PUT https://<connection-server>/vmrest/handlers/directoryhandlers/<directoryHandlerObjectId> Request Body <DirectoryHandler> <ExitAction>1</ExitAction> </DirectoryHandler> Response Code: 204 Example 2: Call should be sent to a call handler or a user greeting Request URI PUT https://<connection-server>/vmrest/handlers/directoryhandlers/<directoryHandlerObjectId> Request Body <DirectoryHandler> <ExitAction>2</ExitAction> <ExitTargetConversation>PHGreeting</ExitTargetConversation> <ExitTargetHandlerObjectId>5f8b4a28-8042-4cce-a11c- 0222f106f79f</ExitTargetHandlerObjectId> </DirectoryHandler> Response Code: 204 JSON Example To update the directory handler, do the following: Request URI PUT https://<connection-server>/vmrest/handlers/directoryhandlers/<directoryHandlerObjectId> Accept: application/json Content-Type: application/json Connection: keep-alive Request Body Cisco Unity Connection Provisioning Interface (CUPI) API 536 Cisco Unity Connection Provisioning Interface (CUPI) API--Directory Handler APIs Updating the Exit Action on a directory handler