> Thanks for that Rich.  Etheral trace is going to be almost impossible 
> for various reasons, but will try the other two options.
> 
> Can't find much online re. debugging - any chance of killing the box by 
> turning this on?
> 
> SIP show channels and the various CAPI show commands do not show 
> anything out of the ordinary when the problem occurs.

In order for anyone to help identify the noise problem, you really
are going to have to find a way to capture some data, otherwise
we're all spinning our wheels and guessing.

To implement debugging, look at /etc/asterisk/logger.conf and add
the keyword 'debug' like:
 messages => notice,warning,error,debug
Adding that keyword requires that * be stopped and restarted to take
effect. That tells asterisk to log all debug statements (that are
embedded in asterisk source code) to write to /var/log/asterisk/debug 
file.

That debug file will grow to a very large size rather quickly, so
you need to pay attention to available disk space, etc.

When the noise problem occurs, note the specific system "time", and
take a look at /var/log/asterisk/debug to see what was happening
around that time. Once you've captured at least some data, you may
want to remove the debug statement.

If you haven't tried some of the other cli debug tools, you might
want to do "help sip debug", "help rtp debug", etc.

If you can't run ethereal on the system with the problem, there are
other tools like tcpdump, etc, that can be used to capture packets.


_______________________________________________
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Reply via email to