.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'
.sp 2P
.LP
\fB4\fR 	\fBRelease procedures\fR 
.sp 1P
.RT
.sp 1P
.LP
4.1
	\fIArrow diagram\fR 
.EF '%	Fascicle\ VI.6\ \(em\ Rec.\ Q.699''
.OF '''Fascicle\ VI.6\ \(em\ Rec.\ Q.699	%'
.sp 9p
.RT
.PP
This section contains the arrow diagrams for the Q.931/Q.764
interworking release procedures.
.RT
.sp 1P
.LP
4.1.1
	\fIEnd\(hyto\(hyend ISDN scenario\fR 
.sp 9p
.RT
.PP
The following normal call release procedures are indicated.
.RT
.LP
	\fICase 1:\fR \ This case shows the normal call release interworking
procedure without tone provision (Figure\ 20/Q.699).
.LP
	A DISConnect message from the originating user is mapped via the
Disconnect Indication and Release Request primitives into a RELease
message in the network.
.LP
	At the destination end, a RELease message from the network is
mapped into a DISConnect message sent to the terminating user via
Release Indication and Disconnect Request primitives.
.LP
	The tone/announcement option is not applied in the terminating
exchange.
.LP
	\fICase 2:\fR \ This case shows the normal call release interworking
procedure with tone provision (Figure\ 21/Q.699).
.LP
	The tone/announcement option is applied in the terminating
exchange.
.LP
	A RELease message from the network is mapped into a DISConnect
message with progress indicator (##\ 8, in\(hyband information or
appropriate pattern is now available) sent to the terminating
user.
.sp 1P
.LP
4.1.2
	\fIPSTN/ISDN interworking scenario\fR 
.sp 9p
.RT
.PP
The following normal release procedures in PSTN to ISDN
interworking scenario are indicated.
.RT
.LP
	\fICase 1:\fR \ Clear forward (Figure 22/Q.699, Case 1)
.LP
	This case shows the normal call release procedure being initiated
from the originating PSTN by means of a clear forward signal.
.LP
	At the ISDN/PSTN interworking exchange, the clear forward signal
is mapped into a RELease message to the ISDN exchange.
.LP
	\fICase 2:\fR \ Clear backward (Figure 22/Q.699, Case 2)
.LP
	This case shows the normal call release procedure being initiated
from the terminating ISDN user by means of a DISConnect message.
.LP
	At the ISDN\(hyPSTN interworking exchange, a RELease message is
mapped into an appropriate backward signal in PSTN.
.sp 1P
.LP
4.1.3
	\fIISDN/PSTN interworking scenario\fR 
.sp 9p
.RT
.PP
The following normal release procedures in the ISDN to PSTN
interworking scenario are indicated.
.RT
.LP
	\fICase 1:\fR \ Clear forward (Figure 23/Q.699, Case 1)
.LP
	This case shows the normal call release procedure being
initiated from the originating ISDN user by means of a DISConnect
message.
.LP
	At the ISDN/PSTN interworking exchange, a RELease message is
mapped into an appropriate clear forward signal in PSTN.
.LP
	\fICase 2:\fR \ Clear backward (Figure 23/Q.699, Case 2)
.LP
	This case shows the normal call release procedure being initiated
from the terminating PSTN by means of a clear backward signal.
.bp
.LP
	At the ISDN/PSTN interworking exchange, the clear backward
signal is mapped into a SUSpend message with suspend/resume
indicator (network initiated).
.LP
	The terminating ISDN exchange starts the time. Upon expiry of
the timer, if the terminating exchange has not received a RESume
message, the terminating exchange initiates clearing by sending a
DISConnect message to the user, and sending a RELease message to
the preceding exchange.
.sp 1P
.LP
4.1.4
	\fINotes for Figures 20/Q.699\(hy23/Q.699\fR 
.sp 9p
.RT
.PP
\fINote\ 1\fR \ \(em\ This procedure is applicable to those basic services
where in\(hyband tone/announcement is not provided, e.g.\ 64\ kbit/s unrestricted 
bearer service.
.PP
\fINote\ 2\fR \ \(em\ The DISC message should not include the progress 
indicator ##8. 
.PP
\fINote\ 3\fR \ \(em\ This procedure is applicable to both speech and 3.1\ kHz
audio bearer services.
.PP
\fINote\ 4\fR \ \(em\ The provision of tone is optional. If tone is provided,
progress indicator ##8 should be included in the DISC message. If tone 
is not provided, progress indicator ##8 should not be included. 
.RT
.LP
.rs
.sp 36P
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure 20/Q.699, p.\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure 21/Q.699, p.\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure 22/Q.699, p.\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure 23/Q.699, p.\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.sp 1P
.LP
4.2
	\fIMapping of parameters\fR 
.sp 9p
.RT
.PP
This section contains the mapping table of Q.763/Q.931 messages and associated 
parameters. 
.RT
.ce
\fBH.T. [T18.699]\fR 
.ce
TABLE\ 16/Q.699
.ce
\fBMapping of release procedure parameters for ISDN call\fR 
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
lw(36p) | cw(48p) | cw(48p) | cw(48p) .
	User/Network	Network	User/Network
_
.T&
lw(36p) | cw(48p) | cw(48p) | cw(48p) .
Message	DISConnect	RELease	DISConnect
_
.T&
lw(36p) | cw(48p) | cw(48p) | cw(48p) .
Contents	*Cause	*Cause	*Cause
_
.TE
.nr PS 9
.RT
.ad r
\fBTable 16/Q.699 [T18.699], p.\fR 
.sp 1P
.RT
.ad b
.RT
.ce
\fBH.T. [T19.699]\fR 
.ce
TABLE\ 17/Q.699
.ce
\fBMapping of release procedure parameters for PSTN\(hyISDN call\fR 
.ce
\fB(Called party clears)\fR 
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
lw(36p) | cw(48p) | cw(48p) | cw(48p) .
	PSTN	Network	User/Network
_
.T&
lw(36p) | cw(48p) | cw(48p) | cw(48p) .
Message	Clear Backward Signal	RELease	DISConnected
_
.T&
lw(36p) | cw(48p) | cw(48p) | cw(48p) .
Contents		*Cause	*Cause
_
.TE
.nr PS 9
.RT
.ad r
\fBTable 17/Q.699 [T19.699], p.\fR 
.sp 1P
.RT
.ad b
.RT
.ce
\fBH.T. [T20.699]\fR 
.ce
TABLE\ 18/Q.699
.ce
\fBMapping of release procedure parameters for PSTN\(hyISDN call\fR 
.ce
\fB(Called party clears)\fR 
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
lw(36p) | cw(48p) | cw(48p) | cw(48p) .
	PSTN	Network	User/Network
_
.T&
lw(36p) | cw(48p) | cw(48p) | cw(48p) .
Message	Clear forward signal	RELease	DISConnect
_
.T&
lw(36p) | cw(48p) | cw(48p) | cw(48p) .
Contents		 {
*Cause
##16, Normal call clearing
 }	 {
*Cause
##16, Normal call clearing
 }
_
.TE
.nr PS 9
.RT
.ad r
\fBTable 18/Q.699 [T20.699], p.\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.ce
\fBH.T. [T21.699]\fR 
.ce
TABLE\ 19/Q.699
.ce
\fBMapping of release procedure parameters for ISDN\(hyPSTN call\fR 
.ce

.ce
\fB
.ce
(Calling party clears)\fR 
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
lw(36p) | cw(48p) | cw(48p) | cw(48p) .
	User/Network	Network	PSTN
_
.T&
lw(36p) | cw(48p) | cw(48p) | cw(48p) .
Message	DISConnect	RELease	Clear forward signal
_
.T&
lw(36p) | cw(48p) | cw(48p) | cw(48p) .
Contents	*Cause	*Cause	
_
.TE
.nr PS 9
.RT
.ad r
\fBTable 19/Q.699 [T21.699], p.\fR 
.sp 1P
.RT
.ad b
.RT
.sp 2P
.LP
\fB5\fR 	\fBInterworking specification for unsuccessful set\(hyup\fR 
\fBprocedure\fR 
.sp 1P
.RT
.sp 1P
.LP
5.1
	\fIArrow diagram\fR 
.sp 9p
.RT
.PP
This section contains the arrow diagrams for the unsuccessful call set\(hyup 
procedures. 
.RT
.sp 1P
.LP
5.1.1
	\fIUnsuccessful call set\(hyup, point\(hyto\(hypoint data link\fR 
.sp 9p
.RT
.PP
Figure 24/Q.699 shows the unsuccessful call set\(hyup procedure, where 
inband tones/announcements are not provided (e.g.\ 64\ kbit/s unrestricted 
bearer 
.PP
service). The RELease COMPlete message at the destination exchange is mapped
into the RELease message via the Reject Indication and Release Request
primitives. At the originating exchange the RELease message is mapped via 
the Release Indication and Disconnect Request primitives into the DISConnect 
message.
.RT
.sp 1P
.LP
5.1.2
	\fIUnsuccessful call \(em Broadcast data link\fR 
.sp 9p
.RT
.PP
Figure 25/Q.699 shows the unsuccessful call set\(hyup procedure, where 
inband tones/announcements are not provided (e.g.\ 64\ kbit/s unrestricted 
bearer service), in the case where the called party is addressed via a 
broadcast data link. The returning of the RELease COMPlete message via 
a broadcast data link is optional. In the case shown, on receipt of the 
RELease COMPlete message at the destination exchange the cause value is 
retained, and to allow for the 
possibility of another terminal accepting the call, the Reject Indication
primitive is not generated until the expiry of timer\ T303.
.PP
\fINote\fR \ \(em\ Where the network does not receive any response to the
initial SETUP message before the expiry of timer\ T303, the SETUP message is
retransmitted and T303 is restarted. If no further response is received by the
.PP
network on the second expiry of timer\ T303, the Reject Indication primitive 
is generated. 
.PP
The RELease message is then mapped from the Reject Ind and Release
Request primitives. At the originating exchange the RELease message is 
mapped via the Release Indication and Disconnect Request primitives into 
the 
DISConnect message.
.RT
.sp 1P
.LP
5.1.3
	 \fIUnsuccessful call \(em Tone/announcement applied at the originating\fR 
\fIexchange\fR 
.sp 9p
.RT
.PP
Figure 26/Q.699 shows the unsuccessful set\(hyup procedure where tones 
or announcements are generated in the originating exchange towards the 
ISDN 
user as a result of receiving a RELease message.
.PP
Timer T306 is started after the appropriate tone/announcement is sent. 
Figure\ 26/Q.699 shows the originating ISDN user releasing before timer\ 
T306 
expires.
.bp
.RT
.sp 1P
.LP
5.1.4
	\fIUnsuccessful call \(em Tone applied by terminating exchange\fR 
.sp 9p
.RT
.PP
Figure 27/Q.699 shows an unsuccessful call where certain tones and announcements 
can only be generated in the terminating exchange (or transit 
.PP
exchange) during call establishment. This is a typical case, for example, 
for a changed number announcement where the changed number information 
is only 
available at the terminating local exchange. Alternatively, a specific
announcement may be applied at a transit exchange to indicate, for example,
that all circuits to a particular destination are busy.
.PP
The originating exchange sends a DISconnect message to the calling
user with progress indicator ## | , thus indicating that in\(hyband information 
is available. Normal release procedures apply after the in\(hyband information 
has 
been connected.
.RT
.sp 1P
.LP
5.1.5
	\fIUnsuccessful call \(em Originating exchange tone/announcement\fR 
\fItime\(hyout expires\fR 
.sp 9p
.RT
.PP
Figure 28/Q.699 shows the case of tone time\(hyout expiry at the local 
exchange. This is very similar to \(sc\ 5.1.3 above except that the caller 
fails to clear the call following the application of the tone. Timer\ T306 
then 
expires.
.RT
.sp 1P
.LP
5.1.6
	\fIISDN\(hyPSTN interworking \(em Tone/announcements applied by\fR 
\fIterminating exchange within PSTN\fR 
.sp 9p
.RT
.PP
Figure 29/Q.699 shows an unsuccessful call where the sending of
tones and announcements is generated by the terminating exchange during the
call set\(hyup phase. In this case, an Address Complete Message is returned 
from the interworking point with indicators set as shown in Note\ 8 (see 
\(sc\ 5.1.8). 
This is mapped to a PROGress Message at the originating local exchange, with
the progress indicator set to value\ 1, to indicate that in\(hyband information 
may be available. The sequence applies to failure occurring at any point 
within the PSTN. 
.RT
.sp 1P
.LP
5.1.7
	\fIPremature release \(em Point\(hyto\(hypoint data link\fR 
.sp 9p
.RT
.PP
Figure 30/Q.699 shows a premature release situation where release is received 
at the terminating local exchange prior to any terminal response. In this 
situation a DISConnect message is sent to the called user and the 
normal clearing procedure is initiated.
.RT
.sp 1P
.LP
5.1.8
	\fINotes for Figures 24/Q.699\(hy30/Q.699\fR 
.sp 9p
.RT
.PP
\fINote\ 1\fR \ \(em\ This procedure is applicable in those cases where
in\(hyband tone/announcements are not provided, e.g.\ 64\ kbit/s unrestricted 
bearer service. 
.PP
\fINote\ 2\fR \ \(em\ This message is delivered by a point\(hyto\(hypoint 
data link. 
.PP
\fINote\ 3\fR \ \(em\ This message is sent by a broadcast data link.
.PP
\fINote\ 4\fR \ \(em\ Timer T306 is started in the Q.931 protocol block.
.PP
\fINote\ 5\fR \ \(em\ If tones/announcements are applied, a DISConnect message
may be sent containing progress indicator ##8. As an alternative, a PROGress
message may also be sent containing progress indicator\ ##8.
.PP
\fINote\ 6\fR \ \(em\ Customized announcements can only be provided by this
exchange.
.PP
\fINote\ 7\fR \ \(em\ Tone/announcement time\(hyout expires.
.PP
\fINote\ 8\fR \ \(em\ Backward call indicators in the Address Complete Message
set as follows:
.PP
	ISDN access indicator = non\(hyISDN
.PP
Protocol control indicators = interworking encountered
.PP
Called party's status indicator = no indication.
.PP
\fINote\ 9\fR \ \(em\ See \(sc\ 2.1.9.1 of Recommendation Q.764 for through\(hyconnect 
timing. 
.PP
\fINote\ 10\fR \ \(em\ If the clearing ISDN user is the called party, this
message becomes a clear back.
.PP
\fINote\ 11\fR \ \(em\ In the case of point\(hyto\(hymultipoint, the DISConnect 
message is not sent. Terminals are released as they respond. 
.bp
.RT
.LP
.rs
.sp 47P
.ad r
\fBFigure 24/Q.699, p.\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure 25/Q.699, p.\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure 26/Q.699, p.\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure 27/Q.699, p.\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure 28/Q.699, p.\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure 29/Q.699, p.\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure 30/Q.699, p.\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.sp 1P
.LP
5.2
	\fIMapping of parameters\fR 
.sp 9p
.RT
.PP
This section contains the mapping of Q.763/Q.931 messages and
associated parameters.
.RT
.ce
\fBH.T. [T22.699]\fR 
.ce
TABLE\ 20/Q.699
.ce
\fBMapping of ISDN user part address complete message parameters\fR 
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
lw(36p) | cw(72p) | cw(72p) .
	Originating user/network	Network
_
.T&
lw(36p) | lw(72p) | lw(72p) .
Message	DISCONNECT (Q.931)	 {
ADDRESS COMPLETE MESSAGE (ISUP)
 }
_
.T&
lw(36p) | lw(72p) | lw(72p) .
	Cause	Cause 
.T&
lw(36p) | lw(72p) | lw(72p) .
Contents	Progress indicator	 {
Inband information indicator (Network tone or announcement
applied)
 }
.TE
.LP
\fINote\fR
\ \(em\ In this case the inclusion of a Progress Indicator is
mandatory.
.nr PS 9
.RT
.ad r
\fBTable 20/Q.699 [T22.699], p.\fR 
.sp 1P
.RT
.ad b
.RT
.ce
\fBH.T. [T23.699]\fR 
.ce
TABLE\ 21/Q.699
.ce
\fBMapping of ISUP Call Progress parameters\fR 
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
lw(36p) | cw(72p) | cw(72p) .
	Originating user/network	Network
_
.T&
lw(36p) | cw(72p) | cw(72p) .
Message	(Q.931) PROGRESS	 {
ADDRESS COMPLETE MESSAGE (ISUP)
 }
_
.T&
lw(36p) | lw(72p) | lw(72p) .
	Cause	Cause
.T&
lw(36p) | lw(72p) | lw(72p) .
Contents	Progress indicator	 {
Inband information indicator
(Network Tone/Announcement applied)
 }
.TE
.LP
\fINote\fR
\ \(em\ In this case the inclusion of a Progress Indicator is
mandatory.
.nr PS 9
.RT
.ad r
\fBTable 21/Q.699 [T23.699], p.\fR 
.sp 1P
.RT
.ad b
.RT
.ce
\fBH.T. [T24.699]\fR 
.ce
TABLE\ 22/Q.699
.ce
\fBMapping of Q.931 RELease COMPlete message information elements\fR 
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
lw(36p) | cw(60p) | cw(60p) | cw(60p) .
	Originating user/network	Network	Terminating user/network
_
.T&
lw(36p) | cw(60p) | cw(60p) | cw(60p) .
Message	(Q.931) DISC	(ISUP) RELEASE	(Q.931) REL COMP
_
.T&
lw(36p) | cw(60p) | cw(60p) | cw(60p) .
Contents	Cause	Cause	
Cause
.TE
.LP

\fINote\fR
\ \(em\ The Progress Indicator is included when Tones/Announcements are
provided at the originating local exchange when the Bearer Capability =
speech or 3.1 kHz Audio (see Fig.\ 5.3).
.nr PS 9
.RT
.ad r
\fBTable 22/Q.699 [T24.699], p.\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.ce
\fBH.T. [T25.699]\fR 
.ce
TABLE\ 23/Q.699
.ce
\fBAlternative mapping of Q.931 RELease COMPlete message
.ce
\fBinformation elements\fR 
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
lw(36p) | cw(48p) | cw(48p) | cw(48p) .
	Originating user/network	Network	Terminating user/network
_
.T&
lw(36p) | cw(48p) | cw(48p) | cw(48p) .
Message	(Q.931) PROGRESS	(ISUP) RELEASE	(Q.931) REL COMP
_
.T&
lw(36p) | cw(48p) | cw(48p) | cw(48p) .
Contents	Cause	Cause	Cause  
_
.TE
.nr PS 9
.RT
.ad r
\fBTable 23/Q.699 [T25.699], p.\fR 
.sp 1P
.RT
.ad b
.RT
.sp 2P
.LP
\fB6\fR 	\fBInterworking specifications for suspend/resume procedures\fR 
.sp 1P
.RT
.sp 1P
.LP
6.1
	\fIArrow diagrams\fR 
.sp 9p
.RT
.PP
This section contains the arrow diagrams for the
Recommendation\ Q.931/Q.764 interworking suspend/resume procedures.
.RT
.sp 1P
.LP
6.1.1
	\fISuccessful and unsuccessful suspend/resume procedures\fR 
.sp 9p
.RT
.PP
Figure 31/Q.699 indicates the successful and unsuccessful suspend and resume 
procedures. 
.PP
Suspension control and supervision point is the originating local
exchange and maybe a controlling exchange in the network.
.PP
The ISDN User Part protocol in the network is used to convey the
notification to the remote end from the originating exchange.
.RT
.sp 1P
.LP
6.1.2
	\fISuspend/resume \(em Control and supervision within NT2\fR 
.sp 9p
.RT
.PP
Figure 32/Q.699 illustrates the suspend and resume interworking
procedures, where the control and supervision point is located within the
NT2.
.RT
.sp 1P
.LP
6.1.3
	\fISuspend/resume \(em ISDN/PSTN interworking\fR 
.sp 9p
.RT
.PP
Figure 33/Q.699 illustrates the suspend and resume procedures for ISDN\(hyPSTN 
interworking. 
.RT
.sp 1P
.LP
6.1.4
	\fISuspend/resume \(em PSTN/ISDN interworking\fR 
.sp 9p
.RT
.PP
Figure 34/Q.699 illustrates the suspend and resume procedures for PSTN\(hyISDN 
interworking. 
.RT
.sp 1P
.LP
6.1.5
	\fINotes for Figures 31/Q.699\(hy34/Q.699\fR 
.sp 9p
.RT
.PP
\fINote\ 1\fR \ \(em\ Supervision control in controlling exchange.
.PP
\fINote\ 2\fR \ \(em\ Supervision may be performed by the interworking 
exchange. In that case the clear\(hyback and reanswer messages would not 
be sent. 
.PP
\fINote\ 3\fR \ \(em\ When a DISConnect message is sent by the terminating
subscriber, the release procedures in accordance with \(sc\ 4 apply.
.bp
.RT
.LP
.rs
.sp 47P
.ad r
\fBFigure 31/Q.699, p.\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure 32/Q.699, p.\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure 33/Q.699, p.\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure 34/Q.699, p.\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.sp 1P
.LP
6.2
	\fIMapping of parameters\fR 
.sp 9p
.RT
.PP
This section contains the mapping of Q.763/Q.931 messages and
associated parameters.
.RT
.ce
\fBH.T. [T26.699]\fR 
.ce
TABLE\ 24/Q.699
.ce
\fBMapping of SUSPEND/RESUME parameters\fR 
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
lw(48p) | cw(60p) | cw(60p) | cw(60p) .
	User/Network	Network	Network/User
_
.T&
lw(48p) | cw(60p) | cw(60p) | cw(60p) .
 {
Message/information element parameter
 }	SUSPEND	 {
SUSPEND
Suspend/Resume indicator
(Note)
 }	 {
NOTIFY
Notification indicator (set to user suspended)
 }
_
.T&
lw(48p) | cw(60p) | cw(60p) | cw(60p) .
	RESUME	 {
RESUME
Suspend/Resume indicator
(Note)
 }
.TE
.LP	
NOTIFY
Notification indicator
(set to user resumed)
.LP
\fINote\fR
\ \(em\ The values of the SUSPEND/RESUME indicator in Q.763 are
respectively \*QISDN subscriber initiated\*U and \*Qnetwork initiated\*U. This
SUSPEND/RESUME message is only mapped into the Q.931 NOTIFY message when
the SUSPEND/RESUME indicator is set to \*QISDN subscriber initiated\*U.
.nr PS 9
.RT
.ad r
\fBTable 24/Q.699 [T26.699], p.\fR 
.sp 1P
.RT
.ad b
.RT
.ce
\fBH.T. [T27.699]\fR 
.ce
TABLE\ 25/Q.699
.ce
\fBMapping of SUSPEND/RESUME parameters for interworking with NT2\fR 
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(36p) | cw(48p) | cw(48p) | cw(48p) | cw(48p) .
User/NT2	NT2/Network	Network	Network/NT2	NT2/User
_
.T&
lw(36p) | cw(48p) | cw(48p) | cw(48p) | cw(48p) .
SUSPEND	 {
NOTIFY
Notification indicator
(user suspended)
(Note 2)
 }	 {
SUSPEND
SUSPEND/Resume indicator
(Note 1)
 }	 {
NOTIFY
Notification indicator
(set to user suspended)
 }	 {
NOTIFY
Notification indicator
(set to user suspended)
 }
_
.T&
lw(36p) | cw(48p) | cw(48p) | cw(48p) | cw(48p) .
RESUME	 {
NOTIFY
Notification indicator
(user resumed)
(Note 2)
 }	 {
RESUME
Suspend/Resume indicator
(Note 1)
 }	 {
NOTIFY
Notification indicator
(set to user resumed)
 }	 {
NOTIFY
Notification indicator
(set to user resumed)
 }
.TE
.LP

\fINote\ 1\fR
\ \(em\ The values of the SUSPEND/RESUME Indicator in Q.763 are respectively \*QISDN subscriber initiated\*U and \*Qnetwork initiated\*U. This SUSPEND/RESUME
message is only mapped into the Q.931 NOTIFY message when the SUSPEND/RESUME
Indicator is set to \*QISDN subscriber initiated\*U.
.LP
\fINote\ 2\fR
\ \(em\ Only when the NOTIFY message indicates a SUSPEND/RESUME is this
message mapped into the ISUP messages SUSPEND and RESUME.
.nr PS 9
.RT
.ad r
\fBTable 25/Q.699 [T27.699], p.\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.ce 1000
ANNEX\ A
.ce 0
.ce 1000
(to Recommendation Q.699)
.sp 9p
.RT
.ce 0
.ce 1000
\fBSource of busy tone generation\fR 
.sp 1P
.RT
.ce 0
.LP
A.1
	\fIIntroduction\fR 
.sp 1P
.RT
.PP
A.1.1
This annex provides a set of rules by which the location of the busy signal 
tone generation point could be determined for signalling 
interworking cases.
.sp 9p
.RT
.PP
A.1.2
It is important to recognize that for those cases where a busy
tone is generated at a location other than the originating exchange, an
end\(hyto\(hyend path between the busy tone source and the user must exist.
.sp 2P
.LP
A.2
	\fITerminology\fR 
.sp 1P
.RT
.PP
A.2.1
The terms originating exchange and terminating exchange refer to the public 
network exchange that is closest to the respective end user. 
.sp 9p
.RT
.PP
\fINote\ 1\fR \ \(em\ When an exchange of a public network has no appropriate 
pre\(hyarrangement with the calling or the called user, it assumes that 
the 
exchange is closest to the end user, and therefore serves as an originating 
or a terminating exchange in this terminology. 
.PP
\fINote\ 2\fR \ \(em\ Some networks may, as a network option, permit NT2s to
generate busy tone (e.g.\ according to Annex\ C/Q.931 or Annex\ O/Q.931). 
In these cases, the following rules shall also be applied, using the terminology 
\*QNT2\*U to replace \*Qoriginating exchange\*U or \*Qterminating exchange\*U 
as 
appropriate.
.RT
.PP
A.2.2
There are three types of signalling to be considered in these discussions 
viz.: 
.sp 9p
.RT
.LP
	i)
	ISDN signalling systems, i.e. Signalling System No. 7
ISDN User Part (SS7 ISUP) and ISDN user\(hynetwork interface;
.LP
	ii)
	Type 1 PSTN signalling systems which can convey a clearing
message (e.g.\ a subscriber busy signal) for an unsuccessful
call, e.g.\ SS7\ TUP, SS6, R2; and
.LP
	iii)
	Type 2 PSTN signalling systems which cannot convey a
clearing message (e.g.\ the subscriber busy signal) for
.LP
an unsuccessful call, e.g.\ R1, and in this signalling system,
busy tone is used to indicate that the called user
interface is busy.
.sp 1P
.LP
A.3
	\fIRules\fR 
.sp 9p
.RT
.PP
This section presents the set of rules for speech and 3.1\ kHz audio bearer 
services. 
.RT
.sp 1P
.LP
A.3.1
	\fIRule No. 1\fR 
.sp 9p
.RT
.PP
For ISDN to ISDN connections, the in\(hyband busy tones shall normally 
be generated at the originating exchange. The terminating exchange shall 
originate a clearing message to the originating exchange upon notification 
or identification that the user interface is busy. 
.RT
.sp 1P
.LP
A.3.2
	\fIRule No. 2\fR 
.sp 9p
.RT
.PP
For non\(hyISDN to ISDN connections, the in\(hyband busy tone shall
normally be generated at the interworking exchange. The terminating exchange
shall originate a clearing message towards the originating exchange. The 
first exchange that cannot originate, or convey, the clearing message (or 
subscriber busy signal) towards the originating exchange shall be defined 
as the 
.PP
interworking exchange and shall generate the busy tone. This interworking
exchange serves as an interworking exchange either between ISDN signalling
system and Type\ 2 PSTN signalling system or between Type\ 1 PSTN signalling
system and Type\ 2 PSTN signalling system. A network containing both the
terminating and the interworking exchange shall have the option of providing
the busy tone from anywhere inside its network.
.bp
.RT
.sp 1P
.LP
A.3.3
	\fIRule No. 3\fR 
.sp 9p
.RT
.PP
For ISDN to non\(hyISDN connections, the in\(hyband busy tone shall be
generated at either the originating exchange or in the non\(hyISDN network. The
source of busy will depend on the connection configuration and shall be
determined uniquely by the following:
.RT
.LP
	\(em
	For ISDN to non\(hyISDN connections:
.LP
	a)
	in which ISDN signalling exists from the originating
exchange to the terminating exchange, or
.LP
	b)
	in which ISDN signalling and Type 1 signalling
exists from the originating to the terminating exchange,
.LP
then the in\(hyband busy tone shall be generated at the
originating exchange.
.LP
	\(em
	For all other ISDN to non\(hyISDN connections, the in\(hyband busy
signal shall be generated in the non\(hyISDN network.
.PP
\fINote\fR \ \(em\ In cases where special call handling, upon user busy, 
is offered, the exchange(s) other than specified by the above three rules 
can have the option of providing the busy tone and causing the appropriate 
message to be sent to the originator, and retain the connection for subsequent 
user 
requests.
\v'1P'
.ce 1000
ANNEX\ B
.ce 0
.ce 1000
(to Recommendation Q.699)
.sp 9p
.RT
.ce 0
.ce 1000
\fBUsage of \*QCause\*U in Recommendations Q.931, Q.763 and Q.730\fR 
.sp 1P
.RT
.ce 0
.LP
B.1
	\fIFormat\fR 
.sp 1P
.RT
.PP
Format of Q.931 Cause information element or Q.763/Q.730 Cause
indicators parameters \fIcontents\fR  | is shown in Figure\ B\(hy1/Q.699.
.RT
.LP
.rs
.sp 17P
.ad r
\fBFigure B\(hy1/Q.699 [T28.699], p.\ (traiter comme tableau MEP)\fR 
.sp 1P
.RT
.ad b
.RT
.sp 2P
.LP
B.2
	\fICodes used in the sub\(hyfield of the \*QCause\*U\fR 
.sp 1P
.RT
.sp 1P
.LP
B.2.1
	\fIExtension indicator (ext)\fR 
.sp 9p
.RT
.LP
.sp 1
	Bit
.LP
	8
.LP
	0
	octet continues through the next octet (e.g. octet 1 to 1a)
.LP
	1
	last octet
	.bp
.sp 1P
.LP
B.2.2
	\fICoding standard\fR 
.sp 9p
.RT
.LP
.sp 1
	Bits
.LP
	7\ \ 6
.LP
	0\ \ 0\ \ \ CCITT standardized coding, as described below
.LP
	0\ \ 1\ \ \ reserved for other international standards (Note)
.LP
	1\ \ 0\ \ \ national standard (Note)
.LP
	1\ \ 1\ \ \ standard specific to identified location (Note)
		\fINote\fR \ \(em\ These other coding standards should be used only when
the desired cause can not be represented with the CCITT\(hystandardized
coding.
	
.sp 1P
.LP
B.2.3
	\fILocation\fR 
.sp 9p
.RT
.LP
.sp 1
	Bits
.LP
	4\ \ 3\ \ 2\ \ 1
.LP
	0\ \ 0\ \ 0\ \ 0
	user
.LP
	0\ \ 0\ \ 0\ \ 1
	private network serving the local user
.LP
	0\ \ 0\ \ 1\ \ 0
	public network serving the local user
.LP
	0\ \ 0\ \ 1\ \ 1
	transit network
.LP
	0\ \ 1\ \ 0\ \ 0
	public network serving the remote user
.LP
	0\ \ 1\ \ 0\ \ 1
	private network serving the remote user
.LP
	0\ \ 1\ \ 1\ \ 1
	international network
.LP
	1\ \ 0\ \ 1\ \ 0
	network beyond interworking point
.LP
	All other values are reserved.
	
.LP
	\fINote 1\fR \ \(em\ Depending on the location of the users, the local
public network and remote public network may be the same network.
.sp 1P
.LP
	\fINote 2\fR \ \(em\ Examples of location values to be used for various
busy/congestion conditions appear in Annex\ J to
Recommendation\ Q.931.
	B.2.4
	\fIRecommendation\fR 
.sp 9p
.RT
.LP
.sp 1
	Bits
.LP
	7\ \ 6\ \ 5\ \ 4\ \ 3\ \ 2\ \ 1
.LP
	0\ \ 0\ \ 0\ \ 0\ \ 0\ \ 0\ \ 0
	Q.931/Q.763 (Note 2)
.LP
	0\ \ 0\ \ 0\ \ 0\ \ 0\ \ 1\ \ 1
	X.21
.LP
	0\ \ 0\ \ 0\ \ 0\ \ 1\ \ 0\ \ 0
	X.25
.LP
	0\ \ 0\ \ 0\ \ 0\ \ 1\ \ 0\ \ 1
	public land mobile networks, Q.1031/Q.1051
(Q.763)
.LP
	All other values are reserved.
		\fINote 1\fR \ \(em\ If octet including this field is omitted,
Recommendation Q.931/Q.763 is assumed.
.LP
	 \fINote 2\fR \ \(em\ This value is used only when the preceding octet 
is extended and the cause in octet 4 is from Table\ B\(hy1/Q.699. 
	
.sp 1P
.LP
B.2.5
	\fICause value\fR 
.sp 9p
.RT
.PP
The cause value is divided into two fields, a class (bits 5 through 7) 
and a value within the class (bits 1 through 4). 
.bp
.RT
.LP
	(1)\ The class indicates the general nature of the event.
.LP
	Class (000) :\ normal event
.LP
	Class (001) :\ normal event
.LP
	Class (010) :\ resource unavailable
.LP
	Class (011) :\ service or option not available
.LP
	Class (100) :\ service or option not implemented
.LP
	Class (101) :\ invalid message (e.g. parameter out of range)
.LP
	Class (110) :\ protocol error (e.g. unknown message)
.LP
	Class (111) :\ interworking
		(2)\ The cause values are listed in
Table B\(hy1/Q.699.
	
.LP
\-v'1P'
\-v'6p'
.ce
\fBH.T. [1T29.699]\fR 
.ce
TABLE\ B\(hy1/Q.699
.ce
\fBCause values\fR 
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(24p) sw(30p) | cw(18p) | cw(114p) | cw(42p) , c | c | ^ | ^ | ^ .
Cause value	Cause number	Cause	Recommendations
Class	Value
_
.T&
cw(24p) | cw(30p) | lw(18p) | lw(114p) | lw(42p) .
7\ \ 6\ \ 5	4\ \ 3\ \ 2\ \ 1			
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
0\ \ 0\ \ 0	0\ \ 0\ \ 0\ \ 1	\ \ 1	 {
Unallocated (unassigned) number (Note 1)
 }	Q.931, Q.763
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
0\ \ 0\ \ 0	0\ \ 0\ \ 1\ \ 0	\ \ 2	 {
No route to specified transit network
 }	Q.931, Q.763
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
0\ \ 0\ \ 0	0\ \ 0\ \ 1\ \ 1	\ \ 3	No route to destination	Q.931, Q.763
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
0\ \ 0\ \ 0	0\ \ 1\ \ 0\ \ 0	\ \ 4	Send special information tone	\fBQ.931,\fR  Q.763
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
0\ \ 0\ \ 0	0\ \ 1\ \ 0\ \ 1	\ \ 5	Misdialled trunk prefix	\fBQ.931,\fR  Q.763
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
0\ \ 0\ \ 0	0\ \ 1\ \ 1\ \ 0	\ \ 6	Channel unacceptable	Q.931
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
0\ \ 0\ \ 0	0\ \ 1\ \ 1\ \ 1	\ \ 7	 {
Call awarded and being delivered in an established channel
 }	Q.931
_
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
0\ \ 0\ \ 1	0\ \ 0\ \ 0\ \ 0	\ 16	Normal call clearing	Q.931, Q.763
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
0\ \ 0\ \ 1	0\ \ 0\ \ 0\ \ 1	\ 17	User busy	Q.931, Q.763
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
0\ \ 0\ \ 1	0\ \ 0\ \ 1\ \ 0	\ 18	No user responding	Q.931, Q.763
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
0\ \ 0\ \ 1	0\ \ 0\ \ 1\ \ 1	\ 19	 {
No answer from user (user alerted)
 }	Q.931, Q.763
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
0\ \ 0\ \ 1	0\ \ 1\ \ 0\ \ 1	\ 21	Call rejected	Q.931, Q.763
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
0\ \ 0\ \ 1	0\ \ 1\ \ 1\ \ 0	\ 22	Number changed	Q.931, Q.763
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
0\ \ 0\ \ 1	1\ \ 0\ \ 1\ \ 0	\ 26	Non\(hyselected user clearing	Q.931
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
0\ \ 0\ \ 1	1\ \ 0\ \ 1\ \ 1	\ 27	Destination out of order	Q.931, Q.763
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
0\ \ 0\ \ 1	1\ \ 1\ \ 0\ \ 0	\ 28	Invalid number format	Q.931, Q.763
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
0\ \ 0\ \ 1	1\ \ 1\ \ 0\ \ 1	\ 29	Facility rejected	Q.931, Q.730
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
0\ \ 0\ \ 1	1\ \ 1\ \ 1\ \ 0	\ 30	Response to STATUS ENQUIRY	Q.931
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
0\ \ 0\ \ 1	1\ \ 1\ \ 1\ \ 1	\ 31	Normal, unspecified	Q.931, Q.763
_
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
0\ \ 1\ \ 0	0\ \ 0\ \ 1\ \ 0	\ 34	No circuit/channel available	Q.931, Q.763
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
0\ \ 1\ \ 0	0\ \ 1\ \ 1\ \ 0	\ 38	Network out of order	Q.931, Q.763
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
0\ \ 1\ \ 0	1\ \ 0\ \ 0\ \ 1	\ 41	Temporary failure	Q.931, Q.763
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
0\ \ 1\ \ 0	1\ \ 0\ \ 1\ \ 0	\ 42	 {
Switching equipment congestion
 }	Q.931, Q.763
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
0\ \ 1\ \ 0	1\ \ 0\ \ 1\ \ 1	\ 43	Access information discarded	Q.931
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
0\ \ 1\ \ 0	1\ \ 1\ \ 0\ \ 0	\ 44	 {
Requested circuit/channel not available
 }	Q.931, Q.763
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
0\ \ 1\ \ 0	1\ \ 1\ \ 1\ \ 1	\ 47	 {
Resources unavailable, unspecified
 }	Q.931, Q.763
_
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
0\ \ 1\ \ 1	0\ \ 0\ \ 0\ \ 1	\ 49	 {
Quality of service unavailable
 }	Q.931
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
0\ \ 1\ \ 1	0\ \ 0\ \ 1\ \ 0	\ 50	 {
Requested facility not subscribed
 }	Q.931, Q.730
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
0\ \ 1\ \ 1	0\ \ 1\ \ 0\ \ 1	\ 53	 {
Outgoing calls barred within CUG
 }	\fBQ.931,\fR  Q.730
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
0\ \ 1\ \ 1	0\ \ 1\ \ 1\ \ 1	\ 55	 {
Incoming calls barred within CUG
 }	\fBQ.931,\fR  Q.730
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
0\ \ 1\ \ 1	1\ \ 0\ \ 0\ \ 1	\ 57	 {
Bearer capability not authorized
 }	Q.931, Q.763
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
0\ \ 1\ \ 1	1\ \ 0\ \ 1\ \ 0	\ 58	 {
Bearer capability not presently available
 }	Q.931, Q.763
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
0\ \ 1\ \ 1	1\ \ 1\ \ 1\ \ 0	\ 62	 {
Inconsistency in designated outgoing access information and subscriber
class
 }	\fBQ.931,\fR  Q.730
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
0\ \ 1\ \ 1	1\ \ 1\ \ 1\ \ 1	\ 63	 {
Service or option not available, unspecified
 }	Q.931, Q.763
_
.TE
.nr PS 9
.RT
.ad r
\fBTable B\(hy1/Q.699 [1T29.699], p.\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.ce
\fBH.T. [2T29.699]\fR 
.ce
TABLE\ B\(hy1/Q.699\ \fI(cont.)\fR 
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(24p) sw(30p) | cw(18p) | cw(114p) | cw(42p) , c | c | ^ | ^ | ^ .
Cause value	Cause number	Cause	Recommendations
Class	Value
_
.T&
cw(24p) | cw(30p) | lw(18p) | lw(114p) | lw(42p) .
7\ \ 6\ \ 5	4\ \ 3\ \ 2\ \ 1			
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
1\ \ 0\ \ 0	0\ \ 0\ \ 0\ \ 1	\ 65	 {
Bearer capability not implemented
 }	Q.931, Q.763
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
1\ \ 0\ \ 0	0\ \ 0\ \ 1\ \ 0	\ 66	Channel type not implemented	Q.931
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
1\ \ 0\ \ 0	0\ \ 1\ \ 0\ \ 1	\ 69	 {
Requested facility not implemented
 }	Q.931, Q.730
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
1\ \ 0\ \ 0	0\ \ 1\ \ 1\ \ 0	\ 70	 {
Only restricted digital information bearer capability is available
 }	Q.931, Q.763
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
1\ \ 0\ \ 0	1\ \ 1\ \ 1\ \ 1	\ 79	 {
Service or option not implemented, unspecified
 }	Q.931, Q.763
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
1\ \ 0\ \ 1	0\ \ 0\ \ 0\ \ 1	\ 81	Invalid call reference value	Q.931
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
1\ \ 0\ \ 1	0\ \ 0\ \ 1\ \ 0	\ 82	 {
Identified channel does not exist
 }	Q.931
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
1\ \ 0\ \ 1	0\ \ 0\ \ 1\ \ 1	\ 83	 {
A suspended call exists, but this call identity does not
 }	Q.931
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
1\ \ 0\ \ 1	0\ \ 1\ \ 0\ \ 0	\ 84	Call identity in use	Q.931
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
1\ \ 0\ \ 1	0\ \ 1\ \ 0\ \ 1	\ 85	No call suspended	Q.931
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
1\ \ 0\ \ 1	0\ \ 1\ \ 1\ \ 0	\ 86	 {
Call having the requested call identity has been cleared
 }	Q.931
_
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
1\ \ 0\ \ 1	0\ \ 1\ \ 1\ \ 1	\ 87	Called user not member of CUG	\fBQ.931,\fR  Q.730
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
1\ \ 0\ \ 1	1\ \ 0\ \ 0\ \ 0	\ 88	Incompatible destination	Q.931, Q.763
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
1\ \ 0\ \ 1	1\ \ 0\ \ 1\ \ 0	\ 90	Non\(hyexistent CUG	\fBQ.931,\fR  Q.730
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
1\ \ 0\ \ 1	1\ \ 0\ \ 1\ \ 1	\ 91	 {
Invalid transit network selection (Note 1)
 }	Q.931, Q.763
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
1\ \ 0\ \ 1	1\ \ 1\ \ 1\ \ 1	\ 95	Invalid message, unspecified	Q.931, Q.763
_
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
1\ \ 1\ \ 0	0\ \ 0\ \ 0\ \ 0	\ 96	 {
Mandatory information element is missing
 }	Q.931
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
1\ \ 1\ \ 0	0\ \ 0\ \ 0\ \ 1	\ 97	 {
Message type non\(hyexistent or not implemented
 }	Q.931, Q.763
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
1\ \ 1\ \ 0	0\ \ 0\ \ 1\ \ 0	\ 98	 {
Message not compatible with call state or message type non\(hyexistent
or not implemented
 }	Q.931
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
1\ \ 1\ \ 0	0\ \ 0\ \ 1\ \ 1	\ 99	 {
Information element non\(hyexistent or not implemented
(Note 2)
 }	Q.931, Q.763
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
1\ \ 1\ \ 0	0\ \ 1\ \ 0\ \ 0	100	 {
Invalid information element contents
 }	Q.931
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
1\ \ 1\ \ 0	0\ \ 1\ \ 0\ \ 1	101	 {
Message not compatible with call state
 }	Q.931
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
1\ \ 1\ \ 0	0\ \ 1\ \ 1\ \ 0	102	Recovery on timer expiry	Q.931
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
1\ \ 1\ \ 0	0\ \ 1\ \ 0\ \ 1	103	 {
Parameter non\(hyexistent or not implemented \(em passed on
 }	\fBQ.931,\fR  Q.763
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
1\ \ 1\ \ 0	1\ \ 1\ \ 1\ \ 0	110	Inconsistency in data	\fBQ.931,\fR  Q.730
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
1\ \ 1\ \ 0	1\ \ 1\ \ 1\ \ 1	111	Protocol error, unspecified	Q.931, Q.763
_
.T&
cw(24p) | cw(30p) | cw(18p) | lw(114p) | lw(42p) .
1\ \ 1\ \ 1	1\ \ 1\ \ 1\ \ 1	127	Interworking, unspecified	 {
Q.931, Q.763
All other values are reserved.
 }
.TE
.LP
\fINote\ 1\fR
\ \(em\ In Recommendation Q.763, the words \*Q(national use)\*U are
added.
.LP
\fINote\ 2\fR
\ \(em\ In Recommendation Q.763, the name of this cause value is
\*Qparameter non\(hyexistent or not implemented\(hydiscard\*U. Further alignment of
definition for this cause may be required.
.nr PS 9
.RT
.ad r
\fBTable B\(hy1/Q.699 [2T29.699], p.\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.sp 7
.bp
.sp 1P
.LP
B.2.6
	\fIDiagnostic(s)\fR 
.sp 9p
.RT
.ce
\fBH.T. [T30.699]\fR 
.ce
TABLE\ B\(hy2/Q.699
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(18p) | cw(168p) | cw(42p) .
Cause	Diagnostic(s)	Recommendations
_
.T&
cw(18p) | lw(168p) | lw(42p) .
\ \ 1	Condition (Note 1)	Q.931, Q.763
.T&
cw(18p) | lw(168p) | lw(42p) .
\ \ 2	Transit Network identity	Q.931, Q.763
.T&
cw(18p) | lw(168p) | lw(42p) .
\ \ 3	Condition (Note 1)	Q.931, Q.763
.T&
cw(18p) | lw(168p) | lw(42p) .
\ 16	Condition (Note 1)	Q.931, Q.763
.T&
cw(18p) | lw(168p) | lw(42p) .
\ 21	 {
Condition (Note 1), User supplied diagnostics
 }	Q.931, Q.763
.T&
cw(18p) | lw(168p) | lw(42p) .
\ 22	 {
New Destination [Q.931]/Called party number (new) [Q.763]
 }	Q.931, Q.763
.T&
cw(18p) | lw(168p) | lw(42p) .
\ 29	 {
Facility identification [Q.931]/Rejected parameter [Q.763]
 }	Q.931, Q.730
.T&
cw(18p) | lw(168p) | lw(42p) .
\ 43	 {
Discarded information element identifier(s)
 }	Q.931
.T&
cw(18p) | lw(168p) | lw(42p) .
\ 49	Condition (Note 2)	Q.931
.T&
cw(18p) | lw(168p) | lw(42p) .
\ 50	 {
Facility identification [Q.931]/Rejected parameter [Q.763]
 }	Q.931, Q.730
.T&
cw(18p) | lw(168p) | lw(42p) .
\ 57	Attribute identity (Note 2)	Q.931, Q.763
.T&
cw(18p) | lw(168p) | lw(42p) .
\ 58	Attribute identity (Note 2)	Q.931, Q.763
.T&
cw(18p) | lw(168p) | lw(42p) .
\ 65	Attribute identity (Note 2)	Q.931, Q.763
.T&
cw(18p) | lw(168p) | lw(42p) .
\ 66	Channel type	Q.931
.T&
cw(18p) | lw(168p) | lw(42p) .
\ 69	 {
Facility identification [Q.931]/Rejected parameter [Q.763]
 }	Q.931, Q.730
.T&
cw(18p) | lw(168p) | lw(42p) .
\ 82	Channel identity	Q.931
.T&
cw(18p) | lw(168p) | lw(42p) .
\ 86	Clearing cause	Q.931
.T&
cw(18p) | lw(168p) | lw(42p) .
\ 88	 {
Incompatible parameter [Q.931]
 }	Q.931, Q.763
.T&
cw(18p) | lw(168p) | lw(42p) .
\ 96	 {
Information element identifier
 }	Q.931
.T&
cw(18p) | lw(168p) | lw(42p) .
\ 97	Message type	Q.931, Q.763
.T&
cw(18p) | lw(168p) | lw(42p) .
\ 98	Message type	Q.931
.T&
cw(18p) | lw(168p) | lw(42p) .
\ 99	 {
Information element identifier(s) [Q.931]/Parameter name(s) [Q.763]
 }	Q.931, Q.763
.T&
cw(18p) | lw(168p) | lw(42p) .
100	 {
Information element identifier(s)
 }	Q.931
.T&
cw(18p) | lw(168p) | lw(42p) .
101	Message type	Q.931
.T&
cw(18p) | lw(168p) | lw(42p) .
102	Timer number	Q.931
.T&
cw(18p) | lw(168p) | lw(42p) .
103	Parameter name(s)	 {
\fBQ.931,\fR
Q.763
 }
.TE
.LP

\fINote\ 1\fR
\ \(em\ The following coding is used:
.LP
Bit 8:
1
Bits 7\(hy3:
00000
Bits 2\(hy1:
Condition as follows:
00 \(em Unknown
01 \(em Permanent
10 \(em Transient.
.LP
\fINote\ 2\fR
\ \(em\ The format of the diagnostic field for causes number\ 57, 58 and 65 is as shown in Figure\ B\(hy2/Q.699 and Table\ B\(hy2a/Q.699 to B\(hy2b/Q.699.
.LP
\fINote\ 3\fR
\ \(em\ Description in [ ] indicates current difference in description
among Recommendations\ Q.931 and\ Q.763. Further alignment may be required for
those cause values, i.e., ##22, ##29, ##50, ##69 and ##99.
.nr PS 9
.RT
.ad r
\fBTable B\(hy2/Q.699 [T30.699], p.\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.sp 5
.bp
.LP
.rs
.sp 18P
.ad r
\fBFigure B\(hy2/Q.699 [T31.699], p.\ (traiter comme tableau MEP)\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.sp 6
.rs
.sp 15P
.ad r
\fBFigure B\(hy2a/Q.699 [T32.699], p.\ (traiter comme tableau MEP)\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.sp 6
.bp
.ce
\fBH.T. [T33.699]\fR 
.ce
TABLE\ B\(hy2b/Q.699
.ce
\fBCoding of the diagnostic field for causes number 57, 58 and 65\fR 
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
lw(228p) .
 {
\fIRejected attribute (octet 5a)\fR
 }
.T&
lw(228p) .
Attribute No. 
.T&
lw(228p) .
 {
\ \ 1.
\fIInformation transfer capability:\fR
.LP
Bits 7\(hy6 : 00
.LP
Bits 5\(hy1 according to Table 4\(hy6, octet 3.
 }
.T&
lw(228p) .
 {
\ \ 2.
\fIInformation transfer mode:\fR
.LP
Bits 7\(hy6 according to Table 4\(hy6, octet 4.
.LP
Bits 5\(hy1 : 00000
 }
.T&
lw(228p) .
 {
\ \ 3.
\fIInformation transfer rate:\fR
.LP
Bits 7\(hy6 : 00
.line
Bits 5\(hy1 according to Table 4\(hy6, octet 4.
 }
.T&
lw(228p) .
 {
\ \ 4.
\fIStructure:\fR
.LP
Bits 7\(hy5 according to Table 4\(hy6, octet 4a.
.LP
Bits 4\(hy1 : 0000
 }
.T&
lw(228p) .
 {
\ \ 5.
\fIConfiguration:\fR
.LP
Bits 7\(hy5 : 000
.LP
Bits 4\(hy3 according to Table 4\(hy6, octet 4a.
.LP
Bits 2\(hy1 : 00
 }
.T&
lw(228p) .
 {
\ \ 6.
\fIEstablishment:\fR
.LP
Bits 7\(hy3 : 00000
.LP
Bits 2\(hy1 according to Table 4\(hy6, octet 4a.
 }
.T&
lw(228p) .
 {
\ \ 7.
\fISymmetry:\fR
.LP
Bits 7\(hy6 according to Table 4\(hy6, octet 4b.
.LP
Bits 5\(hy1 : 00000
 }
.T&
lw(228p) .
 {
\ \ 8.
\fIInformation transfer rate (dest. \(ra orig.):\fR
.LP
Bits 7\(hy6 : 00
.LP
Bits 5\(hy1 according to Table 4\(hy6, octet 4b.
 }
.T&
lw(228p) .
 {
\ \ 9.
\fILayer identification:\fR
.LP
Bits
.LP
7\ \ 6
.LP
0\ \ 1\ \ (layer 1)\ \ Bits 5\(hy1 according to Table 4\(hy6, octet 5.
.LP
1\ \ 0\ \ (layer 2)\ \ Bits 5\(hy1 according to Table 4\(hy6, octet 6.
.LP
1\ \ 1\ \ (layer 3)\ \ Bits 5\(hy1 according to Table 4\(hy6, octet 7.
 }
.T&
lw(228p) .
 {
\fIAvailable attributes (octet 5b)\fR
.LP
The same coding as octet 5a.
.TE
.LP
\fINote\fR
\ \(em\ Table 4\(hy6 referred to above is found in Recommendation Q.931. The
relevant description is found in \(sc\ 3.36 of Recommendation\ Q.763.
.nr PS 9
.RT
.ad r
\fBTableau B\(hy2b/Q.699 [T33.699], p.\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.sp 8
.bp