Hi Ben,
Do not use built-in support for caller group as it does not serve your
purpose.
My suggestion is to create in DR a separate set of rules (with prefixes)
to translate from prefix to a routing group (to be use in the second
step for routing callee prefix based). In the first step, use DR without
setting GW param and put the routing group into rule attrs.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 13.08.2015 17:03, Newlin, Ben wrote:
Bogdan,
Thanks for the reply. I had considered something similar to what you
suggested using the Dialplan module to convert prefixes to groups and
then performing drouting according to the group. Is that what you mean
or is there some way to do that first translation (prefix to group) in
drouting as well? From what I could see in the documentation, the
drouting module only matches the full user in order to determine the
group, not a prefix.
Ben Newlin
From: <users-boun...@lists.opensips.org
<mailto:users-boun...@lists.opensips.org>> on behalf of Bogdan-Andrei
Iancu
Reply-To: OpenSIPS users mailling list
Date: Wednesday, August 12, 2015 at 2:40 AM
To: OpenSIPS users mailling list, "Newlin, Ben"
Subject: Re: [OpenSIPS-Users] CARRIERROUTE module
Hi Ben,
The carrierroute module is not maintained (for like 6 years).
Still, if you want to do a routing based on both caller and caller
number, you can do it with the drouting module. Use a set of prefixes
to translate the caller prefix into a kind of routing group , which
can be used again with drouting as set for searching the callee
prefix. Basically you do 2 droutings, one for caller, one for callee.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 11.08.2015 18:23, Newlin, Ben wrote:
Hi all,
We have some interest in possibly using the CARRIERROUTE module
instead of DROUTING as it allows prefix matching of the originating
number as well as the destination, whereas DROUTING must match the
originating user exactly. However, we noticed that the CARRIERROUTE
module is labeled as alpha, even though it has existed in OpenSIPS
for many years and many releases.
Is there some reason this module is still alpha? Is it considered to
be unstable for production use?
Ben Newlin
_______________________________________________
Users mailing list
Users@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
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
