Purpose ............................................................................................... 1 Exceptions Table ................................................................................ 2 Sub Errors ........................................................................................... 6 Screen Logger Sub-errors .................................................................... 6 CTI Service Observation Universal Failures (1100 - 1199) ......... 7 CTI Stream Immediate failures (1200 - 1299)............................... 12 CTI Service Observation Fail Event Reasons (1300 - 1399) ..... 12 Voice Logger Interface Failures (1400 - 1499) .............................. 14 Nortel System Observe Failures (1500 - 1599): .......................... 15
Purpose
This document contains extended information about all the exception codes that may appear in the Status field of a reported call. It gives the description, the common reasons that may lead to a specific exception, and suggests actions that should be taken. The possible causes do not necessarily contain all possible causes for each exception and other problem might also occur.
NOTE The calls database table has place for just ONE exception code for each record in the table, therefore if several problems had happened only one exception will appear.
EMEA Region/APAC Region: (Europe, Middle East, Asia, Pacific Asia) tel: +972.9.775.3800 fax: +972.9.775.3000 email: support@nice.com Americas Region: tel: 1.800.NICE.611 fax: +604.207.0607 email: support.americas@nice.com Israel: tel: 09.775.3333 fax: 09.775.3000 email: support_helpdesk@nice.com Information herein is proprietary information and trade secrets of NICE Systems Ltd. NICE Systems 2002. All rights reserved. 1 of 15
Exceptions Table
Exceptions Table
The following table contains for each exception its meaning, possible causes and recommended actions to be taken. For exceptions 12 and 14, Sub-error codes may appear. In order to understand the sub error meanings See Sub Errors on page 6.
Excep #
Exception meaning Duplicate start call another call with the same call key has started while this call was open. Call too long - The call was open for more seconds then the value of the registry parameter op_MaxOpenCallDuration and therefore was force closed. Call flushed a Flush command was commited while the call was open. NA End call without start
Recommended Action
1.
2.
The call was really longer then the parameters value. Or there is a problem with the drivers or the PABXs reports.
See if the value of op_MaxOpenCallDuration suits the length of calls in the site.
3.
4. 5.
Problem in the drivers or the PABXs reports. Could be followed by reports with exp2 because the start and end call report has different information
6. 7.
NA No available input channel There are not enough voice recording channels to meet the amount of recording requests in the site. Could be caused because of unclosed recorded calls check for exp2 calls. Problem with logger or connection to logger. Check logger.
8. 9.
2 of 15 TN0325_Exceptions.fm
Exceptions Table
Excep #
Exception meaning Agent logout during the call. Too many open calls for the same agent/ext according to the op_MaxCallPerExt registry parameter. Voice recording failed
Possible causes Problem in the drivers or the PABXs call or logout reports. The agent had more simultaneousl open segments than the parameter value. Could be a problem in the drivers or the PABXs call reports. If appears as e12 check the sub exception ID for more information (see sub-exceptions list below).
Recommended Action Check if it is physically possible to logout during a call. See if the parameter value meets the requirements of the site. Look for calls with exp2 to see if there is a problem with the calls reports.
10.
11.
12.
13. 14.
Screen logger not responding Screen recording failed If appears as e14 check the sub exception ID for more information (see sub-exceptions list below). Problem in the voice channel configuration.
15.
Check channels configuration. See if the there is mapping configured for this call. If the allocation mode is by IP address then check if the agent logged in. Check logger for possible reasons for temporary failures. Check reason for call server failure.
16.
The recording request was received with empty Station or IP address (depends on the screen allocation mode).
17.
Recording voice succeed only after retry Callsrvr was down during the call Cls Call Id was changed during the call Redundancy fail over.
18. 19.
3 of 15 TN0325_Exceptions.fm
Exceptions Table
Excep #
Exception meaning The logger didnt answer to the start record command
Possible causes Stop record command arrived before a response for the start record request arrived 1. If the call was very short (1, 2 sec) it is probable for this to happen. 2. If not it is possible that the following scenario happened:The request was for 2 medias. Success in both was required (usually QA). One media failed immediately. Stop record is sent for both medias.
Recommended Action If scenario 2 happened try to understand what was the recording problem with the first media.
20.
NA NA Stop record without start. 1.Could be like scenario 2 in exp20. One media failed and the stop command got to the second media before the start. 2.Could be internal problem. Same as 23. If scenario 1 happened, try to see what caused the recording failure.
24.
Stop record with wrong ID. No start call request with this Cls Call Id was found. Too many recording requests for the same logger and channel (More than 30). Chansrvr was down during the call The contact started after its segment No available recording resource. The Resource Management cant allocate more resources for this initiator. Segment was open when the contact closed.
Same as 23.
25.
Could occur due to Problem in the drivers or the PABXs call reports calls are not closed. Check for Chansrvr going down reason. Problem in the drivers or the PABXs call or logout reports. 1. Bad resource management configuration. 2. Maybe there is a problem with calls that are not closed and therefore resources are not being freed up. Could be a problem with the drivers or the PABXs reports. 1. See if the configuration meets the site needs. If not change it. 2. Could be a problem with the drivers or the PABXs reports.
29.
4 of 15 TN0325_Exceptions.fm
Exceptions Table
Excep #
Exception meaning Block dummy call was closed due to Callsrvr restart. Client was disconnected during the open block. In slow observe mode, a call with recording request was started, but the observe didnt succeed yet.
Possible causes
Recommended Action Check why Callsrvr was closed. Check why the client disconnected.
30.
31. 32.
The call was started, shortly after the recording request arrived to the CLS server.
If the possible cause happened, its OK. Otherwise check why the observe takes so long.
5 of 15 TN0325_Exceptions.fm
Sub Errors
Sub Errors
NOTE For Exceptions 12 and 14 there are also sub error numbers
CLS_SCREEN_LOGGER_AGENT_IS_ALREADY_RECORD ED = 1006, CLS_SCREEN_TOKEN_NOT_RECORD = 1007, CLS_SCREEN_LOGGER_ILEGAL_PARAMS = 1008, CLS_SCREEN_LOGGER_AGENT_UNKNOWN = 1009, CLS_SCREEN_LOGGER_TOKEN_DOES_NOT_EXIST = 1010, CLS_SCREEN_LOGGER_DATABASE_FULL = 1011, LS_SCREEN_LOGGER_OVERLOADED = 1012, CLS_SCREEN_LOGGER_TOKEN_IS_PLAYED = 1013,
6 of 15 TN0325_Exceptions.fm
Sub Errors
7 of 15 TN0325_Exceptions.fm
Sub Errors
Sub-error string CLS_OBSERV_UNIV_FAIL_INVALID_ALLOCATION_STATE = 1116, CLS_OBSERV_UNIV_FAIL_INVALID_CROSS_REF_ID = 1117, CLS_OBSERV_UNIV_FAIL_INVALID_OBJECT_TYPE = 1118, CLS_OBSERV_UNIV_FAIL_SECURITY_VIOLATION = 1119, CLS_OBSERV_UNIV_FAIL_GENERIC_STATE_INCOMPATI BILITY = 1121, CLS_OBSERV_UNIV_FAIL_INVALID_OBJECT_STATE = 1122, CLS_OBSERV_UNIV_FAIL_INVALID_CONNECTION_ID_FO R_ACTIVE_CALL = 1123, CLS_OBSERV_UNIV_FAIL_NO_ACTIVE_CALL = 1124, CLS_OBSERV_UNIV_FAIL_NO_HELD_CALL = 1125, CLS_OBSERV_UNIV_FAIL_NO_CALL_TO_CLEAR = 1126, CLS_OBSERV_UNIV_FAIL_NO_CONNECTION_TO_ CLEAR = 1127, CLS_OBSERV_UNIV_FAIL_NO_CALL_TO_ANSWER = 1128, CLS_OBSERV_UNIV_FAIL_NO_CALL_TO_COMPLETE = 1129, CLS_OBSERV_UNIV_FAIL_GENERIC_SYSTEM_ RESOURCE_AVAILABILITY = 1131, CLS_OBSERV_UNIV_FAIL_SERVICE_BUSY = 1132, CLS_OBSERV_UNIV_FAIL_RESOURCE_BUSY = 1133, CLS_OBSERV_UNIV_FAIL_RESOURCE_OUT_OF_ SERVICE = 1134, CLS_OBSERV_UNIV_FAIL_NETWORK_BUSY = 1135,
Description the service request specified an allocation condition that is invalid the service request specified a cross reference ID that is invalid the service request specified an object type that is outside the request violates a security requirement server has detected a state incompatibility error the object is in an incorrect state for the service the connection identifier specified in the active call parameter is not valid the call is not in the active state the call is not in the held state there is no call associated with the CSTA connection identifier the specified CSTA connection identifier does not exist there is no call for the CSTA connection identifier specified there is no call for the CSTA connection identifier specified system resource error that is not one of the defined errors the service is supported by the server, but is temporarily busy an internal resource is busy the service requires a resource that is out of service the server sub-domain is busy
8 of 15 TN0325_Exceptions.fm
Sub Errors
Sub-error string CLS_OBSERV_UNIV_FAIL_NETWORK_OUT_OF_ SERVICE = 1136, CLS_OBSERV_UNIV_FAIL_OVERALL_MONITOR_LIMIT_ EXCEEDED = 1137, CLS_OBSERV_UNIV_FAIL_CONFERENCE_MEMBER_ LIMIT_EXCEEDED = 1138,
Description the server sub-domain is out of service the request will exceed the server's overall limit on the number of monitors the request will exceed the server's overall limit on the number of members of a conference subscribed resource availability error the request would exceed the server's limit on the number of monitors for the specified object the limit on the number of external trunks would be exceeded by this request the limit on the number of outstanding requests would be exceeded by this request the server has detected a performance management error a performance limit has been exceeded the server has detected a security error the server has detected an error in the sequence number of the operation the server has detected an error in the time stamp of the operation the server has detected an error in the PAC of the operation the server has detected an error in the seal of the operation
9 of 15
CLS_OBSERV_UNIV_FAIL_EXTERNAL_TRUNK_LIMIT_ EXCEEDED = 1143, CLS_OBSERV_UNIV_FAIL_OUTSTANDING_REQUEST_ LIMIT_EXCEEDED = 1144, CLS_OBSERV_UNIV_FAIL_GENERIC_PERFORMANCE_ MANAGEMENT = 1151, CLS_OBSERV_UNIV_FAIL_PERFORMANCE_LIMIT_ EXCEEDED = 1152, CLS_OBSERV_UNIV_FAIL_UNSPECIFIED_SECURITY_ ERROR = 1160, CLS_OBSERV_UNIV_FAIL_SEQUENCE_NUMBER_ VIOLATED = 1161, CLS_OBSERV_UNIV_FAIL_TIME_STAMP_VIOLATED = 1162, CLS_OBSERV_UNIV_FAIL_PAC_VIOLATED = 1163,
CLS_OBSERV_UNIV_FAIL_SEAL_VIOLATED = 1164,
TN0325_Exceptions.fm
Sub Errors
Sub-error string CLS_OBSERV_UNIV_FAIL_GENERIC_UNSPECIFIED_ REJECTION = 1170, CLS_OBSERV_UNIV_FAIL_GENERIC_OPERATION_ REJECTION = 1171, CLS_OBSERV_UNIV_FAIL_DUPLICATE_INVOCATION_ REJECTION = 1172, CLS_OBSERV_UNIV_FAIL_UNRECOGNIZED_OPERATION _REJECTION = 1173, CLS_OBSERV_UNIV_FAIL_MISTYPED_ARGUMENT_ REJECTION = 1174, CLS_OBSERV_UNIV_FAIL_RESOURCE_LIMITATION_ REJECTION = 1175,
Description this is a PBX Driver internal error, report this error to the PBX driver Vendor this is a PBX Driver internal error, report this error to the PBX driver Vendor the invoke ID in the service request is being used by another outstanding request the service request from a client application is not defined in the API mistyped argument rejection the system lacks internal resources such as the memory or data records to process a service request an acsOpenStream session is terminating the link between the Telephony Server and the PBX is shutting down the PBX Driver did not receive the response of a service request sent to the PBX in the allocated time CSTA requests exceeded PBX device processing queue limit the type of the APDU is not one of the four defined by recommendation the structure of the APDU does not conform to recommendation the structure of the APDU does not conform to recommendation
10 of 15 TN0325_Exceptions.fm
Sub Errors
Description the association-initiator is about to attempt to release the application-association there is no operation in progress with and Invoke-ID equal to the specified LinkedID the invoked operation, referred to by the Linked-ID, is not a parent-operation the invoked child operation is not allowed by the invoked parent-operation the type of the result parameter supplied is not agreed between the ROSEusers the reported error is not one of those agreed between the ROSE-users the reported error is not one that the invoked operation may report the type of error parameter supplied is not that agreed between the ROSE-users a non standard error was received from the Telephony Server
CLS_OBSERV_UNIV_FAIL_UNRECOGNIZED_ERROR_ REJECTION = 1188, CLS_OBSERV_UNIV_FAIL_UNEXPECTED_ERROR_ REJECTION = 1189, CLS_OBSERV_UNIV_FAIL_MISTYPED_PARAMETER_ REJECTION = 1190, CLS_OBSERV_UNIV_FAIL_NON_STANDARD = 191,
11 of 15 TN0325_Exceptions.fm
Sub Errors
12 of 15 TN0325_Exceptions.fm
Sub Errors
Sub-error string CLS_OBSERV_FAIL_EVENT_CAMP_ON = 1312, CLS_OBSERV_FAIL_EVENT_DEST_NOT_OBTAINABLE = 1313, CLS_OBSERV_FAIL_EVENT_DO_NOT_DISTURB = 1314, CLS_OBSERV_FAIL_EVENT_INCOMPATIBLE_ DESTINATION = 1315, CLS_OBSERV_FAIL_EVENT_INVALID_ACCOUNT_CODE = 1316, CLS_OBSERV_FAIL_EVENT_KEY_CONFERENCE = 1317, CLS_OBSERV_FAIL_EVENT_LOCKOUT = 1318, CLS_OBSERV_FAIL_EVENT_MAINTENANCE = 1319,
Description a Camp On feature has been invoked or has matured the call could not obtain the destination the call encountered a Do Not Disturb condition the call encountered an incompatible destination the call has an invalid account code the event report occurred at a bridged or twin device the call encountered inter-digit timeout while dialing the call encountered a facility or endpoint in a maintenance condition the call encountered a congested network the call could not reach a destination network the call has not yet been redirected the call could not access any agent the call overflowed a queue, group, or target the call is alerting a device due to a time-out built into a feature that failed to complete or that anticipated further action from the user the call has been redirected the call encountered reorder, the request was not recognizable resources were not available
CLS_OBSERV_FAIL_EVENT_NETWORK_CONGESTION = 1320, CLS_OBSERV_FAIL_EVENT_NETWORK_NOT_OBTAINAB LE = 1321, CLS_OBSERV_FAIL_EVENT_NO_AVAILABLE_AGENTS = 1323, CLS_OBSERV_FAIL_EVENT_OVERRIDE = 1324, CLS_OBSERV_FAIL_EVENT_OVERFLOW = 1326, CLS_OBSERV_FAIL_EVENT_RECALL = 1327,
13 of 15 TN0325_Exceptions.fm
Sub Errors
Description a transfer is in progress or has occurred the call encountered Trunks Busy
14 of 15 TN0325_Exceptions.fm
Sub Errors
Sub-error string CLS_REC_VOICE_LOGGER_NOT_OTC_MODE = 1413, CLS_REC_VOICE_LOGGER_TOO_MANY_ACTIVE_ CHANNELS = 1414, CLS_REC_VOICE_LOGGER_CHANNEL_IS_PRE_POST_ ALARM = 1415, CLS_REC_VOICE_LOGGER_NORMAL_SWITCHED_ AUDIO = 1416, CLS_REC_VOICE_LOGGER_CANT_SWITCH_TO_NON_ DIGITAL_CHANNEL = 1417, CLS_REC_VOICE_LOGGER_DIFFERENT_MATRIX_CARD S = 1418, CLS_REC_VOICE_LOGGER_DYNAMIC_SWITCH_FAILED = 1419, CLS_REC_VOICE_LOGGER_CANT_SWITCH_MORE_ THAN_4_DATALINES = 1420,
Description voice logger is not in OTC mode there are too many active channels already channel is in pre post alarm mode normal logger switched audio to spare cant switch input from matrix to non digital input channel cant switch from different matrix card dynamic switch failed on scsa system cant switch more than 4 datalines on scsa system
15 of 15 TN0325_Exceptions.fm