Error Code Reference
Response Code |
Result Code |
Description |
Handling Method |
---|---|---|---|
200 |
0 |
success |
No handling is required. |
200 |
0300001 |
The value of {param} cannot be null. |
Check whether the parameter value in the request string is an empty string. |
200 |
0300002 |
The value of {param} cannot be an empty string. |
Check whether the parameter value in the request string is an empty string. |
200 |
0300003 |
The length of {param} is too long. |
Check whether the parameter value is greater than the maximum length specified in the document. |
200 |
0300004 |
The format of {param} is incorrect. |
Check whether the parameter complies with the format described in the document. |
200 |
0300005 |
The length of {param} is too short. |
Check whether the parameter value is less than the maximum length specified in the document. |
200 |
0300006 |
The value of version is error, current version is {param} . |
Check whether the version number parameter is correct. |
200 |
0300007 |
The params of requestBody is null. |
Check whether the parameter length is matched. |
200 |
0300008 |
Reached the download flow control threshold. |
The maximum number of download requests that can be processed by the system is reached. Try again later. |
200 |
0300009 |
Reached the query flow control threshold. |
The maximum number of query requests that can be processed by the system is reached. Try again later. |
200 |
0300010 |
The date in the value of fileName is in an incorrect format. |
Check whether the file name in the request string is valid. The file name format is /{Node ID}/{Call center ID}/record/{App ID}/{Account ID}/{yyyymmdd}/{Agent ID}/{Original file name}.{File name extension}. Check whether {yyyymmdd} is correct. |
200 |
0300011 |
The file does not exist. |
The requested file does not exist. Check whether the requested file is correct. |
200 |
0300012 |
No data found. |
Check whether the value of fileName is correct. The file name format is as follows: {Drive letter}:/{VDN ID}/{0 (inbound call) or 1 (outbound call)}/{Date}/{Agent ID}/{Current time, in milliseconds}.V3 |
200 |
0300013 |
The beginTime cannot be later than the endTime. |
Check the values of beginTime and endTime in the request. |
200 |
0300014 |
The maximum duration between the beginTime and endTime is {param} days. |
Check whether the time range specified by beginTime and endTime in the request string is valid. The maximum time range is 3 days by default. |
200 |
0300015 |
The local storage or voice path does not exist. |
The following configuration items in the configuration file must be properly set: ccfs.common.local.store.path ccfs.common.local.voice.path |
200 |
0300016 |
The value of {param} is greater than current time. |
Check the query interval. |
200 |
0300017 |
Specify ccId. |
Multiple data records are found. The ccId parameter needs to be specified for more accurate query. |
200 |
0300018 |
This record belongs to another developer. |
The developer information in the recording to be queried does not match the developer information in the request. Check whether the value of appId is correct. |
200 |
0300019 |
Specify at least one of fileName and callId. |
Check whether fileName or callId is set. |
200 |
0300020 |
Only one record is required but multiple records are obtained. |
Multiple records are found based on the search criteria. However, only one record is required. Contact the administrator. |
200 |
0300021 |
The {param} in fileName does not match the {param} in the directory. |
Check whether the file name in the request string is valid. The file name format is /{Node ID}/{Call center ID}/record/{App ID}/{Account ID}/{yyyymmdd}/{Agent ID}/{Original file name}.{File name extension}. Check whether {App ID}, record, and {Node ID} are correct. |
200 |
0300022 |
The parameter {param} value contains illegal characters. |
The value of the request parameter contains invalid special characters. Examples are as follows: The value of billFileName in the interface for downloading CDRs and recording indexes can contain only letters, digits, periods (.), hyphens (-), and underscores (_). The value of fileName in the interface for downloading recording files can contain only letters, digits, slashes (/), and periods (.). The value of fileName in the interface for downloading STT files can contain only letters, digits, slashes (/), and periods (.). The value of fileName in the interface for querying and downloading recording files can contain only letters, digits, colons (:), slashes (/), and periods (.) |
200 |
0300023 |
The file name does not match the path configured in the configuration file. |
During the download of IVR voice messages, the directory after the VDN ID in the path specified by the request parameter fileName does not match the value of the system parameter Directory next to vdnId in IVR message recording files. Set the system parameter to a proper file path. |
200 |
0300024 |
The file path is not canonical path. |
Check whether the path is a standard path. |
200 |
0300025 |
Internal system error. |
Contact the administrator. |
200 |
0300026 |
Authentication failed. |
Check whether the account ID or VDN ID is correct. |
200 |
0300027 |
Parameter {param} is empty. |
Check whether the parameter value is empty or an empty string. |
200 |
0300028 |
Parameter {param} is error. |
Check whether the parameter meets the requirements described in the document. |
200 |
0300029 |
File does not exist. |
Check whether the value of fileName is correct. The file requested by the interfaces for requesting and playing back recording files does not exist. |
200 |
0300030 |
Failure of system processing. |
Contact the administrator. |
200 |
0300031 |
Invalid oiap fileName, fileName Length is not legal. |
Check the value length of fileName. |
200 |
0300032 |
file path is invalid. |
Check whether the file path is valid. |
200 |
0300033 |
locationId is empty |
Check whether the parameter value is empty or an empty string. |
200 |
0300034 |
tenantId is empty |
Check whether the parameter value is empty or an empty string. |
200 |
0300035 |
audio file type should be wav. |
Check the file format. Only audio files in WAV format are supported. |
200 |
0300036 |
audio file channel should be mono. |
Check the audio file channel. |
200 |
0300037 |
audio file fileSampleSizeInBits should be 8000Hz. |
Check the number of frames in a file. |
200 |
0300038 |
audio file fileSampleRate should be 8000Hz. |
Check the audio file sampling rate. |
200 |
0300039 |
Failed to read the audio file format. |
Check whether the uploaded audio file format meets requirements. |
200 |
0300040 |
An exception occurred during file deletion. |
Check whether the file permission is correct. |
200 |
0300041 |
The file size exceeds the limit. |
Check the file size. |
200 |
0300042 |
file path config miss parameter %VDNNO% |
Add the VDNNO variable to the path rule configuration item. |
200 |
0300043 |
file path configuration should refer to the example. |
Check the path content configuration item. |
200 |
0300044 |
The directory contains multiple files. |
Check whether the folder contains only one WAV file. |
200 |
0300045 |
Failed to compress the recording files. |
Check whether the recording files exist. |
200 |
0300046 |
The mount path corresponding to the drive letter does not exist. |
Check the file path. |
200 |
0300047 |
Upload file to OBS/LSS failed |
Check whether the OBS/LSS service is normal. |
200 |
0300048 |
In CTI pool mode,the value of ccfs.uap.id cannot be empty |
Check whether the value of ccfs.uap.id in the /home/ccfsapp/webapps/ccfsapp/WEB-INF/classes/config/servicecloud.base.properties configuration file is empty. |
200 |
0300049 |
In CTI pool mode,the value format of ccfs.uap.id is incorrect |
Check whether the value format of ccfs.uap.id in the /home/ccfsapp/webapps/ccfsapp/WEB-INF/classes/config/servicecloud.base.properties configuration file is correct. The value format is {Mount directory},{UAP node ID}. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot