<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div><blockquote type="cite"><div dir="ltr"><div>2. Registered the single back-end server (works as expected; using new transport header options) . BTW, the option for setting suffix is a nice additon!</div></div></blockquote><div><br></div>FYI, you can now use our new application "registerRTSPStream" (in the "testProgs" directory) for this.</div><div><br></div><div><br><blockquote type="cite"><div dir="ltr"><div>3. Connected a single client (VLC) to record the proxy stream to file. (Connects fine and I see debug output recording the connection)</div><div><br></div><div>4. Connect another client (VLC) to proxy stream to record a second file. (Connects fine, but I do not see any debug output showing this connection???)</div></div></blockquote><div><br></div>That's normal, and expected. What's important to understand is that the diagnostic output generated by the "LIVE555 Proxy Server" (when you give it the "-V" option) is only for the proxying functionality (between the proxy server and the back-end server). Proxying starts (by sending "SETUP" and "PLAY" commands) once the first front-end client connects, and stops (by sending a "PAUSE" command) once the last front-end client disconnects. During that time, the proxy server will continue to serve an arbitrary number of connecting/disconnecting front-end clients, but won't have any effect on the connection between the proxy server and the back-end server - until the last front-end client disconnects. That's why you don't see any additional diagnostic output when the second front-end client connects - but data will still be streamed to that front-end client, as expected.</div><div><br></div><div><br><blockquote type="cite"><div dir="ltr"><div>I have attached a debug file that reflects steps (1-6). If you could take a quick look to see if there something obvious that would be great.</div></div></blockquote><div><br></div>Your file looks OK; the proxy server appears to be working normally.</div><div><br></div><div>Once again, what I suspect is happening is that when you have N>1 front-end clients, you are experiencing some packet loss (because, in this case, each outgoing RTP packet from the proxy server is being transmitted N separate times (once to each front-end client)). And apparently your stream recording software is not tolerant of data loss. You can verify this by instead running "openRTSP" with the "-Q" (report QOS) option as your front-end clients.</div><br><br><div apple-content-edited="true">
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; ">Ross Finlayson<br>Live Networks, Inc.<br><a href="http://www.live555.com/">http://www.live555.com/</a></span></span>
</div>
<br></body></html>