.rs
.\" Troff code generated by TPS Convert from ITU Original Files
.\"                 Not Copyright ( c) 1991 
.\"
.\" Assumes tbl, eqn, MS macros, and lots of luck.
.TA 1c 2c 3c 4c 5c 6c 7c 8c
.ds CH
.ds CF
.EQ
delim @@
.EN
.nr LL 40.5P
.nr ll 40.5P
.nr HM 3P
.nr FM 6P
.nr PO 4P
.nr PD 9p
.po 4P

.rs
\v | 5i'
.LP
\fBMONTAGE: REC.Q.763 EN\(hyT\* | TE DE CETTE PAGE\fR 
.sp 1P
.LP
\v'32P'
3.12
	\fICircuit state indicator\fR 
.sp 9p
.RT
.PP
The format of the circuit state indicator parameter field is shown in Figure\ 
15/Q.763. 
.RT
.LP
.rs
.sp 12P
.ad r
\fBFigure 15/Q.763, p.  \fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.PP
The number of octets in the circuit state indicator parameter
field is equal to the specified range\ +\ 1. Each circuit state indicator 
octet is associated with a circuit identification code such that octet\ 
n is 
associated with circuit identification code\ m+n\(em1, where\ m is the circuit
identification code contained in the message.
.PP
The following codes are used in each circuit state indicator
octet.
.RT
.LP
	a)
	\fIfor bits D C = 0 0\fR 
.LP
	bits
	B
	A:
	Maintenance blocking state
.LP
	0
	0
	transient
.LP
	0
	1
	spare
.LP
	1
	0
	spare
.LP
	1
	1
	unequipped
.LP
	bits
	E\(hyH: 
	Spare
.LP
	b)
	\fIfor bits D C not equal to 0 0\fR 
.LP
	bits
	B
	A:
	Maintenance blocking state
.LP
	0
	0
	no blocking (active)
.LP
	0
	1
	locally blocked
.LP
	1
	0
	remotely blocked
.LP
	1
	1
	locally and remotely blocked
.LP
	bits
	D
	C:
	Call processing state
.LP
	0
	1
	circuit incoming busy
.LP
	1
	0
	circuit outgoing busy
.LP
	1
	1
	idle
.LP
	bits
	F
	E:
	Hardware blocking state (Note)
.LP
	0
	0
	no blocking (active)
.LP
	0
	1
	locally blocked
.LP
	1
	0
	remotely blocked
.LP
	1
	1
	locally and remotely blocked
.LP
	bits
	G\(hyH:
	Spare
.LP
	\fINote\fR \ \(em\ If bits F E are not coded 0 0, bits D C must be
coded\ 1\ 1.
.sp 1P
.LP
3.13
	\fIClosed user group interlock code\fR 
.sp 9p
.RT
.PP
The format of the closed user group interlock code parameter field is shown 
in Figure\ 16/Q.763. 
.RT
.LP
.rs
.sp 11P
.ad r
\fBFigure 16/Q.763, p.  \fR 
.sp 1P
.RT
.ad b
.RT
.PP
The following codes are used in the subfields of the closed user group 
interlock code parameter field: 
.LP
	a)
	\fINetwork identity (NI)\fR \fI(octets 1 and 2)\fR 
.LP
	Each digit is coded in the binary coded decimal
representation from\ 0 to\ 9.
.LP
	 If the first digit of this field is coded\ 0 or\ 9, the TCC (Telephony 
Country Code) follows in the second to fourth NI digits (the most significant 
TCC digit is in the\ 2nd NI digit). If the TCC is one or two digits long, 
the excess digit(s) is inserted with the code for RPOA or network 
identification, if necessary. If octet\ 2 is not required, it is coded all\ 0.
.LP
	Coding of the first digit as\ 1 or\ 8 is excluded.
.LP
	 If the first digit is not\ 0, 9, 1 or\ 8 this field contains a DNIC (Data 
Network Identification Code) as defined in Recommendation\ X.121. 
.bp
.LP
	b)
	\fIBinary code (octets 3 and 4)\fR 
.LP
	A code allocated to a closed user group administered by a
particular ISDN or data network. Bit\ 8 of octet\ 3 is the most significant 
and bit\ 1 of octet\ 4 is the least significant. 
.sp 1P
.LP
3.14
	\fIConnected number\fR 
.sp 9p
.RT
.PP
The format of the connected number parameter field corresponds to the format 
shown in Figure\ 17/Q.763. 
.RT
.LP
.rs
.sp 20P
.ad r
\fBFigure 17/Q.763, p.  \fR 
.sp 1P
.RT
.ad b
.RT
.PP
The following codes are used in the subfields of the connected
number parameter field:
.LP
	a)
	Odd/even indicator: see\ \(sc\ 3.7\ a)
.LP
	b)
	Nature of address indicator: see\ \(sc\ 3.7\ b)
.LP
	c)
	Numbering plan indicator: see\ \(sc\ 3.7\ d)
.LP
	d)
	Address presentation restricted indicator: see\ \(sc\ 3.8\ e)
.LP
	e)
	Screening indicator: see\ \(sc\ 3.8\ f)
.LP
	f)
	Address signal: see\ \(sc\ 3.8\ g)
.LP
	g)
	Filler: see\ \(sc\ 3.7\ h).
.sp 1P
.LP
3.15
	\fIConnection request\fR 
.sp 9p
.RT
.PP
The format of the connection request parameter field is shown in
Figure\ 18/Q.763.
.RT
.PP
The following codes are used in the subfields of the connection
request parameter field:
.LP
	a)
	\fILocal reference\fR 
.LP
	A code indicating the local reference allocated by the
signalling connection control part to the end\(hyto\(hyend connection.
.LP
	b)
	\fIPoint code\fR 
.LP
	A code identifying the signalling point at which the
connection request originated.
.LP
	c)
	\fIProtocol class\fR 
.LP
	A code identifying in pure binary representation, the
