CAPI error and status codes
The following table contains the most common CAPI error and status codes. Calling-Us receives the messages you will find in the Calling-Us logfiles/PROTOCOLS viy the CAPI interface of your ISDN connection or telecommunication system.
| CAPI 2.0 internal error codes | |
| 0x2001 | Message not allowed in its present state |
| 0x2002 | Invalid controller or PLCI/NCCI |
| 0x2003 | No free PLCI available |
| 0x2004 | No free NCCI available |
| 0x2005 | No free LISTEN available |
| 0x2007 | Invalid CAPI-message encoding |
| Protocol and hardware errors | |
| 0x3001 | B1-protocol not supported |
| 0x3002 | B2-protocol not supported |
| 0x3003 | B3-protocol not supported |
| 0x3004 | B1-protocol parameter not supported |
| 0x3005 | B2-protocol parameter not supported |
| 0x3006 | B3-protocol parameter not supported |
| 0x3007 | B-protocol combination not supported |
| 0x3008 | NCPI not supported |
| 0x3009 | Unknown CIP value |
| 0x300A | Flags not supported (reserved Bits) |
| 0x300B |
Facility value not supported |
| 0x300C | Data length not supported by current protocol |
| 0x300D | Reset procedure not supported by protocol |
| 0x3301 | Protocol error layer 1 (broken line or B-channel removed by signalling protocol) |
| 0x3302 | Protocol error layer 2 |
| 0x3303 | Protocol error layer 3 |
| 0x3304 | Another application got that call |
| Codes von der Vermittlung oder der Nebenstellen-Anlage | |
| 0x3480 | Normal termination |
| 0x3481 | Unallocated (unassigned) number |
| 0x3482 | No route to specified transit network |
| 0x3483 | No route to destination |
| 0x3486 | Channel unacceptable |
| 0x3487 | Call awarded and being delivered in an established channel |
| 0x3490 | Normal call clearing |
| 0x3491 | User busy |
| 0x3492 | No user responding (invalid MSN?) |
| 0x3493 | No answer from user (user alerted) |
| 0x3495 | Call rejected |
| 0x3496 | Number changed |
| 0x349A | Non-selected user clearing |
| 0x349B | Destination out of order |
| 0x349C | Invalid number format |
| 0x349D | Facility rejected |
| 0x349E | Response to STATUS ENQUIRY |
| 0x349F | Normal, unspecified |
| 0x34A2 | No circuit / channel available |
| 0x34A6 | Network out of order |
| 0x34A9 | Temporary failure |
| 0x34AA | Switching equipment congestion |
| 0x34AB | Access information discarded |
| 0x34AC | Requested circuit / channel not available |
| 0x34AF | Resources unavailable, unspecified |
| 0x34B1 | Quality of service unavailable |
| 0x34B2 | Requested facility not subscribed |
| 0x34B9 | Bearer capability not authorized |
| 0x34BA | Bearer capability not presently available |
| 0x34BF | Service or option not available, unspecified |
| 0x34C1 | Bearer capability not implemented |
| 0x34C2 | Channel type not implemented |
| 0x34C5 | Requested facility not implemented |
| 0x34C6 | Only restricted digital information bearer capability is available |
| 0x34CF | Service or option not implemented, unspecified |
| 0x34D1 | Invalid call reference value |
| 0x34D2 | Identified channel does not exist |
| 0x34D3 | A suspended call exists, but this call identity does not |
| 0x34D4 | Call identity in use |
| 0x34D5 | No call suspended |
| 0x34D6 | Call having the requested call identity has been cleared |
| 0x34D8 | Incompatible destination |
| 0x34DB | Invalid transit network selection |
| 0x34DF | Invalid message, unspecified |
| 0x34E0 | Mandatory information element is missing |
| 0x34E1 | Message type non-existent or not implemented |
| 0x34E2 | Message not compatible with call state or message type non-existent or not implemented |
| 0x34E3 | Information element non-existent or not implemented |
| 0x34E4 | Invalid information element contents |
| 0x34E5 | Message not compatible with call state |
| 0x34E6 | Recovery on timer expiry |
| 0x34EF | Protocol error, unspecified |
| 0x34FF | Interworking, unspecified |
Here you will find additional information about CAPI.
