Telecommunications - Configuration of X.25 Packet layer

7.1 CALL REQUEST PACKET

INCOMING CALL PACKET CALL REQUEST PACKET

+------------------------------------------------------------+

| GFI | LCN |pkt type| address | facil | facil | call user |

| LCGN | | H'0B' | block | len | | data |

+------------------------------------------------------------+

| | _ _

| | see per-user see extended

| | section format

| if A=0 _

| +------------------------------------------+

| | calling | called | calling | called |

| | adr len | adr len| address | address |

| | 4-bits | 4-bits | max 14 dgt| max 14dgt|

| +------------------------------------------+

| if A=1

| +------------------------------------------+

| | calling | called | calling | called |

| | adr len | adr len| address | address |

| | 1 byte | 1 byte | | |

| +------------------------------------------+

| |

| _

| +-----------------------------------+

| | TOA | NPI | address |

| | type of |numbering | digits |

| | address | plan | |

| | |indication| |

_ +-----------------------------------+

8 7 65 4321

------------

A D 01 LCGN

| | | | +---------------------------------------+

| | | +-----------|Logical Channel group number |

| | | +---------------------------------------|

| | +---------------|these two bytes are 01 for modulo 8 |

| | | 10 for modulo 128 |

| | +---------------------------------------+

| +-----------------|D-bit local-remote significance |

| +--------------------------------+

+-------------------|A-bit defines format of |

|address block |

+------------------------+

DTE +-------------+ DTE

---- CALL REQUEST ---_ | network |--- INCOMING CALL ---_

| (DCE) |

_--- CALL CONNECTED -- | |_-- CALL ACCEPTED ----

+-------------+

The call request packet is really the same as an incoming call packet, it is known as a call request packet when it goes from the customers equipment to the network and an incoming call packet when it goes from the network to the customers equipment.

On UK the following values should be used:

	UK(A)	UK(B)
A-bit	0	0
D-bit	0 (remote significance)	0 (local significance)
mod 8/mod128	modulo 8 only	modulo 8 modulo 128 if subscrib
LCGN	4 for bothway circuits 2 for incoming only 6 for outgoing only	4 for bothway 2 for incomng only 6 for outgoing only
Max facility field length	?	?
Maximum data	16 bytes	16 bytes
field length	128 for fast sel	128 for fast sel

A-bit and NPI/TOA address format is not implemented (this is a CCITT 88 feature).

---

7.2 CALL ACCEPTED PACKET

+------------------------------------------------------------+

| GFI | LCN |pkt type| address | facil | facil | call user |

| LCGN | | H'0F' | block | len | | data |

+------------------------------------------------------------+

| _-------------------------------------_

_ these fields are not mandatory in the

see call request basic format of call accepted packets

for coding see call request for coding

DTE DCE DCE DTE

---- CALL REQUEST ---_ --- INCOMING CALL ---_

_--- CALL CONNECTED -- _-- CALL ACCEPTED ----

The call connected packet is really the same as the call accepted packet, it is known as a call accepted packet when it goes from the customers equipment to the network and a call connected packet when it goes from the network to the customers equipment.

In order to send or receive the 'extended format' of the call accepted packet, extended format must be subscribed.

UK(A) - if extended format is not subscribed then outgoing calls will not be redirected.

UK(B) - *** non-enhanced port - check if field removed or call cleared.

A-bit and NPI/TOA address format is not implemented (this is a CCITT 88 feature).

Macro: BRFC - Enhanced or non-enhanced

7.3 CLEAR REQUEST PACKET

CLEAR INDICATION PACKET

An SVC can be cleared at any time by either DTE or by the network.

+--------------------------------------------------------------------------+

| GFI | LCN |pkt type| cause| diag | address | facil | facil | call user |

| LCGN | | H'13' | | | block | len | | data |

+--------------------------------------------------------------------------+

| | _ _-------------------------------------_

| | see below used only in the extended format

| | for codes see call request for coding

_ _

8 7 65 4321 +-----------------------------------------+

------------ |

A D 01 LCGN |

| | | | +---------------------------------------+ |

| | | +-----------|Logical Channel group number | |

| | | +---------------------------------------| |

| | +---------------|these two bytes are 01 for modulo 8 | |

| | | 10 for modulo 128 | |

| | +---------------------------------------+ _

| +-----------------|D-bit local-remote significance | |

| +--------------------------------+ |

+-------------------|A-bit defines format of | |

|address block | |

+------------------------+ |

|

+---------------_-------------------+

+---------------------------------------------------------------+

