Openvocs uses systemd for service operations. The main service is called ov_mc.target, which stands for openvocs Multicast target. This is the root service of openvocs. If you restart this service anything required for openvocs operations will be restarted. Please note, some services, which are not core services, need to have a dedicated restart cycle
ov_mc.target
ov_mc.target is the main service. It contains all subservices to load and may be used to restart / start or stop the openvocs services.
ov_mc_vocs.service
ov_mc_vocs.service is the main service of openvocs. It includes the build in webserver and all authentication and authorization functionality. In addition it manages the subservices e.g. ov_mc_ice_proxy or ov_mc_mixer.
ov_mc_ice_proxy.service
The ice proxy service is used to connect Webpages with the system. It establishes the media connection and forwards media to mixer instances. Another feature of the ice proxy is the media path encryption using SRTP based media streams. A mixed stream of all selected conferences will be send back to the clients.
ov_mc_mixer.target
This service is a parent service target for all mixer instances. Mixer instances will be startet as defined within the mixer.target. By default 50 mixer instances will be started. If you need more instances, for example to support more users, you may configure additional instances within the ov_mc_mixer.target
ov_mc_mixer@service
The mixer service is responsible to start one mixer instance to be available within the system. All mixer instances use the same configuration and will be reconfigured by ov_mc_vocs.service, based on the use of the mixer.
