Hardware requirements for 8 Chat rooms (2 party each) simultaneous
- Thread starter Arif Butt
- Start date
Hello!
For your case, you can use a server with the following minimum characteristics:
To organize 8 chats, two participants each with a recording
4 CPU Core 2.4Ghz
8 GB RAM
2 Gbps channel, provided that only video chat participants will use it. If there is a need to connect more subscribers, then you need to choose the channel width based on their number.
Approximate calculation - One 240p stream is approximately 0.5 - 1 Mbps of traffic.
A 30 GB hard disk is sufficient for the system to function. The archive of records can be stored on another disk or copied to another storage.
If there is a need to store records on the same disk as the rest of the system, then you should rely on the following calculations:
1 minute of recording 320 x 240 at 1000 kbps is approximately 10 MB of disk space.
For your case, you can use a server with the following minimum characteristics:
To organize 8 chats, two participants each with a recording
4 CPU Core 2.4Ghz
8 GB RAM
2 Gbps channel, provided that only video chat participants will use it. If there is a need to connect more subscribers, then you need to choose the channel width based on their number.
Approximate calculation - One 240p stream is approximately 0.5 - 1 Mbps of traffic.
A 30 GB hard disk is sufficient for the system to function. The archive of records can be stored on another disk or copied to another storage.
If there is a need to store records on the same disk as the rest of the system, then you should rely on the following calculations:
1 minute of recording 320 x 240 at 1000 kbps is approximately 10 MB of disk space.
We have not tested WCS in HyperV, but there are the customers using servers in Azure cloud which uses HyperV under the hood.
So WCS should work on CentOS in HyperV.
Please ask the license questions to sales@flashphoner.com
Good day.
Seems like systemd or kernel on your system does not support capabilities setting for service. So the following workarounds may be applied:
1. Update systemd
2. Or update OS kernel
3. Or comment the following line in the file
then restart WCS service
In this case, WCS should start correctly, but can not bind TCP ports in range 0-1000. Please read details here
Seems like systemd or kernel on your system does not support capabilities setting for service. So the following workarounds may be applied:
1. Update systemd
2. Or update OS kernel
3. Or comment the following line in the file
/etc/systemd/system/webcallserver.service
Code:
[Service]
...
# This line should be commented
# AmbientCapabilities=CAP_NET_BIND_SERVICE
Code:
systemctl restart webcallserverPlease clarify: the service is starting, but displayed as failed, or not starting at all?
If service is started, but shows failed state with exit code 143, this known issue is already fixed in latest build 5.2.882, please update and check.
If service is not starting, please try to comment
and restart the service. In this case, service ahould start as root.
If this doues not help, please provide SSH access to the server using this private form.
If service is started, but shows failed state with exit code 143, this known issue is already fixed in latest build 5.2.882, please update and check.
If service is not starting, please try to comment
User and Group parameters in /etc/systemd/system/webcallserver.service file
Code:
[Service]
# Comment this out to start the service as root
#User=flashphoner
#Group=flashphoner
...If this doues not help, please provide SSH access to the server using this private form.
The license should not affect the service status displayed.
Also, you don't need to re-activate the license while updating WCS unless you did not fully removed the previous installation.