ETSI EN 301 140-3-2 V1.1.3 (2000-05)

SLOVENSKI STANDARD
SIST EN 301 140-3-2:2001
01-september-2001
Inteligentno omrežje (IN) - Aplikacijski del inteligentnega omrežja (INAP) - Nabor
zmožnosti 2 (CS2) - 3. del: Zgradba preskušalnega niza in namen preskušanja
(TSS&TP) - Specifikacija za funkcijo preklapljanja storitev (SSF) - 2. podpoglavje:
Obdelava stranke v klicu (CPH)
Intelligent Network (IN); Intelligent Network Application Protocol (INAP); Capability Set 2
(CS2); Part 3: Test Suite Structure and Test Purposes (TSS&TP) specification for
Service Switching Function (SSF); Sub-part 2: Call Party Handling (CPH)
Ta slovenski standard je istoveten z: EN 301 140-3-2 Version 1.1.3
ICS:
33.040.35 Telefonska omrežja Telephone networks
SIST EN 301 140-3-2:2001 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------

SIST EN 301 140-3-2:2001

---------------------- Page: 2 ----------------------

SIST EN 301 140-3-2:2001
ETSI EN 301 140-3-2 V1.1.3 (2000-05)
European Standard (Telecommunications series)
Intelligent Network (IN);
Intelligent Network Application Protocol (INAP);
Capability Set 2 (CS2);
Part 3: Test Suite Structure and Test Purposes (TSS&TP)
specification for Service Switching Function (SSF);
Sub-part 2: Call Party Handling (CPH)

---------------------- Page: 3 ----------------------

SIST EN 301 140-3-2:2001
2 ETSI EN 301 140-3-2 V1.1.3 (2000-05)
Reference
DEN/SPS-03038-3-2
Keywords
IN, CS2, INAP, TSS&TP, SSF
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.:+33492944200 Fax:+33493654716
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network
drive within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at http://www.etsi.org/tb/status/
If you find errors in the present document, send your comment to:
editor@etsi.fr
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 2000.
All rights reserved.
ETSI

---------------------- Page: 4 ----------------------

SIST EN 301 140-3-2:2001
3 ETSI EN 301 140-3-2 V1.1.3 (2000-05)
Contents
Intellectual Property Rights.5
Foreword .5
1 Scope.6
2 References.6
3 Definitions and abbreviations .6
3.1 Definitions.6
3.2 Abbreviations .6
4 Void.7
5 Void.7
6 Void.7
7 TSS and TP for CPH functions.7
7.0 Introduction .7
7.1 Preambles and postambles for CPH .7
7.1.1 Names of preambles and postambles .7
7.1.2 Preamble trees.9
7.1.3 TTCN-like notation for preamble description.10
7.1.4 Representation of preamble/postamble and test purposes using MSCs .10
7.1.5 How to interpret the parameters and their values as used in the MSCs.10
7.1.6 Preamble descriptions.11
7.1.6.1 O (originating) preamble tree .11
7.1.6.2 T (terminating) preamble tree.29
7.1.6.3 I (InitiateCallAttempt) preamble tree .37
7.1.6.4 Event Detecting/Report rules Preambles.43
7.1.7 Postamble descriptions .59
7.1.7.1 Postamble ReleaseAll_1.59
7.1.7.2 Postamble ReleaseAll_2.60
7.1.7.3 Postamble ReleaseAll_3.61
7.1.7.4 Postamble ReleaseAll_4.62
7.1.7.5 Postamble ReleaseAll_5.63
7.1.7.6 Postamble ReleaseAll_6.64
7.1.7.7 Postamble ReleaseAll_7.65
7.1.7.8 Postamble ReleaseAll_8.66
7.2 CPH procedures.66
7.2.1 List of procedures for CPH.66
7.2.2 Definitions of the CPH procedures .67
7.2.2.1 mergeCallSegments procedure.67
7.2.2.2 releaseCall procedure.67
7.2.2.3 continueWithArgument procedure .67
7.2.2.4 disconnectLeg procedure.67
7.2.2.5 moveLeg procedure.67
7.2.2.6 splitLeg procedure.67
7.2.2.7 continueWithArgument procedure .67
7.3 Structure of the test suite (TSS) for CPH .67
7.4 Test Purpose (TP) descriptions for the test of CPH procedures .68
7.4.1 MergeCallSegment procedure (MC).69
7.4.2 MoveCallSegment procedure (MCS).74
7.4.3 ReleaseCall (CS2 complement) procedure (RC) .75
7.4.4 DisconnectLeg Procedure (DL) .78
7.4.5 MoveLeg Procedure (ML).83
7.4.6 RequestReportBCSMEvent Procedure (CS2 additions) (RR) .89
7.4.7 SplitLeg Procedure (SL) .92
7.4.8 Continue with argument Procedure (CW).95
ETSI

