Integrating Web-centric Media Processing for Simplified Development of Web-based Voice and Video Applications

Mike Chapman and Ken Osowski 7/13/2010

Ken Osowski
Director of Product Marketing

Webinar Target Audience
 For Web Service Providers and Enterprises – Add value to Web 2.0 sites and spur innovation by offering easy telecom-enablement for additional services – Rapid development: no need to learn/deal with telecom environment – Draw traffic: expand the usage of Web sites by bridging into service provider phone networks – Example(s): Google Voice, LinkedIn, Twillo, Fring, Facebook, Salesforce.com  For traditional Telcos – Who want to expand into Web 2.0 – Example(s): AT&T, Verizon, Sprint

SLIDE 3

© Copyright 2010 Dialogic Corporation. All rights reserved.

Analysts Size Web 2.0 Market Opportunity
 Enterprise Web 2.0 spending to reach $4.6 billion by 2013 (Source: Forrester Research)

 Enterprise Social Networking Market Expected to Reach $2 billion by 2013 (Source: Wainhouse Research)
 Web 2.0 mobile market is $20 billion Worldwide by 2013 (Source: Juniper Research)  Mobile social networking reaches $29 billion by 2012 (Source: Informa)  Mobile social networking will rise to $17.1 billion in 2013 (Source: Strategy Analytics)
SLIDE 4 © Copyright 2010 Dialogic Corporation. All rights reserved.

All rights reserved.What Kind of Web Services Require Media Processing?  Social networking click-to-call or click-to-video  Voice or video-enabling real-time communications from text “tweets”  Integration of audio and video for Web-based call center access  Web-accessible network-based messaging  Video portals  Adult entertainment  Mobile advertising  Location-based services SLIDE 5 © Copyright 2010 Dialogic Corporation. .

0 Web Services Telephony and Media Processing SLIDE 6 © Copyright 2010 Dialogic Corporation.Defining Some Terms     Application Programming Interface (API) Web 2. All rights reserved. .

Application Programming Interface (API)  An application programming interface – API – is an interface implemented by a software program which enables it to interact with other software components  The API represents an abstraction of functions/capabilities that are invoked by other components – Software components can be on the same computer or connected via a remote connection in a network using remote procedure calls (RPC) – Usage can be interactive user program accessing functions of a component or machine-to-machine (M2M) – API can represent a generalized set of functions or address a need in an application specific domain SLIDE 7 © Copyright 2010 Dialogic Corporation. . All rights reserved.

