C.10 Generic test procedure for MTSI conference creation – EPS
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-7a) UE creates the voice conference. The same message sequence as in steps 2 – 8 of Annex C.21 are used to create the conference into the conference focus and negotiate the media.
8) SS responds to the INVITE request with valid 200 OK response.
9) SS waits for the UE to send an ACK to acknowledge receipt of the 200 OK for INVITE.
10) SS waits the UE to optionally subscribe to the conference event package with a SUBSCRIBE message
11) If UE sent SUBSCRIBE, SS responds to it with 200 OK response.
12) If UE sent SUBSCRIBE, SS sends a NOTIFY for the conference event package to the UE.
13) If SS sent a NOTIFY, SS waits the UE to respond the NOTIFY with 200 OK.
Expected sequence
|
Step |
Direction |
Message |
Comment |
|
|
UE |
SS |
|||
|
1 |
Make the UE attempt an IMS Conference call |
|||
|
2-7a |
Steps 2-8 of Annex C.21 |
The same messages as in steps 2 – 8 of Annex C.21 |
||
|
8 |
🡨 |
200 OK |
The SS responds INVITE with 200 OK and gives the final conference URI within the response |
|
|
9 |
🡪 |
ACK |
The UE acknowledges the receipt of 200 OK for INVITE |
|
|
EXCEPTION: steps 10 – 13 describe optional behaviour depending on UE configuration. The SS shall wait up to 3s for the SUBSCRIBE of step 10 |
||||
|
10 |
🡪 |
SUBSCRIBE |
UE subscribes the conference event |
|
|
11 |
🡨 |
200 OK |
SS responds to the subscription |
|
|
12 |
🡨 |
NOTIFY |
SS sends the initial state of the conference event to the UE |
|
|
13 |
🡪 |
200 OK |
UE responds to the NOTIFY |
|
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 1 – 7a is otherwise identical to what have been specified in Annex C.21, but with the exceptions as below:
INVITE (Step 2)
|
Header/param |
Value/remark |
|---|---|
|
Request-Line |
|
|
Request-URI |
sip:mmtel@conf-factory appended with px_IMS_HomeDomainName |
|
To |
|
|
addr-spec |
sip:mmtel@conf-factory appended with px_IMS_HomeDomainName |
183 Session in Progress for INVITE (Step 4)
|
Header/param |
Value/remark |
|---|---|
|
Contact |
|
|
addr-spec |
sip:temporary@conf-factory. appended with px_IMS_HomeDomainName |
|
feature-param |
isfocus |
|
Record-Route |
|
|
rec-route |
<sip:SS P-CSCF address: protected server port of SS;lr> |
200 OK for INVITE (Step 8)
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 183 response |
|
Contact |
|
|
addr-spec |
sip:final@conf-factory. appended with px_IMS_HomeDomainName |
|
feature-param |
Isfocus |
ACK (Step 9)
Use the default message “ACK” in annex A.2.7 with the following exceptions:
|
Header/param |
Value/remark |
|---|---|
|
Request-Line |
|
|
Request-URI |
sip:final@conf-factory. appended with px_IMS_HomeDomainName |
SUBSCRIBE (Step 10)
Use the default message “SUBSCRIBE for conference event package” in annex A.5.1
200 OK (Step 11)
Use the default message “200 OK for SUBSCRIBE” in annex A.5.2
NOTIFY (Step 12)
Use the default message “MT NOTIFY for conference event package” in annex A.5.3 with condition A3
200 OK (Step 13)
Use the default message “200 OK for other requests than REGISTER or SUBSCRIBE” in annex A.3.1.