ISDN error messages - Cause definitions

Content:
--------
1. Fehlermeldung direkt von der ISDN-Software
2. Fehlermeldungen von der ISDN-Vermittlungsstelle oder Nebenstellenanlage
3. Failure Reports in Euro-ISDN (DSS1 or ETSI)
4. CAPI-Errorcodes

1. Fehlermeldung direkt von der ISDN-Software
---------------------------------------------

0 Die gewaehlte ISDN-Rufnummer wurde nicht erreicht, die Verbindung wurde nach
Ueberschreitung eines Zeitlimits ausgeloest. Eine moegliche Ursache hierfuer ist eine
unvollstaendige Rufnummer (fehlende Amtsziffer beim Waehlen aus Nebenstellenanlagen,
fehlende EAZ beim Anwaehlen von anderen Teilnehmern ...)
0x01 "No channel available"
Es ist kein ISDN-B-Kanal mehr frei um weitere Verbindungen herzustellen.
Wieviele Kanaele momentan verwendet/belegt sind, laesst sich durch Aufruf
von "isistat -i" kontrollieren (NB=Number of B-Channels, UB=Used B-Channels)
0x02 "Illegal protocol options"
Diese Meldung resultiert aus fehlerhaften Eintraegen in der Datei
"/usr/isi/config/services" oder in der Datei "/usr/isi/config/protocols"
0x03 "Illegal ISDN address"
Diese Meldung resultiert aus feherhaften Eintraegen in der Datei
"/usr/isi/config/hosts" oder in der Datei "/usr/isi/config/services". Die
ISDN-Rufnummer (Aufbau siehe
Handbuch ISI/Base, Seite 4-23) darf nur numerische Zeichen enthalten. SI, AI und
ggf. EAZ werden aus der Datei services ermittelt. Die DAD stammt aus der Datei
hosts.
0x08 "Cannot activate L1"
Der Layer 1 einer ISDN-Verbindung kann nicht aufgebaut werden. Dies bedeutet
in der Regel eine physikalische Unterbrechung zwischen Rechner und Anschluss-
dose, oder einen absolut inaktiven ISDN-Anschluss.
Kontrollmoeglichkeiten zum Eingrenzen der Ursache koennen sein :
- Anschluss eines anderen ISDN-Endgeraetes (z.B. Telefon) an die Dose und Test.
- Anwahl der Nummer von einem anderen Apparat (Kein Anschluss unter dieser Nr ?).
- direkter Anschluss des Geraetes an das Network Terminal (NT) der
Bundespost. Dadurch koennen z.B. Fehler in der Inhouse-Verdrahtung erkannt werden.
0x09 "Cannot get TEI"
Der Versuch eine TEI (Terminal Endpunkt Identifier) am S0-Bus zu erhalten, ist
gescheitert. Eventuell haben zum selben Zeitpunkt andere Endgeraete am S0-Bus
ebenfalls versucht eine TEI zu erhalten.
0x0a "Protocol violation on L2"
0x39 "Internal protocol error"


2. Fehlermeldungen von der ISDN-Vermittlungsstelle oder Nebenstellenanlage
im deutschen ISDN (1TR6-Protokoll)
--------------------------------------------------------------------------

0x80 "Normal call clearing"
0x81 "Invalid call reference value"
0x83 "Bearer service not implemented"
Eine Verbindung mit einer bestimmten Dienstkennung (Service Indicator , vgl. Handbuch
ISI/Base Anhang C-1) kann beim Rufenden oder beim Anrufer nicht durchgeschaltet
werden. Sowohl bei Basis-Anschluessen als auch bei Nebenstellenanlagen muss die
Verwendung bestimmter Dienstkennungen beantragt bzw. freigeschaltet werden.
0x87 "Call identity does not exist"
Gleichbedeutend zur Meldung : "Kein Anschluss unter dieser Nummer"
0x88 "Call identity in use"
0x8a "No Channel available"
Alle verfuegbaren B-Kanaele des ISDN-Anschlusses sind belegt (z.B. durch andere
Endgeraete am S0-Bus oder andere Verbindungen vom selben Endgeraet).
0x90 "Requested facility not implemented"
0xa0 "Outgoing calls barred"
Abgehende Rufe von diesem Anschluss sind wegen einer Sperre nicht moeglich.
Diese Meldung tritt haeufig bei Nebenstellenanlagen auf, wenn z.B.Verbindungen
nur zu bestimmten Ortsnetzen/Laendern erlaubt sind.
0xa1 "User Busy"
Alle ISDN-Kanaele beim angerufenen Teilnehmer sind belegt.
0xa2 "negativer GBG-Vergleich"
Der gerufene Teilnehmer ist Mitglied einer geschlossenen Benutzergruppe . In
solchen - von der Post eingerichteten - Benutzergruppen wird ein Anruf nur dann
zugestellt, wenn der Anruf Mitglied der selben Gruppe ist.
0xa3 "Non existant CUG"
0xa5 "als SPV nicht erlaubt"
0xb0 "Reverse charging not allowed at origination"
0xb1 "Reverse charging not allowed at destination"
0xb2 "Reverse charging rejected"
0xb5 "Destination not obtainable"
Gleichbedeutend zur Meldung : "Kein Anschluss unter dieser Nummer".
0xb8 "Number changed"
Tritt z.B. bei Hicom-Nebenstellenalagen auf wenn die gerufene Nummer nicht mit der
Rufnummer des erreichten Zielanschlusses uebereinstimmt. Dies ist z.B. dann der Fall
wenn die Endgeraeteauswahlziffer (EAZ) in der Rufnummer verwendet wird.
0xb9 "Out of order"
Der gerufenene Anschluss ist ausser Betrieb, bzw. derzeit nicht erreichbar.
0xba "User not responding"
Bei dem angerufenen Anschluss wird der Ruf nicht angenommen/abgehoben. Folgende
Ursachen sind moeglich :
- Beim Teilnehmer ist das entsprechende Endgeraet nicht eingeschaltet/angeschlossen.
- Es wurde nicht die erwartete Endgeraeteauswahlziffern (EAZ) uebermittelt.
- Es wurde nicht die korrekte Rufnummer gewaehlt .
0xbb "User access busy"
Beim gerufenen Teilnehmer sind alle B-Kanaele belegt .
0xbd "Incomming calls barred"
Ankommende Verbindungen beim gerufenen Teilnehmer sind nicht erlaubt bzw.
moeglich (z.B. Anschluss ausser Betrieb).
0xbe "Call rejected"
Der angerufene Teilnehmer hat die Annahme des Rufes verweigert,bzw. darf den Anruf
nicht erhalten. Moegliche Ursachen sind :
- Der Anrufer verwendet den Zugangsschutz von ISI/Base. (Eintraege in den Dateien
"/usr/isi/config/group" und "/usr/isi/config/cond", vgl. ISI/Base-Handbuch S. 6-10)
- Die Nebenstellenanlage an der der gerufene Teilnehmer angeschlossen ist verbietet
ankommende Rufe von bestimmten Verbindungspartnern oder Anrufe mit bestimmten
Dienstkennungen.
0xd9 "Network congestion"
Das ISDN-Netzwerk ist an irgendeiner Stelle ueberlastet (gassenbesetzt). Diese
kann z.B. bei Anwahl einer Nebenstellenanlage passieren, wenn alle Amtsleitungen
besetzt sind.
0xda "Remote user initiated"
0xea Diese Fehlermeldung kann an SEL-Nebenstellenanlagen auftreten. Diese Anlage kann
abgehende Rufe mit isilogin grundsaetzlich nicht verarbeiten, da sie erwartet, dass
abgehende Rufe von einem Geraet immer mit einer bestimmten EAZ verknuepft sind.
0xf0 "Local procedure error"
0xf1 "Remote procedure error"
0xf2 "Remote user suspended"
0xf3 "Remote user resumed"
0xf4 "User info discarded locally"


3. Failure Reports in Euro-ISDN (DSS1 or ETSI)
------------------------------------------------------------------------------

Please note that the BinTec software usually only supplies the
least significant 7 bits of the Euro-ISDN cause code, in effect
subtracting 0x80. So instead of e.g. 0x95 the value 0x15 is dis-
played.

