C.10a Generic test procedure for MTSI conference creation – WLAN access to EPC

34.229-13GPPInternet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP)Part 1: Protocol conformance specificationRelease 16TSUser Equipment (UE) conformance specification

The generic test procedure for creating MTSI conference may be performed after successful IMS or early IMS registration

Test procedure

1) UE attempts to make conference call.

2-3) UE creates the voice conference. The same message sequence as in steps 2 – 3 of Annex C.21a are used to create the conference into the conference focus and negotiate the media.

4-9) SS and UE complete the creation of the voice conference. The same message sequence as in steps 8-13 of Annex C.10 is used to complete the voice conference.

Expected sequence

Step	Direction		Message	Comment
	UE	SS
1			Make the UE attempt an IMS Conference call
2-3			Steps 2-3 of Annex C.21a	The same messages as in steps 2 – 3 of Annex C.21a
4-9			Steps 8-13 of Annex C.10	The same messages as in steps 8 – 13 of Annex C.10

NOTE: The default messages contents in annex A are used with condition “IMS security“ or “early IMS security” when applicable

Specific Message Contents

The specific message contents for steps 2-3 is otherwise identical to what have been specified in Annex C.25a and for steps 4-9 is otherwise identical to what have been specified in Annex C.10, but with the exceptions as below:

200 OK for INVITE (Step 4)

Use the default message “200 OK for other requests than REGISTER or SUBSCRIBE” in annex A.3.1 with the following exceptions:

Header/param	Value/remark
Record-Route
rec-route	Same value as in the 180 response
Contact
addr-spec	sip:final@conf-factory. appended with px_IMS_HomeDomainName
feature-param	Isfocus
Require option-tag	precondition
Message-body	same SDP types and values as for C.21a Step 4 (180 Ringing)