McDewey

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

Page 109

↗ View in doc context
page
109
source
finesse/v12.5/developer-guide/developer-guide.md
chunk_id
finesse::v12.5::developer-guide::developer-guide::93

Response Scenario Stand-alone Finesse with Unified CCE: Unified CCE accepts the alphanumeric dtmfString. Coresident Finesse with Unified CCX: Unified CCX allows only 0-9, *, or # in the dtmfString. Using any other values results in the following error: <apiError> <errorData>3</errorData> <errorMessage>CF_VALUE_OUT_OF_RANGE</errorMessage> <errorType>Generic Error</errorType> </apiError> Send a DTMF request with an alphanumeric dtmfString. Asynchronous Errors When accessing the Finesse REST API through the Finesse JavaScript library, asynchronous errors have a status code of 400. When receiving the asynchronous error directly through XMPP, the error message has the format described in "Dialog CTI Error Notification." Note Deployment Type Reason ErrorType Unified CCX Attempt to send a DTMF request with a valid requestedAction, a valid targetMediaAddress (agent's extension), and an alphanumeric dtmfString. Unified CCX allows only 0-9, *, and # for the dtmfString. Any other values result in the error. Generic Error ALL Attempt to send a DTMF request for a call when the participant in the dialog whose extension is the targetMediaAddress is in a HELD state. Generic Error ALL Attempt a PUT request to send DTMF while a call is alerting. Generic Error Dialog—Make a Consult Call Request This API allows an agent to make a consult call request. After the request succeeds, the agent can complete the call as a conference or transfer. The requestedAction for a consult call is CONSULT_CALL. The request is sent to the Dialog URL of an existing active call, from where the call is initiated. Finesse supports the transfer or conference of any held call to the current active call, as long as the agent performing the transfer or conference is a participant in both the held and active call. Finesse does not support blind conference through the API or the desktop. Blind conference is defined as follows: An agent has an active call and initiates a consult call to a destination. The agent starts a conference while the call is ringing at the destination. Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 93 Cisco Finesse Desktop APIs Dialog—Make a Consult Call Request