On September 18, 2015 Microsoft announced that a preview version of the ORTC API implementation is available in the latest Windows Insider Preview release for Microsoft Edge. Microsoft’s initial ORTC implementation includes the following components:

  1. ORTC API Support. Primary focus right now is audio/video communications. Microsoft havs implemented the following objects: IceGatherer, IceTransport, DtlsTransport, RtpSender, RtpReceiver, as well as the RTCStats interfaces that are not shown directly in the diagram.
  2. RTP/RTCP multiplexing is supported and is required for use with DtlsTransport. A/V multiplexing is also supported.
  3. STUN/TURN/ICE support. Edge supports STUN (RFC 5389), TURN (RFC 5766) as well as ICE (RFC 5245). Within ICE, regular nomination is supported, with aggressive nomination partially supported (as a receiver). DTLS-SRTP (RFC 5764) is supported, based on DTLS 1.0 (RFC 4347).
  4. Codec support. For audio codecs, Edge supports G.711, G.722, Opus and SILK. Edge also support Comfort Noise (CN) and DTMF according to the RTCWEB audio requirements. For video we currently support the H.264UC codec used by Skype services, supporting advanced features such as simulcast, scalable video coding and forward error correction. We’re working toward to enabling interoperable video with H.264.

Microsoft is updating their implementation to match recent updates in the latest ORTC specification. The ORTC spec has been relatively stable since the ORTC CG issued the “Call for Implementations,” and Microsoft doesn’t expect a huge challenge at the JavaScript API level. Based on this, Microsoft believes their implementation is ready for cross-browser interoperability testing at the protocol level.

Content Source

You can find more information about the Microsoft’s announcement on their blog.

Read the Full Story