ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
April 17th, 2024 | 14:30-16:00 SGT (UTC+8) | Online

Wireshark-bugs: [Wireshark-bugs] [Bug 4062] T.125 MCS: connect-initial/response 4 bytes left to

Date: Tue, 1 Dec 2009 15:11:56 -0800 (PST)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4062

--- Comment #4 from Franck Guenichot <malphx@xxxxxxx> 2009-12-01 15:11:55 PST ---
(In reply to comment #3)
> So do you mean, that these fields should be at least displayed optionally (eg.
> based on a protocol preference) ?

What i mean is that these values are not really a protocol parameter (from
T.125 or from the encapsulated T.124 PDU) but in fact are part of the coding
method of the parameter itself : ASN.1 BER coding.
The T.125 userData is an Octet String ASN.1 type and this type of data is coded
like that in BER.

You actually could display the meaning of these bytes, in the Wireshark
preferences for BER protocol, by selecting:
Show internal BER encapsulation tokens.

Then you should see information like these ones:
00.. .... = Class: UNIVERSAL (0)
..0. .... = P/C: Primitive Encoding
...0 0100 = Tag: OCTET STRING (4)
Length: 319

Selecting each BER field then, selects also the corresponding bytes in the
hexdump.

Rgds,
Franck.

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