Wireshark-bugs: [Wireshark-bugs] [Bug 7376] Expert Info (Warn/Undecoded): Unknown AVP 872 (vendo
Date: Sun, 17 Jun 2012 05:56:02 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7376

--- Comment #6 from Anders Broman <[email protected]> 2012-06-17 05:56:00 PDT ---
(In reply to comment #2)
> (In reply to comment #1)
> > If the AVP should be 3GPP 872 there is an error in the aplication not sending
> > it with the vendor bit set and the vendor id of 3GPP. "Standard" AVP 872 is not
> > defined hence the Wireshark printout.
> 
> Thanks for the prompt response, Anders.
> Unfortunately this logic still not clear to me. I expected Wireshark recognizes
> AVP just by the code and I don't understand how others fields affect this
> process.

There is "base" AVP:s specified by IETF in RFCs and regitered by IANA these
AVPs dont have the vendor bit set and no vendor ID.

Then there is the Vendor AVP:s any vendor can define AVP:s and use them either
in open specifications (3GPP) or proprietary of course the vendor can chose to 
publish the AVP:s or some one makes their intepretation known to wireshark
(Cisco.xml Ericsson.xml Vodafone.xml...)
So vureshark have tables for base AVPs and Vendor AVPs and makes the lookup
in the apropriate table.

> I can't change anything on app side, 

You should register a bug report with the vendor if possible.

> so could you pls advise how disctionary's
> definition should be modified to match my current configuration?
> Just change vendor-id="TGPP" to vendor-id="3GPP"? I already tried but didn't
> help.
> 
> 
> Thanks

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