McDewey

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

Page 567

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

JSON Example To update the search scope of a directory handler to a search space, 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: { "SearchScope":"6", "SearchScopeObjectId":"1cdaa964-0514-4364-ad74-e55364efb4b4" } The following is an example of the PUT request to update the search scope of directory handler to a search space: Response Code: 200 Updating the Exit Action on a directory handler You can update the exit action, no input action, no selection action and action when caller presses zero on a directory handler. To specify the destination when a caller exits the directory handler using the * key/ or #key, the following fields are used to specify the destination: • ExitAction • ExitTargetConversation • ExitTargetHandlerObjectId In a scenario where caller does not respond to the name entry prompt, the following fields are used to specify the destination the fields: • NoInputAction • NoInputTargetConversation • NoInputTargethandlerObjectId In another scenario where caller does not respond to the name entry prompt the fields, the following fields are used to specify the destination the fields: • NoSelectionAction • NoSelectionTargetConversation • NoSelectionTargetHandlerObjectId If callers press the zero key, the following fields are used to specify the destination the fields: • ZeroAction • ZeroTargetConversation Cisco Unity Connection Provisioning Interface (CUPI) API 535 Cisco Unity Connection Provisioning Interface (CUPI) API--Directory Handler APIs Updating the Exit Action on a directory handler