McDewey

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

Page 112

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

Dialog—Initiate a Single Step Transfer This API allows a user to make a single-step transfer request. After a user makes a successful request, that user's active call is transferred to the destination provided in the toAddress parameter. The requestedAction for a single-step transfer is TRANSFER_SST. This request is sent on the Dialog URL of an existing active call, from where the call is initiated. Therefore, the dialogId in the URL represents the dialogId of the active call. https://<FQDN>/finesse/api/Dialog/<dialogId> URI: https://finesse1.xyz.com/finesse/api/Dialog/54321 Example URI: Agents can use this API. An agent must be a participant in the dialog and the agent's extension must match the targetMediaAddress. Security Constraints: PUT HTTP Method: Application/XML Content Type: XML Input/Output Format: <Dialog> <requestedAction>TRANSFER_SST</requestedAction> <toAddress>1001002</toAddress> <targetMediaAddress>1001001</targetMediaAddress> </Dialog> HTTP Request: dialogId (required): The ID of the dialog requestedAction (required): The way in which the dialog is created (TRANSFER_SST) toAddress (required): The destination to which to transfer the call targetMediaAddress (required): The extension of the agent who is making the request Request Parameters: 202: Successfully Accepted This response only indicates a successful completion of the request. The request is processed and the actual response is sent as part of a dialog notification. Note 400: Parameter Missing 400: Invalid Input 400: Invalid Destination 401: Authorization Failure 401: Invalid Authorization User Specified 500: Internal Server Error HTTP Response: Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 96 Cisco Finesse Desktop APIs Dialog—Initiate a Single Step Transfer