*
>
> Impala Networks
>
> P: 505.327.7300
>
> ** **
>
> *From:* Anton Kvashenkin [mailto:anton.juga...@gmail.com]
> *Sent:* Thursday, October 27, 2011 8:27 AM
>
> *To:* Asterisk Users Mailing List - Non-Commercial Discussion
> *Subject:* Re: [asterisk-users] Tips
m: Anton Kvashenkin [mailto:anton.juga...@gmail.com]
Sent: Thursday, October 27, 2011 8:27 AM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] Tips & best practices for asterisk
troubleshooting & parsing logs
Capture pcap with tshark or tcpdump for
rom: Sammy Govind [mailto:govoi...@gmail.com]
Sent: Wednesday, October 26, 2011 11:09 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] Tips & best practices for asterisk
troubleshooting & parsing logs
It was a challenge to read through a
Capture pcap with tshark or tcpdump for the future analysis with wireshark.
Ngrep is also handy tool for captaring, say, INVITE. You can use grep like
this: tail -f /var/log/asterisk/full | egrep --color -w
'chan_sip.*SIP/911|pbx.*SIP/911'
Interesting technique from Astresk Cookbook, "Debugging dia
It was a challenge to read through all the interesting experience you've
shared over here. I don't know what others may be using for parsing the logs
beautifully and make them usable. What I would recommend you at the very
beginning ,since you mentioned using egrep, is figure out the Channel
identi
Hello all,
I have been running asterisk systems since summer of 2008. I do not claim to be
an expert. But I have worked through many issues during this period. I have
setup & manage 5 systems, which serve 6 companies total (and of course process
calls for all of the people they do business with
