Avaya Aura Session Manager Release 5.2 Service Pack 2 Release Notes

Transcription

1 Avaya Aura Session Manager Release 5.2 Service Pack 2 Release Notes Release 5.2 March 2014 Issue 3 1

2 2014 Avaya Inc. All Rights Reserved. Notice While reasonable efforts were made to ensure that the information in this document was complete and accurate at the time of printing, Avaya Inc. can assume no liability for any errors. Changes and corrections to the information in this document may be incorporated in future releases For full support information, please see the complete documents, Avaya Support Notices for Software Documentation, document number and Avaya Support Notices for Hardware Documentation, document number To locate this document on our Web site, simply go to and search for the document number in the search box. Documentation disclaimer Avaya Inc. is not responsible for any modifications, additions, or deletions to the original published version of this documentation unless such modifications, additions, or deletions were performed by Avaya. Customer and/or End User agree to indemnify and hold harmless Avaya, Avaya's agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation to the extent made by the Customer or End User. Link disclaimer Avaya Inc. is not responsible for the contents or reliability of any linked Web sites referenced elsewhere within this documentation, and Avaya does not necessarily endorse the products, services, or information described or offered within them. We cannot guarantee that these links will work all of the time and we have no control over the availability of the linked pages. Warranty Avaya Inc. provides a limited warranty on this product. Refer to your sales agreement to establish the terms of the limited warranty. In addition, Avaya s standard warranty language, as well as information regarding support for this product, while under warranty, is available through the following Web site: Copyright Except where expressly stated otherwise, the Product is protected by copyright and other laws respecting proprietary rights. Unauthorized reproduction, transfer, and or use can be a criminal, as well as a civil, offense under the applicable law. Avaya support Avaya provides a telephone number for you to use to report problems or to ask questions about your product. The support telephone number is in the United States. For additional support telephone numbers, see the Avaya Web site: 2

3 Table of Contents Avaya Aura Session Manager Release 5.2 Service Pack 2 Release Notes... 4 Product Support Notices... 4 Enhancements to Avaya Aura Session Manager R5.2 included in Service Pack Workarounds... 6 Avaya Aura Communication Manager Interoperability... 8 General Topics... 9 Emergency call improvements... 9 SIP monitoring... 9 Upgrades from Session Manager SIP Phone Firmware... 9 Contacts Communication Manager Dialplan Synchronization Technical Support

4 Avaya Aura Session Manager Release 5.2 Service Pack 2 Release Notes Product Support Notices Some product changes are also documented as Product Support Notices (PSN). The PSN number defines the related document and appears in the Problem column in the tables. To read the PSN description online: 1. Go to the Avaya support site at 2. Scroll down to PRODUCT INFORMATION and click on Product Support Notices. 3. Enter the last four digits of the PSN number into your web browser s Find on Page function to search the page for a link to the PSN. 4. Click on the PSN title link to open the PSN. 4

5 Enhancements to Avaya Aura Session Manager R5.2 included in Service Pack 2 This release includes the following enhancements delivered to Avaya Aura Session Manager: Table1: Enhancements to Avaya Aura Session Manager R5.2 Service Pack 2 Keywords Enhancement ID Reference Verizon Adaptor Sequenced Applications Cisco Adaptation Security Update SIP Firewall Bandwidth Management Trusted Hosts Local Host Name Resolution (LNNR) Alarming Verizon Adapter using "," as a delimiter in History Info used to create an incorrect Diversion Header, now the, is handled correctly. If a non-mandatory application cannot be accessed, and there are no more applications in the sequence, the SM used to send an error back to the caller instead of routing to called party. Now the SM will continue to route the call to the called party. CiscoAdapter Module now delivers the "divert all calls to Voic " function on Cisco phones. Session Manager has been modified to insert a History-Info header with the send-all-calls reason code when it sees a Diversion header with the unconditional reason. This will cause the Cisco UCMs to interact correctly with SIP compliant voic systems. Medium - [RHSA-2010: ] dbus security update has been added to the Session Manager. When retrieving sip firewall configuration from one instance and committing it to another which is not accessible (network down, host down etc..) System Manager will now display an error message when trying to save configuration to unaccessible instances. Network Fragmentation will no longer be seen on the GUI s Manage Bandwidth Usage page (Session Manager -> System State). Prior to this service pack network fragmentation would most likely be seen after a fresh install or an upgrade where the database was deleted. After an SM reboot, audits of links for unresolved FQDNs will now be audited periodically. The ability to edit weights and priorities reliably has been added to this service pack. [Session Manager Network Configuration] The thresholds for a critical SM100 board overheating alarm have been tuned to no longer raise this alarm pre-maturely. 5 wi wi wi wi wi wi wi wi wi