code	clear cause
HEX
00	DTE clearing
01	Number busy
03	Invalid call
05	Network congestion
09	Out of order - clear clear
0B	Access barred
0D	Not obtainable
11	Remote procedure error clear
11	incompatrocedure error clear
13	Local procedure error
15	RPOA out of order
19	Reverse charging not subscribed to
21	DTE incompatible call
29	Fast select not subscribed to
39	Ship absent ....................... not UK(a)
80-FF	DTE ............................... not UK(a)

The call can be cleared by either end (or in case of faults by the network) at any time during the call.

The CLEAR packet contains a 2 byte data field containing the cause and diagnostic bytes, these bytes give the reason for the clear and are therefore very useful for finding faults.

Clear by DTE

------------

DTE DCE DCE DTE

_-- CLEAR INDICATION 00dd -- _-- CLEAR REQUEST 00dd --

--- CLEAR CONFIRMATION --_ --- CLEAR CONFIRMATION --_

Clear by Network

----------------

DTE DCE DCE DTE

_-- CLEAR INDICATION ccdd -- -- CLEAR INDICATION ccdd --_

--- CLEAR CONFIRMATION --_ _--- CLEAR CONFIRMATION --

7.4 CLEAR CONFIRMATION PACKET

An SVC can be cleared at any time by either DTE or by the network.

+-----------------------------------------------+

| GFI | LCN |pkt type| address | facil | facil |

| LCGN | | H'17' | block | len | |

+-----------------------------------------------+

| _------------------------_

| used only in the extended format

| see call request for coding

_

8 7 65 4321

------------

A D 01 LCGN

| | | | +---------------------------------------+

| | | +-----------|Logical Channel group number |

| | | +---------------------------------------|

| | +---------------|these two bytes are 01 for modulo 8 |

| | | 10 for modulo 128 |

| | +---------------------------------------+

| +-----------------|D-bit local-remote significance |

| +--------------------------------+

+-------------------|A-bit defines format of |

|address block |

+------------------------+

Clear by DTE

------------

DTE DCE DCE DTE

_-- CLEAR INDICATION 00dd -- _-- CLEAR REQUEST 00dd --

--- CLEAR CONFIRMATION --_ --- CLEAR CONFIRMATION --_

Clear by Network

----------------

DTE DCE DCE DTE

_-- CLEAR INDICATION ccdd -- -- CLEAR INDICATION ccdd --_

--- CLEAR CONFIRMATION --_ _--- CLEAR CONFIRMATION --

7.5 DATA PACKET 7.5 DATA PACKET.............................................#

modulo 8 format

+-----------------------------------------------+

| GFI | LCN |pkt type| user data |

| LCGN | |xxxxxxx0| |

+-----------------------------------------------+

|

| p(r) M p(s) 0

| _-_ _ _-_ _

| 3 bits 1 bit 3 bits 1 bit

| sequence _ sequence iden as data packet

| number | number

| |

| more data bit

| used when packet is full to say next packet

| is continuation of this one

_

8 7 65 4321

------------

Q D 01 LCGN

| | | | +---------------------------------------+

| | | +-----------|Logical Channel group number |

| | | +---------------------------------------|

| | +---------------|these two bytes are 01 for modulo 8 |

| | +---------------------------------------+

| +-----------------|D-bit local-remote significance |

| +--------------------------------+

+-------------------|Q-bit used with PAD |

+------------------------+

modulo 128 format

+--------------------------------------------------------+

| GFI | LCN | P(s) 0 | P(r) M | user data |

| LCGN | | | | |

+--------------------------------------------------------+

|

_

8 7 65 4321

------------

Q D 10 LCGN

| | | | +---------------------------------------+

| | | +-----------|Logical Channel group number |

| | | +---------------------------------------|

| | +---------------|these two bytes are 10 for modulo 128 |

| | +---------------------------------------+

| +-----------------|D-bit local-remote significance |

| +--------------------------------+

+-------------------|Q-bit used with PAD |

+------------------------+

The M-bit and D-bit should be set according to the following table:

Data packet sent by source DTE
Category	M	D	Full
B	0 or 1	0	no	_- originating network
B	0	1	no	will force the M-bit
B	1	1	no	to 1
B	0	0	yes
B	0	1	yes
A	1	0	yes
B	1	1	yes

Coding of fields - UK(A)

| Q-bit is transmitted through the network transparently for X.25 to X.25 calls.

| D-bit is always set to 0

| M-bit can be set to 1 in full data packet, otherwise it is

set to zero

| User Data must be an itergral number of Bytes, maximum length is 128 bytes unless higher packet sizes have been negotiated.

| Remote significance is always used for acknowledgements, if larger packet and window sizes have been negotiated they must be supported at both ends of the call. No concatenation or division of Data Packets is performed by the Network.

| modulo 128 is not supported on UK(A) lines.

Coding of fields - UK(B)

