We are having MCS 7845 and CCM 4.1 ..i want to check all licence and product detail through Cisco. so how it's ckeck ? actually we are not having any document for server and CCM 4.1, before that nobody mentain document ..i want now made all recored details ??please help me
This is actually an excellent question :) With the release of CUCM 5.x the licensing model has completly changed. For all 3.x and 4.x versions the CH-1 (Channel)Phone License was used and was really totally "honor" based. There was no License actually loaded "on-box" so this is why you can't find any references to them :) Now phones use DLU's (Device License Units)which are loaded on the CUCM First Node or Publisher server. The "Station License" has been replaced with the DLU (Device License Unit) in CCM 5.x and above, also the new model includes "Node and Software Feature" Licenses;
Thanks for reply but how can i prove the my server MCS and CCM 4.1 has support 7500 ip Phone is there any way to show that this server and sofware support 7500 ip phone ...it is ok that we are having white paper and othere document on cisco site but in server and software how it's poosible please help me...
You will not find this information on the CCM 4.x server, and you don't really need to. If/when you upgrade to a newer Communications manager version like 7.x the migration process will identify the registered IP Phones on your current boxes and generate a new License that will be registered with Cisco for you to move forward.
i cant upgrate any newer communication right now first we have to finished all with this version after that i can recommended newer version so please any solution only for this version...which is better to help me
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.