Asterisk.conf debug


#1

Hello,
I would like to get more debug information in my messages log file. I saw on one of the development threads that debug variable was added to the asterisk.conf file. However, there is no informaion on what are the values expected or the variables needed to increase deug information in the messages log file. Please help.
Thanks


#2

Probably what you need is to start Asterisk with the -d option. From the Asterisk man page:

-d Enable extra debugging statements.


#3

When I do this, the asterisk doesn’t go in the background. I would like to see the debug information in the messages.


#4

Try uncommenting this line in /etc/asterisk/logger.conf :

;debug => debug

or this one:

;full => notice,warning,error,debug,verbose


#5

[quote=“WillKemp”]Try uncommenting this line in /etc/asterisk/logger.conf :

;debug => debug

or this one:

;full => notice,warning,error,debug,verbose[/quote]

Hi, I tried it, it still gives me generic information no debug information. Thanks, any other suggestions. I am using the 1.2 beta-1


#6

Well, it works for me! I’m using v1.2.

I uncommented the “full” line in logger.conf and that writes debug information to /var/log/asterisk/full. I also uncommented the following line:

syslog.local0 => notice,warning,error,debug

and added this line to /etc/syslog.conf :

local0.* /var/log/asterisk/syslog

and did

killall -1 syslogd

to get syslogd to re-read it’s config file. Then i get debug output in /var/log/asterisk/syslog.


#7

[quote=“WillKemp”]Well, it works for me! I’m using v1.2.

I uncommented the “full” line in logger.conf and that writes debug information to /var/log/asterisk/full. I also uncommented the following line:

syslog.local0 => notice,warning,error,debug

and added this line to /etc/syslog.conf :

local0.* /var/log/asterisk/syslog

and did

killall -1 syslogd

to get syslogd to re-read it’s config file. Then i get debug output in /var/log/asterisk/syslog.[/quote]

Great, I wasn’t aware of the existence of this file. Yes, I see some debug information. Do you know if there is anyway to get the same debug information received when asterisk -vvvvvvvvvvvvvvr (or more vs) from the console. I am not seeing the calls getting initiated and hangup. I am using asterisk at home and I keep getting complains that once in a while, when making a call a busy signal is received. I am trying to put my hands on this problem. Any suggestions? Thanks for your reply.


#8

Well, i didn’t know when i read your question, but i do now! It’s not really all that hard to find this sort of information sometimes…

If you have a read of the README.asterisk.conf file in the asterisk/doc subdirectory in the Asterisk sources, you’ll find it’s quite interesting. There are a lot of things that can go in asterisk.conf that aren’t in the file provided with the configs.

The documents in the asterisk/doc directory have got a lot of useful information in them. Grep’ing for “debug” in those files helped me find what i was looking for.

As far as answering your question goes, the solution would seem to be to put something similar to this in asterisk.conf :

[options]
debug=3 ; Debug: “No” or value (1-4)

By the way, does that many "v"s really have any effect?


#9

Well, i didn’t know when i read your question, but i do now! It’s not really all that hard to find this sort of information sometimes…

If you have a read of the README.asterisk.conf file in the asterisk/doc subdirectory in the Asterisk sources, you’ll find it’s quite interesting. There are a lot of things that can go in asterisk.conf that aren’t in the file provided with the configs.

The documents in the asterisk/doc directory have got a lot of useful information in them. Grep’ing for “debug” in those files helped me find what i was looking for.

As far as answering your question goes, the solution would seem to be to put something similar to this in asterisk.conf :

[options]
debug=3 ; Debug: “No” or value (1-4)

By the way, does that many "v"s really have any effect?[/quote]

Thank you very much, that did it. I didn’t know about the README files, this is quiet interesting. I really appreciate the help.