Table Of Contents
Configuring the Cisco CTL Client
Cisco CTL Client Overview
Cisco CTL Client Configuration Checklist
Activating the Cisco CTL Provider Service
Activating the Cisco CAPF Service
Configuring Ports for the TLS Connection
Installing the Cisco CTL Client
Upgrading the Cisco CTL Client and Migrating the Cisco CTL File
Configuring the Cisco CTL Client
Updating the CTL File
Updating the Clusterwide Security Mode
Cisco CTL Client Configuration Settings
Deleting a CTL File Entry
Configuring the Cisco CTL Client
This chapter contains information on the following topics:
•
Cisco CTL Client Overview
•Cisco CTL Client Configuration Checklist
•Activating the Cisco CTL Provider Service
•Configuring Ports for the TLS Connection
•Installing the Cisco CTL Client
•Upgrading the Cisco CTL Client and Migrating the Cisco CTL File
•Configuring the Cisco CTL Client
•Updating the CTL File
•Updating the Clusterwide Security Mode
•Cisco CTL Client Configuration Settings
•Deleting a CTL File Entry
Cisco CTL Client Overview
Device, file, and signaling authentication rely on the creation of the Certificate Trust List (CTL) file, which is created when you install and configure the Cisco Certificate Trust List (CTL) client on a single Windows 2000 workstation or server, perhaps a Cisco CallManager server, that has a USB port. The CTL file contains entries for the following servers or security tokens:
•Site Administrator Security Token (SAST)
•Cisco CallManager and Cisco TFTP running on the same server
•Certificate Authority Proxy Function (CAPF)
•Alternate Cisco TFTP
The CTL file contains a server certificate, public key, serial number, signature, issuer name, subject name, server function, DNS name, and IP address for servers. After you create the CTL file, you must restart the Cisco CallManager and Cisco TFTP services in Cisco CallManager Serviceability on all servers in the cluster that run these services. The next time that the phone initializes, it downloads the CTL file from the TFTP server. If the CTL file contains a TFTP server entry that has a self-signed certificate, the phone requests a signed configuration file in .sgn format. If none of the TFTP servers contains a certificate, the phone requests an unsigned file.
Note Cisco CallManager stores the CTL file, which exists in .tlv format, in the directory that is specified in the TFTP File Location and TFTP Alternate File Locations.
After you install and configure the Cisco CTL client, verify that a certificate exists in the phone, and configure the device for authentication or encryption, the phone establishes a TLS connection through a TLS SCCP port, which is a configured port number added to (+) 443. By default, the phone connects to port 2443 by using TLS. The handshake authenticates the certificates and establishes a secure connection.
Related Topics
•Cisco CTL Client Configuration Checklist
•Authentication and Integrity Overview, page 1-20
Cisco CTL Client Configuration Checklist
Table 3-1 provides a list of configuration tasks that you perform to install and configure the Cisco CTL client for the first time.
Table 3-1 Cisco CTL Client Configuration Checklist
Configuration Steps
|
Related Procedures and Topics
|
Step 1
|
On each Cisco CallManager and Cisco TFTP server in the cluster, activate the Cisco CTL Provider service in Cisco CallManager Serviceability.
Tip If you activated this service prior to a Cisco CallManager upgrade, you do not need to activate the service again. The service automatically activates after the upgrade.
|
Activating the Cisco CTL Provider Service
|
Step 2
|
On the publisher database server, activate the Cisco Certificate Authority Proxy service in Cisco CallManager Serviceability.
Timesaver Performing this task before you install and configure the Cisco CTL client ensures that you do not have to update the CTL file to use CAPF.
|
Activating the Certificate Authority Proxy Function Service, page 4-12
|
Step 3
|
If you do not want to use the default settings, configure ports for the TLS connection.
Tip If you configured these settings prior to a Cisco CallManager upgrade, the settings migrate automatically.
|
Configuring Ports for the TLS Connection
|
Step 4
|
Obtain at least two security tokens and the passwords, hostnames/IP addresses, and port numbers for the servers that you will configure for the Cisco CTL client.
|
Configuring the Cisco CTL Client
|
Step 5
|
Install the Cisco CTL client.
Tip You cannot use the Cisco CTL client that was available with Cisco CallManager 4.0. To update the CTL file after a Cisco CallManager 4.1(3) upgrade, you must install the plug-in that is available with Cisco CallManager Administration 4.1(3).
|
•System Requirements, page 1-4
•Installing Security, page 1-11
•Installing the Cisco CTL Client
|
Step 6
|
Configure the Cisco CTL client.
Tip If you created the CTL file prior to the Cisco CallManager upgrade, the CTL file migrates automatically during the upgrade. To update the CTL file after a Cisco CallManager 4.1(3) upgrade, you must install and configure the Cisco CTL client that is available with Cisco CallManager Administration 4.1(3).
|
Configuring the Cisco CTL Client
|
Activating the Cisco CTL Provider Service
After you configure the Cisco CTL client, this service changes the cluster security mode from nonsecure to mixed mode and vice versa and transports the server certificates to the CTL file; the service then transports the CTL file to all Cisco CallManager and Cisco TFTP servers.
If you activate the service and then upgrade Cisco CallManager, Cisco CallManager automatically reactivates the service after the upgrade.
Tip You must activate the Cisco CTL Provider service on all servers in the cluster.
Verify that the local administrator password or the Power Users account username and password are synchronized on all Cisco CallManager and Cisco TFTP servers.
To activate the service, perform the following procedure:
Procedure
Step 1 In Cisco CallManager Serviceability, choose Tools > Service Activation.
Step 2 In the pane on the left side of the window, choose a server where you have activated the Cisco CallManager or Cisco TFTP services.
Step 3 Check the CTL Provider service check box.
Step 4 Click Update.
Step 5 Perform this procedure on all servers in the cluster.
Note After you activate the service, the Cisco CTL Provider service reverts to the default CTL port, which is 2444. If you want to change the port, see the "Configuring Ports for the TLS Connection" section.
Step 6 Verify that the service runs on all servers in the cluster. In Cisco CallManager Serviceability, choose Tools > Control Center to verify the state of the service.
Related Topics
•Cisco CallManager Serviceability Administration Guide
•Cisco CallManager Serviceability System Guide
•Activating the Cisco CTL Provider Service
•Installing the Cisco CTL Client
Activating the Cisco CAPF Service
For information on activating this service, see the "Activating the Certificate Authority Proxy Function Service" section on page 4-12.
Timesaver Performing this task before you install and configure the Cisco CTL client ensures that you do not have to update the CTL file to use CAPF.
Related Topics
•Cisco CTL Client Configuration Checklist
•CAPF Configuration Checklist, page 4-9
•Activating the Certificate Authority Proxy Function Service, page 4-12
•Configuration Checklist Overview, page 1-24
Configuring Ports for the TLS Connection
You may have to configure a different port number if the port is currently being used or if you use a firewall and you cannot use the port within the firewall.
The Cisco CTL Provider default port for the TLS connection equals 2444. The Cisco CTL Provider port monitors requests from the Cisco CTL client. This port processes Cisco CTL client requests, such as retrieving the CTL file, setting the clusterwide security mode, saving the CTL file to TFTP servers, and retrieving a list of Cisco CallManager and TFTP servers in the cluster.
The Cisco CallManager port monitors registration requests from the phone. In nonsecure mode, the phone connects through port 2000. In mixed mode, the Cisco CallManager port for TLS connection equals the value for the Cisco CallManager port number added to (+) 443; therefore, the default TLS connection for Cisco CallManager equals 2443.
Tip After you update the port(s), you must restart the Cisco Provider service in Cisco CallManager Administration.
To change the default setting, perform the following procedure:
Procedure
Step 1 Perform the following tasks, depending on the port that you want to change:
•To change the Cisco CTL Provider port, perform Step 2 through Step 6.
•To change the Cisco CallManager port, perform Step 7 through Step 10.
Step 2 To change the Cisco CTL Provider port, choose Service > Service Parameters from Cisco CallManager Administration.
Step 3 Choose a server where the Cisco CTL Provider service runs.
Step 4 Choose Cisco CTL Provider service.
Tip In the upper, right corner of the window, click the i button to review information for the service parameter.
Step 5 To change the Cisco CTL Provider port, enter the new port number in the Port Number field.
Step 6 Click Update.
Step 7 To change the Cisco CallManager port, choose System > Cisco CallManager in Cisco CallManager Administration.
Step 8 Choose a server where the Cisco CallManager service runs.
Step 9 In the Ethernet Phone Port field, enter the new port number.
Step 10 Click Update.
Related Topics
•Activating the Cisco CTL Provider Service
•Installing the Cisco CTL Client
•Configuring the Cisco CTL Client
•Cisco CTL Client Configuration Settings
•Troubleshooting, page 9-1
Installing the Cisco CTL Client
You install the Cisco CTL client on a single Windows 2000 workstation or server that has a USB port. The server or workstation can exist at a remote site. If you choose to do so, you can install the client on a server where Cisco CallManager is installed as long as the server has a USB port.
You must use the client and update the CTL file when the following events occur:
•After the Cisco CallManager installation
•After you restore a Cisco CallManager server or Cisco CallManager data
•After you change the IP address or hostname of the Cisco CallManager server
•After you add or remove a security token, TFTP server, or Cisco CallManager server
•After you replace a TFTP or Cisco CallManager server
Caution Do not use Terminal Services to install the client. Cisco installs Terminal Services, so Cisco Technical Assistance Center (TAC) can perform remote troubleshooting and configuration tasks.
Before you run the plug-in, you must disable Cisco Security Agent (CSA) or other Cisco-approved intrusion detection or antivirus applications. Failure to disable the applications may prevent the installation and result in unrecoverable errors.
Tip If the Smart Card service is not set to started and automatic on the server or workstation where you plan to install the client, the installation fails. For information on how to perform this task, see the "Troubleshooting" section on page 9-1.
To review a list of messages that could display during the installation of the plug-in, see the "Troubleshooting" section on page 9-1.
To install the Cisco CTL client, perform the following procedure:
Procedure
Step 1 Verify that the Smart Card service is set to started and automatic. For more information, see the "Setting the Smart Card Service to Started and Automatic" section on page 9-11.
Step 2 Browse to Cisco CallManager Administration from the Windows 2000 workstation or server that has the USB port; that is, the location where you plan to install the client.
Step 3 From Cisco CallManager Administration, choose Application > Install Plugins.
Step 4 To download the file, click Cisco CTL Client.
Step 5 Download the file to a location that you will remember.
Step 6 To begin the installation, double-click Cisco CTL Client (icon or executable depending on where you saved the file).
Step 7 The version of the Cisco CTL client displays; click Continue.
Step 8 The installation wizard displays. Click Next.
Step 9 Accept the license agreement and click Next.
Step 10 Choose a folder where the client will exist. If you want to do so, click Browse to change the default location; after you choose the location, click Next.
Step 11 To begin the installation, click Next.
Step 12 After the installation completes, click Finish to exit.
Tip To verify that the client installed, see the "Troubleshooting" section on page 9-1.
Related Topics
•System Requirements, page 1-4
•Interactions and Restrictions, page 1-5
•Activating the Cisco CTL Provider Service
•Setting the Smart Card Service to Started and Automatic, page 9-11
•Activating the Cisco CTL Provider Service
•Configuring the Cisco CTL Client
•Updating the CTL File
•Deleting a CTL File Entry
•Configuring the Device Security Mode, page 5-6
•Troubleshooting, page 9-1
Upgrading the Cisco CTL Client and Migrating the Cisco CTL File
If you want to make changes to the CTL file after the Cisco CallManager 4.1(3) upgrade, you must install and configure the Cisco CTL client that is available with Cisco CallManager Administration 4.1(3).
If you did not remove or add any servers before the Cisco CallManager upgrade, you do not need to reconfigure the Cisco CTL client after the upgrade. The Cisco CallManager upgrade automatically migrates the data in the CTL file.
Related Topics
•Cisco CTL Client Configuration Checklist
•Installing the Cisco CTL Client
•Configuring the Cisco CTL Client
•Troubleshooting, page 9-1
Configuring the Cisco CTL Client
Tip Configure the Cisco CTL client during a scheduled maintenance window because you must restart the Cisco CallManager and Cisco TFTP services in Cisco CallManager Serviceability on all servers in the cluster that run these services.
The Cisco CTL client performs the following tasks:
•Sets the Cisco CallManager cluster security mode.
Tip You cannot set the Cisco CallManager clusterwide mixed mode through the Enterprise Parameters window in Cisco CallManager Administration. You must configure the CTL client to set the clusterwide mode. For more information, see the "Cisco CTL Client Configuration Settings" section.
•Creates the Certificate Trust List (CTL), which is a file that contains certificate entries for security tokens, Cisco CallManager, alternate TFTP, and CAPF servers.
The CTL file indicates the servers that support TLS for the phone connection. The client automatically detects the Cisco CallManager, Cisco TFTP servers, and the Cisco CAPF server and adds certificate entries for these servers.
You must manually add alternate TFTP servers and Site Administrator Security Tokens (SAST) to the CTL file.
The security tokens that you insert during the configuration sign the CTL file.
Tip You can configure an alternative TFTP server, even if this server exists in a different cluster. Through manual configuration, the certificate from the alternate TFTP server gets added to the CTL file, which is written to the FileLocation path as specified in the TFTP service parameter. For a multicluster configuration, you must map the drive on the alternate TFTP server and configure the FileLocation parameter to the mapped drive. For example, if you use TFTP1 as your alternate TFTP server and you have mapped drive L: to the path on TFTP1, the FileLocation equals L:\TFTPPath. You must add the TFTP server, TFTP1, for example, by specifying a valid administrator username and password for TFTP1. The Cisco CTL client will write the CTL file to L:\TFTPPath.
Before you implement this TFTP configuration, all servers in the multicluster environment must run the same version of Cisco CallManager and be configured for the same clusterwide security mode; be aware that all servers in the multicluster environment must run the Cisco CTL Provider service.
Before You Begin
Before you configure the Cisco CTL client, verify that you activated the Cisco CTL Provider service and the Cisco Certificate Authority Proxy Function service in Cisco CallManager Serviceability. Obtain at least two security tokens; the Cisco certificate authority issues these security tokens. You will insert the tokens one at a time into the USB port on the server/workstation. If you do not have a USB port on the server, you may use a USB PCI card.
Obtain the following passwords, hostnames/IP addresses, and port numbers:
•Local administrative password and hostname/IP address for Cisco CallManager and the port number for the CTL Provider service
•Local administrative password and hostname/IP address for alternate TFTP
•Security token administrative password
See Table 3-2 for a description of the preceding information.
Tip Before you install the Cisco CTL client, verify that you have network connectivity to each server in the cluster; likewise, ensure that the server uses DNS and that each server is running. To ensure that you have network connectivity to all servers in the cluster, issue a ping command to each server. Choose Start > Run; enter cmd, and click OK. At the command prompt, enter ping <server>, where server equals the name of the server that displays in the Server Configuration window of Cisco CallManager Administration. Repeat the ping command for each server in the cluster.
If you installed multiple Cisco CTL clients, Cisco CallManager only accepts CTL configuration information on one client at a time, but you can perform configuration tasks on up to five Cisco CTL clients simultaneously. While you perform configuration tasks on one client, Cisco CallManager automatically stores the information that you entered on the other clients.
After You Complete the Cisco CTL Client Configuration
After you complete the Cisco CTL client configuration, the CTL client performs the following tasks:
•Writes the CTL file to all Cisco CallManager servers in the cluster.
•Writes the CTL file to alternate TFTP server(s) that you configured.
•Writes CAPF capf.cer to all Cisco CallManager subscribers in the cluster.
•Writes CAPF certificate file in PEM format to all Cisco CallManager subscribers in the cluster.
To configure the client, perform the following procedure:
Procedure
Step 1 Obtain at least two security tokens that you purchased.
Step 2 Perform one of the following tasks:
•Double-click the Cisco CTL Client icon that exists on the desktop of the workstation/server where you installed it.
•Choose Start > Programs > Cisco CTL Client.
Step 3 Enter the configuration settings for the Cisco CallManager server, as described in Table 3-2; click Next.
Step 4 Click Set CallManager Cluster to Mixed Mode, as described in Table 3-2; click Next.
Step 5 Perform the following tasks, depending on what you want to accomplish:
•To add a security token, see Step 6 through Step 12.
•To add an alternate TFTP server, see Step 13 through Step 15.
•To complete the Cisco CTL client configuration, see Step 17 through Step 21.
Caution You need a minimum of two security tokens the first time that you configure the client. Do not insert the tokens until the application prompts you to do so. If you have two USB ports on the workstation or server, do not insert two security tokens at the same time.
Step 6 When the application prompts you to do so, insert one security token in an available USB port on the workstation or server where you are currently configuring the Cisco CTL client; click OK.
Step 7 The security token information displays for the token that you inserted; click Add.
Step 8 The detected certificate entries display in the pane.
Step 9 To add other security token(s) to the certificate trust list, click Add Tokens.
Step 10 If you have not already done so, remove the token that you inserted into the server or workstation. When the application prompts you to do so, insert the next token and click OK.
Step 11 The security token information for the second token displays; click Add.
Step 12 For all security tokens, repeat Step 9 through Step 11.
Step 13 The certificate entries display in the pane. If you need to add an Alternate TFTP server, click Add TFTP Server.
Step 14 Enter the configuration settings, as described in Table 3-2.
Step 15 Click Next.
Step 16 Enter the configuration settings, as described in Table 3-2; click Next.
Step 17 When you have added all security tokens and servers, click Finish.
Step 18 Enter the username password for the security token, as described in Table 3-2; click OK.
Step 19 After the client creates the CTL file, a window displays the server, file location, and status of the CTL file on each server. Click Finish.
Step 20 Reset all devices in the cluster. See the "Resetting the Devices, Restarting Services, or Rebooting the Server/Cluster" section on page 1-10.
Step 21 In Cisco CallManager Serviceability, restart the Cisco CallManager and Cisco TFTP services that run on each server in the cluster.
Step 22 After you create the CTL file, you may remove the security token from the USB port. Store all security tokens in a safe place that you will remember.
Tip To verify that you set the Cisco CallManager cluster to mixed mode, see the "Troubleshooting" section on page 9-1.
If you are prompted to change the security token password, see the "Troubleshooting" section on page 9-1.
Related Topics
•Cisco CTL Client Configuration Settings
•System Requirements, page 1-4
•Interactions and Restrictions, page 1-5
•Activating the Cisco CTL Provider Service
•Setting the Smart Card Service to Started and Automatic, page 9-11
•Activating the Cisco CTL Provider Service
•Cisco CTL Client Configuration Settings
•Configuring the Cisco CTL Client
•Updating the CTL File
•Configuring the Device Security Mode, page 5-6
•Troubleshooting, page 9-1
Updating the CTL File
You must update the CTL file after the following scenarios occur:
•If you add a new Cisco CallManager server to the cluster
•If you change the name or IP address of the Cisco CallManager server in the cluster
•If you enabled the Cisco Certificate Authority Function service in Cisco CallManager Serviceability
•If you add or delete additional security tokens
•If you add or delete the alternate TFTP server
•If you restore the Cisco CallManager server or Cisco CallManager data
For the changes to take effect, you must restart the Cisco CallManager and Cisco TFTP services in Cisco CallManager Serviceability for all servers that run these services; you must also reset all devices in the cluster after you restart the services. See the "Resetting the Devices, Restarting Services, or Rebooting the Server/Cluster" section on page 1-10 for more information on how to perform this task.
Tip Cisco strongly recommends that you update the file when minimal call-processing interruptions will occur.
To update the information that exists in CTL file, perform the following procedure:
Procedure
Step 1 Obtain one security token that you inserted to configure the latest CTL file.
Step 2 Double-click the Cisco CTL Client icon that exists on the desktop of the workstation/server where you installed it.
Step 3 Enter the configuration settings for the Cisco CallManager server, as described in Table 3-2; click Next.
Tip You make updates in this window for the Cisco CallManager server.
Step 4 To update the CTL file, click Update CTL File, as described in Table 3-2; click Next.
Caution For all CTL file updates, you must insert one security token that already exists in the CTL file into the USB port. The client validates the signature of the CTL file through this token. You cannot add new tokens until the CTL client validates the signature. If you have two USB ports on the workstation or server, do not insert both security tokens at the same time.
Step 5 If you have not already inserted one security token in an available USB port on the workstation or server where you are currently updating the CTL file, insert one of the security tokens; click OK.
Step 6 The security token information displays for the token that you inserted; click Next.
The detected certificate entries display in the pane.
Tip You cannot update the Cisco CallManager or Cisco TFTP entries from this pane. To update the Cisco CallManager entry, click Cancel and perform Step 2 through Step 6 again.
Step 7 To update existing Cisco CTL entries or to add or delete security tokens, consider the following information:
•To update alternate TFTP entries, delete the entry, as described in "Deleting a CTL File Entry" section; then, add the entry, as described in "Configuring the Cisco CTL Client" section.
•To add new security tokens, see "Configuring the Cisco CTL Client" section.
•To delete a security token, see the "Deleting a CTL File Entry" section.
Tip If you are prompted to change the security token password, see the "Troubleshooting" section on page 9-1.
Related Topics
•Cisco CTL Client Configuration Settings
•System Requirements, page 1-4
•Interactions and Restrictions, page 1-5
•Activating the Cisco CTL Provider Service
•Setting the Smart Card Service to Started and Automatic, page 9-11
•Activating the Cisco CTL Provider Service
•Configuring the Cisco CTL Client
•Updating the CTL File
•Configuring the Device Security Mode, page 5-6
•Troubleshooting, page 9-1
Updating the Clusterwide Security Mode
You must use the Cisco CTL client to configure the clusterwide security mode. You cannot change the clusterwide security mode from the Enterprise Parameters window of Cisco CallManager Administration.
To change the clusterwide security mode after the initial configuration of the Cisco CTL client, you must update the CTL file, as described in the "Updating the CTL File" section and Table 3-2. If you change the clusterwide security mode from mixed to nonsecure mode, the CTL file still exists on the servers in the cluster, but the CTL file does not contain any certificates. Because no certificates exist in the CTL file, the phone requests an unsigned configuration file and registers as nonsecure with Cisco CallManager.
Related Topics
•Updating the CTL File
•Cisco CTL Client Configuration Settings
•Troubleshooting, page 9-1
Cisco CTL Client Configuration Settings
The cluster can exist in one of two modes, as described in Table 3-2. Only mixed mode supports authentication. When you configure the Cisco CTL client for authentication, you must choose Set CallManager Cluster to Mixed Mode.
Use Table 3-2 to configure the Cisco CTL client for the first time, to update the CTL file, or to change the mode from mixed to nonsecure.
Table 3-2 Configuration Settings for CTL Client
Setting
|
Description
|
CallManager Server
|
Hostname or IP Address
|
Enter the hostname or IP address for a server in the cluster that runs the Cisco CallManager or Cisco TFTP service.
|
Port
|
Enter the port number, which equals the CTL port for the Cisco CTL Provider service that runs on the specified Cisco CallManager server. The default port number equals 2444.
|
Username and Password
|
Enter a username and password that has administrative privileges on the Cisco CallManager server.
Tip Verify that you entered the username and password for the Cisco CallManager administrator or Power User account. The same username and password must exist on all servers in the cluster.
|
Radio Button
|
Set CallManager Cluster to Mixed Mode
|
Mixed mode allows authenticated or encrypted Cisco IP Phones and nonauthenticated Cisco IP Phones to register with Cisco CallManager. In this mode, Cisco CallManager ensures that authenticated or encrypted devices use a secure SCCP port.
Note Cisco CallManager disables auto-registration if you configure the cluster for mixed mode.
|
Set CallManager Cluster to Non-Secure Mode
|
All devices register as unauthenticated with Cisco CallManager, and Cisco CallManager supports image authentication only.
When you choose this mode, the CTL client removes the certificates for all entries that are listed in the CTL file, but the CTL file still exists in the directory that you specified. The phone requests unsigned configuration files and registers as nonsecure with Cisco CallManager.
Tip To revert the phone to the default nonsecure mode, you must delete the CTL file from the phone and all Cisco CallManager servers. For information on deleting the CTL file from the phone and Cisco CallManager servers, see the "Troubleshooting" section on page 9-1.
Tip You can use auto-registration in this mode.
|
Update CTL File
|
After you have created the CTL file, you must choose this option to make any changes to the CTL file. Choosing this option ensures that the Cluster Security mode does not change.
|
Alternate TFTP Server
|
Hostname or IP Address
|
Note Alternate TFTP server designates a Cisco TFTP server that exists in a different cluster. If you use two different clusters for the alternate TFTP server configuration, both clusters must use the same clusterwide security mode, which means that you must install and configure the Cisco CTL client in both clusters. Likewise, both clusters must run the same version of Cisco CallManager.
Caution Ensure that the path in the TFTP service parameter, FileLocation, is the same for all servers in the cluster.
Enter the hostname or IP address for the TFTP server.
|
Port
|
Enter the port number, which equals the CTL port for the Cisco CTL Provider service that runs on the specified TFTP server. The default port number equals 2444.
|
Username and Password
|
Enter a username and password that have local administrative privileges on the server.
|
Security Token
|
User Password
|
The first time that you configure the Cisco CTL client, enter Cisco123, the case-sensitive default password, to retrieve the private key of the certificate and ensure that the CTL file gets signed.
|
Related Topics
•System Requirements, page 1-4
•Interactions and Restrictions, page 1-5
•Activating the Cisco CTL Provider Service
•Activating the Cisco CTL Provider Service
•Installing the Cisco CTL Client
•Configuring the Cisco CTL Client
•Updating the CTL File
•Configuring the Device Security Mode, page 5-6
•Troubleshooting, page 9-1
Deleting a CTL File Entry
At any time, you can delete some CTL entries that display in the CTL Entries window of the Cisco CTL client. After you open the client and follow the prompts to display the CTL Entries window, click Delete Selected to delete the entry.
From the CTL file, you cannot delete servers that run Cisco CallManager, Cisco TFTP, or Cisco CAPF. You can delete alternate TFTP servers and security tokens that you manually add to the CTL file, but you cannot delete TFTP servers that the client automatically detects.
Two security token entries must exist in the CTL file at all times. You cannot delete all security tokens from the file.
Tip For information on uninstalling the Cisco CTL client, deleting the CTL file from the phone, or deleting the CTL file from the server, see the "Troubleshooting the Cisco CTL Client" section on page 9-8.
Related Topics
•System Requirements, page 1-4
•Interactions and Restrictions, page 1-5
•Activating the Cisco CTL Provider Service
•Installing the Cisco CTL Client
•Configuring the Cisco CTL Client
•Updating the CTL File
•Configuring the Device Security Mode, page 5-6
•Troubleshooting, page 9-1
Feedback
