0
B
T/CS 49-08 E
Page 1
P
-.
Recommendation
SYSTEM
L1 MULTIFREQUENCY
Recommendation
proposed
Text of the Recommendation
“The European
Conference
T/CS 49-08 (Vienna 1982)
CODE CALL CONTROL
by Working
Group T/WG
adopted by the ‘<Telecommunications”
of Postal and Telecommunications
SIGNALING
11 “Switching
PROCEDURES
and Signaling”
(CS)
Commission:
Administrations,
considering
— that Recommendation
T/CS 49-07 [1] provides for multifrequency
code (MFC) signaling functions between
private automatic branch exchanges (PABXS), which are suitable for the fast set-up of calls and the provision of
supplementary services,
-
— that supplementary
services already available to extension users within a single PABX need to be extended
extension users on others PABXS within a private network,
to
recommends
to the members, that the signaling procedures specified below are used when MFC interregister
between private branch exchanges in different countries.”
signaling
is applied
1.
GENERAL
1.1.
Outline
1.1.1.
On international inter-PABX lines, System L1 MFC interregister signaling, as specified in Recommendation T/CS 49-07 [1], is used in conjunction with L1 line signaling, as specified in Recommendation
T/CS 49-01 [2].
1.1.2.
System L1 MFC provides, in principle, the inter-PABX signaling capability to enable a wide range from
set-up of simple calls to a variety of supplementary services to be made available to extension users and
operators.
1.1.3.
The range of supplementary
services provided by a PABX is optional, and depends upon customer
requirements and PABX capability. In any given private network, PABXS of differing capability will be
encountered, and the procedures specified for System L 1 MFC in this Recommendation
take this into
account. During the initial set-up of the call, an interchange of terminal status information takes place
between originating and terminating
PABXS. This enables certain subsequent supplementary
service
demands, from either the interconnected terminals or a third party, to be processed locally without recourse
to inter-PABX signaling.
1.1.4.
Where a supplementary
service demand requires inter-PABX signaling, the request is handled by the
responding PABX on an accept or reject basis, depending upon the availability of the service at that PABX.
1.1.5.
PABXS that do not provide any supplementary services, but require System L1 MFC signaling capability
for fast call set-up and private network compatibility reasons, can utilise a subset of System L1 MFC
signaling procedures referred to as basic. The basic subset provides, as a minimum, the necessary repertoire
of signals to establish an extension-to-extension
call, with an optional procedure to provide locally applied
supervisory tones and limited class-of-service information.
1.2.
Signals
1.2.1.
Interregister
signals
The System 1.1 MFC interregister signals, as well as the 2280 Hz signal for the initiation of the MFC
signaling, are specified in Recommendation
T/CS 49-07 [1]. This includes their allocation to the multifrequency codes and the abbreviations used.
1.2.2.
Line signals
Table
1 (T/CS
49-08)
shows
the System
L1 line signals
which
are used in conjunction
with System
LI MFC
interregister signaling. The meanings of these signals comply with Recommendation
T/CS 41-01 [3]. The
requirements for the transmission of these signals are given in Recommendation
T/CS 49-01 [2].
Edition of September 15, 1986
T/CS 49-08
Page 2
E
Seizing
Answer
Clear-forward
Clear-back
Cleared
Forward-service-request-recall
Forward-link-recall
Backward-service-request-recall
Backward-link-recall
Tablel
2.
SIGNALING
2.1.
General
(T/CS 49-08).
Line signals used for System Ll MFC.
PROCEDURES
This section gives the signaling
procedures
in three parts:
— outline of call control procedures;
— description of the signaling procedures for selection, subset compatibility
Note: This part requires further study. See contribution T/CS (82) 109 [4].
check and dialogue phases;
signal flows in arrow chart form and SDL sequence charts according to CCITT RecommendationZ.101
[5], Z.102 [6] and Z.104 [7].
Note: The SDL diagrams are included in this Recommendation to assist in the understanding of the technical text, and
—
must only be used in association
with the text.
2.2.
Outline of call control procedures
2.2.1.
Establishment of a call by means of System L 1 MFC can be considered
phase, the subset compatibility check phase, and the dialogue phase.
2.2.2.
The selection phase, which includes access to an enhanced routing subset 1), is standard
applications. It enables establishment of an ordinary call.
2.2.3.
The dialogue phase is carried out by one of the following signaling
— Basic:
provides a minimum
— Enhanced:
provides capability
interworking
capability
in three main phases: the selection
procedures
in all System L1 MFC
subsets:
to enable simple call set-up;
for call set-up plus access to supplementary
service procedures;
— Manufacturer:
subsets enabling specific manufacturer’s
procedures to be used (see Paragraph 2.5.3.).
Where part of a multi-link call is routed via a non-MFC private circuit, no dialogue phase will take place.
2.2.4.
The particular subset used will depend upon the capabilities of the interconnected PABXS, and is determined
by the subset compatibility check, which is carried out after the selection phase and before possibly entering
the dialogue phase.
2.2.5.
When the dialogue phase has been entered, both PABXS exchange information
and destination parties in either basic or enhanced working.
2.2.6.
The signaling
2.2.7.
In basic working,
2.2.8.
In enhanced working, the interchange involves at least two signals in each direction and, if a supplementary
service is involved, may extend to many more, except for states such as parked where only one signal
interchange need take place.
2.2.9.
The signal exchange for a supplementary service is a function of the service concerned. The procedures based
on supplementary services harmonised by CEPT are specified in Annexes to this Recommendation.
Procedures required for other categories of supplementary services, e.g. defined for national use or marketed by
PABX providers, are not covered in this Recommendation.
However, provisions are made in System L1
MFC to gain access to such procedures (see Paragraph 2.5.2.3.).
2.2.10.
In basic working,
procedures
structure
regarding
in Figure 1 (T/CS 49-08) shows the relationship
the dialogue phase interchange
the service-request-recall
the originating
between the subsets.
is limited to one signal in each direction.
and link-recall
signals are not used.
‘) Under study.
Edition of September 15, 1986
TICS 49-08 E
Page 3
L
Subset
A-6
I
compat i b i Li ty check
A-7
A-3
&
n
n
Basic
L-
Enhanced
L
R
r
Manufacturer
Suppt ementary
service
I
I
RR
Non-harmonised
supp ( ementary
serv i ces
Harmoni sed
supp ( ementary
serv i ces
*
Conversat ion or c Lear-down
L
Legend:
R
=
revert.
RR
=
register-recall.
A
=
group A backward
signal.
Figure 1 (T/CS 49-08).
n
Edition of September 15, 1986
I
request
System L1 signaling
procedures
structure.
TJCS 49-08 E
Page 4
2.2.11.
PABXS with transit functions must be capable of repeating a service-request-recall
signal to the next link.
If a transit switch is not capable of using a link-recall signal, it will take no action on its recognition.
2.3.
Signaling
procedures for the selection phase
The selection phase covers all signaling necessary to establish a connection between the originating and
destination PABXS, including the forwarding of the required extension number to the destination PABX.
The selection phase is entered, following the application of the seizing signal by the originating PABX. On
recognition of the seizing signal, the responding PABX prepares to receive MFC signals and applies the
proceed-to-send
signal.
As a multi-link call is progressively set-up across a network (see Recommendation
T/CS 49-07 [1]), each
transit switch applies a seizing signal to the subsequent link, and each responding PABX applies the
proceed-to-send
signal.
To facilitate network management, backward MFC signals are used during the selection phase to
i)
request address signals (routing digits and extension number) one after the other from the originating
PABX, as required by the transit switch or terminating PABX; when all address digits have been sent,
the originating PABX responds if it receives a further send-next-digit signal by sending the no-furtherdigit signal (1-15);
ii) inform the originating PABX of the progress of the call, e.g. how many transit switches have been
encountered;
iii) inform the originating PABX of alternative routing that has occurred at a transit switch;
iv) inform the originating PABX that access to the public switched telephone network (PSTN) is about
to occur;
v) request entry into the optional enhanced routing subset 1)in order to influence the routing of the call,
e.g. special quality circuits for data.
Figure 2 (T/CS 49-08) shows the selection phase in arrow chart form.
Figure 3 (T/CS 49-08) shows the entry into the enhanced
2.4.
Signaling
procedures for subset compatibility
routing subset in arrow chart form.
check
On completion of selection, it is necessary for the originating and destination PABXS to determine whether
MFC signaling is going to continue, and if so, which procedure subset is to be used for the remainder of
the call handling.
If no further MFC signaling is possible (e.g. a non-MFC route or a PSTN has been encountered by a transit
switch), an address-complete,
no-MFC, set-up-speech-path
signal will be sent (A-6).
Where further MFC signaling is possible, the subset compatibility check is initiated by the destination
PABX, which applies one of the following signals (see Figure 1 (T/CS 49-08)):
i)
Address-complete,
enhanced, change-over-to-reception-of-group-B
signals (A-1 1);
ii) Address-complete,
request-subset-identity
(A-7);
iii) Address-complete,
basic, change-over-to-reception-of-group-B
signals (A-3).
The originating PABX responds by either:
(a) implicitly accepting the proposed subset (enhanced or basic) by sending forward information as shown
in Section 2.5.;
(b)
~~plicitly agreeing to attempt entry into a manufacturer subset by sending forward its subset identity
digit(s) for subset compatibility checking (the range required and the allocation of subset identity digits
is under study);
(c)
~~ecting the proposed subset by sending either the enhanced-request-not-accepted
request-not-accepted
signal.
The originating
or the manufacturer-
PABX cannot reject a request to enter basic.
On receipt of either a request-not-accepted
signal or an incompatible manufacturer subset identity, the
destination PABX will offer another subset. This interaction will continue until a common subset is found
(usually enhanced or basic). Figure 4 (T/CS 49-08) shows the subset compatibility check in arrow chart form.
2.5.
Signaling
procedures for the dialogue phase
On completion
subsets.
of the subset compatibility
check, both PABXS enter one of the following
procedures
‘)Under study.
Edition of September 15, 1986
T/CS 49-08 E
Page 5
PABX(0)
PABX(T)
PABX(X)
seize
.———
(line signal)
Proceed to send (Iine signal)
/
—
A–1
i–N
(routing
digit)
A–1
(send next signal)
I–N
(routing
digtt)
(send next signal)
‘f+——
Continue
with
\
routing
is
call
tandem to
PABX
?
No
—.
—
Seize (line signal)
9
-7
l-—
Proceed
Yes
to send (line signal)
I \——----—----—–--——
A–14
<
(tandem
d
encountered–
send next digit)
Switchthrough
—
..—
+———————— ——————
I–N
l-l
(routing
——
(send nexl signal)
Continue
Figure 2 (T/CS 49-08).
Edition of September 15, 1986
digit)
with
Routing
routing
via a transit PABX.
-——-+
TICS 49-08 E
Page 6
+jZii+-----
____
_
–—----F~-dL-—.-
I–N
——
(routing
digit)
—-+””-1
>
/
A–1
\
(send next siqnal)
or other
Continue
A-12
‘A’ signal
as shown in fiq.
(enhanced
routing–no
2
4
Does
PABX(T)
No need to send
info to
PABX
?
information)
<
Yes
Does
PABX(0)
need to send
info to
PABX(T)
?
I–N
(next digit)
>
Continue
as shown in fig. 2
@
Yes
I–13
I
———
———
>
— — — ———
(C/O
———
—.——
A–1
<
or other
A–10
>
———
———
31Ll
— ,
— — — — — — — ———
d
‘A’ signal
as shown in fig. 2
(enhanced
routing–information
ready)
<
+.-——
PAB’; (0)
enhanced
?
I–N
NO
Continue
1–13
———
I
I___
(next digit)
-----+
? Yes
as shown in fiq. 2
(C/O
to enhanced
..——
———
———
—..—
._ —_.
———
——..
ANNEX
———
———
A–1
‘+----
–1
(send next signal)
Continue
c+
———
I
ANNEX
— — — — — — — —. — —
I
l——_—_—
I
to EEC)
———
routing)
—.——
.——
———
——.—
———)
———
3———
(send next signal)
or other
Continue
Figure 3 (T/CS 49-08).
-J
‘A’ signal
as shown in fig. 2
Enhanced
routing procedure.
-1
T/CS 49-08 E
Page 7
PABX
PABX(0)
i
(T)
Seize (line signal)
Proceed
to send (line signal)
<
I–N
digit)
Note: all
digits have
been received.
\
/
.
\
(routing
A–1
I–N
(routing
(send next siqnal)
digit)
or 1–15
(no further
digits)
>
A–6
(address complete-no
—
set up speech path)
<—----
End of MFC
A–7
MFC
——.
working
(address complete--request
Yes
user identity)
Q“
No
o .,
/
<
<
Has
ABX(0)
user
subsystem
~
I–N
(diqit representing
A–7
(C/O
user identity)
,
\
No\
Yes
to user subsystem)
/
<
Enter user subsystem
1–12
(user reauest
not acceoted)
\
/
\
+
6’
, Y es
\
A–1
/’
\
Yes
1 (address complete–enhanced
C/O to group n/B
<
working)
PABX
have
enhanced
ubsystem
7
LNo
No
\ /
--+
i l–l
2 (enhanced
system request not accepted)
\
>
A–3
<
(address complete–basic–
+------]
C/O to group I l/B working
ill–9
(limited
list of call class info)
)
B1–10
(limited
list of SOT)
<
End of MFC
“o
To
Figure 4 (T/CS 49-08).
fig. 5
Edition of September 15, 1986
working
Compatibility
check procedure.
TICS 49-08 E
Page 8
2.5.1.
Basic subset
The basic subset provides a single signal interchange
can be sent.
in which one of the following pieces of information
Forward information:
Call originates
from
— an ordinary
extension;
—
—
—
—
—
—
—
a restricted signaling capability private circuit;
maintenance equipment;
the public switched telephone network (PSTN);
an operator position;
data transmission equipment;
an operator assisting an ordinary extension;
an operator assisting a PSTN caller;
-— an operator
assisting a restricted
signaling
capability
private circuit.
Backward information:
The destination is
—
—
—
—
—
in a parked state;
barred PSTN calls;
busy with intrudable status;
temporarily out-of-service, unallocated
free with intrudable status;
number;
— barred to incoming calls;
— busy with non-intrudable
status.
In addition there are signals to indicate:
— destination PABX congestion;
— destination
PABX call failure.
The exchange of additional
2.5.2.
2.5.2.1.
information
using basic is shown as the last two signals in Figure 4 (T/CS 49-08).
Enhanced subset
Exchange of calling and called party information
In enhanced working, the exchange of calling and called party information is by means of two signal
interchanges. The first signal interchange (groups II and B) conveys the following pieces of information,
in addition to the items listed in Paragraph 2.5.1.
Forward direction:
Call originates from
— the network;
— an ordinary extension holding a PSTN call;
— an executive extension;
— the ISDN.
Backward direction:
The destination
is
— an operator position;
— busy with partially-intrudable
status;
— free with partially-intrudable
status;
— in a state with no applicable state of destination.
The second signal interchange (groups III and C) enables further qualifying information to be exchanged,
such as whether the call has been diverted; whether or not it may be partially intruded upon; whether the
called party is barred access to the PSTN; and whether further MFC signaling is required by either PABX,
e.g. supplementary service control information, or calling line identity.
The exchange of additional information using enhanced is shown in Figure 5 (T/CS 49-08) in arrow chart
form.
2.5.2.2.
Simple call
Following the exchange of additional information,
and assuming that no supplementary
services are
required, the MFC registers release and leave the connection under the control of line signals.
Edition of September 15, 1986
TJCS 49-08 E
Page 9
I
PABX(0)
A–1
1 (address complete–enhanced–
<
w,
C/O to groups 11/6)
111–15
(enhanced
MFC
list of call class info)
B1–15 (enhanced
&
>
II–12)
(excluding
MFC
list of SOT
info)
Is
working
in groups
IVID reqd
No
1111–4
(simple)
\
>
I
7
-0
Is
Yes
<
Cl–4
(conclude
MFC
Clear MFC
No
signaling)
registers
working
in groups
IV/D re~d
?
Yes
/
Supplementary
service
.—
—
—.
——
u
/-
—
Manufacturer
supplementary
To
fig. 6
Figure 5 (T/CS 49-08).
Edition of September 15, 1986
——
——
——
—
subsystem or CL I
service required.
Exchange
of SOT/COS
—
(5
CLI
fj”8
information
(enhanced
MFC subsystem).
TICS 49-08 E
Page 10
2.5.2.3.
Supplementary services
In addition to establishing a call, System L1 MFC erzlwuzcedsignaling procedures are specified to provide
access to supplementary services during the exchange of additional information before the MFC registers
release. The supplementary service category concerned will be determined by a supplementary service request
procedure.
Forward supplementary
service request
When the originating PABX requires a supplementary service, it indicates this with a group III signal (III-5
to III-12). Upon recognition of this signal, the destination PABX responds with the request-forward-supplementary-service-category
signal (C- 15). This provokes change-over-to-group-IV-and-D
signals, which are
used for two compelled MFC cycles dedicated to the category and supplementary
service identification.
Backward supplementary services request
The destination PABX changes-over to group IV and D signals by transmission of one of the signals C-7
to C-14. The response on C-7, C-8, C-10 and C-13 shall be the signal IV-15, requesting the backward
supplementary service category and identity. As in forward supplementary service request, two cycles are
used. The signals C-9, C-11, C-12 and C-14 initiate the sending of the calling-line-identity,
see Paragraph 2.5.2.4.
The above arrangements allow transmission of at least 15x 15 codes in both directions. By using code 10
as an escape, extension is possible. Further study is required on the allocation of the codes to identify
category groups and specific supplementary services.
Forward supplementary service requests are given priority over backward requests and, depending upon
the capability of the PABXS concerned, any number of requests can be processed sequentially until neither
PABX has an outstanding requirement for further MFC signaling (see revert on Figure 1 (T/CS 49-08) and
Paragraph 2.5.2.8.).
Signal flows for forward and backward supplementary service requests are shown in Figure 6 (T/CS 49-08)
and 7 (T/CS 49-08) respectively.
Supplementary service requests can also occur after the release of MFC registers, either before or after
answer (see Paragraph 2.5.2.5.).
Signaling procedures specifications for non-harmonised
supplementary services in national use or defined
by a manufacturer, are not shown in this Recommendation.
The relevant documentation should be provided
by the Administration
or manufacturer concerned.
2.5.2.4.
Calling-line-identity
Calling-line-identity
(CLI) requests occur normally as a part of the call establishment
of one of the following backward signals:
Send-CLI (Signal C-9);
Send-CLI, PSTN-barred (Signal C-1 1);
Send-CLI, non-intrusion-request-rejected
(Signal C-12);
Send-CLI, PSTN-barred, non-intrusion-request-rejected
(Signal C- 14).
procedure
by means
Since the calling-line-identity
request is liable to occur on a large number of calls, the necessary signals are
included in the main MFC signaling procedures, and are not included in an Annex like other supplementary
services. This reduces the number of signals required and, consequently, shortens the post-dialling delay.
On completion of the calling-line-identity
request, the responding PABX, dependent upon its capability,
either concludes MFC signaling, or retains its MFC registers to offer a subsequent supplementary service
(see Paragraph 2.5.2.9.). Signal flows for calling-line-identity
request are shown in Figure 8 (T/CS 49-08).
2.5.2.5.
Supplementary services after register release
Where a supplementary service is required after the MFC registers have released, a register-recall signal will
be used. Following a register-recall signal, both PABXS will automatically commence signaling in groups
IV and D. The PABX that sends the register-recall signal will be considered the initiating PABX in terms
of MFC, and will commence the signaling procedure by sending a group IV signal.
2.5.2.6.
Signaling within supplementary services
The subsequent signaling flows within a supplementary service depend upon which supplementary service
is requested. Details will be given in the relevant Annex to this specification as they are agreed upon.
2.5.2.7.
Rejection of supplementary service requests
Where a PABX cannot provide the service that has been requested, it shall return a request-no-accepted
signal and, depending upon its capability, either concludes MFC signaling, or retains the MFC register
to give an opportunity for an alternative service to be requested (see Paragraph 2.5.2.9.).
Edition of September 15, 1986
TfCS 49-08 E
Page 11
,
P~BX(0)
oo
L
I
From
1
fig.
5
!
9
Further
group lV/D
signall;ng
?
/\
/’
A
\
Is
\
/working \
(\;;
/;;:d
\
,)
?/
/
\,
1115-8/11/12 (supplementaryservice)
>
Yes
Yes
L
Cl–4 (concludeMFC signaling)
ClearMFC
reg!sters
,C-15 (requestfoward service
cate90rY)
\
z)
No
Has
PABX(T)
any supp svc
potential
?
+-----J
(C/O to groups lV/D working)
‘es
cate90ry digit
IV1-15 (forwardservice
‘Register
recall
entry
intosupp services.
and/or service identitydigit(a))
*
Note:
When the recall returns to 111/C signaling,
only signals III–5 or 111–13 and Cl or
C–1 3 will be used.
-0
Is
1
/
/
D–14
(requestnot accepted}
(CIO to group ill/Cworking)
No
supP wce
valid
?
1
———
--—
—-—
—-—
--—
Processforward supplementaryservice
—-—
———
———
———
———
——
D–13 (OK) (C/O to group IIIICworking}
D-14 (requestnot accepted)
<
(C/O to group IIIICworking}
III-13 (no furtherMFC
si9nallinQ) \
cl-4 (concludeMFC signallingl
<
Set up speechpath
Figure 6 (T/CS 49-08).
Edition of September 15, 1986
Forward
supplementary
service request.
-——
OK _
J
/
\
———
,
Fail
—-—
~
TICS
49-08 E
Page 12
1
,
PABX(T)
PABX(0)
1
1
1
J
I
0
From
fig. 6
I
I
A
/
C6, 8, 10 or 13 (backward
/
Supp
svce
supp svce request)
\
<
\
\
IV–14
(request
not accepted–further
MFC signaling
supp’\
svce
/’
C“:l
7/
1“/
\/
v
‘#n
/
I
.-
>
possible)
/
Yes
D–14
<
rJ
I
>
/
(C/O
IV–1
(backward
<
and/or
>
D–14
———
Fail
service category)
— —.—
service category
service
(request
further
<
———
II I/C working)
backward
>
D1–10
Yes
l–
! OK
acknowledged)
to group
5 (request
[V–14
No
(reject
——.
to group
——
IV–14
D–14
<
acknowledged)
hi/C
working)
(rejection
(OK further
_--__--,
service
———
———
———
not accepted–
signaling
(C/O to group
IV–13
>
‘+--------
(request
MFC
digit(s))
possible)
Process backward supplementary
———
———
——.
—.—
further
digit
not accepteci–
MFC
(rejection
(C/O
identity
>
possible)
acknowledged)
ill/C
MFC
working)
signaling
possible)
>
D–13
<
(acceptance
(C/O
Figure 7 (T/CS 49-08).
to group
Backward
acknowledged)
ill/C
working)
supplementary
service request.
I
———
I
!
/0
1
-,
\
49-08 E
TfCS
Page 13
PABX(T)
o
From
fig. 6
,i,
C9,
11 or 14 (request
CLI
CLI)
i
z
/’suPP’\
svce
++,
Supp
‘<:>
,
:[,
I
\~/
\
/
\/’
v
I
i
I
I
IV1–10,
11 ~ 14 (digit signal)
>
D–15
(send next signal)
<
—
I
I
:
e<
fi~. 6
IV–15
D–13
(end
(OK–C/O
of diaits)
to group
ill/C
working)
Figure 8 (T/CS 49-08).
Edition of September 15, 1986
/
.
Calling line identity request (CLI).
T/CS 49-08 E
Page 14
2.5.2.8.
Sequential processing of supplementary service requests
During a call it is possible, although improbable, that more than one service demand will need to be
processed at a given time. Examples of this are listed below.
i)
Clash of supplementary services: an incoming call has diversion-override capability and the called party
has diversion activated.
ii) Second attempt: a supplementary service or calling line identification is required, following an unsuccessful attempt to change-over to manufacturer.
iii) Enhancement of a supplementary service: following a supplementary service request, the PABX wants
to change-over to manufacturer for a specific enhancement.
To enable a number of supplementary service requests to be processed sequentially, the following signals
arc included in groups IV and D:
D-13
OK/acceptance-acknowledged,
change-over-to-groups-III-and-C
D-14
Request-not-accepted/rejection-acknowledged,
change-over-to-groups-III-and-C
IV-1 3
OK, further-MFC-signalling-possible
IV- 14
Request-not-accepted,
further-MFC-signalling-possible
These signals, which may be used either on completion of a supplementary service or on rejection of a service
request, return the signaling to groups III and C allocations, thus enabling the PABXS to either request
a further service or conclude MFC signaling. On each return to groups III and C signaling, the originating
PABX has priority. When the originating PABX has no further requests to make, it sends a no-furthersupplementary -service-request signal (III- 15). The responding PABX, on receipt of this signal, either sends
a supplementary service request or concludes MFC signaling by sending a conclude-MFC-signalling
signal
c-1.
Manufacturer
2.5.3.
subset
When the subset compatibility check has identified a common manufacturer subset, call handling continues
in accordance with the appropriate specifications. However, once manufacturer subset procedures have been
entered, it is still possible to revert back to standard System L 1 MFC working.
The signaling procedures within manufacturer subsets are not given in this Recommendation,
relevant documentation
should be provided by the manufacturer concerned.
and the
REFERENCES
[1]
[2]
[3]
[4]
[5]
[6]
[7]
Recommendation
Recommendation
change lines.
Recommendation
T/CS 49-07. System L1 multlfrequency
TICS 49-01. System LI line signaling
T/CS 41-01. Signal and signaling
code interregister signaling.
over international inter private automatic
branch ex-
message names and meanings.
Sub-Working Group CS-IJ3A. System L1 MFC signal descriptions and functions (under study).
Recommendation
Z. 101. General explanation of the specification and description language (SDL).
Recommendation
Z. 102. Symbols and rules.
Recommendation
Z. 104. Semantics.
SDL-DIAGRAMS
Page
Figure
. . . . . . . . . . . . . . . . . . . . .
16
. . . . . . . . . . . . . . . . . . . . . . . . . . .
17
Functional
block description
10
Originating
PABX circuit seizure..
11
Originating
Originating
Originating
Originating
Originating
Functional
Terminating
PABX routing . . . . . . . . . . . . . . . .
PABX compatibility procedure
. . .
. . .
PABX clear-down sequence (basic subset)
. . .
PABX SOT/COS procedure (basic subset)
. . .
PABX answer and conversation (basic subset) . .
block description of terminating and transit PABX
PABX circuit seizure
. . . . . . . .
9
12
13
14
15
16
17
18
19
20
21
22
of originating
PABX
Terminating PABX routing including enhanced routing
. .
Transit PABX routing including enhanced routing
. .
Terminating PABX compatibility procedure
. . . . . . .
Terminating PABX clear-down sequence (basic subset)
. .
Transit PABXcircuit
seizure (O/G).
.
. . . . . .
.
.
.
.
. . . . . . .
. . . . . . .
. . . . . . .
. . .
. . . . . . .
. . . . .
. . . . .
. . .
. . .
. . .
.
. . .
. . .
. . .
.
.
.
.
.
.
.
.
.
. . . .
.
.
. . . .
. . . .
. . .
.
.
.
.
.
.
.
.
.
. . . . .
. . .
.
. . . . .
. . . . .
. . . . .
.
. .
. . . .
.
. .
. . . .
. . .
. . .
.
.
.
.
.
.
.
. . . .
. .
.
. . . .
.
. .
. . .
18
19
20
21
22
23
24
25
26
27
28
29
Edition of September 15, 1986
T/CS 49-08 E
Page 15
Page
Figure
23
Terminating
.
30
24
25
26
27
28
29
Terminating PABX answer and conversation (basic MFC subset)
. . . . . . . . . . . .
Action onreceipt ofunallocated
signal . . . . . . . . . . . . . . . . . . . . . . . . . .
31
Originating
Originating
Originating
Originating
PA13X
PABX
PABX
PABX
33
30
31
Originating
Originating
PABX supplementary
PABX supplementary
32
Originating
PABX SOT/COS procedure
33
Originating
PABX answer and conversation
34
Originating
PABX cleardown
35
procedure
(basic MFC subset)
SOT/COS procedure (part 1)
SOT/COS procedure (part 2)
SOT/COS procedure (part 2)
supplementary service request
. . . . . . . . .
(en/zanced MFC subset)
. . . . . . . . .
.
(enhanced MFC subset)
.
. . . . . . .
(enhanced MFC subset)
. . . . . . . . . . .
procedure (enhanced MFC subset)
. . .
service request procedure
service request procedure
(enhanced MFC subset)
(enhanced MFC subset)
.
. .
. . . . . .
(part 2) + calling line identity (CLI) (enhanced MFC subset)
(enhanced MFC subset)
sequence (enhanced MFC subset)
. .
. . .
. . . . . . .
37
38
40
41
Terminating
. . . . . .
47
41
48
42
Terminating PABX SOT/COS procedure (part 2) + calling line identity (CLI) (enhanced MFC
subset)
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Terminating PABX answer and conversation (enhanced MFC subset) . . . . . . . .
. . . .
43
Terminating
. . . . . . . . . . . . . . .
50
44
Cleardown or register recall during conversation (terminating PABX enhanced MFC subset) . . .
Notexand
Note y........
. . . . . . . . . . . . . . . . . . . . . . . . . . .
Action of a transit PABX on receipt of a recall signal during conversation
.
. . . . . .
51
45
46
Edition of September 15, 1986
PABX supplementary
PABX cleardown
service request procedure
(enhanced MFC subset)
sequence (enhanced MFC subset)
.
.
.
.
.
36
39
38
.
.
.
.
.
.
.
.
.
35
39
. . . . . . . . . .
MFC subset)
.
. . . .
. . . . . .
. . . . . .
subset) . .
34
40
37
PABX enhanced
MFC subset) .
MFC subset) .
MFC subset)
(enhanced MFC
32
Cleardown or register recal during conversation (originating
Terminating PABX SOT/COS procedure (part 1) (enhanced
Terminating PABX SOT/COS procedure (part 2) (enhanced
Terminating PABX SOT/COS procedure (part 2) (enhanced
Terminating PABX supplementary service request procedure
36
n
PABX SOT/COS
.
.
.
.
.
42
43
44
45
46
49
52
53
TICS
49-08 E
Page 16
z
Outgoing
seiZure
Pre-PTS
Walt
Proceed
tosmd
n
RoutIng
Flg10,11
cOmpaaJl Ity
Fig11,12
Enhanced
WC
subset
fbslc
tf[
subset
1
mFlg1415
Amwa”
SOT/COS
(basic)
Flg 12.26
[
Post
register
releesd
Pre
reglstw
relme
Canvw-sat
Im
(basic)
8
n)’:
Mpplmantaiy
sw Ice
[
5
c1
Col-wrsetIm
Fig28,29,
31,3233
[
Register
red I
Figure 9 (T/CS 49-08).
Functional
block description
of originating
PABX.
Edition of September 15, 1986
TICS
49-08 E
Page 17
#--
Sdzlq
I
Pmomd
to Wld
Ualtlng
to ScYKl
n
clm-
fmua-d
fst
o
A
clea-
-
Edition of September 15, 1986
Idle
Fig11
Figure 10 (T/CS 49-08).
proceed
tosalxl
fuwa-d
dlglt
8
tb-1melpt of
8
Originating
PABX circuit seizure.
T/CS 49-08 E
Page 18
Flg10
?
Z=ll
fwt
dlglt
1
Fig11
%
flint
dlglt
(11-10)
med
Frimced
rwt kg Infw-
IKLltlligno
=
~7matlcnl
@
Infmnatlon
(A-i2)
(A-1OI
1
w
Yes
E
send
No
1
Fig1
%-cl C/o
T
to Kilald
no fwtimdlglts
k
Flg13
N
Walt
I
a
TM
Inwy\@Qua
/3
Flg11
muting
dl
I
P
I
o
3
3
I
Flg11
km
39%tIbIIIty
F!!!!5Z
C;*
“’
D
Raqwst
mt ampkd
[1-121
Digit
(11-10)
Wo
to
mutlrg
yls#y
EfAwlad
&
To relavant
sad
ralwant
c$xQ;
88
6WJIII
Slg!at
(11-10)
smd
-f
rotacc@d
-t
not~ted
(II-12
u-1-121
Figure 11 (T/CS 49-08).
‘nFlgll
J)gl
Originating
PABX routing,
Edition of September 15, 1986
TICS
49-08 E
Page 19
9
c
tbnufactm
slllsQt
W&t
Basic
PABX
(A-3)
‘~
a
a
easlc
M=c
VOrklng
D
Flg14
Flg11
Adhss mm
p[etesetup
~L6~th
Note
ErAmwed
(A:h)
~
Q
4
Fig12
Flg12
Walt
%
23
w“
2
1
Fig12
C(=
andSwitch
ttaw.gh
Walt
I
G
WC
working
Fig26
se-d1st
msnuf
d urw
sbbset
dl It
Smd
msnuf
acturw
S.&et
dl It
Ww
1
a
next
Slg!al
J
@nd 2nd
Sutnet
dlglt
(A-1
)
.2q-6
(5 (?)
4
J
.
/’--=
AvaIt
cm@lbl[lty
response
w
Flg12
Fig14
Fig12
r
Fig12
)
3
Inomfmtable
subset
s
C/oto
mnufacturer
subset
Uccklng
(A-7)
L
I
Bmlc
:.
Fig14
‘O’eT
I
Subset
mqus.$t
(A-7)
Fig14
F(912
Fig12
ktd-essmm-
tfmfactwer
PABX
(A-3)
T
Fig12
L
Note
s~L6ath
Flg12
Flg 12
Note We
PSTNis
WccLUItWed
theTIWISI
t
gmated ANSWERslgrral
mayrG@ce signal
A-6
Figure 12 (T/CS 49-08).
Edition of September 15, 1986
Originating
PABX compatibility
procedure.
TICS 49-08
Page 20
E
N
&
Flg11,1$
[lea)’FC
rqlstsr
clew-d
Idle
8
Figure 13 (T/CS 49-08).
Originating
PABX cleardown
sequence (basic subsystem).
Edition of September 15, 1986
)
)
(!3
D
Fig12
Wait
I
S%-d
cdinary
sxtmaim
I
Smd
~lvatecct
r+r. slg.
W@lllty
I
Smd
am[ntwmce
Gq@lmt
I
Smd
tWN
I
I
Smd
opa’ator
I
Wd
&ta
trmwlsslm
I
Smd
cpwatcc
asslstlng
PSTN
I
%d
c$l.
asslstirg
restr.SIg.
G@l[ity
I
lkllnary
estmslm
(IT
-1)
I
1
Pad
(e-1
)
I
Private
cd
restrlctad
Sig
~!:;ty
I
K4ntename
ecp;~t
I
PSTN
(n-4)
I
Oata
tmnmisslm
(U-6)
OpAy
I
J.
I
w
OpEs-atw
assistirg
dl-
tpmatcr
asslstlng
PSTN
(n-B)
I
op.Ssslsting
rsstrlcted
slg
Gll#;;ty
I
I
I
Callfailed
twred P5TN
calls
(B-2)
I
T!us&
Intmdable
(e-3)
I
Talna[
PAox
callfal[ure
(B-4)
I
Callfailed
Iccmlng
callba-rd
(B-8)
WISI
Iccated
rmkel=
(L:]
1
I
Tmnlnal
PABX
congest
im
(B-9)
1
lntrdatde
(B-lo)
I
Fig13
6
E
Flg15
T/CS 49-08
Page 22
E
tf[
a
E
Flg1214
?
clea-
rQglstO-
+
Aval
t
mmslg7a(
t
Extmslm ka not
answar-cal
(Iq
Amvar
@XtEilSIM
I
C(WS
I
FE)E>
a
Releaw
guord
Cleared
Idle
8
Figure 15 (T/CS 49-08).
Originating
PABX answer and conversation
(basic subsystem).
Edition of September 15, 1986
z
Idle
Selzl.m
Fig17
TfCS 49-08 E
Page 23
=4
Tramlt
PABX
O@31rg
5QIZU-Q
Fig19,22
I
Pre-PTs
wait
PmEed
toSmd
Prcceal
to Smd
[[ear reglstsr
andWI tchtfrwjl
:
Cmversat
Im
E!E1--F”
Erkmed
Kc
.uibSet
easlc
tFc
WbsQt
SOT/COS
(baslc)
Fig20,23
s
PostSOT/CU3
Walt
(beslc)
t!arMlfactlJWsUtWt
Flg20
Fig20,23,24
F7---lg202
(!%%
/----=
Cmversat
ion
(bale)
I
I
t
I
Supp&l;:iry
I
c1+
Fig30,39,
40,41,42
Cmvel-sat
IM
I
Figure
Edition of September 15, 1986
16
(T/CS 49-08).
Functional
block description
of terminating
1
I
and transit PABX
T/CS 49-08 E
Page 24
Idle
sQlzlfg
Walt
~s
8
tfc
clea-
reglst-
fa%wd
available
Proceed
to smd
BB
cat[ rmtestablIstnti
Idle
Flg18,19
Figure 17 (T/CS 49-08).
Terminating
PABX circuit seizure.
Edition of September 15, 1986
TICS 49-08 E
Page 25
9
M
Flg17
a
Await
first
digit
C3
Ualt
I
I
I
SW red
digit
(A-1)
1
I
Rautlrg
cmgd Im
(A-9)
I
J
J
Aual
t
gwplI
Slglal
I
I
I
GW@fl
(i’%
a
3
Smddmcd
$.2(KI
d-w-red
NOJtlrg
I-cutIng
info-mat
lm
c1
Infa% Im
~w
c1
Ed?a-iced
GA-la-dra!tlng
Info=
matlm ma@
(A-lo)
/-’--
Ccu@tlblllty
routing
m Infamatim
[A-12)
+
Aualt
mst
signal
I
Rsqwst
mt accsptwl
(1-12)
L
I
1
Dlglts
1-0
(11-10)
L
No furtflw
d~~i
i
C/otoS#lsnmd
rwt Irg
W@::y
I
To relevmt
WUlex
L
Figure 18 (T/CS 49-08).
r’-
Edition of September 15, 1986
Terminating
PABX routing including
enhanced
routing.
cc
Fig20
T/CS 49-08
Page 26
E
0s
Fig17
6
Awlt
first
dlglt
Digit
1-0
(11-10)
(3
Ualt
I
I
SW!d
sendmxt
digit
SW PSTN
Wxsmtsrd
se-dmxt
digit
I
I
Smd
ruutlrg
call
fal(u-a
I
7
Sam!
muting
CmgestIon <
h
I
Smd
smd CS(IIIW
party
catsgcy
I
L
L
Sufficlsfd
digits
be bsm mQiVad
tosf!able
Wtgoll-g
Ilm $QIzl.vw
ti
JJ
Fig16,22
a
Uz$z@i=t’b’””
seed
Srha-md
muting
Infmnatlm
W
c1
<nl
mc~
Enhanced
rwtlnglnfcrmt~f,\e@
ruutlng
m infamatlcm
(A-12)
+
Await
next
Sig!al
I
I
Raquast
notacc~tad
L
Dlglts
1-0
(11-10)
L
No fu%ladlglts
(1-15)
:
Ta
C/otoWard
rwt kg
SUyd)m
To mievtnt
@Figure 19 (T/CS 49-08).
Transit PABX routing including
enhanced
routing,
Edition of September 15, 1986
TJCS 49-08 E
Page 27
Q
cc
Fig19
P
Malwfactwsl=
Wbaet
t
LYC
PABX
1
c
qFlg20
PABX
[A-31
;
Basic
wci-i(
ing
00
C c’
Mmufacturer
subset
rgst
(A-7)
E?slc
Flg23
@
Ad@as
mnpleteset
Up SW, path
m
a Z$EI 6--I
Enhanced
M=c
workIng
66
Fig36
(/0
k
to
w
l/Aworking
L&r
0
Digit
mmpatlbi(lty
?
No
Yes
Send
2mlsubsetdigit
(A-1
)
AvaIt
next
slgna(
we mere Pm is
efmuntmd thetramIt
gwa-atedANSWR slgm(
maymp[aceSig!a[
A-6
(
I
Smd
basic
Wait
)
I
Smd
w
mmlfacturw
subset
reqmst
PABX
I
adck=ess
CCIT@QtQ
Nate
sQtup
S*
path
I
Sad
mharmd
WC
I
Fig20
cm to
Wmufactum
sdmef~;~ Ing
c1
a
a
a
Address
cc@ete set
Up Sp(~) path
Basic
PABX
(A-31
00
clearraglst.a-
Basic
andSWi tch
through
vcrking
@
Fig23
Figure 20 (T/CS 49-08).
Edition of September 15, 1986
Terminating
PABX compatibility
procedure.
T/CS 49-08 E
Page 28
o
Fig18,19,23
a
?
clear
f’Fc
register
C[ea-
E
faward
[1eared
Idle
Figure 21 (T/CS 49-08).
Terminating
PABX cleardown
sequence (basic subsystem).
Edition of September 15, 1986
T/CS 49-08 E
Page 29
JJ
Fig19
?
E
Smd
SQlzwe
O:tp::
Pre
PTs
wait
n
Pracaed
toad
1
a
Smd
dlglt
I
I
I
D
Dlglt
(11-10)
I
*
Aual
t
rnxtsignal
I
Smd
rwxtdlglt
(A-1
)
clear l-l star
Oncc@etlm of
conpe~ld qcle
w Itchttrough
8
R
Figure 22 (T/CS 49-08).
Edition of September 15, 1986
1
Cmvarsat
IM
Transit PABX circuit seizure (0/G).
I
m
m
Fig20
(3
Awlt
next
Siglal
I
1
&cWlary
extmslm
(1-11
I
I
private
cd
restr.
Slg
ca@W;ty
I
I
I+3intmaxs
~;~t
I
I
(
I
3a-Ki
pinked
I
%d
falId
W
P3TN
calls
I
send
h
intmcbble
I
I
J.
I
wait
I
I
%ml cali
failed1/[
Cal(
SGml
u-dIaatd
rlmk=
T03
I
,.
0W
CA
“.
Ca(lfalkd
W
P3TN
cd [S
(e-2)
I
w
Intrcc!atde
(a-31
1
Twn)lnal
PABXcdl
fallu=e
(e-k]
Lha[ICcatad
rmlber(L?)
Q
m
n
~
I
OpaTator
assisting
PSTN
[n-81
I
I
OpAlrsl
;t$g
cca!p;~l:
Itq
I
I
%-d
terminal
PABX
cmgestIm
I
Termlnd
PABX
Kslg2st
Im
(6-91
I
Smd
Intrw!able
I
Intru%ble
(e-lo)
I
1
6
I
)
I
w
Iermlna[
PABXCal(
fal(u-e
I
Data
trmdsslm
(1-6)
y_;r
P3TN
(II
-61
Fig21
8’8
fre2lntrulJ?ble
F=
Intrwkble
(8-6)
fmQ—r?m
Intrudable
F—
Intruiable
(57)
c)
EE
Flg24