<div dir="ltr"><div><div><div><div>Hello,<br><br></div>I can't use load balancing feature because location of sip user is defined. One DID is routed to one server. One to one relationship. So if loadblancer send phone call on one server, but user is not registred on this one, call is hangup/lost.<br></div><br></div>I will use LCR for outgoing call. LCR will "help" CBx to find best carrier following rules defined by administrators. LCR can probe gateways ? I have set ping_interval etc but ping is not sent by kamailio.<br><br></div>Regards.<code></code><br></div><div class="gmail_extra"><br><div class="gmail_quote">2016-05-23 14:36 GMT+02:00 Daniel-Constantin Mierla <span dir="ltr"><<a href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<p>Hello,</p>
<p>dns naptr is ok for locating servers as long as you control the
local infrastructure and make sure dns changes propagation is done
right.</p>
<p>An alternative would be using dispatcher module as a load
balancer. It has a lot of features for this use case, different
distribution algorithms as well as probing the servers (CBx) to
see which one is available.</p>
<p>If the perfomrance is the concern, keeping most of the processing
inside the kamailio is a good choice.</p>
<p>Cheers,<br>
Daniel<br>
</p><div><div class="h5">
<br>
<div>On 23/05/16 10:27, Loic Chabert wrote:<br>
</div>
</div></div><blockquote type="cite"><div><div class="h5">
<div dir="ltr">
<div>
<div>
<div>Hello Kamailio users,<br>
<br>
</div>
I'm working on a sip infrastructure, with opensource
technologies, and of course Kamailio will run on my new
infrastructure :)<br>
<br>
</div>
Kamailio will be my central routing engine, between SBC
(running on asterisk), and somes boxes (asterisk too) where
customers will be registred. Please find below my future
infrastructure:<br>
<br>
<br>
----------
--------------
-------- ----------------</div>
<div>| SBC1 | - - - - - | - - - -| kamailio1 |- - - - - | - - -
- - | CB1 |-----------------| SIPPHONE | </div>
<div>---------- | --------------
| -------- ----------------</div>
<div>
|
| <br>
</div>
<div>----------
| |
-------- <br>
</div>
<div>| SBC2 | - - - - - | |
- - - - - | CB2 | <br>
---------- |
| --------<br>
| -------------- |<br>
</div>
<div>
<div>---------- | - - - -| kamailio2 |- - - -
-| -------- <br>
| SBCn |- - - - - | -------------- | - -
- - - | CBn |<br>
---------- |
| --------<br>
<br>
</div>
<div>Kamailio high availabality will be done with loopback
address and BGP in two datacenters. SIP carriers will be
connected to SBC and customer to one CB.<br>
<br>
</div>
<div>I have made some tests with kamailio, and i use LCR to
route call from CB to SBC, using wheigt and prorities to
send call to carriers.<br>
</div>
<div>Then, when a call arrived from carriers, i use DNS NATPER
lookup to find the right CB box.<br>
<br>
</div>
<div>CB HA is done using DNS SRV. So user is registred at one
location, and only one. No location sharing beetwen boxes.<br>
<br>
</div>
<div>I have some question concerning my architecture, and
technologies used to routing call.<br>
</div>
<div>Is LCR is the best option for routing call between
multiple carriers ? DNS NAPTER is a modern solution to find
an endpoint on this architecture ? Existing a better way to
route call with kamailio, for exemple rt-json and curl ?<br>
</div>
<div><br>
</div>
<div>
<div style="text-align:left">In my point of view, kamailio
should be a routing engine, using internal technologies,
to maximise performances. Less work with kamailio and
external app, best performances in sip routing. Is it the
good vision ?<br>
</div>
<br>
</div>
<div>Thanks in advance.<br>
</div>
<div><br>
</div>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
</div></div><pre>_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
<a href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-router.org</a>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><span class="HOEnZb"><font color="#888888">
</font></span></pre><span class="HOEnZb"><font color="#888888">
</font></span></blockquote><span class="HOEnZb"><font color="#888888">
<br>
<pre cols="72">--
Daniel-Constantin Mierla
<a href="http://www.asipto.com" target="_blank">http://www.asipto.com</a>
<a href="http://twitter.com/#!/miconda" target="_blank">http://twitter.com/#!/miconda</a> - <a href="http://www.linkedin.com/in/miconda" target="_blank">http://www.linkedin.com/in/miconda</a>
Kamailio World Conference, Berlin, May 18-20, 2016 - <a href="http://www.kamailioworld.com" target="_blank">http://www.kamailioworld.com</a></pre>
</font></span></div>
<br>_______________________________________________<br>
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list<br>
<a href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a><br>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><br>
<br></blockquote></div><br></div>