Skip to main content
Skip table of contents

Install Mediaserver MSE (preferred)

All operations will be executed on VM1, unless an alternative is explicitly designated.

To install Mediaserver MSE, follow these steps:

  1. To prepare the configurations files for MSE, run the scripts:

CODE
source ./k8s-onprem/sources.sh
./configure-mse.sh ${MS1_IP}
  1. Find the env file .env.{IP address}.vsaas and configure license information from your online or offline license:

CODE
ls -la ../mse/
vim ../mse/server.json.${MS1_IP}.vsaas
  1. Replace the <url or path to license files> variable with:

    1. for online – the license URL

    2. for offline – the license path /etc/vsaas/license

CODE
  "license": "<url or path to license files>",

If an offline license is used, replace the license.json and public.key files in the ../mse/folder with the appropriate license files.

Optionally, replace the self-signed certificate with your own certificate (replace the key and certificate files keeping the same files names: cert.pem and key.pem). The path to the key and certificate files is ls -la ../mse/.

If you use self-signed certificates, add them to the list of trusted certificates on the client device to view video streams on the VMS web client.

  1. To configure and deploy MSE, run the script:

CODE
source ./k8s-onprem/sources.sh
./configure-mse.sh ${MS1_IP} $(echo ${USER}) configure
./deploy-mse.sh
  1. Check the status of the MSE container:

CODE
kubectl get all -n vsaas-ms
  1. When MSE is successfully installed, register it on VMS. For the detailed instructions, see this guide. This procedure requires a token. To obtain a token, run the following command on MSE:

CODE
curl -k --request POST  --url 'https://localhost:8665/api/' --header 'Content-Length: 114' --header 'Content-Type: application/json' --header 'Accept: application/json' \
--data '{"jsonrpc": "2.0", "method": "Auth.CreateApiToken", "params": {"ttl": 0}, "id": 1}'
JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.