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 4767] New: Multiple RTP Payload Type values for H264

Date: Sat, 15 May 2010 12:10:47 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4767

           Summary: Multiple RTP Payload Type values for H264
           Product: Wireshark
           Version: 1.2.7
          Platform: Other
        OS/Version: Windows XP
            Status: NEW
          Severity: Normal
          Priority: Low
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: carunach@xxxxxxxxx


Created an attachment (id=4654)
 --> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=4654)
packet-h264.c.patch

Build Information:
Version 1.3.6Arun-h264

Copyright 1998-2010 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 with GTK+ 2.16.6, (32-bit) with GLib 2.22.4, with WinPcap (version
unknown), with libz 1.2.3, 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.8.5, with
Gcrypt 1.4.5, with MIT Kerberos, with GeoIP, with PortAudio V19-devel (built
May
11 2010), with AirPcap, with new_packet_list.

Running on Windows XP Service Pack 2, build 2600, with WinPcap version 4.1.1
(packet.dll version 4.1.0.1753), based on libpcap version 1.0 branch 1_0_rel0b
(20091008), GnuTLS 2.8.5, Gcrypt 1.4.5, without AirPcap.

Built using Microsoft Visual C++ 8.0 build 50727
--
Currently, H.264 dissector in Wireshark allows only one value for the "H264 
dynamic payload type" preference value.

On a video call, it is possible to have asymmetric RTP payload type. For 
example, transmit direction may use 97 and receive direction use 98. With the 
above restriction, it is possible to decode only one direction in this 
scenario.

This patch allows users to specify a value range for this parameter (96-127) 
so that both streams can be decoded for a video call with asymmetric rtp 
payload types. This patch uses the same code that is implemented for "TCP 
ports" parameter in HTTP dissector (packet-http.c)

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.