Hello,

run with debug=3 in config file and see if there are log messages that gives you more details about what happens.

Typically, when doing replication, you may need to replicate received and sometime socket information -- that can be done via headers and then added to avps before saving to location in the second peer. Look at the readme of registrar module for those parameters.

Cheers,
Daniel

On 19/01/14 14:05, Volkan Oransoy wrote:
Hi all,

I am trying to setup an active-active pair of sip proxies. I have connected two kamailio boxes to the same PostgreSQL database and my usrloc db_mode is 3. I can see the registration data in the database but "ul show" outputs of two device is not same. I think writing registration data to the same db is not enough. 

I have found a method to replicate the registraiton process. With t_replicate, I synchronize REGISTER requests to both boxes. But I had to disable shared database because of uniqe id validations.

route[REGISTRAR] {
        if (is_method("REGISTER"))
        {
                if(isflagset(FLT_NATS))
                {
                        setbflag(FLB_NATB);
                }
                if (!save("location"))
                        sl_reply_error();
                t_replicate("sip:10.1.1.2:5060;transport=udp");
                exit;
        }
}


My media servers randomly sends calls to SIP proxies. If Media server send the call to the original registrar then the replicated, call initiates normally. But when UA registered in first proxy, and Media server sends the call to the send one, even if second one has UA in location table, call does not initiate.

Does anyone have an idea about this kind of an active active setup?

Thanks in advance. Best regards,

/Volkan


_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda