Error messages displayed on the user interface
Desktop Connect stirves to be an intuitive application to use, however there are cases when an error message needs to be displayed to the user. The limited space available on the desktop allows for a minimalistic error message to be displayed without any instructions on how to eliminate the issue.
This article is meant to provide possible causes and explanations.
| Error message | Description | Possible causes |
|---|---|---|
| Station already in use | User is already signed in and active in a sessions | Please make sure you have logged out from the application, or you have closed all your browser instances. Tabs in the same browser count as a single session |
| Event queue error!Attempting to reconnect | Connection to the Desktop Connect server was lost, and is being re-created | Make sure you have internet connection Make sure configuration stored in the CRM - Call Center name, Organization ID correspond to the configuration sent. |
| setAgentState Failure | Agent state could not be set | Make sure there is no active call on the agent station when trying to login. Make sure the auxiliary reason codes exist on the Avaya CM when trying to switch between not ready states |
| Invalid AgentId is specified | Wrong Avaya CM Elite agent identifier specified | Please specify a valid Avaya CM Elite agent extension |
| Check if station is logged in | Station is not logged in or off hook | Please sign into your Avaya hardphone or Avaya One-X station with the station extetnsion you are trying to use in Desktop Connect |
| An attempt to login in an ACD agent with an incorrect password | Avaya CM Elite password is invalid | Please use correct password when logging in with an Avaya CM Elite agent |
| Agent is already logged into another Station | Agent is alredy logged into ACD | Please logout with the agent or also use the same station when trying to sign into Desktop Connect. |
| Authorization error... | The user is not authorized to use Desktop Connect | Make sure you have internet connection. Make sure you have consented with Desktop Connect authentication requirements and authentication was successfull. |
| Unexpected error :( Try refresh | Unexpected error | Please refresh your browser |
| Station is missing | No station was specified that could be call observed by Desktop Connect | Specify a valid station |
| UNABLE_TO_MONITOR | Desktop Connect is unable to call observe the specified station | Please make sure the station is administered correctly in Avaya CM. Please make sure the station identifier specified is correct. Please make sure that Avaya AES infrastructure is live and capable of observing the specified device. |