On Nov 9, 2007 1:11 AM, Philip Prindeville
[EMAIL PROTECTED] wrote:
For someone that's network-aware, but hasn't sat down and plowed through
umpteen SIP-related RFC's and memorized the standards, is there a good
primer on troubleshooting SIP issues?
It's true that using Ethereal (is that what
On Mon, Nov 12, 2007 at 10:20:16AM +0100, randulo wrote:
It's true that using Ethereal (is that what Wireshark is nowadays?)
Ethereal was the original name of Wireshark.
--
Tzafrir Cohen
icq#16849755 jabber:[EMAIL PROTECTED]
+972-50-7952406
I thought Wireshark was the cute Mac OS X name.
On Nov 12, 2007 10:32 AM, Tzafrir Cohen [EMAIL PROTECTED] wrote:
On Mon, Nov 12, 2007 at 10:20:16AM +0100, randulo wrote:
It's true that using Ethereal (is that what Wireshark is nowadays?)
Ethereal was the original name of Wireshark.
--
And by the way, other than a dump, I'm surprised no one suggested
studying the source code. However, I don't think either would be as
useful as a good paper about these SIP transactions, especially an
asterisk-centric one that could even mention differences in newer
versions of asterisk.
On 12/11/2007, randulo [EMAIL PROTECTED] wrote:
I thought Wireshark was the cute Mac OS X name.
The author changed the name of the codebase last year due to employment changes:
http://en.wikipedia.org/wiki/Wireshark#History
Andrew
--
Linux supports the notion of a command line or a shell for
Brilliant program, whatever it's called this week.
http://www.wireshark.org/faq.html#q1.2
http://en.wikipedia.org/wiki/Wireshark#History
___
--Bandwidth and Colocation Provided by http://www.api-digital.com--
asterisk-users mailing list
To
For general SIP understanding, there's also Sip Scenario from IPtel (
http://www.iptel.org/~sipsc/ ). It will generate sort of human-readable
web stuff from captures, allowing you to click on the graphical portions
of the call and see the actual SIP packets that correspond to that.
N.
Philip Prindeville wrote:
snip /
You're missing the point. There's knowing *what* you're seeing, and
then there's knowing *why* you're seeing it.
The two are not the same.
Agreed, but the knowledge you will gain from working it out will far
exceed that which you might get by
if your router and UA have syslog facility you can use RouterSyslog also.
You can use Cain and Able with wireshark for switched network.
Thanks,
Vivek
On 11/9/07, Alan Lord [EMAIL PROTECTED] wrote:
Steve Edwards wrote:
snip /
Examples of what I'd like to see:
1) A SIP telephone
PROTECTED] [mailto:asterisk-users-
[EMAIL PROTECTED] On Behalf Of Philip Prindeville
Sent: Thursday, November 08, 2007 4:11 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: [asterisk-users] Wanted: tutorial on troubleshooting SIP issues
For someone that's network-aware
On Nov 8, 2007 7:11 PM, Philip Prindeville
[EMAIL PROTECTED] wrote:
Anyway, pointers for someone wanting to learn to quickly diagnose SIP
conversations would be great.
Read rfc2543, rfc3261 rfc3265. Otherwise what you want to do is akin
to trying to diagnose a nuclear reactor and not wanting
On Fri, 9 Nov 2007, [EMAIL PROTECTED] wrote:
On Nov 8, 2007 7:11 PM, Philip Prindeville
[EMAIL PROTECTED] wrote:
Anyway, pointers for someone wanting to learn to quickly diagnose SIP
conversations would be great.
Read rfc2543, rfc3261 rfc3265. Otherwise what you want to do is akin
to
Steve Edwards wrote:
snip /
Examples of what I'd like to see:
1) A SIP telephone registering successfully.
2) A SIP telephone failing to register for reasons x, y, and z.
snip /
I'm sorry but I don't see this as being very hard. Just install
Wireshark and do it yourself...
Alan
Alan Lord wrote:
Steve Edwards wrote:
snip /
Examples of what I'd like to see:
1) A SIP telephone registering successfully.
2) A SIP telephone failing to register for reasons x, y, and z.
snip /
I'm sorry but I don't see this as being very hard. Just install
Wireshark and do
, November 09, 2007 15:39
To: asterisk-users@lists.digium.com
Subject: Re: [asterisk-users] Wanted: tutorial on troubleshooting SIP
issues
Steve Edwards wrote:
snip /
Examples of what I'd like to see:
1) A SIP telephone registering successfully.
2) A SIP telephone failing to register
For someone that's network-aware, but hasn't sat down and plowed through
umpteen SIP-related RFC's and memorized the standards, is there a good
primer on troubleshooting SIP issues?
I'm seeing a lot of NOTIFY/603 messages on my network between Asterisk
and my Sipura 942's, for instance...
Not
16 matches
Mail list logo
