WebConferencing – Features

Min. Bandwidth Required = 512 Kb/S

Max File Size = 10 Mb (MS./Open Office Document file , For best result use Pdf to upload)

Max Slide (File) Pages = 100

software compatibility

Your favourite latest version of Internet Browser like “Google Chrome” or “Mozilla Firefox”. Mobile: You can use mobile version of “Google Chrome”.

Live Demo

How it work, watch the demo video VC-How It Works

You can try a demo of our classroom from here

Choose Meeting : – Demo Meeting or Demo Meeting (Recorded)  ——> Note : – Demo Recorded Session Will Be Deleted after some time.

Name : – Enter Your Name (If Asked)

Password : – ap (As Attendee) or mp (As Trainer)  ———> Note : – Do not type (As Attendee) or (As Trainer) in password field.

Recorded Sessions tried by visitors

There are no recordings available.

Meeting Place

Bandwidth Requirements

What are the bandwidth requirements for running a Saa9vi Video Conference server

You’ll need good upstream and downstream bandwidth from the server. We recommend (at least) 100 MBits/second bandwidth in both directions.

When sharing a webcam as a moderator, Saa9vi Video Conference lets you select 320×240, 640×480, or 1280×720. For bandwidth calculations, each resolution corresponds (roughly) to a .25 Mbits/sec, 0.40 Mbits/sec, and 0.60 Mbits/sec video stream respectively.

For example, if you have a room with 5 users, each sharing their webcam at 320×240, then you can calculate the bandwidth usage as follows:

Y = .25 Mbits/sec
W = amount of webcams that are streaming
U = amount of users that are watching

For calculations:

server incoming bandwidth: W*Y
server outgoing bandwidth: W*(U-1)*Y (minus one since a broadcaster does not have to subscribe to his own stream)

For example, with 5 users in a room with 5 webcams streaming, the bandwidth calculation is as follows:

in: 5*.25 = 1.25 Mbits/sec incoming bandwidth needed to the server
out: 5*(5-1)*.25 = 5 Mbits/sec outgoing bandwidth needed from the server
Total traffic used after one hour: 60 mins*60 secs*(1.25 + 5) = 22.5 GBits/hour

If you’d have a typical classroom situation one presenter broadcasting their webcam to 30 remote students, the calculation is as follows:

in: 1*.25 = .25 Mbits/sec incoming
out: 1*(30-1)*.25 = 7.25 Mbits/sec outgoing
Total traffic used after one hour: 60 mins*60 secs*( .25 + 7.25) = 27 GBits/hour

Large “cafe-style chatroom”: 20 viewers, 8 people broadcasting with a webcam:

in: 8*.25 = 4 Mbits/sec incoming
out: 8*(20-1)*.25 = 38 Mbits/sec outgoing
Total traffic used after one hour: 60 mins*60 secs*( 4 + 38 ) = 252 GBits/hour

Sharing slides takes almost no bandwidth beyond the initial uploading/downloading of slides. When the presenter clicks to show the next slide, the viewers receive a “move next slide” command in their Saa9vi Video Conference client, and they load the next slide from the local cache. Chat has almost no bandwidth as well.

Desktop sharing takes the most bandwidth, and the actual bandwidth at any one time depends on the area chosen by the presenter (full screen and region) and how often their screen updates. At the low end, if the presenter’s screen is largely idle, the Saa9vi Video Conference server would receive 0.2 Mbits/sec; at the high hend, if the presenter’s screen is updating frequently, the Saa9vi Video Conference server could transmit 1.0 Mbits/sec. For a session with N users, Saa9vi Video Conference server would also transmit N desktop sharing streams (the presenter gets a stream as well for their preview window).

A VoIP connection to the Saa9vi Video Conference server takes roughly 0.04 Mbits/sec receiving and 0.04 Mbits/sec transmitting for each user. The bandwidth for VoIP grows linearly with number of users. For example, if there are 20 students in a classroom, then the bandwidth requirements for the server to support VoIP is 20 * 0.04 Mbits/sec = 0.8 Mbits/sec.

From the perspective of the user’s bandwidth needs, if a student is broadcasting their webcam and microphone they require a minimum (roughly) 0.3 Mbits/sec (.25 + .04) upstream bandwidth. If the student is in a session with four other people that are all broadcasting their webcams as well, the student will require the roughly 1 Mbits/sec incoming bandwidth for the 4 0.25 = 1 Mbits/sec incoming webcams and 0.04 Mbits/sec for the incoming audio.

The Saa9vi Video Conference server will lower the bandwidth to a user if their bandwidth is insufficient to receive all stream. For example, in the scenario above where there are 5 students in a session, each sharing a webcam, if 4 students have sufficient bandwidth to receive all incoming webcam streams, their clients will show roughly the same quality of video. If one of the students is on a lower bandwidth, then they will get less frequent updates on the video streams. They may also get degraded audio.

What are the minimum bandwidth requirements for a user

For viewers (students), we recommend users have (at least) 0.5 Mbits/sec — which is 500 Kbits/sec — upstream bandwidth, and (at least) 1 Mbits/sec download bandwidth. The upstream bandwidth is the amount of bandwidth their computer has available to transmit data to the Saa9vi Video Conference server.

These are not hard and fast numbers, as it depends on the activity of the viewer. If the viewer is not broadcasting any webcam, the amount of upstream bandwidth used would be less than 0.5 Mbits/sec.

A good way for users to check their bandwidth is to visit speedtest.net. The results from speedtest.net give the user’s actual bandwidth. This actual number is important because a user may report that their ISP provides them 0.5 Mbits/sec upstream bandwidth; however, speedtest.net may report an actual number that is much lower. The difference may be throttling by the ISP and background activity on their computer (such as background downloads, file sharing clients, etc).

For presenters, we recommend as much upstream bandwidth as possible. For example, if the presenter shares their desktop, then Saa9vi Video Conference desktop sharing will attempt to publish their desktop updates as quickly as possible to the server.