Re: [SR-Users] t_replicate() and Contact

2013-09-05 Thread Daniel-Constantin Mierla
On 9/5/13 11:23 PM, Daniel-Constantin Mierla wrote: Hello, on the second peer, when you get the replicated REGISTER, don't call fix_natted_contact(). to complete: neither call fix_nated_registrar() Cheers, Daniel Also, received and socket should be passed via header form first server to t

Re: [SR-Users] t_replicate() and Contact

2013-09-05 Thread Daniel-Constantin Mierla
Hello, on the second peer, when you get the replicated REGISTER, don't call fix_natted_contact(). Also, received and socket should be passed via header form first server to the backup. Practically, the second server should get the values from headers, store them in avp and then call save().

Re: [SR-Users] t_replicate() and Contact

2013-09-05 Thread Marc Soda
Also, I tried setting the Contact header in onsend_route, but it seems that it's overwritten after that. Perhaps I need to modify it on the second Kamailio server? Is it possible to change it before it's sent on the first server? On Wed, Sep 4, 2013 at 8:53 AM, Marc Soda wrote: > Hey all, > >

[SR-Users] t_replicate() and Contact

2013-09-04 Thread Marc Soda
Hey all, I have 2 Kamailio systems replicating REGISTER's to each other. However, I've noticed that the Contact header seems to be wrong on the second server. For example, if I have endpoint 1.1.1.1 registering to 2.2.2.2, then 2.2.2.2 is calling t_replicate() to 3.3.3.3, the Contact header once