Web 2. mash-ups SLIDE 8 © Copyright 2010 Dialogic Corporation. wikis  Examples of Web 2.0 and the traditional World Wide Web (now referred to as Web 1.0 site allows its users to interact with each other as contributors to the website's content.0  The second generation of the World Wide Web. RSS-generated syndication. and enterprises  Representative Web 2. in contrast to websites where users are limited to the passive viewing of information that is provided to them  One of the most significant differences between Web 2.0 technology – Ajax. social bookmarking. .0) is greater collaboration among Internet users and other users. All rights reserved. content providers.0 usage include: – Blogging. especially the movement away from static web pages to dynamic and shareable content and social networking  A Web 2.

0 – SOAP (RPC)messages embedded in XML documents – Web 2.0 & 2.0 – REST (Representational State Transfer) style communications relying on HTTP  APIs conforming to the REST constraints are referred to as being ‘RESTful’  REST constraints are “properties” of the REST software architecture adhered to by the Web SLIDE 9 © Copyright 2010 Dialogic Corporation.Web Services  Web Services are Application Programming Interfaces (API) or Web APIs that are issued to a remote server using the Hypertext Transfer Protocol (HTTP)  A Web API is typically a defined set of HTTP request messages along with a definition of the structure of response messages – Typically expressed in EXtensible Markup Language (XML) or JavaScript Object Notation (JSON)  Web APIs – Web 1. All rights reserved. .

• Establishing real-time audio & video connections. media processing  Media Processing – Streaming of real-time audio & video for 2-way communications between callers – Processing phone key pad numbers (DTMF) if necessary – Manipulating the stream’s encoded format to bridge different media types on different call legs – Adding information to video media SLIDE 10 © Copyright 2010 Dialogic Corporation.e. i. . etc.Telephony and Media Processing  Telephony – The process of establishing real-time audio or video communications between two callers – Technology components of a call • Call signaling for call set-up. All rights reserved..

All rights reserved.Audio Media Processing SLIDE 11 © Copyright 2010 Dialogic Corporation. .

Video Media Processing SLIDE 12 © Copyright 2010 Dialogic Corporation. All rights reserved. .

All rights reserved.0 applications  Familiarity with API design model – Stick with proven Web API approaches  Eliminate complexity of traditional telephony programming – Developer may not be familiar with network-centric telephony model – Need to take a Web technology point-of-view  Leverage a media processing technology that is purpose built for integrating telephony with Web applications – Targeted for Web development and usage SLIDE 13 © Copyright 2010 Dialogic Corporation.Market Requirements for Web Media Processing  Very fast time-to-develop – Leverage existing Web development tools – Easily integrate with existing Web 2. .

Network-centric versus Web-centric Media Processing  Initiating voice calls from the Web using network-centric call processing approach* SIP Call Control App Server Internet Media Server Media Gateway PSTN Or Mobile Network Cell phone Voice phone SIP Media Control Voice Calls * . SLIDE 14 © Copyright 2010 Dialogic Corporation.Please refer to ‘USE CASE(S)’ portion of the Legal Notice on the last slide. All rights reserved. .

All rights reserved. SLIDE 15 © Copyright 2010 Dialogic Corporation.Please refer to ‘USE CASE(S)’ portion of the Legal Notice on the last slide. .Network-centric versus Web-centric Media Processing  Initiating voice calls from the Web using Web-centric call processing approach* HTTP /RESTful API Call & Media Control Media Server Media Gateway PSTN Or Mobile Network Cell phone Internet Voice phone Voice Calls * .

Mike Chapman Director of Product Management .

Traditional Deployment  Traditionally – An application uses SIP. NetAnn. VoiceXML. or MSCML to control an IP Media Server and initiate the specific media processing functionality desired – An active SIP call is required between an IP Media Server and the application server for each remote telephony endpoint that will be transmitting or receiving media to/from an IP Media Server – This required SIP session serves a dual role • Used by an IP Media Server to create the media stream directly between an IP Media Server and the remote endpoint • Used by the SIP session as a transport mechanism between the application server and an IP Media Server for the media control XML language content SLIDE 17 © Copyright 2010 Dialogic Corporation. All rights reserved. .

Traditional Deployment* Application Server Media Gateway SIP PSTN XML SIP RTP Dialogic® PowerMedia™ IP Media Server * .Please refer to ‘USE CASE(S)’ portion of the Legal Notice on the last slide. SLIDE 18 © Copyright 2010 Dialogic Corporation. . All rights reserved.

0 Interface Configuration  The Dialogic® PowerMedia™ Web Media Server (WMS) provides a new Web 2. .0 (RESTful) interface for control – New media control interface utilizes HTTP requests and responses to perform media and call control operations  PowerMedia WMS uses HTTP event streaming technologies to enable the client to receive asynchronous event notifications  The Web application does not use SIP call control – Application is not involved in call control signaling – Easier for web developers to use even if they are not familiar with telephony development SLIDE 19 © Copyright 2010 Dialogic Corporation. All rights reserved.Web 2.

.Web-centric Deployment* Web Server Media Gateway PSTN HTTP SIP RTP Dialogic® PowerMedia™ Web Media Server (WMS) * . SLIDE 20 © Copyright 2010 Dialogic Corporation.Please refer to ‘USE CASE(S)’ portion of the Legal Notice on the last slide. All rights reserved.

RESTful APIs  REST . . All rights reserved.REpresentational State Transfer  Requests and responses are built around the transfer of "representations" of “resources.” Resources accessed through URIs  REST-style architectures consist of clients and servers – Clients initiate requests to servers – Servers process requests and return appropriate responses SLIDE 21 © Copyright 2010 Dialogic Corporation.

. XML) – Set of operations supported by the web service using HTTP methods • • • • GET . All rights reserved.Delete existing resource SLIDE 22 © Copyright 2010 Dialogic Corporation.retrieve info about resource(s) POST .com/resources/ ) – MIME type of the data supported by the web service (Ex: JSON .RESTful APIs  A RESTful web service (also called a RESTful web API) is a simple web service implemented using HTTP and the principles of REST  Contains following 3 aspects: – Base URI for the web service (Ex: http://example.Create a new resource PUT .Modify existing resource DELETE .

which performs its processing actions and send the HTTP response. then the connection between the client and server is closed • With HTTP event/data streaming. the TCP connection remains open after the response is sent from the server. allowing the server to continue to send raw data to the client without notice SLIDE 23 © Copyright 2010 Dialogic Corporation.RESTful APIs  But……telephony applications must handle unsolicited events – DTMF digit detection – Play completion events – Conference events  Unsolicited events or client notifications do not fit well into the HTTP request / response model  Dialogic® PowerMedia™ Web Media Server (WMS) supports event streaming – HTTP event streaming is a mechanism that enables unsolicited events to be supported • In a normal HTTP interaction. . All rights reserved. the client sends a request to the server.

with API response details in HTTP body WMS HTTP Get to retrieve future asynchronous events 200 OK Response.RESTful Event Handling Client Application Thread HTTP POST with API specific URI and HTTP body HTTP 201 Created. All rights reserved. . No HTTP Body. TCP connection remains open for supplying future events DTMF(s) from caller DTMF(s) from caller Event Data Event Data SLIDE 24 © Copyright 2010 Dialogic Corporation.

RESTful Client Side Technologies  Any language or OS  Must support HTTP and XML processing – Dialogic® PowerMedia™ Web Media Server (WMS) uses HTTP with XML. All rights reserved. based on application needs and developer skill set SLIDE 25 © Copyright 2010 Dialogic Corporation. . not JSON  Sample development platforms: – Java  Dialogic demos are Java-based – PHP – .NET – Perl – Ruby – etc.  Flexibility to select appropriate client-side platform.

A/V conferencing. All rights reserved. HTTP SLIDE 26 © Copyright 2010 Dialogic Corporation. . text overlay IP only • SIP call handling in App Server • SIP inbound / outbound call agent in PowerMedia WMS controlled via HTTP Web GUI Software only – standalone server Management Deployment Model Media access Local.Web Accessible Media Processing Feature Dialogic® PowerMedia™ Web Media Server (WMS) Media Processing Connectivity Call Control Audio / Video play/record. NFS. From RTSP Server.

based on phone numbers in HTTP request – Participants in the HTTP post request are placed into same conference SLIDE 27 © Copyright 2010 Dialogic Corporation. All rights reserved. .Use Case: Click2Conference  Social Media Site Click2Conference  Usage Model: – Click2Conference application uses HTTP Post with list of phone numbers – Dialogic® PowerMedia™ Web Media Server handles incoming HTTP post requests to make outbound calls  Call Flow: – PowerMedia WMS makes outbound SIP calls.

Please refer to ‘USE CASE(S)’ portion of the Legal Notice on the last slide. All rights reserved. .Use Case*: Click2Conference Social Media Site Servers Web Server (Social Media Application ) http http 1 http 2 http Voice or Video Calls SIP 3 Voice Calls Dialogic® Vision™ 1000 Video Gateway * . RTP Dialogic® PowerMedia™ Web Media Server (WMS) SLIDE 28 © Copyright 2010 Dialogic Corporation.

All rights reserved. .com/  User’s Social Media contacts are retrieved (with permission) into a list  User selects the friends to be called SLIDE 29 © Copyright 2010 Dialogic Corporation.socialmediasite.Click2Conference  User clicks on Social Media site link – Example: http://apps.

Click2Conference (cont’d)  Social Media Site does not provide phone numbers through their API. So…  User is asked for phone numbers of selected contacts – Phone numbers are stored in a database – Subsequent requests use stored database phone numbers  User presses continue button to create conference SLIDE 30 © Copyright 2010 Dialogic Corporation. All rights reserved. .

the WMS places the SIP calls’ RTP streams into a conference SLIDE 31 © Copyright 2010 Dialogic Corporation. All rights reserved. slide) results in an http POST. .Click2Conference (cont’d)  The “Continue” button (prev. with phone numbers submitted to the Dialogic® PowerMedia™ Web Media Server (WMS)  PowerMedia WMS initiates outbound SIP calls  Under the direction of the application.

. All rights reserved.Use Case: Click2Call  Mapping Software Click2Call – Customer provides mapping software for many uses • Telecommunications: location of new service availability • Government/Military: location of nearest recruiting office • Commercial: store location – Basic Click2Call application works for any use • Easy to deploy • Increases customer satisfaction and retention   Usage Model: – Click2Call application uses HTTP Post with phone numbers stored in database and supplied by subscriber – Dialogic® PowerMedia™ Web Media Server handles incoming HTTP post requests to make outbound calls Call Flow: – PowerMedia WMS makes outbound SIP calls. based on phone numbers in HTTP request – Participants in the HTTP post request are placed into same conference SLIDE 32 © Copyright 2010 Dialogic Corporation.

. Customer Application) http 1 http 2 http Voice or Video Call SIP 3 Voice Call Dialogic® Vision™ 1000 Video Gateway RTP Dialogic® PowerMedia™ Web Media Server (WMS) * . SLIDE 33 © Copyright 2010 Dialogic Corporation.Please refer to ‘USE CASE(S)’ portion of the Legal Notice on the last slide.Use Case*: Click2Call Web Server (Mapping Software. All rights reserved.

Click2Call  User navigates through the customer maps  Drills down to the desired location SLIDE 34 © Copyright 2010 Dialogic Corporation. . All rights reserved.

Click2Call (cont’d)  User enters phone number to be called  Clicks on “Submit” to initiate call  The company/agency contact information is retrieved and put into a list along with user’s phone number SLIDE 35 © Copyright 2010 Dialogic Corporation. All rights reserved. .

All rights reserved. with phone numbers submitted to the Dialogic® PowerMedia™ Web Media Server (WMS)  The PowerMedia WMS initiates outbound SIP calls  Under the direction of the application. WMS bridges the SIP calls’ RTP streams  User and company / agency contact are connected – Possible for company / agency contact to add a subject matter expert for additional information or immediate inquiry resolution SLIDE 36 © Copyright 2010 Dialogic Corporation.Click2Call (cont’d)  The “Submit” button (prev. slide) results in an http POST. .

All rights reserved.Dialogic® PowerMedia™ Media Processing Product Family SLIDE 37 © Copyright 2010 Dialogic Corporation. .

Dialogic’s New Developer Network SLIDE 38 © Copyright 2010 Dialogic Corporation. All rights reserved. .

Dialogic® inCloud9™ Network Resources  Individual VPN credentials only allow access to: – User’s System – Shared Dialogic® PowerMedia™ IP Media Server (IPMS) – Shared Dialogic® PowerMedia™ Web Media Server (WMS)  Tools on User’s System – Sailfin (J2EE App Server) and demo applications – GUI tools to rapidly create VoiceXML applications • OpenMethods’ OpenVXML • Vicorp’s xMP – Web-Server: Apache Tomcat  Ready to run demos  IPMS and VMs can not access the Internet for security reasons SLIDE 39 © Copyright 2010 Dialogic Corporation. All rights reserved. .

Dialogic® inCloud9™ Network Signup Process  To register.htm  After approval.dialogic. welcome email with VPN instructions forwarded to Developer – Dialogic Tech Support Services for inquiries  Developer uses the VPN to access the Virtual Machine  Developer should review before starting: – inCloud9 readme – Individual demo readmes SLIDE 40 © Copyright 2010 Dialogic Corporation. go to: – https://www. .com/products/ip_enabled/download/ddn . All rights reserved.

Summary  RESTful API based media processing is the most appropriate for Web application developers – Familiar to developers – Can use existing development platforms to develop apps – Reduces programming complexity  Dialogic® inCloud9™ network gives developers rapid access to free resources for Web application development! – No on-site test lab required – No downloads or hardware required  Dialogic® PowerMedia™ media processing product family sets new industry benchmark for range of software-based development APIs and protocols  This market is growing very fast based on industry analyst forecasts SLIDE 41 © Copyright 2010 Dialogic Corporation. All rights reserved. .

Audience Q & A .

SIPcontrol. SwitchKit. scenarios or environments in which Dialogic products can be used. SnowShore. Eicon. 07/10 SLIDE 43 © Copyright 2010 Dialogic Corporation.com . This document discusses one or more open source products. TruFax. your business. Exnet. EXS. All rights reserved. Vision. NaturalConference. Fusion. Making Innovation Thrive. Dialogic encourages all users of its products to procure all necessary intellectual property licenses required to implement their concepts or applications. NaturalFax and Shiva. product descriptions. nor is Dialogic responsible for any present or future effects such usage might have. www. PacketMedia. Brooktrout. Eiconcard. Dialogic Pro. N20. and plans at any time. without notice. Cantata. among others as well as related logos. inCloud9. Eicon Networks. Diva. Such use case(s) are non-limiting and do not represent recommendations of Dialogic as to whether or how to use Dialogic products.dialogic. Video is the New Voice. Dialogic may make changes to specifications. which licenses may vary from country to country. systems and/or releases. Diva ISDN. NMS (stylized). NMS Communications.Dialogic. Dialogic is not responsible for your decision to use open source in connection with Dialogic products (including without limitation those referred to herein). or your intellectual property rights USE CASE(S) Any use case(s) shown and/or described herein represent one or more examples of the various ways. Connecting to Growth. The names of actual companies and products mentioned herein are the trademarks of their respective owners. NaturalCallControl. including without limitation effects on your products. PowerMedia. NaturalAccess. are either registered trademarks or trademarks of Dialogic Corporation or its subsidiaries (“Dialogic”).

Sign up to vote on this title
UsefulNot useful