<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hello,<br>
<br>
<div class="moz-cite-prefix">On 5/1/13 5:08 PM,
<a class="moz-txt-link-abbreviated" href="mailto:mark@brightvoip.co.uk">mark@brightvoip.co.uk</a> wrote:<br>
</div>
<blockquote cite="mid:564DF6A2FF7B4F9C8191D244C2578EFA@fungames2"
type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<meta name="GENERATOR" content="MSHTML 8.00.6001.19412">
<style></style>
<div><font size="2" face="Arial">Hi all,</font></div>
<div> </div>
<div><font size="2" face="Arial">Posted a similar query a few
weeks ago, without much interest - any advice appreciated.</font></div>
<div> </div>
<div><font size="2" face="Arial">I have two sites and will send
calls between them. I have Kamailio at each site which will
route the calls out/in.</font></div>
<div> </div>
<div><font size="2" face="Arial">There are multiple distinct
network routes between the sites, accessible via different IP
addresses. Each Kamailio has multiple IP's, one for each
route.</font></div>
<div> </div>
<div><font size="2" face="Arial">The purpose of the multiple
routes is mainly fault tolerance. Some of the network links
are unreliable, so routing must adapt when route(s) are
unavailable. When all routes are available, all should handle
some traffic, at differing ratios to match the bandwidth
available to each route (e.g route A - 50%, route B - 30%,
route C - 20%).</font></div>
<div> </div>
<div><font size="2" face="Arial">I know that the Dispatcher can
manage the routing for the SIP traffic, with the %ge
distribution, and with SIP OPTIONS 'pings' to detect route
availability.</font></div>
<div> </div>
<div><font size="2" face="Arial">My main headache is that RTP must
follow the same route as SIP for each call. </font></div>
<div> </div>
<div><font size="2" face="Arial">After a bit of web digging, I was
thinking of a solution where each of the Kamailio servers will
run multiple instances of rtpproxy (one for each ip/route).
Then once the dispatcher has chosen a route for the call, to
use the matching rtpproxy instance to direct the audio.</font></div>
<div> </div>
<div><font size="2" face="Arial">Any comments or alternate
solutions/suggestions would be of interest.</font></div>
</blockquote>
<font size="2"><font face="Arial">you need to install many instances
of rtpproxy, because it can listen on one or two (for bridging)
network interfaces</font></font>.<br>
<br>
If there is no IP routing between incoming interface and outgoing
interface, you may need to install as many rtpproxy instances as
combination of incoming and outgoing network interfaces you may
have.<br>
<br>
Cheers,<br>
Daniel<br>
<pre class="moz-signature" cols="72">--
Daniel-Constantin Mierla - <a class="moz-txt-link-freetext" href="http://www.asipto.com">http://www.asipto.com</a>
<a class="moz-txt-link-freetext" href="http://twitter.com/#!/miconda">http://twitter.com/#!/miconda</a> - <a class="moz-txt-link-freetext" href="http://www.linkedin.com/in/miconda">http://www.linkedin.com/in/miconda</a>
Kamailio Advanced Training, San Francisco, USA - June 24-27, 2013
* <a class="moz-txt-link-freetext" href="http://asipto.com/u/katu">http://asipto.com/u/katu</a> *</pre>
</body>
</html>