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
- Browse to the IBM WebSphere® Integrated Solutions
Console on the server hosting the Sametime System Console.
- Log in to the Integrated Solutions Console as the WebSphere administrator.
- In the navigation tree, click .
- On the Status page, click the link for the server hosting
the SIP Proxy/Registrar component.
- On the Configuration page, locate the Container
Settings section, and then expand the SIP Container
Settings. Then click the SIP container transport
chains.
- 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
- Save the change to the master configuration by clicking
the Save link in the "Messages" box at the
beginning of the page.
- In the navigation tree, click .
Click the select the PR Node option and click Full
Resynchronize.
- Restart the SIP Proxy/Registrar.