Wireshark · Wireshark-dev: Re: [Wireshark-dev] Regarding inclusion of operations and parameters inANSI TCAP

["Anders Broman" <anders.broman@xxxxxxxxxxxx>]

Hi,

It should NOT be part of ANSI MAP. I'm not familiar with ANS TCAP but how you should adress this depends on how you are using ANSI TCAP i guess:

- Privare Operation Code.

- Using the dialouge portion or not...

 

You need to make your own dissector for the operations, parameters and results then change find_tcap_subdissector() in packet-ansi_tcap.c to call your

dissector for the apropriate operation codes. You could set up a dissector table for private operation codes and let your dissector register in it.

Regards

Anders

---

From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of taraniteja.vishwanatha@xxxxxxxxx
Sent: den 10 december 2007 10:24
To: wireshark-dev@xxxxxxxxxxxxx
Subject: [Wireshark-dev] Regarding inclusion of operations and parameters inANSI TCAP

Hi,

 

We have a “xxx” protocol which is a Transaction User of ANSI TCAP. We have some operations, parameters and results defined for it.We have to include it in the ANSI part of tcap.asn. Can somebody please suggest me a way??

 

BR,

Tarani

The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.

www.wipro.com