I have console debugging enabled in logger.conf: console => notice,warning,error,debug
Then a issue de command: core set debug 100 manager.c
To see only debugging messages from AMI.
But It shows nothing!!!
And then if I do: core set debug 1
Then I can see managar.c debug info, BUT if lots of other debug from all other files.
How to see only manager.c (or any other ONE file) debug info?
(I'm using asterisk 1.8) Thanks, Gabriel
I have an Asterisk server running 220.127.116.11, where I can't seem to get
the increased logging to save to the /var/log/asterisk/messages file.
I have tried using the standard "core set debug 10" and "core set
verbose 10", as well as specifically pointing it to the filename with
"core set debug 10 /var/log/asterisk/messages". Still, only the most
serious errors are being reported to the messages log file. It seems to work fine with my other Asterisk running 18.104.22.168. Is
there something else that I'm missing? Dean Hoover
On 03/21/2011 06:49 PM, Dan Austin wrote:
> I just finished a fresh install of 22.214.171.124 at home using the packages
> Digium hosts.
> After correcting a number of typo/config’o error that had crept in
> over the years, I thought I had everything working.
> My wife just complained that she cannot call her mother (who is using an
> old IAX hardphone I left for her).
> After turning up the logging level I see-
Hey guys I was hoping I could get a few pointers on a problem I have been
trying to debug for the last couple of months regarding asterisk AGI scripts
and unexpected termination.
I have this agi script that accepts incoming faxes using RxFax on the latest
asterisk 1.4 branch. Its written with perl and it works fine except for one
line that causes the entire script to terminate unexpectedly. The script always terminates at the point where I use the 'system' command
or backticks to run a system command.