Back in 2014, we released a WebRTC industry first – an Archiving API built on top of the OpenTok Platform. The ease of use of the Archiving API which enables the recording of any OpenTok session has become one of the key drivers for our customers to choose TokBox. We’ve seen demand from customers across a range of different industries with a range of use cases but the ability to record OpenTok sessions, in a format that is optimized for playback (Composed Archiving) or one that gives customers complete control over post-processing (Individual Archiving), is a common ask across the board.
It’s hard to believe that in this day and age of digital transformation you still have to announce yourself when you ring a contact center. Or even worse, why you have to repeat your account details from one agent to the next. It’s among the most frustrating of customer service experiences, not to mention inefficient and costly for operators.
When evaluating a new product or service, we know how important it is to be able to test out the technology first. Stakeholders in different areas of the business, both developers and non developers, need to see and understand how the technology works.
We’ve noticed that for customers evaluating the OpenTok platform, without using the API, it can be challenging to visualise your use case. Even when a developer works through our Quick Start Guide, there can be a need for additional implementation to build a custom proof of concept. All of this translates into time invested during the business’ evaluation phase of the product; worse yet, it can lead to an incomplete or inaccurate evaluation.
Since we launched the new version of our platform back in 2012, one of our goals has always been to make it very easy to manage and understand how your applications are performing. In addition to simplifying how to build applications, we believe that those are the key elements for a great experience.
Over the last year we have been working on a completely new way to interact with your TokBox account. As our user-base grew and diversified, it was obvious that our previous dashboard was not enough and needed to be extended. With the number of new tools and services that are in the works, we realized that it was a good opportunity to future proof our stack and give you, our users, a much better experience.
We’re excited to announce the release of the OpenTok One-to-One Sample Application across web, iOS and Android. This open-source application enables you to speed up your development efforts to set up interoperable, production-quality audio/video communication between users.
As you get started with this OpenTok sample, you will learn the best practices used to develop and manage the audio, video, and camera elements on mobile devices or in the browser. We recommend this is as your first step in delivering Real Time Communications (WebRTC) solutions on the OpenTok platform.
Have you ever had to support a WebRTC application and needed to get packet dumps from the user? Wireshark is a great tool for this, but asking a user to install it and make a dump rarely works. It’s just too complicated. So I was pretty excited when I read the Chrome 49 release notes which described (not in much detail) a new feature called the ‘RTC event log’. This is described as follows:
We now provide a new debug option in chrome://webrtc-internals for tracing internal details (e.g., BWE, jitter buffer state) for audio and video sessions. This option creates a log containing the timing and headers of packets as well as the timing of various internal events. We hope this will help resolve issues related to media transport and jitter buffers; attaching this log when reporting such issues will help us tremendously.
We’re happy to announce that we recently made available OpenTok mobile SDKs 2.7.0 for iOS and Android. Improvements have been made in three main areas: Xcode 7 and iOS 9 support, quality and reliability and ease of use of the library.
Now let’s jump into all the details:
Xcode 7 and iOS 9 support
A beta bitcode version of the OpenTok iOS SDK is now available here. For more information about this update you can check out our blog post. If you have any comments or need to report any issues, please contact us at: firstname.lastname@example.org.
Over the last 5 years, we’ve helped hundreds of companies create rich and engaging applications with OpenTok powered live video and voice. Now, we’re bringing broadcasters and brands (who are now broadcasters too) unprecedented audience engagement with the launch of our new Interactive Broadcast Solution.
Until now live broadcasting applications have focused on one-way streaming. This works well for conferences or events. But now, Interactive Broadcast is the first solution to enable multi-party panels, video-based audience participation, and an on-brand experience for website and application owners. The Interactive Broadcast Solution gives broadcasters the tools they need to bring user-generated content and viewer-participation content to both online and TV audiences.
Embedded communications is so powerful because of one very important factor – context. Whether that’s a web page, presentation, LMS, medical scan, (the list goes on), context enhances the conversation. Better still? When collaboration features are layered on top.
Using the OpenTok platform, our aim is to make it super simple for you to add rich collaboration functionality to your apps. Today we’re happy to introduce the Annotation widget for the OpenTok platform in beta – a pre-built UI component that can be quickly added to your application. The widget adds annotation and frame grab capabilities to the OpenTok web, iOS and Android SDKs and is completely customizable.
Apple added Bitcode binary support for developer apps as part of the app thinning process. The reason behind this is to minimize the end user download app size. Prior to Xcode 7 & iOS 9, developers upload the native binary and it’s the final executable that users download.