Hello, if you are looking at sharing the same destination addresses, many kamailio can connect to the same database. If you have active-active LBs want to notify the other LB about a change in a state of a destination, then you can use the event_route blocks executed by dispatcher module to notify the other LB -- you can do it with uac module/uac_req_send() or triggering a rpc (xmlrpc/jsonrpc) commands. On the other hand, each LB is able to detect the state of the destination, so trying to sync a LB from the other will add a complexity that doesn't bring much benefits. You are better keeping the LB as simple as possible, so its resources are oriented towards routing sip traffic at high volume, rather than sync'ing states that are not going to make much difference in routing the sip. Cheers, Daniel On 19/01/16 08:38, sandeep goje wrote: -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com http://miconda.eu