Summary:ASTERISK-08911: GUI access to enable debug logging
Reporter:Steve Langstaff (srl100)Labels:
Date Opened:2007-03-01 04:00:45.000-0600Date Closed:2007-05-16 17:30:33
Versions:Frequency of
Description:With the introduction of the GUI it's simple to do quite a few things with AsteriskNow, but as soon as you have to get a debug trace you are dropped into learning about how to login to the linux command prompt, stop and restart asterisk with different options, sudo, tee etc.

How about a "restart asterisk with logging to file" option from the gui, with the appropriate debug and verbose levels settable, and access to the subsequent logged file?
Comments:By: Serge Vecher (serge-v) 2007-03-01 09:25:36.000-0600

yeah, I'd love the sip debug log I always ask for be to be a bit more automated.

1) Prepare test environment (reduce the amount of unrelated traffic on the server);
2) Make sure your logger.conf has the following line:
  console => notice,warning,error,debug
3) restart Asterisk with the following command:
  'asterisk -Tvvvvvdddddngc | tee /tmp/verbosedebug.txt'
4) Enable SIP transaction logging with the following CLI commands (1.4/trunk commands in parenthesis):
set debug 4 (core set debug 4)
set verbose 4 (core set verbose 4)
sip debug (sip set debug)
5) Reproduce the problem
6) Trim startup information and attach verbosedebug.txt to the issue.

By: Brandon Kruse (bkruse) 2007-05-03 17:06:55

Use feditor.html (options->advanced->File Editor) and edit logger.conf



By: Pari Nannapaneni (pari) 2007-05-16 17:30:32

There is a file editor and CLI added recently to the GUI.

Anyway, the bug tracker is not a place for new feature requests.

We request you to Please discuss any new gui features on
the gui mailing list <asterisk-gui@lists.digium.com>

If you have a patch for a tweak or a feature you can use the
bug tracker to submit the code. But feature requests with out
contributing any code/patches should be out of bug tracker.