I’ve made a simple install in a Debian 10 computer.
I’ve found something about Colibri, but I don’t find anything installed with jitsi packages.
Here seems that with a simple line this is started (for public):
This file has been truncated.
Jitsi-videobridge supports two HTTP(S) interfaces, a _public_ and a _private_ one.
The two interfaces use different ports. The _private_ interface exposes
HTTP endpoints which are not meant to be publicly accessible (but might be used
by other components of the infrastructure, e.g. a signaling server), such as:
* The [COLIBRI control interface](rest-colibri.md) (```/colibri/```)
* The health-check interface (```/about/health```)
* The version interface (```/about/version```)
The _public_ interface inludes:
* Support for serving static files (e.g. the HTML/js for jitsi-meet)
* Support for proxying (for e.g. proxying BOSH connections to a prosody instance)
* A WebSocket API for communication with conference endpoints (```/colibri-ws/```)
**For any of the HTTP interfaces to be enabled, jitsi-videobridge needs to be started with the ```--apis=rest```
parameter (or ```--apis=rest,xmpp``` to also enable the XMPP interface to COLIBRI).** This is enough to enable the
private interface, but for the public interface additional properties are required (see below).
Adding the following to /etc/jitsi/videobridge/sip-communicator.properties
Can be it so simple like this?