Skip to main content
Skip table of contents

Install Mediaserver

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

To install Mediaserver, follow these steps:

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

CODE
source ./k8s-onprem/sources.sh
./configure-mediaserver.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 ../mediaserver/
vim ../mediaserver/.env.${MS1_IP}.vsaas
  1. Replace the LICENSE_SOURCE variable with the license URL (for online) or the license path (for offline):

CODE
# for ONLINE licensing
# LICENSE_SOURCE=<License URL>

# for OFFLINE licensing
# LICENSE_SOURCE=<Path to directory with license.json and public.key>

LICENSE_SOURCE=/etc/aipix/media-server

If an offline license is used, replace the license.json and public.key files in the ../mediaserver/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). Path to the key and certificate files:

ls -la ../mediaserver/

 

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 Mediaserver, run the script:

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

CODE
kubectl get all -n vsaas-ms
  1. When Mediaserver 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 Mediaserver:

CODE
curl -k --location --request POST 'https://localhost:8080/api/auth/token/api/' --header 'Content-Type: application/json' \
--data-raw '{     "client": "client-unique-id",     "duration": 946080000 }'

JavaScript errors detected

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

If this problem persists, please contact our support.