McDewey

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

Page 79

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

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 Request Body: for user system transfer <MenuEntry> <Action>2</Action> <TargetConversation>SubSysTransfer</TargetConversation> </MenuEntry> 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 Example 4: Users with Mailbox Request Body: <MenuEntry> <Action>2</Action> <TargetConversation>PHTransfer</TargetConversation> <TargetHandlerObjectId>71cb381b-fd16-4ba8-8a1d-e71684e57b0e</TargetHandlerObjectId> </MenuEntry> The following is the response from the PUT request and the actual response will depend upon the information given by you: Response Code: 204 JSON Example For conversation, do the following: Request URI: PUT https://<connection-server>/vmrest/callhandlerprimarytemplates/<CallhandlerprimarytemplatesObjectId>/menuentries/4 Accept: application/json Content-type: application/json Connection: keep-alive Request Body: { "Action":"2", "TargetConversation":"SubSignIn" } The following is the response from the above PUT request and the actual response will depend upon the information given by you: Response Code: 204 Cisco Unity Connection Provisioning Interface (CUPI) API 47 Cisco Unity Connection Provisioning Interface (CUPI) API -- User Caller Input Updating Caller Input Keys