Currently, is still in development discussion for its complete implementation whereas (under Vxi*/Asterisk implementation) is already available for any project’s deployments. We have prepared this summary to clarify what are the main features and how to move forward for your business.
We consider, WebRTC is a solution for the future and RTMP a solution for the present that could be required for a while. The question is not whether WebRTC or RTMP, the question is: RTMP, yes sure and WebRTC too, if all industry adopt it properly and make it interoperable over all the web and telephony systems…
The right choice in 2013 and for next years, is to select RTMP to wait for WebRTC complete maturity and continue working with both over your Vxi*/Asterisk platform. Remember, you may know that WebRTC could loose the current battle for its standardization and interoperability, with many implementation proposals over the top web browsers or with a divergent market approach from Google, Microsoft, Apple,…
[dt_divider style=”narrow”/]
Features
Protocol
Work on all Web Browsers
Call Session Protocol
Bandwidth/Quality auto-update
SIP interoperability
DTMF
Voice Codecs
Video Codecs
Autologin
Codec Negociation
Voice over Video Priority
Call without registering
Mobile implementation approach
Web Plugin
IP Packet
Ready Now?
Ready for Next Years?
Phone Interoperability
WebRTC
ETF Open Standard
No, Chrome, Firefox for now
No
No
Yes
Yes
g711, iLBC, iSAC
VP8, H264?
No
Required
No
No
Web app. (require a Browser)
Javascript required
TCP / SRTP
No (under development)
?
Mostly SIP implementations
RTMP
Adobe’s Open Public Protocol
Yes, 99% of all Web Browsers
Yes
Yes
Yes
Yes
g711, Speex
Sorenson Spark, VP6*, H264*
Yes
Not required (internal def.)
Yes
Yes
Native app. (Mobile OS)
Flash Player required
TCP / UDP*
Yes
Yes
SIP, H323, ISDN, SS7…
*Not yet availble for RTMP Channel Server
[dt_divider style=”narrow”/]One more thing…
As we work days a days with customers on an immediate return on investment for RTC developments, we don’t take a “geek’s approach” with new promising technologies or trends. Any customer has to work under real-world conditions and get results for its business over the existing web browsers and production’s systems.
[dt_divider style=”double-gap”/]Some other articles you may read:
- I6NET: How to make calls over the web?
- WebRTChacks: Why the WebRTC API has it wrong?
- NoJitter: Will Microsoft Ever Support Google’s Version of WebRTC?
- Flasphoner: Do you think HTML5-WebRTC Phone Ready? not yet
- OnSIP.com/blog: WebRTC, SIP and HTML5 brief introduction
- InfoWorld.com: WebRTC Browser communications standard has serveral hurdles clear
- Pro.Clubic.com: Interview w3c retour enjeux WebRTC
- Formtek/blog: WebRTC to Enable Peer-to-Peer Browser Communications
