Thanks Klaus. I've found the ngrep is also a very handy tool
(http://sourceforge.net/projects/ngrep/)
ngrep -p -q -t -n 200 -W byline 34820 port 5060 - show messages
containing "34820"
ngrep -p -q -t -n 200 -W byline REGISTER port 5060 - show REGISTER
messages
:Steve
Max Gregorian wrote:
Good link.
Summarises everything in one place for quick reference.
On 18/12/06, *Klaus Darilion* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
Hi!
As SIP debugging often includes low-level network debugging I
think this
tutorial can give some valuable inputs how to debug network problems.
http://penguin-it.co.il/presentations/BrainShare2006/Troubleshooting%20LAN%20hardware%20and%20connectivity%20issues%20on%20SUSE%20Linux%20Enterprise%20Server%209.pdf
<http://penguin-it.co.il/presentations/BrainShare2006/Troubleshooting%20LAN%20hardware%20and%20connectivity%20issues%20on%20SUSE%20Linux%20Enterprise%20Server%209.pdf>
regards
klaus
--
Klaus Darilion
nic.at <http://nic.at>
_______________________________________________
Users mailing list
[email protected] <mailto:[email protected]>
http://openser.org/cgi-bin/mailman/listinfo/users
------------------------------------------------------------------------
_______________________________________________
Users mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/users
