logo itpoint.cz

Přehled kódů V. část stavových hlášení - dobrá pomůcka při řešení problémů se spojením euroISDN telefonu

pokračování ...

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ě.

Cause No. 50 - requested facility not subscribed [Q.850]

This cause indicates that the user has requested a supplementary service which is implemented by the equipment that generated this cause, but the user is not authorized to use.

Cause No. 52 - outgoing calls barred

Cause No. 53 - outgoing calls barred within CUG [Q.850]

This cause indicates that although the calling party is a member of the CUG for the outgoing CUG call, outgoing calls are not allowed for this member of the CUG.

Cause No. 54 - incoming calls barred

Cause No. 55 - incoming calls barred within CUG [Q.850]

This cause indicates that although the calling party is a member of the CUG for the incoming CUG call, incoming calls are not allowed for this member of the CUG.

Cause No. 57 - bearer capability not authorized [Q.850]

This cause indicates that the user has requested a bearer capability which is implemented by the equipment that generated this cause, but the user is not authorized to use.

Cause No. 58 - bearer capability not presently available [Q.850]

This cause indicates that the user has requested a bearer capability, which is implemented by the equipment that generated this cause, but is not available at this time.

Cause No. 62 - inconsistency in outgoing information element. [Q.850]

This cause indicates an inconsistency in the designated outgoing access information and subscriber class

Cause No. 63 - service or option not available, unspecified [Q.850]

This cause is used to report a service or option not available event only when no other cause in the service or option not available class applies.

Cause No. 65 - bearer capability not implemented [Q.850]

This cause indicates that the equipment sending this cause does not support the bearer capability requested.

Cause No. 66 - channel type not implemented [Q.850]

This cause indicates that the equipment sending this cause does not support the channel type requested.

Cause No. 69 - requested facility not implemented [Q.850]

This cause indicates that the equipment sending this cause does not support the requested supplementary services.

Cause No. 70 - only restricted digital information bearer capability is available (national use) [Q.850]

This cause indicates that the calling party has requested an unrestricted bearer service but the equipment sending this cause only supports the restricted version of the requested bearer capability.

Cause No. 79 - service or option not implemented, unspecified [Q.850]

This cause is used to report a service or option not implemented event only when no other cause in the service or option not implemented class applies.

Cause No. 81 - invalid call reference value [Q.850]

This cause indicates that the equipment sending this cause has received a message with a call reference, which is not currently in use on the user-network interface.

Cause No. 82 - identified channel does not exist [Q.850]

This cause indicates that the equipment sending this cause has received a request to use a channel not activated on the interface for a call. For example, if a user has subscribed to those channels on a primary rate interface numbered from 1 to 12 and the user equipment or the network attempts to use channels 13 through 23, this cause is generated.

Cause No. 83 - a suspended call exists, but this call identify does not [Q.850]

This cause indicates that a call resume has been attempted with a call identity which differs from that in use for any presently suspended call(s).

Cause No. 84 - call identity in use [Q.850]

This cause indicates that the network has received a call suspended request containing a call identity (including the null call identity) which is already in use for a suspended call within the domain of interfaces over which the call might be resumed.

Cause No. 85 - no call suspended [Q.850]

This cause indicates that the network has received a call resume request containing a Call identity information element that presently does not indicate any suspended call within the domain of interfaces over which calls may be resumed.

Cause No. 86 - call having the requested call identity has been cleared [Q.850]

This cause indicates that the network has received a call resume request containing a Call identity information element indicating a suspended call that has in the meantime been cleared while suspended (either by network time-out or by the remote user).

Cause No. 87 - user not a member of CUG [Q.850]

This cause indicates that the called user for the incoming CUG call is not a member of the specified CUG or that the calling user is an ordinary subscriber calling a CUG subscriber.

Cause No. 88 - incompatible destination [Q.850]

This cause indicates that the equipment sending this cause has received a request to establish a call that has low layer compatibility, high layer compatibility or other compatibility attributes (for example, data rate), which cannot be accommodated.

Cause No. 90 - nonexistent CUG [Q.850]

This cause indicates that the specified CUG does not exist.

Cause No. 91 - invalid transit network selection (national use) [Q.850]

This cause indicates that a transit network identification was received, which is of an incorrect format as defined in Annex C/Q.931

Cause No. 95 - invalid message, unspecified [Q.850]

This cause is used to report an invalid message event only when no other cause in the invalid message class applies.

Cause No, 96 - mandatory information element is missing [Q.850]

This cause indicates that the equipment sending this cause has received a message that is missing an information element, which must be present in the message before that message can be processed.

Cause No. 97 - message type nonexistent or not implemented [Q.850]

This cause indicates that the equipment sending this cause has received a message with a message type it does not recognize either because this is a message not defined or defined but not implemented by the equipment sending this cause.

Cause No. 98 - message not compatible with call state or message type nonexistent or not implemented. [Q.850]

This cause indicates that the equipment sending this cause has received a message such that the procedures do not indicate that this is a permissible message to receive while in the call state, or a STATUS message was received indicating an incompatible call state.

Cause No. 99 - Information element/parameter nonexistent or not implemented [Q.850]

This cause indicates that the equipment sending this cause has received a message that includes information element(s)/parameter(s) not recognized because the information element(s)/parameter name(s) are not defined or are defined but not implemented by the equipment sending the cause. This cause indicates that the information element(s)/parameter(s) were discarded. However, the information element is not required to be present in the message in order for the equipment sending the cause to process the message.

Cause No. 100 - Invalid information element contents [Q.850]

This cause indicates that the equipment sending this cause has received an information element that it has implemented; however, one or more fields in the I.E. are coded in such a way which has not been implemented by the equipment sending this cause.

Cause No. 101 - message not compatible with call state [Q.850]

This cause indicates that a message has been received which is incompatible with the call state.

Cause No. 102 - recovery on timer expiry [Q.850]

This cause indicates that a procedure has been initiated by the expiration of a timer in association with error handling procedures.

Cause No. 103 - parameter non-existent or not implemented - passed on (national use) [Q.850]

This cause indicates that the equipment sending this cause has received a message that includes parameters not recognized because the parameters are not defined or are defined but not implemented by the equipment sending this cause. The cause indicates that the parameter(s) were ignored. In addition, if the equipment sending this cause is an intermediate point, then this cause indicates that the parameter(s) were passed unchanged.

Cause No. 110 - message with unrecognized parameter discarded [Q.850]

This cause indicates that the equipment sending this cause has discarded a received message that includes a parameter that is not recognized.

Cause No. 111 - protocol error, unspecified [Q.850]

This cause is used to report a protocol error event only when no other cause in the protocol error class applies.

Cause No. 127 - Interworking, unspecified [Q.850]

This cause indicates that an interworking call (usually a call to SW56 service) has ended.

Notes about Cause Codes over 128

Cause code values of 128 and higher are not sent over the network, and are not defined in Rec. Q.850. A terminal displaying a value 128 or higher and claiming it is a cause code arguably has a bug or is implementing some proprietary diagnostic code (not necessarily bad). Some documentation has cause codes listed with numbers higher than 128, but at this time they are proprietary in nature. The PRI equipment vendors are the most likely to use these codes as they have been using proprietary messages in the facilities data link for some time now (there is an as yet undefined area in the FDL which is big enough to carry small datagrams or messages. It is typically used to pass proprietary control or maintenance messages between multiplexers.

Článek ze dne 17. ledna 2001 - středa

Stáhněte si ZDARMA zkušební verzi systému M-Files