| Q-bit is transmitted through the network transparently for X.25 to X.25 calls.

| D-bit is always set to 0

| M-bit can be set to 1 in full data packet, otherwise it is

set to zero, if the M-bit is set to one and the remote end

is operating with a larger packet size, the network may

concaternate the packets into one. In the reverse direction

larger packets may be divided by the network into smaller

packets with the M-bit set, the final packet will always

have M-bit=0.

| User Data must be an itergral number of Bytes, maximum length is 128 bytes unless higher packet sizes have been negotiated.

| Local significance is always used for acknowledgements, if larger packet and window sizes have been negotiated concatenation or division of Data Packets may be performed by the Network.

| Remote significance will be supported at release 6.

Local Significance is a fundamental change from Remote significance which is used on UK(a). It means that the fact that a data packet has been acknowledged does not guarantee that it has been received at the destination. If the sender needs to be sure that data has arrived, then a higher level protocol will be needed.

UK(b) will support remote significance from release 6, however we will need to check the efficiency of this.

8.4 - D-bit

Local acknowledgement of data not supported by current Public Network network.

Data field length of 2048 or 4096

Not supported by UKa. Negotiated down to 1024.

ONA compatibility

RD 0004 part 8:1.C (PICS proforma Public Network1984)

DCN - Is D-bit negotiation supported:

DCN1 - for outgoing VCs.... M = Mandatory

DCN2 - for incoming Vcs.... M = Mandatory

RD 0004 part 3:2.C (connection mode service over UKa 1984)

M-Bit processingM-Bit processing

M-bit will now be checked against the above table from X.25:

7.6 RR PACKET

modulo 8 format

	LCN	pkt type
0001 LCGN		P(r) 0 000 1

modulo 128 format

	LCN	00000001	P(r) 0
0010 LCGN

RR packets are used to acknowledge data packets on a given logical channel.

UK(a) - RR packets will be sent all through the network, therefore the remote end can be polled by sending an RR packet. Modulo 128 is not supported.

UK(b) - RR packets are local. If required as a subscription option, the network can poll on each logical channel at regular intervals, if no data is received.

7.7 RNR PACKET

modulo 8 format

	LCN	pkt type
0001 LCGN		P(r) 0 010 1

modulo 128 format

	LCN	00000101	P(r) 0
0010 LCGN

Used to indicate a busy condition on a give logical channel.

We need to understand more about the UK(b) busy condition and UK(b) congestion mechanisms.

7.8 REJ PACKET

modulo 8 format

	LCN	pkt type
0001 LCGN		P(r) 0 100 1

modulo 128 format

	LCN	00001001	P(r) 0
0010 LCGN

Used to request retransmission of data that has already been received but not acknowledged. This is not normally needed since the link level ensures error free reception of the data.

UK(a) - always supported, not a subscription option.

UK(b) - not supported

7.9 RESET REQUEST PACKET

RESET INDICATION PACKET

An SVC can be reset at any time by either DTE or by the network.

GFI	LCN	pkt type	cause	diag
LCGN		H'1B'

_ _

| see below for coding

code	Reset cause
HEX
00	DTE clearing
01	out of order
03	remote procedure error
05	local procedure error
07	Network cogestion Reset
09	Remote DTE operational - reset reset
0F	Network operational
11	incompatible destination
1D	Network out of order
80-FF	DTE ............................... Not UK(a)

Reset by DTE

------------

DTE DCE DCE DTE

_-- RESET INDICATION 00dd -- _-- RESET REQUEST 00dd --

--- RESET CONFIRMATION --_ --- RESET CONFIRMATION --_

Reset by Network

----------------

DTE DCE DCE DTE

_-- RESET INDICATION ccdd -- -- RESET INDICATION ccdd --_

--- RESET CONFIRMATION --_ _--- RESET CONFIRMATION --

7.10 RESET CONFIRMATION PACKET

An SVC can be reset at any time by either DTE or by the network.

GFI	LCN	pkt type
LCGN		H'1F'

7.11 INTERRUPT PACKET

GFI LCGN	LCN	pkt type	user data
		H'23'

Maximum length of user data field:

UK(A):	1 byte
UK(B):	1 byte
	32 bytes from release 5

All DX2 users will be able to use 32 bytes (not a subscription option)

*** need to check if supported on DX1 (I dont think so)

CCITT '84 increases the maximum length of the data field in an Interrupt packet from 1 byte to 32 bytes.

ONA compatibility

B1 - INTERRUPT packets with data field longer than 1 octet

interrupt packets are not required by ONA - so this is not applicable - so no problems with compatibility

Implementation issues

need to check what happens when a 1984 user makes a call to a 1980 user and sends a 32 byte interrupt.

