<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><font size="-1">Hello,</font></p>
<p><font size="-1"> in an active/stanby kamailio setup with
keepalived I'm using Database replication primary/primary so I
don't need DMQ_USRLOC</font></p>
<p><font size="-1">I'm testing just now and when active kamailio go
down, I can make calls between extensions without connection
problems with the stanby kamailio.<br>
</font></p>
<p><font size="-1">So my question is: where I "NEED" to use
DMQ_USRLOC?<br>
</font></p>
<p><font size="-1">Regards</font><br>
</p>
<pre class="moz-signature" cols="72">---
I'm SoCIaL, MayBe</pre>
<div class="moz-cite-prefix">El 13/07/2021 a las 9:48 a. m., Barry
Flanagan escribió:<br>
</div>
<blockquote type="cite"
cite="mid:981103a5-5129-0ab2-de73-c3a4a3d655b3@flanagan.ie">On
13/07/2021 15:41, Social Boh wrote:
<br>
<blockquote type="cite">Hello,
<br>
<br>
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.
<br>
<br>
Can you offer a practical use of this module, please?
<br>
</blockquote>
<br>
<br>
For example, if you had an active/standby kamailio setup with a
floating IP managed by e.g. Keepalived then when a failover event
occurs, the usrloc is up to date and the failover is completely
transparent.
<br>
<br>
Hope this helps
<br>
<br>
-Barry Flanagan
<br>
<br>
<blockquote type="cite">
<br>
Thank you
<br>
<br>
Regards
<br>
<br>
---
<br>
I'm SoCIaL, MayBe
<br>
<br>
El 13/07/2021 a las 9:01 a. m., Alex Balashov escribió:
<br>
<blockquote type="cite">To replicate knowledge of the
registration contact bindings automatically.
<br>
<br>
It doesn’t provide magic routing to reach them. It just shares
the knowledge. :-)
<br>
<br>
—
<br>
Sent from mobile, with due apologies for brevity and errors.
<br>
<br>
<blockquote type="cite">On Jul 13, 2021, at 9:46 AM, Social
Boh <a class="moz-txt-link-rfc2396E" href="mailto:social@bohboh.info"><social@bohboh.info></a> wrote:
<br>
<br>
If I have to use Path or other solution, which is the main
idea behind the DMQ_USRLOC module?
<br>
<br>
Regards
<br>
<br>
---
<br>
I'm SoCIaL, MayBe
<br>
<br>
<blockquote type="cite">El 13/07/2021 a las 8:36 a. m., Alex
Balashov escribió:
<br>
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.
<br>
<br>
—
<br>
Sent from mobile, with due apologies for brevity and
errors.
<br>
<br>
<blockquote type="cite">
<blockquote type="cite">On Jul 13, 2021, at 8:47 AM,
Social Boh <a class="moz-txt-link-rfc2396E" href="mailto:social@bohboh.info"><social@bohboh.info></a> wrote:
<br>
</blockquote>
Hello,
<br>
<br>
I'm testing DMQ_USRLOC modulo between two Kamailio
servers (A) and (B)
<br>
<br>
The two servers share the same domain and using Amazon
Route53 to distributes 50% requests each Server.
<br>
<br>
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).
<br>
<br>
The call follow this flow:
<br>
<br>
User A --> KamailioA --> UserB
<br>
<br>
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?
<br>
<br>
USER A --> KamailioA --> KamailioB --> User B
<br>
<br>
to resolve this kind of problem or is there other
available option?
<br>
<br>
Thank you
<br>
<br>
-- <br>
---
<br>
I'm SoCIaL, MayBe
<br>
<br>
<br>
__________________________________________________________
<br>
Kamailio - Users Mailing List - Non Commercial
Discussions
<br>
* <a class="moz-txt-link-abbreviated" href="mailto:sr-users@lists.kamailio.org">sr-users@lists.kamailio.org</a>
<br>
Important: keep the mailing list in the recipients, do
not reply only to the sender!
<br>
Edit mailing list options or unsubscribe:
<br>
*
<a class="moz-txt-link-freetext" href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a>
<br>
</blockquote>
__________________________________________________________
<br>
Kamailio - Users Mailing List - Non Commercial Discussions
<br>
* <a class="moz-txt-link-abbreviated" href="mailto:sr-users@lists.kamailio.org">sr-users@lists.kamailio.org</a>
<br>
Important: keep the mailing list in the recipients, do not
reply only to the sender!
<br>
Edit mailing list options or unsubscribe:
<br>
*
<a class="moz-txt-link-freetext" href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a>
<br>
</blockquote>
</blockquote>
__________________________________________________________
<br>
Kamailio - Users Mailing List - Non Commercial Discussions
<br>
* <a class="moz-txt-link-abbreviated" href="mailto:sr-users@lists.kamailio.org">sr-users@lists.kamailio.org</a>
<br>
Important: keep the mailing list in the recipients, do not
reply only to the sender!
<br>
Edit mailing list options or unsubscribe:
<br>
*
<a class="moz-txt-link-freetext" href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a>
<br>
</blockquote>
<br>
__________________________________________________________
<br>
Kamailio - Users Mailing List - Non Commercial Discussions
<br>
* <a class="moz-txt-link-abbreviated" href="mailto:sr-users@lists.kamailio.org">sr-users@lists.kamailio.org</a>
<br>
Important: keep the mailing list in the recipients, do not reply
only to the sender!
<br>
Edit mailing list options or unsubscribe:
<br>
* <a class="moz-txt-link-freetext" href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a>
<br>
</blockquote>
<br>
</blockquote>
</body>
</html>