ETSI TS 186 010-2 V2.1.1 (2009-07)

Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services; Conference (CONF); Part 2: Test Suite Structure and Test Purposes (TSS&TP)

DTS/TISPAN-06026-2-NGN-R2

General Information

• Status: Published
• Publication Date: 30-Jul-2009
• Technical Committee: TISPAN 6 - TISPAN Testing
• Current Stage: 12 - Completion
• Due Date: 12-Aug-2009
• Completion Date: 31-Jul-2009

Standards Content (Sample)

ETSI TS 186 010-2 V2.1.1 (2009-07)
Technical Specification


Telecommunications and Internet converged Services and
Protocols for Advanced Networking (TISPAN);
PSTN/ISDN simulation services;
Conference (CONF);
Part 2: Test Suite Structure and Test Purposes (TSS&TP)

---------------------- Page: 1 ----------------------
2 ETSI TS 186 010-2 V2.1.1 (2009-07)



Reference
DTS/TISPAN-06026-2-NGN-R2
Keywords
IMS, TSS&TP, CONF, testing
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

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://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
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 2009.
All rights reserved.

TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
LTE™ is a Trade Mark of ETSI currently being registered
for the benefit of its Members and of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI

---------------------- Page: 2 ----------------------
3 ETSI TS 186 010-2 V2.1.1 (2009-07)
Contents
Intellectual Property Rights . 4
Foreword . 4
1 Scope . 5
2 References . 5
2.1 Normative references . 5
2.2 Informative references . 5
3 Definitions and abbreviations . 6
3.1 Definitions . 6
3.2 Abbreviations . 6
4 Test Suite Structure (TSS) and configuration . 6
4.1 Configuration . 6
5 Test Purposes (TP) . 7
5.1 Introduction . 7
5.1.1 TP naming convention . 7
5.1.2 Test strategy . 7
5.2 Signalling requirements . 8
5.2.1 Conference Focus . 8
5.2.1.1 Conference creation . 8
5.2.1.2 Joining a conference . 11
5.2.1.3 Inviting other users to a conference . 12
5.2.1.4 Leaving a conference . 23
5.2.1.5 Removing a conference participant from a conference . 23
5.2.1.6 Conference termination . 25
5.2.2 Conference Notification Service . 26
5.2.3 Actions at the UE . 34
5.3 Interaction with other supplementary services . 42
5.3.1 Terminating Identification Restriction (TIR) . 42
5.3.2 Originating Identification Restriction (OIR) . 43
5.3.3 Anonymous Communication Rejection and Communication Barring (ACR/CB) . 46
History . 47

ETSI

---------------------- Page: 3 ----------------------
4 ETSI TS 186 010-2 V2.1.1 (2009-07)
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 ETSI 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://webapp.etsi.org/IPR/home.asp).
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 ETSI 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 Technical Specification (TS) has been produced by ETSI Technical Committee Telecommunications and Internet
converged Services and Protocols for Advanced Networking (TISPAN).
The present document is part 2 of a multi-part deliverable covering the PSTN/ISDN simulation services; Conference
(CONF) as identified below:
Part 1: "Protocol Implementation Conformance Statement (PICS)";
Part 2: "Test Suite Structure and Test Purposes (TSS&TP)";
Part 3: "Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT)
proforma specification for the user".
ETSI

---------------------- Page: 4 ----------------------
5 ETSI TS 186 010-2 V2.1.1 (2009-07)
1 Scope
The present document specifies the Protocol implementation conformance statement (PICS) for the Conference (CONF)
service based on stage one and two of the ISDN CONF supplementary service. Within the Next Generation Network
(NGN) the stage 3 is specified using the IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP)
and Session Description Protocol (SDP), TS 183 005 [1].
A further part of the present document specifies the Abstract Test Suite (ATS) and partial Protocol Implementation
eXtra Information for Testing (PIXIT) proforma based on the present document.
2 References
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• Non-specific reference may be made only to a complete document or a part thereof and only in the following
cases:
- if it is accepted that it will be possible to use all future changes of the referenced document for the
purposes of the referring document;
- for informative references.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee
their long term validity.
2.1 Normative references
The following referenced documents are indispensable for the application of the present document. For dated
references, only the edition cited applies. For non-specific references, the latest edition of the referenced document
(including any amendments) applies.
[1] ETSI TS 183 005: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); PSTN/ISDN simulation services: Conference (CONF); Protocol
specification".
[2] ETSI TS 186 010-1: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); PSTN/ISDN simulation services; Conference (CONF); Part 1:
Protocol implementation Conformance Statement (PICS)".
[3] ETSI TS 124 147: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); LTE; Conferencing using the IP Multimedia (IM) Core
Network (CN) subsystem; Stage 3 (3GPP TS 24.147 version 8.2.0 Release 8)".
2.2 Informative references
The following referenced documents are not essential to the use of the present document but they assist the user with
regard to a particular subject area. For non-specific references, the latest version of the referenced document (including
any amendments) applies.
Not applicable.
ETSI

