Voximplant. Blog

Category Archives: HowTo’s

Screen Sharing in VoxImplant

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.

screen_sharing_article

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!

Tagged in ,

Authorization using tokens instead of passwords

Storing and saving passwords inside applications is not safe. For better security our SDK provides two additional login methods: with the one-time login keys and with the renewable tokens. Keys omits the need to store passwords entirely by using your own backend that will generate a one-time login key each time your application needs to login the Voximplant cloud. Although very secure, the keys require your own backend to be created, while the “tokens” can be used entirely on the SDK side with some security and usability trade-offs that are explained in this article.

Tagged in

Push Notifications for Android

VoxImplant push notifications for Android are based on FirebaseCloud Messaging (FCM) platform and implemented as the “data messages”. Using notifications, a device can be awakened and an app started before a call arrives. Our SDK requires Android API 16 (4.1), while push notifications support also requires Play Services 10.0.1 or higher to be available on the device. Our Android SDK contains a sample application with all the code needed to handle push notification. Following tutorial explains that code and describes additional steps that should be performed to have a working Push Notifications solution for your mobile applications.

Push notifications are available since Android SDK version 2.1.0

Push Notifications for iOS

VoxImplant push notifications for iOS are based on the Apple VoIP Push Notifications. Using notifications, a device can be awakened up and an app started before a call arrives. Our iOS SDK contains a sample application with all the code needed to handle push notification. Following tutorial explains that code and describes additional steps that should be performed to have a working Push Notifications solution for your mobile applications.

Push notifications are available since iOS SDK version 1.1.0

Speech-to-text: ASR

Unlike transcription that is performed after call ends, ASR (automatic speech recognition) works during a call and allows either to recognize a word among given variants or do a “freeform” recognition of an arbitrary speech.

Speech-to-text: transcription

Transcription works just like Audio Recording with only difference that a text file is created alongside an audio file.

Audio Recording

Voximplant cloud scenario allows to record audio, video and transcribe voice-to-text for each individual call object. Recorded audio, video or text is stored at Voximplant cloud for 3 months, after that it’s automatically deleted. Recordings can be downloaded if longer storage is required.

Step-by-step call center tutorial part 8

Call lists, PDS and SIP

There are two ways how Voximplant can handle an outgoing call. First, the outgoing call can be initiated from JavaScript session created from the incoming call. That approach is used if you want to connect two or more people, forward call into a call center or implement any other “connect two persons” logic where and outgoing call is initiated as a response to the incoming call. Second, you can initiate outgoing call via the HTTP API. That approach is used if you want to initiate a call from your service or call multiple users. You can implement any call logic via HTTP API, but you also need to setup your own backend that will initiate calls, maintain the suitable number of simultaneous calls etc. For fast “out-of-the-box” experience we have a built-in “Call list” functionality that allows calling thousands of users with a few commands and without any backend of your own.

Tagged in

Step-by-step call center tutorial part 7

Operator status and temporary ban

While Voximplant ACD framework provides only essential call center backbone, it also has some out-of-the-box features for most popular use cases. One of such features is “Operator Status” that can be set to “Ready” if operator is available to handle a call, or any one of non-“Ready” if calls should not be forwarded to that operator.

Tagged in

Step-by-step call center tutorial part 6

IVR and operator skills

In a simple scenario all incoming user calls are evenly distributed among all available operators. But as a number of users grows, it became more convenient to direct specific requests to specific operators who can handle them better. This raises a number of questions: how to figure out user question and how to define which operator can answer that questions.

Tagged in
Older posts

Categories

Recent Posts

Oct 16, 2017 12:59
ES7/2017 JavaScript syntax support
Sep 21, 2017 12:03
Safari 11 support
Aug 17, 2017 11:59
Messaging update
Aug 14, 2017 03:22
Hot Summer Speech-to-Text Updates
Aug 02, 2017 12:47
Screen Sharing in VoxImplant
May 02, 2017 12:08
H.264 video call recording is now available (in mp4 format)
Apr 17, 2017 10:58
Voximplant mobile SDK for Unity in now available
Feb 13, 2017 10:22
Authorization using tokens instead of passwords
Feb 03, 2017 01:45
Push Notifications for Android
Feb 03, 2017 01:45
Push Notifications for iOS

Archive

Tags