6 SM100 restart FQDN connection support SIP Firewall CDR SM100 hardware manufacturer delivered a new driver that improves the performance and stability of the board. Local Hostname Resolution now supports up to 32 connections per SIP entity (increased from 10). New rules are now available for SIP endpoint connections. With this service pack a user can select Retrieve Default Config in SIP Firewall rules and the proper default firewall rules will be loaded. Call Detail Recording has been augmented to limit output to a single records per call for SIP endpoints. Previously there were rare cases of more than one record for some calls. wi wi wi wi Workarounds This service pack also offers the following helpful tips and workarounds for known issues: Table2: Avaya Aura Session Manager Release 5.2 Service Pack 2 Issues Issue Keywords ID Reference Workaround The following 2 errors may appear occasionally in the SMGR Logging page: 1 - Received SOAP message has a null SOAP Envelope 2 - Failed to retrieve trusted hosts from Asset Logging wi These error messages do not influence any functionality and should be ignored. Failed to read AP Trusted Hosts configuration occasionally After installing SP1 occasionally a false error for data replication status and Security Module status remains. SP1 Installation wi If this happens, an audit should run within 30 minutes to resolve the errors and report accurate status. 6

7 Issue Keywords ID Reference Workaround Can't configure a SIP Trace with non-english characters like à or Ü SIP Firewall rules are not be backed up properly. SIP Trace wi Do not use these unusual characters in the specification of the SIP tracer tool SIP Firewall wi If SIP Firewall feature is being used, make two backups and discard the first one. If the SIP Firewall feature is in use (System Manager: Session Manager Network Configuration SIP Firewall), the first rule (Rate limit and Alarm high new SIP Firewall wi Disable rule #1 calls rate) may cause SM100 board resets (service disruptions). SIP endpoints may experience failed calls if SIP Firewall rule #4 (Rate limit and Alarm slow invite flood from UA connection) is enabled and using default threshold settings. The default may be too strict. SIP Firewall wi Adjust the rule threshold to suit your system requirements. This is standard procedure for any rule alarming. Viewing SIP Firewall current SIP Firewalll wi Deselect the enable configuration for the first time may enable the feature. rules box if the deep inspection rules are not required, and save. 7

8 Avaya Aura Communication Manager Interoperability Avaya Aura Session Manager Release 5.2 supports Avaya Aura Communication Manager Release and later. The following issues with Communication Manager Release have been identified and are planned to be resolved in Communication Manager Release 6.0 unless otherwise noted. The following helpful tips and workarounds are offered. Table3: Communication Manager Workarounds Issue Keywords ID Ref Workaround When the Nortel NRS is used Nortel with SM and a CM user calls a Nortel user that is redirected by NRS, the display on the final answering Nortel station displays the redirected trunk group number. Occasionally a CM user will be cut off when leaving a message for another CM user when both users are served by a core Modular Messaging. The affected CM will execute a soft restart. Modular Messaging The Call Park Timeout to Call-Park Originator feature does not Timeout return the call when the call was parked by use of the feature access code dialing procedure. After a call is disconnected One Touch where the One Touch Record Recording (OTR) button was used to record the call, the OTR button will still show an active status even though the call has ended and is not being recorded. In an Aura Feature Server environment with SIPS encrypted stations, a station calls a hunt group head number. The hunt group head number is not known by Session Manager. The call fails. defsw The Session Manager should be programed with the correct Nortel equipment for Nortel users so the NRS does not redirect with SIP message 302. defsw Administrators should make sure all users in CM-FS are configured with a name and avoid the call number and name blocking feature. This problem was corrected in CM5.2.1 SP1. defsw Use the call-park button on the phone to park a call instead of using a feature access code. trak10168 Manually deactivate the OTR button before ending the call, or manually deactivate the button after the call has finished. Hunt group defsw Administer the hunt group head number in Session Manager user table as a normal extension. 8

