Re: [rtcweb] JSEP: Issues with a=ssrc and RTP payload type switching

[Roman Shpount <[e-mail]>]

On Wed, Jun 3, 2015 at 4:06 PM, Harald Alvestrand <[e-mail]>
wrote:

>
> If we want to have a mechanism that:
>
> a) allows PT switching
> b) uses different clock rates (and therefore different SSRCs)
> c) doesn't need renegotiation on SSRC change
>
> I would think that the initial SDP would have to contain a=ssrc fields for
> *all* the possible SSRCs - that is, one "a=ssrc:<nnnn> cname:<cname>" line
> per payload type.
>
> Section 5.2.1 already specifies that there will be multiple a=ssrc lines
> (and a=ssrc-group lines) in the case of RTX data. So it's not exactly a
> novel solution.
>
>
I agree with one small correction -- it is not a separate SSRC per payload
type, but separate SSRC per clock rate. For instance, if you have G.711
audio, RFC 4733 tones and CN at 8KHz, there is going to be a payload type
for each of them, but all this media should use the same SSRC. Opus, RFC
4733 tones and CN at 48Khz (and you will need to specify to different
payloads for tones and CN for different clock rates), will use second SSRC.

The reason for separate SSRCs is to have RTCP reports to work correctly,
which requires to use the same time units for all the media under
particular SSRC. Multiple payloads running with the same clock rate can
re-use the same SSRC without any issues. It actually is beneficial to use
the same SSRC since they can be synchronized based on the RTP time stamps
which would be more precise then ntp time.
_____________
Roman Shpount