IP Telephony & Contact Center Architects

born to learn & share ...

Untapped market: WebRTC for contact center agent desktop applications, from voice to video to co-browsing to simplicity.

The agent desktop application is the main tool of a contact center agent, this is where she or he manages availability, controls telephony and interacts with whatever application manages the end customer interaction. It can be a fat client installed… Continue Reading →

Real-time communication with WebRTC: Google I/O 2013

Real-time communication with WebRTC: Google I/O 2013

WebRTCGeneral Overview

WebRTC offers web application developers the ability to write rich, realtime multimedia applications (think video chat) on the web, without requiring plugins, downloads or installs. It’s purpose is to help build a strong RTC platform that works across multiple web… Continue Reading →

webRTC API differences

Firefox and Chrome both prefix their interfaces and are likely to continue to do so until the standard is more finalized. The following table shows the relevant names: W3C Standard           Chrome                   Firefox getUserMedia           webkitGetUserMedia       mozGetUserMedia RTCPeerConnection      webkitRTCPeerConnection  mozRTCPeerConnection RTCSessionDescription  RTCSessionDescription   … Continue Reading →

A few things about WebRTC

WebRTC is a realtime communication engine; primarily works in the context of the browser. Though, there are native APIs as well. It is not just a collection of API; it an innovative framework capable to define new protocols; suggest new… Continue Reading →

What is WebRTC?

WebRTC is an open framework for the web that enables Real Time Communications in the browser. It includes the fundamental building blocks for high quality communications on the web such as network, audio and video components used in voice and… Continue Reading →

Are you a newcomer and want to learn WebRTC?

First of all; understand following factors involves in each WebRTC application:     Signalling servers (mandatory)     ICE servers (mandatory)     Media servers (optional)     JavaScript API (or NATIVE API) (mandatory) Signalling Servers E.g. Socket.io, WebSockets, XMPP, SIP or simplest one… Continue Reading →

© 2018 IP Telephony & Contact Center Architects — Powered by WordPress

Theme by Anders Noren — Up ↑