Philip Prindeville wrote: > So, how does one debug Asterisk configuration issues, like dialplans and SIP > configs? > > The common CLI commands work well. Sip show peers is very useful
"Set verbose 4" ( or pick a number ) will show some of what is going on during a call that may help simple dialplan issues. > I've connected on the console with "asterisk -r -c", but I see a lot of > flurries of "NOTIFY" messages that make it hard to see useful > information Some of that can be disabled or changed in logger.conf > (I guess that's how the "qualify" attribute works) when I > have "sip debug" turned on. > SIP is wordy, isn't it? > Also, I've seen that you can use the argument to NoOp() to generate > tracing, That does show up when the console verbose is set to something other than zero, and I use SSH so I can easily scroll back though and hopefully spot something. > but with the default syslog values on AstLinux, that doesn't work. > > How do you configure syslogd? It's part of that busybox weirdness. :-) > > Isn't that documented in busybox? Of course there are many flavors of busybox All in all, AstLinux is damn impressive running with such minimal resources. I am very pleased I found it! John Novack -- Dog is my co-pilot ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