7.12 INTERRUPT CONFIRMATION PACKET

GFI LCGN	LCN	pkt type
		H'27'

CCITT '84 increases the maximum length of the data field in an Interrupt packet from 1 byte to 32 bytes.

All DX2 users will be able to use 32 bytes (not a subscription option)

*** need to check if supported on DX1 (I dont think so)

ONA compatibility

B1 - INTERRUPT packets with data field longer than 1 octet

interrupt packets are not required by ONA - so this is not applicable. so no problems with compatibility

Implementation issues

need to check what happens when a 1984 user makes a call to a 1980 user and sends a 32 byte interrupt.

7.13 RESTART REQUEST PACKET

RESTART INDICATION PACKET

GFI LCGN	LCN	pkt type	cause	diagnostic
		H'FB'

_

code	Restart cause sent by network
HEX
01	local procedure error
03	network congestion
07	network operational
7F	registration/cancellation confirmed (not UK(a))
code	Restart cause sent by DTE
HEX
00	DTE restart

7.14 RESTART CONFIRMATION PACKET

GFI LCGN	LCN	pkt type
		H'FF'

Once the link is established then the packet level is initialised. This ensures packet level starts in a tidy state with all calls cleared. This can be done by either end,

Restart by network: UK(a)

customer network

_--- RESTART IND 07FA --- | cause 07 network operational

---- RESTART CONF ------_ | diagnostic FA line status change

Restart by network: UK(b)

customer network

_--- RESTART IND 0700 --- |

---- RESTART CONF ------_ |

Restart by customer:

customer network

---- RESTART REQ 00xx ----_

_--- RESTART CONF ---------

Restart collision:

------ RESTART REQ -----_

_----- RESTART IND ------

Following a link level failure, calls should not be made or accepted until a Restart exchange has occurred.

Restart - Restart Conf exchanges can be done at any time and will have the effect of clearing all calls on the link.

Note: RESTART and RESTART CONF are the only packet types which affect all calls on the link and so they always use GFI=10, LCN=0, see section on logical channel numbers for details.

7.15 on-line facility registration

REGISTRATION REQUEST PACKET

GFI LCGN	LCN	pkt type	address	regist	registration
		H'F3'	block	len

ONA compatibility

RD 0004 part 8:1.C (PICS proforma Public Network1984)

Z4i - initiating on-line facility registration.. P = Prohibited

Z4r - response to on-line facility registration.. -

Therefore release 4 is compatible with ONA for this option.

7.16 REGISTRATION CONFIRMATION PACKET

GFI LCGN	LCN	pkt type	cause	diag	address block	regist len	registration
		H'F7'

code	Registration cause (not UK(a))
HEX
03	remote procedure error
05	network congestion
13	local procedure error
7F	registration/cancellation confirmed

&internal& = yONA compatibility

RD 0004 part 8:1.C (PICS proforma Public Network1984)

Z4i - initiating on-line facility registration.. P = Prohibited

Z4r - response to on-line facility registration.. -

UK(A): Online Registration not supported.

UK(B): The following facilities may be negotiated from release 5:

Incomming calls barred

Outgoing calls barred

Non-standard default packet size

Non standard default window size

Default throughput class assignment

Flow control parameter negotiation

Throughput class negotiation

Fast select acceptance

Reverse charging acceptance

Allocation of logical channel type ranges

I assume on-line registration will be used for X.32 only.

7.17 DIAGNOSTIC PACKET

GFI	LCN	pkt type	DIAGNOSTIC	diagnostic
LCGN		H'F1'	code	explanation

This packet type is not supported by UK.

7.18 Diagnostic Codes CCITT defined diagnostics

---------------------------------------------------------------

