Hi Kevin,
There is a defect tracking this: CSCva68233, and we hope to fix this in 11.6.
Once done, we can evaluate if it can be back ported. Could you share the TAC
case number so that I can add a note in the case?
Regards,
Abhiram Kramadhati
Technical Solutions Manager, CCBU
CCIE Collaboration
Keep in mind you also need to upload the certificate authority's certificate
into the cluster's trust store (regardless if the certificate is signed by a
public or internal authority).
Additionally, the end-user device would have to trust the CA that signed the
server's identity certificate. If
awesome info, thank you! I'm pretty sure our gateways have DNS, but I'll be
making sure... and I've dealt with enough dbreplication issues lately that
I'll be vigilant on that as well. It may take me 8 hours to do it that way
though blech. I just had to do a cluster reboot earlier this week and
Thanks Ryan. Yes, I'm just trying to change the process node names. Right
now, when someone logs in with cucilync, it prompts them for several
certificates. Those certs are references a CN that is an IP address. I'm
thinking that if I change the node name to an FQDN, and assuming I have my
cert cha
One of the most important points that people tend to forget when changing the
processnode (System>Server) entries is that MGCP and SCCP gateways will
download a config file (like a phone) and will need to resolve these entries.
For what ever reason I've seen so many customers not add any ip name
Nick,
If the UC servers already have DNS entries (means they already have a domain
name too); then the servers are already using FQDNs, at least for internal
referencing. If you're saying the you want to change the processNode names (the
CM Server references) then as long as the FQDNs are reso
We are on 10.0 and this cluster has been upgraded over the years from 8.0
to 8.6 to 10.0. I know it used to be common practice to rip the host name
out of a new node and put in the IP address. That's how we are set up...
but now that I need to do some work with certs so that jabber and cucilync
wo
LBM is part of the new enhanced locations CAC feature. Combined with the
transition of locations from a fixed hub & spoke model to locations & links It
moves bandwidth allocation outside of the ccm process and allows multiple
clusters to run on the same network and exchange bandwidth allocation
Customer is running UCCX 10.6(1). We have some "HTTP Request" actions within a
Finesse workflow that points to one of the customer's internal web servers.
Looking at the packet capture taken from UCCX when this workflow runs, we can
see UCCX sending the https request with a TLS 1.0 hello packe
