Setting properties for the Sametime Bandwidth Manager

Use the Configuration page to define properties that determine how the IBM® Sametime® Bandwidth Manager handles SIP requests.

About this task

The properties you define here apply to the Bandwidth Manager as a whole; the individual modules have additional properties that you define when adding those modules.

Procedure

  1. On the server hosting the Bandwidth Manager, open the IBM WebSphere® Application Server Integrated Solutions Console and log in as the WebSphere administrator.
  2. Click Sametime Servers > Bandwidth Manager.
  3. Click the Configuration tab.
  4. The configuration properties appear at the beginning of the page.
  5. Provide values for the deployment environment's properties:
    OptionDescription
    Call Controller regex Accept the default value. The value is a regular expression used to recognize if an incoming SIP request is coming from the Sametime Media Manager server's Conference Manager.
    SIP server URI The URI to be used as the From header for SIP messages sent between servers within the Bandwidth Manager deployment. Any valid SIP URI can be used. This value is not used for routing.
    Inactive Session Timeout (Hours) Set '0' for No Timeout
    Initial call rate for unmanaged calls (kbps) The initial call rate is a value in Kbps that is applied to all unmanaged calls. It provides an overall call rate policy for such calls.
    Ignored user id prefix (regex) Accept the default value for the ignored user ID prefix. The value is a regular expression that defines prefixes for user identifiers used in From headers in SIP INVITE messages. The prefix is removed and ignored before looking up users IDs in the Federated Repository.
    Allow calls that exceed bandwidth capacity If you set the value to Yes, calls that would otherwise be restricted are allowed to exceed available bandwidth capacity. This setting also affects calls that have no route during ICE re-INVITE, as well as calls to unmanaged destinations.
    Identify organizational units as groups If you set the value to Yes, organizational units in LDAP can be used as groups in policy definitions.
  6. Click Apply to save your changes, or Reset to cancel them and revert to the previous settings.
  7. Save the change to the master configuration by clicking the Save link in the "Messages" box at the beginning of the page."