| Bug ID |
11663
|
| Summary |
single RTP flow shown several times in VoIP calls graph window
|
| Product |
Wireshark
|
| Version |
1.12.8
|
| Hardware |
x86
|
| OS |
Windows 7
|
| Status |
UNCONFIRMED
|
| Severity |
Normal
|
| Priority |
Low
|
| Component |
Dissection engine (libwireshark)
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
Version 1.12.8 (v1.12.8-0-g5b6e543 from master-1.12)
Compiled (64-bit) with GTK+ 2.24.23, with Cairo 1.10.2, with Pango 1.34.0, with
GLib 2.38.0, with WinPcap (4_1_3), with libz 1.2.5, with SMI 0.4.8, with c-ares
1.9.1, with Lua 5.2, without Python, with GnuTLS 3.2.15, with Gcrypt 1.6.2,
without Kerberos, with GeoIP, with PortAudio V19-devel (built Oct 14 2015),
with
AirPcap.
Running on 64-bit Windows 7 Service Pack 1, build 7601, with WinPcap version
4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version 1.0 branch
1_0_rel0b (20091008), GnuTLS 3.2.15, Gcrypt 1.6.2, without AirPcap.
Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz, with 8141MB of physical
memory.
Built using Microsoft Visual C++ 10.0 build 40219
--
In the attached example , a single real RTP flow is shown two or even three
times in the VoIP calls flow graph window.
Clicking on any of the two (three) arrows always highlights the same packet in
the packet list.
I have not identified what decides whether it is drawn twice or three times,
but the fact that there are several calls in the capture does affect the
behaviour: when I tried to filter a single call's SIP and RTP packets into a
separate file so that I wouldn't attach such a huge file, getting the same
result on that reduced file turned out to be impossible.
The behaviour has been verified on 3rd and 4th line in the call list before
submitting the bug. The 2nd line in the list is a bit confusing as the same
Call reference ID is used in SETUPs encapsulated in all the SIP INVITEs.
It does not depend on whether I select just one of the calls (3rd, 4th) or
both, but when I've selected 3rd to 7th call together, the 7th was shown
properly.
Pavel
You are receiving this mail because:
- You are watching all bug changes.