The following list is devided into different classes. The structure is:
Failure Report: Probable Cause

The classes are:
----------------
3.1 Normal class
3.2 Resource unavailable class
3.3 Service or option not available class
3.4 Service or option not implemented class
3.5 Invalid message class
3.6 Protocol error class
3.7 Interworking class

3.1 Normal class
------------------------------------------------------------------------------
0x80: Normal call clearing This is no error!

0x81: Unallocated (unassigned) number
This cause indicates that the destination, re-
quested by the calling user can not be
reached because, although the number is in
a valid format, it is not currently assigned (al-
located).

0x82: No route to specified transit network
This cause indicates that the equipment
sending this cause has received a request to
route the call through a particular transit net-
work which it does not recognise. The equip-
ment sending this cause does not recognise
the transit network either, because the transit
network does not exist or because that par-
ticular transit network, while it does exist,
does not service the equipment which is
sending this cause.
This cause is supported on a network-de-
pendent basis.

0x83: No route to destination
This cause indicates that the called user can
not be reached because the network
through which the call has been routed does
not serve the destination desired.
This cause is supported on a network-de-
pendent basis.

0x86: Channel unacceptable
This cause indicates the channel most re-
cently identified is not acceptable to the
sending entity for use in this call.

0x87: Call awarded and being delivered in an established channel
This cause indicates that the user has been
awarded the incoming call, and that the in-
coming call is being connected to a chan-
nel already established to that user for similar
calls (e.g. packet-mode X.25 virtual calls).

0x90: Normal call clearing This cause indicates that the call is being
cleared because one of the users involved
in the call has requested that the call be
cleared.

0x91: User busy This cause is used when the called user has
indicated the inability to accept another
call.

0x92: No user responding This cause is used when a user does not re-
spond to a call establishment message with
either an alerting or connect indication with-
in the prescribed period of time allocated.

0x93: No answer from user (user alerted)
This cause is used when a user has provided
an alerting indication but has not provided a
connect indication within a prescribed peri-
od of time.

0x95: Call rejected This cause indicates that the equipment
sending this cause does not wish to accept
this call, although it could have accepted
the call because the equipment sending this
cause is neither busy nor incompatible.

0x96: Number changed This cause is returned to a calling user when
the called party number indicated by the
calling user is no longer assigned.

0x9a: Non-selected user clearing
This cause indicates that the user has not
been awarded the incoming call.

0x9b: Destination out of order
This cause indicates that the destination indi-
cated by the user can not be reached be-
cause the interface to the destination is not
functioning correctly. The term "not function-
ing correctly" indicates that a signalling mes-
sage was unable to be delivered to the re-
mote user; e.g. a physical layer or data link
layer failure at the remote user, user-equip-
ment off-line, etc.

0x9c: Invalid number format
This cause indicates that the called user can
not be reached because the called party
number is not in a valid format or is not com-
plete.

0x9d: Facility rejected This cause is returned when a facility request-
ed by the user can not be provided by the
network.

0x9e: Response to STATUS ENQUIRY
This cause is included in the STATUS message
when the reason for generating the STATUS
message was the prior receipt of a STATUS
ENQUIRY message.

0x9f: Normal, unspecified This cause is used to report a normal event
only when no other cause in the normal class
applies.


3.2 Resource unavailable class
------------------------------------------------------------------------------
0xa2: No circuit/channel available
This cause indicates that there is no appropri-
ate circuit/channel presently available to
handle the call.

0xa6: Network out of order
This cause indicates that the network is not
functioning correctly and that the condition
is likely to last a relatively long period of time;
e.g. immediately reattempting the call is not
likely to be successful.

0xa9: Temporarily failure This cause indicates that the network is not
functioning correctly and that the condition
is not likely to last a long period of time; e.g.
the user may wish to try another call attempt
almost immediately.

0xaa: Switching equipment congestion
This cause indicates that the switching
equipment generating this cause is experi-
encing a period of high traffic.

0xab: Access Information discarded
This cause indicates that the network could
not deliver access information to the remote
user as requested; i.e. a user-to-user informa-
tion, low layer compatibility, high layer com-
patibility or subaddress as indicated in the di-
agnostic.

0xac: Requested circuit/channel not available
This cause is returned when the circuit or
channel indicated by the requesting entity
cannot be provided by the other side of the
interface.

0xaf: Resources unavailable, unspecified
This cause is used to report a resource una-
vailable event only when no other cause in
the resource unavailable class applies.


3.3 Service or option not available class
------------------------------------------------------------------------------
0xb1: Quality of service unavailable
This cause is used to report that the request-
ed quality of service, as defined in the ITU-T
recommendation X.213, cannot be provid-
ed (e.g. throughput or transit delay cannot
be supported).

0xb2: Requested facility not subscribed
This cause indicates that the requested sup-
plementary service could not be provided
by the network because the user has not
completed the necessary administrative ar-
rangements with its supporting network.

0xb9: Bearer Capability not authorized
This cause indicates that the user has re-
quested a bearer capability which is imple-
mented by the equipment which generated
this cause but the user is not authorized to
use.

0xba: Bearer Capability not presently available
This cause indicates that the user has re-
quested a bearer capability which is imple-
mented by the equipment which generated
this cause but which is not available at this
time.

0xbf: Service or option not available, unspecified
This cause is used to report a service or op-
tion not available event only when no other
cause in the service or option not available
class applies.


3.4 Service or option not implemented class
------------------------------------------------------------------------------
0xc1: Bearer capability not implemented
This cause indicates that the equipment
sending this cause does not support the
bearer capability requested.

0xc2: Channel type not implemented
This cause indicates that the equipment
sending this cause does not support the
channel type requested.

0xc5: Requested facility not implemented
This cause indicates that the equipment
sending this cause does not support the re-
quested supplementary service.

0xc6: Only restricted digital information bearer capability is available
This cause indicates that one equipment has
requested an unrestricted bearer service but
that the equipment sending this cause only
supports the restricted version of the request-
ed bearer capability.

0xcf: Service or option not implemented, unspec.
This cause is used to report a service or op-
tion not implemented event only when no
other cause in the service or option not im-
plemented class applies.


3.5 Invalid message class
------------------------------------------------------------------------------
0xd0: Invalid call reference value
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.

0xd2: Identified channel does not exist
This cause indicates that the equipment
sending this cause has received a request to
use a channel not activated on the inter-
face for a call. For example, if a user has sub-
scribed 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 to 30 this cause is generat-
ed.

0xd3: A suspended call exists, but this call identity does not
This cause indicates that a call resume has
been attempted with a call identity which
differs from that in use for any presently sus-
pended call(s).

0xd4: Call identity in use
This cause indicates that the network has re-
ceived a call suspend request. The call sus-
pend request contained a call identity (in-
cluding the null call identity) which is already
in use for a suspended call within the domain
of interfaces over which the call might be re-
sumed.

0xd5: No call suspended
This cause indicates that the network has re-
ceived a call resume request. The call
resume request contained a call identity in-
formation element which presently does not
indicate any suspended call within the do-
main of interfaces over which calls may be
resumed.

0xd6: Call having the requested call identity has been cleared
This cause indicates that the network has re-
ceived a call resume request. The call
resume request contained a call identity in-
formation element which once indicated a
suspended call; however, that suspended
call was cleared while suspended (either by
network timeout or by the remote user).

0xd8: Incompatible destination
This cause indicates that the equipment
sending this cause has received a request to
establish a call which has a low layer com-
patibility, high layer compatibility or other
compatibility attributes (e.g. data rate)
which cannot be accommodated.

0xdb: Invalid transit network selection
This cause indicates that a transit network
identification was received, which is of an in-
correct format.

0xdf: Invalid message, unspecified
This cause is used to report an invalid mes-
sage event only when no other cause in the
invalid message class applies.


3.6 Protocol error class
------------------------------------------------------------------------------
0xe0: Mandatory information element is missing
This cause indicates that the equipment
sending this cause has received a message
which is missing an information element
which must be present in the message be-
fore that message can be processed.

