![]() |
This topic describes the currently-known issues for the AE Services Integration for IBM® Sametime®.
When using the Extend to Cellular feature of Avaya Communication Manager, if a called party answers on their mobile device, the fact that the user is on a call is not reflected in their Sametime telephony presence. This is a consequence of the fact that the Presence Services monitors the Avaya device for presence events, but picking up on a mobile device causes the event to occur elsewhere.
By design, the AE Services Integration for IBM® Sametime® does not support Sametime Web Conferencing. Any attempt to schedule a Sametime Web Conference using the AE Services Sametime Conference Service will not succeed.
The Alert Me When feature of Sametime Connect does not work with telephony presence.
Starting or restarting the Presence Services during business hours results in the Presence Services competing with the Conference Service for resources on the AE Services server. It is advised that the administrator start or restart the Presence Services after business hours only, in order to provide the best response time to the users of the Conference Service (i.e., Sametime Connect users making phone calls).
When making a trunk call, the amount of signaling information available about the state of the call (such as ringing and answered) can be limited. Depending on the type of the trunk, this can result in incorrect state appearing in a Sametime Connect call window. This will happen if the trunk is an analog trunk. For example, a user can appear in the Connecting state even after they answered the call. Another manifestation of this phenomenon occurs when a user selects multiple parties in their Sametime Connect contacts list and calls them simultaneously; if the first called party is a trunk call, subsequent participants may not be conferenced into the call.
The Telephony Services Application Programming Interface (TSAPI) switch links used by the AE Services IBM® Sametime®Integration must have lowercase names. That is, when you administer a switch connection in AE Services (Administration > Switch Connections), the connection name must use lowercase characters.
If the TSAPI link goes down or Communication Manager is rebooted, the device monitors created by thePresence Services and Conference Service are lost and not re-added. Restarting either AE Services or both the Presence Services and Conference Service will fix the problem.
When you are running the configurator.bat file and configuring more than one AE Services server, the configurator.bat file will generate exception messages. This is not service affecting. Continue the configuration and save the changes.