Siemens Enterprise Communications Release Note Release Note Version: V1.0 Document Owner: Jim McMahon – Com ESY LIP HPD413

Product Name: IBM-OEM TCS Product-Version: V1 IBM-OEM TCS SW Release is identified by SW Version: V3.1 R2.32.49 Major Release (Upgrade to new Product Version, relevant for manufacturing) Minor Release (Feature Enhancements, relevant for Manufacturing) (Upgrade or Update, depending upon new licensed features required. Upgrade only if license extension required) Fix Release (Update, Error Corrections only, relevant for Manufacturing) Hotfix Release (Update, Error Corrections only, restricted to Service Level 2) Production Version: 12.00.02.ALL.15 (SMR02) with PS32E49 Field Trial: eeQS: General Availability:

DECLARATION DATE: Date : June 18, 2010 DECLARED BY: corresponding PL-Development : Stuart Marshall Com ESY LIP HPD460

DELIVERABLES: Full Release: Delta Release:

Software: Refer to SWS/G-DMS structure according to Product Name and SW-Version Hardware: Refer to Chapter: Hardware Revisions supported Abstract: These Release Notes provide general information about the release, generics, and other relevant notes for the corresponding product and its correction versions. These Release Notes also list and describe the known problems, restrictions and workarounds. Siemens Enterprise Communications GmbH & Co. KG reserves the right to make changes and improvements to the products and any of the features of the products described in this document without prior notice. The contents of this document are provided "as is". Except as required by applicable law, no warranties of any kind, either express or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose, are made in relation to the accuracy, reliability or contents of this document. Siemens Enterprise Communications GmbH & Co. KG reserves the right to revise this document or withdraw it at any time without prior notice. WARNING: THIS DOCUMENT (OR DATA) CONTAINS INFORMATION THAT IS PROPRIETARY INTELLECTUAL PROPERTY AND/OR TRADE SECRET OF SIEMENS ENTERPRISE COMMUNICATIONS GmbH & Co. KG AND MAY ONLY BE VIEWED BY AUTHORIZED PERSONS. UNAUTHORIZED VIEWING OR DISCLOSURE IS STRICTLY PROHIBITED. No part of this material may be copied or reproduced, in whole or in part, in any form (including photocopying and/or storage in any medium by electronic means and whether or not transiently or incidentally to some other use of this document) without the written permission of Siemens Enterprise Communications GmbH & Co. KG. Copyright 2009 Siemens Enterprise Communications GmbH & Co. KG. All rights reserved. Siemens Enterprise Communications GmbH & Co. KG is a Trademark Licensee of Siemens AG.

Release Note Page 2 of 25 OpenScape Voice Server V3.1 R2.32.339

Table of Contents Siemens Enterprise Communications....................................................................................................................1

Release Note .............................................................................................................................................................1

1 History of Changes (Release Note).................................................................................................................4

2 Product and Diagnostics Structure ................................................................................................................5

2.1 Product Structure in G-DMS and SWS..........................................................................................................5

3 Security Policy ..................................................................................................................................................6

3.1 HiSAT ............................................................................................................................................................6 3.2 OS Specific ....................................................................................................................................................6

4 Hardware and Software Compatibility............................................................................................................7

4.1 Hardware Revisions supported .....................................................................................................................7 4.2 Firmware Revisions supported ......................................................................................................................7 4.3 Operating Systems supported .......................................................................................................................8 4.4 Software Releases supported .......................................................................................................................8 4.5 Compliant Products .......................................................................................................................................9

5 Serviceability Information..............................................................................................................................11

5.1 Management Information Base ...................................................................................................................11 5.2 License Management ..................................................................................................................................11 5.3 Remote Serviceability..................................................................................................................................11

6 Release Version History.................................................................................................................................12

7 Changes in this Release ................................................................................................................................14

7.1 Change Requests (FRNs) ...........................................................................................................................14 7.2 Fixed IBM OEM ICTS Tickets......................................................................................................................14

8 Outstanding Problems ...................................................................................................................................15

8.1 Outstanding ICTS Tickets for IBM-OEM TCS .............................................................................................15

9 Installation Instructions .................................................................................................................................16

9.1 RapidStat Report .........................................................................................................................................16 9.2 Base OS for an External OpenScape Voice Assistant/Media Server .........................................................16 9.3 Installing new 3.1 servers ............................................................................................................................16 9.4 Upgrading V3.1 R2 servers .........................................................................................................................17 9.5 Configure endpoint attribute for media server .............................................................................................17

10 Important Information.....................................................................................................................................19

10.1 Open Source Software ................................................................................................................................19 10.2 Knowledge Base documents .......................................................................................................................20 10.3 Important Information for “Easy IP Address Changing”...............................................................................20 10.4 The BG Needs a Default NP .......................................................................................................................20 10.5 Important Information for FRN0497 (Remote Patching Capability).............................................................20 10.6 Configuration of the CIP Addresses ............................................................................................................21

Release Note Page 3 of 25 OpenScape Voice Server V3.1 R2.32.339

10.7 License Activation........................................................................................................................................21

11 Workarounds...................................................................................................................................................23