---------------------- Page: 5 ----------------------

SIST EN 301 140-3-2:2001
4 ETSI EN 301 140-3-2 V1.1.3 (2000-05)
7.5 Test Purpose (TP) descriptions for the test of call handling capabilities.102
7.5.1 originating (O_BCSM) trigger (controlling legId = 1) .102
7.5.2 Terminating (T_BCSM) trigger (controlling legId = 2).174
7.5.3 Network initiated .197
7.6 Test Purpose (TP) descriptions for testing arming/detecting rules .208
7.6.1 Originating (O) trigger.209
7.6.1.1 O_1 Events coming from the controlling leg (legId=1) .209
7.6.1.2 O_2 Events coming from passive legs (legId= 2,3.) .219
7.6.2 Terminating (T) trigger.238
7.6.2.1 T_1 Events coming from the controlling leg (legId=2),.238
7.6.2.2 T_2 Events coming from passive legs (legId= 2,3.).245
Annex A (normative): Preamble trees .263
Annex B (normative): TCAP Parameter values .266
Annex C (normative): Core INAP Parameter values .267
History.269
ETSI

---------------------- Page: 6 ----------------------

SIST EN 301 140-3-2:2001
5 ETSI EN 301 140-3-2 V1.1.3 (2000-05)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect
of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server
(http://www.etsi.org/ipr).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in SR 000 314 (or the updates on the ETSI Web server)
which are, or may be, or may become, essential to the present document.
Foreword
This European Standard (Telecommunications series) has been produced by ETSI Technical Committee Services and
Protocols for Advanced Networks (SPAN).
The present document is part 3, sub-part 2 of a multi-part EN covering the Intelligent Network Application Protocol
(INAP) capability set 2, as identified below:
Part 1: "Protocol specification";
Part 2: "Protocol Implementation Conformance Statement (PICS) proforma specification";
Part 3: "Test Suite Structure and Test Purposes (TSS&TP) specification for Service Switching Function
(SSF)";
Sub-part 1: "Basic capability set of CS-1 including CS-2 complements";
Sub-part 2: "Call Party Handling (CPH)";
Sub-part 3: "Specialized Resource Functions (SRF)";
Part 4: "Abstract Test Suite (ATS) specification and Partial Protocol Implementation eXtra Information for
Testing (PIXIT) proforma for Service Switching Function (SSF)";
Part 5: "Distributed Functional Plane (DFP) [ITU-T Recommendation Q.1224 [2] (1997) modified]".
National transposition dates
Date of adoption of this EN: 28 April 2000
Date of latest announcement of this EN (doa): 31 July 2000
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 31 January 2001
Date of withdrawal of any conflicting National Standard (dow): 31 January 2001
ETSI

---------------------- Page: 7 ----------------------

SIST EN 301 140-3-2:2001
6 ETSI EN 301 140-3-2 V1.1.3 (2000-05)
1 Scope
The present document contains the Test Suite Structure and Test Purposes (TSS&TP) for Call Party Handling (CPH),
part of CoreINAP CS2. It complements the initial document EN 301 140-3-1 [1] dedicated to general introduction and
TSS&TPs for CoreINAP CS1.
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies.
• A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same
number.
[1] ETSI EN 301 140-3-1: "Intelligent Network (IN); Intelligent Network Application Protocol
(INAP); Capability Set 2 (CS2); Part 3: Test Suite Structure and Test Purposes (TSS&TP)
specification for Service Switching Function (SSF); Sub-part 1: Basic capability set of CS-1
including CS-2 complements".
[2] ITU-T Recommendation Q.1224: "Distributed functional plane for intelligent network Capability
Set 2".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in EN 301 140-3-1 [1] apply.
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
BCSM Basic Call State Model
CCF Call Control Function
CPH Call Party Handling
CS Cabability Set
CS Call Segment
CV Connection View
INAP Intelligent Network Application Protocol
MSC Message Sequence Chart
PDU Protocol Data Unit
PIXIT Protocol Implementation eXtra Information for Testing
SCF Service Control Function
SDL Service and Description Language
SRF Specialized Resource Function
SSF Service Switching Function
SSP Service Switching Point
TCAP Transaction Capabilities Application Part
ETSI

---------------------- Page: 8 ----------------------

SIST EN 301 140-3-2:2001
7 ETSI EN 301 140-3-2 V1.1.3 (2000-05)
TP Test Purpose
TSS Test Suite Structure
TTCN Tree and Tabular Combined Notation
4Void
See EN 301 140-3-1 [1].
5Void
See EN 301 140-3-1 [1].
6Void
See EN 301 140-3-1 [1].
7 TSS and TP for CPH functions
7.0 Introduction
The Call Party Handling (CPH) includes a set of operations related to the call handling at the switch. The whole
functionality of the CPH operations is presented by means of the four Core Capabilities
(ITU-T Recommendation Q.1224 [2]):
• Core Capability one: allows the user to enter information during a midcall event;
• Core Capability two: is the ability of the SSF/CCF to connect a call party to an external resource to perform a
transfer;
• Core Capability three is the ability of the SSF/CCF to present the current call view to the SCF;
• Core Capability four: is the ability of the SSF/CCF to combine separate calls into one a single call.
The Test Purposes related to CPH are classified into 3 categories:
1) TP for the test of Conformance of each CPH procedure: this forms a set of TPs testing the basic functionality of
CPH operations;
2) TP for the test of the Switch capabilities: a group of TPs that tests the switch capability of handling different calls
at the same time;
3) Arming/Detecting rules.
7.1 Preambles and postambles for CPH
7.1.1 Names of preambles and postambles
CPH requires a large set of preambles. Due to the complexity of their description, the Connection View (CV) model is
used for an understanding of the configuration, referring to the following CV objects:
• CallSegmentAssociation (always initial);
• CallSegment;
ETSI

