Organization: Sasken Communication Technologies Ltd
Hi!
I have been fiddling with the quick time server, specifically its RTSP
module for some time. I have a small curiosity.
As per RFC 2326 section 14.1:
If the SDP file indicates that the "Control URI" for individual media
streams corresponds to different servers, then does the Quick Time
client open separate RTSP session to the corresponding servers .
For convinience I have reproduced the text corresponding to RFC 2326
section 14.1:
The SDP file is:
v=0
o=- 2890844526 2890842807 IN IP4 192.16.24.202
s=RTSP Session
m=audio 0 RTP/AVP 0
a=control:rtsp://audio.example.com/twister/audio.en
m=video 0 RTP/AVP 31
a=control:rtsp://video.example.com/twister/video
C->A: SETUP rtsp://audio.example.com/twister/audio.en RTSP/1.0
CSeq: 1
Transport: RTP/AVP/UDP;unicast;client_port=3056-3057
A->C: RTSP/1.0 200 OK
CSeq: 1
Session: 12345678
Transport: RTP/AVP/UDP;unicast;client_port=3056-3057;
server_port=5000-5001
C->V: SETUP rtsp://video.example.com/twister/video RTSP/1.0
CSeq: 1
Transport: RTP/AVP/UDP;unicast;client_port=3058-3059
V->C: RTSP/1.0 200 OK
CSeq: 1
Session: 23456789
Transport: RTP/AVP/UDP;unicast;client_port=3058-3059;
server_port=5002-5003
(the client the issues separate PLAY requests to each media server for
activating the audio and video streams)
I was also interested in knowing whether the RTSP implementation of the
"mpeg4ip client" supports this feature.
Regards,
Rahul Kumar
PS: Has anyone come accorss such a scenario in actual usage?
