Steve Anton 07563732f6 [Unified Plan] Avoid offering two senders with the same ID
This can happen with the following sequence of API calls:
1) AddTrack(track) + offer/answer
2) RemoveTrack(track's sender) + offer/answer
3) AddTrack(same track)

Since the first transceiver had already been used to send, it will
not get re-used by the second call to AddTrack. Another RtpSender
will be created with its ID = the track ID. But the code hits a
DCHECK when CreateOffer is later called since both m= sections will
offer the same track ID component of the MSID.

The fix implemented here is to randomly generate a sender ID if
there is already an RtpSender with the track's ID.

Bug: webrtc:8734
Change-Id: Ic2dda23d66e364e77ff7505e1c37e53105a17dae
Reviewed-on: https://webrtc-review.googlesource.com/84249
Commit-Queue: Steve Anton <steveanton@webrtc.org>
Reviewed-by: Taylor Brandstetter <deadbeef@webrtc.org>
Reviewed-by: Henrik Boström <hbos@webrtc.org>
Cr-Commit-Position: refs/heads/master@{#23748}
2018-06-26 19:06:17 +00:00
..
2018-06-19 14:00:39 +00:00
2018-06-19 14:00:39 +00:00
2018-06-19 14:00:39 +00:00
2018-06-19 14:00:39 +00:00
2017-12-12 09:27:07 +00:00
2018-06-19 14:00:39 +00:00
2018-06-19 14:00:39 +00:00
2018-06-19 14:00:39 +00:00
2018-02-03 19:28:58 +00:00
2018-06-19 14:00:39 +00:00
2018-06-19 14:00:39 +00:00
2018-06-19 14:00:39 +00:00
2017-10-30 18:08:29 +00:00