Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-bugs: [Wireshark-bugs] [Bug 10017] New: Wireshark 1.10.6 does not decode some T.38 str

Date: Tue, 22 Apr 2014 16:24:11 +0000
Bug ID 10017
Summary Wireshark 1.10.6 does not decode some T.38 streams.
Classification Unclassified
Product Wireshark
Version 1.10.6
Hardware x86
OS Windows 7
Status UNCONFIRMED
Severity Normal
Priority Low
Component Dissection engine (libwireshark)
Assignee [email protected]
Reporter [email protected]

Created attachment 12720 [details]
Undecoded T.38 starts at frame 86

Build Information:
Version 1.10.6 (v1.10.6 from master-1.10)

Copyright 1998-2014 Gerald Combs <[email protected]> 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.14, with Cairo 1.10.2, with Pango 1.30.1, with
GLib 2.34.1, with WinPcap (4_1_3), with libz 1.2.5, without POSIX capabilities,
without libnl, with SMI 0.4.8, with c-ares 1.9.1, with Lua 5.1, without Python,
with GnuTLS 2.12.18, with Gcrypt 1.4.6, with MIT Kerberos, with GeoIP, with
PortAudio V19-devel (built Mar  7 2014), 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 2.12.18, Gcrypt 1.4.6, without AirPcap.
        Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz, with 3316MB of physical
memory.


Built using Microsoft Visual C++ 10.0 build 40219

Wireshark is Open Source Software released under the GNU General Public
License.

Check the man page and http://www.wireshark.org for more information.
--
In some packet capture files, one T.38 stream is decoded as "Unknown RTP
version 0" while the other is corrected decoded as T.38. The "Decode as"
command also fails to decode these packets as T.38.
Wireshark 1.8.13 decodes the same files properly.


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