cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements
Walkthrough Wednesdays
4356
Views
5
Helpful
10
Replies
Pietro Corti
Beginner

Expressway-C Provisioning server error

Hi, I have a problem with Expressway x8.7 and CUCM 10.5.2.

All works fine but (apparently random) i have the error show on image.

The MRA client can't connect.

Reboot the expressway fix the issue ..

Also I found the message :

edgeconfigprovisioning: Level="ERROR" Service="UDSManager" Detail="UDS get version request failed" UDS=10.10.31.212" Reason="[<twisted.python.failure.Failure <class 'OpenSSL.SSL.Error'>>]" UTCTime="2015-12-03 07:20:42,379" 
edgeconfigprovisioning: Level="ERROR" Detail="Certificate chain verify failure" State="None" Error="18: self signed certificate" Depth="0" UTCTime="2015-12-03 07:20:42,378" 

On VCS I have imported the tomcat CUCM self signed certificate.

Previous of CUCM 10.5.2 upgrade there was no preblem.

Thanks a lot

Pietro

10 REPLIES 10
Md Hasan
Cisco Employee

Please check the white list of VCS-C or the firewall port open for TCP 8443 toward cucm pub

For IM&P the port will be TCP 8443, 5222, other ports are needed but these are basics port needed to be opened

All the ports are open, and after reboot expressway-c the UC registration is correct for some time.

Gents,

Any update as how this error was resolved ?

Regards,

Raaj

heathrw
Enthusiast

You mentioned upgrading to 10.5.2 was the the Expressway also upgraded?

Did you try and delete and re-import the certificates?

I have delete CUCM Tomcat self signed certificates and import the new one from CUCM 10.5.2.

Reboot expressway and all works fine when it restart, but the error still come back after some time(random time).

Can you downgrade 8.7 the previous release that was working. Since UCM has also been upgraded would be good to know if the issue still occurs when Exp is earlier version.

The issue is not related ti expressway release but to CUCM from 10.1 to 10.5.2 ( I can't downgrade CUCM).

I just try expressway 8.5.2 and 8.6 with same problem.

Strange thing that after reboot expressway c all works fine for some random time.

You generated the tomcat MultiSAN cert accross all hosts and restarted tomcat?

I understand this has worked for you in the past but a more supported method would be to have a CA sign all the certifiates (internal or public).

mneira099
Beginner

Hi Pietro, 

Did you get this issue solved?

I'm having the same problem...

Hi,

problem fix yesterday.

Please check nslookup on both vcs-c and vcs-e (Maintenance - Tools - Networks utilities - DNS lookup)

On vcs-c the fqdn of vcs-e need to be only on internal interface (not both).

For a mistake of IT team there was a wrong DNS entry that resolve expressway-e fqdn on both internal and external interface.

Pietro

Content for Community-Ad

Spotlight Awards 2021