- Installing the combined PR+CF components
Use IBM Installation Manager to install IBM Sametime Media Manager's SIP Proxy/Registrar and Conference Manager on the same computer. Installing the two servers on the same computer requires you to create a specialized deployment plan before using it to install each of the individual servers. The combined servers cannot be clustered for high availability; if you expect to require clustering in the future, you should install the SIP Proxy/Registrar and the Conference Manager on separate computers.
- Verifying a Media Manager installation
After installing an IBM Sametime Media Manager component, verify that the server was successfully deployed and federated to its deployment manager.
- Managing trusted IP addresses
Whenever you install an IBM Sametime server that communicates with a Sametime Community Server, you must add the new server's IP address to the Community Server's list of trusted IP addresses.
- Disabling token authentication on the Conference Manager
This release does not support token authentication, so disable the feature on the IBM Sametime Media Manager's Conference Manager component.
- Verifying a SIP Proxy/Registrar virtual host on a stand-alone server
Confirm that the ports used by the SIP Proxy/Registrar, part of the IBM Sametime Media Manager, are defined correctly for the sip_proxyreg_host virtual host. The virtual host must be correct after you can federate a primary node into the Sametime System Console.
- Verifying the Conference Manager virtual host
Confirm that the ports used by the Conference Manager, part of the IBM Sametime Media Manager, are defined correctly for the default_host virtual host. The virtual host must be correct after you federate a primary node into the Sametime System Console.