Kamailio Deployment¶
As is it known, Kamailio implements a script of fisrt_boot_installer.tpl, which can be invoked using provisioning technology or can be executed manually with a previous parameterization of the variables involved.
To get the script, launch the following command:
curl https://gitlab.com/omnileads/omlkamailio/-/raw/master/deploy/first_boot_installer.tpl?inline=false > first_boot_installer.sh && chmod +x first_boot_installer.sh
So, once we have the script, we go to work on the variables, removing comments and setting their values inside the script. We are going to list and explain each of these variables that should be set before running the script.
Installation Variables¶
- oml_infras_stage: Refers to the infrastructure provider involved. The idea is to take advantage of the APIs of cloud providers to determine topics like network parameters. If we are going to install onpremise or in a cloud-based platform not available in the list, assign onpremise as a value for the variable. Possible values:onpremise, aws, digitalocean, vultr, linode.
- oml_kamailio_release: Here you should indicate which release you want to deploy.
- oml_redis_host, oml_acd_host and oml_rtpengine_host: Lastly, we mention these 3 variables in a grouped way, since they have to do with the fact of declaring the network address of each of these components with whom Kamailio needs to interact in his work.
Installation Execution¶
Finally, we can launch the script first-boot-instaler.sh. This can be done as user_data of a cloud instance, through some command line utility to manage the infrastructure, or directly copying the file to the destination Linux host and launching the execution of it.
To verify that the component is operational, we should launch the following command and observe the following output:
systemctl status kamailio
