Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-bugs: [Wireshark-bugs] [Bug 6174] New: Diameter dissector does not decode User-Authori

Date: Thu, 28 Jul 2011 04:17:16 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6174

           Summary: Diameter dissector does not decode
                    User-Authorization-Type AVP properly
           Product: Wireshark
           Version: 1.6.1
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Minor
          Priority: Low
         Component: Wireshark
        AssignedTo: bugzilla-admin@xxxxxxxxxxxxx
        ReportedBy: dobaksz@xxxxxxxxx


Build Information:
Version 1.6.1 (SVN Rev 38096 from /trunk-1.6)

Copyright 1998-2011 Gerald Combs <gerald@xxxxxxxxxxxxx> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled (32-bit) with GTK+ 2.22.1, with GLib 2.26.1, with WinPcap (version
unknown), with libz 1.2.5, without POSIX capabilities, without libpcre, with
SMI
0.4.8, with c-ares 1.7.1, with Lua 5.1, without Python, with GnuTLS 2.10.3,
with
Gcrypt 1.4.6, with MIT Kerberos, with GeoIP, with PortAudio V19-devel (built
Jul
18 2011), with AirPcap.

Running on 32-bit Windows Vista Service Pack 2, build 6002, with WinPcap
version
4.1.2 (packet.dll version 4.1.0.2001), based on libpcap version 1.0 branch
1_0_rel0b (20091008), GnuTLS 2.10.3, Gcrypt 1.4.6, without AirPcap.

Built using Microsoft Visual C++ 9.0 build 21022

Wireshark is Open Source Software released under the GNU General Public
License.

Check the man page and http://www.wireshark.org for more information.
--
Diameter protocol dissect doesn't decode User-Authorization-Type AVP (vendor
id: 3GPP, AVP code: 623) properly. It decodes value 1 as REGISTRATION instead
of DE_REGISTRATION.

Looking at the diameter/imscxdx.xml:

<avp name="User-Authorization-Type" code="623" mandatory="must"
vendor-bit="must" vendor-id="TGPP" may-encrypt="yes">
      <type type-name="Enumerated"/>
      <enum name="REGISTRATION" code="0"/>
      <enum name="REGISTRATION" code="1"/>
      <enum name="REGISTRATION_AND_CAPABILITIES" code="2"/>
</avp>

However, according to the 3GPP TS 29.229:


The User-Authorization-Type AVP is of type Enumerated, and indicates the type
of user authorization being performed in a User Authorization operation, i.e.
UAR command. The following values are defined:
REGISTRATION (0)
    This value is used in case of the initial registration or re-registration.
I-CSCF determines this from the Expires field or expires parameter in Contact
field in the SIP REGISTER method if it is not equal to zero.  
    This is the default value.
DE_REGISTRATION (1)
    This value is used in case of the de-registration. I-CSCF determines this
from the Expires field or expires parameter in Contact field in the SIP
REGISTER method if it is equal to zero.
REGISTRATION_AND_CAPABILITIES (2)
    This value is used when the I-CSCF explicitly requests S-CSCF capability
information from the HSS. The I-CSCF shall use this value when the user's
current S-CSCF, which is stored in the HSS, cannot be contacted and a new
S-CSCF needs to be selected

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