![]() |
Conference Service logging is configured in SametimeDiagnostics_Telephony.properties in the Domino directory. To get more information about what is happening inside the Conference Service, you can configure the logging level of any of the classes listed below by adding a line at bottom of SametimeDiagnostics_Telephony.properties. The log file is Domino\Trace\telephony_0.log. Please note that you can change the logging level of any class in the Conference Service without restarting the Sametime server. The Sametime process that the Conference Service runs within will re-read SametimeDiagnostics_Telephony.properties and rotate the log file for you. (It might take a few minutes for it to do so.) Almost all of the (Avaya) entries in a Conference Service log file will begin with the conference ID, which looks like “CONF-#N” (where N is the conference number). You can use this identifier to trace the activity associated with the given conference.
The classes in the tcspi package are the highest-level classes in the Conference Service. In fact, the Conference Service class itself is the class to which the Sametime Server issues its telephony instructions (e.g. make phone A call phone B). Increasing the logging level of these two classes to FINEST will cause those instructions to be logged.
com.avaya.sametime.click2call.tcspi.ConferenceService com.avaya.sametime.click2call.tcspi.ConferenceController
Below the tcspi package, there are four fundamental classes, one each for the notions of conference (or call), moderator, participant, and cache. PBXConferenceImpl knows the state of the conference (i.e. who's connecting, connected, or disconnected) and moves participants (including the moderator) from one state to the next. ModeratorImpl is responsible for making calls and setting up conferences using the moderator's device. ParticipantImpl's job is rather minimal. CacheImpl and Click2CallCacheImpl gets phone numbers from the LDAP server, converts E.164 numbers to diallable numbers, and keeps a cache of this information.
com.avaya.sametime.click2call.impl.PBXConferenceImpl com.avaya.sametime.click2call.impl.ModeratorImpl com.avaya.sametime.click2call.impl.ParticipantImpl com.avaya.sametime.common.impl.Click2CallCacheImpl com.avaya.sametime.common.impl.CacheImpl
Next on the list are the requests that the Conference Service sends to AE Services. Each request is represented by a class which is responsible for building the request. The request is built immediately before being sent to AE Services by the SendRequest class.
com.avaya.sametime.click2call.impl.SendRequest com.avaya.sametime.click2call.impl.ClearConnectionBuilder com.avaya.sametime.click2call.impl.ConsultationCallBuilder com.avaya.sametime.click2call.impl.ConferenceCallBuilder com.avaya.sametime.click2call.impl.MakeCallBuilder com.avaya.sametime.click2call.impl.ReconnectCallBuilder
Similarly, each response from AE Services -- whether successful or failed -- is handled by a class.
com.avaya.sametime.click2call.impl.ClearConnectionCallback com.avaya.sametime.click2call.impl.ConsultationCallCallback com.avaya.sametime.click2call.impl.ConferenceCallCallback com.avaya.sametime.click2call.impl.ConsultationCallCallback com.avaya.sametime.click2call.impl.MakeCallCallback com.avaya.sametime.click2call.impl.ReconnectCallCallback
Finally, the call control listener classes respond to the events that AE Services sends to the Conference Service. CallControlListenerDelegateImpl logs at the FINEST level the fact that it has received an event, then forwards the event to either the moderator or the participant (or, in special cases, both). The moderator and participant listener classes log exactly how they respond to the event.
com.avaya.sametime.click2call.impl.ModeratorCallControlListener com.avaya.sametime.click2call.impl.ParticipantCallControlListener com.avaya.sametime.common.impl.CallControlListenerDelegateImpl (called DefaultCallControlListenerDelegate in beta release)