<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 15 (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:DengXian;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"\@DengXian";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
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;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
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-SG" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<pre><span style="color:black">> For unicast streams like this, it is the RTSP client that chooses the destination port number for RTP packets. In particular, the "LIVE555 Proxy Server” - which acts as a RTSP client for each ‘back-end’ RTSP server (e.g., IP camera) - chooses the destination RTP port number for each stream, and it will always choose a different port number for each stream. You should be able to see this by looking at the RTSP protocol exchange for each ‘back-end’ stream, which you can see by running “live555ProxyServer” with the -V flag (note the “client_port=“ in each RTSP SETUP request from the proxy server).<o:p></o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black">> It appears that your intermediate “UP-Squared” boxes are likely responsible for your problem; it seems that they are remapping the port number of incoming RTP packets (from the back-end IP camera) to 5004. You will need to disable this functionality in your “UP-Squared” boxes. (Or, alternatively, remove your “UP-Squared” boxes entirely, and change your server so that it acts a a gateway, and is aware of both IP subnets.)<o:p></o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black">> In short, this is a problem with your networking setup, not a problem with the LIVE555 software.<o:p></o:p></span></pre>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hi Ross,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks for the prompt and detailed reply!<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I have checked through the data packets via Wireshark and it looks to me that the RTSP exchange between the server and the UP2 indicates that the live555proxyserver sent out a RTSP SETUP Request with client_port=5004-5005 on each instance.
I have tried using datastead to stream directly from the camera via the UP2 and for the multiple instances I have attempted, the client_port has always been different between the server and the UP2 for both UDP and TCP. Any chance that this could be a live555
problem when it comes to RTP over UDP?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:black">Thanks!</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.75pt;text-autospace:none"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Regards,<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.75pt;text-autospace:none"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Han Hao<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.75pt;text-autospace:none"><b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><br>
<br>
</span></b><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
This email is confidential and may also be privileged. If this email has been sent to you in error, please delete it immediately and notify us. Please do not copy, distribute, or disseminate part or whole of this email if you are not the intended recipient
or if you have not been authorized to do so. We reserve the right, to the extent and under circumstances permitted by applicable laws, to retain, monitor, and intercept email messages to and from our systems. Thank you.
</body>
</html>