WebRTC Expo and iNum

This week the WebRTC Expo is taking place in Atlanta, GA where attendees are learning about an exciting collection of technologies that promises to integrate voice, video and collaboration into any web-page. Speakers at the conference pointed to 20 million JavaScript capable programmers, vs. an estimated eight thousand SIP developers. Hence WebRTC will democratize web communication enabling the estimated one billion end points that are expected to support it. The WebRTC standard does not specify signaling methods. Developers can pick the one they feel best suits the application. Will this cause further fragmentation of communications into even smaller and less connectable islands?

What identifier will be used to connect Web-RTC endpoints? So far for peer to peer, it would appears to be an IP address. Will more permanent identity validation be provided by facebook login, email addresses, cookies or another other method? But why not an iNum number and map that to WebRTC identities so they can interact with the traditional telephony world? While traditional geographic DIDs can fill this objective, iNum numbers have the particular advantage for large scalable implementations since they are available for free. iNum was originally conceived as a bridge between the SIP and PSTN worlds, but can also perhaps play a similar role for the emerging WebRTC world.

At the WebRTC Expo, several hybrid SIP/PSTN/WebRTC services are on display, for example APIDAZE Labs demo’ed their API in action to create a WebRTC demo, including a PSTN DID (a local Atlanta number via iNum parent Voxbone) enabled conference room.

WebRTC developers are invited to experiment with free iNum numbers. Contact us to get yours today.

Comments are closed.