- From: Iñaki Baz Castillo <ibc@aliax.net>
- Date: Tue, 3 Sep 2013 19:06:36 +0200
- To: Martin Thomson <martin.thomson@skype.net>
- Cc: public-orca <public-orca@w3.org>
2013/9/3 Iñaki Baz Castillo <ibc@aliax.net>:
> 2013/9/3 Martin Thomson <martin.thomson@skype.net>:
>> Unfortunately, this will be unable to produce DTMF that is compatible with any existing DTMF sender or receiver. The problem is that the DTMFTrack is a standalone entity that does not associate with an existing audio track.
>
>
> I don't see such a problem
Just to clarify:
RTCConnection.addDtmfTrack( )
-----------------------------------------------------
Adds a sending {{RTCDTMFTrack}} to the {{RTCConnection}}. The sending
{{RTCDTMFTrack}} has its corresponding {{RTCTrack}} instance (which
can be retrieved via the track or tracks methods) with same SSRC and
msid values than the audio track it is attached to, but different kind
attribute ("dtmf") and codec. At RTP level, a DTMF track shares the
same SSRC value as an audio track, but uses a different payload-id.
The function can be called with an optional "container" argument which can be:
- no argument: the DTMF track is attached to the first sending audio
track in the {{RTCConnection}}.
- {{MediaStream}}: the DTMF track is attached to the first sending
audio track in the given {{MediaStream}}.
- {{MediaStreamTrack}}: the DTMF track is attached to the given audio
{{MediaStreamTrack}}.
https://github.com/openpeer/ortc/blob/master/draft-w3c-ortc-api-00.md#adddtmftrack
--
Iñaki Baz Castillo
<ibc@aliax.net>
Received on Tuesday, 3 September 2013 17:07:33 UTC