We have upgraded our Cluster to 11.5 and have discovered some issues with the bosh certificate, with different browsers. If I browse to the :7335/httpbinding url in chrome it attempts to utilize the cup-xmpp-ECDSA certificate which is self signed. If I go to the same url within IE it uses the original CA signed certificate. The reason I have started looking into this is we have a user that attempting to utilize a embrava light for jabber on a Mac but is having issues. This was never utilized until after the upgrade to 11.5 so I don't know if it would have worked prior, would a CA signed certificate to replace cup-xmpp-ECDSA resolve the issue? Has anyone else experienced issues similar?
Actually I am not completely sure that the application is using the EC certificate, but I have verified that chrome will utilize that by browsing the bosh url, IE will utilize the "normal" certificate. Maybe I am assuming to much with the browser results but it seems to correlate to the issue, that the OS/application doesn't trust the self signed certificate.
I am going generate a CSR for the EC certificate and have it signed with our CA and see if the results are different. Thanks for the information, I will update the thread with the results...
I know this a little old but we just updated our IMPS to 11.5 and have a few MACs with Embrava. What we ended up doing was trusting the EC cert after creating a cname in our DNS with the <imserver>-ec.<domain> to our imps server.
You may not need the cname and just need to trust the cert but we did the cname first.
Sucedia que un Supervisor via Finesse necesitaba ingresar a una llamada activa de un Agente, función que se denomina Silent Monitoring, Monitoreo Silencioso.
Cuando queria el Supervisor ingresar por esta funcion salio este error:
Adjunto un documento que muestra a grandes rasgos el procedimiento que le permite a un usuario final acceder al manejo de sus correos de voz usando su Navegador Web.
El componente utilizado fue el Cisco Unity Co...
Luego de un Upgrade de CUCM, version 9.1 a version 11.5, el servicio Extension Mobility Cross Cluster (EMCC) produce falla en IP Phones, ejemplo Cisco 7940.
La falla es que al intentar acceder al servicio de EMCC se ve un mensaje de error en la p...