.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
\fBRecommendation\ Q.82\fR 
.RT
.sp 2P
.sp 1P
.ce 1000
\fBCALL\ OFFERING\ SUPPLEMENTARY\ SERVICES\fR 
.EF '%	Fascicle\ VI.1\ \(em\ Rec.\ Q.82''
.OF '''Fascicle\ VI.1\ \(em\ Rec.\ Q.82	%'
.ce 0
.sp 1P
.LP
\fB1\fR 	\fBCall transfer\fR 
.sp 1P
.RT
.PP
Under study.
.RT
.LP
\fB2\fR 	\fBCall forwarding services\fR 
.sp 1P
.RT
.sp 2P
.LP
2.1
	\fIIntroduction\fR 
.sp 1P
.RT
.sp 1P
.LP
2.1.1
	\fIGeneral\fR 
.sp 9p
.RT
.PP
This Recommendation includes stage 2 descriptions for the three
versions of call forwarding services given below, when implemented using the
\*Qforward switching\*U network routing algorithm described in
Recommendation\ Q.80.
.PP
The following descriptions are for further study:
.RT
.LP
	\(em
	re\(hyrouting case as described in Recommendation Q.80;
.LP
	\(em
	the optional notification to be sent to the calling user\ A
when the value of the subscription option \*Qcalling user receives notification 
that his call has been forwarded\*U is \*Qyes, with forwarded\(hyto\(hyuser 
number\*U; 
.LP
	\(em
	 the optional notification to be sent to the served user B\dm\uwhen the 
value of the subscription option \*Qserved user receives notification 
that his call has been forwarded\*U is \*Qyes, with call offering
information\*U.
.PP
Further details and definitions of the stage 1 description, i.e., the service 
description as seen from the user, can be found in 
Recommendation\ I.252.
.sp 2P
.LP
2.1.2
	\fIDefinitions\fR 
.sp 1P
.RT
.sp 1P
.LP
	\fBcall forwarding unconditional (CFU)\fR 
.sp 9p
.RT
.PP
Call forwarding unconditional (CFU) permits a user to have the
network send all incoming calls, or just those associated with a specific 
basic service, addressed to the served user's ISDN number to another number. 
The 
served user's originating service is unaffected. If this service is activated, 
calls are forwarded no matter what the condition of the termination. Other 
.PP
call forwarding services provide call forwarding based on condition, e.g. 
call forwarding busy (CFB) and call forwarding no reply (CFNR). 
.RT
.sp 1P
.LP
	\fBcall forwarding busy (CFB)\fR 
.sp 9p
.RT
.PP
Call forwarding busy (CFB) permits a served user to have the
network send all incoming calls, or just those associated with a specific 
basic service, which meet busy and are addressed to the served user's ISDN 
number to another number. The served user's originating service is unaffected. 
.RT
.sp 1P
.LP
	\fBcall forwarding no reply (CFNR)\fR 
.sp 9p
.RT
.PP
Call forwarding no reply (CFNR) permits a served user to have the network 
send all incoming calls, or just those associated with a specific basic 
service, which meet no reply and are addressed to the served user's ISDN 
number to another number. The served user's originating service is unaffected. 
.bp
.RT
.sp 1P
.LP
2.2
	\fICall forwarding setup and release\fR 
.sp 9p
.RT
.LP
.rs
.sp 40P
.ad r
\fBFigure 2\(hy1/Q.82, p.\fR 
.sp 1P
.RT
.ad b
.RT
.sp 1P
.LP
2.2.1
	\fIInformation flow diagrams\fR 
.sp 9p
.RT
.PP
Call forwarding unconditional and for \*Qnetwork determined user
busy\*U: Figure\ 2\(hy2/Q.82.
.PP
Call forwarding for \*Quser determined user busy\*U: Figure\ 2\(hy3/Q.82.
.PP
Call forwarding on no reply: Figure\ 2\(hy4/Q.82.
.PP
Call forwarding disconnect procedure (including advice of charge):
Figure\ 2\(hy5/Q.82.
.bp
.RT
.LP
.rs
.sp 47P
.ad r
\fBFigure 2\(hy2/Q.82, p. (\*`a l'italienne)\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure 2\(hy3/Q.82, p. (\*`a l'italienne)\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure 2\(hy4/Q.82 (sheet 1 of 4), p. (\*`a l'italienne)\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
\fINotes related to Figures 2\(hy2 to 2\(hy4/Q.82\fR 
.LP
\fINote\ 1\fR \ \(em\ The calling party number and the last forwarding 
number should be 
included if required by the \*Qcalling line identification presentation\*U
supplementary service.
.LP
\fINote\ 2\fR \ \(em\ The notification should be sent only if the B\(hyparty 
subscribes to 
the \*Qcalling user receives notification that his call has been forwarded\*U
subscription option.
.LP
\fINote\ 3\fR \ \(em\ The connected number is included if required by the 
\*Qconnected line Identification presentation/restriction\*U supplementary 
service. 
.LP
\fINote\ 4\fR \ \(em\ The forwarded\(hyto\(hyuser will receive this information 
depending on his notification option, the availability of this information 
from the network and possible presentation restrictions. 
.LP
\fINote\ 5\fR \ \(em\ This parameter may be omitted between FE4 and FE6 
in order to limit the number of parameters to be passed in the network 
(see Table\ 2\(hy6/Q.82, 
Note\ 1).
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure 2\(hy5/Q.82 (sheet 2 of 4) A L'ITALIENNE, p.\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure 2\(hy4/Q.82 (sheet 3 of 4) A L'ITALIENNE, p.\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure 2\(hy4/Q.82 (sheet 4 of 4) A L'ITALIENNE, p.\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure 2\(hy5/Q.82 p.\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.sp 1P
.LP
2.2.2
	\fISDL diagram for FE4/FE6/FE8\fR 
.sp 9p
.RT
.LP
.rs
.sp 47P
.ad r
\fBFigure 2\(hy6/Q.82 (feuillet 1 sur 8), p.\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure 2\(hy6/Q.82 (sheet 2 of 8), p.\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure 2\(hy6/Q.82 (sheet 3 of 8), p.\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure 2\(hy6/Q.82 (sheet 4 of 8), p.\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure 2\(hy6/Q.82 (sheet 5 of 8), p. (\*`a l'italienne)\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure 2\(hy6/Q.82 (sheet 6 of 8), p.\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure 2\(hy6/Q.82 (sheet 7 of 8), p.\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 26P
.ad r
\fBFigure 2\(hy6/Q.82 (sheet 8 of 8), p.\fR 
.sp 1P
.RT
.ad b
.RT
.sp 1P
.LP
2.2.3
	\fISDL diagrams for other FEs\fR 
.sp 9p
.RT
.PP
These are not explicitly shown since they are equal to basic
services (CC or CCA) SDLs with small additions which can be easily derived 
from the information flow diagrams. 
.RT
.sp 1P
.LP
2.2.4
	\fIDefinition of individual information flows\fR 
.sp 9p
.RT
.PP
Refer to information indicated in the Notes related to Figures\ 2\(hy2 
to 2\(hy5/Q.82 and \(sc\ 2.2.5. 
.RT
.sp 1P
.LP
2.2.5
	\fIMultiple diversion address handling\fR 
.sp 9p
.RT
.LP
.rs
.sp 10P
.ad r
\fBFigure 2\(hy7/Q.82, p.\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.ce
\fBH.T. [T1.82]\fR 
.ce
TABLE\ 2\(hy1/Q.82
.ce
\fBInformation carried in the SETUP req. ind\fR 
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(84p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) .
Parameter	HOP 1	HOP 2	HOP 3	HOP 4	HOP 5	HOP 6
_
.T&
lw(84p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) .
Calling party number	A	A	A	A	A	A
_
.T&
lw(84p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) .
Called party number	B 1	B 2	B 3	B 4	B 5	C
_
.T&
lw(84p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) .
Last forwarding number	\fB.\fR	B 1  Note 1	B 2  \fB.\fR	B 3  \fB.\fR	B 4  \fB.\fR	B 5 \fB.\fR
_
.T&
lw(84p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) .
Original call number	\fB.\fR	B 1	B 1	B 1	B 1	B 1
_
.T&
lw(84p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) .
Forwarding counter	\fB.\fR	1	2	3	4	5
_
.T&
lw(84p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) .
Last forwarding cause	\fB.\fR	V(B 1)  Notes 1, 2	V(B 2)  Note 2	V(B 3)  Note 2	V(B 4)  Note 2	V(B 5)  Note 2
_
.T&
lw(84p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) .
Original forwarding cause	\fB.\fR	V(B 1)  Note 2	V(B 1)  Note 2	V(B 1)  Note 2	V(B 1)  Note 2	V(B 1) Note 2
.TE
.LP
\fINote 1\fR
\ \(em\ May be omitted to limit the number of parameters being passed
in the network.
.LP
\fINote 2\fR
\ \(em\ V(B
1) indicates the reason for diversion from party B
1 with a value (V) equal to: unknown/not available, user busy, no reply or unconditional when diversion occurs.
.nr PS 9
.RT
.ad r
\fBTable 2\(hy1/Q.82 [T1.82], p.\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.sp 6
.ce
\fBH.T. [T2.82]\fR 
.ce
TABLE\ 2\(hy2/Q.82
.ce
\fBInformation in the backward direction\fR 
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(84p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) .
Parameter	HOP 1	HOP 2	HOP 3	HOP 4	HOP 5	HOP 6
_
.T&
lw(84p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) .
Notification from	\fB.\fR	B 1	B 2	B 3	B 4	B 5
_
.T&
lw(84p) | cw(24p) | cw(96p) | lw(24p) .
 {
Forwarded\(hyto\(hynumber from
 }	\fB.\fR	For further study	
_
.TE
.nr PS 9
.RT
.ad r
\fBTable 2\(hy2/Q.82 [T2.82], p.\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.sp 1P
.LP
2.2.6
	\fIFunctional entity actions\fR \v'3p'
.sp 9p
.RT
.LP
	1)
	Functional entity actions for FE1
.LP
	\(em
	Receive indications relating to the service from
FE2.
.LP
	2)
	Functional entity actions for FE2
.LP
	\(em
	Receive indications relating to the service from FE4
and forward them to FE1.
.LP
	3)
	Functional entity actions for FE3
.LP
	\(em
	No functional entity actions uniquely relating to this
service are identified for FE3.
.LP
	4)
	Functional entity actions for FE4/FE6
.LP
	\(em
	Store call information and user's service allocation
and state.
.LP
	\(em
	Run periodic timers specific to the service.
.LP
	\(em
	Stimulate forward basic call setups to nominated
numbers when service is active.
.LP
	\(em
	Increment service call counts and forward to next
FE4/6.
.LP
	\(em
	Stimulate release procedures at service call count
limit.
.LP
	\(em
	Receive and implement user's service requests from
FE5/7.
.LP
	\(em
	Determine information to be notified backwards to other
users.
.LP
	5)
	Functional entity actions for FE5/FE7
.LP
	\(em
	Receive indications relating to the service from FE4/6.
.LP
	\(em
	Receive and forward user's service requests to
FE4/5.
.LP
	6)
	Functional entity actions for FE8
.LP
	\(em
	Receive and increment forward call counter.
.LP
(\fINote\fR \ \(em\ This is an attribute of FE4/6.)
.LP
	\(em
	Send forwarding indicators relating to the service of
FE9 (this would be an attribute to FE6).
.LP
	7)
	Functional entity actions for FE9
.LP
	\(em
	Receive indications relating to the service
from FE8.
.sp 1P
.LP
2.3
	\fIPossible allocation of functional entities to physical locations\fR 
.sp 9p
.RT
.ce
\fBH.T. [T3.82]\fR 
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(36p) | lw(18p) | cw(36p) | cw(36p) | cw(36p) .
A PARTY		B 1 PARTY	B x PARTY	C PARTY
_
.TE
.TS
cw(18p) | cw(18p) | cw(18p) | cw(18p) | cw(18p) | cw(18p) | cw(18p) | cw(18p) | cw(18p) .
FE1	FE2	FE3	FE4	FE5	FE6	FE7	FE8	FE9
_
.T&
lw(42p) | cw(18p) | cw(18p) | cw(18p) | cw(18p) | cw(18p) | cw(18p) | cw(18p) | cw(18p) | cw(18p) .
Scenario 1	TE	LE	TR	LE	TE	LE	TE	LE	TE
_
.TE
.nr PS 9
.RT
.ad r
\fBTable [T3.82], p.\fR 
.sp 1P
.RT
.ad b
.RT
.PP
.sp 3
Other scenarios are for further study.
.sp 1P
.LP
2.4
	\fIInteractions with other supplementary services\fR 
.sp 9p
.RT
.PP
The interaction with supplementary services, such as calling line identification, 
connect\(hytest line identification and advice of charge have been considered; 
interactions with other supplementary services are for further 
study.
.bp
.RT
.sp 1P
.LP
2.5
	\fITerminology and abbreviations\fR 
.sp 9p
.RT
.PP
Abbreviations used:
.RT
.LP
	CFU
	Call forwarding unconditional
.LP
	CFB
	Call forwarding on busy
.LP
	CFNR
	Call forwarding on no reply
.LP
	CD
	Call deflection
.LP
	CC
	Call control
.LP
	CCA
	Call control agent
.LP
	FE
	Functional entity
.LP
	TE
	Terminal equipment
.LP
	LE
	Local exchange
.LP
	TR
	Transit exchange
.LP
	NDUB
	Network determined user busy
.LP
	UDUB
	User determined user busy
.LP
	Terminology:
.LP
	\fIOriginal called number:\fR 
.LP
	The number the originating party dials.
.LP
	\fIConnected line number:\fR 
.LP
	The number of the final destination.
.LP
	\fIForwarding number:\fR 
.LP
	The number of the served user, i.e. the subscriber who
initiates the forwarding service and from where the
call has been forwarded.
.LP
	\fIForwarded\(hyto\(hynumber:\fR 
.LP
	The number to which a call has been forwarded.
.LP
	\fIForwarding indicator:\fR 
.LP
	Indicator showing that call has been forwarded and
indicating whether or not this information should be
given to calling party.
.sp 2P
.LP
\fB3\fR 	\fBCall deflection\fR 
.sp 1P
.RT
.PP
Under study.
.RT
.LP
\fB4\fR 	\fBLine hunting\fR 
.sp 1P
.RT
.sp 2P
.LP
4.1
	\fIIntroduction\fR 
.sp 1P
.RT
.sp 1P
.LP
4.1.1
	\fIDefinition\fR 
.sp 9p
.RT
.PP
Line hunting is a supplementary service which enables incoming calls to 
a specific ISDN number to be distributed over a group of interfaces. 
.PP
\fINote\fR \ \(em\ Expansion of the line hunting service to cover the case of
hunting on available ISDN numbers or addresses, rather than on interfaces 
is a possible extension of the service. 
.RT
.sp 1P
.LP
4.1.2
	\fIDescription\fR 
.sp 9p
.RT
.PP
This description covers the form of line hunting which applies to interfaces 
within one node. It is an anticipated further extension to enable 
the group of interfaces available for selection to be distributed over more
than one node.
.PP
The selection of an interface within a node is performed on the basis of 
the hunting algorithm used. (Where hunting is extended over more than one 
node the network routing techniques used to extend the selection to the next
.PP
node may be similar to that used for the call forwarding supplementary 
service, though applied by the Administration. The precise description 
of multi\(hynode 
line hunting is for further study.)
.PP
An access belonging to a line hunting group may also be addressed
using an individual ISDN number. Facilities associated with the individual
number are not affected by line hunting.
.bp
.RT
.sp 1P
.LP
4.2
	\fIDefinition of the functional model\fR 
.sp 9p
.RT
.PP
The additional functionality required for line hunting, over that of the 
basic service, is confined to a single node, as seen in 
Figure\ 4\(hy1/Q.82.
.RT
.LP
.rs
.sp 11P
.ad r
\fBFigure 4\(hy1/Q.82, p.\fR 
.sp 1P
.RT
.ad b
.RT
.sp 2P
.LP
4.3
	\fIInformation flow\fR 
.sp 1P
.RT
.sp 1P
.LP
4.3.1
	\fIFlow for single node hunting\fR 
.sp 9p
.RT
.PP
For the single node case, the information flows are those defined for the 
basic call as shown in Figure\ 4\(hy2/Q.82. No information flows arise 
as a result of the hunting action. 
.RT
.LP
.rs
.sp 23P
.ad r
\fBFigure 4\(hy2/Q.82, p. 22\fR 
.sp 1P
.RT
.ad b
.RT
.sp 1P
.LP
4.3.2
	\fIFlow for multi\(hynode hunting\fR 
.sp 9p
.RT
.PP
This is for further study.
.bp
.RT
.sp 1P
.LP
4.4
	\fISDL diagrams\fR 
.sp 9p
.RT
.PP
The SDL diagrams for the entity FE1 are shown in Figure\ 4\(hy3/Q.82
and Figure\ 4\(hy4/Q.82.
.RT
.LP
.rs
.sp 49P
.ad r
\fBFigure 4\(hy3/Q.82, p. 23\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure 4\(hy3/Q.82, p.\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.sp 2P
.LP
4.5
	\fIFunctional entity actions\fR 
.sp 1P
.RT
.sp 1P
.LP
4.5.1
	\fISingle node hunting\fR 
.sp 9p
.RT
.PP
The FEAs attributed to entity FE1, the line hunting entity,
indicated by (1) on the information flow diagram are as follows:
.RT
.LP
	\(em
	determine hunting algorithm;
.LP
	\(em
	select free interface.
.sp 1P
.LP
4.5.2
	\fIMulti\(hynode line hunting\fR 
.sp 9p
.RT
.PP
FEAs, in addition to the single node FEAs, which are required for hunting 
over more than one node are for further study. 
.RT
.sp 1P
.LP
4.6
	\fIPhysical locations for functional entities\fR 
.sp 9p
.RT
.PP
The scenarios which apply to line hunting are shown in
Table 4\(hy1/Q.82.
.RT
.ce
\fBH.T. [T4.82]\fR 
.ce
TABLE\ 4\(hy1/Q.82
.ce
\fBPossible line hunting scenarios \fR 
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
lw(84p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) .
Functional entities Scenario	CCA	CC 	CC 	CC/FE1	CC	CCA
_
.T&
lw(84p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) .
1)\ Basic rate access	TE	LE	TR	LE	\(em	TE
_
.T&
lw(84p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) .
2)\ Basic rate access	TE	LE	TR	NT2	\(em	TE
_
.T&
lw(84p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) | cw(24p) .
3)\ Primary rate access	TE	LE	TR	LE	NT2	TE
_
.TE
.nr PS 9
.RT
.ad r
\fBTableau 4\(hy1/Q.82 [T4.82], p.\fR 
.sp 1P
.RT
.ad b
.RT
.LP
.rs
.sp 20P
.sp 2P
.LP
\fBMONTAGE: RECOMMANDATION Q.83 SUR LE RESTE DE CETTE PAGE\fR 
.sp 1P
.RT
.LP
.bp