McDewey

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

Page 280

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

Updating Caller Input Parameters The following is an example of the PUT request that updates caller input parameters: PUT https://<connection-server>/vmrest/handlers/callhandlerprimarytemplates/<CallhandlerprimarytemplatesObjectId>/menuentries All the parameters for caller inputs are present in callhandlerprimarytemplate. Request Body: <CallhandlerPrimaryTemplate> <OneKeyDelay>9999</OneKeyDelay> <EnablePrependDigits>true</EnablePrependDigits> <PrependDigits>4545</PrependDigits> </CallhandlerPrimaryTemplate> 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 <PrependDigit> parameter must be having digits only (extension parameter) Note Updating Caller Input Keys The following is an example of the PUT request that updates the call input keys: PUT https://<connection-server>/vmrest/handlers/callhandlers/<CallhandlerObjectId>/menuentries The following is an example of the PUT request that edits the call input keys: PUT https://<connection-server>/vmrest/handlers/callhandlers/<CallhandlerObjectId>/menuentries/* where "*" is the touchtone key ID. <MenuEntry> <Locked>true</Locked> </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 Example 1: Edit call actions Parameters Values Ignore 0 Hang Up 1 Take Message 4 Cisco Unity Connection Provisioning Interface (CUPI) API 248 Cisco Unity Connection Provisioning Interface (CUPI) API for User Template Updating Caller Input Parameters

Image 1 from page 280