Hello,

I didn't spent time on understanding the exact issue, but from database point of view, do you want to avoid having two different tables for specific reasons, like external applications accessing it?

Have you looked at setting the server_id, maybe that can help to have the records grouped by each server.

Cheers,
Daniel

Hi Guys,

I have a quick question wondered if anyone could provide some suggestions please?!

We have a setup of two registrars in EC2 (kamailio 4.4 running on debian VMs) which act in an active/active fashion with a number of devices

behind NAT where  we use the DMQ dmq_t_replicate function to send the registration details between each server and append the PATH parameter

so the registrar the device registered with is always associated with the client device.

This all works fine, the only issue is persistency should we have a failure of one of the registrars, be it process or server and recovering the correct

PATH detail so the end device can still be reached.

I have tried this with separate databases with each registrar, which works when using cache and db but I ideally want the same database for the two servers and not

change the architecture at this time unless it is a necessary.

I have also tested with dmq_usrloc but this again provides the usrlocation details of the notification servers in the group(not path), again which I understand but I wondered

if there is anything else I could try or its just a question of in the event of a failure half the registrations will be effected until it recovers and they

re-register again if I dont want to have separate databases (location tables) or I add more network elements into the flow, such as HA pair or load balancer but just want to

make sure I have exhausted all options or consider the risk before I look to do this. 

Many thanks!

Jon

_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - March 9-11, 2020, Berlin - www.asipto.com
Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com