<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">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.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">[1] <a href="https://github.com/OpenSIPS/opensips/issues/new?assignees=&labels=&template=feature_request.md&title=%5BFEATURE%5D">
https://github.com/OpenSIPS/opensips/issues/new?assignees=&labels=&template=feature_request.md&title=%5BFEATURE%5D</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="color:black">Ben Newlin </span><o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">Users <users-bounces@lists.opensips.org> on behalf of Kingsley Tart <kingsley@dns99.co.uk><br>
<b>Date: </b>Tuesday, April 20, 2021 at 12:22 PM<br>
<b>To: </b>OpenSIPS users mailling list <users@lists.opensips.org><br>
<b>Subject: </b>[OpenSIPS-Users] dialplan module - dpid - could it be a string?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">I love the dialplan module and how the rules can be reloaded from a DB.<br>
<br>
However, is there any reason why the dpid can't be a string instead of<br>
an integer? (ie the value that's stored in the dialplan.dpid field).<br>
<br>
I think it would be handy to be able to apply names to dialplan<br>
rulesets as it would be more intuitive. If dpid could be a string, then<br>
I could for example create a ruleset that I could refer to as<br>
"uk_local_to_e164" instead of "7".<br>
<br>
Could this be a thing?<br>
<br>
-- <br>
Cheers,<br>
Kingsley.<br>
<br>
<br>
_______________________________________________<br>
Users mailing list<br>
Users@lists.opensips.org<br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><o:p></o:p></p>
</div>
</div>
</body>
</html>