Wireshark · Wireshark-dev: Re: [Wireshark-dev] NBAP: dissection of Private Messages

[praveen.jha@xxxxxxxxxxx]

Hi,
"PrivateMessage" PDU is already defined in the NBAP spec, but it doesn't have any IEs currently.
I am adding IEs to it (PrivateMessage-IEs).

PrivateMessage-IEs NBAP-PRIVATE-IES ::= {

{ ID local:id-type-1 CRITICALITY criticality TYPE Sample-Message-Type PRESENCE optional} ,
...
}

Regards

"Anders Broman" <anders.broman@xxxxxxxxxxxx>

"Anders Broman" <anders.broman@xxxxxxxxxxxx>
Sent by: wireshark-dev-bounces@xxxxxxxxxxxxx

02/26/2008 06:09 PM



Please respond to
Developer support list for Wireshark <wireshark-dev@xxxxxxxxxxxxx>

To	"Developer support list for Wireshark" <wireshark-dev@xxxxxxxxxxxxx>
cc
Subject	Re: [Wireshark-dev] NBAP: dissection of Private Messages

Hi,
Are you trying to add private PDU:s or Privare IE:s to a existing PDU?
Can you post a .pcap file of the message?

Regards
Anders

---

From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of praveen.jha@xxxxxxxxxxx
Sent: den 26 februari 2008 17:25
To: wireshark-dev@xxxxxxxxxxxxx
Subject: [Wireshark-dev] NBAP: dissection of Private Messages

Hi,
I am trying to implement the dissection of NBAP containing private message(s). For that I am including my private message
in asn1 format.
the message format is as follows :

-- ****************************************************************************************************************************
-- Private PDUs
-- ****************************************************************************************************************************

PrivateMessage-IEs NBAP-PRIVATE-IES ::= {
{ ID local:id-type-1 CRITICALITY criticality TYPE Sample-Message-Type PRESENCE optional} |
{ ID local:id-type-2 CRITICALITY criticality TYPE Sample-Message-Type PRESENCE optional} ,
...
}

Sample-Message-Type ::= CHOICE {
type-a value-a ,
type-b value-b
}

the above definition, I have added in NBAP-PDU-Containers.asn file.



--*******************************************************************************************************************************
--Private Constants
--*******************************************************************************************************************************
id-type-1 6000
id-type-2 7000
--*******************************************************************************************************************************
Added the constants in NBAP-Constants.asn file.

Apart from this I have also modified the CNF file,
In REGISTER_NEW added type-1, type-2 as IEs and, then type-a and type-b as IE-Extensions.

But the dissector is not able to dissect the Sample-Message-Type.
Any suggestions??

Regards,
Praveen Kumar Jha


*********************** Aricent-Unclassified ***********************

"DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of
the individual to whom it is addressed. It may contain privileged or confidential information and should not be
circulated or used for any purpose other than for what it is intended. If you have received this message in error,
please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly
prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for
loss or damage arising from the use of the information transmitted by this email including damage from virus."

_______________________________________________
Wireshark-dev mailing list
Wireshark-dev@xxxxxxxxxxxxx
http://www.wireshark.org/mailman/listinfo/wireshark-dev

*********************** Aricent-Unclassified ***********************

"DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of
the individual to whom it is addressed. It may contain privileged or confidential information and should not be
circulated or used for any purpose other than for what it is intended. If you have received this message in error,
please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly
prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for
loss or damage arising from the use of the information transmitted by this email including damage from virus."