[asterisk-dev] Asterisk 11 and console verbosity

[Pavel Troller]

Hi Tilghman,
  
> On Sun, Dec 2, 2012 at 1:51 AM, Pavel Troller <patrol at sinus.cz> wrote:
> > Hi!
> >   Since a recent SVN update, something has changed in the "core set verbose"
> > command processing. If I understand it right, individual verbosities have been
> > implemented for remote eonsole clients. Very cool! But I'm using a CLI alias
> > for this command, and now the expanded form of the command and the alias do
> > different things, which is weird:
> >
> > arcus*CLI> verbose 3
> > Verbosity was 0 and is now 3
> > arcus*CLI> verbose 0
> > Verbosity is now OFF
> > arcus*CLI> core set verbose 3
> > Set remote console verbosity to 3
> > arcus*CLI> core set verbose 0
> > Set remote console verbosity to 0
> > arcus*CLI> cli show aliases
> > Alias Command                                      Real Command
> > ...
> > verbose                                            core set verbose
> > ...
> >
> >   When the aliased form is used, even it writes "Verbosity was 0 and is now x",
> > nothing changes in a real verbosity output for the particular console, but it
> > changes verbosity in the "main" local console (even if invoked remotely). To
> > change the remote console verbosity, one has to use the expanded command syntax
> > (and it costed me a lot of time to discover it :-) ).
> >
> > Is it a bug, or still unfinished work ?
> 
> Aliasing was not taken into account when it was written:
> 
> https://issues.asterisk.org/jira/browse/ASTERISK-20281

I can see it, sorry that I didn't browse Jira first.

However, I have another problem, which I really tried to find in Jira but
unsuccessfully.
  When the traffic processed by the system is high (more than 3 - 5 CAPS) and
the dialplan is not the simplest one (for example, on one of our gateways 
every call runs through cca 800 - 1200 lines of the dialplan), the remote
console prompt with the whole edit line starts to flicker and sometimes it
disappears for a fraction of a second (of course even with a zero verbosity).
Writing commands is very unpleasant in this case, as the reaction is also
delayed, and of course it also generates a lot of network traffic, just by
sending the clearing escape code and the prompt (with possibly longer and
longer edit line) again and again. 
  Is it a know issue planned to be fixed ? Or shall I create a Jira issue for
it ? From my point of view, it's more serious than the aliasing issue.

With regards,
  Pavel