Deleting redundant SIP Proxy/Registrar SIP container transport chains

Confirm that there are no redundant transport chains used by the IBM® Sametime® SIP Proxy/Registrar's SIP container. In deployments where the SIP Proxy/Registrar consists of both the SIP default ports and its own SIP Proxy/Registrar ports, redundant transport chains can be created automatically. Delete any redundant transport chains.

Procedure

  1. Browse to the IBM WebSphere® Integrated Solutions Console on the server hosting the Sametime System Console.
  2. Log in to the Integrated Solutions Console as the WebSphere administrator.
  3. In the navigation tree, click Servers > Server Types > WebSphere application servers.
  4. On the Status page, click the link for the server hosting the SIP Proxy/Registrar component.
  5. On the Configuration page, locate the Container Settings section, and then expand the SIP Container Settings. Then click the SIP container transport chains.
  6. In the transport chains table, check for these entries:
    • SIPCInboundProxyReg
    • SIPCInboundProxyRegSecure
    • SIPCInboundProxyRegUDP
    • SIPCInboundDefault
    • SIPCInboundDefaultSecure
    • SIPCInboundDefaultUDP
    If the entries exist, delete these entries:
    • SIPCInboundProxyReg
    • SIPCInboundProxyRegSecure
    • SIPCInboundProxyRegUDP
    After removing the entries above, these entries remain:
    • SIPCInboundDefault
    • SIPCInboundDefaultSecure
    • SIPCInboundDefaultUDP
  7. Save the change to the master configuration by clicking the Save link in the "Messages" box at the beginning of the page.
  8. In the navigation tree, click System administration > Nodes. Click the select the PR Node option and click Full Resynchronize.
  9. Restart the SIP Proxy/Registrar.