Wireshark-bugs: [Wireshark-bugs] [Bug 1964] Wireshark is not able to parse MGCP over TCP with AS
Date: Wed, 31 Oct 2007 07:40:11 +0000 (GMT)

[email protected] changed:

           What    |Removed                     |Added
         AssignedTo|[email protected]|[email protected]
             Status|NEW                         |ASSIGNED
   Attachment #1090|                            |review_for_checkin?
               Flag|                            |

------- Comment #1 from [email protected]  2007-10-31 07:40 GMT -------
Created an attachment (id=1090)
 --> (http://bugs.wireshark.org/bugzilla/attachment.cgi?id=1090&action=view)
This patch supports parsing of ASCII TPKT header 

To fix this bug MGCP dissector has been modified. A new MGCP dissector routine
“dissect_tpkt_mgcp “ is implemented to take care of MGCP packet. Figure 1
shows MGCP packet over ASCII TPKT header. MGCP dissector routine is associated
with a TCP port number so that the main program will know to call new MGCP
dissector when it gets TCP traffic on that port.
Following is structure of ASCII TPKT header
|      |Version | Reserved | Length |      |           |
| TCP  | 2 bytes| 2 bytes  |4 bytes |Space | MGCP Data |
| DATA |        |          |        |      |           |

            Figure 1
"dissect_tpkt_mgcp “checks if MGCP payload has MGCP data over ASCII TPKT
header. If it has ASCII TPKT header then “dissect_asciitpkt_encap “is
called which dissects ASCII TPKT header and then calls existing MGCP dissector.
If MGCP data does not have ASCII TPKT then existing “dissect_mgcp” is

Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are the assignee for the bug, or are watching the assignee.