McDewey

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

Page 299

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

Request Body: for caller system transfer <Callhandler> <AfterMessageAction>2</AfterMessageAction> <AfterMessageTargetConversation>SystemTransfer</AfterMessageTargetConversation> </Callhandler> 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 <Callhandler> <AfterMessageAction>2</AfterMessageAction> <AfterMessageTargetConversation>GreetingAdministrator</AfterMessageTargetConversation> </Callhandler> The following is the response from the PUT request for greeting administrator and the actual response will depend upon the information given by you: Response Code: 204 For sign in <Callhandler> <AfterMessageAction>2</AfterMessageAction> <AfterMessageTargetConversation>SubSignIn</AfterMessageTargetConversation> </Callhandler> The following is the response from the PUT request for sign in and the actual response will depend upon the information given by you: Response Code: 204 For system transfer: Request Body: <CallhandlerPrimaryTemplate> <AfterMessageAction>2</AfterMessageAction> <AfterMessageTargetConversation>SubSysTransfer</AfterMessageTargetConversation> </CallhandlerPrimaryTemplate> The following is the response from the PUT request for user system transfer and the actual response will depend upon the information given by you: Response Code: 204 JSON Example Cisco Unity Connection Provisioning Interface (CUPI) API 267 Cisco Unity Connection Provisioning Interface (CUPI) API for User Template Updating after Message Actions