12 Restrictions .....................................................................................................................................................25

12.1 Restrictions for this current release. ............................................................................................................25 12.2 Restrictions for this product version ............................................................................................................25

Release Note Page 4 of 25 OpenScape Voice Server V3.1 R2.32.339

1 History of Changes (Release Note)

Version Date Changes Author 1.0 09/17/2010 GA release for IBM-OEM use only. Stuart Marshall

Release Note Page 5 of 25 OpenScape Voice Server V3.1 R2.32.339

2 Product and Diagnostics Structure

2.1 Product Structure in G-DMS and SWS

Release Notes, MOPs and other service documentation for OpenScape Voice and related products can be found in G-DMS. Binary files are distributed via SWS. The following table illustrates how the products are organized in G-DMS/SWS. The first two lines of the table identify the top level structure that is common for all OpenScape Voice products. The remaining lines identify the specific location under the top level structure for each product and version currently being supported or recommended.

Main Category Applications Product Family OpenScape

Product Product Version Product Item Number OpenScape Applications OpenScape IBM-OEM TCS Images V1 P30152-P1427-P2-4 (V3.1 R2.32.24) OpenScape Applications OpenScape IBM-OEM TCS Installation Wizards V1 P30152-P1427-P4-3 (V3.1 R1.17.0) OpenScape Applications OpenScape IBM-OEM TCS Patchsets V1 P30152-P1427-P3-2 (V3.1 R2.32.2) Main Category Applications Product Family OpenScape

Product Product Version Product Item Number OpenScape Applications OpenScape IBM-OEM TAS V1 P30152-P1427-P1-12 (V1.0 R9.5.0)

Release Note Page 6 of 25 OpenScape Voice Server V3.1 R2.32.339

3 Security Policy

3.1 HiSAT

No new information

3.2 OS Specific

OpenScape Voice V3.1 is based on the SuSE Linux Enterprise Server 9 (SLES 9) operating system.

Although security updates for this SLES 9 are periodically released by the manufacturer, Siemens Enterprise Communications does not recommend such updates to be installed “as is“ since they may cause a negative impact on the system. For this reason, Siemens Enterprise Communications periodically releases selected SLES 9 security updates together with OpenScape Voice software updates, in the form of MOPs (released with OpenScape Voice patchsets) or embedded in new OpenScape Voice SMRs.

Release Note Page 7 of 25 OpenScape Voice Server V3.1 R2.32.339

4 Hardware and Software Compatibility

4.1 Hardware Revisions supported

Server model Revision IBM System x 3650T All

For details on the each system’s configuration, please consult the Installation and Upgrade Guide (P31003H8031J103017631).

Note: IBM x3650T systems require a memory upgrade. See INF-08-000392.

4.2 Firmware Revisions supported

The following table specifies the minimal firmware versions required depending on the server model. Servers may come from the factory with newer firmware versions; such servers don’t need to be downgraded, unless otherwise noted. If upgrades are required, the firmware versions listed below can be found in PRISMA and SWS.

Server model Unit Version Alt. Version Build Id Main BIOS P11.00.0090 none not available ISMP/BMC ROM 0.54 none not available FRU/SDR ES-6.6.4 none not available

IBM System x 3650T

Onboard LSI RAID IME-5.10.06 none not available

The official firmware version is listed in the Version column. However, depending on the method used to get the firmware in a running system (BIOS, RSA, ASU), the same firmware may return a different number, listed in the Alternative Version column. The Build Id can also be used for additional confirmation.

Release Note Page 8 of 25 OpenScape Voice Server V3.1 R2.32.339

4.3 Operating Systems supported

OpenScape Voice V3.1 is based on the SuSE Linux Enterprise Server 9 (SLES 9) operating system.

4.4 Software Releases supported

This release note contains information pertinent to the OpenScape Voice Server software only. Additional software products are required to install and operate the OpenScape Voice Server. These products are listed in the following table, which also includes the respective versions required to use with the current OpenScape Voice Server software and the location of their respective Release Notes in G-DMS.

Product Software Version Release Date¹ G-DMS Note OpenScape Voice Server V3.1 R2.32.48 08/25/2010 See section 7 OpenScape Voice Server Image V3.1 R2.32.24 06/05/2009 See section 7 OpenScape Voice Installation Wizard for Image and Non-image Systems

V3.1 R1.17.0 12/22/2008 INF-09-000191

OpenScape Voice Recovery Software V3.1 R0.16.0 12/10/2008 INF-09-000160 OpenScape Voice Basic Traffic Tool V3.1 R0.10.2 08/22/2008 INF-08-001144 OpenScape Voice GEM Tool V3.1 R11.4.0 06/16/2008 INF-08-001145 OpenScape CLM V1.0 R3.0.0 09/07/2007 INF-07-001213 Call Trace Manager V3.1 R0.6.0 11/19/2007 INF-08-000178 OpenScape IBM-OEM TAS V1 V1.0 R9.5.0 + HFs 05/19/2009 P30152-P1427-P1-12

Notes:

¹ Items recently released are marked with a star ( ).

Release Note Page 9 of 25 OpenScape Voice Server V3.1 R2.32.339

4.5 Compliant Products

