The LSC (Locally Significant Certificate) is required for use in phone models that support security, but do not come with a MIC (Manufacturing Installed Certificate). For example, the 7940 and 7960
Installing the LSC requires the use of at least two USB eTokens and the CTL Client, or you can follow the procedure here to be used only with the Phone Proxy feature on the ASA: https://supportforums.cisco.com/docs/DOC-12963. The CTL Client is used to generate the necessary certificates on the CallManager. Once the CTL Provider and CAPF Services are activated on the cluster, the CTL Client can be run to generate the CTL file on the CallManager. Once this process completes it is then possible to set the "Certificate Operation" on the IP Phone to "Install/Upgrade" through the CCMAdmin Interface. This process must be used for all 7940/60 and older model IP Phones. Without the USB eToken and the CTL Client there is no way to install LSCs on IP Phones *(see note). The Part number for the USB eToken is: KEY-CCM-ADMIN-K9=
With the release of CUCM 8.0 and greater some phone models download an ITL (Initial Trust List) file that contains the CAPF certificate. Only 7941/61 and greater phone models support this ITL file. See full documentation here:
When the phone has this CAPF certificate the USB eTokens are no longer required to install an LSC on the phone. Simply perform steps 1 and 13-17.
eTokens will still be required for authenticated or encrypted configuration files, but are not needed to install an LSC on the phone.
Here are the full instructions to get the LSC to the phone. These instructions assume you have not installed the CTL Client or activated any security services on Communications Manager.
In CUCM Serviceability > Service Activation activate Cisco CTL Provider and Cisco Certificate Authority Proxy Function on the publisher server
Obtain two of the previously mentioned security token: KEY-CCM-ADMIN-K9=
Install the CTL Client on a Windows PC. You can get the plugin from CUCM Administration > Application > Plugins > Cisco CTL Client
Reboot the Windows PC
Start the CTL Client and point it to the IP of your publisher server
Select "Update CTL File"
Insert the first token when prompted
When finished with the first token select "Add" again and insert the second token when instructed
Click "Finish" after the second token has been added
Restart the Cisco TFTP and then Cisco CallManager service on all nodes in the cluster
At this point on the 7960 phone GUI you should be able to navigate to Settings > (6) Security Configuration > (5) CTL File and see a long hex string
From CUCM CCMAdmin navigate to Device > Phone > pick the 7940/60 IP Phone you want to provision an LSC on
In the Device config page under Certificate Operation select > Install / Upgrade > By Authentication String > Enter your own auth string. This will need to be punched into the phone itself.
Save the phone config in CCMAdmin and select "Reset"
When the phone resets go to the physical phone and hit Settings > (6) Security Configuration > (4) LSC > **# (This operation unlocks the GUI and allows us to continue to the next step) > Update (Update will not be visible until you perform the previous step) > Enter the auth string into the phone > Hit Submit
You will see "Generating Keys." This will take a few minutes. When it completes the LSC installation has finished. This phone is now ready for use with either ASA Phone Proxy, or a Secure CallManager cluster.
I have a lab environment with CUCM 12.5 and Unity Connection 12.5 , i tried integrating with SIP as well as SCCP,Call is connecting to the Voicemail but i am unable to see MWI turning on in IP communicator as well as Jabber (Since this setup is in V...
Hey experts, i have just started learning Cisco VOIP, so i found out one of the major thing is CUCM, so can you please recommend best and easy way to learn CUCM, you can recommend any guide or anything, I would really appreciate anything, So please sugges...
Hi all, We have 7931G and 7965G phones in our network. They authenticate via CAPF signed certificates (LSC) for SIP-Secure. At present they use SHA1 signed certificates. According to this Cisco Live, both these models should support SHA2 ce...