Wireshark-users: Re: [Wireshark-users] Diameter unknown AVPs
From: "Anders Broman" <a.broman@xxxxxxxxx>
Date: Mon, 26 Feb 2007 20:03:34 +0100
Hi, Changing the chargecontrol.xml file to: <avp name="Volume-Quota-Threshold" code="869" mandatory="must" may-encrypt="no" protected="may"> <type type-name="Unsigned32"/> </avp> Works for me. Quota-Holding-Time is defined in the dictionary.xml file and in the chargecontrol.xml(as vendor specific)perhaps Volume-Quota-Threshold Should be in both files as well. I think there is a bit of a mess with the older 3GPP specs misusing The common AVP's which has been corrected in later specs. Best regards Anders ________________________________________ Från: wireshark-users-bounces@xxxxxxxxxxxxx [mailto:wireshark-users-bounces@xxxxxxxxxxxxx] För Frederiek Debruyne Skickat: den 26 februari 2007 14:52 Till: Community support list for Wireshark Ämne: Re: [Wireshark-users] Diameter unknown AVPs Hi, The cleared flag bits seem not to be the real problem that causes Wireshark not to recognize this Volume-Quota-Threshold AVP. I removed the vendor-id="TGPP" part from the related XML file line, and set vendor-bit="mustnot". That did not help. Furthermore, the 3GPP AVP Quota-Holding-Time, on the other hand, is recognized without any problem, while all its flag bits are cleared too. Regards, Frederiek ________________________________________ From: wireshark-users-bounces@xxxxxxxxxxxxx [mailto:wireshark-users-bounces@xxxxxxxxxxxxx] On Behalf Of Anders Broman (AL/EAB) Sent: maandag 26 februari 2007 13:27 To: Community support list for Wireshark Subject: Re: [Wireshark-users] Diameter unknown AVPs Hi, The problem is that Wireshark expects this to be a vendor AVP but it's sent as a "normal" one. I think this was changed in more recent versions of the 3GPP doc's to be Vendor specific AVP:s. The simplest soulution for you is to edit the XML file and remove "Vendor-id="TGPP" " from the relevant AVP:s Best regards Anders ________________________________________ From: wireshark-users-bounces@xxxxxxxxxxxxx [mailto:wireshark-users-bounces@xxxxxxxxxxxxx] On Behalf Of Frederiek Debruyne Sent: den 26 februari 2007 09:10 To: Community support list for Wireshark Subject: Re: [Wireshark-users] Diameter unknown AVPs Hi Anders, Did you receive the sample file? Is the Volume-Quota-Threshold AVP recognized in your case? Regards, Frederiek ________________________________________ From: wireshark-users-bounces@xxxxxxxxxxxxx [mailto:wireshark-users-bounces@xxxxxxxxxxxxx] On Behalf Of Anders Broman (AL/EAB) Sent: vrijdag 23 februari 2007 16:42 To: Community support list for Wireshark Subject: SV: [Wireshark-users] Diameter unknown AVPs Hi, That should suffice, can you send me a small sample file? Best regards Anders ________________________________________ Från: wireshark-users-bounces@xxxxxxxxxxxxx genom Frederiek Debruyne Skickat: fr 2007-02-23 16:27 Till: Community support list for Wireshark Ämne: Re: [Wireshark-users] Diameter unknown AVPs Hi, The Attempt to load/use Diameter XML Dictionary checkbox, in the preferences for Diameter, is checked. The Diameter XML dictionary is set to C:\Program Files\Wireshark\diameter/dictionary.xml. The Volume-Quota-Threshold AVP (code 869) is not recognized. This AVP is not defined by IETF RFC 3588, but by a 3GPP specification. I am not that familiar with XML, though I noticed the occurrence of following lines in file chargecontrol.xml: <avp name="Volume-Quota-Threshold" code="869" mandatory="must" may-encrypt="no" protected="may" vendor-bit="must" vendor-id="TGPP"> <type type-name="Unsigned32"/> </avp> Im not sure whether this should be sufficient. It does not seem to be, since the AVP is still not recognized. Regards, Frederiek ________________________________________ From: wireshark-users-bounces@xxxxxxxxxxxxx [mailto:wireshark-users-bounces@xxxxxxxxxxxxx] On Behalf Of Anders Broman (AL/EAB) Sent: vrijdag 23 februari 2007 16:04 To: Community support list for Wireshark Subject: SV: [Wireshark-users] Diameter unknown AVPs Hi, AVP:s can be dissected either by the data in the file packet-diameter-defs.h or by the Diameter XML files if those preferences are set. See the wiki page for details. The XML library is more updated than the file. What AVP:s are not recognised? Best regards Anders ________________________________________ Från: wireshark-users-bounces@xxxxxxxxxxxxx genom Frederiek Debruyne Skickat: fr 2007-02-23 15:33 Till: wireshark-users@xxxxxxxxxxxxx Ämne: [Wireshark-users] Diameter unknown AVPs Hi, I frequently use Wireshark to analyze Diameter protocol traffic. I notice that not all AVPs are recognized. That is, the packet details frame contains a line with "Unknown AVP" in that case. What must be done to make Wireshark recognize these AVPs? I am using the latest Wireshark version, i.e. version 0.99.5. Regards, Frederiek This email has been processed by SmoothZap - www.smoothwall.net _______________________________________________ Wireshark-users mailing list Wireshark-users@xxxxxxxxxxxxx http://www.wireshark.org/mailman/listinfo/wireshark-users This email has been processed by SmoothZap - www.smoothwall.net This email has been processed by SmoothZap - www.smoothwall.net This email has been processed by SmoothZap - www.smoothwall.net
- References:
- Re: [Wireshark-users] Diameter unknown AVPs
- From: Frederiek Debruyne
- Re: [Wireshark-users] Diameter unknown AVPs
- Prev by Date: Re: [Wireshark-users] SMB Trans2 FILE_QUERY_INFO Query File Standard Info - what's going on?
- Next by Date: Re: [Wireshark-users] Jitter wrong in wireshark?
- Previous by thread: Re: [Wireshark-users] Diameter unknown AVPs
- Next by thread: [Wireshark-users] Jitter wrong in wireshark?
- Index(es):