Hardware and software products that have been tested together with the OpenScape Voice Server, including third-party products, are listed in the following table, which also includes the respective versions required to use with the current OpenScape Voice Server software and the location of their respective Release Notes in G-DMS. Notes:

Product Family Product SW Version Status G-DMS Note HiPath 4000 Server 3.0 V3.0 R8.3.0 GA INF-08-000895 HiPath 4000 Server 3.0 Hotfix V3.0 R8.3.70 GA HF001169 HiPath 4000 HG3540 (Q2316 hardware)

pzfigw20.m8.007 GA MSC17960

HiPath 4000 Server V4 V4 R2.1.0 GA INF-08-000939 HiPath 4000 Server V4 Hotfix V4 R2.1.87 GA HF001128

HiPath 4000

HiPath 4000 HG3500 (Q2316 & Q2324 hardware)

pzksti40.O4.020-003 GA MSC18116

HiPath 3000 Server V7 V7 R4.4.0 GA INF-08-000954 HiPath 3000

HiG1500/STMI (3K V7 R4 only) V7 R4.5.0 GA INF-08-000709 HiPath AP1120 V5.1 R1.7.0 eeQS INF-09-000478 Mediatrix 41xx V5.0 R0.24.0 eeQS INF-09-000509 OptiPoint 150 S V1 R0.54.0 GA INF-09-000341 OptiPoint 410/420 V7 R5.2.0 GA HW Specific OpenStage 20E V1 R4.23.0 + HFs (eeQS) GA HW Specific OpenStage 20/40 V1 R4.23.0 + HFs (eeQS) GA HW Specific OpenStage 60/80 V1 R4.23.0 + HFs (eeQS) GA HW Specific OpenScape Video V1 R0.2.0 GA INF-09-000017 Wireless LAN Phones (WL2S) V1 R0.62.0 GA INF-09-000138 HiPath WLAN Controller V5 R3.10404.3 GA INF-09-000560 OptiClient 130 SIP V4 R5.241.18 GA INF-09-000535 DLS (Windows version) V2 R4.11.1 Build 619 GA INF-09-000319 DLS (Linux version) V2 R3.520.0 GA Not Available

SIP Clients and Devices

Mediatrix 1104/1124 V5.1 R1.7.0 eeQS INF-09-000478 HiPath RG2700 V1.0 R2.7.0 GA INF-09-000472 HiPath RG8700 V1.3 R2.2.2 GA MSC18837 HiPath RG8700 V1.3 R2.2.10 GA MSC19745 Mediatrix 1204 V5.1 R1.7.0 eeQS INF-09-000475 Mediatrix 1402/1404 V3 R20.3.0 GA INF-08-000169 Mediatrix 1531 V3 R20.0.0 GA INF-07-000090 Mediatrix 1631/2402-2 V3 R20.3.0 GA INF-08-000169 Mediatrix 3531/3532 V1.1 R10.110.0 GA INF-08-001185 Mediatrix 3631/3632 V1.1 R10.118.0 GA INF-09-000457 Mediatrix 4401/4402/4404 V1.1 R10.110.0 GA INF-08-001180 Comdasys Convergence V1 R0.10.0 GA INF-09-000466 Covergence CXC Branch 3.5.0 Build 42753 eeQS INF-09-000248

SIP Gateways, Proxies and SBCs

ACME Net-Net 4250 Firmware C6.0.0 Build 121 Not Available HiPath ComAssistant V2.0 R4.1.0 + Hs GA INF-09-000190 Call Management HiPath OpenScape V2.3 V2.3 R1.7.0 GA INF-08-000831

Release Note Page 10 of 25 OpenScape Voice Server V3.1 R2.32.339

Product Family Product SW Version Status G-DMS Note HiPath OpenScape TCL V1 R3.0.0 FT INF-08-000763 HiPath CAP V3.0 R7.16.0 GA INF-08-000680

HiPath Xpressions ² V5 R2.0.0 Obs. INF-08-000097 + MSC16948

HiPath Xpressions V5 R3.1.0 PSR INF-08-000636 HiPath Xpressions V5 R4.6.0 GA INF-09-000550 HiPath ProCenter V7 R2.7.0 GA INF-09-000144 IP Unity Mereon MS V3.1 R0.23.0 GA INF-08-000356 Convedia CMS1000 V3 R11.0.4 GA INF-08-000262 Convedia CMS3000 V3 R11.0.4 GA INF-08-000261 IP Unity Mereon UM ¹ 3.1.5.1-0034-6 GA Not Applicable IP Unity Mereon CB ¹ 3.1.0.7-0031-6 GA Not Applicable Genesys 7.6 GA Not Applicable HiPath Accounting Management V2 R4 PSR Not Applicable

HiPath Fault Management V3 R8 Test Not Applicable HiPath Management Applications

HiPath User Management V2 R11.1.0 GA INF-09-000222

Notes:

¹ Products not supported by Siemens Enterprise Communications GVS. PSR is required for these items. ² Xpressions V5 R2 is listed only for backward compatibility purposes. SRTP is not supported and Xpressions V5 R2 is not available for new customers.

