Victor Boivie 5625a86f5a dcsctp: Handle re-received stream reset requests
When re-receiving a stream reset request with the same request
sequence number, reply with the same result as previous time. In
case the original request was deferred, and "in progress" was
replied, it's important to not indicate that it was performed
successfully as that will make the sender believe it has completed
before it did.

Bug: webrtc:14277
Change-Id: I5c7082dc285180d62061d7ebebe05566e5c4195c
Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/274080
Commit-Queue: Victor Boivie <boivie@webrtc.org>
Reviewed-by: Florent Castelli <orphis@webrtc.org>
Cr-Commit-Position: refs/heads/main@{#38012}
2022-09-05 11:56:10 +00:00
2022-08-29 21:04:32 +00:00
2022-09-02 15:37:13 +00:00
2022-09-02 10:52:49 +00:00
2021-01-20 15:01:07 +00:00
2022-02-20 14:22:13 +00:00
2021-12-08 08:53:00 +00:00
2022-07-01 15:17:36 +00:00
2022-09-01 17:20:57 +00:00
2022-09-05 07:56:40 +00:00
2022-05-13 09:01:34 +00:00
2020-07-13 11:42:07 +00:00
2022-08-11 14:44:52 +00:00
2022-08-12 11:03:03 +00:00

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 here 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

Description
No description provided
Readme 255 MiB
Languages
C++ 88.6%
C 3.3%
Java 3%
Objective-C++ 1.9%
Python 1.9%
Other 1%