Cannot establish WSS connection
Issue 1:
The following message is displayed at console log when SIP registration is sent from a SIP UA on the Chrome browser:
WebSocket connection to 'wss://[SIP server]:[WSS port]/' failed: [error details]
Solution 1:
Take an appropriate action from the table below based on the error details in the error message shown at the console log.
| Error details | Solution |
| Error in connection establishment: net::ERR_CONNECTION_TIMED_OUT | Check to see if there are any barriers, like a firewall, between SIP UA and WSS port of SIP server. |
| Error in connection establishment: net::ERR_CONNECTION_CLOSED
or Error in connection establishment: net::ERR_CONNECTION_ABORTED |
Check to see if the IP address is on the [Block List] settings of the SIP server. |
| Error in connection establishment: net::ERR_CERT_COMMON_NAME_INVALID | Check to see if the certification’s “Common Name” or “Subject Alternative Names” match SIP server’s domain. |
| Error in connection establishment: net::ERR_CERT_DATE_INVALID | Check to see if certification has expired. |
| Error in connection establishment: net::ERR_CERT_AUTHORITY_INVALID | Check to see if the certification has been issued by a trusted organization.
Or
Check to see if the certification has been replaced by a third-party, like a proxy, that exists in between. |
| WebSocket opening handshake was canceled | Make sure to use the same certification at Tomcat and SIP server. |
| Error in connection establishment: net::ERR_SSL_WEAK_EPHEMERAL_DH_KEY | Refer to the section: Connection error at http/WSS (ERR_SSL_WEAK_EPHEMERAL_DH_KEY). |
Issue 2:
The following message is displayed at console log when SIP registration is sent from a SIP UA from Firefox browser (there is no problem when Chrome browser is used) and unauthenticated certification at the SIP server:
Connection to 'wss://[SIP server]:[WSS port]/' failed.
Solution 2:
When Firefox browser is used, it is necessary to add exceptions for both https port and WSS port.