["Anders Broman \(AL/EAB\)" <anders.broman@xxxxxxxxxxxx>]

Hi,

Are you using the 0.99.5 sources or a fresh SVN checkout?

That code is only in the latest sources I think.

Best regards

Anders

---

From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of durgabhavani.uppuluru@xxxxxxxxx
Sent: den 26 februari 2007 11:45
To: wireshark-dev@xxxxxxxxxxxxx
Subject: Re: [Wireshark-dev] Mixed application contexts in MAP

Hi,

 

I’m adding proprietary operations & application contexts to GSMMAP.

I’m updating the same GSMMAP.asn file with the operations.

 

Please let me know whether I can add them directly, to the GSMMAP file or not.

I couldn’t find the below PlmnContainer in the wireshark soure.

 

Did you mean the below ‘line’ to be an example?

 

Best Regards,

Bhavani

 

 

From: "Anders Broman" <a.broman@xxxxxxxxx>
Date: Sun, 25 Feb 2007 20:01:34 +0100

Hi,,

I’m not sure what you want but see:

register_ber_oid_dissector("1.3.12.2.1006.53.2.1.3", dissect_gsm_mapext_PlmnContainer,

in the packet-gsm_map-template.c file and PlmnContainer in the asn1 file.

Best regards

Anders

---

From: DurgaBhavani Uppuluru

Sent: Sunday, February 25, 2007 6:17 PM
To: 'wireshark-dev@xxxxxxxxxxxxx'
Subject: Mixed application contexts in MAP

 

Hi,

 

Can I add application context with ‘iso(1)….’ OID along with contexts of ‘itu-t(0)’ OIDs in the same dissector development file?

 

Thanks,

Bhavani

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