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”.
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
VoxImplant is a perfect choice if you need to build real-time web-based video chat application in minutes. VoxImplant Web SDK supports WebRTC and lets developers integrate this functionality with any other web application. Peer-to-peer data transfer capabilities available in WebRTC-enabled browsers (Chrome/Firefox/Opera/other) helps with the quality of communication (law latency) and scalability. All infrastructure required for WebRTC p2p communication is offered by VoxImplant, including signaling built-in the SDK, STUN/TURN/ICE support, etc. Let's see what steps are required to get simple video chat application up and running.