This appendix contains a list of the supported switch types. It also contains the ISDN cause codes, cause values, bearer capability values, and progress description field values that are valid within the debug commands for ISDN.
Table B-1 lists the ISDN switch types supported by the ISDN interface.
German 1TR6 ISDN switches
AT&T basic rate switches
NT DMS-100 basic rate switches
NET3 ISDN and Euro-ISDN switches (UK and others), also called E-DSS1 or DSS1
National ISDN-1 switches
Norway Net3 switches
New Zealand Net3 switches
Australian TS013 switches
No switch defined
Japanese NTT ISDN switches (ISDN BRI only)
AT&T 4ESS switch type for the U.S. (ISDN PRI only)
AT&T 5ESS switch type for the U.S. (ISDN PRI only)
NT DMS-100 switch type for the U.S. (ISDN PRI only)
NET5 ISDN PRI switches (Europe)
INS-Net 1500 for Japan (ISDN PRI only)
Australian TS014 switches (ISDN PRI only)
French VN2 ISDN switches (ISDN BRI only)
French VN3 ISDN switches (ISDN BRI only)
French VN4 ISDN switches (ISDN BRI only)
Table B-2 lists the ISDN cause code fields that display in the following format within the debug commands:
i=0x y1 y2 z1 z2 [a1 a2
The values that follow are in hexadecimal.
8---ITU-T standard coding.
1---Private network serving local user
2---Public network serving local user
4---Public network serving remote user
5---Private network serving remote user
A---Network beyond internetworking point
Class (the more significant hexadecimal number) of cause value. Refer to Table B-3 for detailed information about possible values.
Value (the less significant hexadecimal number) of cause value. Refer to Table B-3 for detailed information about possible values.
(Optional) Diagnostic field that is always 8.
(Optional) Diagnostic field that is one of the following values:
The following is sample output of this form of the debug isdn q931 command:
Cause i = 0x8790
Table B-3 lists descriptions of the cause value field of the cause information element. The notes referred to in the Diagnostics column follow the table. For the debug isdn q931 command output, drop the highest bit of the cause value before using this table. For example, a cause value of 0x90 becomes 0x10.
|Decimal Value||Hex Value||Cause||Diagnostics||Explanation|
Unallocated (unassigned) number
The ISDN number was sent to the switch in the correct format; however, the number is not assigned to any destination equipment.
No route to specified transit network
Transit network identity (Note 9)
The ISDN exchange is asked to route the call through an unrecognized intermediate network.
No route to destination
The call was routed through an intermediate network that does not serve the destination address.
The service quality of the specified channel is insufficient to accept the connection.
Call awarded and being delivered in an established channel
The user is assigned an incoming call that is being connected to an already-established call channel.
Normal call clearing
Normal call clearing has occurred.
The called system acknowledges the connection request but is unable to accept the call because all B channels are in use.
No user responding
The connection cannot be completed because the destination does not respond to the call.
No answer from user (user alerted)
The destination responds to the connection request but fails to complete the connection within the prescribed time. The problem is at the remote end of the connection.
Note 10. User supplied diagnostic
The destination is capable of accepting the call but rejected the call for an unknown reason.
The ISDN number used to set up the call is not assigned to any system.
Non-selected user clearing
The destination is capable of accepting the call but rejected the call because it was not assigned to the user.
Designation out of order
The destination cannot be reached because the interface is not functioning correctly, and a signaling message cannot be delivered. This might be a temporary condition, but it could last for an extended period of time. For example, the remote equipment might be turned off.
Invalid number format
The connection could be established because the destination address was presented in an unrecognizable format or because the destination address was incomplete.
Facility identification (Note 1)
The facility requested by the user cannot be provided by the network.
Response to STATUS ENQUIRY
The status message was generated in direct response to the prior receipt of a status enquiry message.
Reports the occurrence of a normal event when no standard cause applies. No action required.
No circuit/channel available
The connection cannot be established because no appropriate channel is available to take the call.
Network out of order
The destination cannot be reached because the network is not functioning correctly, and the condition might last for an extended period of time. An immediate reconnect attempt will probably be unsuccessful.
An error occurred because the network is not functioning correctly. The problem will be resolved shortly.
Switching equipment congestion
The destination cannot be reached because the network switching equipment is temporarily overloaded.
Access information discarded
Discarded information element identifier(s) (Note 5)
The network cannot provide the requested access information.
Requested circuit/channel not available
The remote equipment cannot provide the requested channel for an unknown reason. This might be a temporary problem.
Resources unavailable, unspecified
The requested channel or service is unavailable for an unknown reason. This might be a temporary problem.
Quality of service unavailable
The requested quality of service cannot be provided by the network. This might be a subscription problem.
Requested facility not subscribed
Facility identification (Note 1)
The remote equipment supports the requested supplementary service by subscription only.
Bearer capability not authorized
The user requested a bearer capability that the network provides, but the user is not authorized to use it. This might be a subscription problem.
Bearer capability not presently available
The network normally provides the requested bearer capability, but it is unavailable at the present time. This might be due to a temporary network problem or to a subscription problem.
Service or option not available, unspecified
The network or remote equipment was unable to provide the requested service option for an unspecified reason. This might be a subscription problem.
Bearer capability not implemented
The network cannot provide the bearer capability requested by the user.
Channel type not implemented
Channel Type (Note 6)
The network or the destination equipment does not support the requested channel type.
Requested facility not implemented
Facility Identification (Note 1)
The remote equipment does not support the requested supplementary service.
Only restricted digital information bearer capability is available
The network is unable to provide unrestricted digital information bearer capability.
Service or option not implemented, unspecified
The network or remote equipment is unable to provide the requested service option for an unspecified reason. This might be a subscription problem.
Invalid call reference value
The remote equipment received a call with a call reference that is not currently in use on the user-network interface.
Identified channel does not exist
The receiving equipment is requested to use a channel that is not activated on the interface for calls.
A suspended call exists, but this call identity does not
The network received a call resume request. The call resume request contained a Call Identify information element that indicates that the call identity is being used for a suspended call.
Call identity in use
The network received a call resume request. The call resume request contained a Call Identify information element that indicates that it is in use for a suspended call.
No call suspended
The network received a call resume request when there was not a suspended call pending. This might be a transient error that will be resolved by successive call retries.
Call having the requested call identity has been cleared
The network received a call resume request. The call resume request contained a Call Identity information element, which once indicated a suspended call. However, the suspended call was cleared either by timeout or by the remote user.
Indicates that an attempt was made to connect to non-ISDN equipment. For example, to an analog line.
Invalid transit network selection
The ISDN exchange was asked to route the call through an unrecognized intermediate network.
Invalid message, unspecified
An invalid message was received, and no standard cause applies. This is usually due to a D-channel error. If this error occurs systematically, report it to your ISDN service provider.
Mandatory information element is missing
Information element identifier(s) (Note 5)
The receiving equipment received a message that did not include one of the mandatory information elements. This is usually due to a D-channel error. If this error occurs systematically, report it to your ISDN service provider.
Message type non-existent or not implemented
The receiving equipment received an unrecognized message, either because the message type was invalid or because the message type was valid but not supported. The cause is due to either a problem with the remote configuration or a problem with the local D channel.
Message not compatible with call state or message type non-existent or not implemented
The remote equipment received an invalid message, and no standard cause applies. This cause is due to a D-channel error. If this error occurs systematically, report it to your ISDN service provider.
Information element non-existent or not implemented
Information element identifier(s) (Notes 5, 7)
The remote equipment received a message that includes information elements, which were not recognized. This is usually due to a D-channel error. If this error occurs systematically, report it to your ISDN service provider.
Invalid information element contents
Information element identifier(s) (Note 5)
The remote equipment received a message that includes invalid information in the information element. This is usually due to a D-channel error.
Message not compatible with call state
The remote equipment received an unexpected message that does not correspond to the current state of the connection. This is usually due to a D-channel error.
Recovery on timer expires
Timer number (Note 8)
An error-handling (recovery) procedure was initiated by a timer expiry. This is usually a temporary problem.
Protocol error, unspecified
An unspecified D-channel error when no other standard cause applies.
An event occurred, but the network does not provide causes for the action that it takes. The precise problem is unknown.
Note 1: The coding of facility identification is network dependent.
Note 2: Incompatible parameter is composed of incompatible information element identifier.
Note 3: The format of the diagnostic field for causes 39, 3A, and 41 is shown in the ITU-T Q.850 specification, Table 3b/Q.850.
Note 4: User-supplied diagnostic field is encoded according to the user specification, subject to the maximum length of the cause information element. The coding of user-supplied diagnostics should be made in such a way that it does not conflict with the coding described in Table B-2.
Note 5: Locking and non-locking shift procedures described in the ITU-T Q.931 specification apply. In principle, information element identifiers are in the same order as the information elements in the received message.
Note 6: The following coding is used:
Note 7: When only locking shift information element is included and no variable length information element identifier follows, it means that the codeset in the locking shift itself is not implemented.
Note 8: The timer number is coded in IA5 characters. The following coding is used in each octet:
Note 9: The diagnostic field contains the entire transit network selection or network-specific facilities information element, as applicable.
Note 10: See Table B-2 for the coding that is used.
Table B-4 lists the ISDN bearer capability values that display in the following format within the debug commands:
0x8890 for 64 kbps or 0x8890218F for 56 kbps
Indication that the values that follow are in hexadecimal
ITU-T coding standard; unrestricted digital information
Circuit mode, 64 kbps
Layer 1, V.110/X.30
Synchronous, no in-band negotiation, 56 kbps
Table B-5 lists the values of the Progress description field contained in the ISDN Progress indicator information element.
Call is not end-to-end ISDN; further call progress information may be available in-band
Destination address is non-ISDN
Origination address is non-ISDN
Call has returned to the ISDN
In-band information or appropriate pattern now available
Delay in response at destination interface
All other values for the progress description field are reserved.