|Summary:||ASTERISK-21921: Verbose() ignores remote console VERBOSE message verbosity|
|Reporter:||D'Arcy Cain (DruidZ)||Labels:|
|Date Opened:||2013-06-19 15:01:27||Date Closed:||2013-09-18 09:03:19|
|Environment:||NetBSD 6.0.1 (GENERIC) amd64||Attachments:|
|Description:||Discussed on IRC with newtonr who suggested I report this.
In my dialplan I have a command to execute "same => n,Verbose(3,Hello world)". In logger.conf I set console to "notice,warning,error,verbose" and verbose to 3. I even run "core set verbose 3" in the CLI. When I call the extension it does not output the string. It does work if I call it as "Verbose(0, ..." though.
|Comments:||By: Michael L. Young (elguero) 2013-06-20 09:05:56.936-0500|
Its kind of weird that your priority jumped to 4.
-- Executing [322@LocalSets:2] Verbose("SIP/6477957868-00000001", "3,Hello world") in new stack
-- Executing [322@LocalSets:4] Hangup("SIP/6477957868-00000001", "") in new stack
Can you attach a debug log? Hopefully you can get debug info, https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information
Can you attach the output of "core show settings"?
I have tested out the same settings that you mention in the description plus the dial plan on 11.3 and on trunk. I have been unable to reproduce this issue.
When you say,
In logger.conf I set console to "notice,warning,error,verbose" and verbose to 3
What do you mean by "and verbose to 3"? Can you show us maybe by attaching your logger.conf file?
By: D'Arcy Cain (DruidZ) 2013-06-20 09:34:14.434-0500
Sorry, priority jumped to 4 because I had a more complicated Verbose() call that I removed from the output for clarity.
http://darcy.druid.net/extension_state_issue.txt has my modified extension.conf, sip.conf (sanitized) and logger.conf as well as the actual output when I dial the extension.
By: Michael L. Young (elguero) 2013-06-20 10:03:05.511-0500
What does "core show settings" give you?
In logger.conf, this is not valid BTW.
verbose => 3
What you want is:
console => notice,warning,error,verbose(3)
By: D'Arcy Cain (DruidZ) 2013-06-20 10:50:18.978-0500
I have updated http://darcy.druid.net/extension_state_issue.txt with "core show settings".
Note, before we close this jira I will attach the final version of that file for historical reference.
As for the logger.conf change, I had that string in an earlier attempt at logging. I set it back to that. No change to the output.
By: Michael L. Young (elguero) 2013-06-20 11:31:31.567-0500
"core show settings" shows this:
Try verbose = 3 in asterisk.conf file and reload asterisk. See if that gets the verbosity working.
verbose = 3
;debug = 3
By: D'Arcy Cain (DruidZ) 2013-06-20 14:01:07.625-0500
Yes, that works but isn't "core set verbose 3" in the CLI supposed to do that?
By: Michael L. Young (elguero) 2013-06-20 14:16:49.756-0500
That just affects the remote console but doesn't affect the overall Asterisk system verbosity.
Personally, I think this has been a source of confusion for many in version 11. The remote console verbosity level doesn't affect the Asterisk verbosity settings and then when using Verbose, it is only looking at the Asterisk verbosity setting not the console verbosity. Also, when the remote console session ends, the next time you connect through a remote console, the verbosity goes back to the default level (that was set in logger.conf).
By: Rusty Newton (rnewton) 2013-06-20 17:57:36.298-0500
Yeah as shown with ASTERISK-21122 and ASTERISK-20654 at ASTERISK-20770 there is some potential for confusion.
Sounds like Verbose() needs to be addressed here at least. Or at least this needs to be taken into consideration for whoever looks at the other issues.
By: Michael L. Young (elguero) 2013-08-29 19:46:43.127-0500
Rusty, was this issue just taken care of by an internal issue? AST-1193 and https://reviewboard.asterisk.org/r/2798/
It looks like it may have been and therefore this issue, as well as the other issues you noted in your comment, could possibly be closed out.
By: Rusty Newton (rnewton) 2013-08-29 20:22:08.887-0500
Michael, I do believe it should. If you or the reporter can verify then we can close it out. I won't have time to test it until maybe later next week. I'll also point it out to Kevin Harwell to see which Verbosity related issues he thinks it will affect, as there is about five or six in JIRA floating around.
By: Kevin Harwell (kharwell) 2013-08-30 15:14:35.597-0500
I believe AST-1193 has fixed this issue as well. A simple test seems to output the expected message. However someone else may want to also verify.