Meeting Server configuration settings used in the guided activity

Find more details about IBM® Sametime® Meeting Server configuration settings for the guided activity, "Sametime guided activity: Install Sametime Meeting Server."

The following tables correspond to the tasks in the guided activity:

You must provide a value for all required fields or the installation cannot complete.

Base Meeting Server

The Base Meeting Server hosts online meetings.

Table 1. Base Meeting Server configuration settings

Field names and descriptions for configuring default settings for the Base Meeting Server.
Setting Description

URL for remote Capture Server

Required. Provide the URL of a Sametime Meeting Server that is configured with the Recording Capturer role.

To support the recording feature, the Base Meeting Server must communicate with the Recording Capturer server. In small deployments, these two servers are typically installed on the same computer and this URL is not needed. In large deployments, best practice is to install the Recording Capturer on a different computer from the Base Meeting Server (the Recording Capturer can share a computer with the Recording Renderer), and provide this URL to enable communications. If you deploy multiple Recording Capturer servers, this URL points to the load balancer that fronts them.

Meeting Document Conversion

A Meeting Document Conversion transforms files (stored in the Meeting Room Library) for optimal display. Document conversion is supported directly on the Sametime Meeting Server on IBM AIX®, Windows™, and all Linux™ servers except for those running on IBM System z®. To ensure optimal display of files, you can deploy an additional Meeting Server and configure it to perform the Document Conversion role. Typically, Meeting Servers that run on Microsoft™ Windows do not require conversion services because documents and presentations display clearly without any intervention; however, using a separate conversion server improves performance by offloading conversion tasks from the Base Meeting Server.

Table 2. Meeting Document Conversion configuration settings

Field names and descriptions for configuring default settings for the Meeting Document Conversion.
Setting Description

Document Conversion Server URL
Attention: If you selected both the "Base Meeting Server" and the "Meeting Document Conversion" configuration roles for this server, then leave both the Document Conversion Server URL and the Meeting Server URL fields blank. If you select only the "Meeting Document Conversion" configuration role, set the fields as follows:
  • Document Conversion Server URL

    Provide the URL of a Meeting Server that is configured with the Document Conversion Server role.

  • Meeting Server URL

    Provide the URL a Meeting Server that is configured with the Base Meeting Server role. If the Document Conversion Server is also being configured with the Base Meeting Server role, use the same URL that you provided in the Meeting Server URL field. If you deploy multiple Base Meeting Servers, this URL points to the load balancer that fronts them.

Meeting Server URL
Required. The value of this field depends on the configuration roles you selected for the current server:
  • If you selected both the Base Meeting Server and the Meeting Document Conversion roles, leave this field blank.
  • If you selected only the Meeting Document Conversion role for the current server, then provide the URL of the Base Meeting Server. If you deployed multiple Base Meeting Servers, this URL points to the load balancer that you deployed in front of them.

Meeting Recording Capturer

A Meeting Recording Capturer hosts the real-time recording feature for online meetings. If you want to enable recorded meetings, then at least one Meeting Server must be configured with this role. If you are installing a Sametime SIP Proxy/Registrar, the Meeting Recording Capturer must be added to the list of trusted IP addresses.

All of these fields are required unless marked as optional.

Table 3. Meeting Recording Capturer configuration settings

Field names and descriptions for configuring default settings for the Meeting Recording Capturer.
Setting Description

Capture Server URL
Required. Provide the fully qualified domain name of a Meeting Server that will have the Capture Server role. Do not use an IP address or a local loopback address. Depending on your configuration, use one of the following URLs:
  • If this is the only Capture Server being deployed, enter the URL of the computer where the Capture Server will be installed.
  • If you are deploying multiple Capture Servers, enter the URL of the load balancer that will be deployed in front of them.

The Render Server uses this URL to access the recordings and transform them into movie files that users can view.

Maximum recording duration in minutes

Required. Specify the maximum allowed length of a recording.

URL of the Meeting Server that is configured with the Base Meeting Server role

Required. Provide the URL a Meeting Server that is configured with the Base Meeting Server role.

If the Capture Server is also being configured with the Base Meeting Server role, use the same URL that you provided in the Meeting Server URL field. If you deploy multiple Base Meeting Servers, this URL points to the load balancer that fronts them.

Directory where Capture files will be stored

Required. Provide the path to the shared file system where the Capture Server will store recorded meetings. This is the location where you will store Capture files, which contain recorded meetings in their raw format.

If the Capture Server and the Render Server reside on the same computer, this location can be a directory that both servers can access and you can provide the absolute path here. If the servers reside on different computers, this location must be a shared drive on the network; for example: //shareddiskserver/capture , and must be accessible to both servers. Make sure that the drive is available before installing the Capturer Server and the Renderer Server, and whenever the servers are restarted.

