<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
It would be nice to have a bridge channel capable to operate an
external mediaproxy (<a class="moz-txt-link-freetext" href="http://www.ag-projects.com/MediaProxy.html">http://www.ag-projects.com/MediaProxy.html</a>)<br>
<br>
The latest version is able to forward RTP traffic at router speeds
using linux conntrack module.<br>
<br>
This can be EXTREMELY useful in large Asterisk installs<br>
<br>
Another option would be to integrate a conntrack interface into
asterisk...<br>
<br>
<br>
<br>
Thanks<br>
Vadim<br>
Joshua Colp wrote:
<blockquote
cite="mid:15288931.407561234791995865.JavaMail.root@jupiler.digium.com"
type="cite">
<pre wrap="">----- "Johansson Olle E" <a class="moz-txt-link-rfc2396E" href="mailto:oej@edvina.net"><oej@edvina.net></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I think this together with the changes done by murf in the area of
hash tables will mean that we done some major work to build a new
generation of Asterisk that scales better than the old versions on the
current server architectures! Impressed!
Now, can anyone start a discussion on the way we handle threads? If we
run on a quad-core or a system with dual quad core CPUs, we have
capactiy for an enormous quantity of calls, with at least one thread
per call. Can a modern Linux/Unix thread scheduler handle 10 000
threads efficently?
</pre>
</blockquote>
<pre wrap=""><!---->
Some work is also being done with the new bridging core to change this some. There is a bridging
module called bridge_multiplexed which groups up to 4 bridges (or 8 channels) into the same operating
thread. We'll probably need to play with it to find the sweet spot on number of channels but hopefully
this will help things.
</pre>
</blockquote>
<br>
</body>
</html>