Contents
Error Messages
The following tables present the complete set of error messages T-Server distributes with the EventError event.
T-Server-Defined Errors
Code | Description |
---|---|
50 | Unknown error |
51 | Unsupported operation for the switch |
52 | Internal error |
53 | Invalid attribute |
54 | Switch not connected |
98 | Cannot complete transfer |
119 | Invalid password |
177 | Target DN invalid |
714 | Invalid Call_ID |
ISCC (Inter Server Call Control) Errors
Code | Description |
---|---|
1000 | Invalid or missing server location name |
1001 | Remote server disconnected |
1002 | Remote server has not processed request |
1003 | Wrong protocol version |
1004 | Remote link disconnected |
1005 | External routing feature not initiated |
1006 | No free CDNs |
1007 | No access number |
1008 | TCS feature is not initiated |
1009 | Invalid route type |
1010 | Invalid request |
1011 | No primary server was found on location |
1012 | Location is invalid or missing |
1013 | Timeout performing requested transaction |
1014 | No configured access resources are found |
1015 | No registered access resources are found |
1016 | Client is not authorized |
1017 | Invalid transaction type |
1018 | Invalid or missing transaction data |
1019 | Invalid location query request |
1020 | Invalid origin location |
Switch-Specific Errors
Code | Description |
---|---|
109 | Link down or bad link specified |
231 | DN is busy |
232 | No answer at DN |
233 | Call rejected |
1102 | Badly structured APDU |
1110 | Duplicate invocation (packet missed) |
1131 | Unexpected error response |
1132 | Unrecognized error |
1141 | Request incompatible with object |
1143 | Object not known |
1147 | Request caused privilege violation on device |
1153 | Invalid call destination |
1154 | Invalid feature requested |
1156 | Invalid cross-reference identifier |
1161 | Invalid object state |
1162 | Invalid Connection ID |
1173 | Resource is out of service |
1181 | Object monitor limit exceeded |
1190 | Unspecified security error |
This page was last edited on August 14, 2013, at 18:10.
Comments or questions about this documentation? Contact us for support!