One-to-One Video Chat
This page describes the one-to-one video chat implementation.
One-to-one video chat
The video conferencing capabilities are implemented using WebRTC and rely on an Internet-hosted control service run by AddLive.
This page
Video chat is handled by AddLive, an internet-hosted service. Audio and video do not go through HipChat Server. HipChat Server only sets up the connections between the two HipChat clients' users.
You can disable video chat. Log into HipChat Server and go to Server admin > Video.
Only the HipChat client applications communicate to AddLive to set up the video (or audio) chat. The AV data stream runs peer-to-peer between the clients, when possible.
Media data is sent by the following paths and protocols in order of preference:
- Peer-to-peer mode (UDP ports 540 for audio, 541 for video, and 3478 for audio and video streaming for Chrome WebRTC)
- Relayed to the AddLive server (UDP ports 540 for audio, 541 for video)
- Fallback through the AddLive server (TLS over TCP, port 443)
The domains listed below must be able to connect over ports 80 and 443:
- addlive.com (and all its subdomains)
- d36pfzlm4aixmv.cloudfront.net
Security
No user-provided credentials are transmitted. The full name of the user is transmitted.
All signaling communications are encrypted using cipher suites restricted to AES 128 or 256 bit encryption.
Video and audio data streams are protected using the SRTP protocol. AES CPC 128 bit encryption is used for RTP packet encryption. HMAC SHA1 is used for packet authentication and verification. Encryption keys are generated by the streaming server by session.
Client requirements
Video chat works best when clients have 200ms or less network latency between them.
The Linux client app requires support for OpenGL 2.0 or OpenGL ES 2.0.