Re: [OpenSIPS-Users] Loadbalancer for Registrations and calls

[Kevin Kennedy]

Thank you.  That fixed the ERROR I was seeing.

INVITEs are still not matching the hash and sending out via the Request-URI
DNS record instead of the hashed record from Dispatcher.

Thank you.

Kevin

On Wed, Nov 2, 2022 at 1:34 PM M S  wrote:

> you dont need $ru = (ds_select_dst(3, 7, , "default", 1));
> just run ds_select_dst(...) and it sets $ru for you.
>
> On Wed, Nov 2, 2022 at 9:10 PM Kevin Kennedy 
> wrote:
>
>> I am seeing this in the debug after the hash of the contact, I am getting
>> an error pv_set_ruri: str value required to set R-URI.
>>
>> DBG:dispatcher:ds_hash_pvar: Hashing sip:??@10.10.10.10:23233
>> DBG:dispatcher:ds_select_dst: hash [3896938376], candidate [-1], weight
>> sum [30]
>> DBG:dispatcher:ds_select_dst: candidate is [2]
>> DBG:dispatcher:ds_select_dst: using destination [2]
>> DBG:dispatcher:ds_select_dst: selected [7-3/2] 
>> ERROR:core:pv_set_ruri: str value required to set R-URI
>> ERROR:core:do_assign: setting PV failed
>> ERROR:core:do_assign: error at /etc/opensips/opensips.cfg:223
>>
>> Line 223 - $ru = (ds_select_dst(3, 7, , "default", 1));
>>
>> Not sure if you could help with what is causing this.
>>
>> Thank you
>>
>> Kevin
>>
>> On Wed, Nov 2, 2022 at 12:50 PM Kevin Kennedy 
>> wrote:
>>
>>> 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 
>>> 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 <
 bog...@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 <
> bog...@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 <
>> bog...@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 

Re: [OpenSIPS-Users] Loadbalancer for Registrations and calls

[M S]

you dont need $ru = (ds_select_dst(3, 7, , "default", 1));
just run ds_select_dst(...) and it sets $ru for you.

On Wed, Nov 2, 2022 at 9:10 PM Kevin Kennedy  wrote:

> I am seeing this in the debug after the hash of the contact, I am getting
> an error pv_set_ruri: str value required to set R-URI.
>
> DBG:dispatcher:ds_hash_pvar: Hashing sip:??@10.10.10.10:23233
> DBG:dispatcher:ds_select_dst: hash [3896938376], candidate [-1], weight
> sum [30]
> DBG:dispatcher:ds_select_dst: candidate is [2]
> DBG:dispatcher:ds_select_dst: using destination [2]
> DBG:dispatcher:ds_select_dst: selected [7-3/2] 
> ERROR:core:pv_set_ruri: str value required to set R-URI
> ERROR:core:do_assign: setting PV failed
> ERROR:core:do_assign: error at /etc/opensips/opensips.cfg:223
>
> Line 223 - $ru = (ds_select_dst(3, 7, , "default", 1));
>
> Not sure if you could help with what is causing this.
>
> Thank you
>
> Kevin
>
> On Wed, Nov 2, 2022 at 12:50 PM Kevin Kennedy 
> wrote:
>
>> 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 
>> 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 
>>> 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 <
 bog...@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 <
> bog...@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 

Re: [OpenSIPS-Users] Loadbalancer for Registrations and calls

[Kevin Kennedy]

I am seeing this in the debug after the hash of the contact, I am getting
an error pv_set_ruri: str value required to set R-URI.

DBG:dispatcher:ds_hash_pvar: Hashing sip:??@10.10.10.10:23233
DBG:dispatcher:ds_select_dst: hash [3896938376], candidate [-1], weight sum
[30]
DBG:dispatcher:ds_select_dst: candidate is [2]
DBG:dispatcher:ds_select_dst: using destination [2]
DBG:dispatcher:ds_select_dst: selected [7-3/2] 
ERROR:core:pv_set_ruri: str value required to set R-URI
ERROR:core:do_assign: setting PV failed
ERROR:core:do_assign: error at /etc/opensips/opensips.cfg:223

Line 223 - $ru = (ds_select_dst(3, 7, , "default", 1));

Not sure if you could help with what is causing this.

Thank you

Kevin

On Wed, Nov 2, 2022 at 12:50 PM Kevin Kennedy  wrote:

> 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 
> 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 
>> 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 
>>> 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 <
 bog...@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.
> 

Re: [OpenSIPS-Users] Loadbalancer for Registrations and calls

[Kevin Kennedy]

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  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 
> 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 
>> 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 
>>> 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  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 :
>
>> 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 

