Pascal Quantin
changed
bug 7474
| What |
Removed |
Added |
| Status |
UNCONFIRMED
|
RESOLVED
|
| Resolution |
---
|
FIXED
|
Comment # 8
on bug 7474
from Pascal Quantin
(In reply to comment #7)
> I am trying to extract 3GPP_User_Location_Info from Radius messages. However
> in this instance it is not extracting info correctly
> $ tshark -v TShark 1.10.2 (SVN Rev 51934 from /trunk-1.10)
> tshark -T fields -e radius.Calling_Station_Id -e
> radius.3GPP_User_Location_Info -e radius.3GPP_IMEISV -e
> radius.Framed-IP-Address -E header=y -E separator=, -E quote=d -r
> Nikola_TEST_cap.pcap | head
> radius.Calling_Station_Id,radius.3GPP_User_Location_Info,radius.3GPP_IMEISV,
> radius.Framed-IP-Address "6149891xxxx",,"3598220413753808","144.131.70.63"
> "6145563xxxx",,"3598220423540908","101.175.33.128"
> For some reason the 3GPP-User-Location-Id AVP doesn’t get extracted by
> tshark, although Wireshark shows/decodes the AVP just file.
Please double check the filter names using Wireshark GUI: the various fields
for the 3GPP User Location Info are not named radius.3GPP_User_Location_Info
but gtp.ext_geo_loc_type, e212.mcc, e212.mnc, gtp.tac, and gtp.eci.
You are receiving this mail because:
- You are watching all bug changes.