C.26b Generic test procedure for Terminating MTSI Video Call – Fixed Broadband 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 MTSI MT video call over Fixed Broadband access may be performed after successful IMS registration.

Test procedure

1) SS sends an INVITE request to the UE.

2) SS may receive 100 Trying from the UE.

3) SS expects and receives 180 Ringing from the UE.

4) SS sends PRACK to the UE to acknowledge the 180 Ringing

5) SS expects and receives 200 OK for PRACK from the UE.

6) The UE accepts the session invite.

7) SS expects and receives 200 OK for INVITE from the UE.

8) SS sends ACK to the UE.

9) SS sends BYE to the UE.

10) SS expects and receives 200 OK for BYE from 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

3

🡪

180 Ringing

(Optional) The UE responds to INVITE with 180 Ringing.(Optional) to have SDP added. If added 180 response is reliably send

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 acknowledges the PRACK with 200 OK.

6

Make the UE accept the video offer.

7

🡪

200 OK

The UE responds to INVITE with a 200 OK final response after the user answers the call.

(Optional) to have SDP added. If not included in 180 response

8

🡨

ACK

The SS acknowledges the receipt of 200 OK for INVITE.

9

🡨

BYE

The SS sends BYE to release the call.

10

🡪

200 OK

The UE sends 200 OK for the BYE request and ends the call.

NOTE: The default messages contents in annex A are used with condition “IMS security” or “early IMS security” and the condition “SIP Digest without TLS for Fixed Broadband Access” when applicable.

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

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:352

Time description:

  • t=0 0

Media description:

  • m=audio (transport port) RTP/AVP 99 100
  • b=AS:37
  • b=RS:0
  • b=RR:2000

Attributes for media:

  • 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

Media description:

– m=video (transport port) RTP/AVPF 101

– b=AS: 315

– b=RS: 0

– b=RR: 2500

Attributes for media:

– a=rtpmap:1019 H264/90000

– a=fmtp: 101 packetization-mode=0;profile-level-id=42e00c; \

sprop-parameter-sets=J0LgDJWgUH6Af1A=,KM46gA==

– a=rtcp-fb:* trr-int 5000

– a=rtcp-fb:* nack

– a=rtcp-fb:* nack pli

– a=rtcp-fb:* ccm fir

– a=rtcp-fb:* ccm tmmbr

180 Ringing (Step 3)

Use the default message "180 Session Progress" in annex A.2.6 with the following exceptions:

Header/param

Value/remark

Content-Type

media-type

application/sdp

Message-body

The following SDP types and values shall be present. [Note 3]

Session description:

  • v=0
  • o=(user-name) (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) [Note 2]
  • 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/8000 [Note 2]
  • a=fmtp:(format) [Note 2]

Media description:

– m=video (transport port) RTP/AVPF (fmt) [Note 2]

– b=AS: (bandwidth-value)

– b=RS: (bandwidth-value)

– b=RR: (bandwidth-value)

Attributes for media:

– a=rtpmap: (payload type) H264/90000 [Note 2]

– a=fmtp: (format) packetization-mode=0;profile-level-id=(att-field); \

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

Note 2: The value for fmt, payload type and format is not checked

Note 3: Parameters for the AMR codec are not checked

200 OK (Step 7)

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

Message-body

Present if SDP answer was not included with 180 Ringing (Step 3)

Contents if present: Same as specified in step 3.