RTP is a pretty simple protocol, but meshing the rtp dissector with a
hybrid media/signalling proto like IAX2 might prove troublesome. My
thought is that
writing an IAX2 dissector from scratch shouldn't be too hard. The only
drawback is that you'll miss the built-in RTP stream decoding that
Wireshark provides because
the built-in functionality of tying an RTP stream to a signalling setup
requires you pass the IP and Port of the RTP stream. Since this is the
same as the signalling
in IAX2 I can't see how this will work easily.
Chad Singer
Software Developer
Cypress Communications
Carlos G Mendioroz wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I want to add the capability of "analysing" IAX2 streams much like
RTP streams.
There are a set of cool features there like doing jitter analysis and
stream playback.
Now, IAX2 actually has two parts to it, one is signalling and the other
is transport. And in it's transport role it is very much like RTP.
My idea is to replicate RTP to handle IAX2 as a VOIP transport proto,
and would like to know what way would be cosidered best by the
established style:
- - replicate and have a IAX2 dedicated code with much the same
functionality.
or
- - reuse the code and make it RTP/IAX2 capable.
or some other that I'm not aware of.
I see some advantages to one and to the other. I'm inclined to the
second (simplest code, least side effects although may be more expensive
to mantain and larger code base).
Any hard opinion in one way or the other ?
- --
Carlos G Mendioroz <tron@xxxxxxx>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAklzbSUACgkQ7qM4U9dTH3/eKwCgi2u2yuob5Xdm0L1N+j9teQEu
b+oAn2d7MF/el2XX88fbShbSb68YBEow
=zVHj
-----END PGP SIGNATURE-----
___________________________________________________________________________
Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives: http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
