<div class="gmail_quote">2010/9/2 Simon Perreault <span dir="ltr"><<a href="mailto:simon.perreault@viagenie.ca">simon.perreault@viagenie.ca</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On 2010-09-02 10:54, Nicolas Bourbaki wrote:<br>
> my goal is to have, for any video call a well defined path for RTP flow,<br>
> which can be :<br>
> - Client A --> "RTP proxy 1" --> "RTP proxy 2" --> "RTP proxy N" --><br>
> client B<br>
> with "RTP proxy" 1, 2, 3, ... in the same LAN segment (in fact not<br>
> really but it's the best and easiest way to explain our objectives)<br>
><br>
> OpenSIPs + rtpproxy doesn't work very well (can't pass through multiple<br>
> proxy :s)<br>
<br>
</div>Multiple OpenSIPs then?<br></blockquote><div><br><br>I've tried, but does'nt works. RTP packet flow is the following :<br>from A to B : client A --> rtpproxy1 --> client B<br>from B to A : client B --> rtpproxyN --> client A<br>
<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
Simon<br>
<font color="#888888">--<br>
NAT64/DNS64 open-source --> <a href="http://ecdysis.viagenie.ca" target="_blank">http://ecdysis.viagenie.ca</a><br>
STUN/TURN server --> <a href="http://numb.viagenie.ca" target="_blank">http://numb.viagenie.ca</a><br>
vCard 4.0 --> <a href="http://www.vcarddav.org" target="_blank">http://www.vcarddav.org</a><br>
</font><div><div></div><div class="h5"><br>
--<br>
_____________________________________________________________________<br>
-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
<br>
asterisk-dev mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-dev" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-dev</a><br>
</div></div></blockquote></div><br>