|Oracle® Communications WebRTC Session Controller Web Application Developer's Guide
|PDF · Mobi · ePub|
Web applications developed for WebRTC-enabled browsers can establish real-time communication with each other and with legacy network services. To access such applications, a subscriber needs to be connected to the Internet and use a device (such as a mobile phone, a laptop, a tablet or a desktop computer) equipped with a WebRTC-enabled browser.
Such applications enable end users to perform a multitude of tasks. Suppose that you create an application for the web pages of a real-estate company. When an interested party, such as a buyer's agent, accesses the company's web page, your application starts to respond to the agent's actions while the agent is on that web page. The content of the session managed by your application could include:
A call session when the buyer's agent uses the calling feature in your application to contact and communicate with the seller's agent
An online video chat between the two agents, where your application manages the audio and video synchronization
Sending and/or receiving text or data files, such as a data sheet about the property with a photo of the house
Sending and/or receiving video data, such as an online tour of the house
Signing of some initial terms using electronic signatures
WebRTC Session Controller supports the following building blocks required for your web application development:
WebRTC Session Controller Signaling Engine. See "About WebRTC Session Controller Signaling Engine".
WebRTC Session Controller. See "About the WebRTC Session Controller and Your Applications".
WebRTC-enabled browsers. See "About the Supported WebRTC-Enabled Browsers".
WebRTC Session Controller Signaling Engine manages the connectivity between the browser and the end network services. Sitting between the browser and the telecommunication network, it does the following:
Acts as an intermediary between the web browser and the telecommunication network services, thereby making the browser a client of the network services.
Provides security to the interactions between your applications and the telecommunication network services.
For more information on Signaling Engine, see WebRTC Session Controller Concepts.
The WebSocket uniform resource identifier (URI) your application uses to connect to the WebRTC Session Controller identifies your application, its configuration, and extensions to that default configuration (when present). All interactions between the WebRTC Session Controller and your application take place within that default or extended configuration.
For more information on WebRTC Session Controller, see WebRTC Session Controller Extension Developer's Guide.
WebRTC Session Controller works with any WebRTC-enabled browser. Currently, it is certified with the Google Chrome browser and the Mozilla Firefox browser. See WebRTC Session Controller Installation Guide for more information.
WebRTC-enabled browsers are equipped with the WebRTC API. For more information, go to the WebRTC website at
This guide uses the following conventions:
Whenever the term "application" is used, it refers to a WebRTC-enabled web application.
Session, CallConfig, onIncomingCall, and getValue
Italicized words are placeholders. For example:
wscSession, callObj, callConfig, and so on.