Wireshark-bugs: [Wireshark-bugs] [Bug 6808] New: VoIP RTP packets incorrectly interpreted as T38
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6808
Summary: VoIP RTP packets incorrectly interpreted as T38
packets
Product: Wireshark
Version: 1.6.5
Platform: x86
OS/Version: Windows 7
Status: NEW
Severity: Normal
Priority: Low
Component: Wireshark
AssignedTo: bugzilla-admin@xxxxxxxxxxxxx
ReportedBy: sebastian.zenzerovic@xxxxxxxx
Build Information:
Version 1.6.5 (SVN Rev 40429 from /trunk-1.6)
Copyright 1998-2012 Gerald Combs <gerald@xxxxxxxxxxxxx> 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.22.1, with GLib 2.26.1, with WinPcap (version
unknown), with libz 1.2.5, without POSIX capabilities, without libpcre, with
SMI
0.4.8, with c-ares 1.7.1, with Lua 5.1, without Python, with GnuTLS 2.10.3,
with
Gcrypt 1.4.6, with MIT Kerberos, with GeoIP, with PortAudio V19-devel (built
Jan
10 2012), with AirPcap.
Running on 32-bit Windows 7, build 7600, with WinPcap version 4.1.2 (packet.dll
version 4.1.0.2001), based on libpcap version 1.0 branch 1_0_rel0b (20091008),
GnuTLS 2.10.3, Gcrypt 1.4.6, without AirPcap.
Built using Microsoft Visual C++ 9.0 build 21022
--
Hi,
seems that Wireshark incorrectly interprets G711 RTP frames as T38 packets
after unsuccessfull T38 (fax call) renegotiation. In the attached trace,
Wireshark decodes one-way RTP stream successfully but in the opposite direction
G711 RTP packets are wrongly decoded as T38.
If you filter the trace for "t38", save the displayed packets to a new pcap,
open the new pcap and decode the data as RTP you can actually listen / look at
the fax communication.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
