SIST EN 300 185-3 V1.2.4:2005
(Main)Integrated Services Digital Network (ISDN); Conference call, add-on (CONF) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 3: Test Suite Structure and Test Purposes (TSS&TP) specification for the user
Integrated Services Digital Network (ISDN); Conference call, add-on (CONF) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 3: Test Suite Structure and Test Purposes (TSS&TP) specification for the user
Update to references to cite latest basic call standards et al. Incorporation of minor technical modifications where necessary.
Digitalno omrežje z integriranimi storitvami (ISDN) - Dopolnilna storitev: konferenčni klic, postopno vzpostavljanje (CONF) - Protokol digitalne naročniške signalizacije št. 1 (DSS1) - 3. del: Zgradba preskušalnega niza in nameni preskušanja (TSS&TP) - Specifikacija za uporabnika
General Information
Standards Content (Sample)
SLOVENSKI STANDARD
SIST EN 300 185-3 V1.2.4:2005
01-april-2005
'LJLWDOQRRPUHåMH]LQWHJULUDQLPLVWRULWYDPL ,6'1 'RSROQLOQDVWRULWHY
NRQIHUHQþQLNOLFSRVWRSQRY]SRVWDYOMDQMH &21) 3URWRNROGLJLWDOQHQDURþQLãNH
QQDPHQLVLJQDOL]DFLMHãW '66 GHO =JUDGEDSUHVNXãDOQHJDQL]DL
SUHVNXãDQMD 766 73 6SHFLILNDFLMD]DXSRUDEQLND
Integrated Services Digital Network (ISDN); Conference call, add-on (CONF)
supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol;
Part 3: Test Suite Structure and Test Purposes (TSS&TP) specification for the user
Ta slovenski standard je istoveten z: EN 300 185-3 Version 1.2.4
ICS:
33.080 Digitalno omrežje z Integrated Services Digital
integriranimi storitvami Network (ISDN)
(ISDN)
SIST EN 300 185-3 V1.2.4:2005 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
SIST EN 300 185-3 V1.2.4:2005
---------------------- Page: 2 ----------------------
SIST EN 300 185-3 V1.2.4:2005
EN 300 185-3 V1.2.4 (1998-06)
European Standard (Telecommunications series)
Integrated Services Digital Network (ISDN);
Conference call, add-on (CONF) supplementary service;
Digital Subscriber Signalling System No. one (DSS1) protocol;
Part 3: Test Suite Structure and Test Purposes (TSS&TP)
specification for the user
---------------------- Page: 3 ----------------------
SIST EN 300 185-3 V1.2.4:2005
2 EN 300 185-3 V1.2.4 (1998-06)
Reference
REN/SPS-05145-J1-3 (1por0iqo.PDF)
Keywords
ISDN, DSS1, supplementary service, CONF,
testing, TSS&TP, user
ETSI
Postal address
F-06921 Sophia Antipolis Cedex - FRANCE
Office address
650 Route des Lucioles - Sophia Antipolis
Valbonne - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
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
Internet
secretariat@etsi.fr
http://www.etsi.fr
http://www.etsi.org
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 1998.
All rights reserved.
ETSI
---------------------- Page: 4 ----------------------
SIST EN 300 185-3 V1.2.4:2005
3 EN 300 185-3 V1.2.4 (1998-06)
Contents
Intellectual Property Rights.4
Foreword .4
1 Scope.5
2 Normative references .5
3 Definitions.6
3.1 Definitions related to conformance testing . 6
3.2 Definitions related to EN 300 185-1. 6
4 Abbreviations.7
5 Test Suite Structure (TSS) .7
6 Test Purposes (TP).7
6.1 Introduction. 7
6.1.1 TP naming convention. 8
6.1.2 Source of TP definition . 8
6.1.3 TP structure. 8
6.1.4 Test strategy . 9
6.2 User TPs for CONF . 9
6.2.1 Served user (S/T or T). 9
6.2.1.1 Begin . 9
6.2.1.1.1 Begin from U00 . 9
6.2.1.1.2 Begin from U10 . 10
6.2.1.2 Adding . 11
6.2.1.3 Isolate . 14
6.2.1.4 Reattach . 15
6.2.1.5 Split . 15
6.2.1.6 Disconnection . 16
6.2.1.6.1 Disconnection of remote user. 16
6.2.1.6.2 Disconnection by remote user. 16
6.2.1.7 Terminate. 16
6.2.2 Private ISDN (T). 17
7 Compliance .18
8 Requirements for a comprehensive testing service.18
Annex A (informative): Changes with respect to the previous ETS 300 185-3 .19
History.20
ETSI
---------------------- Page: 5 ----------------------
SIST EN 300 185-3 V1.2.4:2005
4 EN 300 185-3 V1.2.4 (1998-06)
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 free of charge from the ETSI Secretariat. Latest updates are available on the
ETSI Web server (http://www.etsi.fr/ipr or 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 Signalling
Protocols and Switching (SPS).
The present document is part 3 of a multi-part standard covering the Digital Subscriber Signalling System No. one
(DSS1) protocol specification for the Integrated Services Digital Network (ISDN) Conference call, add-on (CONF)
supplementary service, as described 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 the user";
Part 4: "Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT)
proforma specification for the user";
Part 5: "Test Suite Structure and Test Purposes (TSS&TP) specification for the network";
Part 6: "Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT)
proforma specification for the network".
The present version updates the references to the basic call specifications.
National transposition dates
Date of adoption of this EN: 19 June 1998
Date of latest announcement of this EN (doa): 30 September 1998
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 31 March 1999
Date of withdrawal of any conflicting National Standard (dow): 31 March 1999
ETSI
---------------------- Page: 6 ----------------------
SIST EN 300 185-3 V1.2.4:2005
5 EN 300 185-3 V1.2.4 (1998-06)
1 Scope
This third part of EN 300 185 specifies the Test Suite Structure and Test Purposes (TSS&TP) for the User side of the T
reference point or coincident S and T reference point (as defined in ITU-T Recommendation I.411 [7]) of
implementations conforming to the stage three standard for the Conference call, add-on (CONF) supplementary service
for the pan-European Integrated Services Digital Network (ISDN) by means of the Digital Subscriber Signalling System
No. one (DSS1) protocol, EN 300 185-1 [1].
A further part of this EN specifies the Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information
for Testing (PIXIT) proforma based on the present document. Other parts specify the TSS&TP and the ATS and partial
PIXIT proforma for the Network side of the T reference point or coincident S and T reference point of implementations
conforming to EN 300 185-1 [1].
2 Normative references
References may be made to:
a) specific versions of publications (identified by date of publication, edition number, version number, etc.), in
which case, subsequent revisions to the referenced document do not apply; or
b) all versions up to and including the identified version (identified by "up to and including" before the version
identity); or
c) all versions subsequent to and including the identified version (identified by "onwards" following the version
identity); or
d) publications without mention of a specific version, in which case 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] EN 300 185-1 (V1.2): "Integrated Services Digital Network (ISDN); Conference call, add-on
(CONF) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol;
Part 1: Protocol specification".
[2] EN 300 185-2 (V1.2): "Integrated Services Digital Network (ISDN); Conference call, add-on
(CONF) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol;
Part 2: Protocol Implementation Conformance Statement (PICS) proforma specification".
[3] ISO/IEC 9646-1: "Information Technology - OSI Conformance Testing Methodology and
Framework; Part 1: General Concepts".
[4] ISO/IEC 9646-2: "Information Technology - OSI Conformance Testing Methodology and
Framework; Part 2: Abstract Test Suite specification".
[5] ISO/IEC 9646-3: "Information Technology - OSI Conformance Testing Methodology and
Framework; Part 3: The Tree and Tabular Combined Notation".
[6] EN 300 196-1: "Integrated Services Digital Network (ISDN); Generic functional protocol for the
support of supplementary services; Digital Subscriber Signalling System No. one (DSS1) protocol;
Part 1: Protocol specification".
[7] ITU-T Recommendation I.411 (1993): "ISDN user-network interfaces - Reference configurations".
[8] EN 300 403-1: "Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System
No. one (DSS1) protocol; Signalling network layer for circuit-mode basic call control; Part 1:
Protocol specification [ITU-T Recommendation Q.931 (1993), modified]".
[9] ITU-T Recommendation I.112: "Vocabulary and terms for ISDNs".
[10] CCITT Recommendation E.164: "Numbering plan for the ISDN era".
ETSI
---------------------- Page: 7 ----------------------
SIST EN 300 185-3 V1.2.4:2005
6 EN 300 185-3 V1.2.4 (1998-06)
[11] ITU-T Recommendation I.210: "Principles of the telecommunication services supported by an
ISDN and the means to describe them".
3 Definitions
For the purposes of the present document, the following definitions apply:
3.1 Definitions related to conformance testing
abstract test case: Refer to ISO/IEC 9646-1 [3].
Abstract Test Suite (ATS): Refer to ISO/IEC 9646-1 [3].
Implementation Under Test (IUT): Refer to ISO/IEC 9646-1 [3].
implicit send event: Refer to ISO/IEC 9646-3 [5].
lower tester: Refer to ISO/IEC 9646-1 [3].
point of control and observation: Refer to ISO/IEC 9646-1 [3].
Protocol Implementation Conformance Statement (PICS): Refer to ISO/IEC 9646-1 [3].
PICS proforma: Refer to ISO/IEC 9646-1 [3].
Protocol Implementation eXtra Information for Testing (PIXIT): Refer to ISO/IEC 9646-1 [3].
PIXIT proforma: Refer to ISO/IEC 9646-1 [3].
system under test: Refer to ISO/IEC 9646-1 [3].
Test Purpose (TP): Refer to ISO/IEC 9646-1 [3].
3.2 Definitions related to EN 300 185-1
Call Held auxiliary state: See EN 300 196-1 [6], subclause 7.1.2.
call reference: See EN 300 403-1 [8], subclause 4.3.
component: See EN 300 196-1 [6], subclause 11.2.2.1.
Idle auxiliary state: See EN 300 196-1 [6], subclause 7.1.2.
Integrated Services Digital Network (ISDN): See ITU-T Recommendation I.112 [9], definition 308.
ISDN number: A number conforming to the numbering and structure specified in CCITT Recommendation E.164 [10].
invoke component: See EN 300 196-1 [6], subclause 11.2.2.1.
remote user: A user which is involved in an instance of the CONF supplementary service but who has no control over
it.
return error component: See EN 300 196-1 [6], subclause 11.2.2.1.
return result component: See EN 300 196-1 [6], subclause 11.2.2.1.
served user: The user who invokes the CONF supplementary service.
service; telecommunication service: See ITU-T Recommendation I.112 [9], definition 201.
supplementary service: See ITU-T Recommendation I.210 [11], subclause 2.4.
ETSI
---------------------- Page: 8 ----------------------
SIST EN 300 185-3 V1.2.4:2005
7 EN 300 185-3 V1.2.4 (1998-06)
user: The DSS1 protocol entity at the User side of the user-network interface where a T reference point or coincident S
and T reference point applies.
user (S/T): The DSS1 protocol entity at the User side of the user-network interface where a coincident S and T
reference point applies.
user (T): The DSS1 protocol entity at the User side of the user-network interface where a T reference point applies
(User is the Private ISDN).
4 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ATM Abstract Test Method
ATS Abstract Test Suite
CCRef Call Reference for call related to the conference
CONF Conference call, add-on
DSS1 Digital Subscriber Signalling System No. one
ISDN Integrated Services Digital Network
IUT Implementation Under Test
SCRef Call Reference for a private call not related to the conference
TP Test Purpose
TSS Test Suite Structure
U00 Idle call state
U01 Call Initiated call state
U03 Outgoing Call Proceeding call state
U10 Active call state
U12 Disconnect Indication call state
U19 Release Request call state
5 Test Suite Structure (TSS)
CONF - User
Served user (S/T or T) Private ISDN (T)
(10)
Begin Adding Isolate Reattach Split Disconnect Terminate
(03) (04) (05) (06) (09)
from U00 from U10 of remote user by remote user
(01) (02) (07) (08)
NOTE: Numbers in brackets represent group numbers and are used in TP identifiers.
Figure 1: Test suite structure
6 Test Purposes (TP)
6.1 Introduction
For each test requirement a TP is defined.
ETSI
---------------------- Page: 9 ----------------------
SIST EN 300 185-3 V1.2.4:2005
8 EN 300 185-3 V1.2.4 (1998-06)
6.1.1 TP naming convention
TPs are numbered, starting at 001, within each group. Groups are organized according to the TSS. Additional references
are added to identify the actual test suite and whether it applies to the network or the user (see table 1).
Table 1: TP identifier naming convention scheme
Identifier: __
= supplementary service: e.g. "CONF"
= type of IUT: U User
N Network
= group 2 digit field representing group reference according to TSS
= sequential number (001-999)
6.1.2 Source of TP definition
The TPs are based on EN 300 185-1 [1], clauses 9, 10 and 14.
6.1.3 TP structure
Each TP has been written in a manner which is consistent with all other TPs. The intention of this is to make the TPs
more readable and checkable. A particular structure has been used and this is illustrated in table 2. This table should be
read in conjunction with any TP, i.e. use a TP as an example to fully understand the table.
Table 2: Structure of a single TP
TP part Text Example
Header tab see table 1
tab subclause 0.0.0
tab
valid, invalid, inopportune
CR. mandatory, optional, conditional
Stimulus Ensure that the IUT in the
U10, U10, etc.
see below for message structure receiving a XXXX message
or to request a .
Reaction sends, saves, does, etc.
using en-bloc sending, .
if the action is sending
see below for message structure
, etc.
and remains in the same call state
or and enters call state
Message SETUP, FACILITY, CONNECT, .
structure message containing a
a) Bearer capability, Facility, .
information element with
b) a
encoded as or including
and back to a or b,
NOTE: Text in italics will not appear in TPs and text between <> is filled in for each TP and may differ from one
TP to the next.
ETSI
---------------------- Page: 10 ----------------------
SIST EN 300 185-3 V1.2.4:2005
9 EN 300 185-3 V1.2.4 (1998-06)
6.1.4 Test strategy
As the base standard EN 300 185-1 [1] contains no explicit requirements for testing, the TPs were generated as a result
of an analysis of the base standard and the PICS specification EN 300 185-2 [2]. The criteria applied included the
following:
- only the requirements from the point of view of the T or coincident S and T reference point are considered;
- whether or not a test case can be built from the TP is not considered.
6.2 User TPs for CONF
All PICS items referred to in this subclause are as specified in EN 300 185-2 [2] unless indicated otherwise by another
numbered reference.
6.2.1 Served user (S/T or T)
Selection:IUT supports served user requirements. PICS: R 4.1.
6.2.1.1 Begin
6.2.1.1.1 Begin from U00
CONF_U01_001 subclause 9.2.1.1. valid optional
Ensure that the IUT in the call state U00, to request a conference,
sends, using implicitly en-bloc sending, a SETUP message containing a Facility information element with a
BeginCONF invoke component and a compatible (for CONF purposes) Bearer capability information element,
no Called party number and no Called party subaddress information element included and enters call state U01.
Selection: The BeginCONF component does not contain the ConfSize parameter.
CONF_U01_002 subclause 9.2.1.1. valid optional
Ensure that the IUT in the call state U00, to request a conference,
sends, using implicitly en-bloc sending, a SETUP message containing a Facility information element with a
BeginCONF invoke component, including a ConfSize parameter indicating the maximum number of remote users
and a compatible (for CONF purposes) Bearer capability information element, no Called party number and no
Called party subaddress information element included and enters call state U01.
Selection: The BeginCONF component contains the ConfSize parameter.
CONF_U01_003 subclause 9.2.1.1 valid mandatory
Ensure that the IUT in the call state U03 receiving a CONNECT message with a correctly encoded BeginCONF return
result component,
saves the ConferenceId parameter, does not respond to the network and enters call state U10.
CONF_U01_004 subclause 9.2.1.1 invalid mandatory
Ensure that the IUT in the call state U03 receiving a CONNECT message with an incorrectly encoded BeginCONF
return result component including an invalid invokeID,
sends a FACILITY or a DISCONNECT message containing a Facility information element with a reject
component encoded as return result problem.
CONF_U01_005 subclause 9.2.1.2 valid mandatory
Ensure that the IUT in the call state U01 receiving a RELEASE message with a correctly encoded BeginCONF return
error component,
sends a RELEASE COMPLETE message and enters call state U00.
CONF_U01_006 subclause 9.2.1.2 valid mandatory
Ensure that the IUT in the call state U03 receiving a DISCONNECT message with a correctly encoded BeginCONF
return error component,
enters state U12.
ETSI
---------------------- Page: 11 ----------------------
SIST EN 300 185-3 V1.2.4:2005
10 EN 300 185-3 V1.2.4 (1998-06)
CONF_U01_007 subclause 9.2.1.2 invalid mandatory
Ensure that the IUT in the call state U01 receiving a RELEASE message with an incorrectly encoded BeginCONF
return error component including an invalid invokeID,
sends a FACILTY message containing a Facility information element with a reject component encoded as return
error problem followed by a RELEASE COMPLETE message and enters call state U00,
or
sends a RELEASE COMPLETE message containing a Facility information element with a reject component
encoded as return error problem and enters call state U00.
CONF_U01_008 subclause 9.2.1.2 invalid mandatory
Ensure that the IUT in the call state U03 receiving a DISCONNECT message with an incorrectly encoded BeginCONF
return error component including an invalid invokeID,
sends a FACILTY message containing a Facility information element with a reject component encoded as return
error problem and enters call state U12,
or
sends a RELEASE message containing a Facility information element with a reject component encoded as return
error problem and enters call state U19.
6.2.1.1.2 Begin from U10
Selection: IUT supports beginning the conference from the Active call state U10. PICS: MC 1.2.
CONF_U02_001 subclause 9.2.2.1 valid optional
Ensure that the IUT in the call state U10, to request a conference,
sends a FACILITY message indicating the call reference of the existing call containing a Facility information
element with a BeginCONF invoke component and remains in the same call state.
Selection: The BeginCONF component does not contain the ConfSize parameter.
CONF_U02_002 subclause 9.2.2.1 valid optional
Ensure that the IUT in the call state U10 (Call Held), to request a conference,
sends a FACILITY message indicating the call reference of the existing call containing a Facility information
element with a BeginCONF invoke component and remains in the same call state.
Selection: The BeginCONF component does not contain the ConfSize parameter.
Selection: CONF invocation from the Call Held auxiliary state is supported. PICS: MC 3.1.
CONF_U02_003 subclause 9.2.2.1 valid optional
Ensure that the IUT in the call state U10, to request a conference,
sends a FACILITY message indicating the call reference of the existing call containing a Facility information
element with a BeginCONF invoke component with a ConfSize parameter indicating the maximum number of
remote users and remains in the same call state.
Selection: The BeginCONF component does contain the ConfSize parameter.
CONF_U02_004 subclause 9.2.2.1 valid optional
Ensure that the IUT in the call state U10 (Call Held), to request a conference,
sends a FACILITY message indicating the call reference of the existing call containing a Facility information
element with a BeginCONF invoke component with a ConfSize parameter indicating the maximum number of
remote users and remains in the same call state.
Selection: The BeginCONF component does contain the ConfSize parameter.
Selection: CONF invocation from the Call Held auxiliary state is supported. PICS: MC 3.1.
CONF_U02_005 subclause 9.2.2.1 valid mandatory
Ensure that the IUT in the call state U10, receiving a FACILITY message with a correctly encoded BeginCONF return
result component,
does not respond to the network and remains in the same call state.
CONF_U02_006 subclause 9.2.2.1 valid optional
Ensure that the IUT in the call state U10 (Call Held), receiving a FACILITY message with a correctly encoded
BeginCONF return result component,
does not respond to the network and remains in the same call state.
ETSI
---------------------- Page: 12 ----------------------
SIST EN 300 185-3 V1.2.4:2005
11 EN 300 185-3 V1.2.4 (1998-06)
Selection: CONF invocation from the Call Held auxiliary state is supported. PICS: MC 3.1.
CONF_U02_007 subclause 9.2.2.2 valid mandatory
Ensure that the IUT in the call state U10, receiving a FACILITY message with a correctly encoded BeginCONF return
error component,
does not respond to the network and remains in the same call state.
CONF_U02_008 subclause 9.2.2.2 valid optional
Ensure that the IUT in the call state U10 (Call Held), receiving a FACILITY message with a correctly encoded
BeginCONF return error component,
does not respond to the network and remains in the same call state.
Selection: CONF invocation from the Call Held auxiliary state is supported. PICS: MC 3.1.
CONF_U02_009 subclause 9.2.2.1 invalid mandatory
Ensure that the IUT in the call state U10, receiving a FACILITY message with an incorrectly encoded BeginCONF
return result component including an invalid invokeID,
sends a FACILITY message containing a Facility information element with a reject component encoded as return
result problem remains in the same call state.
CONF_U02_010 subclause 9.2.2.1 invalid optional
Ensure that the IUT in the call state U10 (Call Held), receiving a FACILITY message with an incorrectly encoded
BeginCONF return result component including an invalid invokeID,
sends a FACILITY message containing a Facility information element with a reject component encoded as return
result problem and remains in the same call state.
Selection: CONF invocation from the Call Held auxiliary state is supported. PICS: MC 3.1.
CONF_U02_011 subclause 9.2.2.2 invalid mandatory
Ensure that the IUT in the call state U10, receiving a FACILITY message with an incorrectly encoded BeginCONF
return error component including an invalid invokeID,
sends a FACILITY message containing a Facility information element with a reject component encoded as return
error problem and remains in the same call state.
CONF_U02_012 subclause 9.2.2.2 invalid optional
Ensure that the IUT in the call state U10 (Call Held), receiving a FACILITY message with an incorrectly encoded
BeginCONF return error component including an invalid invokeID,
sends a FACILITY message containing a Facility information element with a reject component encoded as return
error problem and remains in the same call state.
Selection: CONF invocation from the Call Held auxiliary state is supported. PICS: MC 3.1.
6.2.1.2 Adding
CONF_U03_001 subclause 9.2.3.1 valid optional
Ensure that the IUT in the SCRef call state U10 and in the CCRef call state U10, to add the remote user to the
conference,
sends a FACILITY message indicating the call reference of the call to be added (SCRef) containing a Facility
information element with an AddCONF invoke component including the correct ConferenceId parameter and
remains in the same call states.
Selection: The IUT is able to handle two (non-held) calls.
CONF_U03_002 subclause 9.2.3.1 valid optional
Ensure that the IUT in the SCRef call state U10(Call Held) and in the CCRef call state U10 (Idle), to add the remote
user to the conference,
sends a FACILITY message indicating the call reference of the call to be added (SCRef) containing a Facility
information element with an AddCONF invoke component including the correct ConferenceId parameter and
remains in the same call states.
Selection: Adding of a party from the Call Held auxiliary state is supported. PICS: MC 3.2.
ETSI
---------------------- Page: 13 ----------------------
SIST EN 300 185-3 V1.2.4:2005
12 EN 300 185-3 V1.2.4 (1998-06)
CONF_U03_003 subclause 9.2.3.1 valid optional
Ensure that the IUT in the SCRef call state U10(Call Held) and in the CCRef call state U10 (Call Held), to add the
remote user to the conference,
sends a FACILITY message indicating the call reference of the call to be added (SCRef) containing a Facility
information element with an AddCONF invoke component including the correct ConferenceId parameter and
remains in the same call states.
Selectio
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.