C.11a Generic test procedure for MTSI MT speech call – 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 setting up MT MTSI speech call may be performed after successful IMS registration over WLAN.

Test procedure

1) SS sends an INVITE request to the UE.

2) SS may receive 100 Trying from the UE.

2A) SS may receive 183 Session Progress from the UE.

2B) SS may send PRACK to the UE to acknowledge the 183 Session Progress.

2C) SS may receive 200 OK for PRACK from the UE.

3) SS may receive 180 Ringing from the UE.

4) SS may send PRACK to the UE to acknowledge the 180 Ringing Progress.

5) SS may receive 200 OK for PRACK from the UE.

5A) The UE accepts the session invite.

6) SS expects and receives 200 OK for INVITE from the UE, with optionally proper SDP as answer.

7) SS sends ACK to the UE.

Expected sequence

Step

Direction

Message

Comment

UE

SS

1

🡨

INVITE

SS sends INVITE with the first SDP offer.

2

🡪

100 Trying

(Optional) The UE responds with a 100 Trying provisional response

2A

🡪

183 Session Progress

(Optional) The UE sends 183 response reliably with the SDP answer to the offer in INVITE

2B

🡨

PRACK

(Optional) SS acknowledges the receipt of 183 response from the UE.

2C

🡪

200 OK

(Optional) The UE responds to PRACK with 200 OK

3

🡪

180 Ringing

(Optional) The UE responds to the offer in INVITE with 180 Ringing with the optional SDP answer if SDP answer was not included with 183 Session Progress in step 2A

4

🡨

PRACK

(Optional) SS shall send PRACK only if the 180 response contains 100rel option tag within the Require header.

5

🡪

200 OK

(Optional) The UE responds to PRACK with 200 OK.

SS waits 5 seconds for UE to send 183 Session Progress and/or 180 Ringing or none of the two before proceeding

5A

Make UE accept the speech AMR offer.

6

🡪

200 OK

The UE responds to INVITE with 200 OK and includes SDP answer to acknowledge its current precondition status if SDP answer was not included with 183 Session Progress in step 2A or 180 Ringing in Step 3.

7

🡨

ACK

The SS acknowledges the receipt of 200 OK for INVITE.

NOTE 1: Steps 3, 4, and 5 can happen in parallel to steps 2B and 2C

Specific Message Content

INVITE (Step 1)

Use the default message “INVITE for MT Call” in annex A.2.9 with the following exceptions:

Header/param

Value/remark

Supported

option-tag

precondition

Message-body

The following SDP types and values.

Session description:

– v=0

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

s=-

– c=IN (addrtype) (connection-address for SS)

– b=AS:37

Time description:

– t=0 0

Media description:

– m=audio (transport port) RTP/AVP 97 98 99 100

– b=AS:37

– b=RS:0

– b=RR:2000

Attributes for media:

– a=rtpmap: 97 AMR-WB/16000/1

– a=fmtp: 97 mode-change-capability=2; max-red=220

– a=rtpmap: 98 telephone-event/16000

– a=fmtp: 98 0-15

– a=rtpmap:99 AMR/8000/1

– a=fmtp:99 mode-change-capability=2; max-red=220

– a=rtpmap: 100 telephone-event/8000

– a=fmtp: 100 0-15

– a=ptime:20

– a=maxptime:240

Attributes for preconditions:

– a=curr:qos local sendrecv

– a=curr:qos remote none

– a=des:qos mandatory local sendrecv

– a=des:qos optional remote sendrecv

183 Session Progress (Step 2A)

Use the default message "183 Session Progress" in annex A.2.3 with the following exceptions:

Header/param

Value/remark

Require

option-tag

precondition

Message-body

The following SDP types and values shall be present.

Session description:

– v=0

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

– s=(session name)

– c=IN (addrtype) (connection-address for UE) [Note 1]

– b=AS: (bandwidth-value)

Time description:

– t=0 0

Media description:

– m=audio (transport port) RTP/AVP (fmt)

– c=IN (addrtype) (connection-address for UE) [Note 1]

– b=AS: (bandwidth-value)

– b=RS: (bandwidth-value)

– b=RR: (bandwidth-value)

Attributes for media:

– a=rtpmap: (payload type) AMR-WB/16000 [Note 2]

– a=fmtp:(format)

Attributes for preconditions:

– a=curr:qos local sendrecv

– a=curr:qos remote sendrecv

– a=des:qos mandatory local sendrecv

– a=des:qos mandatory remote sendrecv

Note 1: At least one "c=" field shall be present.

Note 2: The AMR channel number shall be “/1” or omitted.

180 Ringing (step 3)

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

Header/param

Value/remark

Require

option-tag

precondition

Content-Type

Header optional
Contents if present:

media-type

application/sdp

Content-Length

value

length of message-body

Message-body

Optionally present only if there has been no 183 Session Progress with SDP answer at step 2A.

Contents if present: Same as specified in step 2A.

200 OK (step 6)

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

Require

Same contents as specified in step 3.

Message-body

Present if there has been no SDP answer at step 2A or step 3.

Contents if present: Same as specified in step 2A