Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Configuring error messages

Updated on January 10, 2022

Configure the display of a message on the CSR desktop when an error occurs in a desktop request from the Call Control Panel to the Computer Telephony Integration (CTI) server.

Every error object has the following properties:

A CTI server-specific error code for the received error.
A brief description of the error.

When the CTI server returns an error message, you can map the error code to the message rule that you create in the Pega Platform layer so that you can the efficiently locate the error.

Pega Call maps the error code with the translated error message, and then sends the message to the desktop.

If the translation does not exist, Pega Call displays the text that you passed in the errMessage property in the error object.

The following table describes the default Pega Call error messages.

Pega Call default error messages

Error codeError message
OPENCTI_AGENT_LOGGED_INAn agent is logged in from another device.
OPENCTI_AGENT_NOT_LOGGED_INAn agent is not logged in from any device.
OPENCTI_CALL_REJECTEDA call request is rejected.
OPENCTI_CF_GENERIC_OPERATIONAn operation error occurred.
OPENCTI_CF_INVALID_DESTINATIONThe request specified an invalid destination.
OPENCTI_CF_INVALID_OBJECT_STATEThe object is not in the correct state to serve the request.
OPENCTI_CONF_ALREADY_PRESENTThe party in the request is already in conference.
OPENCTI_DEST_BUSYThe call attempted is to a busy destination.
OPENCTI_HTTP_ERROR_401Authentication failed or not provided or server refused to respond.
OPENCTI_HTTP_ERROR_404The requested resource not found.
OPENCTI_HTTP_ERROR_405The method not supported.
OPENCTI_HTTP_ERROR_408The server timed out. Waiting for request.
OPENCTI_HTTP_ERROR_500Internal server error.
OPENCTI_HTTP_ERROR_502Bad gateway. Gateway received invalid response from the server.
OPENCTI_HTTP_ERROR_503The server is out of service.
OPENCTI_HTTP_ERROR_504The gateway timed out.
OPENCTI_IN_SAME_STATEThe agent is already in the requested state.
OPENCTI_INV_ACTIVE_STATEThe call is no longer in an active state.
OPENCTI_INV_AGENT_STATEThe agent is in invalid state for the requested operation.
OPENCTI_INV_AGENTID_OR_PASSWORDThe request specified has an invalid AgentID or an invalid agent password or both.
OPENCTI_INV_CALL_DNThe device number (DN) in the request is invalid.
OPENCTI_INV_CALL_STATEThe party in the request call state is invalid.
OPENCTI_INV_DEST_DNThe destination device number (DN) in the request is invalid.
OPENCTI_INV_DN_TYPEThe DN type is invalid.
OPENCTI_INV_LOGIN_REQAgent cannot log in at this time.
OPENCTI_INV_LOGON_DEVICEThe login device that is specified in the request is invalid.
OPENCTI_INV_LOGOUT_REQThe agent cannot log out at this time.
OPENCTI_INV_NOTREADY_REQThe agent cannot change to the NotReady state.
OPENCTI_INV_NUMBERThe requested number is invalid.
OPENCTI_INV_READY_REQThe agent cannot change to the Ready state.
OPENCTI_INV_REASON_CODEThe reason code that is specified in the request does not exist.
OPENCTI_LINK_UNAVAILABLEThe link is in the Unavailable state.
OPENCTI_OUTSTANDING_REQA similar request still in progress.
OPENCTI_PARTY_NOT_ON_CALLThe party is not currently on call.
OPENCTI_REASON_CODE_REQUIREDThe state change requires a valid reason code.
OPENCTI_UNKNOWN_ERRORUnspecified error in client's request.
  1. Create a new JavaScript object instance of pega.cti.desktopApi.errorObject.
  2. Map the error message to the JavaScript object properties.
  3. Forward the error object to the failure callback function of the request function.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us