Alan:
Hmmm. I have this working in a lab as follows:
"Master QTSS Relay" is configured with IP 192.168.0.150. It has a
default relay configured to send to "Slave QTSS Relay" at
192.168.0.200. It is important that this relay is configured to use TCP
and that a valid broadcast username and password is specified. You can
test by using QT Broadcaster to send a stream directly to the Slave
QTSS Server using the same username and password. The enclosed file
SafariScreenSnapz001.jpg has a picture of the default relay.
[demime 0.98b removed an attachment of type multipart/appledouble]
The Slave Relay must be configured for a specific .sdp file - use the
same file name you specify in the File: field of QT Broadcaster. In my
case this is 001.sdp. The slave Relay is configured as shown in file
SafariScreenSnapz002.jpg.
[demime 0.98b removed an attachment of type multipart/appledouble]
Broadcaster is configured to broadcast to the Master Server via TCP
announced broadcast as shown in file broadcaster001.jpg.
[demime 0.98b removed an attachment of type image/jpeg which had a name of broadcaster001.jpg]
At this point, I can tune in on either:
rtsp://192.168.0.150/001.sdp
-OR-
rtsp://192.168.0.200/001.sdp
BOTH of these are Unicast streams. To tune in on a multicast, I have to
edit the sdp file. In this test cast I was only streaming video. On the
Slave Server I copied the 001.sdp file to 001-m.sdp. In the copied file
I edited the c= line to match the multicast IP address (239.1.1.1) and
the m= line to match the port number (9016).
Here is the file 001.sdp:
a=x-qt-text-nam:001
a=x-qt-text-cpy:Apple
a=x-qt-text-aut:George Cook
a=x-qt-text-inf:Multicast Streaming Channel 1
a=mpeg4-iod:"data:application/mpeg4-iod;base64,AoF/
AE8BAQEBAQOBEgABQHRkYXRhOmFwcGxpY2F0aW9uL21wZWc0LW9kLWF1O2Jhc2U2NCxBVGdC
R3dVZkF4Y0F5U1FBWlFRTklCRUFGM0FBQVBvQUFBRERVQVlCQkFFWkFwOERGUUJsQlFRTlFC
VUFCOUFBQUQ2QUFBQStnQVlCQXc9PQQNAQUAAMgAAAAAAAAAAAYJAQAAAAAAAAAAA2EAAkA+
ZGF0YTphcHBsaWNhdGlvbi9tcGVnNC1iaWZzLWF1O2Jhc2U2NCx3QkFTZ1RBcUJYSmhCSWhR
UlFVL0FBPT0EEgINAAAUAAAAAAAAAAAFAwAAQAYJAQAAAAAAAAAA"
a=isma-compliance:1,1.0,1
a=control:*
c=IN IP4 192.168.0.200
m=video 0 RTP/AVP 96
a=rtpmap:96 MP4V-ES
a=fmtp:96
profile-level-
id=1;config=000001B0F3000001B50EE040C0CF0000010000000120008440FA285020F0
A31F
a=mpeg4-esid:201
a=cliprect:0,0,240,320
a=control:trackid=1
Here is the edited file 001-m.sdp
a=x-qt-text-nam:001
a=x-qt-text-cpy:Apple
a=x-qt-text-aut:George Cook
a=x-qt-text-inf:Multicast Streaming Channel 1
a=mpeg4-iod:"data:application/mpeg4-iod;base64,AoF/
AE8BAQEBAQOBEgABQHRkYXRhOmFwcGxpY2F0aW9uL21wZWc0LW9kLWF1O2Jhc2U2NCxBVGdC
R3dVZkF4Y0F5U1FBWlFRTklCRUFGM0FBQVBvQUFBRERVQVlCQkFFWkFwOERGUUJsQlFRTlFC
VUFCOUFBQUQ2QUFBQStnQVlCQXc9PQQNAQUAAMgAAAAAAAAAAAYJAQAAAAAA
AAAAA2EAAkA+ZGF0YTphcHBsaWNhdGlvbi9tcGVnNC1iaWZzLWF1O2Jhc2U2NCx3QkFTZ1RB
cUJYSmhCSWhRUlFVL0FBPT0EEgINAAAUAAAAAAAAAAAFAwAAQAYJAQAAAAAAAAAA"
a=isma-compliance:1,1.0,1
a=control:*
c=IN IP4 239.1.1.1
m=video 9016 RTP/AVP 96
a=rtpmap:96 MP4V-ES
a=fmtp:96
profile-level-
id=1;config=000001B0F3000001B50EE040C0CF0000010000000120008440FA285020F0
A31F
a=mpeg4-esid:201
a=cliprect:0,0,240,320
a=control:trackid=1
NOTE: Each m= line needs to be incremented by 2. Also, use and editor
that generates Unix line endings. With this edited file in place, I can
tune in on the multicast by placing the multicast sdp file on the web
server running on my Slave Server:
http://192.168.0.200/001-m.sdp
NOTE: The mime.types file for Apache on the slave server must have the
.sdp file extension mapped to application/sdp.
So, all this was working, then I stopped the broadcast and tried to
restart. When I did, the relay on the Slave Server didn't show up in
Relay Status (the problem you were having) or would show up, but no new
data would arrive. To fix this I followed these steps when starting a
new broadcast:
1. Edited the relay on the Slave Server. Normally you would have to do
this to specify the correct file name, etc. Then I clicked on Save.
2. Started the broadcast from QT Broadcaster.
3. Copied the sdp file from the Slave Server to a web server (in my
case the same machine). Edited the sdp file to reference the multicast
address and port number as outlined above.
Hope this helps,
-George
> Subject: RE:QTSS4 Multicast Relay Help---Please
> To: email@hidden
> From: email@hidden
> Date: Sat, 18 Jan 2003 21:11:28 -0500
>
> Hi, Goerge/user list. I just wanted to update you...no matter what, I
> cannot get "wait for announced streams" to work on my remote servers.
> The
> SDPs get sent with no problem, but using "Wait for announced..." shows
> no
> activity in the Relay Status panel every time. I have to use "request
> incoming stream" in order for things to work properly. What's more, I
> must
> manually start and stop each relay on the remote machines after I begin
> broadcasting in order to see video at the remote locations. (I use
> Apple
> Remote Desktop to do this)
>
> I don't know if this is a 4.0/4.1 issue, or my setup is flawed...who
> knows.
> But this is what I have to do in order for things to work. Hopefully,
> after I upgrade everything to 4.1, this will clear up. Have you ever
> heard
> of this type of situation before?
>
> Thanks much.
>
> --------------------------------------
> Alan Abrams
> Multimedia Specialist
_______________________________________________
streaming-server-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/streaming-server-users
Do not post admin requests to the list. They will be ignored.
