Configuring the Sametime Bandwidth Manager to use the SIP Proxy/Registrar Server

Configure IBM® Sametime® Bandwidth Manager to use the Sametime Media Manager's SIP Proxy/Registrar.

About this task

This task is required for both a stand-alone Bandwidth Manager and a cluster of Bandwidth Managers. Communications between the Bandwidth Manager and the Media Manager are handled by the SIP Proxy/Registrar.

Procedure

  1. Log in to the Bandwidth Manager Server's Integrated Solutions Console as the WebSphere® administrator (in a cluster, use the deployment manager).
  2. In the navigation tree, click Sametime Servers > Bandwidth Manager.
  3. On the Status page, click the Configuration tab.
  4. Change the SIP Server URI field to:
    [sip]:SipProxyIPAddress:ProxyRegistrarHostPort;transport=[tcp|tls]
    where:
    • You use sip for a non-secure or secure port.
    • SipProxyIPAddress is the IP address of the SIP Proxy/Registrar Server (for a cluster, use the deployment manager's IP address).
    • ProxyRegistrarHostPort is the SIP_ProxyRegHOST port number that you noted when confirming the SIP Proxy/Registrar virtual host.
    • The transport setting must be TLS for a secure environment. In a nonsecure environment, use TCP. This setting should match the Transport Protocol setting you used when setting up routing rules.
  5. Click Apply and then save the change to the master configuration by clicking the Save link in the "Messages" box at the beginning of the page.
  6. Restart the Bandwidth Manager Server (or cluster):
    • Stand-alone Server:
      1. Click the Status tab.
      2. On the Status page, click the Start/Restart button at the beginning of the table.
      3. After a few seconds, click the Refresh button and verify that all three Bandwidth Management components are now active.
    • Cluster:
      1. Stop the deployment manager:
        1. Click System Administration > Deployment manager.
        2. Click the Configuration tab.
        3. On the Configuration tab of the deployment manager settings, click Stop.
      2. Start the deployment manager:
        1. Open a command window and navigate to the app_server_root/profiles/DM_profile_name/bin.
        2. Run the startManager command.

        Linux

        cd /opt/IBM/WebSphere/AppServer/profiles/DM_profile_name/bin
startManager.sh

        Microsoft Windows

        cd C:\Program Files\WebSphere\AppServer\profiles\DM_profile_name\bin
startManager.bat