McDewey

<participants> <Participant> <actions> <action>HOLD</action> <action>DROP</action> </actions> <mediaAddress>2002</mediaAddress> <mediaAddressType>AGENT_DEVICE</mediaAddressType> <startTime>2014-02-11T16:10:23.121Z</startTime> <state>ACTIVE</state> <stateCause></stateCause> <stateChangeTime>2014-02-11T16:10:23.121Z</stateChangeTime> </Participant> <Participant> <actions> <action>RETRIEVE</action> <action>DROP</action> </actions> <mediaAddress>2000</mediaAddress> <mediaAddressType>AGENT_DEVICE</mediaAddressType> <startTime>2014-02-11T16:10:23.121Z</startTime> <state>HELD</state> <stateCause></stateCause> <stateChangeTime>2014-02-11T16:10:36.543Z</stateChangeTime> </Participant> </participants> <state>ACTIVE</state> <uri>/finesse/api/Dialog/12345678</uri> <scheduledCallbackInfo> <callbackTime>2014-03-07T14:30</callbackTime> <callbackNumber>9785551212</callbackNumber> </scheduledCallbackTime> </Dialog> The <wrapUpItems> element applies only to Unified CCX deployments. Note Dialog Object for Nonvoice Tasks For nonvoice media types, this object represents a task. A participant represents an internal or external user's leg of the task. The Dialog object is structured as follows for nonvoice tasks: Several Dialog parameters do not apply for nonvoice tasks, and are returned empty. Note <Dialog> <associatedDialogUri>/finesse/api/Dialog/3216_5432_1</associatedDialogUri> <id>1234_5423_1</id> <mediaType>Cisco_Chat_MRD</mediaType> <mediaProperties> <mediaId>5002</mediaId> <dialedNumber></dialedNumber> <queueNumber>5022</queueNumber> <queueName>UCM_PIM.Func.Agents.SG</queueName> <callKeyCallId>217</callKeyCallId> <callKeySequenceNum>1</callKeySequenceNum> <callKeyPrefix>152018</callKeyPrefix> Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 75 Cisco Finesse Desktop APIs Dialog