McDewey

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

Page 365

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

agent on the outbound call. For a reservation call in Preview Outbound mode, the fromAddress is the dialer port. . For a reservation call in Direct Preview Outbound mode, the fromAddress is the dialer port. • toAddress: The dialed number of the original call. If the caller calls a route point, the toAddress is the route point. If the caller calls an agent directly, the toAddress is the agent's extension. For an Outbound Option Dialer call, the toAddress is the customer phone number called by the dialer. For a reservation call in Outbound Option Preview mode, the toAddress is the extension of the agent who received the call. For a reservation call in Direct Preview Outbound mode, the toAddress is the extension of the agent on the outbound call. When a call is transferred, the fromAddress and toAddress in subsequent dialog notifications are those of the surviving call. For example, if an agent who is on a call places a consult call and then transfers the original call, the fromAddress and toAddress in the subsequent dialog notifications are those of the original call because the original call is the surviving call. However, if the agent puts the consult call on hold, retrieves the original call, and then transfers the consult call, the fromAddress and toAddress in subsequent dialog notifications are those of the consult call. In this case, the consult call is the surviving call. When an agent who is on a call places a consult call, the original call will be on hold and the consult call will be active. Once the call is complete where the agent either transfers or places the call on conference, the surviving call's dialog notifications will contain the dropped call's dialog id in the secondary id field. During Dialog notifications, there are two types of notifications that get sent to the Dialog node. • When a dialog is added or removed from the Dialog collection of the user. XML Format: /finesse/api/User/{id}/Dialogs Node: /finesse/api/User/{id}/Dialogs (when a Dialog is added or removed from the Dialog collection for the user) Source: Dialogs Data: <Update> <data> <dialogs> <Dialog> <!-- full Dialog object --> </Dialog> </dialogs> </data> <event>{POST|DELETE}</event> <requestId>xxxxxxxxx</requestId> <source>/finesse/api/User/{id}/Dialogs</source> </Update> Payload: Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 349 Cisco Finesse Notifications Dialog Notification