Danny Windham, Digium CEO, Keynote address - ITEXPO East 2015, Miamii

Editor's Notes

• #2: You know, we come here every year, and we talk about changes in our industry – and over time, some of those changes have been very significant. But, the majority of changes we’ve witnessed over the past several years have been impacted the underlying technology used to build communications systems – and as such are really about the internal plumbing – or the way we construct and implement our communications systems. And - for the most part – these changes have done little to change the model by which we use or communications systems.
• #3: 2
• #4: 3
• #5: 4
• #6: 5
• #7: And about the time the last small town in the US got phone service – most of us had converted our desks to communication device shrines – computer monitors, fax machines, scanners, multiline phones, etc
• #8: It’s interesting that, even today, most businesses configure communications as a standalone application. We all run some collection of business apps in order to power the underlying processes of our businesses.
• #9: 8
• #10: So today, I want to talk about a coming change that involves the model of how we use communications technology – not how we implement communications technologies.
• #11: The change is a evolution away from communications as a standalone app – to a world where communications is directly integrated into every aspect of how business operate. No more island. Communications is being voted off the island.
• #12: 11
• #13: 12
• #14: 13
• #15: 14
• #16: And while the pace of change seems to have accelerated - it’s going to change even faster over the next 5 years – because in the future – communications will move
• #17: It’s voting communications off the island – and integrating communications features and functions into middle of every aspect of how businesses operate.  
• #18: 17
• #19: 18
• #20: 19
• #21: Even if the boss is a luddite – there’s a step you can take.
• #22: 21
• #23: For those that are mildly progressive, your step is to select and implement products that offer some level of ‘out of the box’ integration between applications
• #24: 23
• #25: 24
• #26: For those that are mildly progressive, your step is to establish simple integrations between business systems using the API’s – to create an integration that’s not available out of the box.
• #27: 26
• #28: And – if you’re cautiously adventurous – then incorporating open source technology into your communications solution can provide a way to do more than what can be done just through published APIs. In one sense, open source communications projects give developers the ultimate control in integrating communications into their company’s existing business processes. Open source engines have enable the long tail of communications applications – allowing developers to build integrated solutions that didn't exist in pre packages solutions.
• #29: 28
• #30: And – if you’re aggressively adventurous – then you need to introduce yourself to the world of web communications …
• #31: Web Communications is about building real time communications apps using standard web technologies – HTML, Javascript, and Cascading Style Sheets.   It inherently support multiple modes of communications – including voice, chat, video, screen sharing, and file sharing.   Its encrypted – and its peer-to-peer – so traffic flows outside of the traditional communications service providers.
• #32: Web Communications will leverage WebRTC – which is an emerging standard that when supported within a web browser – allows that browser to become a communications end point device for WebRTC enabled applications and services. Chrome and Firefox are currently leading the pack for WebRTC support – but MSFT has pledged support and it’s rumored that Apple will add support to Safari although there are no published plans for such. Disruptive analysis predicts that by 2019 – there will be 6B devices in the world supporting WebRTC – which means that your mobile device, your tablet, your laptop – any device running a webRTC browser can now become a communications endpoint without the need for client software. This is a fundamental enabler for communications moving to the web.
• #33: 32
• #34: Here you see a simplified view of the Brightstream architecture. The boxes at the top represent clients – in this case web clients – which are connected to the Brightstream platform. The connections in blue represent access over a combination of HTTPS and secure WebSockets. The WebSocket connections allow for asynchronous bi-directional communication between the client and server. This channel is used as the transport for messages – call signaling messages, user-to-user text messages and application control and data messages defined by the application developer. This messaging capability is the basis for all higher-order modes of communication. Built atop the base message-passing architecture are key features like presence, group messaging, publish and subscribe services, and all of the live or real-time communication capabilities of the platform. The message routing service is built to scale seamlessly by simply adding additional front-end API nodes and back-end message routers. Another critical service provided by Brightstream is media relay. Some percentage of calls require the assistance of a media relay server to work around limitations and impediments imposed by NATs and firewalls. Brightstream seamlessly integrates media relay using a dynamic network of TURN servers. When users attempt to create a peer-to-peer connection, the Brightstream platform provides access to the TURN server network. In those cases where a direct peer-to-peer connection cannot be established, the TURN server is used.
• #35: And while all of that is cool and disruptive – what would integrated communications allow you to do?
• #36: So, How about connecting your web site to your UC solution? Using a communications PaaS – and a UC Solution with an API – you can have a customer who is browsing your web site with a WebRTC enable device (Android tablet for example) connect with your sales team suing the existing call queue and sales process. By pressing a button on your website – a call can be created and delivered to the appropriate call queue (context passed) – thereby integrating your web site and you sales department.
• #37: And if your hair is on fire to integrate real time communications into your business to add value – how about
• #38: 37
• #39: Think about it like Amazon did. It our understanding that Amazon has built the Mayday button on the new Kindle using WebRTC – so imagine having a support person there to help just with the push of a button
• #40: Envision a customer support portal where you talk with your customers directly through the web site. Conversations begin as a web chat – promote to a voice or video call – and maybe add screen sharing to help that customer find exactly what they’re looking fro? All of these things are possible when we change the model of how we use our communications technologies.
• #41: 40