Path doesn’t share registrations. It just allows routing from B back through A in order to reach the endpoint, rather than trying to reach the endpoint directly. It’s just a header that says “when contacting this registrant, hop/detour through the original registrant”.
But, Path doesn’t do anything else. So, if you want registrar B to know that the registrant is registered anywhere at all — A or B — and the Contact/URI at which to reach it (whether directly or through a Path hop), you need some means of replicating the registration database. dmq_usrloc provides this aspect.
Path and dmq_usrloc do entirely different things, of different degrees of significance to the overall process. The “heavy” part is done by usrloc/dmq_usrloc.
— Sent from mobile, with due apologies for brevity and errors.
On Jul 13, 2021, at 10:43 AM, Social Boh social@bohboh.info wrote:
Hello,
If I have to use path protocol or other routing logic to share REGISTER between the Two Kamailio so I can call From USERA on KamailioA to USERB on KamailioB, I think I don't need to still use DMQ_USRLOC module.
Can you offer a practical use of this module, please?
Thank you
Regards
I'm SoCIaL, MayBe
El 13/07/2021 a las 9:01 a. m., Alex Balashov escribió: To replicate knowledge of the registration contact bindings automatically.
It doesn’t provide magic routing to reach them. It just shares the knowledge. :-)
— Sent from mobile, with due apologies for brevity and errors.
On Jul 13, 2021, at 9:46 AM, Social Boh social@bohboh.info wrote:
If I have to use Path or other solution, which is the main idea behind the DMQ_USRLOC module?
Regards
I'm SoCIaL, MayBe
El 13/07/2021 a las 8:36 a. m., Alex Balashov escribió: Yes, you need the Path module and special logic for lateral routing of requests received from A and transiting through a Path hop of B.
— Sent from mobile, with due apologies for brevity and errors.
On Jul 13, 2021, at 8:47 AM, Social Boh social@bohboh.info wrote:
Hello,
I'm testing DMQ_USRLOC modulo between two Kamailio servers (A) and (B)
The two servers share the same domain and using Amazon Route53 to distributes 50% requests each Server.
The problem is when I try to make a call from user A (registered on kamailio A) and the user B (registered on Kamailio B).
The call follow this flow:
User A --> KamailioA --> UserB
go directly to userB because KamailioA know, via DMQ_USRLOC IP and port of UserB. With some Softphone the call work with audio without problem; with other Softphone USERB never answer the INVITE sends from Kamailio. Is it possible use this flow?
USER A --> KamailioA --> KamailioB --> User B
to resolve this kind of problem or is there other available option?
Thank you
--
I'm SoCIaL, MayBe
Kamailio - Users Mailing List - Non Commercial Discussions
- sr-users@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
Kamailio - Users Mailing List - Non Commercial Discussions
- sr-users@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
Kamailio - Users Mailing List - Non Commercial Discussions
- sr-users@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
Kamailio - Users Mailing List - Non Commercial Discussions
- sr-users@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: