I have got a strange problem that I have never seen before on other versions of CallManager.
We have a new installation of CUCM 6.1. It was initially CUCM 6.0 and than, before going live, it was upgraded to 6.1. The installation consists of one Pub and one Sub. The CallManager service is activated on both servers but is running only on the Pub - on the Sub it is shown as Active but Not Running. If I start CallManager service on the Sub manually (from the Serviceability web page) it keeps running for about 30 seconds (it is show as running) and after this time it goes back to Not Running. Any idea what it could be before I open TAC case?
There are 2 units authorized and 2 units used - this looks all right. For some reason the SW Version shows 6.0 (not 6.1) but I was told it should not matter because you do not need to have a separate license for 6.0-6.1 upgrade.
I have managed to fix it. All I did was sending the "utils dbreplication repair " command from the Publisher CLI and than restarting the CallManager service on the Sub from Serviceability web page. The service has been running without errors since than and my devices have successfully re-registered to the Sub.
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 ...
This document describe how DST changes and how time changes are
implemented in DST. Daylight Saving Time (DST) is the practice of
setting the clocks forward 1 hour from standard time during the summer
months, and back again in the fall, in order to make b...