ETSI TS 186 010-2 V4.1.1 (2017-12)

Core Network and Interoperability Testing (INT); Conference (CONF) using IP Multimedia (IM) Core Network (CN) subsystem; Conformance test specification; (3GPPTM Release 12); Part 2: Test Suite Structure and Test Purposes (TSS&TP)

RTS/INT-00145-2

General Information

• Status: Published
• Publication Date: 20-Dec-2017
• Technical Committee: INT - Core Network and Interoperability Testing
• Current Stage: 12 - Completion
• Due Date: 04-Jan-2018
• Completion Date: 21-Dec-2017

Standards Content (Sample)

ETSI TS 186 010-2 V4.1.1 (2017-12)






TECHNICAL SPECIFICATION
Core Network and Interoperability Testing (INT);
Conference (CONF) using IP Multimedia (IM)
Core Network (CN) subsystem;
Conformance test specification;
(3GPP™ Release 12);
Part 2: Test Suite Structure and Test Purposes (TSS&TP)

---------------------- Page: 1 ----------------------
2 ETSI TS 186 010-2 V4.1.1 (2017-12)



Reference
RTS/INT-00145-2
Keywords
CONF, conformance, IMS, PICS, 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
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the
print of the Portable Document Format (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
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI 2017.
All rights reserved.

TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M logo is protected for the benefit of its Members.
GSM® and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI

---------------------- Page: 2 ----------------------
3 ETSI TS 186 010-2 V4.1.1 (2017-12)
Contents
Intellectual Property Rights . 4
Foreword . 4
Modal verbs terminology . 4
1 Scope . 5
2 References . 5
2.1 Normative references . 5
2.2 Informative references . 5
3 Definitions, symbols and abbreviations . 6
3.1 Definitions . 6
3.2 Symbols . 6
3.3 Abbreviations . 6
4 Test Suite Structure (TSS) and configuration . 6
4.1 Table of Test Suite Structure . 6
4.2 Configuration . 7
4.2.0 Introduction. 7
4.2.1 Testing of the AS . 7
4.2.2 Testing of the UE . 8
5 Test Purposes (TP) . 8
5.1 Introduction . 8
5.1.1 TP naming convention . 8
5.1.2 Test strategy . 9
5.2 Signalling requirements . 9
5.2.1 Conference Focus . 9
5.2.1.1 Conference creation . 9
5.2.1.2 Joining a conference . 12
5.2.1.3 Inviting other users to a conference . 13
5.2.1.4 Leaving a conference . 19
5.2.1.5 Removing a conference participant from a conference . 20
5.2.1.6 Conference termination . 21
5.2.2 Actions at the UE . 22
5.3 Interaction with other supplementary services . 30
5.3.1 Terminating Identification Restriction (TIR) . 30
5.3.2 Originating Identification Restriction (OIR) . 31
5.3.3 Anonymous Communication Rejection and Communication Barring (ACR/CB) . 34
Annex A (informative): Bibliography . 36
History . 37


ETSI

---------------------- Page: 3 ----------------------
4 ETSI TS 186 010-2 V4.1.1 (2017-12)
Intellectual Property Rights
Essential patents
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 (https://ipr.etsi.org/).
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.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
Foreword
This Technical Specification (TS) has been produced by ETSI Technical Committee Core Network and Interoperability
Testing (INT).
The present document is part 2 of a multi-part deliverable covering the Conformance Test Specification of Conference
(CONF) using IP Multimedia (IM) Core Network (CN) subsystem, 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".
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.

ETSI

---------------------- Page: 4 ----------------------
5 ETSI TS 186 010-2 V4.1.1 (2017-12)
1 Scope
The present document provides the Implementation Conformance Statement (ICS) pro forma for the Conference
(CONF) service based on stage one and two of the ISDN CONF supplementary service defined in ETSI TS 124 605 [1]
in compliance with the relevant requirements
2 References
2.1 Normative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
https://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.
The following referenced documents are necessary for the application of the present document.
[1] ETSI TS 124 605 (V12.5.0) (04-2015): "Digital cellular telecommunications system (Phase 2+);
Universal Mobile Telecommunications System (UMTS); LTE; Conference (CONF) using IP
Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.605
version 12.5.0 Release 12)".
[2] ETSI TS 124 147: "Digital cellular telecommunications system (Phase 2+) (GSM); Universal
Mobile Telecommunications System (UMTS); LTE; Conferencing using the IP Multimedia (IM)
Core Network (CN) subsystem; Stage 3 (3GPP TS 24.147 Release 12)".
[3] ETSI TS 186 010-1: "Core Network and Interoperability Testing (INT); Conference (CONF) using
IP Multimedia (IM) Core Network (CN) subsystem; Conformance test specification (3GPP
Release 12); Part 1: Protocol Implementation Conformance Statement (PICS)".
2.2 Informative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] ISO/IEC 9646-1: "Information technology - Open systems interconnection - Conformance testing
methodology and framework - Part 1: General concepts".
ETSI

