commit a9329dbae21cabd4b860e729ecd7769f5bec9ac7
author Qiang Chen <qiangchen@chromium.org> Thu Dec 14 14:05:43 2017 -0800
committer Commit Bot <commit-bot@chromium.org> Mon Jan 08 17:53:39 2018 +0000
tree bc01ff57251035cc54a18d35e1e5ffcd00ac7237
parent e6aca637ce1a8086052f8c89e78fe6de3abcd0b9

Bug Fix: Peers Cannot Communicate If One With Stereo Codec, One Not

When Chromium hooks up with the stereo codec, then it has difficulty
communicating with a google chrome without stereo codec. By design, we
do allow codec choice for the standalone codecs, but the problem is
that we do not handle the payload correctly, and thus the existence
of stereo codec will remove the payload registry of the standalone
version of its associated codec. (For example, stereo codec on top of
VP9 will remove the payload registry of standalone VP9 codec.)

This CL fixes the issue. When generating payload data, we should use
"stereo" as payload name, instead of its associated codecs.


Bug: webrtc:8657
Change-Id: I9e0b54de6bd41d370b9353f9553c998e4049789f
Reviewed-on: https://webrtc-review.googlesource.com/33122
Reviewed-by: Emircan Uysaler <emircan@webrtc.org>
Reviewed-by: Stefan Holmer <stefan@webrtc.org>
Commit-Queue: Qiang Chen <qiangchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#21523}