The WebRTC online demos allow you to experience WebRTC technology and its capabilities (voice, video, data sharing) for real. Call a phone number, an IP-phone, using traditional phone numbers. Connect to a colleague using WebRTC and establish a video-conferencing session.
WebRTC and FreeSwitch (for Communications Solution Providers)
Solution providers offering applications such as video-conferencing or customer service applications have always struggled with interoperability and support of end devices (traditional phones, soft phones, VoIP clients, etc.) using proprietary technologies. WebRTC promises to establish a standard client that will be available in every platform.
Daitan leveraged its expertise in communications systems to integrate WebRTC applications to the FreeSwitch project and create a deployment in the cloud that can demonstrate end-to-end connections between any combination of WebRTC and other VoIP endpoints using a SIP-based signaling plane in a cloud architecture. This demo shows the possibility to seamlessly integrate WebRTC to the existing commercial conferencing infrastructure and support the transition from a world using proprietary endpoints to a world that embraces Internet technologies.
WebRTC and IMS in the Cloud (for Telecom Operators)
If IP-based communications is unavoidable, telecom operators would like it to be independent of mobile and social platforms (Skype, Google, IOS, etc.). WebRTC offers an alternative that has potential for universal access integrated with traditional telephony in an IMS system.
Daitan leveraged its expertise in communications systems to integrate WebRTC applications to the Clearwater project and create a deployment in the cloud that can demonstrate end-to-end connections between any combination of WebRTC and traditional telephony end-points using a SIP-based signaling plane in an IMS architecture. This demo shows the possibility to seamlessly integrate WebRTC to the existing telephony infrastructure and support the transition from a world using a mix of PSTN and cell phones to communicate worldwide in real time to a world that embraces Internet technologies.
To access the demonstration and make real calls from WebRTC, please visit the WebRTC Demo Landing Page.
To download the White Paper "WebRTC and Universal Communications: A New Era in Telecom", please Click Here.
WebRTC is an important step towards Universal IP-based Communications
It took us the entire 20th century to evolve PSTN technology and build an infrastructure that made phone lines available in virtually every home in the developed world.
In the mid-1980, the first cellular networks appeared, and it took only 25 years before cell phones reached near-universal coverage. As of 2014, more people have access to cell phones than to clean water.
As cell phones emerge towards universal coverage, use of the traditional PSTN is declining quickly. Today, more than 1/3 of the US households have dropped their phone landlines (2012 NHIS Survey), and rely on mobile phones and the Internet for all connectivity needs.
In the early 2000's we saw the first consumer Internet communication applications (like Skype) become popular. Initially these tools were primarily used to make free phone calls when connecting with family from a computer, but we now see increasing use in business and mobile applications, with additional rich media capabilities (voice, video, chat, screen share).
So, over the next few years, we can anticipate that IP-based communications will eventually reach that point of universal coverage and, if patterns repeat, use of cellular phones for real-time communication (RTC) will decline after that. What is the role of WebRTC on this evolution?
For an extended discussion on this, and to access to online WebRTC Demos, please download the white paper "WebRTC and Universal Communications - A new era in Telecom".
Until recently, integrating an application to the telecom infrastructure (so that, for example, a website or mobile app could offer click-to-call or video conferencing capabilities without the installation of an additional native application) required developers to understand and use telecom or VoIP protocols (SS7, SIP, etc.). It comes as no surprise that the web/cloud applications and the telephony spaces have remained separate fields.
However things are changing fast. From its early start in the mid-1990s, VoIP technologies grew to represent a market of about $70B in 2013 (Infonetics). Amazon launched AWS cloud computing services in 2006 and is now joined by other giants like Google and Microsoft. The age of IP-based communications and cloud computing is here.
As VoIP technologies reached maturity, several new companies launched the Telecommunications API industry – allowing web/cloud software to interface with telephony and SMS networks using standard web API's. Examples of such companies include 2600Hz, 46elks, Bandwidth.com, Callfire, MediaBurst, Nexmo, Plivo, Tropo, Twilio, and Voxeo.
For an extended discussion of Telecom Cloud API's, download the white paper "Telecom Cloud API's - Integrating Web/Cloud Solutions with Real-Time Communications". This paper explains Telecom API's, lists their most common use cases, features available from most vendors, and helps choosing the best vendor for a particular application.
Daitan Group is a software development service provider with focus in Telecom, Unified Communications and real-time Cloud/Web Solutions. We partner with technology vendors to help them develop their next software solution. Daitan has organizational experience both helping Telecom API providers to develop their offerings and helping solution developers create their products leveraging Telecom APIs. To know more about what Daitan can do for you, please visit http://daitangroup.com
(Click below to see the live newsletter)
Once upon a time, people just wrote code and then ran it to find how well it worked. Working individually, the developer was able to iterate quickly until the software was useful to solve a real problem.
As software became more complex, it was broken into separate and independent sub-modules developed more or less in isolation by individual developers. Each sub-module was tested, the system was integrated back together, then tested, staged, released, deployed. Software development cycles stretched over several months (or several years).
The pendulum is swinging back. Software engineering is now evolving towards shortening the feedback loops and minimizing the time it takes from code being written to being in production. This time, we want to do it with more quality and predictability. The tools to achieve that are processes, automation, and collaboration.
Moving across the levels depicted on the picture above (Source Code Control, Build Automation, Test Automation, Continuous Integration, Release Automation, Continuous Delivery) is not simple. It involves not only changing processes and automating them, but also changes in culture and organization.
Continuous Integration (CI) is the practice of accelerating the daily commits of code by software developers. If in the past developers would work for weeks before trying to integrate their work to the main tree, in a CI environment you want developers to check-in their work several times a day.
A CI server monitors code check-ins by developers and, as often as practical, it builds the system and runs unit and integration tests. If there is any failure in the process, the CI server alerts the developers. A broken build gets the attention and top priority from the team.
CI requires test-driven development and automation.
Once you are doing Continuous Integration and is able to automate the deployment process, you can consider extending the process and automation all the way to the end-user. Continuous Delivery (CD) is the practice and ability to rapidly, reliably and repeatedly push out enhancements and bug fixes to customers at low risk and with minimal manual overhead.
The automation system let changes to the system be released on a granular basis. Releasing features just to a subset of users and being able to seamless roll back to a previous version becomes possible.
The result is that there is no delay between enhancements and bug fixes being implemented and available to users.
Download Daitan White Paper Now
At Daitan, we work with organizations at different stages of agility. In more conservative and regulated markets (e.g. core telecom), companies operate in a fully structured waterfall model where software goes through discrete and serial phases of development, unit testing, integration and system testing. Companies producing software that is deployed in the Cloud and offered as a service are the ones most aggressively pursuing agility in software development.
The majority is somewhere around the middle of the diagram, trying to move towards more agile software engineering processes. Most of our customers have implemented significant test automation and continuous integration capabilities and are starting to move towards extending that towards release and delivery to end users.
Do you have traditional On-Premisse software you want to move to the cloud? Are you building a solution to be offered in a SaaS model?
The "Reference Model for Cloud Applications" diagram above can help you to evaluate your solution and imagine how a cloud version of your current software should look like.
For a complete discussion on moving applications to the cloud and offering them under a SaaS business model, please download the paper "Reference Model for Cloud Applications - Considerations for SW vendors building a SaaS solution".
Download the White Paper now:
Page 1 of 6