Re: [OpenSIPS-Users] Loadbalancer for Registrations and calls

[Kevin Kennedy]

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 
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 
> 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 
>> 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  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 :

> 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@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>


 --
 С уважением,
 Якимкин Алексей
 ___
 Users mailing list
 Users@lists.opensips.org
 http://lists.opensips.org/cgi-bin/mailman/listinfo/users

>>>
>>> ___
>>> Users mailing 
>>> listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Loadbalancer for Registrations and calls

[Giovanni Maruzzelli]

We all understood what you are doing and why

It's just that... the answer is inside you! And it's wrong :) (famous quote
from an Italian comedian)

answered from mobile, please pardon terseness and typos,
-giovanni

On Mon, Oct 31, 2022, 20:41 Kevin Kennedy  wrote:

> Thank you all for your responses.  Maybe I am going about this all wrong.
> Maybe I can explain it better with a drawing of what I am trying to do.  I
> am trying to front end customers with Opensips to Load balance
> Registrations to 4 different SBC's.  These SBC's will have their own
> Registration cache and pass the Registration to the Application servers.  I
> need Opensips to send the INVITE/SUBSCRIBE to the SBC that it has sent the
> Registration to in order to match the Registration cache in that device.
> The only way I saw to do this was with Mid-Registrar and Dispatcher since
> Loadbalancer would not handle Registrations/Subscribes, etc.
>
> [image: image.png]
> Hopefully that can explain what I am trying to do better and help you
> understand what I am trying to accomplish.
>
> Thank you
>
> Kevin
>
> On Mon, Oct 31, 2022 at 6:07 AM Giovanni Maruzzelli 
> wrote:
>
>> On Mon, Oct 31, 2022 at 1:59 PM Giovanni Maruzzelli 
>> wrote:
>>
>>>
>>> You can use the hashing Bogdan proposed, so ds_select will go to the
>>> same machine because it gets the same result from hashing the same input.
>>> In this case, you must find "something" (eg a cleaned TO for register and a
>>> cleaned FROM for INVITE)
>>>
>>
>> or cleaned TO and cleaned TO, for inbound calls
>>
>> -giovanni
>>
>> ___
>> Users mailing list
>> Users@lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Loadbalancer for Registrations and calls

[Kevin Kennedy]

Thank you all for your responses.  Maybe I am going about this all wrong.
Maybe I can explain it better with a drawing of what I am trying to do.  I
am trying to front end customers with Opensips to Load balance
Registrations to 4 different SBC's.  These SBC's will have their own
Registration cache and pass the Registration to the Application servers.  I
need Opensips to send the INVITE/SUBSCRIBE to the SBC that it has sent the
Registration to in order to match the Registration cache in that device.
The only way I saw to do this was with Mid-Registrar and Dispatcher since
Loadbalancer would not handle Registrations/Subscribes, etc.

[image: image.png]
Hopefully that can explain what I am trying to do better and help you
understand what I am trying to accomplish.

Thank you

Kevin

On Mon, Oct 31, 2022 at 6:07 AM Giovanni Maruzzelli 
wrote:

> On Mon, Oct 31, 2022 at 1:59 PM Giovanni Maruzzelli 
> wrote:
>
>>
>> You can use the hashing Bogdan proposed, so ds_select will go to the same
>> machine because it gets the same result from hashing the same input. In
>> this case, you must find "something" (eg a cleaned TO for register and a
>> cleaned FROM for INVITE)
>>
>
> or cleaned TO and cleaned TO, for inbound calls
>
> -giovanni
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Loadbalancer for Registrations and calls

[Kevin Kennedy]

Sorry, sent by mistake
continuation of email. DIspatcher module.  Is this what you are referring
to? Or are you referring to something else.

   -

   *alg* - the algorithm(s) used to select the destination address
   (variables are accepted).
   -

  “0” - hash over callid
  -

  “1” - hash over from uri.
  -

  “2” - hash over to uri.
  -

  “3” - hash over request-uri.
  -

  “4” - round-robin (next destination).
  -

  “5” - hash over authorization-username (Proxy-Authorization or
  "normal" authorization). If no username is found, round robin is used.
  -

  “6” - random (using rand()).
  -

  “7” - hash over the content of PVs string. Note: This works only when
  the parameter hash_pvar is set.
  -

  “8” - the first entry in set is chosen.
  -

  “9” - The *pvar_algo_pattern* parameter is used to determine the load
  on each server. If the parameter is not specified, then the
