/mcpDescription Field The user is ready for activity in the media. READY The user has a dialog coming in, but has not accepted it. RESERVED The user enters this state when failing over from one Cisco Finesse to the other or when failing over from one PG side to the other. WORK MediaDialog Class finesse.restservices.MediaDialog Extends finesse.restservices.DialogBase Represents a non-voice media dialog and also exposes the methods to perform actions on the media dialog. For example, accepting, starting, pausing, resuming, transferring, closing, and so on. Example _MediaDialogs = _media.getMediaDialogs({ onCollectionAdd: _handleDialogAdd, onCollectionDelete: _handleDialogDelete, onLoad: _handleMediaDialogsLoaded }); _dialogCollection = _MediaDialogs.getCollection(); for (var mediadialogId in _dialogCollection) { if (_dialogCollection.hasOwnProperty(dialogId)) { _mediadialog = _dialogCollection[mediadialogId]; etc... } } For additional parameters and methods, see RestBase Common Parameters, on page 450. Methods setTaskState(action, handlers, target) Sets the state on a media dialog based on the action given. Example _mediaDialog.setTaskState(finesse.restservices.MediaDialog.TaskActions.ACCEPT, { success: _handleAcceptSuccess, error: _handleAcceptError }, null) Parameters Required Description Type Name Yes The action is invoked when the media dialog is set. String action Yes An object containing the handlers for the request. For more information on handlers, see Request Handlers, on page 447. Object handlers Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 501 Cisco Finesse JavaScript APIs MediaDialog