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 schrieb am Di., 19. Nov. 2019,
15:34:
> Actually same as d
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 , п
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 wrote:
>
>
> It’s more proof-of-concept, than other.
> Like what else ways I have built-in
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 , писал:
> Well, what is the nature of the dynamic routing you seek to accomplish? I
> cannot imagine dynamic distribution of registrati
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
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_ro
