<HTML>
<HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META content="Open WebMail 2.20 20031014" name=GENERATOR>
</HEAD>
<BODY bgColor=#ffffff>
<font size="2">I don't think that's entirely fair. We've seen deployments of rtpproxy with several thousand streams (compared to a few dozen on mediaproxy). The biggest problem, of course, becomes that then you're into the gigabits of bandwidth realm.... which gets pricey.
<br />
<br />The biggest differences between mediaproxy and rtpproxy:
<br />
<br />mediaproxy:
<br />-written in python
<br />-uses DNS srv records to allow you to distribute the load onto multuple servers regionally, geographically, etc.
<br />-has a nifty web interface to let you look at statistics of the server (ongoing streams, etc).
<br />-can't handle a WHOLE lot of streams per box
<br />
<br />rtpproxy:
<br />-written in C
<br />-doesn't handle distribution of load (for this, you'd need to do some tricks with load balancing on your own -- local, or geographical load balancing. Not easy, but possible).
<br />-doesn't have any sort of useful interface to gather information about the server and what it's doing
<br />-handles a LOT of streams on a decently-powered box
<br />
<br />
<br />There are limits to both, of course. You're best off limiting the number of users who require the use of mediaproxy or rtpproxy with some effective coding and standards (in reality, the ONLY people who should be using it are people who are connecting via a symmetric NAT) to avoid bottlenecks.
<br />
<br />Like ANY thing else in the massive deployment world, there is always a bottleneck in any SIP scenario, but also like any other massive deployment, you need to analyse your particular environment and decide what works best for you to minimise the bottlenecks using good network design, not just good software.
<br />
<br />
<br />N.
<br /><b>
<br />
<br />On Sun, 10 Sep 2006 18:26:57 -0400, Script Head wrote</b>
<br />> Mediaproxy is more mature but rtpproxy can handle greater load. IMHO both aren't truly fit for the job and consume too much CPU to be useful on large scale.
<br />>
<br />> <span class="gmail_quote">On 9/10/06, <b class="gmail_sendername">
vijay tiwari</b> <<a href="mailto:vijay11tiwari@yahoo.com">vijay11tiwari@yahoo.com</a>> wrote:</span><blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">
<br />>
<br />> hi
<br />>
<br />>
<br />> what is the deference between rtpporxy and mediaproxy
<br />>
<br />>
<br />> with regards
<br />> <span class="sg">
<br />>
<br />>
<br />> <em><font size="4" face="times new roman" color="#0000ff">Vijay Tiwari</font></em>
<br />> <em><font size="4" face="times new roman" color="#0000ff">Network Admin</font></em>
<br />> <em><font size="4" face="times new roman" color="#0000ff">Sachitel Communications</font></em>
<br />> <em><font size="4" face="times new roman" color="#0000ff">Noida(U.P.)</font></em>
<br />> <em><font size="4" face="times new roman" color="#0000ff">M- 09871633711</font></em></span>
<br />> <span class="ad">
<br />>
<hr size="1" />Do you Yahoo!?
<br />>
Get on board. <a onclick="return top.js.OpenExtLink(window,event,this)" target="_blank" href="http://us.rd.yahoo.com/evt=40791/*http:/advision.webevents.yahoo.com/mailbeta">You're invited</a> to try the new Yahoo! Mail.
<br />> </span>
<br />> _______________________________________________
<br />> Serusers mailing list
<br />> <a href="mailto:Serusers@lists.iptel.org" onclick="return top.js.OpenExtLink(window,event,this)">Serusers@lists.iptel.org
</a>
<br />> <a target="_blank" href="http://lists.iptel.org/mailman/listinfo/serusers" onclick="return top.js.OpenExtLink(window,event,this)">http://lists.iptel.org/mailman/listinfo/serusers</a>
<br />>
<br />> </blockquote>
<br />
<br />
<br />
</font>
</BODY>
</HTML>