Wireshark-bugs: [Wireshark-bugs] [Bug 10522] GSM MAP LocationNumber parameter decoded incorrectl
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Fri, 03 Oct 2014 13:30:30 +0000

changed bug 10522


What Removed Added
Status UNCONFIRMED RESOLVED
Resolution --- FIXED

Comment # 3 on bug 10522 from 
(In reply to Geoff Hart from comment #2)
> Hi,
> 
> The problem (in my opinion) is that the first 2 bytes of this 7-byte field
> are flags, specifically: 0x0317 which decodes to:
> 
> 
> Octet 1
> 0... .... = Odd/Even: False
> ..00 0011 = Nature of address indicator: national (significant) number
> (national use) (3)
> 
> Octet 2
> 0... .... = Internal Network Number indicator (INN): False
> ..01 .... = Numbering plan indicator: ISDN (telephony) numbering plan (ITU-T
> Recommendation E.164) (1)
> .... 01.. = Address presentation restricted indicator: presentation
> restricted (1)
> .... ..11 = Screening indicator: network provided (3)
> 
> 
> That should leave you with 5 bytes of undecoded data for the Address-Digits.
> However, in the current decode, you see 6-bytes of address digits:
> 
> Address Digits: 712265113419  from (0x17 22 56 11 43 91)
> 
> 
> So I believe the problem here is the value in Octet-2 got re-used incorrect
> in the Address Digits field, making it 2 digits longer than it should be.
> 
> Geoff

Argh, I didn't see that at first, fixed in trunk 
https://code.wireshark.org/review/4439

You are receiving this mail because:
  • You are watching all bug changes.