Máte-li problém s např. s euroISDN telefonem, přinášíme Vám přehled kódů stavových hlášení, která se mohou objevovat na displeji přístroje. Tyto kódy nejsou podle našich zkušeností běžně dostupné, jejich znění přinášíme v originále - tedy v angličtině.
|57||39||Bearer capability not authorized||Note 3||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.|
|58||3A||Bearer capability not presently available||Note 3||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.|
|63||3F||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.|
|65||41||Bearer capability not implemented||Note 3||The network cannot provide the bearer capability requested by the user.|
|66||42||Channel type not implemented||Channel Type (Note 6)||The network or the destination equipment does not support the requested channel type.|
|69||45||Requested facility not implemented||Facility Identification (Note 1)||The remote equipment does not support the requested supplementary service.|
|70||46||Only restricted digital information bearer capability is available||The network is unable to provide unrestricted digital information bearer capability.|
|79||4F||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.|
|81||51||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.|
|82||52||Identified channel does not exist||Channel identity||The receiving equipment is requested to use a channel that is not activated on the interface for calls.|
|83||53||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.|
|84||54||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.|
|85||55||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.|
|86||56||Call having the requested call identity has been cleared||Clearing cause||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.|
|88||58||Incompatible destination||Incompatible parameter (Note 2)||Indicates that an attempt was made to connect to non-ISDN equipment. For example, to an analog line.|
|91||5B||Invalid transit network selection||The ISDN exchange was asked to route the call through an unrecognized intermediate network.|
|95||5F||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.|
|96||60||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.|
|97||61||Message type non-existent or not implemented||Message type||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.|
|98||62||Message not compatible with call state or message type non-existent or not implemented||Message type||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.|
|99||63||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.|
|100||64||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.|
|101||65||Message not compatible with call state||Message type||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.|
|102||66||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.|
|111||6F||Protocol error, unspecified||An unspecified D-channel error when no other standard cause applies.|
|127||7F||Internetworking, unspecified||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:
Bearer Capatibility Values
0x8890 for 64 kbps or 0x8890218F for 56 kbps
|0x||Indication that the values that follow are in hexadecimal|
|88||ITU-T coding standard; unrestricted digital information|
|90||Circuit mode, 64 kbps|
|21||Layer 1, V.110/X.30|
|8F||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.
|0000001||1||Call is not end-to-end ISDN; further call progress information may be available in-band|
|0000010||2||Destination address is non-ISDN|
|0000011||3||Origination address is non-ISDN|
|0000100||4||Call has returned to the ISDN|
|0001000||8||In-band information or appropriate pattern now available|
|0001010||10||Delay in response at destination interface|
Článek ze dne 17. ledna 2001 - středa