Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
The client MUST first follow the steps as specified in section 3.1.5.2.
An RTSP status code in the response in the range 300 to 305 indicates that the server is asking the client to connect to another server. The client MUST connect to the server specified in the response by following the rules as specified in [RFC2326] section 11.2. This is a brief summary of those rules: If the status code is 305, the URL on the Location header (as specified in [RFC2326] section 12.25) is for a proxy, and the URL used in the Describe request MUST remain unchanged. For status codes 300 to 304, the URL on the Location header MUST replace the URL used in the Describe request. The server MUST close the current TCP connection and establish a new TCP connection to the server or proxy server, as appropriate, depending on the status code. The client MUST then continue by following the steps, as specified in section 3.1.4.2.1.
If the RTSP status code in the response is 401, then the server requires authentication; if the status code is 407, then the proxy server requires authentication. The rules for access authentication, as specified in [RFC2616] section 11, MUST be followed. When the client is ready to resubmit the Describe request with the authentication challenge, it MUST continue by following the steps defined in section 3.1.4.2.1.<25>
If the RTSP status code indicates that the request succeeded (as specified in [RFC2326] section 11), the client MUST perform the following steps:
The client MUST extract the ASF file header from the SDP (section 2.2.5.2.3.1) and SHOULD make it available to the higher layer. If the SDP contains a content description list (section 2.2.5.2.3.2), it SHOULD also be made available to the higher layer.
If the higher layer allows RTP packets to be streamed over UDP, and the SDP specifies a retransmission stream (section 2.2.5.5), the client SHOULD send a SelectStream request to select that retransmission stream. The SelectStream request MUST specify UDP as the transport protocol.
Otherwise, if the higher layer wants to measure the bottleneck bandwidth on the network path between the server and the client, and the Server-features variable in the abstract data model indicates that the server supports com.microsoft.wm.srvppair (section 2.2.6.10.6), the client MUST send a TcpPacketPair request to the server.
If the value of the SelectStream-request-counter is greater than 0, then it MUST wait for the response to the SelectStream request. How to process the response is specified in section 3.1.5.6.
If the client has sent the TcpPacketPair request, it MUST wait for the response to the TcpPacketPair request. How to process the response is specified in section 3.1.5.5. <26>
Otherwise, the client MUST wait until a higher-layer triggered event occurs. The next higher-layer triggered event is a request to start streaming content, as specified in section 3.1.4.3.