Universal Messaging 10.1 | Administration Guide | Using Command Central to Manage Universal Messaging | Managing Universal Messaging using Command Central
Managing Universal Messaging using Command Central
You can configure and administer Universal Messaging server instances using the Command Central web or command-line interface.
Command Central uses one of the Universal Messaging ports (interfaces) for configuration and administration. Command Central checks the ports (interfaces) of a Universal Messaging server instance in the following order and chooses the first available port (interface) to connect to the server:
1. Interfaces that use HTTP protocol (nhp)
2. Interfaces that use socket protocol (nsp)
3. Interfaces that use HTTPS protocol (nhps)
4. Interfaces that use SSL protocol (nsps)
Command Central will use a secured port (nhps and nsps) to connect with a Universal Messaging server instance only if the client-side certificates are not required for establishing the connection. Command Central does not use ports that use shared memory protocol (shm).
If there is a disconnection between Command Central and the Universal Messaging server, Command Central will connect to a new port using the same order used to check the next available port for communicating with the Universal Messaging server.