C.27 Generic test procedure for forked response of MTSI MO speech call – 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

Test procedure:

1) SS responds to the INVITE request with a 183 Session Progress response.

NOTE: Steps 1 to 4 in annex C.21 are performed before this generic test procedure is initiated. This procedure may be performed in parallel with step 5 and later steps in annex C.21.

2) SS waits for the UE to send a PRACK request possibly containing the second SDP offer.

3) SS responds to the PRACK request with a 200 OK.

4) SS waits for the UE to send a UPDATE request containing the final SDP offer.

5) SS responds to the UPDATE request with a 200 OK.

6) SS responds to the INVITE request with a 180 Ringing.

7) SS waits for the UE to send a PRACK request.

8) SS responds to the PRACK request with a 200 OK.

Expected sequence:

Step

Direction

Message

Comment

UE

SS

1

🡨

183 Session Progress

SS sends an SDP answer.

2

🡪

PRACK

UE acknowledges and optionally offer a second SDP if a dedicated EPS bearer is established by the network.

3

🡨

200 OK

SS sends a 200 OK and answers the second SDP if present.

4

🡪

UPDATE

Optional step: UE sends a second SDP if a dedicated EPS bearer is established by the network.

5

🡨

200 OK

Optional step: SS sends a 200 OK.

6

🡨

180 Ringing

SS sends a 180 Ringing.

7

🡪

PRACK

UE acknowledges.

8

🡨

200 OK

SS responds PRACK with 200 OK.

Specific Message Contents

183 Session Progress (Step 1)

Use the "183 Session Progress (Step 4)" in annex C.21 with the following exceptions:

Header/param

Value/remark

To

tag

different value from common to-tag (invite)

Message-body

o=- 1111111112 1111111111 IN (addrtype) (unicast-address for SS)

PRACK (Step 2)

Use the "PRACK (Step 5)" in annex C.21 with the following exceptions:

Header/param

Value/remark

To

tag

same value as used in step 1

Message-body

Header optional

Contents if present: The following SDP types and values shall be present.

Session description:

– o=(username) (sess-id) (sess-version) IN (addrtype) (unicast-address for UE) [Note1]

Note 1: "o=" line identical to previous SDP sent by UE in the same dialog, except that sess-version is incremented by one if the SDP is not identical to the previous SDP sent by the UE

200 OK for PRACK (Step 3)

Use the "200 OK for PRACK (Step 6)" in annex C.21 with the following exceptions:

Header/param

Value/remark

To

tag

same value as used in step 1

UPDATE (Step 4)

Use the "UPDATE (Step 7)" in annex C.21 with the following exceptions:

Header/param

Value/remark

To

tag

same value as used in step 1

200 OK for UPDATE (Step 5)

Use the "200 OK for UPDATE (Step 8)" in annex C.21 with the following exceptions:

Header/param

Value/remark

To

tag

same value as used in step 1

180 Ringing (Step 6)

Use the default message "180 Ringing for INVITE" in annex A.2.6 with the following exceptions:

Header/param

Value/remark

To

tag

same value as used in step 1

PRACK (Step 7)

Use the default message "PRACK" in annex A.2.4 with the following exceptions:

Header/param

Value/remark

To

tag

same value as used in step 1

200 OK for PRACK (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

To

tag

same value as used in step 1