value in	diagnostics	UK(a)	UK(b)
dec	hex
00	1	No additional information		¹
01	1	INVALID P(S)	RESET	¹
02	2	INVALID P(R)	RESET	¹
16	10	packet type invalid (general)	NR4	¹
17	11	for STATE r1 (pkt level ready)	RESTAR	¹
18	12	for STATE r2 (DTE restart)	RESTAR	¹
19	13	for STATE r3 (DCE restart)	RESTAR	¹
20	14	for STATE p1 (ready state)	CLEAR	¹
21	15	for STATE p2 (DTE waiting)	CLEAR	¹
22	16	for STATE p3 (DCE waiting)	CLEAR	¹
23	17	for STATE p4 (data transfer)	CLEAR	¹
24	18	for STATE p5	RESET	x
25	19	for STATE p6 (DTE clear)	CLEAR	¹
26	1A	for STATE p7 (DCE clear)	CLEAR	¹
27	1B	for STATE d1 (flow control rdy)	RESET	¹
28	1C	for STATE d2 (DTE reset)	RESET	¹
29	1D	for STATE d3 (DCE reset)	RESET	¹
32	20	PACKET NOT ALLOWED		¹
33	21	UNIDENTIFIABLE PACKET		¹
34	22	CALL ON ONE-WAY LOGICAL CHANNEL	CLEAR	¹
35	23	INVALID PACKET TYPE ON PVC	RESET	¹
36	24	PACKET ON UNASSIGNED LCN	CLEAR	¹
37	25	REJECT NOT SUBSCRIBED TO	RESET	¹
38	26	PACKET TOO SHORT	RESET	¹
39	27	PACKET TOO LONG	RESET	¹
40	28	INVALID GFI	CLEAR	¹
41	29	RESTART WITH NON-ZERO BITS 1-4,9-16		¹
42	2A	PACKET TYPE NOT COMPATIBLE WITH FACILITY	CLEAR	¹
43	2B	UNAUTHORISED INTERRUPT CONF	RESET	¹
44	2C	UNAUTHORISED INTERRUPT	RESET	¹
45	2D	unauthorised reject	no	r5
48	30	timer expired (general)	nr4	¹
49	31	for INCOMING CALL		¹
50	32	for CLEAR INDICATION		¹
51	33	for RESET INDICATION		¹
52	34	for RESTART ind/req		¹
value in	diagnostics	UK(a)	UK(b)
dec	hex
64	40	call set-up, call clearing or reg prob	CLEAR	¹
65	41	FACILITY/registration code not allowed	CLEAR	¹
66	42	FACILITY PARAMETER NOT ALLOWED	CLEAR	¹
67	43	INVALID CALLED ADDRESS	CLEAR	¹
68	44	INVALID CALLING ADDRESS	CLEAR	¹
69	45	invalid facility/registration length	not r4	r5
70	46	incoming call barred	not r4	r5
71	47	no logical channel available	not r4	r5
72	48	call collision	not r4	r5
73	49	duplicate facility/utility requested	not r4	r5
74	4A	non-zero address length	not r4	r5
75	4B	non-zero facility length	not r4	r5
76	4C	facility/utility not prov when expected	not r4	r5
77	4D	invalid CCITT - specified DTE facility	not r4	r5
78	4E	max number redirections/deflec exceeded	x	r6
80	50	miscellaneous	not r4	r5
81	51	improper cause code from DTE	not r4	r5
82	52	not aligned octet	not r4	r5
83	53	inconsistent Q-bit setting		r5
84	54	NUI problem	x	r6
		96-103 X.75 only
96	60	international call setup/clearing probl	nr4	r5
97	61	unknown calling DNIC	nr4	r5
98	62	TNIC mismatch	nr4	r5
99	63	call identifier mismatch	nr4	r5
100	64	negotiation error in Utility param value	nr4	r5
101	65	invalid utility length	nr4	r5
102	66	non-zero utility length	nr4	r5
103	67	M-bit violation	nr4	r5
112	70	international problem (general)	not r4	r5
113	71	remote network problem	not r4	r5
114	72	international protocol problem	not r4	r5
115	73	international link out of order	not r4	r5
116	74	international link busy	not r4	r5
117	75	transit network facility problem	not r4	r5
118	76	remote network facility problem	not r4	r5
119	77	international routing problem	not r4	r5
120	78	temporary routing problem	not r4	r5
121	79	unknown called DNIC	not r4	r5
122	7A	maintenance action (national/internat)	not r4	r5

---------------------------------------------------------------

Diagnostic Codes UK(a) network dependant diagnostics

---------------------------------------------------------------

128	80	Proto clearing - standard clearing cause
129	81	not used
130	82	subline down
131	83	unable to reformat packet
132	84	No slave side for call accept packet
133	85	packet received with X.25 line in wrong state
134	86	insufficient buffers to complete call
135	87	timer expired
136	88	interrupt confirmation received while no
		outstanding interrupts
137	89	P(s) received from slave not equal to what
		proto expects
