Rebooting a Conferencing Node
Occasionally, it may be necessary to reboot a Conferencing Node. A reboot is typically required if:
- You have changed some specific such as the media and signaling port ranges, or you have enabled or disabled call protocols.
- A Conferencing Node fails to upgrade, for example if 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.