Tag: web sdk

There are some cases when you need to login users into web phone automatically, but don't want plain text password (that is accepted by VoxImplant.getInstance().login()) to be available in JavaScript code.

Loading Web SDK from CDN

Before Web SDK can be used it should be loaded and initialized. Since Web SDK is a javascript library it can be loaded using standard HTML code for embedding javascript library into a web page (usually it's added somewhere before closing HEAD tag):

<script type="text/javascript" src="//cdn.voximplant.com/edge/voximplant.min.js"></script>

Screen Sharing allows you to share information on your screen during a call. You can share the entire screen or one of the active windows.

The best way to understand any functionality is to build a simple demo application. Let’s create a demo app that allows username1 to make a video call to username2 and, during the call, users can share their screen with one another. The demo app has three video blocks: the first one is for your own video stream, the second one is for the incoming video stream and the third one is for viewing locally what is being shared.

To simplify the process, we will use our video chat demo as a boilerplate. You can follow the link and copy whatever piece of code you want. So let’s do it!

One of the most popular scenarios for our Web/Mobile SDK is about enabling true click-to-call/tap-to-call function in web and mobile applications. True click-to-call means that it's not about callback version when a call is initiated from the platform to both parties and connects them together, it means that call is initiated from the client side and goes via IP to the platform and then routed to required destination. True click-to-call is cheaper, faster and offers better UX; of course, you need to have the internet connection to use it (shouldn't be an issue these days). This tutorial explains how to easily embed click-to-call into your app using VoxImplant SDKs and setup call routing using VoxEngine scenarios.

We recommend to check our Quickstart before you proceed

Full Featured Instant Messaging

Our first release of instant messaging functionality offered limited number of functions for 1-to-1 communication, we’ve been working on instant messaging upgrade that enables group messaging, messaging history, contact list control and other capabilities for full featured IM system. IM/presence should be explicitly enabled in VoxImplant application settings before it’s available.

We are working on the tutorial explaining how to use new functionality and will update our simple messenger application on GitHub in the near future. Other features for IM we have in the roadmap: search in history, checking presence from VoxEngine scenarios, sending messages from VoxEngine scenarios and via HTTP API.

New Instant Messaging functionality is only available in WebRTC mode

Web SDK improvements

VoxImplant Web SDK now supports Temasys WebRTC plugin for IE/Safari. We are working on ORTC support in Edge, but a lot of companies still use IE/Safari and want to have access to VoxImplant functionality in these browsers.

Video calls support without access to local webcam is now possible, just set videoSupport to true and videoConstraints to false in config during the SDK initialization:

VoxImplant.getInstance().init({
  micRequired: true,
  videoSupport: true, 
  videoConstraints: false
});

Now you can make/receive video calls, but your camera won’t be used, if you want to stream your video you can use Client.setVideoSettings or Call.setVideoSettings depending on the app logic.

A lot of people use video conferencing functionality in Skype, but Skype is standalone application and it's hard to integrate it with your own service. VoxImplant lets developers embed similar functionality into any web or mobile application. This tutorial will explain how to build video conferencing service with dial-in/dial-out functionality (to connect PSTN participants) and browser-based client application using WebRTC capabilities and VoxImplant.

Mozilla recently released Firefox 34 and there were some changes in WebRTC stack that weren't compatible with our Web SDK. We have fixed most of them, p2p video calling will be fixed on Monday.

There are a lot of scenarios when you need to transfer a call to some other user or join it with another call by sending some command from a client built using Web SDK. New transferCall function enabled this functionality. It's rather simple function - just provide two call instances as its parameters and VoxImplant will try to join call1 with call2. If you want to know the result of the transfer you can add the following event listeners to call1 - VoxImplant.CallEvents.TransferComplete and VoxImplant.CallEvents.TransferFailed. If call was transferred successfully both call1 and call2 will be disconnected from Web SDK. In the world of telephony people usually call this function "Attended transfer".