138	8A	not used - reserved for proto
143	8F	not used - reserved for proto
144	90	DTE/DCE CONGESTION RESET
145	91	RECEIVED FAST SELECT CLEAR REQUEST
146	92	LINE RESTARTING BY DEBUG COMMAND RESTART
147	93	invalid restart confirm in state R3 nr4
148	94	looped trunk lines detected nr4
149	95	invalid length trunk restart nr4
150	96	call quota distribution clear nr4
151	97	reconnect multiple race nr4
152	98	reconnect race timeout at destination nr4
153	99	VH call to DTE which isnt a VH nr4
154	9A	requires security key nr4
155	9B	non-matching security key nr4
156	9C	DNIC utility barred nr4
157	9D	Local charging prevention nr4
158	9E	Invalid Traffic priority nr4
159	9F	Network table overflow nr4
160	A0	NON-ZERO RESET CAUSE FROM DTE RESET
161	A1	DATA PACKET TOO LONG RESET
162	A2	INTERRUPT PACKET TOO LONG RESET
163	A3	INT PACKET TOO SHORT; NO USERDATA RESET
164	A4	INT CONFIRMATION PACKET TOO LONG RESET
165	A5	RR PACKET TOO LONG RESET
166	A6	RNR PACKET TOO LONG RESET
167	A7	RESET PACKET TOO LONG RESET
168	A8	RESET CONF PACKET TOO LONG RESET
169	A9	INVALID `Q' BIT IN DATA PACKET RESET
170	AA	PACKET WINDOW RANGE EXCEEDED RESET
171	AB	UNABLE TO TRANSMIT PACKET RESET
172	AC	`Q' BIT SET IN NON-DATA PACKET RESET
173	AD	OUTSTANDING PACKET COUNT LESS THAN ZERO RESET
174	AE	RETRANSMISSION queue ERROR RESET
175	AF	RESET PACKET TOO SHORT (NO CAUSE) RESET
176	B0	REJECT PACKET TOO LONG RESET
177	B1	INVALID 1D PACKET RESET
178	B2	UNSUCCESSFUL RECONNECTION RESNC CLEAR
179	B3	NON-RECONNECT CALL IN STATE C1 CLEAR
180	B4	SECOND 1D PACKET FROM DTE CLEAR
181	B5	BAD DATA TRANSFER STATE IN RECONNECT CLEAR
182	B6	PACKET FORMAT INVALID CLEAR
183	B7	FACILITY BYTE COUNT TOO LARGE CLEAR
184	B8	INVALID PACKET DETECTED CLEAR
185	B9	FACILITY/UTILITY FIELD BYTE COUNT > 109 CLEAR was 63
186	BA	OUTGOING CALLS BARRED CLEAR
187	BB	INCOMING CALLS BARRED CLEAR
188	BC	CLEARING OF PVC CLEAR
189	BD	CALLED ADDRESS TOO LONG CLEAR
190	BE	CALLED ADDRESS TOO SHORT CLEAR
191	BF	CALLING ADDRESS TOO LONG CLEAR
192	C0	CALLING ADDRESS TOO SHORT CLEAR
193	C1	BCD ERROR IN CALL ADDRESS CLEAR
194	C2	BCD ERROR IN CALLING ADDRESS CLEAR
195	C3	USER DATA FIELD TOO LONG CLEAR
196	C4	NO BUFFER AVAILABLE CLEAR
197	C5	LOCAL DTE IS NOT ENHANCED CLEAR
198	C6	FACILITY NEGOTIATION INVALID CLEAR
199	C7	MANDATORY UTILITY NOT present CLEAR
200	C8	quarter BUFFER NO AVAILABLE FOR TNIC CLEAR
201	C9	OVERFLOW OF TNIC IN BUFFER CLEAR
202	CA	DTE LINE CONGESTED CLEAR
203	CB	TABLE ERROR IN PACKET PROCEDURES
204	CC	INSERT TABLE OVERFLOW
205	CD	DELETE TABLE OVERFLOW (extended XLB not present)
206	CE	call forward procedure error nr4
207	CF	call forward reset nr4
208	D0	TRUNK LINE RESTART RESTART
209	D1	INVALID EVENT IN STATE p2
210	D2	INVALID EVENT IN STATE p3
211	D3	INVALID 1D EVENT IN STATE d1
212	D4	CALL COLLISION ON TRUNK LINE
213	D5	NO BUFFER AVAILABLE for EXCB
214	D6	CALL COLLISION ON DTE LINE
215	D7	DTE RESTART
216	D8	CALL REQUEST TO TRUNK LINE Timed OUT
217	D9	RECONNECT SET-UP TIMED OUT
218	DA	INVALID OUTPUT SIDE STATE
219	DB	ERROR DETECTED IN BLINK PACKET QUEUE PROCEDURE
220	DC	RESET INDICATION RETRANSMISSION COUNT EXPIRED
221	DD	INVALID OUTPUT SIDE STATE
222	DE	BLIND BUFFER QUEUE OVERFLOW IN STATE d4
223	DF	BLIND BUFFER QUEUE OVERFLOW IN STATE c1
224	E0	BLIND BUFFER QUEUE OVERFLOW IN STATE c2
225	E1	CLEAR PACKET BYTE COUNT TOO LARGE OR TOO SMALL
226	E2	NON-ZERO CLEAR CAUSE
227	E3	CLEAR CONF PACKET BYTE COUNT TOO SMALL OR TOO LARGE
228	E4	CALL COLLISION
229	E5	INVALID TP LOAD REQUEST CALL PKT
230	E6	MAXIMUM	OPCOUNT EXCEEDED
231	E7	ROUTING LOOP DETECTED
232	E8	PVC CALL REQUEST FAILURE
233	E9	RECONNECT CALL REQUEST FAILED
234	EA	NO LC AVAILABLE ON OUTPUT XLB
235	EB	NO BUFFER AVAILABLE for txcb
236	EC	CALL REDIRECTION CLEAR
237	ED	NO PATH ROUTE CALL
238	EE	CALL ROUTED TO DTE LINE
239	EF	CALL CANNOT BE REROUTED
240	F0	ADDRESS NOT IN ROUTING TABLES
241	F1	ROUTING TABLE CHANGE DURING CALL ROUTING
242	F2	NO LC AVAILABLE ON FAKE TRUNK line
243	F3	REMOTE DTE DOWN ON A PVC
244	F4	INVALID EVENT DETECTED no xxcb or no call
245	F5	INVALID PACKET RECEIVED; STATE d4
246	F6	INVALID PACKET RECEIVED; STATE d5
247	F7	INVALID PACKET RECEIVED; STATE p8
248	F8	INTERNAL PROCESSING FAILURE getarea fail
249	F9	INVALID RESTART INDICATION
250	FA	LINE STATUS CHANGE IN STATE r5 down>up
251	FB	INVALID PACKET RECEIVED; STATE r5
252	FC	INVALID PACKET RECEIVED; STATE r4
253	FD	LINE STATUS CHANGE IN STATE r3 up>down
254	FE	LINE STATUS CHANGE IN STATE r2 up>down
255	FF	LINE STATUS CHANGE IN STATE r1 up>down