Release Note Page 11 of 25 OpenScape Voice Server V3.1 R2.32.339

5 Serviceability Information

5.1 Management Information Base

Product forwards SNMP traps according to a MIB

5.2 License Management

Product is licensed via: CLS CSC Other

5.3 Remote Serviceability

Product is certified for: SIRA HiSPA RTPatch Other

Release Note Page 12 of 25 OpenScape Voice Server V3.1 R2.32.339

6 Release Version History

The following table is a list of all V1 IBM-OEM TCS Server software updates, including the location of the respective Release Notes in G-DMS. This list can also be used to locate all patchsets required when performing a fresh installation.

SW Version Production Version Contents Release Date

G-DMS Note Remarks

V3.1 R2.28.7 12.00.02.ALL.15_PS0028.E07 Patchsets 27..28E07 08/08/2008 INF-08-001067 General Availability V3.1 R2.28.10 12.00.02.ALL.15_PS0028.E10 Patchsets 28E08..28E10 08/25/2008 MSC18356 General Availability V3.1 R2.28.11 12.00.02.ALL.15_PS0028.E11 Patchsets 28E11 08/27/2008 MSC18362 General Availability V3.1 R2.28.12 12.00.02.ALL.15_PS0028.E12 Patchsets 28E12 09/15/2008 MSC18445 General Availability V3.1 R2.32.2 12.00.02.ALL.15_PS0032.E02 Patchsets 29..32E02 10/31/2008 INF-09-000066 General Availability V3.1 R2.32.3 12.00.02.ALL.15_PS0032.E03 Patchsets 32E03 10/31/2008 MSC18615 General Availability V3.1 R2.32.4 12.00.02.ALL.15_PS0032.E04 Patchsets 32E04 11/18/2008 MSC18697 General Availability V3.1 R2.32.5 12.00.02.ALL.15_PS0032.E05 Patchsets 32E05 12/08/2008 MSC18767 General Availability V3.1 R2.32.9 12.00.02.ALL.15_PS0032.E09 Patchsets 32E06..32E09 12/12/2008 MSC18794 General Availability V3.1 R2.32.11 12.00.02.ALL.15_PS0032.E11 Patchsets 32E10..32E11 01/30/2009 MSC18939 General Availability V3.1 R2.32.18 12.00.02.ALL.15_PS0032.E18 Patchsets 32E12..32E18 03/30/2009 MSC19241 General Availability V3.1 R2.32.21 12.00.02.ALL.15_PS0032.E21 Patchsets 32E19..32E21 04/30/2009 HF001078 General Availability V3.1 R2.32.24 12.00.02.ALL.15_PS0032.E24 Patchsets 32E22..32E24 05/15/2009 HF001107 General Availability V3.1 R2.32.26 12.00.02.ALL.15_PS0032.E26 Patchsets 32E25..32E26 05/26/2009 HF001126 General Availability V3.1 R2.32.27 12.00.02.ALL.15_PS0032.E27 Patchsets 32E27 05/29/2009 HF001132 General Availability V3.1 R2.32.28 12.00.02.ALL.15_PS0032.E28 Patchsets 32E28 06/01/2009 HF001134 General Availability V3.1 R2.32.29 12.00.02.ALL.15_PS0032.E29 Patchsets 32E29 06/05/2009 HF001150 General Availability V3.1 R2.32.30 12.00.02.ALL.15_PS0032.E30 Patchsets 32E30 06/06/2009 HF001151 General Availability V3.1 R2.32.31 12.00.02.ALL.15_PS0032.E31 Patchsets 32E31 06/09/2009 HF001153 General Availability V3.1 R2.32.33 12.00.02.ALL.15_PS0032.E33 Patchsets 32E32..32E33 07/01/2009 General Availability V3.1 R2.32.37 12.00.02.ALL.15_PS0032.E37 Patchsets 32E34..32E37 08/27/2009 General Availability V3.1 R2.32.38 12.00.02.ALL.15_PS0032.E38 Patchsets 32E38 09/30/2009 General Availability V3.1 R2.32.39 12.00.02.ALL.15_PS0032.E39 Patchsets 32E39 10/07/2009 General Availability V3.1 R2.32.40 12.00.02.ALL.15_PS0032.E40 Patchsets 32E40 10/15/2009 General Availability V3.1 R2.32.42 12.00.02.ALL.15_PS0032.E42 Patchsets 32E41..32E42 11/13/2009 General Availability V3.1 R2.32.44 12.00.02.ALL.15_PS0032.E44 Patchsets 32E43..32E44 02/11/2010 General Availability V3.1 R2.32.46 12.00.02.ALL.15_PS0032.E46 Patchsets 32E45..32E46 04/08/2010 General Availability V3.1 R2.32.47 12.00.02.ALL.15_PS0032.E47 Patchsets 32E47 06/18/2010 General Availability V3.1 R2.32.48 12.00.02.ALL.15_PS0032.E48 Patchsets 32E48 08/24/2010 General Availability V3.1 R2.32.49 12.00.02.ALL.15_PS0032.E49 Patchsets 32E49 09/17/2010 General Availability

.

The following table is a list of V1 IBM-OEM TCS software released for image installations.

