From what I can see the default CAPF certificate on a 8.x CUCM is 1024bit signed with SHA-1. As phones can do 2048bit can I also put the the CAPF certificate to this higer security standard? In other words, can CAPF generate a 2048bit certificate signed with a more up to date SHA-2?
now 18 months later I am working through the same issue on 8.5(1).
The service paramaters let you raise the key size to 2048, but this only (appears to) affect the RSA handshake for encrypted transmission of the same old cert - with modulus of 1024 . I still can't seem to generate a .csr to pull a 2048 bit cert from our 3rd party CA.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
[toc:faq]CUCM Database Replication is an area in which Cisco customers
and partners have asked for more in-depth training in being able to
properly assess a replication problem and potentially resolve an issue
without involving TAC. This document discusse...