---------------------- Page: 5 ----------------------
6 ETSI TS 186 010-2 V2.1.1 (2009-07)
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in [1] apply.
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in [1] apply.
4 Test Suite Structure (TSS) and configuration
Table 1: Test suite structure
ConferenceFocus
 CONF_N01_xxx
 CONF_N02_xxx
 CONF_N03_xxx
 CONF_N04_xxx
 CONF_N05_xxx
 CONF_N06_xxx
 CONF_N07_xxx

UserEquipment
 CONF_U01_xxx

Interaction
TIR CONF_N08_xxx
OIR CONF_N09_xxx
ACR CONF_N10_xxx

4.1 Configuration
The scope of the present document is to test the signalling and procedural aspects of the stage 3 requirements as
described in [1]. The stage 3 description respects the requirements to several network entities and also to requirements
regarding to end devices. Therefore several interfaces (reference points) are addressed to satisfy the test of the different
entities.
Therefore to test the appropriate entities the configurations below are applicable:
Testing of the Application Server. This entity is responsible to perform the service. Hence the ISC interface is the
appropriate access point. Figure 1 points to this.

Figure 1: Applicable interface to test AS functionalities
ETSI

---------------------- Page: 6 ----------------------
7 ETSI TS 186 010-2 V2.1.1 (2009-07)
If the ISC interface is not accessible it is also applicable to perform the test of the AS using any NNI (Mw, Mg, Mx)
interface (consider figure 2). In case only the Gm interface is accessible this shall be used instead. In this case, be aware
that the verification of several requirements is impeded.
Mw, Mg, Mx
Mw, Mg, Mx
CSCF
Test (and/or AS) Test
System System
Implementation
under Test

Figure 2: Applicable interfaces to test using the (generic) NNI interface
Figure 2 illustrates the usage of any NNI interface.
5 Test Purposes (TP)
5.1 Introduction
For each test requirement a TP is defined.
5.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 2).
Table 2: TP identifier naming convention scheme
Identifier: __
= supplementary service: e.g. "CONF"
= type of IUT: U User
N Network
yyy service
= group 2 digit field representing group reference according to TSS
= sequential number (001-999)

