So the RTCP liveness indicator is only based on the port found in Transport parameter of the SETUP response?<br><br>Fan<br><br><div class="gmail_quote">2010/4/27 Ross Finlayson <span dir="ltr"><<a href="mailto:finlayson@live555.com">finlayson@live555.com</a>></span><br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
We use openRTSP to test our video server timeout, openRTSP is able to send RTCP<br>
"RR" to the server to maintain the session but it does not use the good port<br>
that it's indicated in SETUP response. RTCP is defined in RTSP response from the server with the following:<br>
a=rtcp:5000 IN IP4 "@IP"<br>
</blockquote>
<br></div>
Unfortunately we do not yet support the "a=rtcp:" attribute defined by RFC 3605.<br>
-- <br><font color="#888888">
<br>
Ross Finlayson<br>
Live Networks, Inc.<br>
<a href="http://www.live555.com/" target="_blank">http://www.live555.com/</a><br>
_______________________________________________<br>
live-devel mailing list<br>
<a href="mailto:live-devel@lists.live555.com" target="_blank">live-devel@lists.live555.com</a><br>
<a href="http://lists.live555.com/mailman/listinfo/live-devel" target="_blank">http://lists.live555.com/mailman/listinfo/live-devel</a><br>
</font></blockquote></div><br>