Hi Nick,
The linking between the dialplan and drouting must be done by you, at
script level, to reflect whatever you try to achieve - this is so
because of flexibility reasons.
Now imagine you use DR to determine what kind of number the user has
dialed - like national , international, etc (simply use dr for prefix
matching and put in the attribute of the rule some ID about the the type
of the number).
Hope this helps, if not, please come back with some more details on what
you are trying to do.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 01/08/2013 11:10 PM, Nick Khamis wrote:
Hello Everyone,
I already have all the dialplan directives defined and working fine
using the dialplan table. Now when trying to limit the individual's
ability to call, for example, (local, international, and extensions),
I am not seeing the foreign key relationship between dialplan and
dr_rules and conversely dr_groups.
Is this functionality done in the background, or do I have to redefine
all the dialplan digitmaps again via the "prefix" field in dr_rules?
Also, is dr_groups more like dr_users since we are inserting
individual users in the table, or did I mess that up too :)?
On a slightly unrelated, is it common practice to completely replace
the "REGISTER", and "INVITE" based authentication for routing rights?
Or is there gaping security breach using that method?
Thanks in Advance,
Nick.
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
