Skip navigation
All Places > Ignite Realtime Blog > 2013 > February

Bla, bla bla...

WebRTC is on the march


With a stable implementation in Chrome since ver 23, applications are appearing as fast as flowers blooming in Spring. The nightly and developer builds (ver 25+) have more features including full desktop screen capture and ability to send it as a video stream over a peer connection. By adding DTLS encryption to Chrome nightly build, Google have achieved interoperability with Firefox nightly build.


Back in 2007 at ignite realtime, we built the first open source Flash to SIP gateway for SparkWeb and followed that up a few months later with Red5phone, the first open source web soft phone. Red5phone has now evolved into Apache OpenMeetings Red5Sip.


Fast-forward to today and we now have the iNum initiative from Voxbone which enables us to have a new geographical independent phone number for free phone calls on the Internet. iNums are global, supported by most telephone carriers including my former employer BT in the UK. Combine WebRTC with iNum and you can send and recieve free phone calls anywhere in the world provided you have a web browser and an iNum.


That was all the incentive I needed to get started on webrtc-phone.

Ok, so what does it do?


The prime purpose is to make and recieve free phone calls with iNums. It can also make SIP calls with domains that accept them.


For more details go to the project page.


How did I make it. What did I use?


  • Customized version of Phono SDK for webrtc only that connects to the Voxeo SIP cloud and handles the Jingle signalling and WebRTC media. Flash support has completely been removed. It only works with Chrome ver 23+ for now. Firefox support will come later
  • Openfire Server with websockets and redfire plugins to lookup iNums and map to Phono SIP addresses using XMPP Presence for anonymous users.
  • Candybar and DialPad? GUI components from AT&T Foundry and &Yet
  • AddThis social sign on service for Facebook, Google and Twitter


Free calls! Whats the catch?


Calls from iNum to/from the public PSTN still costs money. If you divert your iNum to a mobile or landline, your voice service provider will charge you for diverting the call. You will be paying for all calls from your iNum to your mobile or landline phone.


Calls from the public PSTN to your iNum cannot be intercepted and are therfore are not supported by webrtc-phone. If your iNum is dialed from a regular phone, the call will end up on whatever device you have forwarded it to. It is only when the number is dialed from a webrtc-phone elsewhere that it will be re-mapped to your webrtc-phone session.

Can I play?....


Live demo is hosted at  by the very kind folks at who are also members of the ignite realtime community.


Project source code is hosted on a Git repository at, so go ahead and clone

The Ignite Realtime community is happy to announce the release of version 3.8.0 of Openfire! Downloads for various platforms are available here.


Openfire is a real time collaboration (RTC) server licensed under the Open Source Apache license. It uses the only widely adopted open protocol for instant messaging, XMPP (also called Jabber). Openfire is incredibly easy to setup and administer, but offers rock-solid security and performance.


This release accumulates development efforts made over the past fifteen months. Some highlights of this release are:

  • the new Hazelcast-based clustering plugin (subject of an earlier blog post)
  • substantial improvements to the functionality, scalability and stability of the PubSub implementation (including fixing the PEP related memory leak)
  • improvements of the server-to-server connectivity routines
  • many performance improvements and general bug fixes

The changelog lists these and other changes in more detail.


As always, we welcome your feedback, suggestions, tips, hints, questions and other contributions in the Ignite Realtime Community pages.

Filter Blog

By date: By tag: