Avaya Aura Collaboration Environment 2.0 Release Notes

Transcription

1 Avaya Aura Collaboration Environment 2.0 Release Notes Operational Assistance This software offers the following helpful tips and workarounds: Table1: Avaya Aura Collaboration Environment 2.0 Assistance Keywords Issue ID Reference Workaround Audit Service profile name WhiteList sample service The time elapsed since last successful audit that is displayed when there is a service audit error on instance service status page is incorrect. XML Parsing Error when attempting to navigate to the Attribute Configuration page from profile edit The WhiteList sample service sometimes redirects calls to the Redirect Number destination administered in the user s service profile even though the calling party is in the database for called party s whitelist No workaround available It is recommended that a service profile name uses only these characters: a-z, A-Z, 0-9, ".", "-", "*", and "_". Service profiles that use other characters besides the ones listed can still be edited on the Service Profile Attribute Configuration page, but instead of using the link in the service profile editor screen, they will have to be edited from the left navigation menu. Look at the asm.log file (ce dlogv) around the time the call was made. If the following exception is present: java.lang.noclassdeffounder ror: org.apache.commons.dbcp.del egatingpreparedstatement the issue is likely resolved by restarting Websphere using the command was restart. It is recommended to place the CE in Deny New Service state before restarting WebSphere. This will prevent traffic from being affected.

2 Service versioning Installation Installation Installation Flow Control GetDisplayName API Global attributes return previous services values Installing multiple OVAs on the same LAN simultaneously displays errors and the second one may not succeed. If guest (VM) and host (hypervisor) do not agree on time, VM deployment can fail Only 1 version of the ClickatellSmsConnector should be loaded and/or installed. When CE receives SIP/MSML DTMF match from AMS, the CE platform is not sending digitscollected to the calling service. If a call involves feature interactions (such as bridging or conferencing), then getdisplayname() will SHAREDL IBRARY Installing a new version of the same service maintains the existing service s attribute settings In order to not break the existing service. For example, if you install MyService with attribute foo and a default value of 1, then attempt to install MyService with default value for foo of 2, the default value for foo for both services will be 1. Global service attributes and service profile attributes behave the same way. There are 2 options to address this: 1) Give the variable that needs a new value a different name in the new version of the service 2) uninstall the older version of the service before installing the newer version; note that uninstalling the service will remove it from the users Service Profiles and the new version of the service will need to be added back to the Service Profiles. Avoid installing CEs on the same LAN simultaneously or use vcenter for installation. Make sure NTP is configured and running on ESXi host. If upgrading, delete the currently loaded or installed versions of the connector. This is not an issue on a new installation. See the Flow Control section later in this document. no workaround available

3 Service versioning Logging return NULL. The Service Profile Editor page shows a Service with the Latest version as Installed when actually all versions of the service are only Loaded The service s log statements other than INFO level do not show up in the asm.log (ce dlogv) If the Latest service verson is added to a Service Profile, the State column may become stale if all versions of the service go from being Loaded to Installed or Installed to Loaded. To fix this, remove the service from the Service Profile and add the Latest version back again. This will update the service entry with the correct state. A service using com.avaya.common.logging.cl ient.logger or com.avaya.collaboration.uti l.logger.logger at levels besides INFO do not show up in asm.log (ce dlogv) when using package names which do not start with com.avaya.* (e.g., package com.mycompany.*) There are two options to work around this issue: 1. Use the ce dlogon command to change the settings for a logger matching the package name. For example: ce dlogon com.mycompany which sets the level to ALL, or ce dlogon ERROR com.mycompany which sets the level to ERROR. 2. Change the package name to start with com.avaya.* SMS integration SMS behavior varies by country. CE has not been tested in every 930 *By default logs at INFO level are always logged. Depending on how the service logs information, this may lead to excessive logs written to the asm.log file no workaround available

4 Communication Manager Settings country so we recommend setting up a Clickatell account with a small number of credits for lab verification before deployment. Contact Avaya if you have problems with SMS delivery. Also be aware that local or regional regulations may prevent or delay delivery of an SMS (for example, delivery of an SMS might delayed until normal business hours). Communication Manager only supports 32 media delay timers to allow for the far-end media shuffle to complete in the case of DTMF relay for H.323 stations using DirectMedia or Shuffling. The media is required to shuffle back to the local Digital Signal Processor (DSP) resource in order to transmit any digits pressed during a phone call. Therefore if you have more than 32 simultaneous requests to send DTMF to the far-end, the digit may be lost in transmission because it is sent too early before the media connection has been fully established end-toend. defsw The recommendation until this issue is resolved is to disable direct media and shuffling on the Communication Manager signaling group(s) and verify media resources to meet station capacity needs.

5 General Topics Flow control It is important to avoid traffic congestion for a service that sends a burst of voice announcement requests through Collaboration Environment. The current recommendation is no more than 200 phone numbers to be included per single request to this type of service. Each request should be staggered by seconds between subsequent requests to the same service on the same Collaboration Environment (CE) instance. Additional consideration should be given when the sum of requests targeted for the voice announcements exceeds the maximum port allocation for a single instance of the Avaya Media Server (AMS). The Avaya Media Server (AMS) virtual machine bundled with Collaboration Environment is maximum rated at 1000 ports. A single AMS would be expected to service 1000 announcements over a period of 5 minutes and therefore 2000 announcements would be serviced over 10 minutes. Given this guideline, 5 AMS instances will be required at a traffic level of voice announcement requests serviced over a 10 minute period of time for an average announcement length of 30 seconds. The same traffic distribution guidelines as discussed above apply here as well. Please note that if the phone numbers specified in the voice announcement request contain non-sip devices such as H.323 endpoints (please see table1 keyword Communication Manager Settings for additional information) or non-sip trunk resources please be sure to verify this configuration to ensure you have the needed Digital Signal Processors (DSP) resources required to support a simultaneous voice announcemment request to this set of users. For example: Using the sample service, MultiChannel Broadcast, send 10,000 voice announcements to individual phone numbers within or off enterprise. In this type of example, a single request needs to be bounded at 200 phone numbers and 50 requests would be required to reach 10,000 phone numbers in total. request1=[phone1 phone200]; request2=[phone201 phone400],, request50=[phone9800 phone10000] Additionally, requests1-request25 would be sent to CE instance1 and requests26-50 to CE instance2 Each request per Collaboration Environment instance would still need to be staggered by seconds. In this example, a total of 5 AMS and 2 CE instances will service the request for 10,000 voice announcements within 10 minutes.

6 System Manager Interoperability Avaya Aura System Manager supports Avaya Aura Collaboration Environment 2.0. Please see the Avaya Aura System Manager Release Notes for further details about software enhancements and issues. Collaboration Environment 2.0 is only compatible with this release of System Manager, earlier versions of System Manager must be upgraded to Session Manager Interoperability Avaya Aura Session Manager supports Avaya Aura Collaboration Environment 2.0. Please see the Avaya Aura Session Manager Release Notes for further details about software enhancements and issues. Collaboration Environment 2.0 is only compatible with this release of Session Manager, earlier versions of Session Manager must be upgraded to Proper interoperation between Session Manager and Collaboration Environment requires a special Session Manager patch, see Session Manager PSN notices for more information. Upgrade Compatibility and Sequence When installing updates to the Avaya Aura solution it is important that the different components are upgraded in the correct order to ensure platform stability and manageability of the network as part of the upgrade process. Please refer to Avaya Aura component release notes for the proper upgrade order. Collaboration Environment can be upgraded at anytime after Avaya Aura System Manager is upgraded.