Wireshark

  • Riverbed Technology
  • WinPcap
the world's foremost network protocol analyzer
  • Wireshark
    • About
    • Download
    • Blog
  • Get Help
    • Ask a Question
    • FAQs
    • Documentation
    • Mailing Lists
    • Online Tools
    • Wiki
    • Bug Tracker
  • Develop
    • Get Involved
    • Developer's Guide
    • Browse the Code
    • Latest Builds

Wireshark-dev: [Wireshark-dev] Improve Tcap oid management

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next


From: Florent.Drouin@xxxxxxxxxx
Date: Tue, 3 Oct 2006 17:19:30 +0200

      Hello,


I did improve the OID management in the tcap dissector.
Now, when a tcap message is reveived, without upper layer, the ACN is saved
in the TCAP context, and can be used for the next messages of the dialogue.
It is used only when the upper layer session is opened with Tcap only
messages.

Example:
a Tcap dialogue is opened with TC_BEGIN (oid camelv2)/TC_cont (accept oid
CamelV2)
And then, the Camel messages are echanged without oid, but can be decoded
according to the oid stored in the context.

(See attached file: packet-tcap-template.c.diff)

Regards
Florent

Attachment: packet-tcap-template.c.diff
Description: Binary data

  • Follow-Ups:
    • Re: [Wireshark-dev] Improve Tcap oid management
      • From: Anders Broman
  • Prev by Date: [Wireshark-dev] Repost a patch for tap-iostat.c to have new output format
  • Next by Date: Re: [Wireshark-dev] [Patch] update to packet-newmail.c
  • Previous by thread: [Wireshark-dev] Repost a patch for tap-iostat.c to have new output format
  • Next by thread: Re: [Wireshark-dev] Improve Tcap oid management
  • Index(es):
    • Date
    • Thread

Wireshark and the "fin" logo are registered trademarks of the Wireshark Foundation