Wireshark-bugs: [Wireshark-bugs] [Bug 11847] Failure of automatic detection of UDP packets as RT
Pavel Uhliar
changed
bug 11847
| What |
Removed |
Added |
| CC |
|
pavel.uhliar@gmail.com
|
Comment # 11
on bug 11847
from Pavel Uhliar
I believe I have triggered the same bug as Pavel Sindelka (RTP not displayed in
flow sequence), but in my case it seems to be related to size of the capture
file.
I have a 670MB capture file with 26600355 packets, and when using this one, RTP
is not displayed in flow sequence.
When I filter the packets by destination port found in SIP dialog, I see the
RTP packets are captured, Wireshark just does not pair them to call flow.
When I filter this file to time interval starting with the second where INVITE
occurs and finishing 10 seconds after BYE and ACK are handled, export it to a
new file (130MB, 499122 packets), the RTP is visible in flow sequence.
The procedure I use to display flow sequence is:
- open the capture file
- menu Telephony -> VoIP Calls
- sort lines by To column
- select the call I need
- button Flow Sequence
I will upload screenshots of flow window from both files as attachment.
Pavel Uhliar
My Wireshark info:
Version 2.0.4 (v2.0.4-0-gdd7746e from master-2.0)
Compiled (64-bit) with Qt 5.3.2, with WinPcap (4_1_3), with libz 1.2.8, with
GLib 2.42.0, with SMI 0.4.8, with c-ares 1.11.0, with Lua 5.2, with GnuTLS
3.2.15, with Gcrypt 1.6.2, with MIT Kerberos, with GeoIP, with QtMultimedia,
with AirPcap.
Running on 64-bit Windows 10, build 10586, with locale C, with WinPcap version
4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version 1.0 branch
1_0_rel0b (20091008), with GnuTLS 3.2.15, with Gcrypt 1.6.2, without AirPcap.
Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz (with SSE4.2), with 8097MB of physical
memory.
Built using Microsoft Visual C++ 12.0 build 40629
You are receiving this mail because:
- You are watching all bug changes.
