05-01-2014 06:22 PM - edited 03-18-2019 02:56 AM
I'm trying to find out the process for activating encryption keys for my Telepresence server clusters.
I know that we need the encryption license key (L-AESCDN7-K9). Do we need one per chassis, or one per blade?
Solved! Go to Solution.
05-01-2014 08:52 PM
The encryption key is installed directly to each blade/server, so you would apply the key to each one. Each blade/server has it's own key.
05-01-2014 08:52 PM
The encryption key is installed directly to each blade/server, so you would apply the key to each one. Each blade/server has it's own key.
08-21-2014 01:17 PM
Hi All,
I have installed Telepresence Server on Virtual Machine (vTS). Can anyone tell me how I can get demo activation key?
Thanks
08-21-2014 01:30 PM
I don't think the virtual TelePresence Server has a demo mode, it's either activated or not. In order to get it activated you'd have to purchase it and an appropriate number of screen licesnses.
TelePresence Server part number: R-VTS-K9
1 screen license: LIC-VTS-1SL
For more information, see the TelePresence Server data sheet.
01-27-2015 10:40 AM
Hi , i have the some question as uddinabu1.
In my case, I bought the nfr 10.x licenses but do not come any license for vts, and what I realized, I can only have conference bridge resources with the vts if the connection between the conductor and the vts is TLS which only work with encryption license. If you set TCP this will work? Is there any way to make a demo of multipoint conferences without this license?
Best Regards
01-27-2015 10:57 AM
TLS is a requirement for Conductor to work. If I'm understanding you correct you're missing the encryption key? You can get this key for $0, it's a free zero-dollar option key, contact licensing@cisco.com. Your Cisco Account Manager should be able to help or local partner you purchased the virtual TelePresence Server through as well.
Part Number: L-AES-VTS-K9
01-30-2015 03:39 AM
Hi,
This is to thank you for your help and to inform, that after all , the NFR always brought a U-VTS-BASE-PAK (that includes L-AES-VTS-K9 and L-VTS-K9) license that was what I needed, it brought there also the encryption key L-AES-VTS-K9 , which allowed me to configure TLS and put my solution working.
For the conductor, I ordered a free license to the Licensing team and they arranged me this one (LIC-CNDTR-K9).
Best Regards.
10-09-2017 11:47 AM
Hello Patrick,
I have just installed the encryption key on vts 4.4 but the conductor is saying missing encryption key.... I checked the status of the conference bridge in the conductor and it's showing encryption key not enabled.
When I checked the telepresence server, it showed media encryption enabled. I have contacted licensing @cisco.com but they say the key is correct
I also have version 4.2 and it's showing enabled on both conductor and telepresence server. Is there an encryption key issue with vts version 4.4?does it require the conductor to be upgraded?
10-10-2017 07:03 PM
What software version is Conductor running?
If TelePresence Server is running 4.2 and later while Conductor is running XC4.0 and earlier, you will see an encryption key alarm on Conductor until you upgrade to XC4.1 and later.
10-12-2017 09:32 AM
10-12-2017 09:39 AM
Hello Patrick, I noticed a new feature in conductor 4.1 called multiparty mode which could be pmp or smp. I have ts screen license 9 for two vts(though showing 4 cos of the cpu count of 8) I understand that the multiparty license manages the licenses of all the telepresence server. Does mean that with multi party license, the conductor can cascade the telepresence servers?
10-12-2017 10:44 AM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide