Hi, I have below AVP's added in avp.xml <avp name="Subscriber_Category" code="1003" vendor-id="Comviva" mandatory="must" protected="mustnot" may-encrypt="yes" vendor-bit="must"> <type type-name="Unsigned32"/> </avp> still i am getting AVP as unknown . I am using tshark to read pcap and am using -z for diameter protocol . i am unable to get that AVP as it is a unknown AVP . will tshark supports AVP's of Vendor other than 3GPP? BR, Ankamma asked 10 Sep '14, 06:50 ankamma edited 11 Sep '14, 06:05 JeffMorriss ♦ |
One Answer:
To add a new .xml file you neeed to update the ENTITY list in dictionaty.xml and also add it at the bottom of the file( Compare with say HP.xml) For the vendor-id You need to add Comviva to the vendor list. answered 10 Sep '14, 07:38 Anders ♦ Hi, by adding below lines it is working fine and am able to get AVP names in wireshark(windows). but how to achieve the same in tshark(linux)? where to add Entity in Linux? [[email protected] tmp]# tshark -r /tmp/Gx_dump1.pcap -d 'tcp.port==3870,diameter' -R "diameter.cmd.code==272 and diameter.flags.request==0" -z "diameter,avp,272,CC-Request-Type,CC-Request-Number,Session-Id,Subscription-Id-Data,Rating-Group,Result-Code,Session-Id,Custom_Result_Code" tshark: -R without -2 is deprecated. For single-pass filtering use -Y. tshark: Couldn't register diam,csv tap: Filter "diameter||diameter.CC-Request-Type||diameter.CC-Request-Number||diameter.Session-Id||diameter.Subscription-Id-Data||diameter.Rating-Group||diameter.Result-Code||diameter.Session-Id||diameter.Custom_Result_Code" is invalid - "diameter.Custom_Result_Code" is neither a field nor a protocol name. BR, Ankamma (10 Sep '14, 23:06) ankamma hi, i got it working by adding entity in the same way (10 Sep '14, 23:16) ankamma Glad you got it working. If an Answer answers your question, please Accept the answer by clicking on the little checkbox next to it. See the FAQ for details. (11 Sep '14, 06:05) JeffMorriss ♦ |
hi ,
i have two files dictionary,vendor_avp.xml .
dictionary file is like below:
# # Vendor-Specific attributes use the SMI Network Management Private # Enterprise Code from the "Assigned Numbers" RFC (currently RFC 1700) # # # You need to activate a VSA mode on your box to get these attributes # in accounting records #
and vendor_avp.xml is like below: