3.1.5.3 Receiving a RTSP response

The client MUST process the RTSP response in accordance with the rules in [DLNA] guideline 7.4.210.

If the response is to a SETUP request, the Transport header SHOULD be parsed according to section 2.2.3.4. The value of the ssrc token on the Transport header SHOULD be added to the Ssrc-list variable such that a mapping is established between the ssrc value and the stream referenced in the SETUP request. If the rtcp-fb-ssrc token is present on the Transport header, then the value of that token SHOULD be added to the Ssrc-list variable such that a mapping is established between the rtcp-fb-ssrc value and the stream referenced in the SETUP request.

The client MUST now continue with standard RTSP and RTP protocol usage. Standard RTSP and RTP protocol usage involves processing additional RTSP responses, processing ANNOUNCE requests, processing RTP packets and RTCP packets, as specified in [DLNA] and [RFC2326]. The following Microsoft Extensions apply:

  • For any additional RTSP response that is received, the rules in the current section MUST be followed.

  • When RTP packets are received, the rules in section 3.1.5.4 MUST be followed.

  • If an ANNOUNCE request is received, the rules in section 3.1.5.5 MUST be followed.

The client MUST also be prepared for a higher layer to request a DLNA Media Operation, as specified in section 3.1.4.3.