You should select the packets and choose Decode As... from the menu
then you can tell thet those packets are MEGACO. or with tethereal use
-d'tcp.port==2222,megaco'.
The message in frame 12 is decoded OK.
For the message split between frames 11 and 13 unfortunatelly the
MEGACO dissector does not perform tcp reassembly (yet).
However it looks like your MGC has problems calculating TCP checksums.
On Wed, 2 Mar 2005 20:06:39 +0530, ksaurabh@xxxxxxxxxxxx
<ksaurabh@xxxxxxxxxxxx> wrote:
>
> Hi All,
>
> I have captured Megaco messages (on TCP) using ethereal (ver 0.10.6) but the
> ethereal is not able to identify the protocol as Megaco.
> Can someone tell if there is a problem in the Megaco plugin or if the
> captured Megaco messages are malformed ?
> I am attaching the capture file with the mail. Frame 11 and 12 are Megaco
> messages.
>
> Thanks,
> Saurabh
>
>
>
> ***************** FSS-Unclassified *************
> "DISCLAIMER: This message is proprietary to Flextronics Software Systems
> Limited (FSS) and is intended solely for the use of the individual to whom
> it is addressed. It may contain privileged or confidential information and
> should not be circulated or used for any purpose other than for what it is
> intended. If you have received this message in error, please notify the
> originator immediately. If you are not the intended recipient, you are
> notified that you are strictly prohibited from using, copying, altering, or
> disclosing the contents of this message. FSS accepts no responsibility for
> loss or damage arising from the use of the information transmitted by this
> email including damage from virus."
> _______________________________________________
> Ethereal-users mailing list
> Ethereal-users@xxxxxxxxxxxx
> http://www.ethereal.com/mailman/listinfo/ethereal-users
>
>
>
>
--
This information is top security. When you have read it, destroy yourself.
-- Marshall McLuhan