I would like to know the license license portability for CallManager and Subscribers in Unity.
for example if we deploy a network in San Jose with 600 users and we only deploy 400 we still have 200 license that we might use on a different site/cluster is that possible? if not what would be the best solution
With CallManager, licenses from one cluster cannot be shared with another cluster. Except for if these can be divided into 2 different license files, one for a cluster of 400 phones and another for a cluster of 200 phones. I'm not sure if this can be done or not, but you should contact your Cisco AM/SE for them to check if this can be done or not.
With Unity, if you have License Pooling enabled, then the license files can be shared across multiple Unity servers within the same AD Forest. So, if you have 2 different locations, 2 Unity servers, these Licesnes can be shared, provided the server belong to the same forest.
Got that. I think we did not understand the issue with callmanager in a 100% could you explain us what the share means. for example if we buy 1000 licenses for one cluster and then if we want to create a different cluster could we take those 500 licenses out of the 1000 and move them over to the new cluster or not
For this to be done, you would need to contact your Cisco AM/SE to know if they could do this. You cannot move the license without having a new license file generated. Also, if the licenses were already generated for 1000 users with one cluster, I dont believe Licensing team would allow the move. But to get a confirmation, contact your Cisco Rep
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: firstname.lastname@example.org Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...