[Asterisk-Dev] Extracting specific call from 'iax debug' on a busy server?

Kris Boutilier Kris.Boutilier at scrd.bc.ca
Fri Sep 10 11:51:02 MST 2004


> -----Original Message-----
> From: steve at daviesfam.org [mailto:steve at daviesfam.org] 
> Sent: September 10, 2004 11:35 AM
> To: Asterisk Developers Mailing List
> Subject: Re: [Asterisk-Dev] Extracting specific call from 
> 'iax debug' on a busy server?
> 
{clip}
> 
> Yeah - its a bit of a mess.  Jitter related stuff can be found with 
> grep 'Jitter: call=2'
> 
> For other stuff you do get a feel for the messages and how to 
> keep it all 
> straight after a while ;-)
> 

In your IAX2/Jitter debug procedure you recommended:

> To do that, in /etc/asterisk/logger.conf edit the debug line to be:
> debug => notice,warning,error,debug,verbose
> Then run asterisk like so:
> /usr/sbin/asterisk -vvvvvv -g  -dddddd -c 
> Then go "iax2 debug" at the CLI prompt.

I missed that so wasn't getting debug info, however this machine is
production and remote to me so running in console mode over SSH is not safe.
Is it ok to run backgrounded with those flags and just 'asterisk -r'?




More information about the asterisk-dev mailing list