Hi Gholamreza, Most Kamailio functionality can be used in an active-active way as long as there is a database persistence layer that can be shared among them: In particular, since you asked about the registrar: you can use `db_mode` 3 with `usrloc` to achieve this persistence: http://kamailio.org/docs/modules/4.3.x/modules/usrloc.html#usrloc.p.db_mode That is to say, if multiple Kamailio instances are configured to use the same database with usrloc db_mode 3, then any of them can resolve any registration binding regardless of which actual proxy it was saved on. That said, database-based sharing is certainly not the only approach, particularly to replication of registration contacts. A few others: 1) Replicate registration messages manually with t_replicate(): http://kamailio.org/docs/modules/4.3.x/modules/tm.html#tm.f.t_replicate 2) Use the `dmq` interprocess messaging bus to replicate the location table that way: http://kamailio.org/docs/modules/4.3.x/modules/dmq_usrloc.html So, it's fair to say this problem is amply solved in relation to the registrar functionality specifically. If your question was more general: there is no generic Kamailio clustering concept that can continuously replicate all internal state across multiple proxy instances. In keeping with Kamailio's fairly low-level interior, you must choose and implement your own specific methodologies for this that are appropriate for the architecture and business rules of your applications and services. -- Alex -- Alex Balashov | Principal | Evariste Systems LLC 303 Perimeter Center North, Suite 300 Atlanta, GA 30346 United States Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

Thank you so much Alex. I tried REGISTER replication and DM_MODE 3. But my problem here is that in these scenarios Kamailio will give you a non-local socket error. I want to have multiple Kamailio servers so that a user that is registered on one server can easily call other users on another server. On Mon, Feb 1, 2016 at 10:01 AM, Alex Balashov <abalashov(a)evaristesys.com> wrote:

Here's a thought, though: If your goal is really for users registered on one server to be able to easily call users registered on another server, you probably don't care to replicate or share the 'location' table per se. You just want one Kamailio server to call the right Kamailio server to reach the user's native home. In that case, why not create a database view over a composition of the 'location' tables of various servers that exposes a map of AoR -> socket? You can then query those values with 'sqlops' yourself and forward the call to the correct server, which can then do a native lookup(). -- Alex Balashov | Principal | Evariste Systems LLC 303 Perimeter Center North, Suite 300 Atlanta, GA 30346 United States Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

Hi, I think you need to make record routing, so it will keep initial(to what user registered) Kamailio in signaling path. I hope it will helps. With kind regards, Jurijs 2016-02-01 9:33 GMT+02:00 Gholamreza Sabery <gr.sabery(a)gmail.com>om>: -- Jurijs

Hi Alex, You are right. :) With kind regards, 2016-02-01 10:09 GMT+02:00 Alex Balashov <abalashov(a)evaristesys.com>om>: -- Jurijs

All right. Thank you so much. On Mon, Feb 1, 2016 at 11:47 AM, Federico Cabiddu < federico.cabiddu(a)gmail.com&gt; wrote:

On Mon, Feb 01, 2016 at 09:17:41AM +0100, Federico Cabiddu wrote: Be warned that any stateful firewall or NATed client will not accept the messages from any other sipserver to that client. My solution was to use edge/loadbalancer proxies which add the Path header using add_path_received to store both the edge/loadbalancer ip and client source before passing the request to the backends (using dispatcher). Any backend will send messages based on the Path headers to the edge/loadbalancer and that will pass it to the client to appease statefull firewalls.

Hi, If you have following: UA A ====> Kamilio 1 UA B ====> Kamailio 2 With path you just make sure that all calls are routed to that server where UA initially registered. So if UA A is calling UA B, call will go in such way: UA A=> Kamilio 1 => Kamailio 2 => UA B. I hope I answered your question. With kind regards, 2016-02-03 12:18 GMT+02:00 Gholamreza Sabery &lt;gr.sabery(a)gmail.com&gt;om>: -- Jurijs

Hi, Interesting discussion going on. Ive to ask can OP use shared location table between different kamailio servers and use db mode 3. All he has to do is if UA B calls UA A via Kamailio2 he just needs to find the received socket and if it is not local Kamailio2 then route to the IP maybe attach a custom header and relay call to Kamailio1. Kamailio1 gets call with the custom headers sends call to route(LOCATION) or w/e he has for lookups. Regards, Sammy On Feb 3, 2016 06:19, "Daniel Tryba" &lt;d.tryba(a)pocos.nl&gt; wrote: