[OpenSIPS-Users] dialplan module - dpid - could it be a string?

[Ben Newlin]

This sounds like it might be a good feature request [1] and I agree it sounds nice. I can’t offer any assistance in that direction at this time, but I wanted to say that we use M4 in our config scripts to allow us to define string constants like this and make the script more readable, among other reasons. Could be a good short-term workaround. We specifically use it to define string-based dialplan IDs for use in the script, just like this.

[1] https://github.com/OpenSIPS/opensips/issues/new?assignees=&labels=&template=feature_request.md&title=%5BFEATURE%5D

Ben Newlin

From: Users <users-bounces at lists.opensips.org> on behalf of Kingsley Tart <kingsley at dns99.co.uk>
Date: Tuesday, April 20, 2021 at 12:22 PM
To: OpenSIPS users mailling list <users at lists.opensips.org>
Subject: [OpenSIPS-Users] dialplan module - dpid - could it be a string?
I love the dialplan module and how the rules can be reloaded from a DB.

However, is there any reason why the dpid can't be a string instead of
an integer? (ie the value that's stored in the dialplan.dpid field).

I think it would be handy to be able to apply names to dialplan
rulesets as it would be more intuitive. If dpid could be a string, then
I could for example create a ruleset that I could refer to as
"uk_local_to_e164" instead of "7".

Could this be a thing?

--
Cheers,
Kingsley.


_______________________________________________
Users mailing list
Users at lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210420/2e32cf47/attachment.html>