McDewey

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

Page 289

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

The following is the response from the PUT request and the actual response will depend upon the information given by you: Response Code: 204 AfterGreetingTargetHandlerObjectId can be viewed from URI: Note GET https://<connection-server>/vmrest/handlers/directoryhandler Example 5: Change Conversation Request Body: for broadcast message administrator <UserTemplateGreeting> <AfterGreetingAction>2</AfterGreetingAction> <AfterGreetingTargetConversation>BroadcastMessageAdministrator</AfterGreetingTargetConversation> </UserTemplateGreeting> The following is the response from the PUT request for broadcast message administrator and the actual response will depend upon the information given by you: Response Code: 204 Request Body: for caller system transfer <UserTemplateGreeting> <AfterGreetingAction>2</AfterGreetingAction> <AfterGreetingTargetConversation>SystemTransfer</AfterGreetingTargetConversation> </UserTemplateGreeting> The following is the response from the PUT request for caller system transfer and the actual response will depend upon the information given by you: Response Code: 204 Request Body: for greeting administrator <UserTemplateGreeting> <AfterGreetingAction>2</AfterGreetingAction> <AfterGreetingTargetConversation>GreetingsAdministrator</AfterGreetingTargetConversation> </UserTemplateGreeting> The following is the response from the PUT request for greeting administrator and the actual response will depend upon the information given by you: Cisco Unity Connection Provisioning Interface (CUPI) API 257 Cisco Unity Connection Provisioning Interface (CUPI) API for User Template Changing after Greeting Actions

Image 1 from page 289