Voximplant. Blog

Voximplant mobile SDK for Unity in now available

Voximplant Unity SDK
We are happy to announce our new mobile SDK for Unity platform. Now Unity developers can use the SDK to embed real-time voice and video communication into VR/AR apps and games in minutes, we will take care of complexity and infrastructure. The SDK is compatible with Google Daydream. Please visit https://unity.voximplant.com/ to learn more.

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 Android 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.

VoIP Push Notifications support for iOS SDK has arrived

Dear Voximplant developers, we are happy to announce that Voximplant now supports VoIP Push Notifications for calls to iOS SDK. We tried to make everything as simple for developer as possible; the following steps are required to enable VoIP Push Notifications for your app:

1. Upload your Apple VoIP Push certificate at https://manage.voximplant.com/#certificates and specify (bind) Voximplant application(s) where you will be using VoIP Push functionality

2. Add

require(Modules.PushService);

in the beginning of your VoxEngine scenario

3. Now VoxEngine’s callUser and callUserDirect functions will start using VoIP Pushes to notify the SDK about incoming calls. (same applies to helper functions: forwardCallToUser and forwardCallToUserDirect)

4. Get new version of iOS SDK at http://voximplant.com/docs/references/mobilesdk/ios/

That’s it!

P.S. Android Push support is on its way to production, expect it right after the New Year in January 2017!

New billing for video calls running via servers

We are happy to announce that currently video calls that go via Voximplant servers (not P2P ones) are billed per megabyte of video traffic. Since the resolution of a video stream can be different (so as fps, video codec and other params) it means that per minute billing was a bad idea for this case – 1 minute of video call generates different load on our infrastructure depending on various parameters. So now the formula for video call going via Voximplant servers looks as follows:

SDK-platform / platform-SDK call – $0.002 per minute per call leg
+ $0.001 per megabyte of video traffic sent to the platform

See http://voximplant.com/pricing/ for the details

Tagged in , ,

Blind transfer support for SIP phones

A lot of traditional telephony services rely on this function. It lets callee transfer a call to another person by pressing special transfer button and entering another person’s number (usually extension number). It’s called blind transfer because the person who transfers the call won’t talk with the person to whom he transfers it.

Blind transfer
The following scheme describes the process in Voximplant terms:

Categories

Recent Posts

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
Jan 19, 2017 08:38
Speech-to-text: ASR
Jan 19, 2017 08:38
Speech-to-text: transcription
Jan 19, 2017 08:37
Audio Recording
Dec 28, 2016 12:47
VoIP Push Notifications support for iOS SDK has arrived
Dec 14, 2016 02:00
New billing for video calls running via servers
Dec 07, 2016 02:29
Blind transfer support for SIP phones

Archive

Tags