Skip to main content

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

Handling errors

Updated on October 6, 2021

If an error occurs during a CTI toolbar request, such as hold, answer, and make call, an error message is displayed on the user's desktop.

Every error object has the following properties:

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

When an error message is received the error code can be mapped to the message rule you created in the Pega Platform layer so that the error can be localized. Pega Call maps the error code with the translated error message and sends it to the desktop.

If the translation does not exist it just displays the text that you passed in the errMessage property in error object.

The following are the default error messages provided with Pega Call application:

Pega Call default error messages

Error codeError message
OPENCTI_AGENT_LOGGED_INAgent is logged in from another device.
OPENCTI_AGENT_NOT_LOGGED_INAgent is not logged in from any device.
OPENCTI_CALL_REJECTEDCall 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_PRESENTParty in request is already in conference.
OPENCTI_DEST_BUSYCall attempted to a busy destination.
OPENCTI_HTTP_ERROR_401Authentication failed or not provided, server refused to respond.
OPENCTI_HTTP_ERROR_404Requested resource not found.
OPENCTI_HTTP_ERROR_405Method not supported.
OPENCTI_HTTP_ERROR_408Server 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_503Server out of service.
OPENCTI_HTTP_ERROR_504Gateway timed out.
OPENCTI_IN_SAME_STATEAgent is already in the requested state.
OPENCTI_INV_ACTIVE_STATECall is no longer in an active state.
OPENCTI_INV_AGENT_IDAgent ID is invalid.
OPENCTI_INV_AGENT_STATEAgent is in invalid state for the requested operation.
OPENCTI_INV_AGENTID_OR_PASSWORDThe request specified has an invalid AgentID and/or invalid agent password.
OPENCTI_INV_CALL_DNThe device number (DN) in the request is invalid.
OPENCTI_INV_CALL_STATEParty in request call state is invalid.
OPENCTI_INV_DEST_DNThe destination device number (DN) in the request is invalid.
OPENCTI_INV_DN_TYPEThe device number (DN) type is invalid.
OPENCTI_INV_LOGIN_REQAgent cannot log in at this time.
OPENCTI_INV_LOGON_DEVICEThe logon device specified in the request is invalid.
OPENCTI_INV_LOGOUT_REQAgent cannot log out at this time.
OPENCTI_INV_NOTREADY_REQAgent cannot change to NotReady state.
OPENCTI_INV_NUMBERThe requested number is invalid.
OPENCTI_INV_READY_REQAgent cannot change to Ready state.
OPENCTI_INV_REASON_CODEThe reason code specified in the request does not exist.
OPENCTI_LINK_UNAVAILABLELink is in Unavailable state.
OPENCTI_OUTSTANDING_REQSimilar 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 of type pega.cti.desktopApi.errorObject.
  2. Map the error message to the JavaScript object properties.
  3. Forward the error object created 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