[asterisk-bugs] [Asterisk 0010847]: executing CLI command from command line have bad verbosity

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10847 
====================================================================== 
Reported By:                atis
Assigned To:                qwell
====================================================================== 
Project:                    Asterisk
Issue ID:                   10847
Category:                   General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:            1.4.10  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             09-28-2007 13:42 CDT
Last Modified:              10-04-2007 02:42 CDT
====================================================================== 
Summary:                    executing CLI command from command line have bad
verbosity
Description: 
I have asterisk running with -vvvd. When i execute command from command
line with "-rx" i get "Verbosity is at least 3" all the times, and
sometimes i get output of CLI for some period (larger when asterisk is
under load).

I would generally expect the "-rx" to have executed with verbosity 0 and
debug 0. If i would want to add some verbosity i would do "-v" and "-d" as
much as i need.

There is option "-m" that is supposed to mute CLI output, but it doesn't
seems to work.


====================================================================== 

---------------------------------------------------------------------- 
 jamesgolovich - 10-04-07 02:42  
---------------------------------------------------------------------- 
I've got this pretty much solved, but I'm curious what the preferred action
of -m is.  Like qwell said if you start up the main console with -m then
all of the new remote consoles start up muted.

If you start up a remote console with -m, it looks like its supposed to
print an error message saying that its muted but it really tries to send
that message to the other side.

My opinion of how this should work would be to get rid of the -m usage
from the main console (unless it gets made to actually mute the main
console) and make it so that if a remote console is called with -m with
will mute its output.

The patched I attached does this.  If we want to keep the existing odd
behavior, then all the muting commands will have to be extended so we can
explicitly set muting on/off rather than just toggle back and forth. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
10-04-07 02:42  jamesgolovich  Note Added: 0071431                          
======================================================================