[asterisk-bugs] [Asterisk 0013016]: [patch] new CLI commands for handling dialplan variables and name standartization for the old ones

noreply at bugs.digium.com noreply at bugs.digium.com
Fri Jul 11 08:53:01 CDT 2008


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13016 
====================================================================== 
Reported By:                caio1982
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   13016
Category:                   Core/PBX
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 128638 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             07-07-2008 15:16 CDT
Last Modified:              07-11-2008 08:53 CDT
====================================================================== 
Summary:                    [patch] new CLI commands for handling dialplan
variables and name standartization for the old ones
Description: 
Some commands like 'core set global' should actually be called 'dialplan
set global' as they deal with dialplan variables directly (they even state
that in their help messages), so I decided to change them after commenting
about it on #asterisk-dev. I'm not sure about the consequences of it since
a deprecated warning should be printed, but I will let it to someone more
experienced to decide.

Since there are CLI commands to set new global and per channel variables I
also decided to create equivalent ones to unset these variables as they'd
stay in memory forever until a reload or restart is executed. Not good, now
I can unset them :-)

Ultimately there was not a way to list all those per channel variables set
with 'dialplan set chanvar <channel> <name> <value>', except parsing the
very long output of DumpChan(). I created a command called 'dialplan show
chanvar <channel>', using the same idea from 'show globals' and dumping all
variables associated with the given channel.
====================================================================== 

---------------------------------------------------------------------- 
 caio1982 - 07-11-08 08:53  
---------------------------------------------------------------------- 
In my new patch I've added the deprecated commands mvanbaak, thanks for
reminding me :-)

Corydo76, the same issue of unset variables could happen if someone just
use the standard set command to change its value to an empty string too.
Isn't the same side effect but with an already existing command?

It would possibly be correct to not let the set command set an empty value
then. I can add it to my new patch before uploading it, do you think it's
better? 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
07-11-08 08:53  caio1982       Note Added: 0090076                          
======================================================================




More information about the asterisk-bugs mailing list