Current WebRTC implementations use Opus (audio) and VP8 (video) codecs:
As a result, a single-party HD call can require up to 2.5+ Mbps of network bandwidth. Add a few more peers, and the quality must drop to account for the extra bandwidth and CPU, GPU, and memory processing requirements.
Kandy uses the following ports:
STUN: 3478 (UDP, TCP)
RTP: 30000 - 65535 (UDP)
This is a unique identifier for your project. We use the domain of the email you've signed up with so that you can use your business's domain if you have one. It's okay if you don't own the domain of your email since it's just an identifier.
This key is used to authenticate your application to access Kandy API services. After you log into http://developer.kandy.io, the first screen displayed will list the “API KEY” for each project that you have previously created.
The user needs to be deleted and then added again in order to 'reset' the password.
Currently (04/18/2017) multiple video conferencing is not supported. However, it has been scheduled for a future release.
The 64 bit browser plugin should only be used with a 64 bit browser. Having a 64 bit system does not mean that you should use this version.
If you have saved your user's User Access Token, you can use kandy.loginSSO() with the UAT. You can do this as your page loads. You can get the UAT from the success callback of kandy.login().
Current Kandy PhoneGap API for iOS is compatible with Kandy Mobile SDK 1.6 (both iOS and Android). For more information and tutorials, click the following link to get started: https://github.com/Kandy-IO/kandy-phonegap/
The co-browsing feature is available only on the Kandy JS SDK. The Kandy Mobile SDKs do not have the co-browsing feature as of 10/29/15.