Add an external Sametime® community to IBM® Sametime Gateway Server.
You connect to a Sametime community
by specifying domains in the external community, selecting a translation
protocol, and setting the host name, port, and transport protocol
for the external community.
Before you begin
You must add the local Sametime community first
before adding an external community. In addition, if you are not connecting
to a Sametime 7.5 or
later server using its own Sametime Gateway Server,
be sure that the external Sametime 6.5.1 or 7.0 server
has the Sametime SIP
Gateway enabled. Finally, confirm that the external Sametime server and Sametime Gateway Server
have the latest fixes installed.
About this task
Expected state:
- Single server: the local Sametime Gateway Server
is started.
- Cluster: the deployment manager is started, and the node agent
and a Sametime Gateway
Server are started on at least one node.
Procedure
- In the Integrated Solutions Console, click .
- In the table that lists communities, click New.
- In the Name field, type a logical
name for the new community.
Restriction: After
you name and save a community, the name cannot be changed. To rename
a community, you must remove the original community and add the community
again with the new name.
- In the Community Type field, select External.
- In the Domains field, type the Fully
qualified domain names in which users are found in the external community.
Each domain name must access the same user directory. For example:
example.com, us.example.com, fr.example.com, and uk.example.com must
all be linked by a common user directory to be in the community. Obtain
this information from the system administrator in the external community.
You can use a wildcard character (*) in this field as a prefix,
but it must always be followed by a period and at least two components
of the fully qualified domain name. A value of *.example.com includes us.example.com and test.prod2.example.com.
For
example, you can use either of these values, *.example.com and *.us.example.com,
but you cannot use *example.com because the
wildcard is not followed by a period.
- Select a Translation Protocol:
Option | Description |
---|
SIP for Sametime Gateway |
Use SIP for Sametime Gateway for Connections
to Sametime Gateway
Server versions 7.5 or later communities. |
SIP for legacy Sametime Gateway |
Use SIP for legacy Sametime Gateway for Sametime versions 7.0 or
6.5.1 communities. |
- In the Host Name field, type the
name of the external real-time communication server such as ExampleServer1.com,
for example.
Note: If the host name is an IPv6-format
network address, set an explicit address here; do not use an abbreviated
address (no brackets, no leading zeroes). For example, all of these
IPv6-format network addresses are equivalent, but only the first
form is accepted:
1:2:0:0:0:6:7:8
[acceptable]
1:2::6:7:8
[do not use this abbreviated format]
01:2:0:0:0:006:0007:8
[do not use leading zeroes]
- In the Port field, type the port
number (the default port number is 5061).
The port you
use is dependent on the Transport protocol you
select in the next step:
- TLS uses port 5061
- TCP uses port 5060
- In the Transport protocol field,
select TLS (Transport Layer Security) or TCP (Transmission
Control Program or TCP/IP).
If you select TLS as the
protocol, you must set up SSL with a certificate signed by a Certificate
Authority and exchange trusted certificates with the external community.
- Click OK to save the new community.
Note that you can't assign users to the community until you save the
community.
- On the Communities panel, select
the name of the community that you created, scroll to the end, and
click Assign local users to this community to
assign local users access to the external community.
- The following steps are optional, but be sure to restart
the Sametime Gateway
Servers if you make any changes to the community.
- In the Route properties field,
set the maximum sessions for instant messaging or presence for
this community. The session numbers set for this community cannot
exceed the global maximum sessions set for Sametime Gateway. If Route
properties are not visible, you must connect to a local
community first.
- Select the check box to disable the route to the community.
- Click the Translation Protocol link
to set custom properties for the translation protocol. The Custom
properties links are available only after the community
is saved.
- Click Custom Properties to set
additional properties for the community. The Custom properties links
are available only after the community is saved.