Rebooting and shutting down a Conferencing Node
Occasionally, it may be necessary to reboot or shut down a Conferencing Node.
In many cases, Conferencing Nodes will reboot automatically as a result of certain configuration updates:
- Changing some specific such as the media and signaling port ranges, or when you have enabled or disabled call protocols.
- Changing the system location of a Conferencing Node.
- Changing a Conferencing Node's role from a transcoding node to a proxying node or vice versa.
However, sometimes a manual reboot may be required, for example if a Conferencing Node fails to upgrade and it remains on a Waiting for calls to clear status.
There are two main ways to reboot a Conferencing Node:
- Log in to the hypervisor or your cloud service that is managing the host server and reboot the virtual machine using the relevant processes according to the management system.
- Connect to the Conferencing Node via SSH, log in as admin, and issue the command sudo reboot.
Sometimes you may need to shut down a Conferencing Node for maintenance, or if you are deleting it permanently. There are two main ways to do this:
- Log in to the hypervisor that is managing the host server and power off the virtual machine using the relevant processes according to the management system.
- Connect to the Conferencing Node via SSH, log in as admin, and issue the command sudo poweroff.
If your nodes are running in a cloud service, you should power off via SSH / serial console for a clean shutdown, and then use the cloud service's management portal to shutdown/stop the virtual machine to ensure that its associated resources are released.