[SR-Users] Dynamic routing and REGISTER

Karsten Horsmann khorsmann at gmail.com
Wed Nov 20 11:21:36 CET 2019


Hi Igor,

I would then more test dmq and dmq_usrloc modules. Therefore you can hold
the register state on multiple Kamailio at the same time.

https://kamailio.org/docs/modules/devel/modules/dmq_usrloc.html

Cheers
Karsten

Igor Olhovskiy <igorolhovskiy at gmail.com> schrieb am Di., 19. Nov. 2019,
15:34:

> Actually same as dynamic routing of calls, but have same time-based
> routing in a case of internal servers set.
> Like if we have planned maintenance and use time-based rules upfront.
> And to have sort of strip/add functions in one place.
>
> Regards, Igor
> 19 нояб. 2019 г., 15:05 +0100, Alex Balashov <abalashov at evaristesys.com>,
> писал:
>
> But what business need drives the desire for “complex scenarios” with
> registration routing?
>
>> Sent from mobile, with due apologies for brevity and errors.
>
> On Nov 19, 2019, at 9:01 AM, Igor Olhovskiy <igorolhovskiy at gmail.com>
> wrote:
>
> 
> It’s more proof-of-concept, than other.
> Like what else ways I have built-in to get complex scenarios.
>
> Regards, Igor
> 19 нояб. 2019 г., 14:52 +0100, Alex Balashov <abalashov at evaristesys.com>,
> писал:
>
> Well, what is the nature of the dynamic routing you seek to accomplish? I
> cannot imagine dynamic distribution of registrations being very complex, or
> informed by the kinds of LCR-type weights and metrics that drive the need
> for drouting and friends...
>
>> Sent from mobile, with due apologies for brevity and errors.
>
> On Nov 19, 2019, at 8:35 AM, Igor Olhovskiy <igorolhovskiy at gmail.com>
> wrote:
>
> 
> Hi!
>
> I’m trying to get `drouting` module working for REGISTER. But seems it’s
> not passing one of internal checks, cause in REGISTER R-URI does not
> contains username and I’m getting errors
>
> drouting [drouting.c:567]: build_ruri(): stripping 0 makes username <> null
> drouting [drouting.c:970]: do_routing(): failed to build ruri
>
> So, as I got, this module is mainly for calls (means INVITE) routing,
> rather than to use it like one more dispatcher, or it’s also a way to
> handle this part here?
>
> Thanks, Igor
> _______________________________________________
> Kamailio (SER) - Users Mailing List
> sr-users at lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
>
> _______________________________________________
> Kamailio (SER) - Users Mailing List
> sr-users at lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
> _______________________________________________
> Kamailio (SER) - Users Mailing List
> sr-users at lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
>
> _______________________________________________
> Kamailio (SER) - Users Mailing List
> sr-users at lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
> _______________________________________________
> Kamailio (SER) - Users Mailing List
> sr-users at lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20191120/58f3e560/attachment.html>


More information about the sr-users mailing list