/mcp<MediaDomainList> <MediaDomain> <description>Default Media Routing Domain for Cisco_Voice</description> <id>1</id> <interruptible>false</interruptible> <maxDialogDuration>0</maxDialogDuration> <name>Cisco_Voice</name> </MediaDomain> <MediaDomain> <description /> <id>5000</id> <interruptible>true</interruptible> <maxDialogDuration>28800</maxDialogDuration> <name>Cisco_Chat_MRD</name> </MediaDomain> <MediaDomain> <description /> <id>5003</id> <interruptible>false</interruptible> <maxDialogDuration>60</maxDialogDuration> <name>Cisco_Twitter_MRD</name> </MediaDomain> </MediaDomainList> Example HTTP Response <ApiErrors> <ApiError> <ErrorType>Internal Server Error</ErrorType> <ErrorMessage>Runtime Exception</ErrorMessage> <ErrorData></ErrorData> </ApiError> </ApiErrors> Example Failure Response: Agent States for Nonvoice Media Users can set the following states with the Media APIs: • LOGIN • READY • NOT_READY • LOGOUT Users enter the following states automatically while on a task. Users cannot place themselves in these states. For example, agents enter ACTIVE state when they accept a task. • RESERVED • ACTIVE • PAUSED • INTERRUPTED • WORK_READY The agent enters WORK_NOT_READY state automatically if the Finesse server on which the agent is signed in disconnects. When agent signs in again or Finesse side reconnects to CCE, the agent is moved out of the WORK_NOT_READY state. This state cannot be set from the agent desktop. Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 178 Cisco Finesse Desktop APIs Agent States for Nonvoice Media