McDewey

<event>PUT</event> <requestId>xxxxxxxxx</requestId> <source>/finesse/api/Dialog/16804377</source> </Update> • Modification of participant state (for example, when a participant answers or hangs up a call) • A new participant on the call • Modification of the call data or actions Notification Triggers: Dialogs/Media Notification Finesse sends a Dialogs/Media notification when information (or an action) changes for a nonvoice dialog to which the user belongs. For an interruptible Media Routing Domain configured to accept interrupts, Finesse sends only a Media state change when an agent is interrupted in that MRD. It does not send Dialogs/Media notifications with the action list modified to reflect the fact that actions not permitted on the tasks in that media. The state change is the only indication to the Finesse applications that no actions are allowed on the interrupted dialogs. 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. Important XML Format: /finesse/api/User/{id}/Dialogs/Media Node: /finesse/api/User/{id}/ Media/{mrdId}/Dialogs (when a Dialog is added or removed from the Dialog collection for the user, for example offered or closed) 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}/Media{mrdld}/Dialogs</source> </Update> Payload: Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 355 Cisco Finesse Notifications Dialogs/Media Notification