Today we are releasing the OpenTok iOS SDK v2.1.7 that includes:
- This version fixes peer-to-peer publishing and subscribing issues between iOS and Chrome.
- This version fixes memory leaks in OpenGL rendering.
- This version fixes issues when disconnecting from a session.
Learn more about our iOS SDK >
This update will be available to developers starting today.
Have you heard something like these feature requests:
“I take French lessons online. I meet with my tutor twice a week. But every Tuesday we spend some time refreshing what we’ve covered on Thursday. I’d pay extra if I could replay the recording of the previous session on my own time.”
“I have to record each conversation with a customer and store it for legal reasons.”
Until now, once an OpenTok-powered conversation ended, there was no way to go back and see what was said. In a lot of scenarios (including the ones above) you could add a lot of value to your product by recording the conversation and making it available on demand.
Today we’re announcing new Intelligent Quality Controls in the OpenTok platform. To catch everyone up, Intelligent Quality Controls are the features and enhancements we’re developing to make sure that each participant in a video call has the best possible experience.
Update (Nov 25): Developers, check out our new blog post that provides details on using dynamic frame rate controls.
You may recall that over the summer we launched traffic shaping for the audio-only fallback feature. This feature drops video in low bandwidth situations to prevent a participant with poor QOS from dragging down the video quality for everyone else. Essentially, we built the automatic (video) mute button for “that guy on his cell phone in a convertible!”
Connectivity, we at TokBox believe, is one of the cornerstones of real-time communication applications. So we are happy to announce that we now support TURN over TCP.
There are several technologies which are used to help establish connectivity in WebRTC. The first mechanism is using a protocol called STUN. STUN uses a ping-pong mechanism to find the public IP of a client end-point so that a peer-to-peer session can be established and one can traverse a firewall. While this is useful in a number of scenarios, there are cases where one could be behind symmetric NATs, where STUN does not suffice. TURN helps in these cases. TURN is a mechanism by which real-time media can be relayed through a TURN server to punch through firewalls. OpenTok seamlessly supports STUN and TURN so a developer doesn’t have to worry about how to setup up these servers, scale them, establish connectivity etc.
Today we’re excited to announce the launch of our native OpenTok 2.0 Android SDK Beta powered by WebRTC! This is a big milestone for the OpenTok platform, and the result of several months work for our engineering team.
The Android SDK enables OpenTok developers to create rich and interactive native applications with fully featured real-time video communication. It features the ability to make either P2P or multi party calls through our Mantis infrastructure.