<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-cite-prefix">On 30-05-15 07:34, Ross Finlayson
wrote:<br>
</div>
<blockquote
cite="mid:5F7FFE33-0F51-49B2-AEB0-DA2071D87584@live555.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<div>
<blockquote type="cite" class="">
<div class="">
<div bgcolor="#FFFFFF" text="#000000" class="">In my
situation, I have multiple cameras with a unique ip
address and port number, but the remaining url could be
the same as another camera. When using the proxy server I
can register both back-end urls but not at different ports
(because only one port is used when creating the
RTSPServerWithREGISTERProxying object).</div>
</div>
</blockquote>
<div><br class="">
</div>
I’m not sure I understand what you’re referring to here, but I
suspect that you may be confused about which port numbers are
used where. The proxy server’s port number is the port number
that 'front-end clients use when communicating with the proxy
server. However, the port number that’s used by the ‘back-end’
stream is the one that’s mentioned (either implicitly or
explicitly) in the “<a moz-do-not-send="true" href="rtsp://%93"
class="">rtsp://“</a> URL that you register with the proxy
server. (By default, this port number - if it’s not included
explicitly in the “<a moz-do-not-send="true" href="rtsp://%93"
class="">rtsp://“</a> URL - is 554, but if can be any other
port number.) Or alternatively, if you use the ‘REGISTER’
mechanism asking to reuse the TCP connection, then the
‘back-end’ stream’s port number will be whatever ephemeral port
number was used to receive the ‘REGISTER’ command . In either
case, this port number (which can be different for different
‘back-end’ streams) is completely independent of whatever port
number is used by the proxy server.</div>
<div><br class="">
</div>
<div>
<div class="">Ross Finlayson</div>
<div apple-content-edited="true" class=""><span
class="Apple-style-span" style="border-collapse: separate;
border-spacing: 0px;">Live Networks, Inc.<br class="">
<a moz-do-not-send="true" href="http://www.live555.com/"
class="">http://www.live555.com/</a></span></div>
</div>
<div><br class="">
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
live-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:live-devel@lists.live555.com">live-devel@lists.live555.com</a>
<a class="moz-txt-link-freetext" href="http://lists.live555.com/mailman/listinfo/live-devel">http://lists.live555.com/mailman/listinfo/live-devel</a>
</pre>
</blockquote>
Hi Ross,<br>
<br>
Thank you for your answer. Maybe I can explain it a bit more with an
example.<br>
<br>
Old situation: Clients directly connect to different back-end
streams (i.e. cameras). Suppose we have two cameras with the
following url:<br>
Camera 1: rtsp://192.168.1.1:1234/camera_stream_1<br>
Camera 2: rtsp://192.168.1.2:4567/camera_stream_2<br>
<br>
New situation: Clients connect through a proxy server with the
back-end streams. Suppose the proxy server is started and both urls
are registered. When instantiating the proxy server the proxy port
is specified at 7621:<br>
RTSPServerWithREGISTERProxying::createNew(*env, 7621, NULL,
NULL, 65, False, verbosityLevel)<br>
<br>
For the back-end streams the clients have to play either the url
rtsp://172.16.1.1:7621/camera_stream_1 or
rtsp://172.16.1.1:7621/camera_stream_2. There is only a difference
in the url suffix, not in the used port (both are 7621).<br>
<br>
The problem is, I have cameras in my network which have the same url
suffix (camera_stream_equal). How can I distinguish (from a clients
point of view) between these cameras? I guess the only way to make a
difference is to give both cameras a unique url suffix when
registering?<br>
<br>
<br>
<div class="moz-signature">-- <br>
<div itacorner="6,7:1,1,0,0" tabindex="1" style="direction: ltr;
min-height: 380px;" role="textbox" g_editable="true" id=":fg"
class="Am Al editable LW-avf" hidefocus="true"
aria-label="Message Body" contenteditable="true"><br clear="all">
<div>
<div class="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div dir="ltr">
<div><font color="#444444" face="arial,
sans-serif">Met vriendelijke groeten /
With kind regards,<br>
<br>
</font></div>
<div><font color="#444444" face="arial,
sans-serif"><b>Frank van Eijkelenburg</b>
Lead Designer</font></div>
<div><font face="arial, sans-serif"><br>
</font></div>
<div><span
style="font-family:arial,sans-serif;line-height:1.5;background-color:transparent"><b><font
color="#999999">T</font></b> <font
color="#444444">+31(0)182594000</font>
<font color="#ffd966">|</font> <font
color="#999999"><b>E</b></font> <font
color="#444444"><a class="moz-txt-link-abbreviated" href="mailto:frank.van.eijkelenburg@technolution.nl">frank.van.eijkelenburg@technolution.nl</a></font></span></div>
<div><b
style="font-family:arial,sans-serif;line-height:1.5;background-color:transparent"><font
color="#999999">A</font></b><span
style="font-family:arial,sans-serif;line-height:1.5;background-color:transparent">
<font color="#444444">Burgemeester
Jamessingel 1, P.O. Box 2013, 2800 BD
Gouda, The Netherlands</font> <font
color="#ffd966">|</font> </span><font
style="font-family:arial,sans-serif;line-height:1.5;background-color:transparent"
color="#999999"><b>W</b></font><span
style="font-family:arial,sans-serif;line-height:1.5;background-color:transparent">
<font color="#444444">technolution.com</font></span></div>
<div><font face="arial, sans-serif"><br>
</font></div>
<div><font color="#444444" face="arial,
sans-serif" size="1">This e-mail is
intended exclusively for the
addressee(s), and may not be
passed on to, or made available for use
by any person other than the
addressee(s). Technolution B.V. rules
out any and every liability
resulting from any electronic
transmission.</font></div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>