Wireshark-bugs: [Wireshark-bugs] [Bug 11897] New: wrong order of the SIP messages in call flow o
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Wed, 16 Dec 2015 08:04:22 +0000
Bug ID 11897
Summary wrong order of the SIP messages in call flow of telephony function druing life capture
Product Wireshark
Version 1.12.8
Hardware x86
OS Windows 7
Status UNCONFIRMED
Severity Normal
Priority Low
Component GTK+ UI
Assignee bugzilla-admin@wireshark.org
Reporter rolstein@gmx.de 

Created attachment 14151 [details]
screenshots of call flow and corresponding packets

Build Information:
Version 1.12.8 (v1.12.8-0-g5b6e543 from master-1.12)

Copyright 1998-2015 Gerald Combs <gerald@wireshark.org> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled (32-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,
with
MIT Kerberos, with GeoIP, with PortAudio V19-devel (built Oct 14 2015), with
AirPcap.

Running on 32-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)2 Duo CPU     T7500  @ 2.20GHz, with 2015MB of physical
memory.


Built using Microsoft Visual C++ 10.0 build 40219

--
Using Wireshark for life capturing of VoIP trafic, it happens repetitively that
the call flow of menu telephony-VoIP calls shows the SIP messages in wrong
order (see screenshots in the attachement). As soon, as the life capture is
stopped and the trace is saved, the order of the sip messages is correct again.
This problem occurs on different Win 7 PC. It seems to be an old problem,
because the last version without this problem in my test environment is
Wireshark 1.6.2

You are receiving this mail because:
  • You are watching all bug changes.