![]() |
Use this procedure to test a configuration of the AE Services Integration for IBM Lotus Sametime.
For Windows: Open a terminal and, in .\telephony_ext\AES\presence\bin (Community server) or \sametime_tcspi\AES\presence\bin (Media Manager) or .\presence_service\AES\presence\bin (Standalone Presence Services), run wrapper.exe wrapper.conf. This will run the Telephony Presence Services in the foreground. The log level can be controlled via logging.properties in .\telephony_ext\AES\resources (Community server) or .\sametime_tcspi\AES\resources (Media Manager) or .\sametime_tcspi\AES\resources (Standalone Presence Services). (Note: If you rebooted the Domino server after installing the Telephony Presence Services, it will already be running as a service. Go to the Windows Service Controller and stop the service before performing this step.)
For Linux: Open a terminal and navigate to /telephony_ext/AES/presence/bin and run /wrapper. This will run the Telephony Presence Services in the foreground. The log level can be controlled via logging.properties in /telephony_ext/AES/resources (Community Server) or /sametime_tcspi/AES/resources (Media Manager) or /presence_service/AES/resources (Standalone Presence Services. (Note: If you rebooted the Domino server after installing the Telephony Presence Services, it will already be running as a service. From root, run /sbin/service presence-service stop.)
If you do not see that user's phone icon go off hook after placing the call, then the Telephony Presence Services is not functioning correctly. Increase the logging level if there are not any obvious errors in .\telephony_ext\AES\presence\logs\presence.log.0 (Community server) or .\sametime_tcspi\AES\presence\logs\presence.log.0 (Media Manager) or .\presence_service\AES\presence\logs\presence.log.0 (Standalone Presence Services). (Note: ignore the exceptions about not finding the files in the mapping directory.) When the Telephony Presence Services is initialized successfully, you will see the message The presence service is starting. followed some lines later by The presence service started. in presence.log. Otherwise you will see the message The presence service failed to start.
For Windows, go to the Windows Service Controller, and start the Presence Services.
For Linux, run /sbin/service presence-service start.
If the call does not succeed, there may be a configuration problem with the Conference Service or the LDAP store. Look at Trace\telephony_0.log for errors. The logging level for click-to-call is controlled via SametimeDiagnostics_Telephony.properties in the Domino directory. When the Conference Service is initialized successfully, you will see the message The conference service is starting. followed some lines later by The conference service started. in telephony_0.log. Otherwise you will see the message The conference service failed to start.
Comments on this document? | May 2018 | © 2016-2018, Avaya Inc. All Rights Reserved. |