---------------------- Page: 9 ----------------------

SIST EN 301 140-3-2:2001
8 ETSI EN 301 140-3-2 V1.1.3 (2000-05)
• Connection point;
• Legs.
NOTE 1: The controlling leg can be either joined, shared or surrogate. The controlling leg identifies the physical
access to the end user.
NOTE 2: The legs are named by the LegId, and there is an unique correspondence between a LegId and a BCSM.
Restrictions: The test configuration is limited to three passive legs within a call segment, and three call segments within
a call segment association.
Comment on T preambles: The preamble T_OS (and all preambles and test cases which use this preamble) contains
reference to an ASP Mgt_SetTriggerTable. This does not exist in the protocol, but in the SDL model it identifies which
Trigger Detection points need to be set before commencing the test case.
Based on these considerations, using the naming conventions indicated in subclause 4.5.4 of EN 301 140-3-1 [1], and in
addition to the CS1 preambles, which are:
O_OS_null_null;
O_S2P_null_null.
CPH uses the following preambles:
- Originating
O_OH(1)_S2P_null(1)
O_OH(1)_OH(1)_S2P
O_null_OH(2)_S2P
O_null_OH(2)_S2P_controlling (To test the event report rules)
O_null_OH(2)_S2P_passive (To test the event report rules)
O_null_S2P_OH(3)
O_S2P_OH(1)_OH(3)
O_S2P_OH(2)_OH(3)
O_S2P_OH(3)_OH(3)
O_null_S3P_null
O_null_S3P_OH(3)
O_null_null_S4P
O_null_null_S4P_controlling (To test the event report rules)
O_null_null_S4P_passive (To test the event report rules)
O_null_S4P_OH(3)
- Terminating
T_TS_null_null
T_S2P_null_null
T_S2P_null_null_controlling (To test the event report rules)
T_S2P_null_null_passive (To test the event report rules)
ETSI

---------------------- Page: 10 ----------------------

SIST EN 301 140-3-2:2001
9 ETSI EN 301 140-3-2 V1.1.3 (2000-05)
T_OH(1)_S2P_null
T_null_OH(2)_S2P
T_null_S3P_null
T_null_null_S4P
T_null_null_S4P_controlling (To test the event report rules)
T_null_null_S4P_passive (To test the event report rules)
T_TF(2)_null_null
- Initiate Call Attempt (network initiated)
I_S1P_null_null
I_null_TF(2)_null
I_null_TF(2)_null_passive(To test the event report rules)
I_null_null_TF(3)
I_S1P_S1P_null
I_S1P_S1P_null _passive(To test the event report rules)
I_null_TF(2)_S1P
I_S1P_S1P_S1P
7.1.2 Preamble trees
Each preamble is composed of a limited set of operations (listed below) with the indication of the main parameters used.
These operations are shown in the preamble descriptions:
• CWA (ContinueWithArgument): CsId;
• CON (Connect): LegToBeCreated (default = 2), CsID;
• ICA (InitiateCallAttempt): LegToBeCreated (default = 1), newCallSegment (default = 1);
• MC (MergeCallSegments): sourceCallSegment, targetCallSegment;
• SL (SplitLeg): LegToBeSplit, newCallSegmentID;
• IDP (Initial Detection Point): trigger;
• RRB (RequestReportBCSMEvent): LegID, eventTypeBCSM.
Each operation shows the value of the required parameters, knowing that the leg numbers successively take the values 1,
2, 3, etc. In the case of CS, the same number is reused when a CS returns to idle following a mergeCallSegment.
The preamble trees are defined in subclause 7.1.6, where each branch or each preamble is numbered 1, 2, 3, etc., except
when there is an alternative or a node of two possible branches, which are then numbered 4-1 and 4-2 for example.
Each preamble shows the state from where it starts (idle or a different state reached by the execution of another
preamble), then it shows the operations executed in this preamble and finally the state or configuration reached, using
the notation described above.
ETSI

---------------------- Page: 11 ----------------------

SIST EN 301 140-3-2:2001
10 ETSI EN 301 140-3-2 V1.1.3 (2000-05)
7.1.3 TTCN-like notation for preamble description
The notation used to describe the trees and the required operations to move from one preamble to the next one, is a
TTCN-like notation, showing what is sent (character !) and received (character ?) by the co-ordination points (CPs)
addressing either Signalling Control or user A (CP1-1) or B (CP1-2) or C (CP1-3), etc., or by the main tester L1 playing
theroleofthe SCF.
7.1.4 Representation of preamble/postamble and test purposes using
MSCs
In addition to the TTCN-like notation, an MSC is drawn from the SDL simulator to represent each preamble or
postamble. For each test purpose, an MSC is also given, in addition to the tabular description of each TP.
Each MSC shows the interface between SCF and SSF using TCAP primitives, and the signalling control points. As there
can be any number of signalling control points (from 1 up to 8), the MSC shows SigCon A in one column, while all the
other SigCon are merged in a second column. The parameter CallRef number makes it possible to identify the SigCon
concerned, SigCon B being number 2, SigCon C being 3, etc.
7.1.5 How to interpret the parameters and their values as used in the
MSCs
The MSCs show the exchanges of PDUs of the TCAP protocol, as well as the Core INAP protocol. PDUs of both
protocols use parameters.
The list of the parameters for the Core INAP protocol is given in reference EN 301 140-3-1 [1].
The list of parameters for the TCAP protocol is repeated here for each TCAP primitive. Note that only mandatory
parameters are used.
TCAP primitives from SCF to TCAP:
TC_InvokeReq (InvokeID, DialogueID, Class, OperationCode, Timeout);
TC_BeginReq (DialogueID, OriginatingAddress);
TC_ContinueReq (DialogueID, OriginatingAddress);
TC_EndReq (DialogueID, Termination);
TC_AbortReq (DialogueID).
TCAP primitives from TCAP to SCF:
TC_InvokeInd (InvokeID, DialogueID, Class, OperationCode, LastComponent);
TC_BeginInd (DialogueID, OriginatingAddress, ComponentPresent);
TC_ContinueInd (DialogueID, OriginatingAddress, ComponentPresent);
TC_EndInd (DialogueID, Termination, ComponentPresent);
TC_AbortInd (DialogueID);
TC_ErrorInd (InvokeID, DialogueID, ErrorCode, LastComponent);
TC_ReturnResultInd (InvokeID, DialogueID, LastComponent, OperationCode, OperationArg);
TC_RejectInd (InvokeID, DialogueID).
The values of these parameters are either mandatory and imposed by the specifications, or they are informative only and
chosen arbitrarily in ranges compatible with the specifications.
ETSI

