Re: [rtcweb] Rate for telephone-events in combination with OPUS

Same with Firefox: https://bugzilla.mozilla.org/show_bug.cgi?id=964282

> On Jul 17, 2014, at 10:02, Justin Uberti <juberti@google.com> wrote:
> 
> For Chrome, we just haven't gotten to it yet. I think there is an open bug on it.
> 
> 
>> On Wed, Jul 16, 2014 at 11:48 PM, Roman Shpount <roman@telurix.com> wrote:
>> So, I guess the fact that neither Chrome no Firefox do this is an oversight or an unimplemented feature.
>> 
>>> On Jul 16, 2014 11:14 PM, "Justin Uberti" <juberti@google.com> wrote:
>>> Yes, this is my understanding as well.
>>> 
>>> 
>>>> On Wed, Jul 16, 2014 at 2:45 PM, Roman Shpount <roman@telurix.com> wrote:
>>>> Should we specify two telephone-events payloads, one with 8000 rate to be used with PCMU/PCMA and another with 48000 rate to be used with OPUS?
>>>> 
>>>> From what I can see, based on RFC 7160, if OPUS codec is used telephone-events should either be transmitted with the rate 48Khz or use a different SSRC. On the other hand if PCMU/PCMA is selected then DTMF should be transmitted using 8000 clock or use a different SSRC. Using different SSRC is problematic since it will create synchronization issues with audio playback (things like record your name and press pound will stop working) apart from other webrtc related issues. I think the only solution that makes sense is to advertise two telephone-events payloads and use the appropriate one based on the selected transmit codec, similar to CN.
>>>> _____________
>>>> Roman Shpount
>>>> 
>>>> _______________________________________________
>>>> rtcweb mailing list
>>>> rtcweb@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/rtcweb
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb