[OpenSIPS-Users] Loadbalancer for Registrations and calls

Wed Nov 2 19:50:35 UTC 2022

I did find setting this, works for contact
modparam("dispatcher", "hash_pvar", "$ct.fields(uri)")

But is there a way to break it up to only look at the tgrp and
trunk-context if available and if not available look at the URI as a whole?

INVITE is still not looking at the hash and is still sending out based on
FQDN resolution resolved in the R-URI.  Not sure how to resolve this to
force it to match the hash.

Thank you.

Kevin

On Wed, Nov 2, 2022 at 11:00 AM Kevin Kennedy <kennedy4260 at gmail.com> wrote:

> I am not seeing an option, but Is it possible to hash on the Contact
> Header?
>
> Right now I have it hashing on From Header and I know that the From on the
> Register and the From on the INVITE match except for the tag. I added the
> "u" flag and it is still not working.  What it is doing is looking at the
> DNS record of the R-URI domain and routing on that.
>
>  $ru = (ds_select_dst(1, 1, "u", "default", 1));
>
> How do I get it to not use the domain in the R-URI to route on.
>
> Thank you.
>
> Kevin
>
> On Tue, Nov 1, 2022 at 12:51 AM Bogdan-Andrei Iancu <bogdan at opensips.org>
> wrote:
>
>> Hi,
>>
>> The REGISTERs of used X and the calls to user X will both have the X SIP
>> URI into the TO URI, so hashing it will give the same value, so the same
>> destination.
>>
>> Regards,
>>
>> Bogdan-Andrei Iancu
>>
>> OpenSIPS Founder and Developer
>>   https://www.opensips-solutions.com
>> OpenSIPS Bootcamp 5-16 Dec 2022, online
>>   https://www.opensips.org/training/OpenSIPS_eBootcamp_2022/
>>
>> On 10/30/22 7:16 AM, Kevin Kennedy wrote:
>>
>> I have set the ds_select_dst used in the mid_registrar part of the script
>> to hash the To URI
>>
>> $ru = (ds_select_dst(1, *2*, , "default", 1));
>>
>> but I am not seeing exactly how to do this for the INVITE. If I use
>> ds_select_dst for the INVITE, it just chooses a random destination,
>> not performing a match on the Registration destination.
>>
>> Am I missing something with this?
>>
>> Is there a way to pull information out of the usrloc contact kv-store.
>> The information that is needed is in the hop field of the json string.
>>
>> Thank you.
>>
>> On Fri, Oct 28, 2022 at 4:03 AM Bogdan-Andrei Iancu <bogdan at opensips.org>
>> wrote:
>>
>>> Hi Kevin,
>>>
>>> You may try for REGISTERs to do hashing over TO uri and for INVITEs over
>>> TO or RURI - so they may get to the same box.
>>>
>>> Regards,
>>>
>>> Bogdan-Andrei Iancu
>>>
>>> OpenSIPS Founder and Developer
>>>   https://www.opensips-solutions.com
>>> OpenSIPS Bootcamp 5-16 Dec 2022, online
>>>   https://www.opensips.org/training/OpenSIPS_eBootcamp_2022/
>>>
>>> On 10/25/22 1:13 AM, Kevin Kennedy wrote:
>>>
>>> Yes that is correct.  Trying to send the INVITE to the same dispatcher
>>> destination that the Registration is at.
>>>
>>> I will check the Call-ID based dispatching algorithm
>>>
>>> Thank you.
>>> Kevin
>>>
>>> On Mon, Oct 24, 2022 at 8:50 AM Bogdan-Andrei Iancu <bogdan at opensips.org>
>>> wrote:
>>>
>>>> Hi Kevin
>>>>
>>>> 1) use the call-id based dispatching alg, so the INVITE with
>>>> credentials will get sent to the same destination
>>>>
>>>> 2) yes, mid-register (as register SIP mechanism) is allows the UA to
>>>> receive calls only, it is not related to handling the outbound calls of the
>>>> UA. I understand you try to get a call from A to B to be sent to the same
>>>> dispatcher destination as the registers of B, right ?
>>>>
>>>> Regards,
>>>>
>>>> Bogdan-Andrei Iancu
>>>>
>>>> OpenSIPS Founder and Developer
>>>>   https://www.opensips-solutions.com
>>>> OpenSIPS Bootcamp 5-16 Dec 2022, online
>>>>   https://www.opensips.org/training/OpenSIPS_eBootcamp_2022/
>>>>
>>>> On 10/21/22 10:28 PM, Kevin Kennedy wrote:
>>>>
>>>> I believe I have mid_registrar somewhat working with dispatcher, but I
>>>> seem to have a coulple issues.
>>>>
>>>> 1) When I receive the 401 request the second authentication INVITE is
>>>> sending to another $ru host in the dispatcher instead of the initial one it
>>>> sent to.
>>>> 2) How do I send an outbound INVITE matching the registration cache  to
>>>> the same $ru that it is Registered to.
>>>>     mid_registrar_lookup uses the AOR instead of contact so it is only
>>>> allowing the Incoming INVITEs to reach the client.
>>>>
>>>> Thank ou.
>>>>
>>>> Thank you.
>>>>
>>>> On Fri, Aug 19, 2022 at 8:46 AM Alex <ayakimkin at gmail.com> wrote:
>>>>
>>>>> Hello,
>>>>>
>>>>> setup mid registrar easy with this instruction.
>>>>> https://www.opensips.org/Documentation/Tutorials-MidRegistrar
>>>>> There is link to config
>>>>>
>>>>> But It relays every Registration request every 60sec on my server.
>>>>> Please let me know if you could set up like on picture in instruction.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> чт, 18 авг. 2022 г. в 18:37, Kevin Kennedy <kennedy4260 at gmail.com>:
>>>>>
>>>>>> I am looking for a configuration to be able to front end multiple
>>>>>> SBC's to load balance Registrations and keep track of them to send INVITE's
>>>>>> to the corresponding SBC.
>>>>>>
>>>>>> I am thinking of using a combination of Dispatcher and midregister,
>>>>>> but not sure how to set this up correctly.
>>>>>>
>>>>>> Any thoughts?
>>>>>>
>>>>>> Thank you.
>>>>>>
>>>>>> Kevin
>>>>>> _______________________________________________
>>>>>> Users mailing list
>>>>>> Users at lists.opensips.org
>>>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> С уважением,
>>>>> Якимкин Алексей
>>>>> _______________________________________________
>>>>> Users mailing list
>>>>> Users at lists.opensips.org
>>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>>>
>>>>
>>>> _______________________________________________
>>>> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>>
>>>>
>>>>
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20221102/66fc03d8/attachment.html>