NETWORK SPECIFIC DIAGNOSTIC CODES (128-) UK(b)

128	80	INTERNAL MULFUCTION:
		DPORT NOT ASSIGNED WHEN PROCESSING DATA PKT
		DPORT NOT ASSIGNED WHEN PROCESSING LEV1 PKT
129	81	MEANING DEPENDING ON CAUSE CODE
130	82	MEANING DEPENDING ON CAUSE CODE
131	83	BAD MUD SUP MSG RECEIVED
133	85	NO HOST SUP MSG RECEIVED
134	86	MUD ERROR SUP MSG RECEIVED
135	87	CALLING ADDRESS DOES NOT MATCH CHKCLG(adr)
136	88	RCVD CALL REQUEST ON DTE CLEAR STATE (X.75)
137	89	---- RESERVED ----
138	8A	LOGIN ERROR
139	8B	LOGIN ERROR - "ERROR, TYPE USERNAME" RCVD
140	8C	RECEIVED CLEAR WHEN GETTING NEEDLE RESPONSE
141	8D	AUX CIRCUIT TIME OUT WHILD SENDING CALL ACCEPT
142	8E	LOGIN TIME OUT
143	8F	INFOSWITCH- CALL ACCEPT TIME OUT
144	90	BREAK GENERATED RESET
		THE FOLLOWING IS REPLACED BY 1984 CODE 117 OR 118
145	91	ILLEGAL FACILITY REQUEST (X.75)
146	92	NON CCITT DEFINED PROTOCOL ID
		OR PROTOCOL ID FIELD TOO SHORT
147	93	CALL USER DATA FIELD IN CALL ACCEPT
148	94	DIALECT RESPONSE NOT RECOGNIZABLE/
		CANNOT ACCEPT ANY DIALECT CHOICES OFFERED
		THE FOLLOWING HAS BEEN REPLACED BY 1984 CODE 83
149	95	Q BIT VIOLATION
		LAST PACKET M=1,Q=1, BUT THIS HAS Q=0,
		LAST PACKET Q=0,M=1, BUT THIS HAS Q=1
		changed to INVALID GFI(DIAGNOSTIC 40) NR5
150	96	Q BIT SET ON NON DATA PACKET
		changed to DIAGNOSTIC 38 NR5
151	97	CALL USER DATA FIELD TOO LONG, >16 FOR
		NON-FAST SELECT, >128 FOR FAST SELECT
152	98	DATA LOST IN NETWORK, RCVD BLK BALL OR GRY BALL
		153 TO 168 LOGON FAILURE OR PSEUDO-NEEDLE REJECT
		REASON FOR FAILURE:
