[gstreamer-bugs] [Bug 324011] New: Invalid payload type definition for some rtp payloaders

[GStreamer (bugzilla.gnome.org)]

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=324011
 GStreamer | gst-plugins-good | Ver: 0.10.0

           Summary: Invalid payload type definition for some rtp payloaders
           Product: GStreamer
           Version: 0.10.0
          Platform: Other
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-plugins-good
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: andrunko at gmail.com
         QAContact: gstreamer-bugs at lists.sourceforge.net
                CC: all-bugs at bugzilla.gnome.org


As described in gst-plugins-good/gst/rtp/README the payload type for RTP packets
should be defined in a range between 0 and 255. According to
http://www.iana.org/assignments/rtp-parameters theses values should be between 0
and 127, while dynamic payload types should be defined between 96 and 127. To
fix this the folowing files should be updated:

gst-plugins-good/gst/rtp/gstasteriskh263.c
gst-plugins-good/gst/rtp/gstrtpamrdepay.c
gst-plugins-good/gst/rtp/gstrtpamrpay.c
gst-plugins-good/gst/rtp/gstrtpg711depay.c
gst-plugins-good/gst/rtp/gstrtpg711depay.c
gst-plugins-good/gst/rtp/gstrtpgsmdepay.c
gst-plugins-good/gst/rtp/gstrtph263pay.c
gst-plugins-good/gst/rtp/gstrtph263pdepay.c
gst-plugins-good/gst/rtp/gstrtph263ppay.c
gst-plugins-good/gst/rtp/gstrtpmp4vdepay.c
gst-plugins-good/gst/rtp/gstrtpmp4vpay.c
gst-plugins-good/gst/rtp/gstrtpmpadepay.c
gst-plugins-good/gst/rtp/gstrtpmpapay.c
gst-plugins-good/gst/rtp/README

Just change in the caps where there is
"payload = (int) [ 96, 255 ], " to "payload = (int) [ 96, 127 ], " and 
"payload = (int) [ 0, 255 ], " to "payload = (int) [ 0, 127 ], ".

------- You are receiving this mail because: -------
You are the assignee for the bug.
You are the QA contact for the bug.