---------------------- Page: 12 ----------------------

SIST EN 301 140-3-2:2001
11 ETSI EN 301 140-3-2 V1.1.3 (2000-05)
The list of the informative parameters, for which a value is to be assigned in particular for the execution of a test suite, is
included in the PIXIT proforma.
Annex B and Annex C of the present document contain a copy of the PIXIT proforma parameter tables of respectively
the TCAP and the Core INAP protocols. These proforma tables are filled up and contain the parameter values used for
the definition of the MSCs and TPs.
7.1.6 Preamble descriptions
7.1.6.1 O (originating) preamble tree
Preamble O_OS_null_null
O_null
CP1-1! SetUpInd
L1? InitialDP
O_OS_null_null
MSC O_OS_null_null
SCF CS2_SSF SigCon_A otherSigCon
SetupInd
{ callRef 1, calledPartyNumber ’2000’H, callingPartyNumber ’1000’H }
TC_BeginInd
51, oSSF, TRUE
TC_InvokeInd
101, 51, IDP, TRUE, iDPArg : { serviceKey 1, calledPartyNumber ’2000’H, callingPartyNumber ’1000’H,
eventTypeBCSM analysedInformation, createdCallSegmentAssociation 1 }
2 - Preamble O_S2P_null_null
O_OS_null_null
L1! RequestReportBCSMEvent(2,oDisconnect)
L1! Connect(2,1)
CP1-2? SetUpReq
O_S2P_null_null
ETSI

---------------------- Page: 13 ----------------------

SIST EN 301 140-3-2:2001
12 ETSI EN 301 140-3-2 V1.1.3 (2000-05)
MSC O_S2P_null_null
SCF CS2_SSF SigCon_A otherSigCon
O_OS_null_null
TC_InvokeReq
1, 51, 2, RRB, medium, rRBArg : { bcsmEvents { { eventTypeBCSM oDisconnect, monitorMode interrupted, legID sendingSideID : ’02’H } } }
TC_InvokeReq
2, 51, 2, CON, medium, cONArg : { destinationRoutingAddress { ’2001’H }, callingPartyNumber ’1000’H, legToBeCreated sendingSideID : ’02’H }
TC_ContinueReq
51, oSCF
SetupReq
{ callRef 2, calledPartyNumber ’2001’H, callingPartyNumber ’1000’H }
3 - Preamble O_OH(1)_S2P_null
O_S2P_null_null
L1! SplitLeg(1,2)
L1?SplitLegReturnResult
L1! ContinueWithArgument (CsID = 1)
L1! RequestReportBCSMEvent(3,oDisconnect)
L1! Connect(3,2)
CP1-3? SetUpReq
O_OH(1)_S2P_null
ETSI

---------------------- Page: 14 ----------------------