9 General Topics Emergency call improvements When administering Emergency Dial numbers, the administrator should use the Network Routing Policy > Dial Patterns menu item on the SMGR console. Each emergency dial number is associated with a location. Note these important constraints on the use of this feature: Each location should only be assigned ONE emergency dial number. This emergency dial number MUST match the emergency dial number in the 96xx settings file for all SIP phones in the identified location. Failure to follow these guidelines can result in users being unable to dial emergency numbers. SIP monitoring wi , SIP Monitoring was enhanced to allow for the administration of responses to the SIP options messages sent to a specific SIP Entity will cause the link to that entity to be marked up or down. Previously no response to the SIP options message, or a 408 or 504 response would mark the link down, while any other response would mark the link up. With this service pack, 503 Service Unavailable will now also mark the link down by default. The Notes field of the SIP Entity screen in System Manager, can now contain a list of UpResponses and DownResponses for the entity. For example, to have a 503 Service Unavailable mark an entity link Up and to have a 405 or 600 response mark the link Down, the following could be placed in the SIP Entity Notes field: UpResponses=503 Service Unavailable;DownResponses=405,600 Upgrades from Session Manager 1.1 Upgrades from Session Manager 1.1 Service Pack 3 are supported to Session Manager 5.2 Service Pack 2. See Installing Service Packs on Avaya Aura Session Manager on the Avaya support web site, SIP Phone Firmware Session Manager 5.2 supports SIP phone firmware 2.5 or higher. Please contact support for help downloading. 9

10 Contacts Use of contacts by either the administrator or the end user is supported with SIP phone firmware 2.5 or later. 1. Management of contact lists by the Administrator: a. When adding a contact to a user s list of private contacts, each entry must include a type sip handle. The sip entry can be a real or a dummy sip handle of the forms sip: @xyz.com. A second entry for the same contact of type phone should also be added for the normal phone number. Note that the sip handle must be unique. b. When adding an entry to user A s default contact list, it is possible to select another user in the enterprise, e.g. user B. If user B is administered on a different SM than user A, this operation will fail (with no notification of the failure to the user). In this case the recommended workaround is to add user B as a private contact for user A. c. Assigning a contact to a user s speed-dial list is not supported. 2. Management of contact lists by the end user: a. Using the phone UI, the ability to search contacts is not supported. b. Using the phone UI, the ability to edit contacts is not supported. 10

11 Communication Manager Dialplan Synchronization Changes in the Communication Manager dialplan will be synchronized to Session Manager only once per day, at approximately 3:30 AM system time. This is independent of any synchronization settings administered in the System Manager. After administering the Communication Manager entity under Applications > Entities, a synchronization activity with this Communication Manager will begin. The synchronization uses OSSI to pull relevant data from the Communication Manager and therefore will take available CPU from the Communication Manager in order to complete this large task. This activity runs at a much lower priority than call processing tasks; however the traditional administration interfaces, such as SAT, may become sluggish or slow in response. List Measurements Occupancy on the Communication Manager will also report a large spike in Communication Manager activity during this interval. This is normal and expected. 11

12 Technical Support Support for Session Manager is available through Avaya Technical Support. If you encounter trouble with Session Manager: 1. Retry the action. Carefully follow the instructions in written or online documentation. 2. Check the documentation that came with your hardware for maintenance or hardwarerelated problems. 3. Note the sequence of events that led to the problem and the exact messages displayed. Have the Avaya documentation available. 4. If you continue to have a problem, contact Avaya Technical Support by: Logging into the Avaya Support Web site Calling or faxing Avaya Technical Support at one of the telephone numbers in the Support Directory listings on the Avaya support Web site. You may be asked to one or more files to Technical Support for analysis of your application and its environment. Note: If you have difficulty reaching Avaya Technical Support through the above URL or address, please go to for further information. When you request technical support, provide the following information: Configuration settings, including Session Manager configuration and browser settings. Usage scenario, including all steps required to reproduce the issue. Screen shots, if the issue occurs in the Administration Application, one-x Portal, or one-x Portal Extensions. Copies of all logs related to the issue. All other information that you gathered when you attempted to resolve the issue. Tip: Avaya Global Services Escalation Management provides the means to escalate urgent service issues. For more information, see the Escalation Contacts listings on the Avaya Support Web site. For information about patches and product updates, see the Avaya Support Web site at 12