Verifying the stavconfig.xml file settings for the SIP Proxy/Registrar and Conference Manager components

Verify the settings in the stavconfig.xml file for the IBM® Sametime® Media Manager SIP Proxy/Registrar and Sametime Media Manager Conference Manager.

About this task

Complete this procedure for every SIP Proxy/Registrar node and every Conference Manager node. Ensure that the settings match on every node so that every node looks at the same servers.

Note: In this example, the Sametime TURN Server is disabled, therefore, the IP address for the TURN Server is 0.0.0.0.

Procedure

  1. On the server hosting the SIP Proxy/Registrar or Conference Manager’s deployment manager, locate the stavconfig.xml file in the deployment manager’s profile.
  2. Open the file for editing.
  3. In the stavconfig.xml file, verify that your settings match the following settings:

    The following example uses fictitious host names; replace them with the fully qualified host names used in your deployment.

    STCommunityServerHost: STCommSrv.example.com 
      STCommunityServerPort: 1516
      ConferenceServerHost: STConfMngr.example.com
      ConferenceServerPort: 5062    
      NotificationServerHost: NotifySrv.example.com
      NotificationServerPort: 9443
      SIPProxyServerHost: SIPPRSrv.example.com
      SIPProxyServerPort: 5062
      VMGRServerHost: Vmgr.example.com
      VMGRServerHTTPPort: 7443
      VMGRServerSIPPort: 5080
      ConferenceServerHTTPPort: 9080
      NATTraversalEnabled: false
      TurnServerUdpHost: 0.0.0.0
      TurnServerUdpPort: 3478
      TurnServerTcpHost: 0.0.0.0
      TurnServerTcpPort: 3478
    
  4. Save and close the file.
  5. Synchronize all nodes by completing these steps:
    1. On the cluster's deployment manager, log in to the Integrated Solutions Console as the WebSphere®® administrator.
    2. Click System administration > Nodes.
    3. Select all of the nodes in the cluster.
    4. Click Full Resynchronize.