Hi, Could anybody please help me with this?
Attached to this email is a binary dump file of the problematic GSM MAP pdu I\'m getting. I try to decode that using encode/decode function I got by processing the ITU TCAP and ETSI 29.002 5.8.3 ASN.1 source files. There're many more Binary dump files, like the one I attached here. Some are getting processed without a problem, when I try to decode the component part of an Invoke message as ArgumentType. The attached binary corresponds to a reportSM-DeliveryStatus operation under MAP- ShortMessageServiceOperations. Once I processed I get the TCAP component part, which is <<108,28,161,26,2,1,232,2,1,47,48,18,4,7,145,73,39,51,22,6,241,4,7,145,25,137,19,32,41,0>> (a text representation of a binary string). Then I decode that component part and I get the component as an Invoke Message with Local Operation as, 47 - reportSM-DeliveryStatus operation of MAP-ShortMessageServiceOperations and User Information as, <<48,18,4,7,145,73,39,51,22,6,241,4,7,145,25,137,19,32,41,0>> (a text representation of a binary string). When I tried to decode that User Information as an ArgumentType message of reportSM- DeliveryStatus, it fails. But when I decode it as a ResultType message, it succeeds. Could you please decode that file or go through the above description and see if you can identify where the problem is. Thanks in advance! - Eranga --------------This mail sent through OmniBIS.com--------------
1113555218_482_1-3.bin
Description: Binary data
_______________________________________________ ASN1 mailing list [email protected] http://lists.asn1.org/mailman/listinfo/asn1