protocol class requested for the end\(hyto\(hyend connection.
.LP
	d)
	\fICredit\fR 
.LP
	 A code identifying in pure binary representation the window size requested 
for the end\(hyto\(hyend connection. 
.bp
.LP
.rs
.sp 19P
.ad r
\fBFigure 18/Q.763, p.  \fR 
.sp 1P
.RT
.ad b
.RT
.sp 1P
.LP
3.16
	\fIContinuity indicators\fR 
.sp 9p
.RT
.PP
The format of the continuity indicators parameter field is shown in Figure\ 
19/Q.763. 
.RT
.LP
.rs
.sp 7P
.ad r
\fBFigure 19/Q.763, p.  \fR 
.sp 1P
.RT
.ad b
.RT
.PP
The following codes are used in the continuity indicators
parameter field.
.LP
	bit
	A:
	Continuity indicator
.LP
	0
	continuity check failed
.LP
	1
	continuity check successful
.LP
	bits
	B\(hyH:
	Spare
.sp 1P
.LP
3.17
	\fIEnd of optional parameters indicator\fR 
.sp 9p
.RT
.PP
The last optional parameter field of a message is followed by the end of 
optional parameters indicator, which occupies a one octet field 
containing all zeros.
.RT
.sp 1P
.LP
3.18
	\fIEvent information\fR 
.sp 9p
.RT
.PP
The format of the event information parameter field is shown in
Figure\ 20/Q.763.
.bp
.RT
.LP
.rs
.sp 8P
.ad r
\fBFigure 20/Q.763, p.  \fR 
.sp 1P
.RT
.ad b
.RT
.PP
The following codes are used in the event indicator parameter
field:
.LP
	bits
	GFEDCBA:\ Event indicator
.LP
	0000000
	spare
.LP
	0000001
	ALERTING
.LP
	0000010
	PROGRESS
.LP
	0000011
	in\(hyband information of an appropriate pattern  is now available
.LP
	0000100
	call forwarded on busy
.LP
	0000101
	call forwarded on no reply
.LP
	0000110
	call forwarded unconditional
.LP
	0000111
	
.LP
	\  | o
		spare
.LP
	1111111
	
.LP
	bit
	H:
	Event presentation restricted indicator
.LP
	0
	no indication
.LP
	1
	presentation restricted
.sp 1P
.LP
3.19
	\fIFacility indicator\fR 
.sp 9p
.RT
.PP
The format of the facility indicator parameter field is shown in
Figure\ 21/Q.763.
.RT
.LP
.rs
.sp 7P
.ad r
\fBFigure 21/Q.763, p.  \fR 
.sp 1P
.RT
.ad b
.RT
.PP
The following codes are used in the facility indicator parameter   field.
.LP
	00000000
	spare
.LP
	00000001
	spare
.LP
	00000010
	user\(hyto\(hyuser service
.LP
	00000011
	
.LP
	\ \ to
		spare
.LP
	11111111
	
.sp 1P
.LP
3.20
	\fIForward call indicators\fR 
.sp 9p
.RT
.PP
The format of the forward call indicators parameter field is shown in Figure\ 
22/Q.763. 
.bp
.RT
.LP
.rs
.sp 9P
.ad r
\fBFigure 22/Q.763, p.  \fR 
.sp 1P
.RT
.ad b
.RT
.PP
The following codes are used in the forward call indicators
parameter field:
.LP
	bit
	A:
	National/international call indicator
.LP
	0
	call to be treated as a national call
.LP
	1
	call to be treated as an international call
.LP
	 This bit can be set to any value in the country of origin. In the international 
network this bit is not checked. In the destination country, 
calls from the international network will have this bit set to\ 1.
.LP
	bits
	C
	B:
	End\(hyto\(hyend method indicator (Note)
.LP
	0
	0
	no end\(hyto\(hyend method available (only
link\(hyby\(hylink method available)
.LP
	0
	1
	pass along method available
.LP
	1
	0
	SCCP method available
.LP
	1
	1
	pass along and SCCP methods available
.LP
	bit
	D:
	Interworking indicator (Note)
.LP
	0
	no interworking encountered (No.\ 7 signalling all
the way)
.LP
	1
	interworking encountered
.LP
	bit
	E:
	End\(hyto\(hyend information indicator (Note)
.LP
	0
	no end\(hyto\(hyend information available
.LP
	1
	end\(hyto\(hyend information available
.LP
	bit
	F:
	ISDN user part indicator (Note)
.LP
	0
	ISDN user part not used all the way
.LP
	1
	ISDN user part used all the way
.LP
	bits
	H
	G:
	ISDN user part preference indicator
.LP
	0
	0
	ISDN user part preferred all the way
.LP
	0
	1
	ISDN user part not required all the way
.LP
	1
	0
	ISDN user part required all the way
.LP
	1
	1
	spare
.LP
	bit
	I:
	ISDN access indicator
.LP
	0
	originating access non\(hyISDN
.LP
	1
	originating access ISDN
.LP
	bits
	K
	J:
	SCCP method indicator
.LP
	0
	0
	no indication
.LP
	0
	1
	connectionless method available
.LP
	1
	0
	connection oriented method available
.LP
	1
	1
	connectionless and connection oriented methods available
.LP
	bit
	L:
	Spare
.LP
	bits
	M\(hyP:
	Reserved for national use
.LP
	\fINote\fR \ \(em\ Bits B\(hyF and J\(hyK constitute the protocol control
indicator.
.sp 1P
.LP
3.21
	\fIInformation indicators\fR 
.sp 9p
.RT
.PP
The format of the information indicators parameter field is shown in Figure\ 
23/Q.763. 
.bp
.RT
.LP
.rs
.sp 9P
.ad r
\fBFigure 23/Q.763, p.  \fR 
.sp 1P
.RT
.ad b
.RT
.PP
The following codes are used in the information indicators
parameter field:
.LP
	bits
	B
	A:
	Calling party address response indicator
.LP
	0
	0
	calling party address not included
.LP
	0
	1
	calling party address not available
.LP
	1
	0
	spare
.LP
	1
	1
	calling party address included
.LP
	bit
	C:
	Hold provided indicator (national use)
.LP
	0
	hold not provided
.LP
	1
	hold provided
.LP
	bits
	E
	D:
	Spare
.LP
	bit
	F:
	Calling party's category response indicator
.LP
	0
	calling party's category not included
.LP
	1
	calling party's category included
.LP
	bit
	G:
	Charge information response indicator
(national\ use)
.LP
	0
	charge information not included
.LP
	1
	charge information included
.LP
	bit
	H:
	Solicited information indicator
.LP
	0
	solicited
.LP
	1
	unsolicited
.LP
	bits
	I\(hyP:
	Spare
.sp 1P
.LP
3.22
	\fIInformation request indicators\fR 
.sp 9p
.RT
.PP
The format of the information request indicators parameter field is shown 
in Figure\ 24/Q.763. 
.RT
.LP
.rs
.sp 9P
.ad r
\fBFigure 24/Q.763, p.  \fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.PP
The following codes are used in the information request indicators parameter 
field. 
.LP
	bit
	A:
	Calling party address request indicator
.LP
	0
	calling party address not requested
.LP
	1
	calling party address requested
.LP
	bit
	B:
	Holding indicator (national use)
.LP
	0
	holding not requested
.LP
	1
	holding requested
.LP
	bit
	C:
	Spare
.LP
	bit
	D:
	Calling party's category request indicator
.LP
	0
	calling party's category not requested
.LP
	1
	calling party's category requested
.LP
	bit
	E:
	Charge information request indicator (national\ use)
.LP
	0
	charge information not requested
.LP
	1
	charge information requested
.LP
	bits
	G
	F:
	Spare
.LP
	bit
	H:
	Malicious call identification request indicator
(national\ use)
.LP
	0
	malicious call identification not requested
.LP
	1
	malicious call identification requested
.LP
	bits
	I\(hyP:
	Spare
.sp 1P
.LP
3.23
	\fINature of connection indicators\fR 
.sp 9p
.RT
.PP
The format of the nature of connection indicators parameter field is shown 
in Figure\ 25/Q.763. 
.RT
.LP
.rs
.sp 7P
.ad r
\fBFigure 25/Q.763, p.  \fR 
.sp 1P
.RT
.ad b
.RT
.PP
The following codes are used in the nature of connection
indicators parameter field:
.LP
	bits
	B
	A:
	Satellite indicator
.LP
	0
	0
	no satellite circuit in the connection
.LP
	0
	1
	one satellite circuit in the connection
.LP
	1
	0
	two satellite circuits in the connection
.LP
	1
	1
	spare
.LP
	bits
	D
	C:
	Continuity check indicator
.LP
	0
	0
	continuity check not required
.LP
	0
	1
	continuity check required on this circuit
.LP
	1
	0
	continuity check performed on a previous
circuit
.LP
	1
	1
	spare
.LP
	bit
	E:
	Echo control device indicator
.LP
	0
	outgoing half echo control device not included
.LP
	1
	outgoing half echo control device included
.LP
	bits
	F\(hyH:
	Spare
.sp 1P
.LP
3.24
	\fIOptional backward call indicators\fR 
.sp 9p
.RT
.PP
The format of the optional backward call indicators parameter field is 
shown in Figure\ 26/Q.763. 
.bp
.RT
.LP
.rs
.sp 7P
.ad r
\fBFigure 26/Q.763, p.  \fR 
.sp 1P
.RT
.ad b
.RT
.PP
The following codes are used in the optional backward call
indicators parameter field:
.LP
	bit
	A:
	In\(hyband information indicator
.LP
	0
	no indication
.LP
	1
	in\(hyband information or an appropriate pattern is now  available
.LP
	bit
	B:
	Call forwarding may occur indicator
.LP
	0
	no indication
.LP
	1
	call forwarding may occur
.LP
	bits
	C\(hyD:
	Spare
.LP
	bits
	E\(hyH:
	Reserved for national use
.sp 1P
.LP
3.25
	\fIOptional forward call indicators\fR 
.sp 9p
.RT
.PP
The format of the optional forward call indicators parameter field is shown 
in Figure\ 27/Q.763. 
.RT
.LP
.rs
.sp 7P
.ad r
\fBFigure 27/Q.763, p.  \fR 
.sp 1P
.RT
.ad b
.RT
.PP
The following codes are used in the optional forward call
indicators parameter field:
.LP
	bits
	B
	A:
	Closed user group call indicator
.LP
	0
	0
	non\(hyCUG call
.LP
	0
	1
	spare
.LP
	1
	0
	closed user group call, outgoing access
allowed
.LP
	1
	1
	closed user group call, outgoing access not
allowed
.LP
	bit
	C\(hyH:
	Spare
.sp 1P
.LP
3.26
	\fIOriginal called number\fR 
.sp 9p
.RT
.PP
The format of the original called number parameter field
corresponds to the format shown in Figure\ 28/Q.763.
.RT
.PP
The following codes are used in the subfields of the original
called number parameter field:
.LP
	a)
	Odd/even indicator: see \(sc 3.7 a)
.LP
	b)
	Nature of address indicator: see \(sc 3.7 b)
.LP
	c)
	Numbering plan indicator: see \(sc 3.7 d)
.LP
	d)
	Address presentation restricted indicator: see \(sc 3.8 e)
.LP
	e)
	Address signal: see \(sc 3.8 g)
.LP
	f)
	Filler: see \(sc 3.7 h).
.bp
.LP
.rs
.sp 19P
.ad r
\fBFigure 28/Q.763, p.  \fR 
.sp 1P
.RT
.ad b
.RT
.sp 1P
.LP
3.27
	\fIRange and status\fR 
.sp 9p
.RT
.PP
The format of the range and status parameter field is shown in
Figure\ 29/Q.763.
.RT
.LP
.rs
.sp 13P
.ad r
\fBFigure 29/Q.763, p.  \fR 
.sp 1P
.RT
.ad b
.RT
.PP
The following codes are used in the subfields of the range and
status parameter field:
.LP
	a)
	\fIRange\fR 
.LP
	A number in pure binary representation ranging from\ 0
to\ 255. Range code\ 0 indicates absence of the status field. The number
represented by a non\(hyzero range code\ +1 indicates the range of circuits
affected by the message.
.LP
	b)
	\fIStatus\fR 
.LP
	The status subfield contains from\ 1 to\ 256 status bits
numbered from\ 0 to\ 255. Status bit\ 0 is located in bit position\ 1 of 
the first status subfield octet. Other status bits follow in numerical 
order. The number of relevant status bits in a given status subfield is 
equal to range\ +1. 
.LP
	 Each status bit is associated with a circuit identification code such 
that status bit\ n is associated with circuit identification code\ m+n, 
where\ m is the circuit identification code contained in the message. 
.bp
.LP
	The status bits are coded as follows:
.LP
	\(em
	in circuit group blocking messages
	0\ \ no indication
.LP
	1\ \ blocking
.LP
	\(em
	in circuit group blocking acknowledgement
messages
	0\ \ no indication
.LP
	1\ \ blocking acknowledgement
.LP
	\(em
	in circuit group unblocking messages
	0\ \ no indication
.LP
	1\ \ unblocking
.LP
	\(em
	in circuit group unblocking acknowledgement
messages
	0\ \ no indication
.LP
	1\ \ unblocking acknowledgement
.LP
	\(em
	in circuit group reset acknowledgement messages
	0\ \ not blocked for maintenance reasons
.LP
	1\ \ blocked for maintenance reasons
.PP
The number of circuits affected by a group supervision message is limited 
to\ 32 or less. For the group reset and query messages this requires 
that the range value be\ 31 or less. For the group blocking and unblocking
messages the range value may be up to\ 255, but the number of status bits set
to\ 1 must be\ 32 or less.
.PP
For the group blocking, unblocking and reset messages, range code\ 0 is 
reserved. 
.RT
.sp 1P
.LP
3.28
	\fIRedirecting number\fR 
.sp 9p
.RT
.PP
The format of the redirecting number parameter field corresponds to the 
format shown in Figure\ 28/Q.763. 
.PP
The following codes are used in the subfields of the redirecting
number parameter field:
.RT
.LP
	a)
	Odd/even indicator: see \(sc\ 3.7 a)
.LP
	b)
	Nature of address indicator: see \(sc\ 3.7 b)
.LP
	c)
	Numbering plan indicator: see \(sc\ 3.7 d)
.LP
	d)
	Address presentation restricted indicator: see \(sc\ 3.8 e)
.LP
	e)
	Address signal: see \(sc\ 3.8 g)
.LP
	f)
	Filler: see \(sc\ 3.7 f).
.sp 1P
.LP
3.29
	\fIRedirection information\fR 
.sp 9p
.RT
.PP
The format of the redirection information parameter field is shown in Figure\ 
30/Q.763. 
.RT
.LP
.rs
.sp 12P
.ad r
\fBFigure 30/Q.763, p.  \fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.PP
The following codes are used in the redirection information
parameter field:
.LP
	bits
	C
	B
	A:
	Redirecting indicator
.LP
	0
	0
	0
	no redirection
.LP
	0
	0
	1
	call rerouted
.LP
	0
	1
	0
	call rerouted, all redirection
information presentation restricted
.LP
	0
	1
	1
	call forwarded
.LP
	1
	0
	0
	call forwarded, all redirection
information presentation restricted
.LP
	1
	0
	1
	call rerouted, redirection number
presentation restricted
.LP
	1
	1
	0
	call forwarded, redirection number
presentation restricted
.LP
	1
	1
	1
	spare
.LP
	bit
	D:
	Spare
.LP
	bits
	H
	G
	F
	E:
	Original redirection reasons
.LP
	0
	0
	0
	0
	unknown/not available
.LP
	0
	0
	0
	1
	user busy
.LP
	0
	0
	1
	0
	no reply
.LP
	0
	0
	1
	1
	unconditional
.LP
	0
	1
	0
	0
	
.LP
	\  | o
	\ \ spare
.LP
	1
	1
	1
	1
	
.LP
	bits
	K
	J
	I:
	Redirection counter. Number of
redirections the call has
undergone expressed as a binary number between\ 1 and\ 5.
.LP
	bit
	L:
	Spare
.LP
	bits
	P
	O
	N
	M:
	Redirecting reason
.LP
	0
	0
	0
	0
	unknown/not available
.LP
	0
	0
	0
	1
	user busy
.LP
	0
	0
	1
	0
	no reply
.LP
	0
	0
	1
	1
	unconditional
.LP
	0
	1
	0
	0
	
.LP
	\  | o
	\ \ spare
.LP
	1
	1
	1
	1
	
.sp 1P
.LP
3.30
	\fIRedirection number\fR 
.sp 9p
.RT
.PP
The format of the redirection number parameter field corresponds to the 
format shown in Figure\ 9/Q.763. 
.PP
The following codes are used in the subfields of the redirection
number parameter field:
.RT
.LP
	a)
	Odd/even indicator: see \(sc 3.7 a)
.LP
	b)
	Nature of address indicator: see \(sc 3.7 b)
.LP
	c)
	Internal nerwork number indicator: see \(sc 3.7 c)
.LP
	d)
	Numbering plan indicator: see \(sc 3.7 d)
.LP
	e)
	Address signal: see \(sc 3.8 f)
.LP
	f)
	Filler: see \(sc 3.7 f).
.sp 1P
.LP
3.31
	\fISignalling point code\fR 
\fI(national use)\fR 
.sp 9p
.RT
.PP
The format of the signalling point code parameter field is shown in Figure\ 
31/Q.763. 
.RT
.LP
.rs
.sp 8P
.ad r
\fBFigure 31/Q.763, p.  \fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.PP
The signalling point code is a pure binary representation of the code allocated 
to a node in the signalling network. 
.sp 1P
.LP
3.32
	\fISubsequent number\fR 
.sp 9p
.RT
.PP
The format of the subsequent number parameter field is shown in
Figure\ 32/Q.763.
.RT
.LP
.rs
.sp 13P
.ad r
\fBFigure 32/Q.763, p.  \fR 
.sp 1P
.RT
.ad b
.RT
.PP
The following codes are used in the subfields of the subsequent
number parameter field:
.LP
	a)
	Odd/even indicator: see \(sc 3.7 a)
.LP
	b)
	Address signal: see \(sc 3.7 e)
.LP
	c)
	Filler: see \(sc 3.7 f).
.sp 1P
.LP
3.33
	\fISuspend/resume indicators\fR 
.sp 9p
.RT
.PP
The format of the suspend/resume indicators parameter field is
shown in Figure\ 33/Q.763.
.RT
.LP
.rs
.sp 7P
.ad r
\fBFigure 33/Q.763, p.  \fR 
.sp 1P
.RT
.ad b
.RT
.PP
The following codes are used in the suspend/resume indicators
parameter field:
.LP
	bit
	A:
	Suspend/resume indicator
.LP
	0:
	ISDN subscriber initiated
.LP
	1:
	network initiated
.LP
	bits
	B\(hyH:
	Spare
.bp
.sp 1P
.LP
3.34
	\fITransit network selection\fR 
\fI(national use)\fR 
.sp 9p
.RT
.PP
The format of the transit network selection parameter field is
shown in Figure\ 34/Q.763.
.RT
.LP
.rs
.sp 11P
.ad r
\fBFigure 34/Q.763, p.  \fR 
.sp 1P
.RT
.ad b
.RT
.PP
The following codes are used in the subfields of the transit
network selection parameter field:
.LP
	a)
	\fIOdd/even indicator\fR 
.LP
	0
	even number of digits
.LP
	1
	odd number of digits
.LP
	b)
	\fIType of network identification\fR 
.LP
	000
	CCITT\(hystandardized identification
.LP
	010
	national network identification
.LP
	other
	reserved
.LP
	c)
	\fINetwork identification plan\fR 
.LP
	i)
	For CCITT\(hystandardized identification
	0000
	unknown
.LP
	0011
	public data network identification code
(DNIC), Recommendation X.121
.LP
	0110
	public land mobile network identification
code (MNIC), Recommendation E.212
.LP
	other
	spare
.LP
	ii)
	For national network identification
	This information is coded according to national
specifications.
.LP
	d)
	\fINetwork identification\fR 
.LP
	This information is organized according to the network
identification plan and the encoding principles given in\ \(sc\ 3.8\ f).
.sp 1P
.LP
3.35
	\fITransmission medium requirement\fR 
.sp 9p
.RT
.PP
The format of the transmission medium requirement parameter field is shown 
in Figure\ 35/Q.763. 
.RT
.LP
.rs
.sp 7P
.ad r
\fBFigure 35/Q.763, p.  \fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.PP
The following codes are used in the transmission medium
requirement parameter field.
.LP
	00000000
	speech
.LP
	00000001
	spare
.LP
	00000010
	64 kbit/s unrestricted
.LP
	00000011
	3.1 kHz audio
.LP
	00000100
	alternate speech (service 2)/64 kbit/s
unrestricted (service 1) (Note 1)
.LP
	00000101
	alternate 64 kbit/s unrestricted (service 1)/speech
(service 2) (Note 2)
.LP
	00000110
	spare
.LP
	00000111
	reserved for 2 \(mu 64 kbit/s unrestricted
.LP
	00001000
	reserved for 384 kbit/s unrestricted
.LP
	00001001
	reserved for 1536 kbit/s unrestricted
.LP
	00001010
	reserved for 1920 kbit/s unrestricted
.LP
	00001011
	
.LP
	\ to
		spare
.LP
	11111111
	
.LP
	\fINote\ 1\fR \ \(em\ The initial mode is speech.
.LP
	\fINote\ 2\fR \ \(em\ The initial mode is 64 kbit/s unrestricted.
.sp 1P
.LP
3.36
	\fIUser service information\fR 
.sp 9p
.RT
.PP
The format of the user service information parameter field is shown in 
Figure\ 36/Q.763. This format is the same as the bearer capability 
information element from Recommendation\ Q.931 and not all capabilities coded
here are supported at this time.
.RT
.LP
.rs
.sp 24P
.ad r
\fBFigure 36/Q.763, p.\fR 
.sp 1P
.RT
.ad b
.RT
.PP
The following codes are used in the subfields of the user service information 
parameter field: 
.LP
	a)
	\fIExtension indicator (ext)\fR 
.LP
	0
	octet continues through the next octet
(e.g. octet 2 to 2a, 2a to 2b, 3 to 3a)
.LP
	1
	last octet
.bp
.LP
	b)
	\fICoding standard\fR 
.LP
	00
	CCITT standardized coding as described below
.LP
	01
	reserved for other international standards (Note)
.LP
	10
	national standard (Note)
.LP
	11
	standard defined for the network (either public or
private) present on the network side of the interface (Note)
.LP
	 \fINote\fR \ \(em\ These other coding standards should only be used when 
the desired bearer capability cannot be represented with the CCITT standardized 
coding.
.LP
	c)
	\fIInformation transfer capability\fR 
.LP
	00000
	speech
.LP
	01000
	unrestricted digital information
.LP
	01001
	restricted digital information
.LP
	10000
	3.1\ kHz audio
.LP
	10001
	7 kHz audio
.LP
	11000
	video
.LP
	All other values are reserved
.LP
	d)
	\fITransfer mode\fR 
.LP
	00
	circuit mode
.LP
	10
	packet mode
	All other values are reserved
.LP
	e)
	\fIInformation transfer rate (octets 2 and 2b)\fR  | (Note 1)
.LP
	00000
	This code shall be used for packet\(hymode calls
.LP
	10000
	64 kbit/s
.LP
	10001
	2 \(mu 64 kbit/s (Note 2)
.LP
	10011
	384 kbit/s
.LP
	10101
	1536 kbit/s
.LP
	10111
	1920 kbit/s
	All other values are reserved.
.LP
	\fINote\ 1\fR \ \(em\ When octet 2b is omitted, the bearer capability is
bidirectional symmetric at the information transfer rate specified in octet\ 
2. When octet\ 2b is included, the information rate in octet\ 2 refers 
to the 
origination to destination direction.
.LP
	 \fINote\ 2\fR \ \(em\ For this case, the coding of octets 1 and 2a refer 
to both 64 kbit/s circuits. 
.LP
	f
)
	\fIStructure\fR 
.LP
	000
	default (Note 1)
.LP
	001
	8 kHz integrity (Note 2)
.LP
	100
	service data unit integrity
.LP
	111
	unstructured
.LP
	All other values are reserved.
.LP
	 \fINote\ 1\fR \ \(em\ If octet 2a is omitted, or the structure field 
is coded 000, then the value of the structure attribute is according to 
the 
following:
.LP
	\fITransfer mode\fR 	\fITransfer capability\fR 	\fIStructure\fR 
.LP
	circuit
	speech
	8 kHz integrity
.LP
	circuit
	unrestricted digital
	8 kHz integrity
.LP
	circuit
	restricted digital
	8 kHz integrity
.LP
	circuit
	audio
	8 kHz integrity
.LP
	circuit
	video
	8 kHz integrity
.LP
	packet
	unrestricted digital
	service data unit integrity
.LP
	\fINote\ 2\fR \ \(em\ When the information transfer rate 2 \(mu 64 kbit/s is
used, 8\ kHz integrity with Restricted Differential Time Delay (RDTD) is
offered.
.LP
	g)
	\fIConfiguration\fR 
.LP
	00
	point\(hyto\(hypoint
	All other values are reserved. If omitted, the configuration is
assumed to be point\(hyto\(hypoint.
.LP
	h)
	\fIEstablishment\fR 
.LP
	00
	demand
	All other values are reserved. If omitted, the establishment is
assumed to be demand.
.bp
.LP
	i)
	\fISymmetry\fR 
.LP
	00
	bidirectional symmetric
	All other values are reserved. If omitted, the symmetry is
assumed to be bidirectional symmetric.
.LP
	j)
	\fILayer identification\fR 
.LP
	00
	reserved
.LP
	01
	user information layer 1 protocol
.LP
	10
	user information layer 2 protocol
.LP
	11
	user information layer 3 protocol
.LP
	\fINote\fR \ \(em\ Bits 5\(hy1 of the same octet represent the corresponding
identification as per points\ k), l) and m) below. If octet\ 3, 4 or 5 is
omitted,
the corresponding user information protocol is assumed to be undefined.
.LP
	k)
	\fIUser information layer 1 protocol identification\fR 
.LP
	00001
	CCITT standardized rate adaption V.110/X.30. This
implies the presence of octet 3a defined in \(sc\ 3.36 k) 1), and optionally 
octets 3b, 3c and 3d defined in \(sc\ 3.36 k) 2) below. 
.LP
	00010
	Recommendation G.711 \(*m\(hylaw
.LP
	00010
	Recommendation G.711 A\(hylaw
.LP
	00100
	Recommendation G.721 32 kbit/s ADPCM and
Recommendation\ I.460
.LP
	00101
	Recommendations G.722 and G.724 for 7 kHz audio
.LP
	00110
	Recommendation G.735 for 384 kbit/s video
.LP
	00111
	non\(hyCCITT standardized rate adaption. This implies
the presence of octet 3a, and optionally 3b, 3c and\ 3d. The use of this
codepoint indicates that the user rate specified in octet 3a is defined in
accordance with the non\(hyCCITT standardized rate adaption scheme. Additionally, 
octets 3b, 3c and 3d, if present, are defined consistent with the specified 
rate adaption.
.LP
	01000
	CCITT standardized rate adaption V.120. This implies
the presence of octet 3a defined in \(sc\ 3.36\ k) 1), octet\ 3b defined 
in \(sc\ 3.36\ k) 3), and optionally octets\ 3c and\ 3d defined in 
\(sc\ 3.36\ k) 2) below.
.LP
	01001
	CCITT standardized rate adaption X.31 HDLC flag
stuffing.
	All other values are reserved.
.LP
	\fINote\fR \ \(em\ Octet 3 shall be omitted if the transfer mode is
\*Qcircuit\(hymode\*U, the information transfer capability is \*Qunrestricted 
digital 
information\*U or \*Qrestricted digital information\*U and the user information
layer\ 1 protocol is not to be identified to the network; octet 3 may be 
omitted if the transfer mode is \*Qpacket\(hymode\*U; otherwise octet\ 
3 shall be present. 
.LP
	1)
	\fIOctet 3a for layer 1 rate adaption\fR  | (see Figure 37/Q.763)
.LP
.rs
.sp 7P
.ad r
\fBFigure 37/Q.763, p.\fR 
.sp 1P
.RT
.ad b
.RT
.LP
	\(em
	The synchronous/asynchronous indicator is coded:
	0
	synchronous
.LP
	1
	asynchronous
	Octets 3b to 3d may be omitted in case of synchronous user rates.
.LP
	\(em
	The negotiation indicator is coded:
	0
	in\(hyband negotiation not possible
.LP
	1
	in\(hyband negotiation possible
.LP
	\fINote\fR \ \(em\ See Recommendations V.110 and X.30
.bp
.LP
	\(em
	The user rate is coded:
.LP
	00000
	rate indicated by E\(hybits
	Rec. I.460
.LP
	00001
	0.6 kbit/s
	Rec. V.6 and X.1
.LP
	00010
	1.2 kbit/s
	Rec. V.6
.LP
	00011
	2.4 kbit/s
	Rec. V.6 and X.1
.LP
	00100
	3.6 kbit/s
	Rec. V.6
.LP
	00101
	4.8 kbit/s
	Rec. V.6 and X.1
.LP
	00110
	7.2 kbit/s
	Rec. V.6
.LP
	00111
	8.0 kbit/s
	Rec. I.460
.LP
	01000
	9.6 kbit/s
	Rec. V.6 and X.1
.LP
	01001
	14.4 kbit/s
	Rec. V.6
.LP
	01010
	16.0 kbit/s
	Rec. I.460
.LP
	01011
	19.2 kbit/s
	Rec. V.6
.LP
	01100
	32.0 kbit/s
	Rec. I.460
.LP
	01110
	48.0 kbit/s
	Rec. V.6 and X.1
.LP
	01111
	56.0 kbit/s
	Rec. V.6
.LP
	10101
	0.1345 kbit/s
	Rec. X.1
.LP
	10110
	0.100 kbit/s
	Rec. X.1
.LP
	10111
	0.075/1.2 kbit/s
	Rec. V.6 and X.1 (Note)
.LP
	11000
	1.2/0.075 kbit/s
	Rec. V.6 and X.1 (Note)
.LP
	11001
	0.050 kbit/s
	Rec. V.6 and X.1
.LP
	11010
	0.075 kbit/s
	Rec. V.6 and X.1
.LP
	11011
	0.110 kbit/s
	Rec. V.6 and X.1
.LP
	11100
	0.150 kbit/s
	Rec. V.6 and X.1
.LP
	11101
	0.200 kbit/s
	Rec. V.6 and X.1
.LP
	11110
	0.300 kbit/s
	Rec. V.6 and X.1
.LP
	11111
	12 kbit/s
	Rec. V.6 and X.1
	All other values are reserved.
.LP
	\fINote\fR \ \(em\ The first rate is the transmit rate in the forward
direction of the call. The second rate is the transmit rate in the backward
direction of the call.
.LP
	2)
	 \fIOctets 3b, 3c and 3d for Recommendations V.110/X.30 rate adaption\fR 
(see Figure\ 38/Q.763) 
.LP
.rs
.sp 14P
.ad r
\fBFigure 38/Q.763, p.\fR 
.sp 1P
.RT
.ad b
.RT
.LP
	\(em
	Intermediate rate indicator is coded:
	00
	not used
.LP
	01
	8 kbit/s
.LP
	10
	16 kbit/s
.LP
	11
	32 kbit/s
.LP
	\(em
	Network independent clock (NIC) on transmission (TX)
indicator is coded:
	0
	not required to send data with NIC
.LP
	1
	required to send data with NIC
.bp
.LP
	\fINote\fR \ \(em\ Refers to transmission in the forward direction of the
call, see Recommendations\ V.110 and X.30
.LP
	\(em
	Network independent clock (NIC) on reception (Rx) indicator   is coded:
	0
	cannot accept data with NIC (i.e.\ sender does not support
this optional procedure)
.LP
	1
	can accept data with NIC (i.e.\ sender does support this
optional procedure)
.LP
	 \fINote\fR \ \(em\ Refers to transmission in the backward direction of 
the call, see Recommendations\ V.110 and\ X.30. 
.LP
	\(em
	Flow control on transmission (Tx) indicator is coded:
	0
	not required to send data with flow control mechanism
.LP
	1
	required to send data with flow control mechanism
.LP
	\fINote\fR \ \(em\ Refers to transmission in the forward direction of the
call, see Recommendations\ V.110 and\ X.30.
.LP
	\(em
	Flow control on reception (Rx) indicator is coded:
	0
	 cannot accept data with flow control mechanism (i.e.\ sender does not 
support this optional procedure) 
.LP
	1
	can accept data with flow control mechanism (i.e.\ sender
does support this optional procedure)
.LP
	\fINote\fR \ \(em\ See Recommendations\ V.110 and\ X.30.
.LP
	\(em
	Number of stop bits indicator is coded:
	00
	not used
.LP
	01
	1 bit
.LP
	10
	1.5 bits
.LP
	11
	2 bits
.LP
	\(em
	Number of data bits indicator, including parity bit if
present, is coded:
	00
	not used
.LP
	01
	5 bits
.LP
	10
	7 bits
.LP
	11
	8 bits
.LP
	\(em
	Parity indicator is coded:
	000
	odd
.LP
	010
	even
.LP
	011
	none
.LP
	100
	forced to 0
.LP
	101
	forced to 1
	All other values are reserved
.LP
	\(em
	Duplex mode indicator is coded:
	0
	half duplex
.LP
	1
	full duplex
.LP
	\(em
	modem type indicator is coded according to network specific   rules.
.LP
	3)
	\fIOctet 3b for Recommendation V.120 rate adaption\fR  | (see
Figure\ 39/Q.763)
.LP
.rs
.sp 10P
.ad r
\fBFigure 39/Q.763, p.\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
	\(em
	Rate adaption header/no header indicator is coded:
	0
	rate adaption header not included
.LP
	1
	rate adaption header included
.LP
	\(em
	Multiple frame establishment support in data link indicator   is coded:
	0
	multiple frame establishment not supported, only UI
frames allowed
.LP
	1
	multiple frame establishment supported
.LP
	\(em
	Mode of operation indicator is coded:
	0
	bit transparent mode of operation
.LP
	1
	protocol sensitive mode of operation
.LP
	\(em
	Logical link identifier (LLI) negotiation indicator is
coded:
	0
	default, LLI = 256 only
.LP
	1
	full protocol negotiation (Note)
.LP
	\fINote\fR \ \(em\ A connection over which protocol negotiation will be
executed is indicated in bit\ 2 of octet\ 3b.
.LP
	\(em
	Assignor/assignee indicator is coded:
	0
	message originator is \*Qdefault assignee\*U
.LP
	1
	message originator is \*Qassignor only\*U
.LP
	\(em
	In\(hyband/out\(hyof\(hyband negotiation indicator is coded:
	0
	negotiation is done with USER INFORMATION messages on a
temporary signalling connection
.LP
	1
	negotiation is done in\(hyband using logical link zero
.LP
	l)
	\fIUser information layer 2 protocol identification\fR 
.LP
	00010
	Recommendation Q.921 (I.441)
.LP
	00110
	Recommendation X.25, link level
	All other values are reserved. If the transfer mode is \*Qpacket
mode\*U, this octet shall be present. In other cases, the octet is present 
only if the protocol is to be identified to the network. 
.LP
	m)
	\fIUser information layer 3 protocol identification\fR 
.LP
	00010
	Recommendation Q.931 (I.451)
.LP
	00110
	Recommendation X.25, link level
	All other values are reserved. The octet is present only
if the protocol is to be identified to the network.
.sp 1P
.LP
3.37
	\fIUser\(hyto\(hyuser indicators\fR 
.sp 9p
.RT
.PP
The format of the user\(hyto\(hyuser indicators parameter field is shown 
in Figure\ 40/Q.763. 
.RT
.LP
.rs
.sp 7P
.ad r
\fBFigure 40/Q.763, p.\fR 
.sp 1P
.RT
.ad b
.RT
.PP
The following codes are used in the user\(hyto\(hyuser indicators
parameter field:
.LP
	bit
	A
	Type
.LP
	0
	request
.LP
	1
	response
.bp
.LP
	If bit A equals 0 (request):
	bits
	C
	B:
	Service 1
.LP
	0
	0
	no information
.LP
	0
	1
	spare
.LP
	1
	0
	request, not essential
.LP
	1
	1
	request, essential
.LP
	bits
	E
	D:
	Service 2
.LP
	0
	0
	no information
.LP
	0
	1
	spare
.LP
	1
	0
	request, not essential
.LP
	1
	1
	request, essential
.LP
	bits
	G
	F:
	Service 3
.LP
	0
	0
	no information
.LP
	0
	1
	spare
.LP
	1
	0
	request, not essential
.LP
	1
	1
	request, essential
.LP
	bit
	H
	Spare
.LP
	If bit A equals 1 (response):
	bits
	C
	B:
	Service 1
.LP
	0
	0
	no information
.LP
	0
	1
	not provided
.LP
	1
	0
	provided
.LP
	1
	1
	spare
.LP
	bits
	E
	D:
	Service 2
.LP
	0
	0
	no information
.LP
	0
	1
	not provided
.LP
	1
	0
	provided
.LP
	1
	1
	spare
.LP
	bits
	G
	F:
	Service 3
.LP
	0
	0
	no information
.LP
	0
	1
	not provided
.LP
	1
	0
	provided
.LP
	1
	1
	spare
.LP
	bit
	H
	Spare
.sp 1P
.LP
3.38
	\fIUser\(hyto\(hyuser information\fR 
.sp 9p
.RT
.PP
The format of the user\(hyto\(hyuser information parameter is shown in
Figure\ 41/Q.763.
.RT
.LP
.rs
.sp 9P
.ad r
\fBFigure 41/Q.763, p.\fR 
.sp 1P
.RT
.ad b
.RT
.PP
The format of the user\(hyto\(hyuser information parameter field is
coded identically to the protocol discriminator plus user information field
described in Recommendation\ Q.931, \(sc\ 4.5.29.
.bp
.sp 2P
.LP
\fB4\fR 	\fBISDN user part messages and codes\fR 
.sp 1P
.RT
.PP
In the following tables the format and coding of ISDN user part
messages is specified. For each message, a list of the relevant parameters 
is given and for each parameter: 
.RT
.LP
	\(em
	 a \fIreference\fR to the section where the formatting and coding of the 
parameter content is specified; 
.LP
	\(em
	the \fItype\fR  | f the parameter. The following types are used in the tables:
.LP
	F\ =
	mandatory fixed length parameter;
.LP
	V\ =
	mandatory variable length parameter;
.LP
	O\ =
	optional parameter of fixed or variable length;
.LP
	\(em
	the \fIlength\fR  | f the parameter. The value in the table
includes:
.LP
	\(em
	\fIfor type F parameters\fR  | he length, in octets, of the
parameter content;
.LP
	\(em
	\fIfor type V parameters\fR  | he length, in octets, of the
length indicator and of the parameter content. The minimum and the maximum
length are indicated;
.LP
	\(em
	\fIfor type O parameters\fR  | he length, in octets, of the
parameter name, length indicator and parameter content. For variable length
parameters the minimum and maximum length is indicated.
.PP
For each message type, type F parameters and the pointers for the type\ 
V parameters must be sent in the order specified in the tables. 
.PP
The routing label and circuit identification code fields, which are
transmitted ahead of the message type field if required are not shown.
Parameter names, pointers to mandatory variable fields and the optional 
part, and length indicators appear in the message in accordance with Figure\ 
3/Q.763 and are not shown explicitly in Tables\ 5/Q.763 to\ 28/Q.763. 
.RT
.LP
.sp 4
.LP
.rs
.sp 20P
.ad r
\fBTableau 5/Q.763 [T5.763], p. 28\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.sp 4
.bp
.LP
.rs
.sp 19P
.ad r
\fBTableau 6/Q.763 [T6.763], p. 29\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.rs
.sp 21P
.ad r
\fBTableau 7/Q.763 [T7.763], p. 30\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 12P
.ad r
\fBTableau 8/Q.763 [T8.763], p. 31\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.sp 3
.rs
.sp 10P
.ad r
\fBTableau 9/Q.763 [T9.763], p. 32\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.sp 3
.rs
.sp 11P
.ad r
\fBTableau 10/Q.763 [T10.763], p. 33\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.sp 2
.bp
.LP
.rs
.sp 19P
.ad r
\fBTableau 11/Q.763 [T11.763], p. 34\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.rs
.sp 10P
.ad r
\fBTableau 12/Q.763 [T12.763], p. 35\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.rs
.sp 14P
.ad r
\fBTableau 13/Q.763 [T13.763], p. 36\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 16P
.ad r
\fBTableau 14/Q.763 [T14.763], p. 37\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.sp 5
.rs
.sp 12P
.ad r
\fBTableau 15/Q.763 [T15.763], p. 38\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.rs
.sp 10P
.ad r
Blanc
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 33P
.ad r
\fBTableau 16/Q.763 [T16.763], p. 39\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.rs
.sp 13P
.ad r
Blanc
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 20P
.ad r
\fBTableau 17/Q.763 [T17.763], p. 40\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.rs
.sp 11P
.ad r
\fBTableau 18/Q.763 [T18.763], p. 41\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.rs
.sp 11P
.ad r
\fBTableau 19/Q.763 [T19.763], p. 42\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 13P
.ad r
\fBTableau 20/Q.763 [T20.763], p. 43\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.sp 2
.rs
.sp 12P
.ad r
\fBTableau 21/Q.763 [T21.763], p. 44\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.sp 2
.rs
.sp 13P
.ad r
\fBTableau 22/Q.763 [T22.763], p. 45\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 15P
.ad r
\fBTableau 23/Q.763 [T23.763], p. 46\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.rs
.sp 16P
.ad r
\fBTableau 24/Q.763 [T24.763], p. 47\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.rs
.sp 13P
.ad r
\fBTableau 25/Q.763 [T25.763], p. 48\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 12P
.ad r
\fBTableau 26/Q.763 [T26.763], p. 49\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.rs
.sp 15P
.ad r
\fBTableau 27/Q.763 [T27.763], p. 50\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.rs
.sp 13P
.ad r
\fBTableau 28/Q.763 [T28.763], p. 51\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.ce 1000
ANNEX\ A
.ce 0
.ce 1000
(to Recommendation Q.763)
.sp 9p
.RT
.ce 0
.ce 1000
\fBInterpretation of spare codes\fR 
.sp 1P
.RT
.ce 0
.PP
This Annex describes interpretations which can be applied when a recognized 
parameter is received containing codes currently indicated as being spare 
in Recommendation\ Q.763. This situation can occur when an implementation 
in accordance to this Recommendation interworks with a future version of 
this Recommendation. The default interpretations for some of these cases 
are listed in Table\ A\(hy1/Q.763. 
.sp 1P
.RT
.PP
For the remaining cases, listed in Table\ A\(hy2/Q.763, there is no
default which is considered appropriate. It is recommended that the entire
parameter in these cases should be considered uninterpretable except as noted.
.PP
Actions taken after applying the default interpretation of
unrecognized fields or after determining that an entire parameter should be
considered uninterpretable are described in \(sc\ 2.10.5.3 of Recommendation\ 
Q.764. Application of default interpretations is of particular interest 
when an 
unrecognized parameter value is passed on at an intermediate exchange or is
used at a connection endpoint. However, other applications are not
precluded.
.RT
.LP
.rs
.sp 30P
.ad r
\fBTableau A\(hy1/Q.763 [T29.763], p.\fR 
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 23P
.ad r
\fBTableau A\(hy2/Q.763 [T30.763], p.\fR 
.ad b
.RT
.LP
.rs
.sp 25P
.LP
\fBMONTAGE: REC. Q.764 SUR LE RESTE DE CETTE PAGE\fR 
.sp 1P
.RT
.LP
.bp