Table of Contents
The CAPI interface used here has its own coding of standard ISDN error codes. Most of the errors described in the section called “Internal CAPI errors” are only important for developers of the CapiSuite core. As user, you only need to know the codes shown in the section called “CAPI errors describing connection problems” as they'll be used in the CapiSuite Python functions like capisuite.disconnect.
You'll find a list of all the codes and a short description below. A detailled description of the CAPI codes can be found in the CAPI specification available at http://www.capi.org.
All numbers are given hexadecimal!
All errors described here indicate some problem with the connection. These errors are also important for script writers as they're returned by some CapiSuite Python functions. See the section called “CapiSuite command reference” for further details.
Protocol errors indicate some problem during data transfer. Only messages for the transparent (voice) and fax protocols spoken by CapiSuite are shown here.
0 - Normal call clearing, no error
3301 - Protocol error layer 1 (broken line or B-channel removed by signalling protocol)
3302 - Protocol error layer 2
3303 - Protocol error layer 3
3304 - Another application got that call
3311 - T.30 (fax) error: Connection not successful (remote station is not a G3 fax device)
3312 - T.30 (fax) error: Connection not successful (training error)
3313 - T.30 (fax) error: Disconnect before transfer (remote station doesn't support transfer mode, e.g. wrong resolution)
3314 - T.30 (fax) error: Disconnect during transfer (remote abort)
3315 - T.30 (fax) error: Disconnect during transfer (remote procedure error)
3316 - T.30 (fax) error: Disconnect during transfer (local transmit data underflow)
3317 - T.30 (fax) error: Disconnect during transfer (local receive data overflow)
3318 - T.30 (fax) error: Disconnect during transfer (local abort)
3319 - T.30 (fax) error: Illegal parameter coding (e.g. defective SFF file)
These codes are ISDN error codes which are described by the ETS 300 102-01 standard in more detail. It's currently available for private use at http://www.etsi.org without fee. For details how the ISDN codes are mapped to the CAPI numbers see the CAPI specification, parameter "Info".
3400 - Normal termination, no reason available
3480 - Normal termination
3481 - Unallocated (unassigned) number
3482 - No route to specified transit network
3483 - No route to destination
3486 - Channel unacceptable
3487 - Call awarded and being delivered in an established channel
3490 - Normal call clearing
3491 - User busy
3492 - No user responding
3493 - No answer from user (user alerted)
3495 - Call rejected
3496 - Number changed
349A - Non-selected user clearing
349B - Destination out of order
349C - Invalid number format
349D - Facility rejected
349E - Response to STATUS ENQUIRY
349F - Normal, unspecified
34A2 - No circuit / channel available
34A6 - Network out of order
34A9 - Temporary failure
34AA - Switching equipment congestion
34AB - Access information discarded
34AC - Requested circuit / channel not available
34AF - Resources unavailable, unspecified
34B1 - Quality of service unavailable
34B2 - Requested facility not subscribed
34B9 - Bearer capability not authorized
34BA - Bearer capability not presently available
34BF - Service or option not available, unspecified
34C1 - Bearer capability not implemented
34C2 - Channel type not implemented
34C5 - Requested facility not implemented
34C6 - Only restricted digital information bearer capability is available
34CF - Service or option not implemented, unspecified
34D1 - Invalid call reference value
34D2 - Identified channel does not exist
34D3 - A suspended call exists, but this call identity does not
34D4 - Call identity in use
34D5 - No call suspended
34D6 - Call having the requested call identity has been cleared
34D8 - Incompatible destination
34DB - Invalid transit network selection
34DF - Invalid message, unspecified
34E0 - Mandatory information element is missing
34E1 - Message type non-existent or not implemented
34E2 - Message not compatible with call state or message type non-existent or not implemented
34E3 - Information element non-existent or not implemented
34E4 - Invalid information element contents
34E5 - Message not compatible with call state
34E6 - Recovery on timer expiry
34EF - Protocol error, unspecified
34FF - Interworking, unspecified