Home
Deploying
IBM® Sametime® consists of a variety of servers and clients, and can be deployed to suit many different environments. The deployment instructions are organized by feature set, beginning with the minimum components that are necessary to support instant messaging, and then expanding the deployment to include features such as audio and video support, and conferencing.
Deploying an instant messaging gateway for external communities
Clients in a local IBM® Sametime® community can communicate with users in other communities through the Sametime Gateway.
Installing Sametime® Gateway Servers in a cluster
Install a cluster of IBM® Sametime® Gateway servers in a network deployment.
Creating a cluster and proxy servers
Create a Sametime® Gateway cluster, install proxy servers, and then configure the proxy servers to use the cluster. Set up node replication only if you need high availability and failover, and then start the cluster.
Configuring a SIP proxy server
Configure the Session Initiation Protocol (SIP) proxy server for a cluster of IBM® Sametime® Gateway Servers. There is no need to configure external domains in the SIP proxy server; this is done through the Sametime Gateway configuration.
Configuring the sent-by host name for the SIP proxy server
Create a custom property that specifies the proxy server's fully qualified host name as the "sent by" value.

Configuring the sent-by host name for the SIP proxy server

Create a custom property that specifies the proxy server's fully qualified host name as the "sent by" value.

About this task

By default, SIP messages use the sending server's IP address as the "sent by" value. If the sending server is behind a firewall or is managed by a load balancer or a network address translator, the IP address will not be directly reachable. You can work around the problem by creating a custom property for every IBM® WebSphere® SIP proxy server in the cluster and specifying the server's fully qualified host name.

Procedure

Complete the following steps on every WebSphere SIP proxy server in the cluster.

On the SIP proxy server, log in to the Integrated Solutions Console as the WebSphere administrator.
In the navigation list, click Servers > WebSphere application servers > server_name.
In the Container Settings section of the Configuration page, click SIP Container Settings > SIP Container > Custom properties.
Create a new custom property with the following settings:
- Name: com.ibm.ws.sip.sent.by.host
- Value: FQDN_of_Gateway_server
Save the new property.