Wireshark treats the letter E in SSRC as an exponential representation of a number
Summary
Wireshark in "VoIP call > Flow sequence" treats the letter E in SSRC as an exponential representation of a number.
Steps to reproduce
- Open attached pcap
- VoIP call > Flow sequence
- Compare SSRC in packets list and in Flow sequence
What is the current bug behavior?
Wireshark in "VoIP call > Flow sequence" treats the letter E in SSRC as an exponential representation of a number.
Example: SSRC 0x4A6E3891 showing as 0x4A6*10^3891
What is the expected correct behavior?
SSRC 0x4A6E3891 showing as 0x4A6E3891
Sample capture file
Relevant logs and/or screenshots
Build information
Version 4.1.0rc0-1543-gdda2ead9c052 (v4.1.0rc0-1543-gdda2ead9c052).
Compiled (64-bit) using Microsoft Visual Studio 2022 (VC++ 14.32, build 31332),
with GLib 2.72.3, with PCRE2, with zlib 1.2.12, with Qt 6.2.3, with libpcap,
with Lua 5.2.4 (with UfW patches), with GnuTLS 3.6.3 and PKCS #11 support, with
Gcrypt 1.10.1, with Kerberos (MIT), with MaxMind, with nghttp2 1.49.0, with
brotli, with LZ4, with Zstandard, with Snappy, with libxml2 2.9.14, with libsmi
0.4.8, with QtMultimedia, with automatic updates using WinSparkle 0.5.7, with
AirPcap, with Minizip, with binary plugins, debug build (+utf8).
Running on 64-bit Windows 10 (22H2), build 19045, with AMD Ryzen 5 5600H with
Radeon Graphics (with SSE4.2), with 15715 MB of physical memory, with GLib
2.72.3, with PCRE2 10.40 2022-04-14, with Qt 6.2.3, with Npcap version 1.71,
based on libpcap version 1.10.2-PRE-GIT, with c-ares 1.18.1, with GnuTLS 3.6.3,
with Gcrypt 1.10.1, with nghttp2 1.49.0, with brotli 1.0.9, with LZ4 1.9.3, with
Zstandard 1.5.2, without AirPcap, with light display mode, without HiDPI, with
LC_TYPE=Russian_Russia.utf8, binary plugins supported.
Edited by Gennadiy Apollonov