first entry in
  the set is chosen.
  -

  “X” - if the algorithm is not implemented, the first entry in set is
  chosen.
  From what we have always seen on the SBC's is the best identifier for
   looking up the registration cache is the CONTACT header.  As this will have
   the TGRP and Trunk-Context in it.


On Mon, Oct 31, 2022 at 1:00 PM Kevin Kennedy  wrote:

> I am pretty new to Opensips, so maybe I am not understanding what you mean
> by hashing.  The only place I see hashing is on the dispatcher module
>
>
> On Mon, Oct 31, 2022 at 12:44 PM Giovanni Maruzzelli 
> wrote:
>
>> We all understood what you are doing and why
>>
>> It's just that... the answer is inside you! And it's wrong :) (famous
>> quote from an Italian comedian)
>>
>> answered from mobile, please pardon terseness and typos,
>> -giovanni
>>
>> On Mon, Oct 31, 2022, 20:41 Kevin Kennedy  wrote:
>>
>>> Thank you all for your responses.  Maybe I am going about this all
>>> wrong.  Maybe I can explain it better with a drawing of what I am trying to
>>> do.  I am trying to front end customers with Opensips to Load balance
>>> Registrations to 4 different SBC's.  These SBC's will have their own
>>> Registration cache and pass the Registration to the Application servers.  I
>>> need Opensips to send the INVITE/SUBSCRIBE to the SBC that it has sent the
>>> Registration to in order to match the Registration cache in that device.
>>> The only way I saw to do this was with Mid-Registrar and Dispatcher since
>>> Loadbalancer would not handle Registrations/Subscribes, etc.
>>>
>>> [image: image.png]
>>> Hopefully that can explain what I am trying to do better and help you
>>> understand what I am trying to accomplish.
>>>
>>> Thank you
>>>
>>> Kevin
>>>
>>> On Mon, Oct 31, 2022 at 6:07 AM Giovanni Maruzzelli 
>>> wrote:
>>>
 On Mon, Oct 31, 2022 at 1:59 PM Giovanni Maruzzelli 
 wrote:

>
> You can use the hashing Bogdan proposed, so ds_select will go to the
> same machine because it gets the same result from hashing the same input.
> In this case, you must find "something" (eg a cleaned TO for register and 
> a
> cleaned FROM for INVITE)
>

 or cleaned TO and cleaned TO, for inbound calls

 -giovanni

 ___
 Users mailing list
 Users@lists.opensips.org
 http://lists.opensips.org/cgi-bin/mailman/listinfo/users

>>>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Loadbalancer for Registrations and calls

[Kevin Kennedy]

I am pretty new to Opensips, so maybe I am not understanding what you mean
by hashing.  The only place I see hashing is on the dispatcher module


On Mon, Oct 31, 2022 at 12:44 PM Giovanni Maruzzelli 
wrote:

> We all understood what you are doing and why
>
> It's just that... the answer is inside you! And it's wrong :) (famous
> quote from an Italian comedian)
>
> answered from mobile, please pardon terseness and typos,
> -giovanni
>
> On Mon, Oct 31, 2022, 20:41 Kevin Kennedy  wrote:
>
>> Thank you all for your responses.  Maybe I am going about this all
>> wrong.  Maybe I can explain it better with a drawing of what I am trying to
>> do.  I am trying to front end customers with Opensips to Load balance
>> Registrations to 4 different SBC's.  These SBC's will have their own
>> Registration cache and pass the Registration to the Application servers.  I
>> need Opensips to send the INVITE/SUBSCRIBE to the SBC that it has sent the
>> Registration to in order to match the Registration cache in that device.
>> The only way I saw to do this was with Mid-Registrar and Dispatcher since
>> Loadbalancer would not handle Registrations/Subscribes, etc.
>>
>> [image: image.png]
>> Hopefully that can explain what I am trying to do better and help you
>> understand what I am trying to accomplish.
>>
>> Thank you
>>
>> Kevin
>>
>> On Mon, Oct 31, 2022 at 6:07 AM Giovanni Maruzzelli 
>> wrote:
>>
>>> On Mon, Oct 31, 2022 at 1:59 PM Giovanni Maruzzelli 
>>> wrote:
>>>

 You can use the hashing Bogdan proposed, so ds_select will go to the
 same machine because it gets the same result from hashing the same input.
 In this case, you must find "something" (eg a cleaned TO for register and a
 cleaned FROM for INVITE)

>>>
>>> or cleaned TO and cleaned TO, for inbound calls
>>>
>>> -giovanni
>>>
>>> ___
>>> Users mailing list
>>> Users@lists.opensips.org
>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>
>>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Loadbalancer for Registrations and calls

