[SR-Users] DMQ_USRLOC module and calls

[Barry Flanagan]

On 13/07/2021 15:41, Social Boh 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?


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.

Hope this helps

-Barry Flanagan

>
> 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 at 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 at 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 at lists.kamailio.org
>>>>> Important: keep the mailing list in the recipients, do not reply 
>>>>> only to the sender!
>>>>> Edit mailing list options or unsubscribe:
>>>>> * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>>> __________________________________________________________
>>>> Kamailio - Users Mailing List - Non Commercial Discussions
>>>>    * sr-users at lists.kamailio.org
>>>> Important: keep the mailing list in the recipients, do not reply 
>>>> only to the sender!
>>>> Edit mailing list options or unsubscribe:
>>>>    * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>> __________________________________________________________
>> Kamailio - Users Mailing List - Non Commercial Discussions
>>    * sr-users at lists.kamailio.org
>> Important: keep the mailing list in the recipients, do not reply only 
>> to the sender!
>> Edit mailing list options or unsubscribe:
>>    * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
> __________________________________________________________
> Kamailio - Users Mailing List - Non Commercial Discussions
>  * sr-users at lists.kamailio.org
> Important: keep the mailing list in the recipients, do not reply only 
> to the sender!
> Edit mailing list options or unsubscribe:
>  * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

-- 
-Barry

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_0xB1C81B216B50A825.asc
Type: application/pgp-keys
Size: 3066 bytes
Desc: OpenPGP public key
URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20210713/7fce30bc/attachment.key>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20210713/7fce30bc/attachment.sig>