---------------------- Page: 5 ----------------------
6 ETSI TS 186 010-2 V4.1.1 (2017-12)
3 Definitions, symbols and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in ETSI TS 124 605 [1] and the following
apply:
Implementation Under Test (IUT): Refer to ISO/IEC 9646-1 [i.1].
PICS pro forma: Refer to ISO/IEC 9646-1 [i.1].
Point of Control and Observation: Refer to ISO/IEC 9646-1 [i.1].
Protocol Implementation Conformance Statement (PICS): Refer to ISO/IEC 9646-1 [i.1].
System Under Test (SUT): Refer to ISO/IEC 9646-1 [i.1].
Test Purpose (TP): Refer to ISO/IEC 9646-1 [i.1].
NOTE: This may contain additional information.
3.2 Symbols
For the purposes of the present document, the symbols given in ETSI TS 124 605 [1] apply.
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in ETSI TS 124 605 [1] and the following apply:
CONF CONFerence calling
IUT Implementation Under Test
SUT System Under Test
UE User Equipment
4 Test Suite Structure (TSS) and configuration
4.1 Table of Test Suite Structure
ETSI

---------------------- Page: 6 ----------------------
7 ETSI TS 186 010-2 V4.1.1 (2017-12)
Table 4.1-1: Test suite structure
ConferenceFocus
CreateConf CONF_N01_xxx
JoinConf CONF_N02_xxx
InviteToConf CONF_N03_xxx
LeaveConf CONF_N04_xxx
RemoveFromConf CONF_N05_xxx
TerminateConf CONF_N06_xxx

UserEquipment
 CONF_U01_xxx

Interaction
TIR CONF_N08_xxx
OIR CONF_N09_xxx
ACR-CB CONF_N10_xxx

4.2 Configuration
4.2.0 Introduction
The scope of the present document is to test the signalling and procedural aspects of the stage 3 requirements as
described in ETSI TS 124 605 [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.
4.2.1 Testing of the AS
The AS entity is responsible for performing and managing services. The ISC interface is the appropriate access point for
testing.

Figure 4.2-1: Applicable interface to test AS functionalities
If the ISC interface is not accessible it is also possible to perform the test of the AS using any NNI (Mw, Mg, Mx)
interface (see figure 4.2-2). In case only the Gm interface is accessible this interface can be used instead for testing, but
the verification of all requirements may not be possible.
ETSI

---------------------- Page: 7 ----------------------
8 ETSI TS 186 010-2 V4.1.1 (2017-12)

Figure 4.2-2: Applicable interfaces for tests using a (generic) NNI interface
4.2.2 Testing of the UE
There are special clauses in the protocol standard describing the procedures that apply at the originating and terminating
user equipment. Therefore the test configuration in figure 4.2-3 has been chosen.

Figure 4.2-3: Applicable configuration to test UE functionalities
5 Test Purposes (TP)
5.1 Introduction
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 5.1-1).
Table 5.1-1: 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)

ETSI

---------------------- Page: 8 ----------------------
9 ETSI TS 186 010-2 V4.1.1 (2017-12)
5.1.2 Test strategy
As the base standard ETSI TS 124 605 [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 ETSI TS 186 010-1 [3].
5.2 Signalling requirements
5.2.1 Conference Focus
5.2.1.1 Conference creation
TSS TP Reference Selection expression
ConferenceFocus/CreateConf CONF_N01_001 5.3.2.3.1, 5.3.3 [2] PICS 4.5.1/2
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). In addition the conference participant
subscribes to the conference event package and receives a NOTIFY request describing the conference status.
SIP header values:
INVITE: Request URI indicating the conference factory URI
200 OK: conference URI and "isfocus" feature parameter included in Contact header field
SUBSCRIBE: Request URI indicating 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/CreateConf CONF_N01_002 5.3.2.3.1 [2] PICS 4.5.1/2
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 does not
subscribe to the conference event package.
SIP header values:
INVITE:  Request URI indicating the conference factory URI
200 OK:  conference URI and "isfocus" feature parameter included in 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 V4.1.1 (2017-12)
TSS TP Reference Selection expression
ConferenceFocus/CreateConf CONF_N01_003 5.3.2.3.2, 5.3.3 [2] PICS 4.5.1/2
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). In addition the conference participant subscribes
to the conference event package and receives a NOTIFY request describing the conference status.
SIP header values:
INVITE: Request URI indicating the conference URI
200 OK: "isfocus" feature parameter included in Contact header field
conference URI contained in the Contact header field
SUBSCRIBE: Request URI indicating 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
5.3.2.3.2 [2]
CONF_N01_004 PICS 4.5.1/2
ConferenceFocus/CreateConf
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 does not subscribe to
the conference event package.
SIP header values:
INVITE: Request URI indicating 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: 10 ----------------------
11 ETSI TS 186 010-2 V4.1.1 (2017-12)
TSS TP Reference Selection expression
ConferenceFocus/CreateConf CONF_N01_005 5.3.2.3.1 [2] PICS 4.5.1/2
AND PICS 4.7.1/4
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).
SIP header values:
INVITE: Request URI indicating 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 included in Contact header field
  conference URI contained in the Contact header field
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/CreateConf CONF_N01_006 5.3.2.3.1 [2] PICS 4.5.1/2
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 a 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 indicating a conference factory URI not allocated in the focus
Comments:
ISC#1 Focus
INVITE
488 Not Acceptable Here

ACK

ETSI

---------------------- Page: 11 ----------------------
12 ETSI TS 186 010-2 V4.1.1 (2017-12)
5.2.1.2 Joining a conference
TSS TP Reference Selection expression
5.3.2.4.1 [2]
ConferenceFocus/JoinConf CONF_N02_001 PICS 4.5.1/2
Test purpose
Participant dial-in the conference, the conference URI is used.

