TMS reports no Https respnse from the VCS. The VCS has the ip address of the TMS as the external manager, The connection shows active over HTTP to the TMS. I've enabled self-signed certificates on the TMS using the https tool, but can not figure out what else I can do to clear this up.
The are 2 very common causes for no https responce. One is the use of a proxy server:
To follow up with what Artem posted, the bitsadmin utility is built into Windows Server 2008. If you are running Windows Server 2003, you will need to download the Windows Server 2003 Service Pack 2 32-bit Support Tools:
Run the command prompt by right-clicking it and select "run as administrator". There are three commands you will need to run:
bitsadmin /util /getieproxy localsystem
bitsadmin /util /getieproxy localservice
bitsadmin /util /getieproxy networkservice
If you receive "AUTO" as a response, run the command:
The "AUTO" setting sets Windows to do a DNS resoltuion for wpad. Besure *NOT* to do the FQDN including your DNS domain. Windows will auto-append its known DNS domains to wpad. If wpad returns a response that resolves to a proxy server, or if bitsadmin returns a manually configured list, verify if the TMS services need to use a proxy server to managed its registered devices. If i does not, run the following command to clear the proxy settings:
If the TMS server does require the use of a proxy server to manage its endpoints, besure that the proxy configuration allows a bypass for those devices that TMS does not need to use a proxy for. Also, besure that the proxy server does not require authentication for the TMS services to access the devices it needs to use a proxy for. Keep in mind that proxy settings could be getting applied via Active Directory Group Policies. If this is the case, you will need to work with the AD Administrators to verify tha tthe correct settings are applied to the TMS server.
The second most common cause is having FIPS enabled on the TMS server. To verify the FIPS settings, on the Windows Server, open Administrative Tools > Local Securoty Policy
Go to: Securoty Settings > Local Policies > Security Options > System cryptography: USE FIPS compliant algoriths for encryption, hashing, and signing
If this is enabled, please disable it. This setting could also be getting pushed down through AD GPO. As stated above, you may need the assitance with your AD Admins to make this change.
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...