User ID for Capture Server to record meetings
Required. Accept the default user ID, or create a new one; this ID is used only for recording meetings.
Important: Do not use an existing user from the LDAP directory, and do not use this server's WebSphere® administrator account. Using the WebSphere administrator account here will prevent the server from installing properly.

Sametime meetings do not allow anonymous users, so the Capture Server requires a valid user account to be able to "attend" and record meetings.

Password for Capture Server

Required. Create a password for the Capture Server user ID.

Hostname for the local audio capture application. This host name must be resolvable and routable from the SIP Proxy/Registrar.

Required. This is typically the same host name as the Capture Server that you are deploying; it uniquely identifies the local Capture Server that is recording meetings.

Port on which the local audio recorder application listens for SIP invitations

Required. This is the port that the Capture Server is listening on for communications from the SIP Proxy/Registrar. Typically this is port 5060 (unsecured communications) or 5061 (encrypted communications).

Audio Recorder IP with outbound connectivity to TURN/MCU

Required. Provide the IP address of the Meeting Capturer Server that is configured for outbound access to the Sametime Video MCU. The Meeting Capturer Server needs to be able to connect to the Sametime Video MCU to capture audio. In some network topologies, such as IBM SmartCloud®, the Meeting Capturer Server may reside on two different networks. Use the IP address on the network that can actually access the Video MCU. If a Meeting Capturer farm is deployed, use the IP address of the load balancer fronting the Meeting Capturer farm.

If you use multiple network cards, it is important to fill in the IP address to ensure that the Capture Server can access the Video MCU.

SIP Proxy/Registrar host
Required. Provide the fully qualified domain name of the preferred SIP Proxy/Registrar. If the SIP Proxy/Registrar is clustered, provide the fully qualified domain name of the cluster. If there is a load balancer fronting the cluster, use the fully qualified domain name of the load balancer.
Note: Do not use an IP address or a local loopback address.

SIP Proxy/Registrar port

Required. Provide the port number of the preferred SIP Proxy/Registrar.

SIP Proxy/Registrar transport

Required. Select the preferred transport protocol.

TURN host

Optional. Provide the fully qualified host name of the Sametime TURN Server. Do not use an IP address or a local loopback address.

If NAT or firewalls are in place and the SIP Proxy/Registrar is configured to use a Sametime TURN Server, the Capture Server must be able to connect to the TURN Server.

TURN transport
Optional. Select the preferred transport protocol, and then do the following:
  • If you selected TLS, click TURN uses TLS.
  • If you selected TCP or UDP, provide the TURN Server's port number.

Meeting Recording Renderer

A Meeting Recording Renderer opens files stored by the Capture Server, transforms them into movie files, and stores the files so that users can download and view them. If the computer is running Windows, you must already have installed Desktop Experience.

Table 4. Meeting Recording Renderer configuration settings

Field names and descriptions for configuring default settings for the Meeting Recording Renderer.
Setting Description

Directory where Render files will be stored

Required. Provide the path to the location where the Render Server will store movie files.

This is the location where you will store Render files, which are Capture files that have been transformed to movie format. If you store the files on the computer hosting the Render Server, provide the absolute path. If you are using a remote storage location, make sure that it is available whenever the Render server is restarted.

Horizontal resolution in output movie files

Required. Specify the width, in pixels, of the displayed recording. The most common display resolution uses 720 pixels for the width.

Vertical resolution in output movie files

Required. Specify the height, in pixels, of the displayed recording. The most common display resolution uses 1028 pixels for the height.

Number of days that recordings are valid for download

Required. Specify how long recorded meetings should remain available for users to download.

If many users record meetings, the number of stored Render files will grow quickly. You can conserve disk space by specifying how long each recorded meeting will be available for users to download. When this time period ends, the files "expire" and are eventually deleted from the server. After the download period ends, you should plan to archive expired recordings to another location in case users need to retrieve them later.

Number of days until expired recordings are deleted

Required. Specify how long expired recordings should be saved; when the time expires, the recordings will be deleted.

An expired recording is no longer valid for download, but you should not delete it until you have archived it. To allow time for archiving, specify how many days expired recordings should be saved in the Render Server's storage location before they are automatically deleted.

Number of simultaneous renders allowed per processor core

Required. Specify the number of renders that will be allowed to run at the same time on each processor core; typically this is limited to 2 renders on each processor core.

A render can process one recorded meeting at a time. Allowing too few simultaneous renders limits the number of recordings that can be transformed at once, and may result in a backlog of unprocessed recordings. Allowing too many simultaneous renders reduces server performance, which can also result in a backlog of unprocessed recordings. Choose an appropriate setting for your environment. Remember that if there are multiple processor cores on the Render Server, each core will allow the specified number of simultaneous renders.