Hi,a solution in this case could be making usage of Path header (https://tools.ietf.org/html/rfc3327).You have to load the path moduleĀand enabled its usage in registrar moduleĀIf you plan to use REGISTER replication through t_replicate() just call add_path() before replicating the message to the other server(s).If you use a shared database with db_mode = 3, call msg_apply_changes (http://www.kamailio.org/docs/modules/devel/modules/textopsx.html#textopsx.f.msg_apply_changes) before saving the contact. In this case also be sure to set path_check_local parametr of the registrar module (http://www.kamailio.org/docs/modules/devel/modules/registrar.html#registrar.p.path_check_local) to 1.Cheers,FedericoOn Mon, Feb 1, 2016 at 9:10 AM, Jurijs Ivolga <jurij.ivo@gmail.com> wrote:With kind regards,Hi Alex,You are right. :)--2016-02-01 10:09 GMT+02:00 Alex Balashov <abalashov@evaristesys.com>:On 02/01/2016 02:59 AM, Jurijs Ivolga wrote:
I think you need to make record routing, so it will keep initial(to what
user registered) Kamailio in signaling path.
Ah, no. Record-Route is for INVITEs only. You're thinking of Path.
--
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/
_______________________________________________
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
Jurijs
_______________________________________________
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
_______________________________________________
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