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) 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 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) Hi, That should suffice, can you send me a small sample file? Best regards Anders Från:
wireshark-users-bounces@xxxxxxxxxxxxx genom 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> I’m 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) 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 Hi,
This email has been processed by SmoothZap - www.smoothwall.net |
- Follow-Ups:
- Re: [Wireshark-users] Diameter unknown AVPs
- From: Anders Broman
- Re: [Wireshark-users] Diameter unknown AVPs
- References:
- Re: [Wireshark-users] Diameter unknown AVPs
- From: Anders Broman (AL/EAB)
- Re: [Wireshark-users] Diameter unknown AVPs
- Prev by Date: Re: [Wireshark-users] Jitter wrong in wireshark?
- Next by Date: [Wireshark-users] Large numbers of lost packets, duplicate ACKs, and retransmissions?
- Previous by thread: Re: [Wireshark-users] Diameter unknown AVPs
- Next by thread: Re: [Wireshark-users] Diameter unknown AVPs
- Index(es):