Configuring Sametime 8.5.1 Media and Proxy Servers with an 8.0.2 Community Server using Sametime System Console 

Many customers have asked Lotus to extend configuration support from the Sametime System Console to environments that are still using 8.0.2 Community servers, but want to take advantage of the new features offered in the 8.5.1 release.  This article describes the process for doing this.

Before you begin

Make sure you have the following

• Sametime 8.0.2 Community server installed
• An Installed  8.5.1 Sametime System Console Server
• LDAP Deployment defined in the System Console Server- This should match the LDAP Server you are using on your Sametime 8.0.2 Community Servers.
• Your Sametime 8.0.2 Servers must be using an LDAP directory

Community Server Tasks

Place a copy of the 'SystemConsoleManualRegistration' folder and its contents from the Sametime 8.5.1 Community server installation media on to the Sametime 8.0.2 server. If you have a Sametime 8.5.1 Community server installed, the 'console' directory is equivalent to the 'SystemConsoleManualRegistration' folder on the installation media.  The console directory can be found in the Domino program directory on Windows and in the Domino data directory on non-Windows platforms.

• Place this on the 8.0.2 Community server in the Domino program directory on Windows and in the Domino data directory on non-Windows platforms.
• Make sure to use the same version of the console folder that matches the SSC server

In this Console folder, edit the console.properties file to match the items below. Ensure that the SSCHostName, SSCUserName and SSCPassword are correct.

Then edit the productConfig.properties - again ensuring that the NodeHostName is correct, the DepName should be something you can recognize in the Sametime System Console UI.

Edit the notes.ini

Add parameter SametimeDirectoryType=LDAP or SametimeDirectoryType=DOMINO as appropriate. Note: this parameter may already be there, if it is, don't alter it.

Run the Registration Utility on The Community Server

Run the registration utility - this is located in the 'console' folder - called "registerSTServerNode.bat/sh" from a command line.
When asked, make sure to use forward slashes when specifying domino program directory path - for example c:/program files/ibm/lotus/domino

When this completes successfully, you will see a new Community Server listed in the Guided Activities on the Sametime System Console

Sametime System Console tasks

Create The 8.5.1 Product Server Deployment Plans

In the Sametime System Console - when you are prompted to select a Community Server for the plan, select the newly registered 8.0.2 server from the list.

Install The 8.5.1 product servers

Install the 8.5.1 servers using the deployment plans you created - use the Sametime System Console during the install so that it will pick up the Deployment Plan you created for it.
 

Access the Admin UI for the Media Manager

Open the admin ui for the media manager - this will confirm its availability and allow you to make any needed changes

Configure the Sametime 8.0.2 Community Server

Do this on all of the roomservers in the Community Cluster:

1. Add media server ip to community server's trusted ips directly in stconfig.nsf
2. Add proxy server ip to community server's trusted ips directory in stconfig.nsf

Disable Telephony Services

1. Run regedit on windows and locate My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Lotus\Sametime\MeetingServer\Services\TelephonyService
2. Set value of Enabled to 0.

Update policies on the 802 community servers

1. Select Policies then Sametime Default Policies.
2. Set the value of Allow Telephony to 'Contact lists, instant messaging, and instant meetings'.
3. Set the value of Allow all Sametime Connect features to be used with integrated clients to Yes.

Restart All of the Community Servers so the change takes affect

Test

1. Make sure that "remember password" is enabled.
2. Make sure to try to video chat with another user - options will be greyed out if you try against yourself.

IMPORTANT NOTE: The 8.0.2 Community servers will NOT be administered from the Sametime System Console, they will still be administered from the administration pages on the Community server itself.  This also means that any policy settings you create for media server will not be applied in this environment- the policy settings for media need to be added directly to the community server.  In this configuration, the SSC will not pass the policy information to the 8.0.2 server, however the UI that appears to allow you to administer policies for media servers will not be disabled.

Setting 8.5.1 Media Client/Server Policies in the 8.0.2 community server

No new policies are required to be added to the 8.0.2 stpolicy.nsf, as the client will default to the following settings:

Client/Server (Global) Attributes for A/V

1. av.allowClientSideHosting
1. Type: boolean (numeric 1 or 0)
2. Default: 1
2. av.videoResolution
1. Type: string
2. Default: "CIF 352x288@15fps 384kbps". Other examples "HD 960x720@30fps 14000kbps", "VGA 640x480@15fps 4000kbps", "QCIF 176x144@30fps 192kbps" etc
3. av.audioCodecPreferenceList
1. Type: string
2. Default: "ISAC,iLBC,G7221-32000,G7221-24000,G7221-16000,G.711"
4. av.videoCodecPreferenceList
1. Type: string
2. Default: "H264,H263"
5. im.2017
1. Type: integer
2. Default: 20830 (Range: 10000 to 99999 - 100)
6. im.2018
1. Type: integer
2. Default: 20832 (Range: 10000 to 99999 - 100)
7. av.encryption
1. Type: choice (0 - RC2, 1 - SRTP, 2 - No Encryption)
2. Default: 0
8. av.enableNATTraversal
1. Type: boolean (numeric 1 or 0)
2. Default: 0
9. av.sipPRServerHost
1. Type: string
2. Default: ""
10. av.sipPRServerPort
1. Type: integer
2. Default: 5060
11. av.sipPRServerTransportProtocol
1. Type: string
2. Default: "TCP"

Policies for A/V are
1. av.allowAccessToTPartyFromCListAndIM
1. Type: boolean (numeric 1 or 0)
2. Default: 0
2. av.allowChangesToPrefNumbers
1. Type: boolean (numeric 1 or 0)
2. Default: 0
3. av.avCapAvailableThroughSMS
1. Type: choice (0 - None, 1 - Audio only, 2 - Audio and video)
2. Default: 2

If a change from the default is required, you would add only the item that needs to change directly to the stpolicy.nsf on the 8.0.2 servers, by editing the existing policy documents and adding them to the end of the document in the empty fields provided.