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 a cluster of Bandwidth Managers. Communications between the Bandwidth Manager and the Media Manager are handled by the SIP Proxy/Registrar.

Procedure

Log in to the Deployment Manager's Integrated Solutions Console as the WebSphere® administrator.
In the navigation tree, click Sametime Servers > Bandwidth Manager.
On the Status page, click Start/Restart.
Click the Configuration tab.
In the SIP Server URI field, enter the following string:
```
sip:host:5060;transport=tcp
```
where:
- You use sip for a non-secure port and sips for a secure port.
- host is the name of the load balancer in front of the SIP Proxy/Registrar server.
- 5060 is the Proxy/Registrar Port number you noted when Verifying host names and ports for Bandwidth Manager servers.
- The transport setting matches the setting that you specified for force-routing the SIP Proxy/Registrar.
For example, in the staging environment, specify
sip:sippr.example.com:5060;transport=tcp
Locate the Cluster SIP URI column in the table. Locate the rows labeled SIPFrontEnd in the table. For the SIPFrontend rows, add ;transport=tcp to the end of the settings in the Cluster SIP URI fields. For example, enter
sip:sippr.example.com:5060;transport=tcp
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.
Restart the Bandwidth Manager cluster:
- 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
```