Google Git
Sign in
webrtc / src / / 3518e7bea490fb74cf52c5e37aa0a7c8fda8630e
commit3518e7bea490fb74cf52c5e37aa0a7c8fda8630e[log] [tgz]
authorZhi Huang <zhihuang@webrtc.org>Tue Jan 30 21:20:35 2018
committerCommit Bot <commit-bot@chromium.org>Tue Jan 30 23:07:28 2018
tree92a57b49e43b6c5abb3d7ff43a40a4132cc59cb3
parent018dd6e9d102c93788d62673f81c710a4bc101a2 [diff]
Add the rejected TransportInfo when creating an answer.

Previously, if a media section is rejected by the answerer, the TransportInfo
of that section will not be added to the answer but when answer SDP is
deserialized by the offerer, the rejected TransportInfo will be added.

This CL fixes this inconsistency by adding the TransportInfo of all the m=
sections including the rejected ones.

Bug: webrtc:8818
Change-Id: I3b163245979c4ac4df31db39262e499f1c4901c4
Reviewed-on: https://webrtc-review.googlesource.com/46380
Reviewed-by: Taylor Brandstetter <deadbeef@webrtc.org>
Commit-Queue: Zhi Huang <zhihuang@webrtc.org>
Cr-Commit-Position: refs/heads/master@{#21815}
2 files changed
tree: 92a57b49e43b6c5abb3d7ff43a40a4132cc59cb3
  1. api/
  2. audio/
  3. build_overrides/
  4. call/
  5. common_audio/
  6. common_video/
  7. data/
  8. examples/
  9. infra/
  10. logging/
  11. media/
  12. modules/
  13. ortc/
  14. p2p/
  15. pc/
  16. resources/
  17. rtc_base/
  18. rtc_tools/
  19. sdk/
  20. stats/
  21. system_wrappers/
  22. test/
  23. tools_webrtc/
  24. video/
  25. .clang-format
  26. .git-blame-ignore-revs
  27. .gitignore
  28. .gn
  29. .vpython
  30. AUTHORS
  31. BUILD.gn
  32. CODE_OF_CONDUCT.md
  33. codereview.settings
  34. common_types.cc
  35. common_types.h
  36. DEPS
  37. LICENSE
  38. license_template.txt
  39. LICENSE_THIRD_PARTY
  40. native-api.md
  41. OWNERS
  42. PATENTS
  43. PRESUBMIT.py
  44. presubmit_test.py
  45. presubmit_test_mocks.py
  46. pylintrc
  47. README.chromium
  48. README.md
  49. style-guide.md
  50. typedefs.h
  51. WATCHLISTS
  52. webrtc.gni
  53. whitespace.txt
README.md

WebRTC is a free, open software project that provides browsers and mobile applications with Real-Time Communications (RTC) capabilities via simple APIs. The WebRTC components have been optimized to best serve this purpose.

Our mission: To enable rich, high-quality RTC applications to be developed for the browser, mobile platforms, and IoT devices, and allow them all to communicate via a common set of protocols.

The WebRTC initiative is a project supported by Google, Mozilla and Opera, amongst others.

Development

See http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.

Authoritative list of directories that contain the native API header files.

More info