SW Version Production Version Contents Release Date G-DMS Note Remarks V3.1R2.28.5 12.00.02.ALL.15_PS0028.E05 Server Image Installation 08/13/2008 INF-08-001084 See Section 10.3 V3.1R2.32.2 12.00.02.ALL.15_PS0032.E02 Server Image Installation 10/31/2008 INF-09-000065 See Section 10.3 V3.1R2.32.9 12.00.02.ALL.15_PS0032.E09 Server Image Installation 12/22/2008 INF-09-000192 See Section 10.3 V3.1R2.32.24 12.00.02.ALL.15_PS0032.E24 Server Image Installation 06/05/2009 See Section 10.3

The following table is a list of cumulative updates that require the use of MOPs (Manual Operation Procedures), including the location of the respective documents in G-DMS. Unless specifically noted, these MOPs must be applied after system installation.Items recently released are marked with a star ( ).

Document Number Release Date

Released with

G-DMS Note Title

P30310-Q2523-Q120-04-76201 12/14/2007 PS13E04 INF-08-000226 IBM X3650T base firmware #4

Release Note Page 13 of 25 OpenScape Voice Server V3.1 R2.32.339

Document Number Release Date

Released with

G-DMS Note Title

P30310-X0692-R222-03-76201 05/05/2008 PS23E03 INF-08-000392 Install Additional RAM Mem on Installed IBM x3650 P30310-Q1410-Q101-44-7620 05/28/2008 PS23E07 INF-08-000390 Modified Split Mode Upgrade Linux P30310-Q1410-Q101-44-7620 05/27/2008 PS23E07 INF-08-000390 Modified Split Mode Upgrade P30310-Q2616-Q120-05-7620 08/08/2008 PS28E06 INF-08-001068 IPMIUTIL Package Update P30310-Q2590-Q120-07-7620 10/31/2008 PS32E02 INF-09-000075 Upgrade EKS Set1 P30310-Q2608-Q120-06-7620 10/31/2008 PS32E02 INF-09-000076 Upgrade of SLES9 SP3 Set3 P30310-Q2638-Q120-06-7620 09/30/2009 PS32E38 Upgrade of SLES9 SP4 and PCL

Notes: 1 This MOP can be installed on V3.1R2 systems with patchset P23E03 and above.

Release Note Page 14 of 25 OpenScape Voice Server V3.1 R2.32.339

7 Changes in this Release

7.1 Change Requests (FRNs)

FRN Number Title Note

7.2 Fixed IBM OEM ICTS Tickets

Set Patch ICTS Ticket Description E49 E1770 NA05518752 System backup of the TCS nodes fails using sFTP server

E49 E1781 NA05759517 System backup of the TCS nodes fails using the default backup profile

Release Note Page 15 of 25 OpenScape Voice Server V3.1 R2.32.339

8 Outstanding Problems

8.1 Outstanding ICTS Tickets for IBM-OEM TCS

ICTS Ticket Description Fixed In None

Release Note Page 16 of 25 OpenScape Voice Server V3.1 R2.32.339

9 Installation Instructions

9.1 RapidStat Report

A RapidStat report must be generated after performing any upgrade or downgrade of the switch. This will help identify any problems that may be caused by the configuration change.

9.2 Base OS for an External OpenScape Voice Assistant/Media Server

When the OpenScape Voice Assistant or Media Server is installed on an external server (i.e., a non-integrated environment), the base operating system for that server must be SLES 10 SP1. See G-DMS INF-08-000313

See the OpenScape Voice Assistant or Media Server Release Notes for further installation instructions.

9.3 Installing new 3.1 servers

Beginning with v3.1 R2, new installations must use an “image installation” process.

Image installation is described in the following document:

• “OpenScape Voice Cookbook for Image Installation.pdf “ in G-DMS INF-08-000762.

Notes regarding image installations:

• Each x3650T server requires 8 GB of system memory (see INF-08-000392). The FSC RX-330 already comes with 8 GB of system memory.

• Image installation applies only to new (fresh) v3.1 R2 installations, not to upgrades.

• Restore of a DB backup taken from a previously-installed (non-image) system is NOT permitted.

• Following the image installation, it may be necessary to:

o update the system with the latest patchset or E-patchset. See Section 4.4 for the current software releases supported and links to the patchsets, software image & software installation wizard.

o install the license file(s)

o install/execute one or more MOPs (see section 7).

• Important note if installing a layer 3 node separated IBM cluster:

o Very intermittently, image installation may fail. This is a very intermittent timing problem. The workaround is to repeat the installation procedure.

Installation Time:

– Simplex: approximately 1 hour – Cluster: approximately 1 hour

Release Note Page 17 of 25 OpenScape Voice Server V3.1 R2.32.339

9.4 Upgrading V3.1 R2 servers

Bug corrections are provided using patchsets and emergency patchsets. They must be installed using the Rolling Upgrade procedure described in the Installation and Upgrade Guide (P31003H8031J103017631). If necessary, patchsets should be removed using the Rolling Downgrade procedure described in the same document.

Patchsets can be usually installed all in a single Rolling Upgrade. Please consult Section 9.3 New Installations to know if restrictions require patchsets to be installed in more than one Rolling Upgrade, and also to know which MOPs must be executed in addition to the patchsets.

