MiCollab Client - WSP Service

[bribob]

vMiCollab 6.0.41.0
MiCollab Client 6.0.327.0

Freshly integrated MiCollab Client DB with USP DB. The desktop client will connect briefly before showing 'Connection Lost'. The desktop client's uca.log has these entries repeating multiple times:

2015/05/29 13:06:59.695 TRACE [8:] Mitel.Communicator.Listeners.OfflineStateListener - Setting client connection state: Reconnecting.
2015/05/29 13:06:59.695 WARN [8:] Mitel.Communicator.Listeners.OfflineStateListener - Attempting to reconnect the WSP socket.
2015/05/29 13:06:59.697 INFO [1:MainThread] Mitel.Communicator.Listeners.WebSocketListener - Web socket (session ID: 5e10adbf-c6af-47ef-8f6d-4d3f2edab8a4) is trying to connect to wss://HOSTNAME.DOMAIN.COM:36008/ with state None
2015/05/29 13:06:59.697 INFO [1:MainThread] Mitel.Communicator.Listeners.WebSocketListener - Setting the WSP socket state to Connecting because of connecting.
2015/05/29 13:07:06.447 ERROR [38:] Mitel.Communicator.Listeners.WebSocketListener - Web socket error: System.Exception: RemoteCertificateNameMismatch
2015/05/29 13:07:06.447 INFO [38:] Mitel.Communicator.Listeners.WebSocketListener - Closing the web socket (None) because web socket has error.
2015/05/29 13:07:06.447 INFO [38:] Mitel.Communicator.Listeners.WebSocketListener - Setting the WSP socket state to ConnectionLost because of System.Exception: RemoteCertificateNameMismatch.
2015/05/29 13:07:06.447 TRACE [1:MainThread] Mitel.Communicator.Listeners.OfflineStateListener - WSP socket connection state changed: ConnectionLost.
2015/05/29 13:07:06.447 ERROR [38:] Mitel.Communicator.Listeners.WebSocketListener - Web socket error: System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure.
at System.Net.Security.SslState.InternalEndProcessAuthentication(LazyAsyncResult lazyResult)
at System.Net.Security.SslState.EndProcessAuthentication(IAsyncResult result)
at System.Net.Security.SslStream.EndAuthenticateAsClient(IAsyncResult asyncResult)
at SuperSocket.ClientEngine.SslStreamTcpSession.OnAuthenticated(IAsyncResult result)
2015/05/29 13:07:06.452 INFO [38:] Mitel.Communicator.Listeners.WebSocketListener - Setting the WSP socket state to ConnectionLost because of System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure.
at System.Net.Security.SslState.InternalEndProcessAuthentication(LazyAsyncResult lazyResult)
at System.Net.Security.SslState.EndProcessAuthentication(IAsyncResult result)
at System.Net.Security.SslStream.EndAuthenticateAsClient(IAsyncResult asyncResult)
at SuperSocket.ClientEngine.SslStreamTcpSession.OnAuthenticated(IAsyncResult result).
2015/05/29 13:07:06.452 TRACE [1:MainThread] Mitel.Communicator.Listeners.OfflineStateListener - WSP socket connection state changed: ConnectionLost.
2015/05/29 13:07:06.497 TRACE [8:] Mitel.Communicator.Listeners.OfflineStateListener - Setting client connection state: WaitingForReconnect.​

HOSTNAME is the actual name of the server and the DOMAIN.COM certificate is valid. I had played with the UCA client on this particular server [when it was MAS 5.0] some time ago when the server name and domain did not match the current certificate, so there has been a name change since I last connected. The desktop client has been uninstalled and reinstalled. Another forum indicated that deleting the locally stored certificate would resolve this issue, but there is another plot twist.

Server Diagnostics shows this:

Can anyone shed some light on the WSP service and why it would be in an OUT_OF_SERVICE state even after restarting the MiCollab Client Service? Note that the MiCollab server has NOT been restarted, that will happen tonight after hours.


-b

 

[bribob]

And I'll follow up with what I've just done to fix the WSP service.

As this vMiCollab has MBG, I had previously configured and enabled the Application Integration settings for MiCollab Client. With this connector turned on, it would appear that the ucawebsocket will sit on port 36008 and not allow the actual MiCollab Client service to start up.

TLDR; Disabled the application connector, restarted MiCollab Client service, WSP service is IN_SERVICE.


-b

 

[jpruder]

What kind of certificate is now installed

 

[bribob]

@jpruder: Wildcard


-b