5.1.2 Test strategy
As the base standard TS 183 005 [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 TS 186 010-1 [2].
ETSI

---------------------- Page: 7 ----------------------
8 ETSI TS 186 010-2 V2.1.1 (2009-07)
5.2 Signalling requirements
5.2.1 Conference Focus
5.2.1.1 Conference creation
TSS TP Reference Selection expression
ConferenceFocus CONF_N01_001 5.3.2.3/ [3]
Test purpose
Conference creation with a conference factory URI. Conference event package subscribed.

Ensure that a conference can be created by a UE using the conference factory URI. The "isfocus" feature
parameter indicated in Contact header is received in the 200 OK (INVITE). The conference participant shall store
the content of the received Contact header as the conference URI. In addition the conference participant
subscribes to the conference event package.
SIP header values:
INVITE: Request URI contained the conference factory URI
200 OK: "isfocus" feature parameter indicated in Contact header field
  conference URI contained in the Contact header field
SUBSCRIBE: Request URI contained the conference URI
 Event header contains "conference"
NOTIFY: Event contains conference; Subscription-State contains active; expires=xxxx
Comments:
ISC#1 Focus
INVITE


200 OK (INVITE)

ACK

SUBSCRIBE

200 OK (SUBSCRIBE)
NOTIFY
200 OK NOTIFY
Apply post test routine

TSS TP Reference Selection expression
ConferenceFocus CONF_N01_002 5.3.2.3/[3]
Test purpose
Conference creation with a conference factory URI. Conference event package not subscribed.

Ensure that a conference can be created by a UE using the conference factory URI. The "isfocus" feature
parameter indicated in Contact header is received in the 200 OK (INVITE). The conference participant shall store
the content of the received Contact header as the conference URI. The conference participant does not subscribe
to the conference event package.
SIP header values:
INVITE:  Request URI contained the conference factory URI
200 OK:  "isfocus" feature parameter indicated in Contact header field
   conference URI contained in the Contact header field
Comments:
ISC#1 Focus

INVITE



200 OK (INVITE)
ACK
Apply post test routine

ETSI

---------------------- Page: 8 ----------------------
9 ETSI TS 186 010-2 V2.1.1 (2009-07)
TSS TP Reference Selection expression
ConferenceFocus CONF_N01_003 5.3.2.3/[3] PICS 1/5
Test purpose
Conference creation with a conference URI. Conference event package subscribed.

Ensure that a conference can be created by a UE using the conference URI. The "isfocus" feature parameter
indicated in Contact header is received in the 200 OK (INVITE). The conference participant shall store the content
of the received Contact header as the conference URI. In addition the conference participant subscribes to the
conference event package.
SIP header values:
INVITE: Request URI contained the conference URI
200 OK: "isfocus" feature parameter indicated in Contact header field
  conference URI contained in the Contact header field
SUBSCRIBE: Request URI contained the conference URI
  Event header contains "conference"
NOTIFY: Event contains conference; Subscription-State contains active; expires=xxxx
Comments:
ISC#1 Focus
INVITE


200 OK (INVITE)
ACK

SUBSCRIBE
200 OK (SUBSCRIBE)
NOTIFY
200 OK NOTIFY
Apply post test routine

TSS TP Reference Selection expression
ConferenceFocus CONF_N01_004 5.3.2.3/[3] PICS 1/5
Test purpose
Conference creation with a conference URI. Conference event package not subscribed.

Ensure that a conference can be created by a UE using the conference URI. The "isfocus" feature parameter
indicated in Contact header is received in the 200 OK (INVITE). The conference participant shall store the content
of the received Contact header as the conference URI. The conference participant does not subscribe to the
conference event package.
SIP header values:
INVITE: Request URI contained the conference URI
200 OK: "isfocus" feature parameter indicated in Contact header field
  conference URI contained in the Contact header field
Comments:
ISC#1 Focus
INVITE


200 OK (INVITE)

ACK
Apply post test routine

ETSI

---------------------- Page: 9 ----------------------
10 ETSI TS 186 010-2 V2.1.1 (2009-07)
TSS TP Reference Selection expression
ConferenceFocus CONF_N01_005 5.3.2.3/[3] NOT PICS 1/4
AND PICS 1/7
Test purpose
Conference creation with a conference factory URI. Preconditions indicated a conference URI is sent in the first
provisional response.

Ensure that a conference can be created by a UE using the conference factory URI. Preconditions are requested
by the originating UE. The "isfocus" feature parameter indicated in Contact header is received in the 200 OK
(INVITE). The conference participant shall store the content of the received Contact header as the conference
URI.
SIP header values:
INVITE: Request URI contained the conference factory URI
 SDP a=curr:qos local none
  a=curr:qos remote none
  a=des:qos mandatory local sendrecv
  a=des:qos none remote sendrecv

183 conference URI contained in the Contact header field
SDP a=curr:qos local none
  a=curr:qos remote none
  a=des:qos mandatory local sendrecv
  a=des:qos mandatory remote sendrecv
  a=conf:qos remote sendrecv

UPDATE:
SDP a=curr:qos local sendrecv
  a=curr:qos remote none
  a=des:qos mandatory local sendrecv
  a=des:qos mandatory remote sendrecv

200 OK UPDATE
SDP a=curr:qos local sendrecv
  a=curr:qos remote sendrecv
  a=des:qos mandatory local sendrecv
  a=des:qos mandatory remote sendrecv

200 OK: "isfocus" feature parameter indicated in Contact header field
 conference URI contained in the Contact header field
SUBSCRIBE: Request URI contained the conference URI
Comments:
ISC#1 Focus
INVITE

183 Session Progress
PRACK
200 OK PRACK
UPDATE
200 OK UPDATE

200 OK (INVITE)

ACK
Apply post test routine

TSS TP Reference Selection expression
ConferenceFocus CONF_N01_007 5.3.2.3/[3]
Test purpose
Conference creation with a conference factory URI not allocated in the focus unsuccessful.

Ensure that a conference cannot be created by a UE using the conference factory URI not allocated in the focus.
The request is rejected by the focus with a 488 Not Acceptable Here final response.
SIP header values:
INVITE: Request URI contained the conference factory URI not allocated in the focus
Comments:
ISC#1 Focus

INVITE
488 Not Acceptable Here
ACK

ETSI

---------------------- Page: 10 ----------------------
11 ETSI TS 186 010-2 V2.1.1 (2009-07)
5.2.1.2 Joining a conference
TSS TP Reference Selection expression
ConferenceFocus CONF_N02_001 5.3.2.4/[3] NOT PICS 1/6
Test purpose
Participant dial-in the conference, the conference URI is used.

ISC#1 established a conference. ISC#2 joins in that conference after has been received a REFER request and the
Refer-To header referring to the Focus. The UE sends an INVITE request to the conferencing AS the conference
URI is known at the ISC#2. The request is successful.
SIP header values:
REFER: Request URI=ISC#2
  Refer-To=Focus; method=INVITE
  Referred-By=ISC#1
INVITE 2: Focus
18x "isfocus" feature parameter indicated in Contact header field
200 OK: "isfocus" feature parameter indicated in Contact header field
  conference URI contained in the Contact header field
Comments:
ISC#1 Focus ISC#2
Conference creation
INVITE INVITE

200 OK (INVITE) 200 OK (INVITE)
ACK ACK

ISC#2 joining in the conference
REFER  REFER
202 Accepted  202 Accepted

NOTIFY (100)  NOTIFY (100)
200 OK (NOTIFY)  200 OK (NOTIFY)

 INVITE INVITE 2
 18x 18x

 200 OK INVITE 200 OK INVITE
 ACK ACK


NOTIFY (200) NOTIFY (200)
200 OK (NOTIFY)  200 OK (NOTIFY)
Apply post test routine

TSS TP Reference Selection expression
ConferenceFocus CONF_N02_002 5.3.2.4/[3]
Test purpose
Participant dial-in the conference, the conference URI is not allocated, the request is rejected.

ISC#1 established a conference. ISC#2 joins in that conference. The conference URI in the INVITE request is not
allocated at the focus. The request is rejected with the final response 4xx.
SIP header values:
INVITE 2: Request URI contained the conference URI not allocated in the focus (PIXIT)
Comments:
ISC#1 Focus ISC#2
Conference creation
INVITE INVITE

200 OK (INVITE) 200 OK (INVITE)
ACK ACK

ISC#2 joining in the conference
 INVITE INVITE 2
 4xx 4xx

 ACK ACK

ETSI

---------------------- Page: 11 ----------------------
12 ETSI TS 186 010-2 V2.1.1 (2009-07)
5.2.1.3 Inviting other users to a conference
TSS TP Reference Selection expression
ConferenceFocus CONF_N03_001 5.3.1.5.3/[3] NOT PICS 1/6
Test purpose
Inviting participant by sending REFER to the focus.

ISC#1 established a conference. ISC#1 invites ISC#2 to join into the conference. The ISC#1 sends a REFER to
the focus; the focus sends an INVITE request to ISC#2 to invite the ISC#2 to the conference.
SIP header values:
REFER: Request URI contained the conference URI
 Refer-To contains the URI of ISC#2, method=invite
 Referred-By contains SIP URI of ISC#1
INVITE 2: Request URI contained the conference URI
 The P-Asserted-Identity contains the conference URI.
 "isfocus" feature parameter indicated in Contact header field
 conference URI contained in the Contact header field
 Referred-By contains SIP or tel URI of ISC#1
NOTIFY 1 Event contains conference; Subscription-State contains active
 message/sipfrag contains SIP/2.0 100 Trying
NOTIFY 2 Event contains conference; Subscription-State contains active
 message/sipfrag contains SIP/2.0 200 OK
Comments:
ISC#1 Focus ISC#2
Conference creation

INVITE INVITE
200 OK (INVITE) 200 OK (INVITE)
ACK ACK
ISC#1 invites ISC#2 to the conference

REFER REFER
202 Accepted 202 Accepted

 Focus dials out to invite ISC#2
 INVITE 2 INVITE

NOTIFY NOTIFY 1
200 OK NOTIFY 200 OK NOTIFY
 180 Ringing 180 Ringing

 200 OK INVITE 200 OK INVITE
 ACK ACK
NOTIFY NOTIFY 2
200 OK NOTIFY 200 OK NOTIFY
Apply post test routine

ETSI

---------------------- Page: 12 ----------------------
13 ETSI TS 186 010-2 V2.1.1 (2009-07)
TSS TP Reference Selection expression
ConferenceFocus CONF_N03_002 5.3.1.5.3/[3] NOT PICS 1/6
Test purpose
Inviting participant by sending REFER to the participant.

ISC#1 established a conference. ISC#1 invites ISC#2 to join into the conference by sending a REFER to this
participant. The participant sends an INVITE request to the focus to dial in. The conference event package is not
subscribed.
SIP header values:
REFER: Request URI contained the URI of ISC#2
 Refer-To contains the conference URI, method=invite
 Referred-By contains the URI of ISC#1
INVITE 2: Request URI contained the conference URI
 The P-Asserted-Identity contains the URI of ISC#2.
 "isfocus" feature parameter indicated in Contact header field
 conference URI contained in the Contact header field
 Referred-By contains SIP or tel URI of ISC#1
NOTIFY 1 Event contains conference; Subscription-State contains active
 message/sipfrag contains SIP/2.0 100 Trying
NOTIFY 2 Event contains conference; Subscription-State contains active
 message/sipfrag contains SIP/2.0 200 OK
Comments:
ISC#1 Focus ISC#2
Conference creation
INVITE INVITE
200 OK (INVITE) 200 OK (INVITE)
ACK ACK
ISC#1 invites ISC#2 to the conference

REFER REFER

202 Accepted 202 Accepted
NOTIFY  NOTIFY 1

200 OK NOTIFY 200 OK NOTIFY

 ISC#2 joins in the conference

 INVITE INVITE 2
 180 Ringing 180 Ringing
 200 OK INVITE 200 OK INVITE

ACK ACK
NOTIFY NOTIFY 2
200 OK NOTIFY 200 OK NOTIFY
Apply post test routine

ETSI

---------------------- Page: 13 ----------------------
14 ETSI TS 186 010-2 V2.1.1 (2009-07)
TSS TP Reference Selection expression
ConferenceFocus CONF_N03_003 5.3.1.5.4/[3] NOT PICS 1/6
Test purpose
Inviting participant by sending a participant list to the focus.

ISC#1 established a conference. A participant list is contained in the INVITE to create the conference. The AS
establishes a communication to the user indicated in the participant list.
SIP header values:
INVITE 1: Request URI=Focus
    

INVITE 2: Request URI = ISC#2
  The P-Asserted-Identity contains the conference URI.
  "isfocus" feature parameter indicated in Contact header field
  conference URI contained in the Contact header field
Comments:
ISC#1 Focus ISC#2
Conference creation
INVITE 1 INVITE

200 OK (INVITE) 200 OK (INVITE)
ACK ACK
 Focus dials out to invite ISC#2

 INVITE 2 INVITE
 180 Ringing 180 Ringing
 200 OK INVITE 200 OK INVITE
 ACK ACK
Apply post test routine

TSS TP Reference Selection expression
ConferenceFocus CONF_N03_004 5.3.1.5.4/[3] NOT PICS 1/6
Test purpose
Inviting participant by sending a participant list to the focus in an active session.

ISC#1 established a conference. A participant list is contained in the INVITE to create the conference. The AS
establishes a communication to the user indicated in the participant list.
SIP header values:
INVITE 1: Request URI=Focus
        cp:copyControl="to"/>

INVITE 2: Request URI = ISC#2
  The P-Asserted-Identity contains the conference URI.
  "isfocus" feature parameter indicated in Contact header field
  conference URI contained in the Contact header field
Comments:
ISC#1 Focus ISC#2
INVITE (S1)
180 Ringing
200 OK INVITE

ACK

INVITE 1 (S1, sendonly)  INVITE
200 OK (INVITE)  200 OK (INVITE (recvonly)
ACK  ACK
Conference creation

INVITE 1 (S2) INVITE
200 OK (INVITE) 200 OK (INVITE)
ACK ACK
Focus dials out to invite ISC#2

 INVITE 2 INVITE
 180 Ringing 180 Ringing

200 OK INVITE 200 OK INVITE
 ACK ACK
Apply post test routine

ETSI

---------------------- Page: 14 ----------------------
15 ETSI TS 186 010-2 V2.1.1 (2009-07)
TSS TP Reference Selection expression
ConferenceFocus CONF_N03_005 5.3.1.3.3/[3]
Test purpose
Three-way session creation. REFER is sent to the participants.

Ensure that it is possible that two active sessions are able to join in a three way session and the existing sessions
with the served user is terminated by the remote users. The remote users receive a REFER request and the
Refer-To header contains the address of the Focus. The remote users use the URI of the Refer-To header as the
Request URI of the INVITE request.
SIP header values:
REFER (S1): Request line=ISC#2
  Refer-To=Focus; method=INVITE
  Referred-By=ISC#1
REFER (S2): Request line=ISC#3
  Refer-To=Focus; method=INVITE
  Referred-By=ISC#1
INVITE (S4): Request URI=Focus
  Referred-By=ISC#1
INVITE (S5): Request URI=Focus
  Referred-By=ISC#1
Comments:
ISC#1 Focus ISC#2 ISC#3

Establish session #1
Session #1 on hold
Establish session #2
Session #2 on hold
INVITE (S3) INVITE

200 OK (INVITE) 200 OK (INVITE)

ACK ACK


REFER (S1) REFER
202 Accepted  202 Accepted


NOTIFY (100) NO
...