Question why is tshark ignoring diameter AVP Policy-Counter-Identifier?

asked 2018-06-15 16:32:41 +0000

Silva
1

updated 2018-10-26 17:49:33 +0000

11115 ●11 ●317 ●165 https://www.igt.com/

Opening a .cap file with diameter messages using wireshark tool i can find avp Policy-Counter-Identify AVPs, but using the tshark tool to read the same .cap file i can't find these specific AVPs. It's sounds like tshark is ignoring this specific AVP. All the other AVPs are displayed ok.

To read the .cap file whith tshark tool i'm using the command 'tshark -V -O diameter -r file.cap'.

I appreciate any help.

edit retag flag offensive close merge delete

Comments

What happens if you use the command

tshark -2 -V -O diameter -r file.cap

to request two-pass processing in TShark?

Guy Harris ( 2018-06-15 19:35:59 +0000 )edit

Also, there's no AVP named "Policy-Counter-Identify" in the current dictionary; did you mean "Policy-Counter-Id" or "Policy-Counter-Identifier"?

Guy Harris ( 2018-06-15 19:45:20 +0000 )edit

Hi Guy, thanks for your reply and you're right! The corret AVP's name is Policy-Counter-Identifier. My bad. I tried the command you wrote 'tshark -2 -V -O diameter -r file.cap' and the AVP is still not present in the output.

Silva ( 2018-06-15 19:59:48 +0000 )edit

Additionally, bellow is the AVP complete data decoded and displayed by wireshark tool. That's the information i can't find when using tshark tool as i told when i started this case.

AVP: Policy-Counter-Status-Report(2903) l=48 f=VM- vnd=TGPP
    AVP Code: 2903 Policy-Counter-Status-Report
    AVP Flags: 0xc0, Vendor-Specific: Set, Mandatory: Set
        1... .... = Vendor-Specific: Set
        .1.. .... = Mandatory: Set
        ..0. .... = Protected: Not set
        ...0 .... = Reserved: Not set
        .... 0... = Reserved: Not set
        .... .0.. = Reserved: Not set
        .... ..0. = Reserved: Not set
        .... ...0 = Reserved: Not set
    AVP Length: 48
    AVP Vendor Id: 3GPP (10415)
    Policy-Counter-Status-Report: 00000b55c0000013000028af446174614e61630000000b56...
        AVP: Policy-Counter-Identifier(2901) l=19 f=VM- vnd=TGPP val=BlaBlaBla
            AVP Code: 2901 Policy-Counter-Identifier
            AVP Flags: 0xc0, Vendor-Specific: Set, Mandatory: Set
                1... .... = Vendor-Specific: Set
                .1.. .... = Mandatory: Set
                ..0. .... = Protected: Not set
                ...0 .... = Reserved: Not set
                .... 0... = Reserved: Not set
                .... .0.. = Reserved: Not set
                .... ..0. = Reserved: Not set
                .... ...0 = Reserved: Not set
            AVP Length: 19
            AVP Vendor ...

(more)

Silva ( 2018-06-15 20:12:55 +0000 )edit

The unique information about this AVP to the same diameter message obtained by tshark tool is what i'm sending below:

AVP: Policy-Counter-Status-Report(2903) l=48 f=VM- vnd=TGPP val=
    AVP Code: 2903 Policy-Counter-Status-Report
    AVP Flags: 0xc0
        1... .... = Vendor-Specific: Set
        .1.. .... = Mandatory: Set
        ..0. .... = Protected: Not set
        ...0 .... = Reserved: Not set
        .... 0... = Reserved: Not set
        .... .0.. = Reserved: Not set
        .... ..0. = Reserved: Not set
        .... ...0 = Reserved: Not set
    AVP Length: 48
    AVP Vendor Id: 3GPP (10415)
    Policy-Counter-Status-Report:

:´-(

Silva ( 2018-06-15 20:24:21 +0000 )edit

add a comment

Question why is tshark ignoring diameter AVP Policy-Counter-Identifier?

Comments

1 Answer

Comments

Your Answer

Question Tools

Stats

Related questions

Question why is tshark ignoring diameter AVP Policy-Counter-Identifier? edit

Comments

1 Answer

Comments

Your Answer

Question Tools

Stats

Related questions

Question why is tshark ignoring diameter AVP Policy-Counter-Identifier?