Hello Larry,
We'll be doing further testing with SpamPro
ourselves (at Apple), try to reproduce this same
issue here the lab.
For the near-term, I can't promise anything, but do
know that we're looking into it.
As for the 400 RTSP connections vs. your expected 800 RTP
connections... this is incorrect. The RTP count should
be the same as the RTSP count (even for movies with
multiple tracks, such as audio + video).
You can verify this by connecting a standard QT4.1.2
client to your QTSS server and watching the RTP vs. RTSP
counts (notice that they are both the same, 1 and 1).
Thanks again for providing this additional feedback.
--
Billy Brown
>Billy,
> Well, I had time to try SpamPro with the 2.0.1 Server. As
>instructed, I used the web_stats_url directive to allow monitoring of the
>number of connections. My browser's URL looked like the following:
>
>
>http://qtss.domain.com:554/stats?refresh=5&fields=curtime,currtp,curtsp,thru
>limit
>
>This would display the Current Number of RTP Connections and also the
>Current Number of RTSP Connections. With 400 sessions "playing" according
>to SpamPro, we still get large variations in the connection numbers reported
>within the web browser. Since the movie we are playing contains two RTP
>streams ( audio + video), I would expect the number of RTSP connections to
>be 400 and the number of RTP connections to be 800. At one point, SpamPro
>reported 402 RTSP connections and 314 RTP Connections. After about 5
>minutes, it reported 183 RTSP connections and 155 RTP Connections. Within
>our SpamPro config file, we told it to play for 3600 seconds and the actual
>movie length is around 1 hour 7 minutes. Therefore, unless errors are
>occurring ( none reported in the either error log), we should not see
>anything less than 400 RTSP connections and 800 RTP connections.
>
>Any help you could give us to help isolate the problem further would be
>appreciated.
>
>Thanks,
>Larry Deaton
