We are happy to announce that video calls that use H.264 video codec can now be recorded. Recorded video calls that use H.264 will be stored as mp4 files (calls with video in VP8 format are stored as webm files). There are few ways to enable H.264 in your video calls:
– Use H264first Config param (Web SDK)
– Use H264first flag in CallSettings (Web SDK)
– Mobile SDKs are being updated to let developers enable H264 in video calls
According to the following research from Chris Koehncke using H.264 instead of VP8 can save up to 50% in terms of power consumption https://www.chriskranky.com/webrtc-impacts-on-battery-life/ , in addition to that mp4/avc is widely used and supported by most players in both online and offline worlds.
See the example of video recording below (Firefox->Voximplant, no post-processing)
P.S. Feel free to ping us if you have any problems with video call recording
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.
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
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/
P.S. Android Push support is on its way to production, expect it right after the New Year in January 2017!
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
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.
Hi everyone! We’ve been busy working on new cool features for you, many developers asked us about high quality speech recognition for both audio call records transcription and real-time recognition scenarios. We are happy to announce that this functionality is now available for all our developers.
- Support for audio calls in Microsoft Edge. With Microsoft recently updating the browser’s web and audio support, Voximplant is one of the first companies to make its platform compatible with Edge. With Web SDK 4.0, web apps are empowered to handle incoming and outgoing voice calls from within the Edge web browser. Video calls in Edge will be functional as soon as VP9 or h.264 codec support is added to the browser.
- Video can be enabled during an existing audio call. Now developers can create web apps that offer a Skype-like “enable video” option during active audio calls. Video can be enabled or disabled at any time during the call.
- Both local and remote audio and video streams can be modified by applying filters. Developers can now modify video and audio streams in realtime. Possible applications of this feature include using video and audio filters to add watermarks, hide or alter faces, mask voices, etc.
- h.264 video codec can be set as “high priority”. The “h.264” video codec is known for its valuable speed in modern hardware, especially in mobile devices. Developers can now force this codec to provide better video quality with less CPU usage.
Additional enhancements include:
- Reduced latency of audio and video calls.
- Improved syncing between audio and video tracks.
- Calls within the Chrome browser now maintain better performance – even with poor network conditions.
- Audio and video codec priorities can be manually configured.
- Full support for WebRTC to offer users the best in voice and video quality.
New SDK also supports asynchronous initialization and drops support for Flash, which can still be used with legacy systems via 3.x versions of the SDK. Complete documentation for Voximplant’s Web SDK 4.0 beta can be found at https://voximplant.com/docs/references/websdk4/
Many voximplant developers use our online VoxEngine scenarios editor. It simplifies the development process since it has autocomplete and other useful functions, but there was a problem some our developers reported about – it’s hard to check the changes in the scenario before you save it, so the wrong version of the scenario can be saved accidentally. We have embedded the Diff utility that shows the difference between a scenario version which is now stored in the voximplant’s cloud and the one with the recent changes that will be saved. Developers can find the Diff button and Enforce Diff checkbox near the Save button now.
If the Enforce Diff checkbox is active then Diff util will be launched before scenario can be saved.
Now developers can use Promise in their VoxEngine scenarios and we also added Net.httpRequestAsync and Net.sendMailAsync functions that return Promise object in addition to standard ones that used callbacks. We will be working on additional ES6/ES7 functionality in the future to help VoxImplant developers build apps and services even faster.
This post is short and simple: your mp3 or ogg files played on VoxEngine scenario level with call.startPlayback or using Player will be played on the Web or Mobile SDK side in HD quality (48KHz), or on SIP side if it does support wideband audio codecs (Speex or Opus). It also appeared that Opus has 3 encoding presets – auto / speech / music, currently we use auto, but maybe we will let developers decide which preset can be used on VoxEngine scenario level later.
- 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
- 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
- May 2017
- April 2017
- February 2017
- January 2017
- December 2016
- November 2016
- October 2016
- September 2016
- July 2016
- June 2016
- April 2016
- March 2016
- February 2016
- January 2016
- December 2015
- September 2015
- August 2015
- July 2015
- May 2015
- March 2015
- February 2015
- January 2015
- December 2014
- November 2014
- October 2014
- September 2014
- July 2014
- June 2014
- May 2014
- April 2014
- January 2014
- December 2013
- November 2013
- October 2013
- September 2013
- August 2013