Error Codes

A problem with an X.25 application might be a result of a problem communicating with the PSDN or a problem with the remote host. When a problem causes your call to be cleared, you receive a diagnostic code in the form of two pairs of digits. The first pair indicates why the call was cleared; the second pair gives additional diagnostic information. The tables on the following pages specify the meanings for these numeric codes. Table C-1 specifies reasons for call-clearing. Table C-2 specifies diagnostic information in addition to the call-clearing cause.

In many instances, if you receive any of these error codes, you will need to contact your service provider. However, in some instances the error code may indicate a configuration problem that you can correct yourself.

A zero (00) call-clearing code indicates that the call-clearing request originated in the remote host. A non-zero call-clearing code indicates the call-clearing request originated in the PSDN.

For example, your call is cleared with a code 03 42. As specified in Table C-1, 03 indicates an invalid facility request. Table C-2 tells you that 42 (hex) means that a facility parameter (that you used) is not allowed. This combination of messages tells you that:

1. The problem was detected by the PSDN, not by the remote host.

2. One or more parameter settings that you made in x25tool are unacceptable to the PSDN.

Often, a diagnostic gives only a general clue as to the source of a problem. For example, your call might be cleared with the code 00 42, indicating an invalid facility parameter setting. You might, in fact, have a facility parameter set to a value outside of the range of what you subscribed to. However, you can also receive this message if the maximum I-frame size is set to a size lower than the PSDN expects. Solstice X.25 clears the call rather than allow it to start and possibly fail later.

If you receive error code 00 42 and are not subscribing to any facilities, or are confident that your facilities parameters settings are correct, confirm that you and your PSDN agree on the maximum I-frame size. Remember that any adjustment of the maximum I-frame size, a LAPB parameter, might also require a change to the default packet size parameter, at the X.25 Packet Layer. Use x25tool to modify your link configuration as necessary.

In Table C-1 note the four categories of codes, separated by the double horizontal lines:

• The first category, code 00, indicates that the call-clearing request originated with the remote host. The remaining codes, in all other categories, indicate that the call-clearing request originated within the PSDN.

• Codes in the second category (hexadecimal code 01 through 29) indicate problems between the PSDN and the remote host.

• Codes in the third category (hexadecimal code 03 through 13) indicate problems between the local host and the PSDN.

Codes in the fourth category (hexadecimal codes 05 through 15) indicate problems within the PSDN. Table C-1 lists the fourth category causes for call clearing codes:

Table C-1 Causes for Call Clearing

Hexadecimal Code	Decimal Code	Meaning
00	00	Originated by remote DTE
01	01	Number busy
09	09	Out of order
11	17	Remote procedure error
19	25	Reverse charging acceptance not subscribed
21	33	Incompatible destination
29	41	Fast select acceptance not subscribed
03	03	Invalid facility request
0B	0B	Access barred
13	19	Local procedure error
05	05	Network congestion
0D	13	Not obtainable
15	21	RPOA out of order

Table C-2 lists the X.25 diagnostic codes.

Table C-2 X.25 Diagnostic Codes

Hexadecimal Code	Decimal Code	Meaning
00	00	No additional information
01	01	Invalid P(S) (send-packet sequence number)
02	02	Invalid P(R) (receive-packet sequence number)
10-1F	16-31	Invalid packet type
20	32	Packet not allowed
21	33	Unidentifiable packet
22	34	Call on one-way logical channel
23	35	Invalid packet type on a permanent virtual circuit
24	36	Packet on an unassigned logical channel
25	37	Reject not subscribed to
26	38	Packet too short
27	39	Packet too long
28	40	Invalid general format identifier
29	41	Restart with nonzero in bits 1-4, 9-16
2A	42	Packet type not compatible with facility
2B	43	Unauthorized interrupt confirmation
2C	44	Unauthorized interrupt
30	48	Timer expired
31	49	For incoming call
32	50	For clear indication
33	51	For reset indication
34	52	For restart indication
40	64	Call setup problem
41	65	Facility code not allowed
42	66	Facility parameter not allowed
43	67	Invalid called address
44	68	Invalid calling address

Note in the table above that hexadecimal codes 0, 20, 30, and 40 (decimal 0, 32, 48, and 64) stand for general messages that include the specific conditions indicated by the codes that follow them. Your PSDN might return only the codes that stand for the general messages.

Table C-3 lists X.25 diagnostic codes that you might receive when you are running Solstice X.25 over the Connection-Oriented Network Service (CONS).

Table C-3 CONS Diagnostic Codes

Hexadecimal Code	Decimal Code	Meaning
Sent by CONS
E0	224	Unspecified
E1	225	Disconnect--transient
E2	226	Disconnect--permanent
E3	227	Reject--transient
E4	228	Reject--permanent
E5	229	QOS not available--transient
E6	230	QOS not available--permanent
E7	231	NSAP unreachable--transient
E8	232	NSAP unreachable--permanent
E9	233	Unspecified Reset
EA	234	Reset due to congestion
EB	235	Unknown NSAP
Sent by CONS user (TP0/TP2)
F0	240	Unspecified
F1	241	Normal disconnect
F2	242	Abnormal disconnect
F4	244	Reject--transient
F5	245	Reject--permanent
F6	246	No QOS--transient
F7	247	No QOS--permanent
F8	248	Incompatible NS user data
FA	250	User Reset

Note that you receive the reset codes, hexadecimal numbers E9, EA, and FA, in Reset Request/Indication packets. You receive the remaining codes in Clear Request/Indication packets.