<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Courier New";}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-GB link=blue vlink=purple><div class=WordSection1><pre>Hi Ross,<o:p></o:p></pre><pre>> Huh? If your RTSP server is "based on testOnDemandRTSPServer", then it most certainly *is* 'starting' both RTP and RTCP. That's what a unicast RTSP server does. You seem very confused here.<o:p></o:p></pre><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'>>But the issue here is your *client*. It is apparently not sending back periodic RTCP "RR" (Reception Report) packets in response to the RTP packets that it's receiving from the server. That's why the server is timing out the stream<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I’ve talked to the developers of the NVR software (our client) and they tell me they do send regular RTCP reports, but they don’t send GET_PARAMETER messages like VLC does. However, my streams don’t keep alive and I don’t see their RTCP report messages coming in.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>When I look at testOnDemandRTSPServer, I don’t see any specify RTCPInstance:createNew() call, that’s why I thought RTCP wasn’t running. I guess you’re saying that RTCP and RTP are implicit in UNICAST RTSP. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Where can I put some debug to catch the RTCP reports coming in? I enabled the debug in RTSPServer::RTSPClientSession:: handleRequestBytes() after parseRTSPRequestString(), but I don’t see the RTCP messages there.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks for your help - David<o:p></o:p></p></div></body></html>