0xe1: Message type non-existent or not implemented
This cause indicates that the equipment
sending this cause has received a message
with a message type it does not recognise ei-
ther because this is a message not defined or
defined but not implemented by the equip-
ment sending this cause.

0xe2: Message not compatible with call state
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.

0xe3: Information element non-existent or not implemented
This cause indicates that the equipment
sending this cause has received a message
which includes information elements not rec-
ognised because the information element
identifier is not defined or it is defined but not
implemented by the equipment sending the
cause. 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.

0xe4: Invalid information element contents
This cause indicates that the equipment
sending this cause has received an informa-
tion element which it has implemented;
however, one or more fields in the informa-
tion element are coded in such a way which
has not been implemented by the equip-
ment sending this cause.

0xe5: Message not compatible with call state
This cause indicates that a message has
been received which is incompatible with
the call state.

0xe6: Recovery on timer expiry
This cause indicates that a procedure has
been initiated by the expiry of a timer in as-
sociation with error handling procedures.

0xef: Protocol error, unspecified
This cause is used to report a protocol error
event only when no other cause in the proto-
col error class applies.


3.7 Interworking class
------------------------------------------------------------------------------
0xff: Internetworking, unspecified
This cause indicates that there has been in-
terworking with a network which does not
provide causes for actions it takes; thus the
precise cause for a message which is being
sent cannot be ascertained.

4. CAPI-Errorcodes
---------------------------------------------
Ausgegeben werden die Fehlermeldungen im APITRACE in hex und Klartext
Ausserdem werden CAPI Fehlercodes auch im ISIPCTL ACCOUNT bzw ISIPCTL DEBUG
protokolliert.

CAPI error codes:
-----------------
classes:
--------

0x10xx
message queue errors or wrong coded messages
0x20xx
wrong capi address format
0x31xx
wrong parameters or wrong mode
0x32xx
not supported modes
0x33xx
network error
0x34xx
network messages or causes
0x40xx
fax error messages

{ 0x1001, "application registration error" },
{ 0x1002, "wrong application id" },
{ 0x1003, "message error" },
{ 0x1004, "wrong api command" },
{ 0x1005, "message queue full" },
{ 0x1006, "message queue empty" },
{ 0x1007, "messages lost" },
{ 0x1008, "error during deinstallation" },
{ 0x3309, "abort b-channel layer 2" },
{ 0x330a, "abort b-channel layer 3" },
{ 0x330b, "reestablish b-channel layer 2" },
{ 0x330c, "reestablish b-channel layer 3" },

{ 0x3480, "normal call clearing" },
{ 0x3481, "Invalid call reference value" },
{ 0x3483, "Bearer service not implemented" },
{ 0x3487, "Call identity does not exist" },
{ 0x3488, "Call identity in use" },
{ 0x348a, "No channel available" },
{ 0x3490, "Requested facility not implemented" },
{ 0x3491, "requested facility not subscribed" },
{ 0x34a0, "Outgoing calls barred" },
{ 0x34a1, "User Busy" },
{ 0x34a2, "negativer GBG-Vergleich" },
{ 0x34a5, "als SPV nicht erlaubt" },
{ 0x34b0, "Reverse charging not allowed at origination" },
{ 0x34b1, "Reverse charging not allowed at destination" },
{ 0x34b2, "Reverse charging rejected" },
{ 0x34b5, "Destination not obtainable" },
{ 0x34b8, "Number changed" },
{ 0x34b9, "Out of order" },
{ 0x34ba, "User not responding" },
{ 0x34bb, "User access busy" },
{ 0x34bd, "Incomming calls barred" },
{ 0x34be, "Call rejected" },
{ 0x34d9, "Network congestion" },
{ 0x34da, "Remote user initiated" },
{ 0x34f0, "Local procedure error" },
{ 0x34f1, "Remote procedure error" },
{ 0x34f2, "Remote user suspended" },
{ 0x34f3, "Remote user resumed" },
{ 0x34ff, "User info discarded locally" },
{ 0x34a3, "Non existant CUG"

 

Wichtige Links

FAQ-Indexseite
 
If you have comments or suggestions, send email  at support@BinTec.DE