10-05-2016 01:14 PM - edited 03-19-2019 11:39 AM
Hi,
I have upgraded Expressway C&E from 8.2 to 8.8.2 (the latest). After upgrade the Expressway has a connection with the CUCM, but not anymore with IMP. In the GUI from Expressway-C and checking the "IMP and Presence nodes" I see the status
Inactive: (Remote host is reachable but connection is not established. Either refresh this page, or check the credentials.)
I have deleted the node and added it again, but each time I see this message. When I give a wrong password I get the message wrong password, so some communication is established.
Anyone has seen this?
CUCM version 11.5.1.11900-26
IMP version 11.5.1.11900-21
Any help would be apreciated
JH
10-05-2016 11:48 PM
Hi JH,
In version 8.8, there is a new module cvs.verifier which is doing more struct checks on the certificate. In order to discover successfully a CUCM/IM&P cluster when using self signed certificates, certificate of each node of the cluster MUST be added to the trust store of Expressway. If there is one missing certificate, discovery will fail for all nodes.
You may verify this and see if it helps.
Manish
10-06-2016 12:41 AM
Hello Manish,
I downloaded the tomcat certificate from the IMP server and uploaded it to the trusted store of Expressway-C. From the log-files from Expressway-C I can see there is an issue with the certificate, some messages regarding "handshake"
The issue is that the CUCM is discovered correctly
Maybe a regenerate of the IMP certificate?
Tanks!
Jan
10-25-2016 02:52 PM
Hi ,,
I have the same exact issue, any update regarding this please.
10-25-2016 11:23 PM
we execute the following command on Expressway-C
xConfiguration XCP TLS Certificate CVS EnableCvs: Off
No idea what it does, but it solved the problem
06-13-2019 11:23 AM
Thanks, It Worked for me.
11-02-2020 01:05 PM
As a workaround you can disable reverse DNS verification running the command on both Exp-E and Exp-C:
xConfiguration XCP TLS Certificate CVS EnableCvs: Off
03-16-2017 03:50 AM
The issue was resolved when I added the XMPP certificate of the IMP on the expressway
12-09-2016 07:35 AM
As to add to this topic: i was seeing the same behaviour after having upgraded the IM&P node from 10.5.1 to 10.5.2.24900-8 (while using X8.8.3 on Expressway-C/E)
Restarting the XCP Router services on the IM&P node resolved the matter for me.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide