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%2...
regards klaus
Good link.
Summarises everything in one place for quick reference.
On 18/12/06, Klaus Darilion klaus.mailinglists@pernau.at 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%2...
regards klaus
-- Klaus Darilion nic.at
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
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* <klaus.mailinglists@pernau.at mailto:klaus.mailinglists@pernau.at> 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 Users@openser.org <mailto:Users@openser.org> http://openser.org/cgi-bin/mailman/listinfo/users
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
On Wed, Dec 20, 2006 at 09:26:13AM -0500, Steve Blair wrote:
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
The best way use sipgrep (wrapper for ngrep)
http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/sip_router/utils/sipgrep/
:Steve
Wbr,
Also if you the have sip_trace module enabled and cdrtool you can see in the web the traces of incoming and outgoing messages as seen by the sip proxy:
https://secure.dns-hosting.info/CDRTool/sip-trace.phtml? cdr_source=sip_trace&callid=31d490ea478786da% 40bWlyY2VhLmRucy1ob3N0aW5nLmluZm8.&fromtag=605cc345&action=toggleVisibil ity&toggleVisibility=1&public=1
Adrian
On Dec 20, 2006, at 3:34 PM, Alexandr Dubovikov wrote:
On Wed, Dec 20, 2006 at 09:26:13AM -0500, Steve Blair wrote:
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
The best way use sipgrep (wrapper for ngrep)
http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/sip_router/utils/ sipgrep/
:Steve
Wbr,
Alexandr Dubovikov * baron@iRC RusNet * mailto:shurik@start4.info AD1-UANIC * ICQ: 122351182 * http://www.start4.info
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Adrian Georgescu wrote:
Also if you the have sip_trace module enabled and cdrtool you can see in the web the traces of incoming and outgoing messages as seen by the sip proxy:
https://secure.dns-hosting.info/CDRTool/sip-trace.phtml?cdr_source=sip_trace...
Hi Adrian!
Does this work only with the free version of CDRtool or only with the commercial one?
regards klaus
Adrian
On Dec 20, 2006, at 3:34 PM, Alexandr Dubovikov wrote:
On Wed, Dec 20, 2006 at 09:26:13AM -0500, Steve Blair wrote:
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
The best way use sipgrep (wrapper for ngrep)
http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/sip_router/utils/sipgrep/
:Steve
Wbr, --Alexandr Dubovikov * baron@iRC RusNet * mailto:shurik@start4.info AD1-UANIC * ICQ: 122351182 * http://www.start4.info
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Hi Klaus, it is only one version, which is GPL.
On Dec 20, 2006, at 5:05 PM, Klaus Darilion wrote:
Adrian Georgescu wrote:
Also if you the have sip_trace module enabled and cdrtool you can see in the web the traces of incoming and outgoing messages as seen by the sip proxy: https://secure.dns-hosting.info/CDRTool/sip-trace.phtml? cdr_source=sip_trace&callid=31d490ea478786da% 40bWlyY2VhLmRucy1ob3N0aW5nLmluZm8.&fromtag=605cc345&action=toggleVisi bility&toggleVisibility=1&public=1
Hi Adrian!
Does this work only with the free version of CDRtool or only with the commercial one?
regards klaus
Adrian On Dec 20, 2006, at 3:34 PM, Alexandr Dubovikov wrote:
On Wed, Dec 20, 2006 at 09:26:13AM -0500, Steve Blair wrote:
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
The best way use sipgrep (wrapper for ngrep)
http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/sip_router/utils/ sipgrep/
:Steve
Wbr, --Alexandr Dubovikov * baron@iRC RusNet * mailto:shurik@start4.info AD1-UANIC * ICQ: 122351182 * http://www.start4.info
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
-- Klaus Darilion nic.at