Differences between revisions 1 and 2
Revision 1 as of 2004-10-27 18:48:04
Size: 2021
Editor: h80n2fls33o887
Comment:
Revision 2 as of 2004-10-27 18:56:22
Size: 2208
Editor: h80n2fls33o887
Comment: Start MEGACO page
Deletions are marked like this. Additions are marked like this.
Line 26: Line 26:
The MEGACO dissector works for TEXT encoding of the protocoll if EOL is used as SEParator. Also add info of additional Ethereal features where appropriate, like special statistics of this protocol. The MEGACO dissector works for TEXT encoding of the protocoll if EOL is used as SEParator. Dissection of binary encoding has recently been added (2004-10-25)as a separate dissector, but is currently only working if M3UA is used as transport.
 If TCP is used there may be issues with desegmentation, such traces would be valuable.
Line 29: Line 30:

(XXX add links to preference settings affecting how PROTO is dissected).
 * You can change the PORTS on which MEGACO is dissected for UDP/TCP
 * Raw text output can be selected
 * Something else
Line 37: Line 39:
A complete list of PROTO display filter fields can be found in the [http://www.ethereal.com/docs/dfref/PROTO/PROTO.html display filter reference] A complete list of MEGACO display filter fields can be found in the [http://www.ethereal.com/docs/dfref/MEGACO/MEGACO.html display filter reference]
Line 39: Line 41:
 Show only the PROTO based traffic: {{{
 PROTO }}}
 Show only the MEGACO based traffic: {{{
 MEGACO }}}

Media Gateway Control Protocol (MEGACO/H.248.1)

MEGACO is used to control a Media GAteway in a VoIP system, MEGACO can be Text or Binary encoded.

History

Protocol dependencies

  • ["M3UA"]: MEGACO can use ["M3UA"] as its transport protocol, if M3UA is used there is an indication in the M3UA part that this is

MEGACO.

  • ["SCTP"]: Typically(?) MEGACO uses ["SCTP"] as its transport protocol, MEGACO is indicated in SCTP.
  • ["TCP"]: MEGACO can use ["TCP"] as its transport protocol. The well known TCP port for MEGACO traffic is xx, if TCP is used

a TPKT header must be included.

  • ["UDP"]: MEGACO can use ["UDP"] as its transport protocol. The well known UDP port for MEGACO traffic is xx
  • ["SCTP"]: Typically(?) MEGACO uses ["UDP"] as its transport protocol.

Example traffic

XXX - Add example traffic here (as plain text or Ethereal screenshot).

Ethereal

The MEGACO dissector works for TEXT encoding of the protocoll if EOL is used as SEParator. Dissection of binary encoding has recently been added (2004-10-25)as a separate dissector, but is currently only working if M3UA is used as transport.

  • If TCP is used there may be issues with desegmentation, such traces would be valuable.

Preference Settings

  • You can change the PORTS on which MEGACO is dissected for UDP/TCP
  • Raw text output can be selected
  • Something else

Example capture file

XXX - Add a simple example capture file to the SampleCaptures page and link from here. Keep it short, it's also a good idea to gzip it to make it even smaller, as Ethereal can open gzipped files automatically.

Display Filter

A complete list of MEGACO display filter fields can be found in the [http://www.ethereal.com/docs/dfref/MEGACO/MEGACO.html display filter reference]

  • Show only the MEGACO based traffic:

     MEGACO 

Capture Filter

You cannot directly filter PROTO protocols while capturing. However, if you know the ["TCP"] port used (see above), you can filter on that one.

  • add link to PROTO specification and where to find additional info on the web about PROTO

Discussion

H248/MEGACO (last edited 2010-05-24 19:34:29 by BillMeier)