Wireshark-bugs: [Wireshark-bugs] [Bug 5788] New: Missing decoding for CalledPartyBCD number
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Mon, 28 Mar 2011 02:29:57 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5788

           Summary: Missing decoding for CalledPartyBCD number
           Product: Wireshark
           Version: 1.4.0
          Platform: All
        OS/Version: Windows XP
            Status: NEW
          Severity: Major
          Priority: Low
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: martin.cekan@xxxxxxxxx


Build Information:
Paste the COMPLETE build information from "Help->About Wireshark", "wireshark
-v", or "tshark -v".
--
Hello all,

I noticed differences in decoding CalledPartyBCD number for CAMEL between
version of Wireshark especially v. 0.99 and v. 1.4.4(also older versions). 


Decoded with Wireshark 0.99 version

calledPartyBCDNumber: 91197859226346

                    1... .... = Extension: No Extension

                    .001 .... = Nature of address: International Number (0x01)

                    .... 0001 = Numbering plan indicator: ISDN/Telephony
Numbering (Rec ITU-T E.164) (0x01)

                    Address digits: 918795223664



Decoded with Wireshark 1.4.4 version

                    calledPartyBCDNumber: 91197859226346


Does somebody know why was decoding of CalledPartyBCD number removed from
latter versions of Wireshark and replaced by octet string? Was it some special
reason for it or..?

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.