Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
  • wireshark wireshark
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 1,340
    • Issues 1,340
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 155
    • Merge requests 155
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • External wiki
    • External wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

Scheduled maintenance on the database layer will take place on 2022-07-02. We expect GitLab.com to be unavailable for up to 2 hours starting from 06:00 UTC. Kindly follow our status page for updates and read more in our blog post.

  • Wireshark Foundation
  • wiresharkwireshark
  • Issues
  • #18018
Closed
Open
Created Mar 29, 2022 by Ben Weltevrede@benwel

RTP analysis does not use all data

Summary

The RTP analysis function in the telephony section does not use all available packets. Moreover the number of packets used varies between invocations of the analysis function. (see

Steps to reproduce

Capture pcap file of sufficient length (if used 15 minutes or more). Invoke the RTP analysis function.

What is the current bug behavior?

Not all packets are used in the computation of statistics. See attached screendumps. The pcap file has captured 205937 packets. The analysis uses fewer packets, as it visible form the RTP packet count, durcation and the graph. In subsequent invocations of the analysis other values are used. (see screendumps below).

What is the expected correct behavior?

All available packets should be used.

Sample capture file

(If possible attach a sample capture file, not screenshot of dissection, showing this issue)

Relevant logs and/or screenshots

(Paste any relevant logs here)

(Paste any relevant screenshots here) rtp_analysis_2

rtp_analysis_1

rtp_player

Build information

3.6.2 (v3.6.2-0-g626020d9)

Compiled (64-bit) using Microsoft Visual Studio 2019 (VC++ 14.29, build 30139), with Qt 5.15.2, with libpcap, with GLib 2.66.4, with zlib 1.2.11, with Lua 5.2.4, with GnuTLS 3.6.3 and PKCS #11 (closed) support, with Gcrypt 1.8.3, with MIT Kerberos, with MaxMind DB resolver, with nghttp2 1.44.0, with brotli, with LZ4, with Zstandard, with Snappy, with libxml2 2.9.10, with libsmi 0.4.8, with QtMultimedia, with automatic updates using WinSparkle 0.5.7, with AirPcap, with SpeexDSP (using bundled resampler), with Minizip.

Running on 64-bit Windows 7 Service Pack 1, build 7601, with Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz (with SSE4.2), with 16375 MB of physical memory, with GLib 2.66.4, with Qt 5.15.2, with WinPcap version 4.1.2 (packet.dll version 4.1.0.2001), based on libpcap version 1.0 branch 1_0_rel0b (20091008), with c-ares 1.17.0, with GnuTLS 3.6.3, with Gcrypt 1.8.3, with nghttp2 1.44.0, with brotli 1.0.9, with LZ4 1.9.3, with Zstandard 1.4.0, without AirPcap, with light display mode, without HiDPI, with LC_TYPE=C, binary plugins supported (9 loaded).

Edited Mar 29, 2022 by Alexis La Goutte
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking