<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title></title>
</head>
<body>
<div name="messageBodySection">
<div dir="auto">Actually same as dynamic routing of calls, but have same time-based routing in a case of internal servers set.
<div dir="auto">Like if we have planned maintenance and use time-based rules upfront.</div>
<div dir="auto">And to have sort of strip/add functions in one place. </div>
</div>
</div>
<div name="messageSignatureSection"><br />
<div dir="auto">Regards, Igor</div>
</div>
<div name="messageReplySection">19 нояб. 2019 г., 15:05 +0100, Alex Balashov <abalashov@evaristesys.com>, писал:<br />
<blockquote type="cite" class="spark_quote" style="margin: 5px 5px; padding-left: 10px; border-left: thin solid #1abc9c;">But what business need drives the desire for “complex scenarios” with registration routing?<br />
<br />
—<br />
Sent from mobile, with due apologies for brevity and errors.<br />
<br />
<blockquote type="cite" class="spark_quote" style="margin: 5px 5px; padding-left: 10px; border-left: thin solid #e67e22;">On Nov 19, 2019, at 9:01 AM, Igor Olhovskiy <igorolhovskiy@gmail.com> wrote:<br />
<br />
<br />
It’s more proof-of-concept, than other.<br />
Like what else ways I have built-in to get complex scenarios.<br />
<br />
Regards, Igor<br />
19 нояб. 2019 г., 14:52 +0100, Alex Balashov <abalashov@evaristesys.com>, писал:<br />
<blockquote type="cite" class="spark_quote" style="margin: 5px 5px; padding-left: 10px; border-left: thin solid #3498db;">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...<br />
<br />
—<br />
Sent from mobile, with due apologies for brevity and errors.<br />
<br />
<blockquote type="cite" class="spark_quote" style="margin: 5px 5px; padding-left: 10px; border-left: thin solid #d35400;">On Nov 19, 2019, at 8:35 AM, Igor Olhovskiy <igorolhovskiy@gmail.com> wrote:<br />
<br />
<br />
Hi!<br />
<br />
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<br />
<br />
drouting [drouting.c:567]: build_ruri(): stripping 0 makes username <> null<br />
drouting [drouting.c:970]: do_routing(): failed to build ruri<br />
<br />
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?<br />
<br />
Thanks, Igor<br />
_______________________________________________<br />
Kamailio (SER) - Users Mailing List<br />
sr-users@lists.kamailio.org<br />
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users<br /></blockquote>
<br />
_______________________________________________<br />
Kamailio (SER) - Users Mailing List<br />
sr-users@lists.kamailio.org<br />
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users<br /></blockquote>
_______________________________________________<br />
Kamailio (SER) - Users Mailing List<br />
sr-users@lists.kamailio.org<br />
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users<br /></blockquote>
<br />
_______________________________________________<br />
Kamailio (SER) - Users Mailing List<br />
sr-users@lists.kamailio.org<br />
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users<br /></blockquote>
</div>
</body>
</html>