A customer is troubleshooting the integration between AES and Avaya Oceana Call Server Connector. During the integration the customer finds the following message while checking the AES DMCC log files:Cd /var/log/avaya/aes/dmcc-trace.log hr-oceana1-aes DmccMain[24600] -06:00 2017 275 1 com.avaya/aes | :StartApplicationSTE: com.avaya.sessionsvc.SessionServicesImp1 WARNING ""Authentication failed: clientID=XML Encrypted: 192.168.1.100:25067, user=cscAfter reviewing the error message, which action will fix the customer's problem?
A customer is running an Avaya Oceana® solution and a technical engineer is troubleshooting an operational issue. Many components are logging errors showing that they cannot connect to Unified Collaboration Module (UCM). Which three actions will help to verify the current deployed state of UCM in the solution? (Choose three.)
Which two log files are used to troubleshoot CSC-AES connection problems? (Choose two.)
An administrator logs in to ED admin console to check the current interactions status and finds an ED instance with Event Type "ROUTE_CONTACT_SMS". How is the event type mapped to the SMS channel in Avaya Oceana®?
A customer is unable to login to the Agent Workspaces with Multimedia Channels. Given these log messages:2018-04-23 07:01:11, 358 [pool-128-thread-1] config.OcpOceanaMonitorWASProduction INFO "" [M:setOceanaHeartbeatMessage][T:null].OceanaHeartbeatMessage.MessageText: [GigaSpaces connection OK. Database connection is Broken. ORC Rest service is reachable (http 200).AgentControllerService Alive, Cluster Status ACTIVE] Status: [ERROR]2018-04-24 07:02:09,853 [pool-128-thread-1] serviceability.AgentControllerStatusTask ERROR "" [M:agentControllerStatusRunnable][T:null].error in DBConnection com.avaya.ocp.db.util.PersistenceException: java.sql.SQLException: [Cache JDBC] Communication link failure: Connection refused at com.avaya.ocp.db.util.DbConnFactoryDbcpPool.getDbConnection (DbConnFactoryDbcpPool.java:166)What is causing these log messages?
When describing the Avaya Oceana Monitor, which cluster will have a monitoring snap-in installed that will create a web socket subscription service to feed statistics?