Custom Jitsi
To use your own Jitsi, you must edit your plugin parameters and, in the server, select the Custom Jitsi Option
The easiest way to set up your custom Jitsi Meet is to use the docker version. to do this you can follow this tutorial: https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-docker
make sure you use the Authentication using JWT tokens
On the Meet plugin parameter, you MUST fill in the value of the following parameters
- secret: no need to change, this is used only on our own servers
- invitation: this is used on the create meet page
- CUSTOM_JITSI_DOMAIN: the URL for your Jitsi server
- JWT_APP_ID: you can find it on your .env file, just copy and paste the value here. This is required for the JWT authentication
- JWT_APP_SECRET: you can find it on your .env file, just copy and paste the value here. This is required for the JWT authentication
For example, we have an example of Jitsi here https://jitsi.eu1.ypt.me/, so our CUSTOM_JITSI_DOMAIN is jitsi.eu1.ypt.me.
Make sure you verify those values on your .env file and make sure the values on the {JWT_APP_ID} and the {JWT_APP_SECRET} are the same as the values on the plugin's parameters. the other parameters must be the same as the one below
# Select authentication type: internal, jwt or ldap
AUTH_TYPE=jwt
# JWT authentication
#
# Application identifier
#YPT
JWT_APP_ID={JWT_APP_ID}
# Application secret known only to your token generator
#YPT
JWT_APP_SECRET={JWT_APP_SECRET}
# (Optional) Set asap_accepted_issuers as a comma separated list
#YPT
JWT_ACCEPTED_ISSUERS=*,avideo
# (Optional) Set asap_accepted_audiences as a comma separated list
#YPT
JWT_ACCEPTED_AUDIENCES=*
The camera and microphone will require an HTTPS connection to work. Access from insecure HTTP will not work. Camera and microphone are powerful features, and browsers will only expose them in secure contexts.
Remember, in order to use the camera, your domain MUST BE in HTTPS.
