i have setup Secure SRST in a 2821 router. All configs look good so far. Except, when I update the SRST reference to Secure SRST, CM tries to update the certificate, I get an error in CM saying, TLS Socket error while trying to retrieve the certifate.
Debug credentials on the router shows the following.
I created the CA server and setup the router as a trustpoint. Even authenticated the trustpoint to the CA server. But forgot to enroll the router to the CA server in order to get the certificate. Did that and Callmanager is able to download the certificate now.
maybe you can give me a little help. I try to configure secure SRST, but can?t find any IOS for 2811 capable for that feature. I tried "advanced enterprise services 12.4.11T - it is also missing the "credentials" command in global config...
Yes, I had set up the CA-Server in IOS and also enrolled the router itself to that CA. The problem was, I had no credentials-server, so CCM could not connect to port 2445 and catch the certificate. Wrong IOS! (If you don?t need that stick for you any longer, maybe you can send it over to me...)
I now found an IOS with that feature in it. But still the phones say TLS error when trying to register at secure SRST. How can I find out, what type of phone needs what .0-file from CCM. I pasted three of them to trustpoints. Do I need them all?
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...
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 discusses the bas...