Our goal is to provide a service that is browser-based (no need to download or install software), accessible from anywhere and is available 24/7.

Client hardware requirements

Windows Mac Linux
For participants: For participants: For participants:
2.0GHz CPU with dual-core processor minimum (Recommended: Quad-core i5 processor or better) Mac computer with an Intel processor (Recommended: Dual core 2.0GHz or faster) 2.4GHz or faster x86-compatible processor or Intel® Atom™ 1.6GHz or faster processor for netbooks
4GB of RAM minimum (Recommended: 8GB or more) 4GB of RAM minimum (Recommended: 8GB or more) 4GB of RAM minimum (Recommended: 8GB or more)

Client operating system requirements

Windows Mac Linux1 Solaris
Microsoft® Windows 10® Chrome v50 or higher (recommended for best performance), Firefox 49.x or higher Mac OS X v10.8 or higher Chrome v50 or higher (recommended for best performance), Firefox 49.x or higher Red hat® enterprise linux (RHEL) 5 Chrome v50 or higher (recommended for best performance), Firefox 49.x or higher Solaris 10 Chrome v50 or higher (recommended for best performance), Firefox 49.x or higher
Microsoft® Windows 8.x® Chrome v50 or higher (recommended for best performance), Firefox 49.x or higher Novell SUSE® 9.x or higher Chrome v50 or higher (recommended for best performance), Firefox 49.x or higher
Microsoft® Windows 7® SP1Chrome v50 or higher (recommended for best performance), Firefox 49.x or higher Ubuntu 10 or later Firefox 49.x or higher, Chrome v50 or higher (recommended for best performance), Firefox 49.x or higher

Client bandwidth requirements
While Onstream Webinars Live is designed to use bandwidth efficiently, and even though it does try to degrade gracefully, it is still a broadband platform. For best possible and most reliable experience do not use WiFi equipment and use a high-grade, dedicated, low-latency broadband internet access. Use our System Check application to test your connection prior to attending a conference. Please consider packet loss, latency in round trips and jitter value of connections used.

Audio Video Video (HD & Resolution) Ports
Minimum 50 kbps upload/download (100 kbps recommended) Minimum 100kbps upload/download (200 kbps recommended) Minimum 500 kbps upload/download (1 mbps recommended) Minimum 800 kbps upload/download (1.5 mbps recommended)

Mobile requirements

Android iOS
Chrome Safari

Supported Input Devices

Camera & Video

Windows Mac Linux
Any camera or video card compatible with the Windows Driver Model (WDM) Any camera or video card compatible with the QuickTime driver model USB and FireWire supported
USB and FireWire supported USB and FireWire supported
Onstream Webinars Live has been tested and works well with most Logitech Web Cameras. Logitech C920 and later models recommended

Microphone, Headset & Audio

Windows Mac Linux
Any microphone or sound card compatible with the Windows Driver Model (WDM) Any microhphone or sound card compatible with the QuickTime driver model USB and FireWire supported
USB and FireWire supported USB and FireWire supported Headsets or echo-cancelling microphones are strongly recommended
Headsets or echo-cancelling microphones are strongly recommended Headsets or echo-cancelling microphones are strongly recommended

Supported File Types

Native Support

Image Video Audio External Sources
PNG MP4 MP3 YouTube ®
GIF M4A
JPG MP4V

Supported by File Converter

MS Office™, text and PDF
PPT, PPTX
DOC, DOCX
XLS, XLSX
TXT, RTF
PDF

Ports

Please be sure to your ports and our server IP addresses using our System Check

WEB SERVER

https traffic on port 443.

SIGNALLING SERVER
https traffic on port 443 (recently changed from port 80).

MEDIA SERVER API
https traffic on port 443.

MEDIA SERVER

The following port options are available to you, in order of decreasing performance.

1. Allow RTP Traffic UDP:1024-65535
This will give the best performance, as it provides a direct connection path to our media servers.

2. Allow RTP Traffic UDP:80 or UDP:443 (incoming/outgoing)
This will allow UDP connections to our media servers via a TURN server on port 80. UDP is the preferred transfer protocol for real-time communications. However, the single port could cause performance problems if there is a lot of traffic between our networks.

3. Allow RTP Traffic TCP:80 or TCP:443 (incoming/outgoing)
This will allow TCP connections to our media servers via a TURN server on port 80. TCP could cause issues, especially when there is a lot of traffic or poor connectivity. Additionally, the single port could cause performance problems if there is a lot of traffic between our networks.

NOTE: For security reasons, we do not allow direct TCP connections to our media server.

What happens if you only open a few ports to the Media Server?
We require four ports per user for UDP streaming. Ports cannot be shared by users, and ports are assigned in a random fashion from any available server port in the range of 1024-65k. If the ports the service attempts to connect to are not available on the client then the system will fall back to relaying via TCP over the signalling server. So, if you happen to be extremely lucky, and all four ports you are assigned happen to fall into the IP range you opened then you will connect via UDP. This is not recommended.

Feedback

Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment