Although the latest versions of Safari support WebRTC, users still may experience some issues with video calls. By default, Safari uses only the H264 codec while other browsers use both H264 and VP8 popular codecs. To fix the issue, you can explicitly specify a video codec list conventionally called “scheme”.
How often did you consider masking your private phone number? At first, this question may seem odd but imagine the situation when you order a taxi and, after the trip, the driver starts calling you. That’s not what you normally expect from a taxi service, right? The same is true for the driver: it wouldn’t be great if previous customers would call and distract the driver on the ride or (even worse) on vacation.
First, having a delicate distance between yourself and service workers is much better than having no distance at all. Second, it is important that both parties have the fastest way to contact each other. The Voximplant cloud can easily address these requirements with a phone number masking approach. This article will guide you through all the necessary steps to implement this feature for a simplified case of a single driver and a few customers. Note that this solution is scalable for any number of drivers and customers.
The latest version of our Web SDK is fully compatible with the new Safari 11 audio/video calls support. Please note that Safari imposes a number of restrictions for voice/video usage:
- Web page should load with HTTPS
- If voice or video call is initiated from iframe, this iframe and all iframes in-between should be loaded from the same domain as a website that loads them
- Video will not autoplay on iOS Safari browser without the explicit user command.
- Only H.264 video codec is supported, so set H264first flag to “true” while initializing the Web SDK.
User interface should be created in order for video to play during a call. It should be interactive element like an HTML “button” with “onclick” handler that calls “play” method on the “video” HTML element.
A brand-new messaging API was added across Web, Android and iOS SDK. Single Voximplant user id can be used to log in from multiple SDK instances, with API to send online and offline messages across one-on-one or multi-user conversations. Both our client and server-side are highly optimized for minimal resource usage and push notifications support.
- One Voximplant user id can be used to login on multiple devices, with unread message count sync across all devices
- Universal “conversations” that can be used to create one-on-one messaging, channels, public and private chats
- Messages are saved if user is offline and delivered when they are back online
- Push notifications support
- “Moderators” support
- “Typing” notification support
- Channels, users and messages can be edited
- Notifications for all event across all affected users
- Conversations and messages can be saved to and loaded from app storage
- Optimized for low cpu, memory and network usage
- Other messengers integration via HTTP API and callbacks
Getting started with Web SDK
Use the new Messenger singleton via getMessenger and createConversation/joinConversation API to access the Conversation object with a sendMessage method. Subscribe for different events to get notified when a conversation is created, new message arrives, new user joins a conversation etc.
Getting started with Android SDK
Use the new IMessenger singleton via getMessenger and createConversaton/joinConversation API to access the IConversation object with a sendMessage method. Subscribe for different events to get notified when a conversation is created, new message arrives, new user joins a conversation etc.
Getting started with iOS SDK
Use the new messenger singleton property via VIClient and createConversaton/joinConversation API to access the VIConversation object with a sendMessage method. Subscribe for different events to get notified when a conversation is created, new message arrives, new user joins a conversation etc.
Following Google’s release of new Speech API, we are happy to announce improved quality of call records transcription. No changes are required, your old code like will be producing more accurate results. In addition to that, you can now specify output format to get transcription in form of JSON file with timestamps for further processing. We are working on some examples that will be available in HowTo’s in the nearest future.
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!
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.
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.
- Jan 10, 2018 01:19
- Making Video Calls in Safari
- Dec 14, 2017 12:45
- Phone Number Masking
- Oct 16, 2017 12:59
- 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
- January 2018
- December 2017
- October 2017
- September 2017
- August 2017
- 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