[Bogdan-Andrei Iancu]

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 
mailto:bog...@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
mailto:bog...@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 mailto:ayakim...@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
mailto:kennedy4...@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@lists.opensips.org

http://lists.opensips.org/cgi-bin/mailman/listinfo/users




-- 
С уважением,

Якимкин Алексей
___
Users mailing list
Users@lists.opensips.org 

Re: [OpenSIPS-Users] Loadbalancer for Registrations and calls

[Giovanni Maruzzelli]

On Mon, Oct 31, 2022 at 1:59 PM Giovanni Maruzzelli 
wrote:

>
> You can use the hashing Bogdan proposed, so ds_select will go to the same
> machine because it gets the same result from hashing the same input. In
> this case, you must find "something" (eg a cleaned TO for register and a
> cleaned FROM for INVITE)
>

or cleaned TO and cleaned TO, for inbound calls

-giovanni
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Loadbalancer for Registrations and calls

[Giovanni Maruzzelli]

On Mon, Oct 31, 2022 at 1:49 PM Giovanni Maruzzelli 
wrote:

> On Sun, Oct 30, 2022 at 6:19 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));
>>
>> You cannot use ds_select to send INVITE to where the REGISTER was
>

You can use the hashing Bogdan proposed, so ds_select will go to the same
machine because it gets the same result from hashing the same input. In
this case, you must find "something" (eg a cleaned TO for register and a
cleaned FROM for INVITE) that is exactly the same in REGISTER and INVITE to
use as base for the hashing. The hashing (like an MD5) will then be used to
send the method to the same machine (because the "md5" of the hash "base"
is the same (and will be the same only if the base is the same), it will go
to the same machine.


> You can make the kv-store visible to MI, and then ul_dump the AOR complete
> of kv-store
>
> Also, you can simply write in a memory hash or in a db table to which
> destination was the REGISTER going
>
> btw, I believe this architecture is fragile, you don't want INVITEs going
> to a destination related to the one REGISTER was, a lot of bad things can
> happen if you have such constraints.
> If you really really really want that, then just go for sharding based on
> domains or on users ranges, with some fallback schema
>
> -giovanni
>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Loadbalancer for Registrations and calls

[Giovanni Maruzzelli]

On Sun, Oct 30, 2022 at 6:19 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.
>
>
You cannot use ds_select to send INVITE to where the REGISTER was
You can make the kv-store visible to MI, and then ul_dump the AOR complete
of kv-store

Also, you can simply write in a memory hash or in a db table to which
destination was the REGISTER going

btw, I believe this architecture is fragile, you don't want INVITEs going
to a destination related to the one REGISTER was, a lot of bad things can
happen if you have such constraints.
If you really really really want that, then just go for sharding based on
domains or on users ranges, with some fallback schema

-giovanni

-- 
Sincerely,

Giovanni Maruzzelli
OpenTelecom.IT
cell: +39 347 266 56 18
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Loadbalancer for Registrations and calls

[Kevin Kennedy]

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 
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 
> 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  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 :
>>>
 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@lists.opensips.org
 http://lists.opensips.org/cgi-bin/mailman/listinfo/users

>>>
>>>
>>> --
>>> С уважением,
>>> Якимкин Алексей
>>> ___
>>> Users mailing list
>>> Users@lists.opensips.org
>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>
>>
>> ___
>> Users mailing 
>> listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Loadbalancer for Registrations and calls

[Bogdan-Andrei Iancu]

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 
mailto:bog...@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 mailto:ayakim...@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
mailto:kennedy4...@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@lists.opensips.org 
http://lists.opensips.org/cgi-bin/mailman/listinfo/users




-- 
С уважением,

Якимкин Алексей
___
Users mailing list
Users@lists.opensips.org 
http://lists.opensips.org/cgi-bin/mailman/listinfo/users



___
Users mailing list
Users@lists.opensips.org  
http://lists.opensips.org/cgi-bin/mailman/listinfo/users  





___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Loadbalancer for Registrations and calls

[Bogdan-Andrei Iancu]

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 > 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 mailto:kennedy4...@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@lists.opensips.org 
http://lists.opensips.org/cgi-bin/mailman/listinfo/users




-- 
С уважением,

Якимкин Алексей
___
Users mailing list
Users@lists.opensips.org 
http://lists.opensips.org/cgi-bin/mailman/listinfo/users



___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Loadbalancer for Registrations and calls

[Kevin Kennedy]

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  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 :
>
>> 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@lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>
>
> --
> С уважением,
> Якимкин Алексей
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Loadbalancer for Registrations and calls

[Alex]

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 :

> 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@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>


-- 
С уважением,
Якимкин Алексей
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users