UE1 (via ISC#1) established a conference. UE2 (via ISC#2) joins in that conference by sending an INVITE request
to the conferencing AS (the conference URI is known at the UE2). The request is successful.
SIP header values:
INVITE 2: Request URI indicating the conference URI
18x "isfocus" feature parameter included in Contact header field
200 OK: "isfocus" feature parameter included 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

UE#2 joining in the conference

 INVITE INVITE 2
 18x 18x
 200 OK INVITE 200 OK INVITE

 ACK ACK
Apply post test routine

TSS TP Reference Selection expression
5.3.2.4.1 [2]
ConferenceFocus/JoinConf CONF_N02_002 PICS 4.5.1/2
Test purpose
Participant dial-in the conference, the conference URI is not allocated, the request is rejected.

UE2 (via ISC#2) tries to join in a conference but 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: Request URI contained the conference URI not allocated in the focus (PIXIT)
Comments:
ISC#1 Focus ISC#2
UE#2 joining in the conference

 INVITE INVITE 2
 4xx 4xx
 ACK ACK

ETSI

---------------------- Page: 12 ----------------------
13 ETSI TS 186 010-2 V4.1.1 (2017-12)
5.2.1.3 Inviting other users to a conference
TSS TP Reference Selection expression
5.3.2.5.2, 5.3.2.5.4 [2]
ConferenceFocus/InviteToConf CONF_N03_001 PICS 4.5.1/2
AND PICS 4.7.1/2
Test purpose
Inviting participant by sending REFER to the focus.

UE1 (via ISC#1) established a conference and invites UE2 (connected via ISC#2) to join into the conference. UE1
sends a REFER to the focus; the focus sends an INVITE request to UE2 to invite it to the conference.
SIP header values:
REFER: Request URI indicating the conference URI
  Refer-To contains the URI of UE2, method=INVITE
  Referred-By contains SIP URI of UE1
INVITE 2: Request URI indicating the address of UE2
  The P-Asserted-Identity contains the conference URI.
  conference URI and "isfocus" feature parameter indicated in Contact header field
  Referred-By contains SIP or tel URI of UE1
NOTIFY 1 Event contains refer; Subscription-State contains active
  message/sipfrag contains SIP/2.0 100 Trying
NOTIFY 2 Event contains refer; Subscription-State contains terminated
  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
UE#1 invites UE#2 to the conference
REFER REFER
2xx REFER 2xx REFER

Focus dials out to invite UE#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: 13 ----------------------
14 ETSI TS 186 010-2 V4.1.1 (2017-12)
TSS TP Reference Selection expression
ConferenceFocus/InviteToConf CONF_N03_002 5.3.2.5.3, 5.3.2.5.4 [2] PICS 4.5.1/2
AND PICS 4.7.1/3
Test purpose
Inviting participant by sending a participant list to the focus.

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

INVITE 2: Request URI = UE#2
  The P-Asserted-Identity contains the conference URI.
  conference URI and "isfocus" feature parameter indicated in 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 UE#2

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

ETSI

---------------------- Page: 14 ----------------------
15 ETSI TS 186 010-2 V4.1.1 (2017-12)
TSS TP Reference Selection expression
ConferenceFocus/InviteToConf CONF_N03_004 5.3.1.3.3, 5.3.1.5.2 [2] PICS 4.5.1/2
AND PICS 4.7.1/2
Test purpose
Three-way session creation. REFER is sent to the participants.

Ensure that it is possible that two active sessions S1 and S2 towards UE2 (via ISC#2) and UE3 (via ISC#3) are
joined in a three way session by UE1 and that the existing sessions S1 and S2 can be released by the served user
UE1. The remote users receive a REFER request with the Refer-To header containing the address of the Focus
directly from UE1. 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=UE#2
  Refer-To=Focus; method=INVITE
  Referred-By=UE#1
REFER (S2): Request line=UE#3
  Refer-To=Focus; method=INVITE
  Referred-By=UE#1
INVITE (S4): Request URI=Focus
  Referred-By=UE#1
INVITE (S5): Request URI=Focus
  Referred-By=UE#1
Comments:
ISC#1 Focus ISC#2 ISC#3

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

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


REFER (S1) REFER
2xx REFER  2xx REFER


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


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

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

BYE (S1)  BYE (S1)
200 OK (BYE)  200 OK (BYE)


REFER (S2)  REFER
2xx REFER   2xx REFER

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

 INVITE  INVITE (S5)
 200 OK (INVITE)  200 OK (INVITE)

 ACK ACK
NOTIFY (200)   NOTIFY (200)
200 OK (NOTIFY)   200 OK (NOTIFY)

BYE (S1)   BYE (S2)
200 OK (B
...