Dear Devaraj, the touched rows:
destinationAddress (32) IMPLICIT AddressStringExtended OPTIONAL cAMELDestinationAddress (38) IMPLICIT AddressStringExtended OPTIONAL originatingAddress (33) IMPLICIT AddressStringExtended OPTIONAL Do you have info about them? Thanks Gábor Cseresnyés Allround Informatika Kft. www.allround.net -----Original Message----- From: devaraj[IT] [mailto:[EMAIL PROTECTED]] Sent: 2002. június 13. 06:04 To: '[EMAIL PROTECTED]' Subject: RE: [ASN.1] Question about AddressStringExtended data type Dear Gábor Cseresnyés , Can you tell me the CDR field name exactly (for example callingPartyNumber is addressstring).So that I can help you in this regard. regards, KB Devaraj RPG Cellular Services Ltd. India GSM +91 9841012030 > -----Original Message----- > From: Cseresnyés Gábor [SMTP:[EMAIL PROTECTED]] > Sent: Wednesday, June 12, 2002 12:00 AM > To: '[EMAIL PROTECTED]' > Subject: [ASN.1] Question about AddressStringExtended data type > > Dear All, > > I am Gábor Cseresnyés from Allround Informatika Kft., from Hungary. > We are developing CDR processing applications for the mobile > communications > field, so we often handle ASN.1 BER encoded files. > > Although we can handle a lot of ASN.1 BER standard and quasi-standard > (vendor-specific) data types actually we have met a new one: > AddressStringExtended which is not clear for us. > It can have 2 kind of encoding: TBCD and Character representations. > > I would like to ask you whether somebody knows more about this? > My question is what controls the used encoding? The definition made by the > given vendor says that it is depending on the value of the TON part. > Ok, but how? > > Have you got any idea? > > Best regards > > Gábor Cseresnyés > Allround Informatika Kft. > www.allround.net
