ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
April 17th, 2024 | 14:30-16:00 SGT (UTC+8) | Online

Wireshark-bugs: [Wireshark-bugs] [Bug 8910] Incorrect information in radius/dictionary.3gpp for

Date: Wed, 10 Jul 2013 08:02:02 +0000

changed bug 8910

What Removed Added
Status UNCONFIRMED RESOLVED
Resolution --- NOTABUG

Comment # 1 on bug 8910 from
Turns out this is, naturally, a lot more complicated than it first appeared.

In the 5.7.0 revision of 29.061, 3GPP-Charging-Id is indeed described as an
unsigned 32-bit integer value. However, in later revisions of the standard, it
is only described as an OctetString without any details as to the data format.

Since hopefully no one is insane enough to quietly change the data type of an
AVP which is typeless on the wire between versions, the only reasonable
assumption here is that although the standard only describes the value as an
OctetString, it should indeed be interpreted as an unsigned 32-bit integer.


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