SIST EN 301 140-3-2:2001
13 ETSI EN 301 140-3-2 V1.1.3 (2000-05)
MSC O_OH1_S2P_null
SCF CS2_SSF SigCon_A otherSigCon
O_S2P_null_null
TC_InvokeReq
3, 51, 1, SL, medium, sLArg : { legToBeSplit sendingSideID : ’01’H, newCallSegment 2 }
TC_ContinueReq
51, oSCF
TC_ContinueInd
51, oSSF, TRUE
TC_ReturnResultInd
3, 51, TRUE, SL_R, sLRArg : Null
TC_InvokeReq
4, 51, 2, CWA, medium, cWAArg : { legorCSID csID : 1 }
TC_InvokeReq
5, 51, 2, RRB, medium, rRBArg : { bcsmEvents { { eventTypeBCSM oDisconnect,
monitorMode interrupted, legID sendingSideID : ’03’H } } }
TC_InvokeReq
6, 51, 2, CON, medium, cONArg : { destinationRoutingAddress { ’2003’H },
callSegmentID 2, legToBeCreated sendingSideID : ’03’H }
TC_ContinueReq
51, oSCF
SetupReq
{ callRef 3, calledPartyNumber ’2003’H }
4 1 - Preamble O_OH(1)_OH(1)_S2P
ETSI

---------------------- Page: 15 ----------------------

SIST EN 301 140-3-2:2001
14 ETSI EN 301 140-3-2 V1.1.3 (2000-05)
O_OH(1)_S2P_null
L1! SplitLeg(1,3)
L1?SplitLegReturnResult
L1! ContinueWithArgument (CsID = 2)
L1! RequestReportBCSMEvent(4,oDisconnect)
L1! Connect(4,3)
CP1-4? SetUpReq
O_OH(1)_OH(1)_S2P
ETSI

---------------------- Page: 16 ----------------------

SIST EN 301 140-3-2:2001
15 ETSI EN 301 140-3-2 V1.1.3 (2000-05)
MSC O_OH1_OH1_S2P
SCF CS2_SSF SigCon_A otherSigCon
O_OH1_S2P_null
TC_InvokeReq
7, 51, 1, SL, medium, sLArg : { legToBeSplit sendingSideID : ’01’H, newCallSegment 3 }
TC_ContinueReq
51, oSCF
TC_ContinueInd
51, oSSF, TRUE
TC_ReturnResultInd
7, 51, TRUE, SL_R, sLRArg : Null
TC_InvokeReq
8, 51, 2, CWA, medium, cWAArg : { legorCSID csID : 2 }
TC_InvokeReq
9, 51, 2, RRB, medium, rRBArg : { bcsmEvents { { eventTypeBCSM oDisconnect,
monitorMode interrupted, legID sendingSideID : ’04’H } } }
TC_InvokeReq
10, 51, 2, CON, medium, cONArg : { destinationRoutingAddress { ’2005’H }, callSegmentID 3,
legToBeCreated sendingSideID : ’04’H }
TC_ContinueReq
51, oSCF
SetupReq
{ callRef 4, calledPartyNumber ’2005’H }
5 - Preamble O_null_OH(2)_S2P
ETSI

---------------------- Page: 17 ----------------------

SIST EN 301 140-3-2:2001
16 ETSI EN 301 140-3-2 V1.1.3 (2000-05)
O_OH(1)_OH(1)_S2P
L1! MergeCallSegments(1,2)
L1?MergeCallSegmentsReturnResult
L1! ContinueWithArgument(CSId=2)
O_null_OH(2)_S2P
ETSI

---------------------- Page: 18 ----------------------

SIST EN 301 140-3-2:2001
17 ETSI EN 301 140-3-2 V1.1.3 (2000-05)
MSC O_null_OH2_S2P
SCF CS2_SSF SigCon_A otherSigCon
O_OH1_OH1_S2P
TC_InvokeReq
11, 51, 1, MC, medium, mCArg : { sourceCallSegment 1, targetCallSegment 2 }
TC_ContinueReq
51,
...