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 <kennedy4...@gmail.com> 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 <gmar...@gmail.com> > 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 <kennedy4...@gmail.com> 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 <gmar...@gmail.com> >>> wrote: >>> >>>> On Mon, Oct 31, 2022 at 1:59 PM Giovanni Maruzzelli <gmar...@gmail.com> >>>> 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