/mcpMedia Data: <Update> <event>{put|delete}</event> <source>/finesse/api/User/{id}/Media/{mrdId}</source> <data> <Media> <!-- full Media object --> </user> </data> </Update> Payload: <Update> <event>put</event> <source>/finesse/api/User/1001004/Media/5000</source> <requestId>xxxx-xxxx</requestId> <data> <Media> <uri>/finesse/api/User/1001004/Media/5000</uri> <description>Chat MRD</description> <dialogLogoutAction>CLOSE</dialogLogoutAction> <id>5000</id> <interruptible>true</interruptible> <maxDialogLimit>10</maxDialogLimit> <name>Cisco_Chat_MRD</name> <ReasonCode> <category>NOT_READY</category <code>10</code> <forAll>true</forAll> <id>16</id> <label>Team Meeting</label> <uri>/finesse/api/ReasonCode/16</uri> </ReasonCode> <reasonCodeId>16</reasonCodeId> <routable>true</routable> <state>NOT_READY</state> <stateChangeTime>2015-09-11T06:55:14.782Z</stateChangeTime> </Media> </data> </Update> Sample Notification Payload: • State change Notification Triggers: Media and Dialogs/Media Asynchronous Error Notification If an operations performed on a Media or nonvoice Dialog results in an asynchronous error, the error notifications include the error type, error code, and error constant. The ErrorMedia parameter indicates the Media Routing Domain to which the error applies. XML Format: /finesse/api/User/{id}/Media /finesse/api/User/{id}/Dialogs/Media Node: Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 366 Cisco Finesse Notifications Media and Dialogs/Media Asynchronous Error Notification