If you are seeking information on troubleshooting your audio & video connection, we recommend first checking out Troubleshooting Audio & Video for BrazenLive Video Broadcast and 1-on-1 Video Chats and then review the technical requirements below.

What Is BrazenLive & 1-on-1 Video Chat?

BrazenLive lives right within the Brazen virtual event platform and provides live video broadcast + screen sharing capabilities in the event. 1-on-1 Video Chat gives representatives the option to transition from a text-based conversation to a private video chat with an event attendee.

BrazenLive and 1-on-1 Video use Vonage technology, which is built using WebRTC. All multimedia traffic is routed through Vonage media servers; peer-to-peer connections are never used.

 

What Are the Technical Requirements?

Interactive Broadcasts & 1-on-1 Video Chats

Broadcast Hosts and Presenters participate in an Interactive Broadcast. They will see incoming video in real time and have the ability to share their video, audio, and screen. Interactive Broadcasts are delivered using WebRTC. These are the same requirements for users engaging in 1-on-1 video chats.

Hardware

BrazenLive and 1-on-1 video chats require access to each user's camera and microphone. Users are prompted for this access when using BrazenLive or entering a 1-on-1 chat.

Supported Browsers

All modern browsers which support WebRTC, including the latest versions of:

• Chrome (desktop and mobile)
  • Version 83 and higher for Windows
• Safari (desktop and mobile; screen sharing feature is limited)
• Firefox
• MS Edge
  • NOTE: Older, non-Chromium versions of Microsoft Edge (versions less than 79) do not support screen sharing capabilities

Bandwidth

A minimum of 350Kbps available bandwidth per stream is recommended. A stream is any incoming or outgoing video source.

Example: an Interactive Broadcast with a Host, a Presenter, and the Presenter's shared screen is three streams, so each Host and Presenter should have at least 3×350Kbps available bandwidth.

Required Domains

Users' browsers must be able to reach the following domains directly, in addition to the standard Brazen Connect domains:

• *.tokbox.com

• *.opentok.com

Ports

BrazenLive and 1-on-1 Video automatically negotiate the best possible route for multimedia traffic. Clients must be able to send

and receive TCP traffic on port 443. We also highly recommend allowing traffic on UDP port 3478, as UDP's speed-over-reliability approach is much better suited to streaming multimedia.

WebSockets

WebSockets are recommended, but not required, for BrazenLive and 1-on-1 Video. Certain metadata, such as other users' connectivity status, is relayed over a WebSocket connection and is lost when this connection type is blocked.

Proxies

BrazenLive and 1-on-1 Video work as normal through transparent proxies. Proxies which inspect and or alter traffic may interfere with BrazenLive and 1-on-1 Video. Please ask your account manager for more details.

 

Live Streaming

Broadcast viewers see BrazenLive as a Live Stream. This is a single consolidated video showing all Hosts and Presenters, along with any shared screens. Live Streams are delayed by roughly 15 seconds. Live Stream viewers are not given the option to broadcast video or audio. Because Live Streams are delivered over HTTP Live Streaming, they have much less stringent technical requirements.

Hardware

No hardware requirements

Supported Browsers

All modern browsers, including the latest versions of:

• Chrome (desktop and mobile)
  • Version 83 and higher for Windows
• Safari (desktop and mobile; screen sharing feature is limited)
• Firefox
• MS Edge
  • NOTE: Older, non-Chromium versions of Microsoft Edge (versions less than 79) do not support screen sharing capabilities

Bandwidth

Live Stream viewers always receive exactly one incoming stream and never have outgoing streams of their own. A minimum of 350Kbps available bandwidth is recommended.

Required Domains

Users' browsers must be able to reach the following domains directly, in addition to the standard Brazen Connect domains:

• *.tokbox.com

• *.opentok.com

Ports

No port requirements

WebSockets

Live streaming does not require WebSockets.

Proxies

HTTP Live Streaming is treated as normal HTTP traffic and should not be affected by proxies.

 

IP Whitelist

All Vonage video communication will occur on the following set of IP ranges: