Adobe Connect Support Blog

August 1, 2015 /General /

Troubleshooting On-premise Telephony SSL Handshake

The inability to save an audio profile is sometimes caused by a failure of the the ssl connection. Here is an example of a pop-up generated by an ssl handshake error using a telephony adaptor:

ssltel.fw

If the ssl handshake for a telephony adaptor connection fails, check the telephonyservice.conf file in C:\Connect\9.3.1\TelephonyService\conf

Backup the file and find the System properties definitions:

# System property definitions (-D) ( 50 … 99)
wrapper.java.additional.50=-Dapplication.home=..\TelephonyService
wrapper.java.additional.51=-Djava.endorsed.dirs=..\tomcat\bin
wrapper.java.additional.52=-Dcatalina.base=.
wrapper.java.additional.53=-Dcatalina.home=..\tomcat
wrapper.java.additional.54=-Djava.io.tmpdir=.\temp
wrapper.java.additional.55=-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
wrapper.java.additional.56=-Djava.util.logging.config.file=..\tomcat\conf\logging.properties
wrapper.java.additional.57=-Dlibrary.service=WIN32

Add a line if needed:

wrapper.java.additional.58=-Djavax.net.debug=ssl:handshake

Save and restart the Adobe Connect Telephony service.

telephsvc.fw

In this example case an error was found in the Intercall_Adaptor.log; check the log appropriate to the adapter being used \logs\telephony\

logstelephony.fwssltel1.fw

Check the server to server connection (from the Connect server) using the URL in telephony-settings.xml in \TelephonyService\conf\ In this example:

https://iccapi.audiocontrols.net:8443/axis2/services/CCAPI?wsdl

ccapi.fw

Check the TelephonyService.keystore:

  • Connect\9.3.1\TelephonyService\cert
  • Connect\9.3.1\\jre\bin\keytool.exe

keystoredir.fw

From a command prompt (edit install directory location as required):

C:\Connect\9.3.1\jre\bin>keytool -list -v -keystore C:\Connect\9.3.1\TelephonyService\cert\TelephonyService.keystore

Check the cacerts in C:\Breeze\9.3.1\jre\lib\security\cacerts.txt

cacerdir.fw

Compare from a command prompt (edit install directory location as required):

C:\Connect\9.3.1\jre\bin>keytool -list -v -keystore C:\Breeze\9.3.1\jre\lib\security\cacerts.txt

Note: TelephonyService.keystore packaged with Connect expired on Nov 9 2013; this will be updated in version 9.6.

Check the SSL entry in the server.xml file in \Connect\9.3.1\TelephonyService\conf

<Connector port=”9443″ protocol=”HTTP/1.1″ SSLEnabled=”true”
maxThreads=”150″ scheme=”https” secure=”true”
keystoreFile=”${catalina.base}/cert/TelephonyService.keystore” keystorePass=”connect”
clientAuth=”false” sslProtocol=”TLS” URIEncoding=”UTF-8″ />

 The logs for each adaptor are depicted by name: \Connect\logs\telephony\-relevant-adaptor.xx.log

logstelephony.fw

The debug log is also often helpful: \Connect\logs\support\debug.xx.log

debuglog.fw

As is the telephony application log: \Connect\logs\support\apps\_defaultHost_\telephonyProviderTesterApp\instances\7\####\application.xx.log

teltestapplog.fw

Note: As a general rule, when sending logs to Adobe Connect Support for scrutiny of a telephony (or any server-side) issue, it is prudent to send all logs (if allowable) by truncating them to focus on the issue at hand:

  • Stop all services: FMS, FMG, Connect & Telephony
  • Rename or delete all log directories
  • Restart all services and recreate the problem being scrutinized
  • Stop all services and zip complete log directories focused on the issue at hand and provide them to the support consultant

And along those same lines, entire conf directories and custom.ini file can also will help us locate the source of problems as well:

  • C:\Connect\9.3.1\TelephonyService\conf
  • C:\Connect\9.3.1\comserv\win32\conf
  • C:\Connect\9.3.1\comserv\conf
  • \Connect\9.3.1\custom.ini
General