Voximplant. Blog

Monthly Archives: December 2016

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:

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

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