Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hello,I've upgraded a Call Manager cluster in my lab from 11.5.1 to 14 (SU3). This is a simple cluster of 3 nodes. This is a classified gov't system so I'm unable to post screenshots. I apologize for that. I also do not have access to RTMT.The Publis...
Hi all,I have a lab environment with a cluster of one Pub and two Subs. A couple of 8841 phones and 7975G phones.The 8841 phones and one 7975G phone can access the Corporate directory and User Preferences such as wallpapers and ringtones. All of the ...
Hello all,My Google-Fu seems weak today. My customer would like to know which version and flavor of Linux that Call Manager 14 is based on? I see that v12 is CentOS but I'd really like to know the specifics for v14.I appreciate the help.Rich A.
Hello, I have purchased 20 SMART licenses for my lab environment. The lab and production environment are isolated, government systems so I'm converting the license to SLR's. I have obtained the CSSM authorization code and input it into the CUCM CLI, ...
Question:We have an isolated, classified government Call Manager Cluster running 14.0.1(SU2). We have successfully created an SLR request and obtained the authorization code from Cisco TAC.In the event of a catastrophic loss of data that forces us to...
Hi TLC910,It turns out that my problem was that several of the certificates in my labCall Manager had expired. I went through each node and updated/recreatedthem until everything was within periodicity. The upgrade proceedednormally on the next attem...
I have now run the standard set of commands for resetting the database from scratch. The process just completed and <utils dbreplication runstimestate> has returned the same results: Publisher: (0) Setup CompletedSubscribers: (-) Out Of Sync
The output of utils dbreplication status is:checked 754 tables out of 754 tables No Errors os Mismatches found.SERVER ID STATE STATUS QUEUE CONNECTION CHANGEDg_2_ccm14...
Hey Roger,This was the fix. I would have sworn that the cluster was starting at TLS v1.1 so that was what I regressed back to, but obviously I was suffering from a faulty memory. Reverting back to TLS v1.0 cleared the problem.As an aside, in all of t...
I should clarify:In the lab, I upgraded the cluster from 11.5.1 to 14.0.1(SU2) on TLS v1.1. All phones worked normally.I then was directed to implement TLS v1.2. I made a few test calls successfully but did not check ALL features of ALL phones.A coup...
