It's not a tomcat-trust cert though, the docs (and expressway) say it needs
to go in the callmanager-trust
On Thu, May 28, 2015 at 10:25 AM, Charles Goldsmith wo...@justfamily.org
wrote:
Just restart Tomcat
On Thu, May 28, 2015 at 8:21 AM, Ed Leatherman ealeather...@gmail.com
wrote:
Good
Good morning!
Cert related question - think I know the answer but I dont see it
explicitly stated so figured I'd ask.
I need to add the CA cert for my expressway-C to call manager as a
callmanager-trust cert - do I need to reboot the call manager service for
this to take effect? No forced phone
Just restart Tomcat
On Thu, May 28, 2015 at 8:21 AM, Ed Leatherman ealeather...@gmail.com
wrote:
Good morning!
Cert related question - think I know the answer but I dont see it
explicitly stated so figured I'd ask.
I need to add the CA cert for my expressway-C to call manager as a
I'm sorry, I read your email too quickly, and you are probably correct.
I've only done 3rd party certs so far with MRA, so I've only had to restart
Tomcat with UCM.
On Thu, May 28, 2015 at 8:37 AM, Ed Leatherman ealeather...@gmail.com
wrote:
It's not a tomcat-trust cert though, the docs (and
I've seen it work most of the time just adding the CallManager-trust. On
one occasion, I did have to restart the CallManager service for it to take
affect. Make sure to upload to every node.
You also shouldn't see any phone reboots for adding a CallManager-trust.
That would only be in the case
Brian, since it's a trust cert you shouldn't need to upload it to every
node. The certificate replication process I talked about previously in this
thread handles putting the trust cert on all CUCM servers. Also - since
it's a trust cert you're right - no resets of phones anywhere.
Since this is
Looks like I need to get my Tomcat certs signed before I can test this out
after all.. the CN for the tomcat and callmanager certs (self-signed) right
now on my cluster are the same and expressway won't setup the initial
connection.
The good news is I can get our internal CA to sign them which is
Ed,
All phones re-registering is expected behavior for when any CallManager,
CAPF, or TVS certificate on any node in the cluster is regenerated. This
is to allow phones to download an updated ITL before another certificate
change is made. This is also the same reason all phones re-register when
Ed.
All changes that cause an ITL file to update, such as regenerating
certain certificates or changing host or domain names (which cause cert
regens themselves) cause an Enterprise Phone Reset. Changing names
(certs) on multiple CUCM servers causes multiple enterprise resets. This
is by design
Good morning,
This morning I enabled DNS servers, domain name on our CUCM Cluster, which
involved regenerating all the certs on the cluster. Note I have cluster
mixed mode. Everything appears to have gone smoothly, but I had 2 odd
things happen that I did not expect.. tossing them out here in
10 matches
Mail list logo
