Hi, The principle is ok but you should probably use "dissect_ResetResource_PDU" and give it a new tvb with the RANAP data. Possibly causes of the decoding problem dissect_ranap_ResetResource() may expect offset in bits and return bit_offset. The data given to dissect_ranap_ResetResource() is not correct(including opcode etc perhaps?). The .cnf file should be used to export functions. Regards Anders
________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: den 22 januari 2008 11:54 To: [email protected] Subject: [Wireshark-dev] Problems in calling a message from RANAP dissector Hi , I have my test dissector , running over SUA , in TLV ( tag length value) format. In one of the messages, I want to add an existing RANAP ( asn.1 format) message along with the other parameters of my protocol. The coding of one of the messages in which I have called RANAP message goes like this: dissect_message(tvbuff_t *tvb,int offset ,proto_tree *xxx_tree,packet_info *pinfo) { asn1_ctx_t actx; asn1_ctx_init(&actx, ASN1_ENC_PER, TRUE, pinfo); offset = dissect_ranap_ResetResource(tvb, offset, &actx, macic_tree, hf_macic_ranap_resetResource); proto_tree_add_item(xxx_tree, hf_xxx_clust,tvb, offset, en, FALSE); offset = offset + len; } I have seen this way of implementation in MEGACO , trying to call a h245 message. But the RANAP message is not dissected properly and also I am not able to get the remaining parameters in the message. Could somebody confirm whether it is the right way to call a message from a different dissector. 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
_______________________________________________ Wireshark-dev mailing list [email protected] http://www.wireshark.org/mailman/listinfo/wireshark-dev
