Call/text: +1 (604) 337-7899

RTT (Real Time Text) is something that some may think is important as part of the RTCWEB initiative, after all having a text component baked into the spec might make interoperability real, it also might help out with the hearing impaired.

Others feel that current technologies out there are more than sufficient to deliver RTT and we should leave it up to the developers eg. XMPP, SIMPLE, Open Peer, etc. etc. I would have to agree with that.

It seems the dataChannel was partially conceived to deal with this type of content, and adding more work to the heap there now is just going to delay things in the working groups. Let’s get the dataChannel supporting protocols, this seems like more important work and it might just take care of any RTT requirement by a developer?

Privacy Settings
We use cookies to enhance your experience while using our website. If you are using our Services via a browser you can restrict, block or remove cookies through your web browser settings. We also use content and scripts from third parties that may use tracking technologies. You can selectively provide your consent below to allow such third party embeds. For complete information about the cookies we use, data we collect and how we process them, please check our Privacy Policy
Youtube
Consent to display content from - Youtube
Vimeo
Consent to display content from - Vimeo
Google Maps
Consent to display content from - Google
Spotify
Consent to display content from - Spotify
Sound Cloud
Consent to display content from - Sound