1. Starting patchset level must be PS32E33.

2. Delete files still resident in the /software/patch/12.00.02.ALL.15 directory.

3. Copy PS32E34 through PS32E37 to the patch directory (above).

4. Using the OpenScape Voice Assistant, install the patchsets in a single rolling upgrade.

Update Time:

– Approximately 20 minutes.

Please consult E-Doku document Software Maintenance Manual (P31003H8031S114017620) for instructions if problems occur during the Rolling Upgrade.

9.5 Configure endpoint attribute for media server

In order to be able to establish a single step conference inviting a third SUT party into the conference, the configured SIP endpoint for the media server needs to be provisioned with the endpoint attribute: Ignore Incoming OTG. When this flag is provisioned on the Media Server’s endpoint in the TCS DB, the TCS will not answer the calls when a call is queued in a MLHG that has the Intercept treatment Answer flag set to Yes. This parameter is mandatory for the SIP endpoints configured for the media server. Forcing the Answer flag on MLHG announcements to No for the Media Server

This attribute is not exposed to the TCS Assistant and therefore must be set via the ‘startCli’ tool that is available on the TCS nodes itself.

The attribute is set, on either of the 2 TCS nodes, as follows:

1) Start a secure remote shell to the TCS node (e.g. using putty) or log in to the TCS node with the srx user account.

2) Call startCli at the srx user prompt

3) Enter sysad as login name (no password is required)

4) Select 6 ‘Application Management’

5) Select 5 ‘Zone Management’

6) Select 2 ‘Modify Endpoint’

7) Enter the name of the just created Media Server (in the example: MsTAS1)

8) Hit Enter (choosing the defaults) until the line: Change SIP endpoint attributes as bitmap sums? (default: true): appears and enter false

9) Hit Enter (choosing the defaults) until the line: Ignore Incoming OTG <0=false|1=true|-1=unchanged> (default: -1): appears and enter 1.

Release Note Page 18 of 25 OpenScape Voice Server V3.1 R2.32.339

10) Hit Enter (choosing the defaults) until the command gets executed.

Release Note Page 19 of 25 OpenScape Voice Server V3.1 R2.32.339

10 Important Information

10.1 Open Source Software

The product contains Open Source Software developed by third parties and licensed under an Open Source Software License. Such software files are protected by copyright. Your rights to use the Open Source Software beyond the OpenScape Voice application are governed by the relevant Open Source Software license conditions.

Your compliance with such license conditions will entitle you to use the Open Source Software as foreseen in the relevant license. In the event of conflicts between Siemens Enterprise Communications GmbH & Co. KG license conditions and the Open Source Software license conditions, the Open Source Software conditions shall prevail with respect to the Open Source Software portions of the software.

Open Source Software is licensed free of royalties, i.e. no fees are charged for exercising the licensed rights, whereas fees may be charged for reimbursement of costs incurred by Siemens Enterprise Communications GmbH & Co. KG to provide or distribute the software. The license conditions can be found in the source code or at the following Internet websites:

- ASF Apache License - OSI Common Development and Distribution License - PERL Artistic License - Vovida Software License - OpenSSL License

Warranty

Siemens Enterprise Communications GmbH & Co. KG gives no warranty for Open Source Software programs embedded with OpenScape Voice if such programs are used in any manner other than originally intended by Siemens Enterprise Communications GmbH & Co. KG. In such cases, warranty, if any, shall be provided by the authors of the Open Source Software as described in the license conditions referred above.

Siemens Enterprise Communications GmbH & Co. KG specifically disclaims any warranties for defects caused by altering any Open Source Software program or its application or configuration within OpenScape Voice. Technical support, if any, will only be provided for unmodified software.

You have no warranty claims against Siemens Enterprise Communications GmbH & Co. KG in the event that the Open Source Software infringes the intellectual property rights of a third party.

Release Note Page 20 of 25 OpenScape Voice Server V3.1 R2.32.339

10.2 Knowledge Base documents

The following table contains links to G-DMS documents with procedures and other information that is not included in the Product Documentation. Such documents are provided directly by System Test, GVS and Development, including certain MOPs.

Release Date G-DMS Note Title

09/20/2007 INF-07-001256 MOP Q2245 IBM-RSA Firmware Upgrade for x346 10/23/2007 INF-08-000069 HiPath 8000 Solution USB device resolution procedure 10/22/2007 INF-08-000786 HiPath 8000 Solution Upgrade Guide 10/22/2007 INF-08-000789 HiPath 8000 Solution Configuration Guides 01/31/2008 INF-08-000391 MOP Q2514 Qos Profile Adaption 10/29/2008 INF-09-000069 Modify_Treatments Script for IBM-OEM

Note: Items recently released are marked with a star ( ).

10.3 Important Information for “Easy IP Address Changing”

Please consult Section 11 Workarounds for important information regarding Easy IP Address Changing.

10.4 The BG Needs a Default NP

The BG needs a default NP! For just in case we create a subscriber and forgot to assign it for a PNP that subscriber will be assigned the default PNP (this scenario is true for the soapCli only. In the Assistant we create the Subscriber within the PNP and not from the BG dialog).

If we use the soapCli to create BG the system will assign the E164NANP as default NP to the BG (system requirements) but we must change that E164NANP by a PNP specified by the administrator. If we do not do that, and than we create a subscriber without assigning him to a PNP, This subscriber will have the BG default NP (in our case the E164NANP) as his NP. This is a problem because the E164NANP is not meant for Private subscriber but for Global translation. We must bear in mind that if we have 10 BGs and every BG has 100 PNP, all will use the E164NANP for translation and routing.

The Assistant by assigning a default PNP to the BG it is preventing the possibility of making the mistake to have a BG with the E164NANP as a NP.

The soapCli is unable to read the administrators mind and choose a specific PNP to assign it to the BG! For this reason the soapCli used the E164NANP as a default. The Assistant has a better solution which is creating a PNP to the BG.

10.5 Important Information for FRN0497 (Remote Patching Capability)

While installing a new patchset, it will be verified that all emergency patchsets being simultaneously rolled out are obsoleted. It will not be possible to roll in a new patchset that does not obsolete all emergency patchsets. For example, if the system is currently at PS7E4, and the user wants to install PS8, but PS8 does not contain all the fixes from 7E4, the user will not be able to roll from PS7E4 directly to PS8. The user will have to either roll to a later patchset which does include all the fixes form 7E4 (i.e. PS9) or first remove the E patches which are not obsoleted by PS8 (i.e. PS7E4 and PS7E3 need to be removed in one operation if they are not obsoleted by PS8, then it is possible to roll directly from PS7E2 to PS8). This restriction is true for both the new GUI-based

Release Note Page 21 of 25 OpenScape Voice Server V3.1 R2.32.339

method of rolling upgrade, and the traditional Cli-based method (using the setup_rtp_unit script), which has been updated along with the introduction of FRN0479.

10.6 Important Information for FRN3656 (ONS Silent Handover)

After patch PS32E38 has been installed and the TCS Server has been brought to state 4, execute the following command as root in order to provision the NO_ANN treatment:

/unisphere/srx3000/callp/tools/ms_assign_single_tr.sh

Note: This script requires that media server provisioning has already been performed according to a MOP corresponding to the media server being used.

10.7 Configuration of the CIP Addresses

Certain V3.1 installations may require the CIP addresses, used by the two LAN interfaces that connect both nodes of a cluster, to be changed by the user if the default addresses conflict with the existing network.

Please consider the following guidelines when choosing new CIP addresses:

1. Three different subnets must be defined: one for the first physical link between the nodes, one for the second physical link, and one for the “logical” cross-connection (which connects the nodes using the first or second physical link depending on their availability).

2. All subnets must have the same subnet mask, defined by parameter cip_netmask. The mask must support at least four IP addresses (e.g. 255.255.255.252): one for each node plus the network and broadcast addresses (respectively first and last address in the range).

3. Parameters node_0_cip0 and node_1_cip0 must belong to the first physical subnet, while node_0_cip1 and node_1_cip1 must belong to the second physical subnet. Be careful not to assign the first and last addresses in the range defined by the subnet mask.

4. Parameters node_0_cip_logical and node_1_cip_logical must belong to the logical subnet. In addition, parameters cip_network and cip_broadcast must be equal, respectively, to the first and last addresses in the range defined by the subnet mask.

Note: parameters node_1_cip0, node_1_cip1 and node_1_cip_logical are ignored in simplex systems.

10.8 License Activation

OpenScape Voice V3.1 introduces three types of licenses: End-user License, which controls the number of BGLs assigned to the system, Dynamic License, which controls the number of SIP subscribers that are concurrently registered in the system, and Trunking License, which controls the number of concurrent calls between two SIP NNI endpoints. A license file is required in order to administer local endpoints, registered subscribers, trunking calls and associated servers. Without this file, the system will allow up to 10 end users, 10 registered subscribers and 10 trunking licenses. In case the database is already configured with more endpoints than the license limits, an alarm will continually be raised until the appropriate license is installed.

For the detailed description of licensing concepts, please refer to the latest customer document, which is OpenScape Voice V3.1 R2, Delta Specifications, System Description, Issue 4, Section 3.7, Licensing Enhancement. (P31003H8031Y111017618)

Release Note Page 22 of 25 OpenScape Voice Server V3.1 R2.32.339

A license file must be purchased by the customer through the sales channels. This XML file is specific for the type of system and requires the MAC address of the node’s administration interface (bond0). The MAC address can be retrieved by logging on as root user and using the ifconfig command. In duplex configurations, licenses are required for both nodes.

The type of system (name and version) is identified by parameters HiQ/Main/ProductType and HiQ/Main/ProductVersion which are pre-configured at installation time based upon the node.cfg file. Licenses will not be activated if those parameters are not set correctly.

To install the license files, if the computer was previously defined as a License Server in the node.cfg file during the TCS Server installation, copy the XML file into directory /opt/unisphere/srx3000/cla/import in both nodes.

