Robert:
> where does the relayconfig.xml file exist? I'm using QTSS in OS X
> 10.3.3, and the relay configuration in ServerAdmin.
That's in /Library/QuickTimeStreaming/Config on Mac OS X. Using the
Server Admin gui app or the web gui changes the contents of the xml
config files. There is a sample file for relays in that directory you
might want to look at:
relayconfig.xml-Sample
> It asks for a source, I entered:
>
> Relay Name: Test
> Relay Type: Request Incoming Stream
> Source IP: 63.100.142.111
> Path: /now.jpg?snap=spush
>
> For the Destination, I did:
>
> Destination IP Address: IP address of the machine running the QTSS
> Destination Type: Unannounced UDP
> UDP Base Port Number: 5000 (default)
> Multicast Time to live: 16 (default)
>
> How do these entries correlate to your configuration in the XML file?
> Is there any thing you can (I NEED) to specify in the XML that can't
> be specified from the GUI?
What you set up will create an entry like the following in
relayconfig.xml:
<OBJECT TYPE="relay" NAME="Test">
<OBJECT CLASS="source" TYPE="rtsp_source">
<PREF NAME="source_addr">63.100.142.111</PREF>
<PREF NAME="url">/now.jpg?snap=spush</PREF>
</OBJECT>
<OBJECT CLASS="destination" TYPE="udp_destination">
<PREF NAME="ttl">16</PREF>
<PREF NAME="dest_addr">IP address of the machine running the
QTSS</PREF>
<PREF NAME="udp_base_port">5000</PREF>
</OBJECT>
<PREF NAME="enabled">true</PREF>
</OBJECT>
Using this method, you would have to hand edit an sdp file on the
server. This file would direct clients to the destination of your
relay.
You can also select an "announced udp" destination. This will
automatically create the sdp file on the server for you (BTW I usually
use the 127.0.0.1 when setting the destination of a relay to the same
server QTSS is running on). There is no need to use a username/password
when creating an announced udp destination and using 127.0.0.1. If you
target a different server, you'll need to use the broadcast password
for that server (unless you have it configured for unrestricted
broadcasting). When I tried this with your camera the sdp file gets
created (step in the right direction). However, when I try tuning in on
it I just get "connecting" - which makes me suspect that the server is
having trouble tuning in on the stream and reflecting it. Announced sdp
files will be deleted if the server can't access the source - and this
is what happens with the camera as a source. So, something isn't right
here...
> I don't see a place in the GUI for the rtsp_port on the source. What
> exactly is the Base Port Number?
There are options that aren't supported in the gui. See the example
file for more information.
The base port is the port number corresponds to the rtp ports the
server will use. In the sdp file, these ports are listed in the lines
beginning with "m=". The reason it is referred to as a base port is
that QTSS will automatically increment the port number by 2 for
additional tracks. For instance, the destination I sent before:
<OBJECT CLASS="destination" TYPE="udp_destination">
<PREF NAME="ttl">5</PREF>
<PREF NAME="dest_addr">239.10.10.101</PREF>
<PREF NAME="url"></PREF>
<PREF NAME="udp_base_port">9600</PREF>
</OBJECT>
Would correspond to an sdp file that looks something like:
v=0
c=IN IP4 239.10.10.101
a=range:npt=0-
a=x-qt-text-nam:IQEYE010761
a=x-qt-text-inf:Live A/V stream
a=x-qt-text-aut:
a=x-qt-text-cmt:opts: snap=spush
m=video 9600 RTP/AVP 26
a=control:trackID=2
a=x-bufferdelay:0
If the stream had additional tracks (i.e. audio) then we would
increment the base port by 2 for every track in the sdp file.
(I tried this BTW and it didn't work either. The same setup works with
other encoders I've used).
Hope this helps...
-George
[demime 0.98b removed an attachment of type application/pkcs7-signature which had a name of smime.p7s]
_______________________________________________
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.
