Release Notes for Avaya SIP Enablement Services (SES) Release 5.0 Service Pack 2d Target Products: SIP Enablement Services 5.0 deployed on Avaya S8500 servers or deployed as an embedded component of Communication Manager 5.0 on the S8300C Release Notes Issue 1.0 April 7, 2008 What's Fixed in Service Pack 1 Installation and Upgrade Notes Known Issues and Workarounds Best Practices What s Fixed in Service Pack 2d Previously, SIP Enablement Services sip server process occasionally generated a core dump while shutting down. Previously, SIP Enablement Services sip server process may not start following an upgrade from SIP Enablement Services 4.0 or earlier. Previously, SIP Enablement Services sip server process did not reach a fully up state when the data base was restarted. This has been addressed ensuring no impact to media server and media server extensions. Avaya SIP Enablement Services now supports additional USB compact flash readers and USB memory sticks. The SIP Enablement Services Master Admin web pages were modified to ensure registered and unregistered users are displayed with the appropriate check boxes. When deleting a user from SIP Enablement Services Master Admin, the change to the home is completed immediately. Enhancements were made to Personal Profile Manager. It now acknowledges contact data updates to 96XX endpoints. Previously, changing the domain name did not correctly update emergency contacts or adjunct systems with the new domain name. Now, when the sip domain is changed, calls to administered adjunct servers will be directed to the correct domain and complete successfully. Previously, on a SIP Enablement Services configuration with Avaya Distributed Office, a database error occurred after a domain name change that impacted the buddy lists. Enhancements were made to ensure that names containing multi-byte characters such as Japanese display correctly on the Registered Users Master Admin page. Corrected the authentication issues, that prevented off-board applications such as Avaya Distributed Office Central Management from connecting to SIP Enablement Services. A search for Media Server Extensions will not cause a data base alarm due to valid or non-valid extensions. or trademarks, respectively, of All other trademarks are the property of their respective
Previously, a trap/alarm was generated every 5 minutes when the back up server was down. This has been addressed so that only alarms for new issues are generated after the initial alarm. Enhancements were made to certificate expiration alarms to include Data Services Certificates. Previously, only users with root privilege had the ability to add, update or delete trusted certificates. This has been addressed so that susers login can issue the commands. Previously, an import from ProVision may have generated a database error and the import was not successful. Import was modified to ensure tracking of presence, and the ability to send IMs across homes has been enabled. Security enhancements were made to block TCP connections from an outside server to port 61616. External TLS connections to SIP Enablement Services data service are accepted only on port 61617. Previously, the data service may not have correctly replicated data to home servers following a SIP Enablement Services database restore on the edge server. Installation and Upgrade Notes The upgrade procedure for pre-5.0 releases to SIP Enablement Services Release 5.0 can be found in the document Installing, Administering, Maintaining, and Troubleshooting SIP Enablement Services, 03-600768, which is on Avaya s Support website, at the following link: http://support.avaya.com/japple/css/japple?temp.documentid=331496&temp.productid=160073& temp.releaseid=328125&temp.bucketid=160259&page=document Known Issues and Workarounds Restore When performing a Restore, verify that all servers in the configuration are up and running in order for data replication to be successful. While restoring an Edge server s database, the Home server(s) are instructed (through a web service) to delete subscriber data and accept refreshed data pushed from the SIP Enablement Services Edge. If this process is not successful (for example, newly administered users may be unable to register), the Restore function will report success, but databases could be inconsistent across the SIP Enablement Services system configuration. In this instance, repeat Restore. A Restore that contains a different profile service password for the SIP Enablement Services Edge than is used in the currently running configuration reports success, but data replication fails, leaving the databases inconsistent across the SIP Enablement Services system configuration. To recover the Restore: 1. Allow the Restore function to complete. 2. Modify the service profile password on the SIP Enablement Services Edge to match the running configuration. Use caution when making changes to the profile service password. This could have unexpected impacts on subsequent Restore operations. 3. Back up the data. 4. Immediately perform a Restore with this backup. or trademarks, respectively, of All other trademarks are the property of their respective
Restoring a SIP Enablement Services Release 4.0 backup onto an Edge running Release 5.0 results in loss of Personal Profile Manager related data (for example, user contact information and preferences). Restore each Home individually to recover all this data. Restoring a SIP Enablement Services Edge 5.0 causes a temporary system-wide outage while user data is being propagated to all of the Homes. User registrations are preserved. Alarms Alarms are viewed 500 at a time. Clearing the alarms will clear the entire set of alarms, not just those that are currently shown. Best Practices Installing, Administering, Maintaining and Troubleshooting SIP Enablement Services Before beginning any installation or upgrade, verify that all your SIP Enablement Services documentation is the most current issue/date listed for SIP Enablement Services Release 5.0 on Avaya's Support website at http://www.avaya.com/support. Server Availability Management Processor (SAMP) firmware and operations When installing a new S8500B or S8500C as an Avaya SIP Enablement Services (SES) 5.0 server, the software installer will load the proper version of the Server Availability Management Processor (SAMP) firmware. It is recommended for proper operation of the SIP Enablement Services server that you do not upgrade the SAMP firmware manually, even if a newer version may be available. Root Certificates The tlscertmanage command replaces the 4.0 web page for management of the trusted root certificates. Root certificates must first be placed in /var/home/ftp/pub (the default directory for the Download Files page in the Maintenance web interface, or for anonymous ftp, if it is enabled) before running the command as follows. Usage of tlscertmange: tlscertmanage -l List all CA certificates on the system tlscertmanage -i file Install a CA tlscertmanage -r # Remove a CA (Specify #) tlscertmanage -help Gives this USAGE screen Restore from pre 5.0 Databases Restoring a SIP Enablement Services Release 4.0 backup onto an Edge running SIP Enablement Services Release 5.0 results in loss of Personal Profile Manager related data until each Home server is restored with SIP Enablement Services 4.0 or earlier database backup. Contacts/presence are case sensitive Presence is not reported properly if the case of a handle in the contact list for Avaya one-x Desktop SIP does not exactly match the case of the administered user handle in SIP Enablement Services. Ensure that user handles that are administered on the SIP Enablement Services Administration web pages and the Avaya one-x Desktop SIP contact information use the same character case. or trademarks, respectively, of All other trademarks are the property of their respective
Communication Manager Failover Service/Avaya Enterprise Survivable Server (ESS) configurations The default server connection between Avaya SIP Enablement Services 5.0 and Communication Manager is through SSH (secure shell protocol). Communication Manager configurations with ESS use the C-LAN s IP address to connect upon ESS failover. C-LANs support only telnet connections, which requires that you select telnet as the desired SMS Connection Type when configuring Communication Manager s ESS server in the SIP Enablement Services Administration interface. SNMP administration on duplex systems Administer SNMP destinations at both the primary and the backup servers of a duplex system through the Maintenance web pages. Connect to the backup server using the physical IP address of the backup server. That is, to access the Maintenance web pages on the backup server, enter the physical IP address of the backup server in your web browser. For example, enter http://999.16.99.201/admin, where 999.16.99.201 is the physical IP address of the backup server. Trusted hosts There are third-party proxies that do not support proxy authentication and therefore must be configured as trusted hosts. Use the SIP Enablement Services Administration s trusted host web page. Before configuring an entity as a trusted host, ensure that the entity will properly validate SIP requests before forwarding them to Avaya SIP Enablement Services. SIP Enablement Services will "trust" all requests received from the entities so configured. ASCII Characters Only in WebLM License Path When installing a WebLM license using Microsoft Internet Explorer on a PC with a non-u.s. English version of Microsoft Windows (for example, Japanese Windows), verify that the full path name to the license file contains ASCII characters only, without international or special characters. Configuration considerations for Third-Party SIP phones Some third-party SIP telephones have the ability to perform features locally that are typically provided by Communication Manager. It is highly recommended that the local telephone version of these types of features be disabled, if at all possible. For example, when you make a call from a Cisco 7940/7960 SIP phone with the local Caller ID Block feature of the phone enabled, the called endpoint still displays your number. To work around this issue, use the Calling Number Block FNE in Avaya Communication Manager instead of the local feature of the telephone. Call Forwarding is another example of a feature that some SIP phones can perform locally, but is typically a feature that is provided by Communication Manager. In general, Avaya Communication Manager should always be used to provide these types of features, both to ensure the consistency of the user experience across all types of telephones, and also to prevent unexpected interactions that may occur with other Communication Manager features. or trademarks, respectively, of All other trademarks are the property of their respective
Verify component compatibility Verify that all your components are upgraded to the latest available. For maximum compatibility and interoperability among VoIP resources such as the TN2602AP IP Media Resource 320 and Avaya SIP Enablement Services 5.0, ensure that the firmware has been upgraded to the latest vintage available for your component and release of Communication Manager. Visit the Downloads section of the Avaya Support Web site at http://support.avaya.com. or trademarks, respectively, of All other trademarks are the property of their respective