Wireshark-dev: Re: [Wireshark-dev] Regarding inclusion of operationsandparametersinANSI TCAP
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: <taraniteja.vishwanatha@xxxxxxxxx>
Date: Mon, 10 Dec 2007 17:08:43 +0530

Thanks Anders …I was using an older version. I shall look into it and get back to you in case of any queries.

 

From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Anders Broman
Sent: Monday, December 10, 2007 4:48 PM
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Regarding inclusion of operationsandparametersinANSI TCAP

 

Hi,

Ary you using the latest SVN sources?

Since 0.99.6 TCAP has been split in ANSI and ITU part.

ANSI MAP is the only ANSI TCAP user currently.

Packet-ranap.c might give an idea on how to register a dissector per operational code.

Regards

Anders

 

From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of taraniteja.vishwanatha@xxxxxxxxx
Sent: den 10 december 2007 11:51
To: wireshark-dev@xxxxxxxxxxxxx
Subject: Re: [Wireshark-dev] Regarding inclusion of operations andparametersinANSI TCAP

Hi ,

 

I agree to that it shoud not be a part of ANSI MAP. In the file tcap.asn, a generic format is mentioned regarding the ansi operations, parameters , both with and without sequence and results.When we write our dissector, we don’t have the asn file for it, so we want to use a  already existing asn as a base ( usual practice). In this case, we found it to be TCAP.

 

The operations of the protocol are class 1.

 

I am not able to find both packet-ansi_tcap.c either in asn or in epan/dissectors directory. The function add_ansi_tcap_subdissector is there in packet-tcap.c.

Are there any more Transaction capability users of ANSI TCAP / TCAP, so that we can have a better idea.

 

You could set up a dissector table

 

Can you please briefly explain how to go about it??

 

BR,

Tarani

 

From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Anders Broman
Sent: Monday, December 10, 2007 3:19 PM
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Regarding inclusion of operations andparameters inANSI TCAP

 

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

 


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

 


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