Error diagnostic codes
Following are the various error diagnostic codes from different services that are part of Gatekeeper, Media Manager, and Connectors:
Diagnostic Code |
Description |
|---|---|
| CC-CCAAS-10001 | The request missed required parameters. If the problem persists, contact support. |
| CC-CCAAS-10002 | An error occurred while reading the configuration. If the problem persists, contact support. |
| CC-CCAAS-10003 | The extension monitoring was not found. If the problem persists, contact your CCaaS provider. |
| CC-CCAAS-10004 | An error occurred while starting the monitoring. If the problem persists, contact support. |
| CC-CCAAS-10005 | An error occurred while starting the monitoring. If the problem persists, contact support. |
| CC-CCAAS-10007 | An error occurred. If the problem persists, contact support. |
| CC-CCAAS-10008 | An error occurred while starting the monitoring. If the problem persists, contact support. |
| CC-CCAAS-10009 | An error occurred while starting the monitoring. The request timeout limit has been reached. If the problem persists, contact support. |
| CC-CCAAS-10010 | The credential to request the media is invalid. Update the credential with the correct information. |
| CC-CCAAS-10011 | An error occurred while starting the monitoring. If the problem persists, contact support. |
| CC-CCAAS-10012 | The credential provided has insufficient permission. Update the credential with the correct information. |
| CC-CCAAS-10013 | An error occurred while starting the monitoring. The CCaaS Provider rate limit has been exceeded. Check the CCaaS Provider limits’ configuration. |
| CC-CCAAS-10014 | An error occurred while starting the monitoring. The CCaaS Provider quota limit has been exceeded. Check the CCaaS Provider limits’ configuration. |
| CC-CCAAS-10015 | The CCaaS Provider could not find the extension informed. Check if the extension is correct. |
| CC-CCAAS-10016 | The extension informed is invalid. Check if the extension is correct. |
| CC-CCAAS-10017 | An error occurred. If the problem persists, contact support. |
| CC-CCAAS-10018 | Failed to start CTI Integration monitoring. Check if the extension is correct. |
| CC-CCAAS-10101 | The request missed required parameters. If the problem persists, contact support. |
| CC-CCAAS-10102 | An error occurred while reading the configuration. If the problem persists, contact support. |
| CC-CCAAS-10103 | The monitoring subscription was not found. If the problem persists, contact your support. |
| CC-CCAAS-10104 | An error occurred while stopping the monitoring. If the problem persists, contact support. |
| CC-CCAAS-10105 | An error occurred. If the problem persists, contact support. |
| CC-CCAAS-10106 | An error occurred. If the problem persists, contact support. |
| CC-CCAAS-10199 | Stop monitoring executed successfully. |
| CC-CCAAS-10201 | The request missed required parameters. If the problem persists, contact support. |
| CC-CCAAS-10202 | An error occurred while reading the configuration. If the problem persists, contact support. |
| CC-CCAAS-10203 | The monitoring subscription was not found. If the problem persists, contact support. |
| CC-CCAAS-10204 | An error occurred while updating the call data. If the problem persists, contact support. |
| CC-CCAAS-10205 | An error occurred. If the problem persists, contact support. |
| CC-CCAAS-10206 | An error occurred. If the problem persists, contact support. |
| CC-CCAAS-10299 | Update call data executed successfully. |
| CC-CCAAS-10301 | The Recording Identifier is empty. Check the RecordingIdentifierKey configuration in the scope configuration. |
| CC-CCAAS-10302 | An error occurred while reading the configuration. If the problem persists, contact support. |
| CC-CCAAS-10303 | An error occurred while starting the recording. If the problem persists, contact support. |
| CC-CCAAS-10304 | The media didn’t arrive in time from the CCaaS provider. If the problem persists, contact your CCaaS provider. |
| CC-CCAAS-10305 | An error occurred while starting the recording. If the problem persists, contact support. |
| CC-CCAAS-10306 | An error occurred while starting the recording. If the problem persists, contact support. |
| CC-CCAAS-10307 | An error occurred while starting the recording. If the problem persists, contact support. |
| CC-CCAAS-10308 | An error occurred while starting the recording. If the problem persists, contact support. |
| CC-CCAAS-10309 | The CCaaS Provider could not find the media with the recording identifier (callId) informed. |
| CC-CCAAS-10310 | The credential to request the media is invalid. Update the credential with the correct information. |
| CC-CCAAS-10311 | An error occurred while starting the recording. If the problem persists, contact support. |
| CC-CCAAS-10312 | The credential provided has insufficient permission. Update the credential with the correct information. |
| CC-CCAAS-10313 | An error occurred while starting the recording. If the problem persists, contact support. |
| CC-CCAAS-10314 | An error occurred while starting the recording. The CCaaS Provider rate limit has been exceeded. Check the CCaaS Provider limits’ configuration. |
| CC-CCAAS-10315 | An error occurred while starting the recording. The CCaaS Provider quota limit has been exceeded. Check the CCaaS Provider limits’ configuration. |
| CC-CCAAS-10316 | An error occurred while starting the recording. The request timeout limit has been reached. If the problem persists, contact support. |
| CC-CCAAS-10317 | An error occurred while starting the recording. The recording side configuration doesn’t match with the media available. Please check the recording side configuration in Gatekeeper and the CCaaS Provider. |
| CC-CCAAS-10318 | An error occurred while starting the recording. If the problem persists, contact support. |
| CC-CCAAS-10319 | The recording identifier (callId) is invalid. Check the RecordingIdentifierKey configuration in the scope configuration. |
| CC-CCAAS-10320 | An error occurred. If the problem persists, contact support. |
| CC-CCAAS-10399 | Start recording executed successfully. |
| CC-CCAAS-10401 | An error occurred while stopping the recording. If the problem persists, contact support. |
| CC-CCAAS-10402 | An error occurred while stopping the recording. If the problem persists, contact support. |
| CC-CCAAS-10403 | An error occurred while stopping the recording. If the problem persists, contact support. |
| CC-CCAAS-10499 | Stop recording executed successfully. |
| CC-CCAAS-10501 | An error occurred while pausing the recording. If the problem persists, contact support. |
| CC-CCAAS-10502 | An error occurred while pausing the recording. If the problem persists, contact support. |
| CC-CCAAS-10503 | An error occurred while pausing the recording. If the problem persists, contact support. |
| CC-CCAAS-10504 | An error occurred while pausing the recording. If the problem persists, contact support. |
| CC-CCAAS-10505 | An error occurred. If the problem persists, contact support. |
| CC-CCAAS-10599 | Pause recording command executed successfully |
| CC-CCAAS-10601 | An error occurred while resuming the recording. If the problem persists, contact support. |
| CC-CCAAS-10602 | An error occurred while resuming the recording. If the problem persists, contact support. |
| CC-CCAAS-10603 | An error occurred while resuming the recording. If the problem persists, contact support. |
| CC-CCAAS-10604 | An error occurred while resuming the recording. If the problem persists, contact support. |
| CC-CCAAS-10605 | An error occurred while resuming the recording. If the problem persists, contact support. |
| CC-CCAAS-10606 | An error occurred while resuming the recording. The token used to authenticate with the CCaaS provider has expired. If the problem persists, contact support. |
| CC-CCAAS-10607 | An error occurred while resuming the recording. The CCaaS provider endpoint is unreachable. If the problem persists, contact support. |
| CC-CCAAS-10608 | An error occurred while resuming the recording. The CCaaS provider access limit was exceeded. If the problem persists, contact support. |
| CC-CCAAS-10609 | An error occurred while resuming the recording. The credentials used to authenticate with the CCaaS provider do not have the necessary permissions to resume the recording. If the problem persists, contact support. |
| CC-CCAAS-10610 | An error occurred. If the problem persists, contact support. |
| CC-CCAAS-10699 | ResumeRecordingCommand executed successfully. |
| CC-CCAAS-10701 | An error occurred. If the problem persists, contact support. |
| CC-CCAAS-20004 | An error occurred. If the problem persists, contact support. |
| CC-CCAAS-20005 | An error occurred. If the problem persists, contact support. |
| CC-CCAAS-20006 | An error occurred. If the problem persists, contact support. |
| CC-CCAAS-20007 | An error occurred. If the problem persists, contact support. |
| CC-CCAAS-20008 | An error occurred. If the problem persists, contact support. |
| CC-CCAAS-20009 | An error occurred. If the problem persists, contact support. |
| CC-CCAAS-20010 | An error occurred. If problem persists, contact support. |
| CC-CCAAS-20011 | An error occurred. If the problem persists, contact support. |
| CC-CCAAS-20012 | An error occurred. If the problem persists, contact support. |
| CC-CCAAS-20013 | An error occurred. If the problem persists, contact support. |
| CC-CCAAS-20014 | An error occurred. If the problem persists, contact support. |
| CC-CCAAS-20015 | An error occurred. If the problem persists, contact support. |
| CC-CCAAS-20016 | An error occurred. If the problem persists, contact support. |
| CC-CCAAS-30010 | An error occurred. If the problem persists, contact support. |
| GK-ASR-00000 | Generic Error. Contact support and provide all diagnostic code info. |
| GK-ASR-00001 | Invalid request as it contains some invalid parameters. You can see additional fields of the response for invalid parameters and their values. For more information, contact support and provide all diagnostic code info. |
| GK-ASR-00002 | Server is unavailable. One of the internal services is not available. For more information, contact support and provide all diagnostic code info. |
| GK-ASR-00003 | Server API timeout. An API call to one of the internal services has timed out. For more information, contact support and provide all diagnostic code info. |
| GK-AUD-00400 | Invalid Request: the request is invalid as it contains some invalid parameters. |
| GK-AUD-00403 | Unauthorized: the user is unauthorized to perform the requested operation. |
| GK-AUD-00404 | Not Found: the specified entity identifier does not exist. |
| GK-AUD-00409 | Already Exists: the specified entity identifier is already in use. |
| GK-AUD-00423 | Invalid State: the entity’s current state is not aligned with the required state. |
| GK-AUD-10000 | Generic Error: an unexpected internal error has occurred. |
| GK-AUD-10499 | Server API Canceled: an API call to one of the internal services has canceled. |
| GK-AUD-10500 | Server Error: an API call to one of the internal services has failed. |
| GK-AUD-10503 | Server is Unavailable: one of the internal services is not available. |
| GK-AUD-10504 | Server API Timeout: an API call to one of the internal services has timed out. |
| GK-AUD-30000 | Database Generic Error: an unexpected error occurred while trying to perform database operation. |
| GK-AUD-30503 | Database Unavailable: failed to connect to the database. |
| GK-AUD-30529 | Database Overloaded: the database cannot handle the incoming request load. |
| GK-AUD-30900 | Database Delete Quota Exceeded: the number of delete requests has exceeded the quota limit. Please try again later. |
| GK-AUD-33000 | Blob-Storage Generic Error: an unexpected error occurred while trying to perform blob-storage operation. |
| GK-AUD-33503 | Blob-Storage Unavailable: failed to connect to the blob-storage. |
| GK-AUD-90400 | Invalid Scope Resource: the scope resource is invalid as it contains some invalid parameters. |
| GK-AUD-90404 | Missing Scope Resource: the required scope resource does not exist. |
| GK-AUD-99000 | Server Error: an API call to one of the internal services has failed. |
| GK-AZM-10000 | Your organization’s administrator has not yet approved access to this application. Contact your Entra ID administrator to grant the necessary permissions for your tenant. |
| GK-AZM-10001 | The userinfo API can only be accessed by a USER member type. |
| GK-AZM-10002 | The request is missing an access token. |
| GK-AZM-10003 | Missing or invalid user ID issuer. |
| GK-AZM-10004 | Missing or invalid user ID. |
| GK-AZM-10005 | No authorization was found for a user or client in this request. Contact your administrator. |
| GK-AZM-10006 | An error occurred in the LNcP service while retrieving user info. Please check the service logs for more details. |
| GK-CAL-00400 | Invalid Request: the request is invalid as it contains some invalid parameters. |
| GK-CAL-00403 | Unauthorized: the user is unauthorized to perform the requested operation. |
| GK-CAL-00404 | Not Found: the specified entity identifier does not exist. |
| GK-CAL-00409 | Already Exists: the specified entity identifier is already in use. |
| GK-CAL-00423 | Invalid State: the entity’s current state is not aligned with the required state. |
| GK-CAL-01900 | Invalid Calibration Model: the calibration model did not meet the validation criteria. |
| GK-CAL-10000 | Generic Error: an unexpected internal error has occurred. |
| GK-CAL-10499 | Server API Canceled: an API call to one of the internal services has canceled. |
| GK-CAL-10500 | Server Error: an API call to one of the internal services has failed. |
| GK-CAL-10503 | Server is Unavailable: one of the internal services is not available. |
| GK-CAL-10504 | Server API Timeout: an API call to one of the internal services has timed out. |
| GK-CAL-30000 | Database Generic Error: an unexpected error occurred while trying to perform database operation. |
| GK-CAL-30503 | Database Unavailable: failed to connect to the database. |
| GK-CAL-30529 | Database Overloaded: the database cannot handle the incoming request load. |
| GK-CAL-30900 | Database Delete Quota Exceeded: the number of delete requests has exceeded the quota limit. Please try again later. |
| GK-CAL-33000 | Blob-Storage Generic Error: an unexpected error occurred while trying to perform blob-storage operation. |
| GK-CAL-33503 | Blob-Storage Unavailable: failed to connect to the blob-storage. |
| GK-CAL-99000 | Server Error: an API call to one of the internal services has failed. |
| GK-CIDVC-00400 | Invalid Request: the request is invalid as it contains some invalid parameters. |
| GK-CIDVC-00403 | Unauthorized: the user is unauthorized to perform the requested operation. |
| GK-CIDVC-00404 | Not Found: the specified entity identifier does not exist. |
| GK-CIDVC-00409 | Already Exists: the specified entity identifier is already in use. |
| GK-CIDVC-01901 | Version Mismatch: the received Neustar version does not match the expected one. |
| GK-CIDVC-10000 | Generic Error: an unexpected internal error has occurred. |
| GK-CIDVC-10499 | Server API Canceled: an API call to one of the internal services has canceled. |
| GK-CIDVC-10500 | Server Error: an API call to one of the internal services has failed. |
| GK-CIDVC-10503 | Server is Unavailable: one of the internal services is not available. |
| GK-CIDVC-10504 | Server API Timeout: an API call to one of the internal services has timed out. |
| GK-CIDVC-30000 | Database Generic Error: an unexpected error occurred while trying to perform database operation. |
| GK-CIDVC-30503 | Database Unavailable: failed to connect to the database. |
| GK-CIDVC-30529 | Database Overloaded: the database cannot handle the incoming request load. |
| GK-CIDVC-30900 | Database Delete Quota Exceeded: the number of delete requests has exceeded the quota limit. Please try again later. |
| GK-CIDVC-90400 | Invalid Scope Resource: the scope resource is invalid as it contains some invalid parameters. |
| GK-CIDVC-90404 | Missing Scope Resource: the required scope resource does not exist. |
| GK-CIDVC-99000 | Server Error: an API call to one of the internal services has failed. |
| GK-CIDVC-NE-00400 | Invalid Request: an invalid request error has been received from the Caller ID Validation provider. |
| GK-CIDVC-NE-00403 | Unauthorized: an unauthorized error has been received from the Caller ID Validation provider. |
| GK-CIDVC-NE-00422 | Bad Request: a bad request error has been received from the Caller ID Validation provider. |
| GK-CIDVC-NE-01902 | Delayed Request: the gap between the call_start_timestamp value and the time the request is recorded at the Caller ID Validation provider exceeds 4 seconds. |
| GK-CIDVC-NE-10000 | Generic Error: an internal error has been received from the Caller ID Validation provider. |
| GK-CPC-00000 | Generic Error. Contact support and provide all diagnostic code info. |
| GK-CPC-00001 | Invalid request as it contains some invalid parameters. You can see additional fields of the response for invalid parameters and their values. For more information, contact support and provide all diagnostic code info. |
| GK-CPC-00002 | Server is unavailable. One of the internal services is not available. For more information, contact support and provide all diagnostic code info. |
| GK-CPC-00003 | Server API timeout. An API call to one of the internal services has timed out. For more information, contact support and provide all diagnostic code info. |
| GK-CPC-00004 | Server network error. The communication with one of the internal services has failed due to a network error. For more information, contact support and provide all diagnostic code info. |
| GK-CPM-00400 | Invalid Request: the request is invalid as it contains some invalid parameters. |
| GK-CPM-00403 | Unauthorized: the user is unauthorized to perform the requested operation. |
| GK-CPM-00404 | Not Found: the specified entity identifier does not exist. |
| GK-CPM-00409 | Already Exists: the specified entity identifier is already in use. |
| GK-CPM-10000 | Generic Error: an unexpected internal error has occurred. |
| GK-CPM-10499 | Server API Canceled: an API call to one of the internal services has canceled. |
| GK-CPM-10500 | Server Error: an API call to one of the internal services has failed. |
| GK-CPM-10503 | Server is Unavailable: one of the internal services is not available. |
| GK-CPM-10504 | Server API Timeout: an API call to one of the internal services has timed out. |
| GK-CPM-30000 | Database Generic Error: an unexpected error occurred while trying to perform database operation. |
| GK-CPM-30503 | Database Unavailable: failed to connect to the database. |
| GK-CPM-30529 | Database Overloaded: the database cannot handle the incoming request load. |
| GK-CPM-30900 | Database Delete Quota Exceeded: the number of delete requests has exceeded the quota limit. Please try again later. |
| GK-CPM-33000 | Blob-Storage Generic Error: an unexpected error occurred while trying to perform blob-storage operation. |
| GK-CPM-33503 | Blob-Storage Unavailable: failed to connect to the blob-storage. |
| GK-CPM-99000 | Server Error: an API call to one of the internal services has failed. |
| GK-CPP-00000 | Generic Error. Contact support and provide all diagnostic code info. |
| GK-CPP-00001 | Invalid request as it contains some invalid parameters. You can see additional fields of the response for invalid parameters and their values. For more information, contact support and provide all diagnostic code info. |
| GK-CPP-00002 | Server is unavailable. One of the internal services is not available. For more information, contact support and provide all diagnostic code info. |
| GK-CPP-00003 | Server API timeout. An API call to one of the internal services has timed out. For more information, contact support and provide all diagnostic code info. |
| GK-CPP-00004 | Server network error. The communication with one of the internal services has failed due to a network error. For more information, contact support and provide all diagnostic code info. |
| GK-CRA-00400 | Invalid Request: the request is invalid as it contains some invalid parameters. |
| GK-CRA-10000 | Generic Error: an unexpected internal error has occurred. |
| GK-CRA-10499 | Server API Canceled: an API call to one of the internal services has canceled. |
| GK-CRA-10500 | Server Error: an API call to one of the internal services has failed. |
| GK-CRA-10503 | Server is Unavailable: one of the internal services is not available. |
| GK-CRA-10504 | Server API Timeout: an API call to one of the internal services has timed out. |
| GK-CRA-30000 | Database Generic Error: an unexpected error occurred while trying to perform database operation. |
| GK-CRA-30503 | Database Unavailable: failed to connect to the database. |
| GK-CRA-30529 | Database Overloaded: the database cannot handle the incoming request load. |
| GK-CRA-30900 | Database Delete Quota Exceeded: the number of delete requests has exceeded the quota limit. Please try again later. |
| GK-CRA-99000 | Server Error: an API call to one of the internal services has failed. |
| GK-CSM-01900 | CSM cannot initiate a recording due to a missing parameter (realmId or agentInfo). |
| GK-CSM-01901 | CSM cannot initiate a recording due to a missing recording call identifier parameter. |
| GK-CSM-01902 | CSM failed to call CreateSubscription due to a missing RealmId parameter. |
| GK-CSM-01903 | Agent subscription events stream suspended, pending resuming or deletion. |
| GK-CSM-01904 | Agent subscription events stream deleted. |
| GK-CSM-01905 | A REPORT_ERROR action was either triggered explicitly by a Webhook or Light Rule, or relates to external webhook unavailability. |
| GK-CSM-10000 | Generic Error: an unexpected internal error has occurred. |
| GK-CSM-10500 | Server Error: an API call to one of the internal services has failed |
| GK-CWTM-00400 | Invalid Request: the request is invalid as it contains some invalid parameters. |
| GK-CWTM-00403 | Unauthorized: the user is unauthorized to perform the requested operation. |
| GK-CWTM-00404 | Not Found: the specified entity identifier does not exist. |
| GK-CWTM-00409 | Already Exists: the specified entity identifier is already in use. |
| GK-CWTM-10000 | Generic Error: an unexpected internal error has occurred. |
| GK-CWTM-10499 | Server API Canceled: an API call to one of the internal services has canceled. |
| GK-CWTM-10500 | Server Error: an API call to one of the internal services has failed. |
| GK-CWTM-10503 | Server is Unavailable: one of the internal services is not available. |
| GK-CWTM-10504 | Server API Timeout: an API call to one of the internal services has timed out. |
| GK-CWTM-30000 | Database Generic Error: an unexpected error occurred while trying to perform database operation. |
| GK-CWTM-30503 | Database Unavailable: failed to connect to the database. |
| GK-CWTM-30529 | Database Overloaded: the database cannot handle the incoming request load. |
| GK-CWTM-30900 | Database Delete Quota Exceeded: the number of delete requests has exceeded the quota limit. Please try again later. |
| GK-CWTM-33000 | Blob-Storage Generic Error: an unexpected error occurred while trying to perform blob-storage operation. |
| GK-CWTM-33503 | Blob-Storage Unavailable: failed to connect to the blob-storage. |
| GK-CWTM-99000 | Server Error: an API call to one of the internal services has failed. |
| GK-DPC-00000 | Generic Error. Contact support and provide all diagnostic code info. |
| GK-DPC-00001 | Invalid request as it contains some invalid parameters. You can see additional fields of the response for invalid parameters and their values. For more information, contact support and provide all diagnostic code info. |
| GK-DPC-00002 | Server is unavailable. One of the internal services is not available. For more information, contact support and provide all diagnostic code info. |
| GK-DPC-00003 | Server API timeout. An API call to one of the internal services has timed out. For more information, contact support and provide all diagnostic code info. |
| GK-DPC-00004 | Server network error. The communication with one of the internal services has failed due to a network error. For more information, contact support and provide all diagnostic code info. |
| GK-DPM-00400 | Invalid Request: the request is invalid as it contains some invalid parameters. |
| GK-DPM-00403 | Unauthorized: the user is unauthorized to perform the requested operation. |
| GK-DPM-00404 | Not Found: the specified entity identifier does not exist. |
| GK-DPM-00409 | Already Exists: the specified entity identifier is already in use. |
| GK-DPM-10000 | Generic Error: an unexpected internal error has occurred. |
| GK-DPM-10499 | Server API Canceled: an API call to one of the internal services has canceled. |
| GK-DPM-10500 | Server Error: an API call to one of the internal services has failed. |
| GK-DPM-10503 | Server is Unavailable: one of the internal services is not available. |
| GK-DPM-10504 | Server API Timeout: an API call to one of the internal services has timed out. |
| GK-DPM-30000 | Database Generic Error: an unexpected error occurred while trying to perform database operation. |
| GK-DPM-30503 | Database Unavailable: failed to connect to the database. |
| GK-DPM-30529 | Database Overloaded: the database cannot handle the incoming request load. |
| GK-DPM-30900 | Database Delete Quota Exceeded: the number of delete requests has exceeded the quota limit. Please try again later. |
| GK-DPM-33000 | Blob-Storage Generic Error: an unexpected error occurred while trying to perform blob-storage operation. |
| GK-DPM-33503 | Blob-Storage Unavailable: failed to connect to the blob-storage. |
| GK-DPM-99000 | Server Error: an API call to one of the internal services has failed. |
| GK-DPP-00000 | Generic Error. Contact support and provide all diagnostic code info. |
| GK-DPP-00001 | Invalid request as it contains some invalid parameters. You can see additional fields of the response for invalid parameters and their values. For more information, contact support and provide all diagnostic code info. |
| GK-DPP-00002 | Server is unavailable. One of the internal services is not available. For more information, contact support and provide all diagnostic code info. |
| GK-DPP-00003 | Server API timeout. An API call to one of the internal services has timed out. For more information, contact support and provide all diagnostic code info. |
| GK-DPP-00004 | Server network error. The communication with one of the internal services has failed due to a network error. For more information, contact support and provide all diagnostic code info. |
| GK-ENG-00400 | Invalid Request: the request is invalid as it contains some invalid parameters. |
| GK-ENG-00403 | Unauthorized: the user is unauthorized to perform the requested operation. |
| GK-ENG-00404 | Not Found: the specified entity identifier does not exist. |
| GK-ENG-00409 | Already Exists: the specified entity identifier is already in use. |
| GK-ENG-00423 | Invalid State: the entity’s current state is not aligned with the required state. |
| GK-ENG-10000 | Generic Error: an unexpected internal error has occurred. |
| GK-ENG-10499 | Server API Canceled: an API call to one of the internal services has canceled. |
| GK-ENG-10500 | Server Error: an API call to one of the internal services has failed. |
| GK-ENG-10503 | Server is Unavailable: one of the internal services is not available. |
| GK-ENG-10504 | Server API Timeout: an API call to one of the internal services has timed out. |
| GK-ENG-30000 | Database Generic Error: an unexpected error occurred while trying to perform database operation. |
| GK-ENG-30503 | Database Unavailable: failed to connect to the database. |
| GK-ENG-30529 | Database Overloaded: the database cannot handle the incoming request load. |
| GK-ENG-30900 | Database Delete Quota Exceeded: the number of delete requests has exceeded the quota limit. Please try again later. |
| GK-ENG-33000 | Blob-Storage Generic Error: an unexpected error occurred while trying to perform blob-storage operation. |
| GK-ENG-33503 | Blob-Storage Unavailable: failed to connect to the blob-storage. |
| GK-ENG-99000 | Server Error: an API call to one of the internal services has failed. |
| GK-FRM-00400 | Invalid Request: the request is invalid as it contains some invalid parameters. |
| GK-FRM-00403 | Unauthorized: the user is unauthorized to perform the requested operation. |
| GK-FRM-00404 | Not Found: the specified entity identifier does not exist. |
| GK-FRM-00409 | Already Exists: the specified entity identifier is already in use. |
| GK-FRM-10000 | Generic Error: an unexpected internal error has occurred. |
| GK-FRM-10499 | Server API Canceled: an API call to one of the internal services has canceled. |
| GK-FRM-10500 | Server Error: an API call to one of the internal services has failed. |
| GK-FRM-10503 | Server is Unavailable: one of the internal services is not available. |
| GK-FRM-10504 | Server API Timeout: an API call to one of the internal services has timed out. |
| GK-FRM-30000 | Database Generic Error: an unexpected error occurred while trying to perform database operation. |
| GK-FRM-30503 | Database Unavailable: failed to connect to the database. |
| GK-FRM-30529 | Database Overloaded: the database cannot handle the incoming request load. |
| GK-FRM-30900 | Database Delete Quota Exceeded: the number of delete requests has exceeded the quota limit. Please try again later. |
| GK-FRM-99000 | Server Error: an API call to one of the internal services has failed. |
| GK-GRM-00400 | Invalid Request: the request is invalid as it contains some invalid parameters. |
| GK-GRM-00403 | Unauthorized: the user is unauthorized to perform the requested operation. |
| GK-GRM-00404 | Not Found: the specified entity identifier does not exist. |
| GK-GRM-00409 | Already Exists: the specified entity identifier is already in use. |
| GK-GRM-10000 | Generic Error: an unexpected internal error has occurred. |
| GK-GRM-10499 | Server API Canceled: an API call to one of the internal services has canceled. |
| GK-GRM-10500 | Server Error: an API call to one of the internal services has failed. |
| GK-GRM-10503 | Server is Unavailable: one of the internal services is not available. |
| GK-GRM-10504 | Server API Timeout: an API call to one of the internal services has timed out. |
| GK-GRM-30000 | Database Generic Error: an unexpected error occurred while trying to perform database operation. |
| GK-GRM-30503 | Database Unavailable: failed to connect to the database. |
| GK-GRM-30529 | Database Overloaded: the database cannot handle the incoming request load. |
| GK-GRM-30900 | Database Delete Quota Exceeded: the number of delete requests has exceeded the quota limit. Please try again later. |
| GK-GRM-99000 | Server Error: an API call to one of the internal services has failed. |
| GK-JOB-00400 | Invalid Request: the request is invalid as it contains some invalid parameters. |
| GK-JOB-00403 | Unauthorized: the user is unauthorized to perform the requested operation. |
| GK-JOB-00404 | Not Found: the specified entity identifier does not exist. |
| GK-JOB-00409 | Already Exists: the specified entity identifier is already in use. |
| GK-JOB-10000 | Generic Error: an unexpected internal error has occurred. |
| GK-JOB-10499 | Server API Canceled: an API call to one of the internal services has canceled. |
| GK-JOB-10500 | Server Error: an API call to one of the internal services has failed. |
| GK-JOB-10503 | Server is Unavailable: one of the internal services is not available. |
| GK-JOB-10504 | Server API Timeout: an API call to one of the internal services has timed out. |
| GK-JOB-30000 | Database Generic Error: an unexpected error occurred while trying to perform database operation. |
| GK-JOB-30503 | Database Unavailable: failed to connect to the database. |
| GK-JOB-30529 | Database Overloaded: the database cannot handle the incoming request load. |
| GK-JOB-30900 | Database Delete Quota Exceeded: the number of delete requests has exceeded the quota limit. Please try again later. |
| GK-JOB-99000 | Server Error: an API call to one of the internal services has failed. |
| GK-PRM-00400 | Invalid Request: the request is invalid as it contains some invalid parameters. |
| GK-PRM-00403 | Unauthorized: the user is unauthorized to perform the requested operation. |
| GK-PRM-00404 | Not Found: the specified entity identifier does not exist. |
| GK-PRM-00409 | Already Exists: the specified entity identifier is already in use. |
| GK-PRM-10000 | Generic Error: an unexpected internal error has occurred. |
| GK-PRM-10499 | Server API Canceled: an API call to one of the internal services has canceled. |
| GK-PRM-10500 | Server Error: an API call to one of the internal services has failed. |
| GK-PRM-10503 | Server is Unavailable: one of the internal services is not available. |
| GK-PRM-10504 | Server API Timeout: an API call to one of the internal services has timed out. |
| GK-PRM-30000 | Database Generic Error: an unexpected error occurred while trying to perform database operation. |
| GK-PRM-30503 | Database Unavailable: failed to connect to the database. |
| GK-PRM-30529 | Database Overloaded: the database cannot handle the incoming request load. |
| GK-PRM-30900 | Database Delete Quota Exceeded: the number of delete requests has exceeded the quota limit. Please try again later. |
| GK-PRM-99000 | Server Error: an API call to one of the internal services has failed. |
| GK-REC-00400 | Invalid Request: the request is invalid as it contains some invalid parameters. |
| GK-REC-10000 | Generic Error: an unexpected internal error has occurred. |
| GK-REC-10499 | Server API Canceled: an API call to one of the internal services has canceled. |
| GK-REC-10500 | Server Error: an API call to one of the internal services has failed. |
| GK-REC-10503 | Server is Unavailable: one of the internal services is not available. |
| GK-REC-10504 | Server API Timeout: an API call to one of the internal services has timed out. |
| GK-REC-30000 | Database Generic Error: an unexpected error occurred while trying to perform database operation. |
| GK-REC-30503 | Database Unavailable: failed to connect to the database. |
| GK-REC-30529 | Database Overloaded: the database cannot handle the incoming request load. |
| GK-REC-30900 | Database Delete Quota Exceeded: the number of delete requests has exceeded the quota limit. Please try again later. |
| GK-REC-99000 | Server Error: an API call to one of the internal services has failed. |
| GK-REP-00400 | Invalid Request: the request is invalid as it contains some invalid parameters. |
| GK-REP-00404 | Not Found: the specified entity identifier does not exist. |
| GK-REP-00423 | Invalid State: the entity’s current state is not aligned with the required state. |
| GK-REP-01900 | Invalid Calibration Model Buffer: the calibration-model buffer is invalid. |
| GK-REP-10000 | Generic Error: an unexpected internal error has occurred. |
| GK-REP-10499 | Server API Canceled: an API call to one of the internal services has canceled. |
| GK-REP-10500 | Server Error: an API call to one of the internal services has failed. |
| GK-REP-10503 | Server is Unavailable: one of the internal services is not available. |
| GK-REP-10504 | Server API Timeout: an API call to one of the internal services has timed out. |
| GK-REP-30000 | Database Generic Error: an unexpected error occurred while trying to perform database operation. |
| GK-REP-30503 | Database Unavailable: failed to connect to the database. |
| GK-REP-30529 | Database Overloaded: the database cannot handle the incoming request load. |
| GK-REP-30900 | Database Delete Quota Exceeded: the number of delete requests has exceeded the quota limit. Please try again later. |
| GK-REP-33000 | Blob-Storage Generic Error: an unexpected error occurred while trying to perform blob-storage operation. |
| GK-REP-33503 | Blob-Storage Unavailable: failed to connect to the blob-storage. |
| GK-REP-99000 | Server Error: an API call to one of the internal services has failed. |
| GK-SCP-00400 | Invalid Request: the request is invalid as it contains some invalid parameters. |
| GK-SCP-00403 | Unauthorized: the user is unauthorized to perform the requested operation. |
| GK-SCP-00404 | Not Found: the specified entity identifier does not exist. |
| GK-SCP-00409 | Already Exists: the specified entity identifier is already in use. |
| GK-SCP-00423 | Invalid State: the entity’s current state is not aligned with the required state. |
| GK-SCP-10000 | Generic Error: an unexpected internal error has occurred. |
| GK-SCP-10499 | Server API Canceled: an API call to one of the internal services has canceled. |
| GK-SCP-10500 | Server Error: an API call to one of the internal services has failed. |
| GK-SCP-10503 | Server is Unavailable: one of the internal services is not available. |
| GK-SCP-10504 | Server API Timeout: an API call to one of the internal services has timed out. |
| GK-SCP-30000 | Database Generic Error: an unexpected error occurred while trying to perform database operation. |
| GK-SCP-30503 | Database Unavailable: failed to connect to the database. |
| GK-SCP-30529 | Database Overloaded: the database cannot handle the incoming request load. |
| GK-SCP-30900 | Database Delete Quota Exceeded: the number of delete requests has exceeded the quota limit. Please try again later. |
| GK-SCP-99000 | Server Error: an API call to one of the internal services has failed. |
| GK-SES-00400 | Invalid Request: the request is invalid as it contains some invalid parameters. |
| GK-SES-00403 | Unauthorized: the user is unauthorized to perform the requested operation. |
| GK-SES-00404 | Not Found: the specified entity identifier does not exist. |
| GK-SES-00423 | Invalid State: the entity’s current state is not aligned with the required state. |
| GK-SES-01900 | Session Quota Exceeded: the number of sessions within the engagement has exceeded the permitted limit. |
| GK-SES-10000 | Generic Error: an unexpected internal error has occurred. |
| GK-SES-10499 | Server API Canceled: an API call to one of the internal services has canceled. |
| GK-SES-10500 | Server Error: an API call to one of the internal services has failed. |
| GK-SES-10503 | Server is Unavailable: one of the internal services is not available. |
| GK-SES-10504 | Server API Timeout: an API call to one of the internal services has timed out. |
| GK-SES-30000 | Database Generic Error: an unexpected error occurred while trying to perform database operation. |
| GK-SES-30503 | Database Unavailable: failed to connect to the database. |
| GK-SES-30529 | Database Overloaded: the database cannot handle the incoming request load. |
| GK-SES-30900 | Database Delete Quota Exceeded: the number of delete requests has exceeded the quota limit. Please try again later. |
| GK-SES-33000 | Blob-Storage Generic Error: an unexpected error occurred while trying to perform blob-storage operation. |
| GK-SES-33503 | Blob-Storage Unavailable: failed to connect to the blob-storage. |
| GK-SES-99000 | Server Error: an API call to one of the internal services has failed. |
| GK-TRC-00000 | Generic Error. Contact support and provide all diagnostic code info. |
| GK-TRC-00001 | Invalid request as it contains some invalid parameters. You can see additional fields of the response for invalid parameters and their values. For more information, contact support and provide all diagnostic code info. |
| GK-TRC-00002 | Server is unavailable. One of the internal services is not available. For more information, contact support and provide all diagnostic code info. |
| GK-TRC-00003 | Server API timeout. An API call to one of the internal services has timed out. For more information, contact support and provide all diagnostic code info. |
| GK-TRC-00004 | Server network error. The communication with one of the internal services has failed due to a network error. For more information, contact support and provide all diagnostic code info. |
| GK-TXT-00400 | Invalid Request: the request is invalid as it contains some invalid parameters. |
| GK-TXT-00404 | Not Found: the specified entity identifier does not exist. |
| GK-TXT-00409 | Already Exists: the specified entity identifier is already in use. |
| GK-TXT-10000 | Generic Error: an unexpected internal error has occurred. |
| GK-TXT-10499 | Server API Canceled: an API call to one of the internal services has canceled. |
| GK-TXT-10500 | Server Error: an API call to one of the internal services has failed. |
| GK-TXT-10503 | Server is Unavailable: one of the internal services is not available. |
| GK-TXT-10504 | Server API Timeout: an API call to one of the internal services has timed out. |
| GK-TXT-30000 | Database Generic Error: an unexpected error occurred while trying to perform database operation. |
| GK-TXT-30503 | Database Unavailable: failed to connect to the database. |
| GK-TXT-30529 | Database Overloaded: the database cannot handle the incoming request load. |
| GK-TXT-30900 | Database Delete Quota Exceeded: the number of delete requests has exceeded the quota limit. Please try again later. |
| GK-TXT-33000 | Blob-Storage Generic Error: an unexpected error occurred while trying to perform blob-storage operation. |
| GK-TXT-33503 | Blob-Storage Unavailable: failed to connect to the blob-storage. |
| GK-TXT-99000 | Server Error: an API call to one of the internal services has failed. |
| GK-VPC-00000 | Generic Error. Contact support and provide all diagnostic code info. |
| GK-VPC-00001 | Invalid request as it contains some invalid parameters. You can see additional fields of the response for invalid parameters and their values. For more information, contact support and provide all diagnostic code info. |
| GK-VPC-00002 | Server is unavailable. One of the internal services is not available. For more information, contact support and provide all diagnostic code info. |
| GK-VPC-00003 | Server API timeout. An API call to one of the internal services has timed out. For more information, contact support and provide all diagnostic code info. |
| GK-VPC-00004 | Server network error. The communication with one of the internal services has failed due to a network error. For more information, contact support and provide all diagnostic code info. |
| GK-VPM-00400 | Invalid Request: the request is invalid as it contains some invalid parameters. |
| GK-VPM-00403 | Unauthorized: the user is unauthorized to perform the requested operation. |
| GK-VPM-00404 | Not Found: the specified entity identifier does not exist. |
| GK-VPM-00409 | Already Exists: the specified entity identifier is already in use. |
| GK-VPM-10000 | Generic Error: an unexpected internal error has occurred. |
| GK-VPM-10499 | Server API Canceled: an API call to one of the internal services has canceled. |
| GK-VPM-10500 | Server Error: an API call to one of the internal services has failed. |
| GK-VPM-10503 | Server is Unavailable: one of the internal services is not available. |
| GK-VPM-10504 | Server API Timeout: an API call to one of the internal services has timed out. |
| GK-VPM-30000 | Database Generic Error: an unexpected error occurred while trying to perform database operation. |
| GK-VPM-30503 | Database Unavailable: failed to connect to the database. |
| GK-VPM-30529 | Database Overloaded: the database cannot handle the incoming request load. |
| GK-VPM-30900 | Database Delete Quota Exceeded: the number of delete requests has exceeded the quota limit. Please try again later. |
| GK-VPM-33000 | Blob-Storage Generic Error: an unexpected error occurred while trying to perform blob-storage operation. |
| GK-VPM-33503 | Blob-Storage Unavailable: failed to connect to the blob-storage. |
| GK-VPM-99000 | Server Error: an API call to one of the internal services has failed. |
| GK-VPP-00000 | Generic Error. Contact support and provide all diagnostic code info. |
| GK-VPP-00001 | Invalid request as it contains some invalid parameters. You can see additional fields of the response for invalid parameters and their values. For more information, contact support and provide all diagnostic code info. |
| GK-VPP-00002 | Server is unavailable. One of the internal services is not available. For more information, contact support and provide all diagnostic code info. |
| GK-VPP-00003 | Server API timeout. An API call to one of the internal services has timed out. For more information, contact support and provide all diagnostic code info. |
| GK-VPP-00004 | Server network error. The communication with one of the internal services has failed due to a network error. For more information, contact support and provide all diagnostic code info. |
| GK-VPP-00100 | Cannot mix incompatible calibration models. Incompatible calibration models are used in the same biometrics request. If the operation involves a watchlist, use the CheckWatchlistCompatibility API to detect the problem. For more information, contact support and provide all diagnostic code info. |
| GK-VPP-00102 | Engine internal error. The error is generated by the engine itself, due to an unexpected condition. These errors require a deep analysis of logs. Contact support and provide all diagnostic code info. |
| GK-VPP-00103 | Print is locked. Unlock or retrain the print to use it again in a verfication. |
| GK-VPP-00104 | Print is not trained. Train the print to use it in a verfication. |
| GK-VPP-00105 | Print was previously deleted, probably because the owner opted out. |
| GK-WAC-00001 | The Web Agent Console is not receiving agent monitoring messages from the server. This may be due to a connectivity issue. Please refresh or try reconnecting. |
| GK-WAC-00002 | The Web Agent Console is not receiving call monitoring messages from the server. This may be due to a connectivity issue. Please refresh or try reconnecting. |
| GK-WEBAPP-10001 | The error you’re experiencing may suggest that the tenant is not registered. Contact Nuance support for assistance. |
| GK-WEBAPP-10002 | The error you’re encountering may indicate an invalid token. Try logging out and back in. If the issue persists, contact Nuance support. |
| GK-WTM-00400 | Invalid Request: the request is invalid as it contains some invalid parameters. |
| GK-WTM-00403 | Unauthorized: the user is unauthorized to perform the requested operation. |
| GK-WTM-00404 | Not Found: the specified entity identifier does not exist. |
| GK-WTM-00409 | Already Exists: the specified entity identifier is already in use. |
| GK-WTM-10000 | Generic Error: an unexpected internal error has occurred. |
| GK-WTM-10499 | Server API Canceled: an API call to one of the internal services has canceled. |
| GK-WTM-10500 | Server Error: an API call to one of the internal services has failed. |
| GK-WTM-10503 | Server is Unavailable: one of the internal services is not available. |
| GK-WTM-10504 | Server API Timeout: an API call to one of the internal services has timed out. |
| GK-WTM-30000 | Database Generic Error: an unexpected error occurred while trying to perform database operation. |
| GK-WTM-30503 | Database Unavailable: failed to connect to the database. |
| GK-WTM-30529 | Database Overloaded: the database cannot handle the incoming request load. |
| GK-WTM-30900 | Database Delete Quota Exceeded: the number of delete requests has exceeded the quota limit. Please try again later. |
| GK-WTM-99000 | Server Error: an API call to one of the internal services has failed. |
| MM-CA-00102 | Invalid Request: The request is invalid because the requested connector information is not valid. |
| MM-CA-00404 | Not Found: The specified entity identifier doesn’t exist. Verify the id sent in the request. |
| MM-CA-00409 | Already Exists: The specified connector already exists. |
| MM-CA-10400 | Invalid Request: The request is invalid as it contains some invalid parameters. Check the returned field violations for more information. For more information, contact support and provide all diagnostic code info. |
| MM-CA-10403 | Unauthorized: The user is unauthorized to perform the requested operation. |
| MM-CA-10404 | Not Found: The specified entity identifier doesn’t exist. Verify the ID sent in the request. For more information, contact support and provide all diagnostic code info. |
| MM-CA-10500 | An unexpected internal error occurred. For more information, contact support and provide all diagnostic code info. |
| MM-CA-10503 | Server is Unavailable: One of the internal services isn’t available. If the problem persists, contact support and provide all diagnostic code info. |
| MM-CA-30000 | There was a problem when trying to find the connector with the specified tenant. |
| MM-CA-30110 | There was a problem when trying to create the connector or the connector config. |
| MM-CA-30120 | There was a problem when trying to create the connector or the connector config. |
| MM-CA-30200 | There was a problem when trying to delete the connector or the connector config. |
| MM-CA-30210 | There was a problem when trying to delete the connector or connector config. |
| MM-CA-30504 | Database Timeout: A call to the database timed out. If the problem persists, contact support and provide all diagnostic code info. |
| MM-CM-00001 | No connector session is available. Verify the health of the CTI connectors in case of login/logout failures or Media connectors in case of recording failures. If recording fails, make sure there is a healthy Media connector on the same datacenter/environment of the RCC connector that is handling the impacted call. |
| MM-CM-00002 | The connector request has timed out. Verify the health of CTI connectors if login/logout fails or Media connectors for recording issues and look for network issues. |
| MM-CM-00003 | The connector command request has returned an exception. Verify the health of CTI connectors if login/logout fails or Media connectors for recording issues and look for network issues. |
| MM-CM-00004 | There was a problem with the event request service. Verify the health of the service. |
| MM-CM-00102 | Invalid Request: The request is invalid because the requested connector information is not valid. |
| MM-CM-00404 | Not Found: The specified entity identifier doesn’t exist. Verify the id sent in the request. |
| MM-CM-00405 | Invalid request: The request received is not valid and some fields might be missing. |
| MM-CM-00501 | Invalid request: The connector address is empty and it is mandatory for OVS connector type. |
| MM-CM-10400 | Invalid Request: The request is invalid as it contains some invalid parameters. Check the returned field violations for more information. For more information, contact support and provide all diagnostic code info. |
| MM-CM-10403 | Unauthorized: The user is unauthorized to perform the requested operation. |
| MM-CM-10404 | Not Found: The recording control connector session was not found. This may indicate the session has expired, was terminated, or an incorrect session ID was provided. Verify the health of the Recording Control Connector (RCC) and ensure the session is active. For more information, contact support and provide all diagnostic code info. |
| MM-CM-10500 | An unexpected internal error occurred. For more information, contact support and provide all diagnostic code info. |
| MM-CM-10503 | Server is Unavailable: One of the internal services isn’t available. If the problem persists, contact support and provide all diagnostic code info. |
| MM-CM-30000 | Database Generic Error: An unexpected error occurred while trying to perform the database operation. If the problem persists, contact support and provide all diagnostic code info. |
| MM-CM-30504 | Database Timeout: A call to the database timed out. If the problem persists, contact support and provide all diagnostic code info. |
| MM-CM-34000 | Redis Connection Error: A connection to the Redis cache could not be established. If the problem persists, contact support and provide all diagnostic code info. |
| MM-CM-34001 | Redis Timeout Error: A Redis operation timed out. If the problem persists, contact support and provide all diagnostic code info. |
| MM-CM-34002 | Redis Command Failed: A Redis command execution failed. If the problem persists, contact support and provide all diagnostic code info. |
| MM-CM-34003 | Redis Serialization Error: An error occurred while serializing or deserializing data for Redis. If the problem persists, contact support and provide all diagnostic code info. |
| MM-ES-00404 | Not Found: The specified event ID doesn’t exist. Verify the ID in the request. |
| MM-ES-10400 | The request contains invalid or missing parameters. Check field violations for details. |
| MM-ES-10403 | Unauthorized: You don’t have permission to perform this operation. |
| MM-ES-10404 | Not Found: The requested event does not exist. |
| MM-ES-10500 | An unexpected internal error occurred. Contact support with diagnostic info. |
| MM-ES-10503 | A dependent internal service is unavailable. Try again later or contact support. |
| MM-ES-30000 | A database error occurred while processing the event request. |
| MM-ES-30504 | Database Timeout: The backend database did not respond in time. |
| MM-ESM-00404 | Not Found: The specified entity identifier doesn’t exist. Verify the id sent in the request. |
| MM-ESM-00500 | The request sent to the connector manager was not successful. |
| MM-ESM-00501 | The request is invalid and could not be completed as the partition is not consumed. |
| MM-ESM-10400 | Invalid Request: The request is invalid as it contains some invalid parameters. Check the returned field violations for more information. For more information, contact support and provide all diagnostic code info. |
| MM-ESM-10403 | Unauthorized: The user is unauthorized to perform the requested operation. |
| MM-ESM-10404 | Not Found: The specified entity identifier doesn’t exist. Verify the ID sent in the request. For more information, contact support and provide all diagnostic code info. |
| MM-ESM-10500 | An unexpected internal error occurred. For more information, contact support and provide all diagnostic code info. |
| MM-ESM-10503 | Server is Unavailable: One of the internal services isn’t available. If the problem persists, contact support and provide all diagnostic code info. |
| MM-ESM-30000 | Database Generic Error: An unexpected error occurred while trying to perform the database operation. If the problem persists, contact support and provide all diagnostic code info. |
| MM-ESM-30504 | Database Timeout: A call to the database timed out. If the problem persists, contact support and provide all diagnostic code info. |
| MM-ESM-34000 | Redis Connection Error: A connection to the Redis cache could not be established. If the problem persists, contact support and provide all diagnostic code info. |
| MM-ESM-34001 | Redis Timeout Error: A Redis operation timed out. If the problem persists, contact support and provide all diagnostic code info. |
| MM-ESM-34002 | Redis Command Failed: A Redis command execution failed. If the problem persists, contact support and provide all diagnostic code info. |
| MM-ESM-34003 | Redis Serialization Error: An error occurred while serializing or deserializing data for Redis. If the problem persists, contact support and provide all diagnostic code info. |
| MM-MH-00000 | StartRecord internal failure. Contact support and provide Media Connector logs. |
| MM-MH-00404 | Not Found: The specified media ID doesn’t exist. Verify the ID in the request. |
| MM-MH-10400 | The request contains invalid or missing parameters. See returned violations for details. |
| MM-MH-10403 | Unauthorized: You don’t have permission to perform this operation. |
| MM-MH-10404 | Not Found: The requested media item doesn’t exist. |
| MM-MH-10500 | An unexpected internal error occurred. Contact support with diagnostic info. |
| MM-MH-10503 | Server is Unavailable: One of the internal services isn’t available. If the problem persists, contact support and provide all diagnostic code info. |
| MM-MH-30000 | A database error occurred while processing the media request. |
| MM-MH-30504 | Database Timeout: A call to the database timed out. If the problem persists, contact support and provide all diagnostic code info. |
| MM-MP-10400 | Invalid Request: The request is missing the required media URN. The media URN uniquely identifies the media resource to be published or retrieved. Ensure that the request includes a valid mediaUrn field before retrying. |
| MM-MP-10403 | Unauthorized: The user is not allowed to publish or modify media content. |
| MM-MP-10404 | Not Found: The specified media item does not exist. |
| MM-MP-10500 | An unexpected internal error occurred. Contact support and provide diagnostic information. |
| MM-MP-10503 | Service Unavailable: A dependent internal media service is down. |
| MM-MP-30000 | A database error occurred while processing the media request. |
| MM-MP-30504 | Database Timeout: The backend database did not respond in time. |
| MM-MP-34000 | Redis Connection Error: A connection to the Redis cache could not be established. If the problem persists, contact support and provide all diagnostic code info. |
| MM-MP-34001 | Redis Timeout Error: A Redis operation timed out. If the problem persists, contact support and provide all diagnostic code info. |
| MM-MP-34002 | Redis Command Failed: A Redis command execution failed. If the problem persists, contact support and provide all diagnostic code info. |
| MM-MP-34003 | Redis Serialization Error: An error occurred while serializing or deserializing data for Redis. If the problem persists, contact support and provide all diagnostic code info. |
| MM-RS-00001 | The CALL_STARTED event is missing from the RCC Connector. Review RCC Connector logs to verify if there was a successful CALL_STARTED request using the correct CallID. If not, investigate why this request was not completed with the correct CallID. Ensure that there was no CALL_ENDED event sent out before or around the time this code was issued. If there was a successful request with the correct CallID and no CALL_ENDED event, contact support and provide all diagnostic code info. |
| MM-RS-00404 | Entity Not Found: A required entity (media, recording, realm, or recording control event) was not found. The ’entityType’ field in the diagnostic extras identifies which entity is missing. Verify that the entity identifier in the request is correct and that the entity has not expired from the cache. For more information, contact support and provide all diagnostic code info. |
| MM-RS-10001 | Invalid Call ID: The call identifier in the StartRecord request contains an invalid (all-zeros) call ID. This typically indicates the CTI gateway did not provide a valid call UUID. Verify the CTI connector configuration and ensure the call ID is being populated correctly by the upstream system. For more information, contact support and provide all diagnostic code info. |
| MM-RS-10400 | Invalid Request: The request is invalid as it contains some invalid parameters. Check the returned field violations for more information. For more information, contact support and provide all diagnostic code info. |
| MM-RS-10403 | Unauthorized: The user is unauthorized to perform the requested operation. |
| MM-RS-10404 | Not Found: The specified entity identifier doesn’t exist. Verify the ID sent in the request. For more information, contact support and provide all diagnostic code info. |
| MM-RS-10410 | Recording Already Stopped: The recording associated with the specified media has already been stopped, either due to reaching the maximum recording length or by an explicit stop request. Verify that the recording is still active before sending Pause or Resume commands. The ‘maxRecordingLengthReached’ field indicates whether the recording was stopped by the max recording length timer. For more information, contact support and provide all diagnostic code info. |
| MM-RS-10500 | An unexpected internal error occurred. For more information, contact support and provide all diagnostic code info. |
| MM-RS-10503 | Server is Unavailable: One of the internal services isn’t available. If the problem persists, contact support and provide all diagnostic code info. |
| MM-RS-30000 | Database Generic Error: An unexpected error occurred while trying to perform the database operation. If the problem persists, contact support and provide all diagnostic code info. |
| MM-RS-30504 | Database Timeout: A call to the database timed out. If the problem persists, contact support and provide all diagnostic code info. |
| MM-RS-34000 | Redis Connection Error: A connection to the Redis cache could not be established. If the problem persists, contact support and provide all diagnostic code info. |
| MM-RS-34001 | Redis Timeout Error: A Redis operation timed out. If the problem persists, contact support and provide all diagnostic code info. |
| MM-RS-34002 | Redis Command Failed: A Redis command execution failed. If the problem persists, contact support and provide all diagnostic code info. |
| MM-RS-34003 | Redis Serialization Error: An error occurred while serializing or deserializing data for Redis. If the problem persists, contact support and provide all diagnostic code info. |
| MM-TM-00100 | Invalid Request: The request is invalid because it contains duplicate parameters. Verify that the configuration sent in the request does not contain duplicates. |
| MM-TM-00101 | Found multiple entities with the same name. Each name should be unique. |
| MM-TM-00102 | Invalid Request: The request is invalid because it uses an entity that doesn’t belong to the requested tenant. |
| MM-TM-00404 | Not Found: The specified entity identifier doesn’t exist. Verify the id sent in the request. |
| MM-TM-00409 | Already Exists: The specified entity ID is already in use. |
| MM-TM-00423 | You can’t delete this entity because other entities use it. Check if the using entities can be deleted, and delete those first. |
| MM-TM-10400 | Invalid Request: The request is invalid as it contains some invalid parameters. Check the returned field violations for more information. For more information, contact support and provide all diagnostic code info. |
| MM-TM-10403 | Unauthorized: The user is unauthorized to perform the requested operation. |
| MM-TM-10404 | Not Found: The specified entity identifier doesn’t exist. Verify the ID sent in the request. For more information, contact support and provide all diagnostic code info. |
| MM-TM-10500 | An unexpected internal error occurred. For more information, contact support and provide all diagnostic code info. |
| MM-TM-10503 | Server is Unavailable: One of the internal services isn’t available. If the problem persists, contact support and provide all diagnostic code info. |
| MM-TM-30000 | Database Generic Error: An unexpected error occurred while trying to perform the database operation. If the problem persists, contact support and provide all diagnostic code info. |
| MM-TM-30504 | Database Timeout: A call to the database timed out. If the problem persists, contact support and provide all diagnostic code info. |
| OC-CTI-10000 | StartMonitor internal failure. Contact support and provide CTI connector logs. |
| OC-CTI-10001 | StartMonitor internal failure. Contact support and provide CTI connector logs. |
| OC-CTI-10002 | StartMonitor failure: No pattern match found for extension. Check connector config to make sure the pattern is configured according to extension needs. This applies to multiAdapterRegexPattern in APPLICATION_MULTI_CTI_LIST. Refer to SOG for more details. |
| OC-CTI-11001 | StartMonitor failure: Failed to register extension since the JTAPI provider is unavailable for server. Check the network to ensure the connector is able to connect to AES, and review the connector configuration to confirm that the credentials to login AES are correct. |
| OC-CTI-11002 | StartMonitor failure: Failed to register extension due to ResourceUnavailableException returned from the platform. Search connector logs for the corresponding commandId to know the detailed reason of the failure. Make sure the extension is configured properly in the platform. |
| OC-CTI-11003 | StartMonitor failure: Failed to register extension due to MethodNotSupportedException returned from the platform. Search connector logs for the corresponding commandId to know the detailed reason of the failure. Platform configuration adjustment may be needed based on the exception message. |
| OC-CTI-11004 | StartMonitor failure: Failed to register extension due to InvalidArgumentException returned from the platform. Search connector logs for the corresponding commandId to know the detailed reason of the failure. Platform configuration adjustment may be needed based on the exception message. |
| OC-CTI-13001 | StartMonitor failure: Failed to register extension since the JTAPI provider is unavailable for server. Check the network to ensure the connector is able to connect to CUCM, and review the connector configuration to confirm that the credentials to login to CUCM are correct. |
| OC-CTI-13002 | StartMonitor failure: Failed to register extension due to ResourceUnavailableException returned from the platform. Search connector logs for the corresponding commandId to know the detailed reason of the failure. Make sure the extension is configured properly in the platform. |
| OC-CTI-13003 | StartMonitor failure: Failed to register extension due to MethodNotSupportedException returned from the platform. Search connector logs for the corresponding commandId to know the detailed reason of the failure. Platform configuration adjustment may be needed based on the exception message. |
| OC-CTI-13004 | StartMonitor failure: Failed to register extension due to InvalidArgumentException returned from the platform. Search connector logs for the corresponding commandId to know the detailed reason of the failure. Platform configuration adjustment may be needed based on the exception message. |
| OC-CTI-15001 | StartMonitor failure: Connection to TServer is not properly initialized. Check the network to make sure the connector is able to connect to TServer. Review and confirm the configuration for TServer/SIP Server, and ensure that the connector can initialize successfully before any agent attempts to log in. |
| OC-CTI-15002 | StartMonitor failure: Invalid extension. Validate if the extension is correct and it exists in the Engage platform. |
| OC-CTI-15003 | StartMonitor failure: ProtocolException returned from the Genesys platform. In connector log, search for commandId that displays the log lines related to the request. Analyze the detailed exception in the log that provides some detailed information. Since it’s a platform-returned exception, check the platform related to this request. |
| OC-CTI-15004 | StartMonitor failure: ChannelClosedOnSendException returned from the Genesys platform. Check the connection between the connector and the platform. Review connector logs and increase log level if more details are needed. Refer to SOG for more details. |
| OC-CTI-15005 | StartMonitor failure: ChannelClosedOnCloseException returned from the Genesys platform. Check the connection between the connector and the platform. Review connector logs and increase log level if more details are needed. Refer to SOG for more details. |
| OC-CTI-15011 | StartMonitor internal failure. Contact support and provide CTI connector logs. |
| OC-CTI-15012 | StartMonitor failure: Unable to find person in the Config server. Validate that the extension/agentId is correct and exists in the Config server configuration. |
| OC-CTI-15013 | StartMonitor failure: Unable to find the agent info in the person record retrieved from the Config server. Validate that the extension/agent Id is correct and exists in the Config server configuration. |
| OC-CTI-15014 | StartMonitor failure: Unable to find place in the agent info of the person record retrieved from the Config server. Validate that the extension/agentId is correctly configured and exists in the Config server configuration. |
| OC-CTI-15015 | StartMonitor failure: Unable to find DN from person record retrieved from the Config server. Validate that the extension/agentId is correctly configured and exists in the Config server configuration. |
| OC-CTI-15016 | StartMonitor failure: ConfigException returned from the platform. In connector log, search for commandId to see the log lines related to the request. Analyze the exception in the log that provides some detailed information. Since it’s a platform-returned exception, check the platform related to this request. |
| OC-CTI-15017 | StartMonitor failure: ProtocolException returned from the platform - Failed to connect to the Engage server. In connector log, search for the commandId to see the log lines related to the request. Analyze the exception in the log that provides some detailed information. Since it’s a platform-returned exception, check the platform related to this request. |
| OC-CTI-15018 | StartMonitor failure: Internal error - Failed to connect to the Engage server. Contact support and provide CTI connector logs. |
| OC-CTI-17001 | StartMonitor internal failure. Contact support and provide CTI connector logs. |
| OC-CTI-17002 | StartMonitor failure: UsersSearchResponse returned empty user list. Invalid UserId/Extension. Review the configuration in the Genesys Cloud platform for this UserID. |
| OC-CTI-17003 | StartMonitor failure: UsersSearchResponse returned an unexpected user list size (expecting 1). In connector log, search for commandId that displays the log lines related to the request. Analyze the detailed exception in the log that provides some detailed information. Review the configuration in the Genesys Cloud platform for this UserID: check if the extension (user email) exists and is valid and available in the Genesys cloud platform. Ensure that the platform has proper configurations for the extension/user, that a single record matches the provided extension (user email) |
| OC-CTI-17004 | StartMonitor failure: UsersSearchResponse returned a user with empty user id. In connector log, search for commandId that displays the log lines related to the request. Analyze the detailed exception in the log that provides some detailed information. Review the configuration in the Genesys Cloud platform for this UserID: check if the extension (user email) exists and is valid and available in the Genesys cloud platform. Ensure that the platform has proper configurations for the extension/user, that a single record matches the provided extension (user email) |
| OC-CTI-17005 | StartMonitor failure: Notification Channel could not be created. Contact support and provide CTI connector logs. |
| OC-CTI-17006 | StartMonitor failure: IOException: Failed to initialize Notifications Channel Listener returned by the Genesys Cloud SDK. In connector log, search for commandId that displays the log lines related to the request. Analyze the detailed exception in the log that provides some detailed information. Since it’s a platform-returned exception, check the platform related to this request. |
| OC-CTI-17007 | StartMonitor failure: APIException: Failed to initialize Notifications Channel Listener returned by the Genesys Cloud SDK. In connector log, search for commandId that displays the log lines related to the request. Analyze the detailed exception in the log that provides some detailed information. Since it’s a platform-returned exception, check the platform related to this request. |
| OC-CTI-17008 | StartMonitor failure: WebSocketException: Failed to initialize Notifications Channel Listener returned by the Genesys Cloud SDK. In connector log, search for commandId that displays the log lines related to the request. Analyze the detailed exception in the log that provides some detailed information. Since it’s a platform-returned exception, check the platform related to this request. |
| OC-CTI-30000 | StopMonitor internal failure. Contact support and provide CTI connector logs. |
| OC-CTI-30001 | StopMonitor internal failure. Contact support and provide CTI connector logs. |
| OC-CTI-30002 | StopMonitor internal failure. Contact support and provide CTI connector logs. |
| OC-CTI-30003 | StopMonitor failure: No pattern match found for extension. Contact support and provide CTI connector logs. |
| OC-CTI-31001 | StopMonitor failure: Internal failure. Contact support and provide CTI connector logs. |
| OC-CTI-31002 | StopMonitor failure: Internal failure. Contact support and provide CTI connector logs. |
| OC-CTI-33001 | StopMonitor failure: Internal failure. Contact support and provide CTI connector logs. |
| OC-CTI-33002 | StopMonitor failure: Internal failure. Contact support and provide CTI connector logs. |
| OC-CTI-35001 | StopMonitor internal failure. Contact support and provide CTI connector logs. |
| OC-CTI-35002 | StopMonitor failure: Connection to TServer is not properly initialized: Protocol is null. Check the network to make sure the connector is able to connect to TServer. Review and confirm the configuration for TServer/SIP Server, and ensure that the connector stays up. If the root cause cannot be found, contact support and provide CTI connector logs. |
| OC-CTI-35003 | StopMonitor failure: ProtocolException returned from Genesys platform. In connector log, search for the commandId to see the log lines related to the request. Analyze the detailed exception in the log that provides some detailed information. Since it’s a platform-returned exception, check the platform related to this request. |
| OC-CTI-35004 | StopMonitor failure: ChannelClosedOnSendException returned from the Genesys platform. Check the connection between the connector and the platform. Review connector logs and increase log level if more details are needed. Refer to SOG for more details. |
| OC-CTI-35005 | StopMonitor failure: ChannelClosedOnCloseException returned from the Genesys platform. Check the connection between the connector and the platform. Review connector logs and increase log level if more details are needed. Refer to SOG for more details. |
| OC-CTI-37001 | StopMonitor internal failure. Contact support and provide CTI connector logs. |
| OC-CTI-37002 | StopMonitor failure: APIException: Failed to unregister extension due to an exception returned by the Genesys Cloud SDK. In connector log, search for commandId that displays the log lines related to the request. Analyze the detailed exception in the log that provides some detailed information. Since it’s a platform-returned exception, check the platform related to this request. |
| OC-CTI-37003 | StopMonitor internal failure. Contact support and provide CTI connector logs. |
| OC-CTI-50000 | UpdataCallData internal failure. This code does not cause any oops screen and is transparent to call center agents. Please ignore this error.. |
| OC-CTI-50001 | UpdataCallData internal failure. This code does not cause any oops screen and is transparent to call center agents. Please ignore this error.. |
| OC-CTI-50002 | UpdataCallData internal failure. This code does not cause any oops screen and is transparent to call center agents. Please ignore this error.. |
| OC-CTI-50003 | UpdataCallData internal failure. This code does not cause any oops screen and is transparent to call center agents. Please ignore this error.. |
| OC-CTI-55001 | UpdataCallData internal failure. This code does not cause any oops screen and is transparent to call center agents. Please ignore this error. |
| OC-CTI-55002 | UpdataCallData internal failure. This code does not cause any oops screen and is transparent to call center agents. Please ignore this error. |
| OC-CTI-55003 | UpdataCallData internal failure. This code does not cause any oops screen and is transparent to call center agents. Please ignore this error. |
| OC-CTI-55004 | UpdataCallData internal failure. This code does not cause any oops screen and is transparent to call center agents. Please ignore this error. |
| OC-CTI-55005 | UpdataCallData internal failure. This code does not cause any oops screen and is transparent to call center agents. Please ignore this error. |
| OC-CTI-55006 | UpdataCallData internal failure. This code does not cause any oops screen and is transparent to call center agents. Please ignore this error. |
| OC-CTI-55007 | UpdataCallData internal failure. This code does not cause any oops screen and is transparent to call center agents. Please ignore this error. |
| OC-CTI-55008 | UpdataCallData internal failure. This code does not cause any oops screen and is transparent to call center agents. Please ignore this error. |
| OC-CTI-57001 | UpdataCallData internal failure. This code does not cause any oops screen and is transparent to call center agents. Please ignore this error. |
| OC-CTI-57002 | UpdataCallData internal failure. This code does not cause any oops screen and is transparent to call center agents. Please ignore this error. |
| OC-CTI-57003 | UpdataCallData internal failure. This code does not cause any oops screen and is transparent to call center agents. Please ignore this error. |
| OC-CTI-57004 | UpdataCallData internal failure. This code does not cause any oops screen and is transparent to call center agents. Please ignore this error. |
| OC-MC-00001 | Connector internal failure. Contact support and provide Media Connector logs. |
| OC-MC-10001 | StartRecord failure. Contact support and provide Media Connector logs. |
| OC-MC-10002 | StartRecord failure: failed to parse media format. Check the SIPREC RCC connector that handled the SIP INVITE and verify that the SDP contained one of the supported media formats: PCMU, PCMA, or G729. If unsure, contact support and provide RCC and Media Connector logs. |
| OC-MC-10003 | StartRecord failure: deadline exceeded while calling Media Manager to create media. Review logs and check the network connection between Media Connector and Gatekeeper/Media Manager. |
| OC-MC-10004 | StartRecord failure. Contact support and provide Media Connector logs. |
| OC-MC-10005 | StartRecord internal failure. Contact support and provide Media Connector logs. |
| OC-MC-10006 | StartRecord internal failure. Contact support and provide Media Connector logs. |
| OC-MC-10007 | StartRecord internal failure. Contact support and provide Media Connector logs. |
| OC-MC-10008 | StartRecord internal failure. Contact support and provide RCC and Media Connector logs. |
| OC-MC-10009 | StartRecord internal failure. Contact support and provide Media Connector logs. |
| OC-MC-10010 | StartRecord failure: No rtp port(s) available to allocate. This means either the call volume is too high or all ports have been allocated and not released promptly enough. If SIP_REINVITE is disabled, makes sure SBC sends a SIP BYE for all sip sessions. Also make sure SIPREC RCC and Media Connector are deployed in a one-to-one model. If SIP_REINVITE is enabled, the call volume may be too high or call duration too long, or a combination of both. If unsure, contact support and provide RCC and Media Connector logs. |
| OC-MC-10011 | StartRecord internal failure. Contact support and provide RCC and Media Connector logs. |
| OC-MC-10012 | StartRecord internal failure. Contact support and provide RCC and Media Connector logs. |
| OC-MC-10013 | StartRecord internal failure. Contact support and provide RCC and Media Connector logs. |
| OC-MC-10014 | StartRecord internal failure. Contact support and provide RCC and Media Connector logs. |
| OC-MC-10017 | StartRecord failure: deadline exceeded while calling RCC. Review logs and check the network connection between Media Connector and the target RCC. Check RCC log and verify if the RCC received the request and confirm if it took too long to respond. If unsure, open a support ticket and attach connector logs. |
| OC-MC-10018 | StartRecord internal failure. Contact support and provide RCC and Media Connector logs. |
| OC-MC-10019 | StartRecord internal failure. Contact support and provide RCC and Media Connector logs. |
| OC-MC-10020 | StartRecord internal failure. Contact support and provide RCC and Media Connector logs. |
| OC-MC-10021 | StartRecord internal failure. Contact support and provide Media Connector logs. |
| OC-MC-10022 | StartRecord internal failure. Contact support and provide Media Connector logs. |
| OC-MC-10023 | StartRecord internal failure. Contact support and provide Media Connector logs. |
| OC-MC-10024 | StartRecord internal failure. Contact support and provide Media Connector logs. |
| OC-MC-10025 | StartRecord failure to get cypher information from RCC. Check network and connector settings and make sure Media Conenctor can reach RCC. Contact support and provide RCC and Media Connector logs. |
| OC-MC-10026 | StartRecord failure to get cypher information from RCC. Check network and connector settings and make sure Media Conenctor can reach RCC. Contact support and provide RCC and Media Connector logs. |
| OC-MC-10027 | StartRecord internal failure. Contact support and provide RCC and Media Connector logs. |
| OC-MC-10028 | StartRecord internal failure. Contact support and provide RCC and Media Connector logs. |
| OC-MC-10029 | StartRecord internal failure. Contact support and provide RCC and Media Connector logs. |
| OC-MC-10030 | StartRecord internal failure. Contact support and provide RCC and Media Connector logs. |
| OC-MC-10031 | StartRecord internal failure. Contact support and provide RCC and Media Connector logs. |
| OC-MC-10032 | StartRecord internal failure. Contact support and provide RCC and Media Connector logs. |
| OC-MC-30001 | PauseRecord failure: no active recording found for recordingId. This may be due to the connector restarting and clearing its cache. It may also be due to very long recorfings that reached the maximum. Review the logs, and if unsure, contact support and Media Connector logs. |
| OC-MC-30002 | PauseRecord internal failure. Contact support and provide RCC and Media Connector logs. |
| OC-MC-30003 | PauseRecord internal failure. Contact support and provide RCC and Media Connector logs. |
| OC-MC-50001 | ResumeRecord failure: no active recording found for recordingId. This may be due to the connector restarting and clearing its cache. It may also be due to very long recorfings that reached the maximum. Review the logs, and if unsure, contact support and Media Connector logs. |
| OC-MC-50002 | ResumeRecord internal failure. Contact support and provide RCC and Media Connector logs. |
| OC-MC-50003 | ResumeRecord internal failure. Contact support and provide Media Connector logs. |
| OC-MC-50004 | ResumeRecord failure: deadline exceeded while calling RCC. Review logs and check the network connection between Media Connector and the target RCC. Check RCC log and verify if the RCC received the request and confirm if it took too long to respond. If unsure, open a support ticket and attach connector logs. |
| OC-MC-50005 | ResumeRecord internal failure. Contact support and provide RCC and Media Connector logs. |
| OC-MC-50006 | ResumeRecord internal failure. Contact support and provide RCC and Media Connector logs. |
| OC-MC-50007 | ResumeRecord internal failure. Contact support and provide RCC and Media Connector logs. |
| OC-MC-70001 | StopRecord failure: no active recording found for recordingId. This may be due to the connector restarting and clearing its cache. It may also be due to very long recorfings that reached the maximum. Review the logs, and if unsure, contact support and Media Connector logs. |
| OC-MC-70002 | StopRecord internal failure. Contact support and provide Media Connector logs. |
| OC-MC-70003 | StopRecord internal failure. Contact support and provide RCC and Media Connector logs. |
| OC-MC-90001 | Failed to stream media: no RTP received from SBC. Check in SIPREC RCC connector log to see what is inside the SIPREC SDP for the recording type. Also check why RTP is not sent to Media Connector. Could be due to a network issue or an incorrect configuratio in the SBC. If needed, contact support and provide RCC and Media Connector logs. |
| OC-MC-90002 | Failed to stream media: failed to detect RTP type. Check in SIPREC RCC connector log to see what is inside the SIPREC SDP for the recording type. Also validate and confirm that the RTP is in the expected format. If needed, contact support and provide RCC and Media Connector logs. |
| OC-MC-90003 | Failed to stream media internal failure. Contact support and provide RCC and Media Connector logs. |
| OC-MC-90004 | Failed to stream media: RecordingSrtpException - SRTP Unprotect failure. Check in SIPREC RCC connector log the info related to SRTP crypto key and capture tcpdump to validate that the data contains only SRTP packets. Also ensure that the SRTP can be decrypted with the crypto key seen in SIPREC invite. Ensure that during recording no crypto key is changed. If needed, contact support and provide RCC and Media Connector logs. |
| OC-MC-90005 | Failed to stream media internal failure. Contact support and provide RCC and Media Connector logs. |
| OC-RCC-00000 | StartRecord internal failure. Contact support and provide RCC and Media Connector logs. |
| OC-RCC-00001 | Connector internal failure. Contact support and provide RCC connector logs. |
| OC-RCC-00002 | Connector internal failure. Contact support and provide RCC connector logs. |
| OC-RCC-01001 | Connector unable to distinguish between multiple SIP callIDs mapped to same UCID. Contact support and provide RCC connector logs. |
| OC-RCC-01009 | StartRecord failure: Missing media flow attribute in SIPREC INVITE. Review SBC settings to provide a valid media flow attribute (a=sendonly) in the SIP INVITE SDP section. |
| OC-RCC-01010 | StartRecord failure: Invalid media format specified in SIPREC INVITE. Review SBC settings to provide in the SIPREC INVITE’s SDP section a valid media format: RTP, SAVPRTP, or AVP. |
| OC-RCC-01011 | Connector internal failure. Contact support and provide RCC connector logs. |
| OC-RCC-01014 | StartRecord failure: Failed to receive SIP ACK in time. Check if there are network delays and ensure SIP ACK is sent by SBC to RCC within 5 seconds. |
| OC-RCC-01015 | Connector internal failure. Contact support and provide RCC connector logs. |
| OC-RCC-01018 | Connector internal failure. Contact support and provide RCC connector logs. |
| OC-RCC-01019 | Deadline exceeded while waiting for SIP OK/ACCEPTED. Check if there are network delays and ensure SIP OK is sent by SBC to RCC within 5 seconds. |
| OC-RCC-01023 | Connector internal failure. Contact support and provide RCC connector logs. |
| OC-RCC-01024 | Connector internal failure. Contact support and provide RCC connector logs. |
| OC-RCC-03000 | Unknown Operation Type, Unknown recording operation type detected. Contact support and provide RCC connector logs. |
| OC-RCC-03001 | Failed to build the ovs flow, incorrect recording side is received. Contact support and provide RCC connector logs. |
| OC-RCC-03002 | Failed to build the ovs flow, incorrect flow control info is configured. Please review connector configuration. |
| OC-RCC-03003 | Failed to modify the ovs flow, as no existing flow can be found for the request. Contact support and provide RCC connector logs. |
| OC-RCC-03004 | Failed to process the request. No ovs bridge can be found. Contact support and provide RCC connector logs. |
| OC-RCC-03005 | Failed to verify the open flow with ovs server. Contact support and provide RCC connector logs. |
| OC-RCC-03006 | Failed to find the added ovs flow. Contact support and provide RCC connector logs. |
| OC-RCC-03007 | Failed to send flow stats. Contact support and provide RCC connector logs. |
| OC-RCC-10000 | StartRecord internal failure. Contact support and provide RCC connector logs. |
| OC-RCC-10001 | StartRecord internal failure. Contact support and provide RCC connector logs. |
| OC-RCC-10002 | StartRecord internal failure. Contact support and provide RCC connector logs. |
| OC-RCC-11000 | StartRecord failure. Contact support and provide RCC connector logs. |
| OC-RCC-11001 | StartRecord failure: The connector could not find a matching SIP session (based on the recordingIdentifier). Check the connector logs to ensure that a SIP INVITE is received for this ``recordingIdentifier` and that the parsing is successful. |
| OC-RCC-11002 | StartRecord failure. Contact support and provide RCC connector logs. |
| OC-RCC-11003 | StartRecord failure. Contact support and provide RCC connector logs. |
| OC-RCC-11004 | StartRecord failure: Side one party not found. Check connector logs and ensure the SIP INVITE’s SDP/XML contains valid info to locate the mentioned SIP party. |
| OC-RCC-11005 | StartRecord failure: Side two party not found. Check connector logs and ensure the SIP INVITE’s SDP/XML contains valid info to locate the mentioned SIP party. |
| OC-RCC-11006 | StartRecord failure: Side one party not found. Check connector logs and ensure the SIP INVITE’s SDP/XML contains valid info to locate the mentioned SIP party. |
| OC-RCC-11007 | StartRecord failure: Side two party not found. Check connector logs and ensure the SIP INVITE’s SDP/XML contains valid info to locate the mentioned SIP party. |
| OC-RCC-11008 | StartRecord failure: Side one party not found. Check connector logs and ensure the SIP INVITE’s SDP/XML contains valid info to locate the mentioned SIP party. |
| OC-RCC-11009 | StartRecord failure: Side two party not found. Check connector logs and ensure the SIP INVITE’s SDP/XML contains valid info to locate the mentioned SIP party. |
| OC-RCC-13000 | Failed to start recording due to unknown error. Contact support and provide RCC connector logs. |
| OC-RCC-13001 | Failed to start recording due to missing agent ip info in the request. Contact support and provide RCC connector logs. |
| OC-RCC-13002 | Failed to start recording due to missing gateway ip info in the request. Contact support and provide RCC connector logs. |
| OC-RCC-13003 | Failed to start recording due to missing either agent ip or gateway ip info in the request. Contact support and provide RCC connector logs. |
| OC-RCC-13004 | Failed to start recording due to unexpected ovs controller state. Contact support and provide RCC connector logs. |
| OC-RCC-13005 | Failed to start recording due to failure building ovs flow - missing port description from switch. Contact support and provide RCC connector logs. |
| OC-RCC-30000 | PauseRecord internal failure. Contact support and provide RCC connector logs. |
| OC-RCC-30001 | PauseRecord internal failure. Contact support and provide RCC connector logs. |
| OC-RCC-30002 | PauseRecord internal failure. Contact support and provide RCC connector logs. |
| OC-RCC-30003 | PauseRecord internal failure. Contact support and provide RCC connector logs. |
| OC-RCC-31000 | PauseRecord failure. Contact support and provide RCC connector logs. |
| OC-RCC-31001 | PauseRecord failure: Failed to find the SIP session based on recordingIdentifier. Check logs to see if there are SIP parsing issues due to unparsable SIP INVITE. Also check if a SIP BYE was already received. |
| OC-RCC-31002 | PauseRecord failure. Contact support and provide RCC connector logs. |
| OC-RCC-33000 | Failed to pause recording due to unknown error. Contact support and provide RCC connector logs. |
| OC-RCC-33001 | Failed to pause recording due to missing agent ip info in the request. Contact support and provide RCC connector logs. |
| OC-RCC-33002 | Failed to pause recording due to missing gateway ip info in the request. Contact support and provide RCC connector logs. |
| OC-RCC-33003 | Failed to pause recording due to missing either agent ip or gateway ip info in the request. Contact support and provide RCC connector logs. |
| OC-RCC-33004 | Failed to pause recording due to unexpected ovs controller state. Contact support and provide RCC connector logs. |
| OC-RCC-33005 | Failed to pause recording due to failure building ovs flow - missing port description from switch. Contact support and provide RCC connector logs. |
| OC-RCC-50000 | ResumeRecord internal failure. Contact support and provide RCC connector logs. |
| OC-RCC-50001 | ResumeRecord internal failure. Contact support and provide RCC connector logs. |
| OC-RCC-50002 | ResumeRecord internal failure. Contact support and provide RCC connector logs. |
| OC-RCC-50003 | ResumeRecord internal failure. Contact support and provide RCC connector logs. |
| OC-RCC-51000 | ResumeRecord failure. Contact support and provide RCC connector logs. |
| OC-RCC-51001 | ResumeRecord failure: Failed to find the SIP session based on recordingIdentifier. Check logs to see if there are SIP parsing issues due to unparsable SIP INVITE. Also check if a SIP BYE was already received earlier. |
| OC-RCC-51002 | ResumeRecord failure. Contact support and provide RCC connector logs. |
| OC-RCC-53000 | Failed to resume recording due to unknown error. Contact support and provide RCC connector logs. |
| OC-RCC-53001 | Failed to resume recording due to missing agent ip info in the request. Contact support and provide RCC connector logs. |
| OC-RCC-53002 | Failed to resume recording due to missing gateway ip info in the request. Contact support and provide RCC connector logs. |
| OC-RCC-53003 | Failed to resume recording due to missing either agent ip or gateway ip info in the request. Contact support and provide RCC connector logs. |
| OC-RCC-53004 | Failed to resume recording due to unexpected ovs controller state. Contact support and provide RCC connector logs. |
| OC-RCC-53005 | Failed to resume recording due to failure building ovs flow - missing port description from switch. Contact support and provide RCC connector logs. |
| OC-RCC-53006 | Failed to resume recording as flow is already cleared. Contact support and provide RCC connector logs. |
| OC-RCC-70000 | StopRecord internal failure. Contact support and provide RCC connector logs. |
| OC-RCC-70001 | StopRecord internal failure. Contact support and provide RCC connector logs. |
| OC-RCC-70002 | StopRecord internal failure. Contact support and provide RCC connector logs. |
| OC-RCC-71000 | StopRecord failure. Contact support and provide RCC connector logs. |
| OC-RCC-71001 | StopRecord failure: Failed to find the SIP session based on recordingIdentifier. Check logs to see if there are SIP parsing issues due to unparsable SIP INVITE. Also check if a SIP BYE was already received earlier. |
| OC-RCC-71002 | StopRecord failure. Contact support and provide RCC connector logs. |
| OC-RCC-73000 | Failed to stop recording due to unknown error. Contact support and provide RCC connector logs. |
| OC-RCC-73001 | Failed to stop recording due to unexpected ovs controller state. Contact support and provide RCC connector logs. |
| OC-RCC-73002 | Failed to stop recording due to failure building ovs flow - missing port description from switch. Contact support and provide RCC connector logs. |
| OC-RCC-90000 | GetSrtpCipher internal failure. Contact support and provide RCC connector logs. |
| OC-RCC-90001 | GetSrtpCipher internal failure. Contact support and provide RCC connector logs. |
| OC-RCC-91000 | GetSrtpCipher failure. Contact support and provide RCC connector logs. |
| OC-RCC-91001 | GetSrtpCipher failure: Failed to find the SIP session based on recordingIdentifier. Check logs to see if there are SIP parsing issues due to unparsable SIP INVITE. Also check if a SIP BYE was already received earlier. |
| OC-RCC-91002 | GetSrtpCipher failure. Contact support and provide RCC connector logs. |