[ortc] SSRC values should not entered by the user

ibc has just created a new issue for https://github.com/openpeer/ortc:

== SSRC values should not entered by the user ==
Currently, if the user calls `RtpSender.send()` without setting 
specific SSRC values, the browser will choose them. This is fine. The 
problem is that, at that point, RTP negotiation is already supposed to
 be done so we cannot signal our SSRC. Even worse: `RtpSender` does 
not have a `getRtpParameters()` method that retrieves the effective 
parameters (including SSRC values chosen by the browser).

This basically means that the user (the JS) is required to manually 
set a random SSRC which IMHO is not very cool.

NOTE: I do know that, given "RTP Matching Rules" the receiver may be 
able to somehow correlate received RTP packets, but that is not valid 
for all the cases (if I send two video tracks over two `RtpSenders` 
over the same `DtlsTransport` and choose the same PT value for both, 
the receiver won't be able to properly demux RTP packets belonging to 
both video streams, so SSRC values are required).

Please view or discuss this issue at 
https://github.com/openpeer/ortc/issues/438 using your GitHub account

Received on Monday, 21 March 2016 10:34:22 UTC