153	99	ISIS OR NODE UNABLE TO COMPLETE REQUEST
154	9A	FORMAT ERROR:HJR-SWBT1
155	9B	BAD USER NAME
156	9C	BAD MUD
157	9D	SYSTEM UNAVAILABLE
158	9E	DOWN-LINE LOAD OR DIAL-OUT FAILURE
159	9F	TIMEOUT
160	A0	ACCESS NOT PERMITTED
161	A1	OUT OF ORIGINATION PORTS
162	A2	TRY AGAIN LATER
163	A3
164	A4	WHEN CAUSE 0, AN ISIS HANG MSG IS SENT TO
		PHYSICALLY DISCONNECT THE LINE ON A CLEAR PKT
165	A5	BAD REQUESTING HOST NUMBER
166	A6	REQUESTING HOST NOT UP ON THIS NODE
169	A9	A DSP DIALECT CHOICE WAS OFFERED, BUT
		IT WAS ANOT A DSP CALL
170	AA	X TO X (TURKEY) LEVEL RESPONSE GREATER THAN OUR LEVEL
171	AB	A DSP CALL DID NOT GET DSP DIALECT OFFERED
		AS A IIX DIALECT COMMAND CHOICE
172	AC	BUFFER ZAP OCCURED FOR THIS CHANNEL
173	AD	CALL RESET - UNAVAILABLE PMP BLOCK
174	AE	ERROR IN RECEIVED CLEAR REQUEST PACKET
175	AF	RCVD ILLEGALY FORMATTED INTERNAL MSG
176	B0	RCVD UNIMPLEMENTED GLOBAL IIX MESSAGES
		THIS DAIGNOSTIC HAS BEEN REPLACED BY 1984 CODE 122
177	B1	XOM OPERATOR BROUGHT PACKET LEVEL DOWN
178	B2	REC'VD RPOA FOUND IN ODNIC
		THIS DAIGNOSTIC HAS BEEN REPLACED BY 1984 CODE 119
179	B3	RECEIVED UNKNOWN RPOA
180	B4	RECEIVED ERRONEOUS CALL ACCEPT INTERNAL MSG
181	B5	NATIONAL OPTIONS IN CALL REQUEST
182	B6	OUTGOING CALLS BARRED WITHIN CUG,
		OR CUG WITH NO OUTGOING ACCESS FACILITY
183	B7	INCOMING CALLS BARRED WITHIN CUG,
		OR CUG WITH NO INCOMING ACCESS FACILITY
		THIS DIAGNOSTIC HAS BEEN REPLACED BY 1984 CODE 73
184	B8	DUPLICATED APPERANCE OF FACILITY CODE
185	B9	REQUESTED PS NOT ACCEPTABLE IN FLOW NEGOTIATION
186	BA	REQUSTED WS NOT ACCEPTABLE IN FLOW NEGOTIATION
187	BB	NON EXISTENT CUG
		THIS DIAGNOSTIC HAS BEEN REPLACED BY 1984 CODE 99
188	BC	MISSING CALLL ID UTILITY IN CAL REQUEST PAKCET
189	BD	DESTINATION DOES NOT UNDERSTAND CUG
190	BE	CALL REQUEST ON ALREADY ASSIGNED CHANNEL
191	BF	XOM WANTS NO MORE CALLS
192	C0	NO AVAILABLE INTERNAL PORT TO ASSGIN WHEN RCV CALL REQ
193	C1	NO MATCHED NATIONAL INTERLOCK CODE IN
		CUGMAPPING MACRO NR5
194	C2	INVALID listno USED IN CUGMAPPING MACRO NR5
195	C3	DNIC OF CALLED ADDRESS IS NOT IN THE GOOD
		CUGDNIC LIST NR5
196	C4	INVALID INTERLOCK CODE RECVD FROM ESPC 8C MSG NR5
197	C5	DNIC OF CALLING ADDRESS IS NOT IN THE GOOD NR5
		CUGDNIC LIST
198	C6	NO MATCHED INTERNATIONAL INTERLOCK CODE IN NR5
		CUGMAPPING MACRO
199	C7	DIAG. CODE FOR DCD OFF JH
200	C8	DIAG. CODE FOR LINE IDLE JH
201	C9	XLINK DTE DOES NOT RESPOND JH
202	CA	PAD REPORT PACKET WHICH ASYC. TERMINAL
		FAILS TO RESPONSE OR POWER GOES OFF JH
		203-9 *** RESERVED FOR LOG-II ***
203	CB	CIRCUIT REJECT CODE UNKNOWN
204	CC	NODE OUT OF BUFFERS
205	CD
206	CE	SUPERVISOR PROBLEM
207	CF	NODE CODE NOT PRESENT
210	D0	UNABLE TO SELECT LINK FOR INCOMING CALL
		diags 211 to 220 reserved for BOC applications
221	D1	ON-LINE REGISTRATION IN PROGRESS NR6
222	D2	LOGICAL CHANNEL RANGES OVERLAPPED, 1984,

 

EuclideanSpace

home