There are several cases where it is necessary to map causes between this Recommendation and Recommendation X.25. ISDN networks shall use Table 6-5 and Table 6-6 to map the causes between Q.931 and X.25 messages. The figures in Appendix II describe some example situations.
Mapping of Q.931 cause fields to X.25cause field
Item |
Q.931 cause |
Code |
Q.931diagnostic |
X.25 cause |
Code |
X.25 diagnostic |
Code |
01 |
Unallocated (unassigned) number |
001 |
Condition: unknown, transient, permanent |
Not obtainable |
13 |
Invalid called address |
67 |
02 |
No route to destination |
003 |
Condition: unknown, transient, permanent |
Not obtainable |
13 |
Invalid called address |
67 |
03 |
Channel unacceptable |
006 |
(None) |
Remote procedure error |
17 |
Call set-up, call clearing or registration problem |
64 |
04 |
Normal call clearing |
016 |
Condition: unknown, transient, permanent |
DTE originated |
00 |
No additional information |
00 |
05 |
User busy |
017 |
(None) |
Number busy |
01 |
No logical channel available |
71 |
06 |
No user responding |
018 |
(None) |
Remote procedure error |
17 |
Call set-up, call clearing or registration problem |
64 |
07 |
User alerting, no answer |
019 |
(None) |
Remote procedure error |
17 |
Call set-up, call clearing or registration problem |
64 |
08 |
Call rejected |
021 |
Condition: unknown, transient, permanent + user applied diagnostics |
DTE originated |
00 |
No additional information |
00 |
09 |
Number changed |
022 |
New destination address |
Not obtainable |
13 |
Invalid called address |
67 |
10 |
Destination out of order |
027 |
(None) |
Out of order |
09 |
No additional information |
00 |
11 |
Invalid number format (incomplete number) |
028 |
(None) |
Local procedure error |
19 |
Invalid called address |
67 |
12 |
Normal, unspecified |
031 |
(None) |
DTE originated |
00 |
No additional information |
00 |
13 |
No circuit/channel available |
034 |
(None) |
Number busy |
01 |
No logical channel available |
71 |
14 |
Network out of order |
038 |
(None) |
Out of order |
09 |
No additional information |
00 |
15 |
Temporary failure |
041 |
(None) |
Out of order |
09 |
No additional information |
00 |
16 |
Switching equipment congestion |
042 |
Network identity |
Network congestion |
05 |
No additional information |
00 |
17 |
Requested circuit/channel available |
044 |
(None) |
Number busy |
01 |
No logical channel available |
71 |
18 |
Resources unavailable, unspecified |
047 |
(None) |
Network congestion |
05 |
No additional information |
00 |
19 |
Quality of service unavailable |
049 |
Condition: unknown, transient, permanent |
Network congestion |
05 |
No additional information |
00 |
20 |
Bearer capability not authorized |
057 |
Attribute number |
Incompatible destination |
33 |
No additional information |
00 |
21 |
Bearer capability not presently available |
058 |
Attribute number |
Remote procedure error |
17 |
Call set-up, call clearing or registration problem |
64 |
22 |
Service or option not available, unspecified |
063 |
(None) |
Remote procedure error |
17 |
Call set-up, call clearing or registration problem |
64 |
23 |
Bearer service not implemented |
065 |
Attribute numbers |
Incompatible destination |
33 |
No additional information |
00 |
24 |
Channel type not implemented |
066 |
Channel type |
Remote procedure error |
17 |
Call set-up, call clearing or registration problem |
64 |
25 |
Service or option not implemented, unspecified |
079 |
(None) |
Remote procedure error |
17 |
Call set-up, call clearing or registration problem |
64 |
26 |
Valid call reference value |
081 |
(None) |
Remote procedure error |
17 |
Call set-up, call clearing or registration problem |
64 |
27 |
Identified channel does not exist |
082 |
Channel identity |
Remote procedure error |
17 |
Call set-up, call clearing or registration problem |
64 |
28 |
Incompatible destination |
088 |
Incompatible parameter |
Incompatible destination |
33 |
No additional information |
00 |
29 |
Invalid message, unspecified |
095 |
(None) |
Remote procedure error |
17 |
Call set-up, call clearing or registration problem |
64 |
30 |
Mandatory information element is missing |
096 |
Information element identifier(s) |
Remote procedure error |
17 |
Call set-up, call clearing or registration problem |
64 |
31 |
Message type non-existent or not implemented |
097 |
Message type |
Remote procedure error |
17 |
Call set-up, call clearing or registration problem |
64 |
32 |
Message not compatible with call state or message type non-existent or not implemented |
098 |
Message type |
Remote procedure error |
17 |
Call set-up, call clearing or registration problem |
64 |
33 |
Information element non-existent or not implemented |
099 |
Information element identifier(s) |
Remote procedure error |
17 |
Call set-up, call clearing or registration problem |
64 |
34 |
Invalid information element contents |
100 |
Information element identifier(s) |
Remote procedure error |
17 |
Call set-up, call clearing or registration problem |
64 |
35 |
Message not compatible with call state |
101 |
Message type |
Remote procedure error |
17 |
Call set-up, call clearing or registration problem |
64 |
36 |
Recovery on timer expiry |
102 |
Timer number |
Remote procedure error |
17 |
Call set-up, call clearing or registration problem |
64 |
37 |
Protocol error, unspecified |
111 |
(None) |
Remote procedure error |
17 |
Call set-up, call clearing or registration problem |
64 |
38 |
Interworking, unspecified |
127 |
(None) |
Remote procedure error |
17 |
Call set-up, call clearing or registration problem |
64 |
NOTES 1. When clearing occurs during the X.25 data transfer phase, the procedure described in 6.4.1 should be used. 2. When a Q.931 RESTART message is received during the X.25 data transfer phase, switched virtual circuits shall be cleared with a clear indication packet containing cause No. 9, Out of order, with diagnostic No. 0, no additional information. Permanent virtual circuits shall have an X.25 reset packet sent with the same cause and diagnostic. |