Cisco Cisco MeetingTime Quick Setup Guide

Configuring Cisco Unified MeetingPlace Web Conferencing and SQL Server

How to Use a Custom TCP Port for the SQL Server Connection

Note

All SQL Servers are required to be local to the Cisco Unified MeetingPlace server that is handling the
replication. SQL Servers can be “remote” in that they are installed on separate machines within a local
data center. However, Release 7.1 does not support attaching to an SQL Server in a remote data center.

•

Customizing the Port for an SQL Database, page 26

•

Customizing the SQL Port for the “Remote” SQL Database, page 26

•

Switching to the “Remote” SQL Database on the Custom Port, page 27

Customizing the Port for an SQL Database

Procedure

Step 1

In the SQL server network utility, perform the following:

Note

To perform this operation in SQL Server 2005, use the SQL Server Configuration Manager tool.

Select TCP.

Select Properties

Change the default port from 1433 to the desired port, then select OK.

Step 2

Stop the SQL server.

Step 3

Start the SQL server.

Step 4

Edit the registry:

Go to HKEY_LOCAL_MACHINE\SOFTWARE\Latitude\ODBC.

Create a registry key of type DWORD named SlaveDBPort.

Set the created entry to your desired value for the port.

Step 5

Restart the Cisco Unified MeetingPlace Web Conferencing service.

Note

When you restart the Web Server, all manual changes made to the registry are lost.

Customizing the SQL Port for the “Remote” SQL Database

Note