After the license files are installed in both nodes, the license will be activated in 5 minutes if installed in a running system that had no previous license. The current licensing state can be determined using the CLI options 6>1>1>11>1, or from the main view of the communication processor in Assistant.

Note: If an invalid license file is installed inadvertently, it's not necessary to re-install the server. The system can accept a new valid license file.

Release Note Page 23 of 25 OpenScape Voice Server V3.1 R2.32.339

11 Workarounds

1. Easy IP Address Changing due to an open issue with DVDs 7, 8 and 9 the following workaround is required prior to using EZ-IP (IFGUI update) to change IP addresses of the OpenScape Voice Server::

• For Integrated Systems:

• uninstall the integrated applications

• execute EZ-IP to change the OpenScape Voice Server IP addresses, as usual

• create a new configurator file for applications install

• install the integrated applications

• For Non-integrated Systems:

• execute EZ-IP to change the OpenScape Voice Server IP addresses, as usual

• ‘remove’ and ‘add’ the OpenScape Voice Server on the Assistant

2. Use Nero6 to burn DVD images

When using NERO v6 to burn an OpenScape Voice installation DVD from the image provided, the following procedure must be performed:

• The command line utility NeroCmd that comes with Nero v6 needs to be used. It is usually located in the Nero directory. If not, perform a file search for NeroCmd.

• Use the NeroCmd utility with the following parameters in a command line window:

- NeroCmd --write --real --drivename X --dvd --image ISO_IMAGE_FILE.iso

- Where X is the letter of the drive (usually D, E, F, etc.) and ISO_IMAGE_FILE.iso is the ISO image you want to burn.

• DVD-R media is recommended when burning DVD images

3. Convedia CMS-3000 V3.11.x workarounds

• Manually verify the CMS configuration does not contain duplicate IP addresses for the media port (Convedia ticket #11796).

• Set time and date in CMS manually after powering on or rebooting, or connect to an NTP server (Convedia ticket #14133)

• Use CLI until both nodes are up & CMP is reconnected.

4. Administrators might not be able to login to the CMP under the following conditions:

Using an offboard Assistant; the OpenScape components are also installed on this offboard server and the number of users being managed by this Assistant is > 5000 (number of BGLs over all OpenScape Voice Servers the Assistant is managing)

• Workaround: the OpenScape WebClient service (not used for Assistant but present since there is only one common deployment) can be disabled via the following commands:

- sh /etc/init.d/symphoniad stop

Release Note Page 24 of 25 OpenScape Voice Server V3.1 R2.32.339

- rpm -e CA2-OSC-WEB-STANDARD

- sh /etc/init.d/symphoniad start

Release Note Page 25 of 25 OpenScape Voice Server V3.1 R2.32.339

12 Restrictions

12.1 Restrictions for this current release.

• TCS Node naming restrictions for new installations and split node upgrades. See G-DMS INF-07-000994.

12.2 Restrictions for this product version

• TLS / SRTP related restrictions:

o Gateways Cisco 3725, all Mediatrix gateways, HG3540 (with 4K V3.0) and RG2700 do not support TLS and also do not support SRTP. Calls from a secure endpoint to one of these gateways are negotiated from SRTP to RTP.

o Gateways HiPath 4000 v4.1 HG3540/HG3500 can support SRTP, however their COT parameter BKDU (BCCC) must NOT be set on the IP trunking COT to the OpenScape Voice Server

o The following SIP endpoints do not support SRTP but can negotiate from SRTP to RTP: OptiPoint 150S, Wireless WL2, analog adapters AP11xx, Convedia CMS1000/CMS 3000, and IPUnity v3.1.

o When using TLS/SRTP, make sure to configure the network time server parameters on the OpenScape Voice Server; OpenScape Voice Endpoints; gateways connecting to the OpenScape Voice Server; OpenScape Media Server. Secure calls cannot be made if the time parameters are out of sync.

o Cisco V7 and V8 7940/7960 series IP phones do NOT negotiate from SRTP to RTP. Secure calls to these phones will fail.

• DVD-R media is recommended when burning OpenScape Voice DVD images.

• OpenScape One Number Service related restrictions:

o Home DNs and BGLs must be configured in fully qualified E.164 format (including country code)

o These OpenScape Voice subscriber features are not available to users of ONS from an ONS client (e.g. the OpenScape V3 Rich Client), in cases where ONS /= OND: Executive Override; Simultaneous Ringing; Serial Ringing; Call Pickup Group/Directed; DND; Selective Call Acceptance/Rejection; Anonymous Caller Rejection; Remote Activation; Night Bell Call Pickup; Hot Desking; System Call Forwarding (except for Call Forwarding-Dependable); post-dialing of DTMF.

o Provisioning of a Call Forward-Dependable target is required for ONS BGLs, for backup routing purposes in case of loss of connectivity between the OpenScape Voice Server and the ONS application or application failure.

o OpenScape Voice devices which are to be used for ONS (ONDs) must:

• Be configured in the OpenScape Voice (BGL attributes) for CSTA with "Siemens Type 1" for OptiPoints, "CSTA Over SIP" for OpenStage.

o Held calls are cleared during RU. Also, active calls should be terminated before RU since it requires a restart of the RC and OSC to disconnect existing calls.