[Wireshark-dev] Dissecting sua info string

Hi, How to dissect the (proprietary) information present in SUA 'info string' part? Should I create a separate dissector handle for that? Please provide your inputs. Thanks in advance. Regards, Bhavani. The information contained in this electronic message and any attachments to this

Re: [Wireshark-dev] Segmentation fault in dissector

Hi, Thanks for your inputs. The problem has been resolved with the inclusion of the epan/emem.h for 64 bit environment. Yes, the dissector is a proprietary one. Regards, Bhavani. The information contained in this electronic message and any attachments to this message are intended for

[Wireshark-dev] Segmentation fault in dissector

Hi, We are using a 32 bit machine and dissector is working fine. The same dissector when used in a 64 bit m/c is giving problems. I would like to know how is it going to get affected in the change of environment, because initially it did not even compile properly .While testing in a 64 bit

Re: [Wireshark-dev] User information in the packet

: interrogate_ss.cap.gz) Regards Florent durgabhavani.uppuluru To: [EMAIL PROTECTED] Sent by: cc: [EMAIL PROTECTED

[Wireshark-dev] Proprietary information in the TCAP packet

Hi, I'm trying to generate TCAP packet with the proprietary user information. I'm using TC-BEGIN primitive. I'm confused about the 'user information' mentioned at various locations in TCAP message specification. Should I transfer proprietary user information as part of structured

[Wireshark-dev] User information in the packet

Hi, How to transfer proprietary information in TCAP? Can the packet contain component portion? Can it also contain MAP OPEN information along with proprietary information in the dialogue portion? I'm using GSMMAP as TC user. Any hints are welcome. Thanks in advance. Best

Re: [Wireshark-dev] local operation code in MAP

Hi, I've given the value for operation code, not the ASN1 compiler. I've tried below suggestion but still got the problem. Operation code length : 02, and the operation code : H'81 H'99. I tried to print the opcode value read from dissect_ber_integer, dissect_ber_integer64 They

Re: [Wireshark-dev] local operation code in MAP

Hi, I've made the following changes in the packet: opcode length : 2 bytes opcode value : 00 99. It works. Thanks a lot for your help. Regards, Bhavani. From: DurgaBhavani Uppuluru Sent: Tuesday, February 27, 2007 7:44 PM To:

Re: [Wireshark-dev] local operation code in MAP

Hi Anders, Hex value shown, in the bytes pane is 99. I've tried other numbers too (150) and I get similar result. Best Regards, Bhavani. From: Anders Broman [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Date: Sun, 25 Feb 2007 19:55:43 +0100 Hi, What is the hex value shown in the

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

Re: [Wireshark-dev] local operation code in MAP

Hi, I'm using wireshark 0.99.5 sources. The below code is right. I've added the operations in the same way. Here are the steps followed: My GSMMAP.asn files looks 1. OperationLocalvalue ::= INTEGER{ updateLocation (2), : noteMM-Event (89),

Re: [Wireshark-dev] local operation code in MAP

Hi Again, I've tried latest svn version files too, still I get the same problem. I've added gsmmap, ranap directories packet-gtp.c from svn Revision 20934, on top of wireshark-0.99.5 sources. Please help me. Best Regards, Bhavani. From:

[Wireshark-dev] local operation code in MAP

Hi All, Greetings to you. I'm adding an operation with local value 153 to GSMMAP. But dissector does not recognize 153, it reports Unknown -103. Kindly tell me how to set this value. Thanks, Bhavani. The information contained in this electronic message and any attachments to

[Wireshark-dev] 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

[Wireshark-dev] Query reg MAP asn

Hi All, Greetings to you. Can you please answer my query? For MAP dissector, if it is indicated that TC-BEGIN may carry additional information, does that mean additional information has to be part of components (invoke, reject.. etc)? Should additional information be described as a