OpenScape UC Application V7 Installation and Upgrade, Installation Guide, Issue 12

Documentation
OpenScape UC Application V7
Installation and Upgrade
Installation Guide
A31003-S5070-J100-12-7631
Siemens Enterprise Communications

www.siemens-enterprise.com
Our Quality and Environmental Management

Systems are implemented according to the
requirements of the ISO9001 and ISO14001 standard
certified by an external certification company.
Copyright Siemens Enterprise

Communications GmbH & Co. KG02/2013
Hofmannstr. 51, D-80200 Mnchen
Siemens Enterprise Communications GmbH & Co. KG
is a Trademark Licensee of Siemens AG
Reference No.: A31003-S5070-J100-12-7631
The information provided in this document contains
merely general descriptions or characteristics of
performance which in case of actual use do not always
apply as described or which may change as a result of
further development of the products. An obligation to
provide the respective characteristics shall only exist if
expressly agreed in the terms of contract. Availability
and technical specifications are subject to change
without notice.
Siemens Enterprise Communications

www.siemens-enterprise.com
OpenScape, OpenStage and HiPath are registered

trademarks of Siemens Enterprise
Communications GmbH & Co. KG.
All other company, brand, product and service names
are trademarks or registered trademarks of their
respective holders.
Contents
History of Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1 About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 Target Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 How to Use This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3 Related Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4 Documentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4.1 In Countries other than the U.S. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4.2 In the U.S.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.5 Data Protection and Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19
19
19
20
22
22
22
22
2 General Preparations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1 Deployment Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2 Installation Process Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3 Information Provision by the Customer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4 Domain System Environment Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
25
25
27
30
32
3 Providing Virtual Computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

3.1 Installing Virtual Computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
3.1.1 Requirements on the Host Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
3.1.2 Overview of the VM Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
3.1.3 VMware Features and OpenScape UC Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
3.1.4 Restriction of the Product Application and Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
3.1.4.1 Cold Stand-by Availability Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
3.1.4.2 Warm Stand-by Availability Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
3.1.5 Settings for creating a VM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
3.1.6 VM Parameters under Edit Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
3.1.7 Installing the Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
3.1.8 Installing the VMware Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
3.1.8.1 Installing the VMware Tools on SLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
3.1.9 Computer Time Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
3.1.9.1 Deactivating the Time Synchronization by VMware Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
3.1.9.2 Configuring the NTP Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
3.1.10 Using Virtual Appliance for Small Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
3.1.10.1 General Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
3.1.10.2 Major Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
3.1.10.3 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
3.1.11 Using Virtual Appliance for Large Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
3.1.11.1 General Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
3.1.11.2 Major Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
3.1.11.3 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
3.2 Operating System Update Consequences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
4 Installing and Configuring the Computer and Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1 File System and Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2 SLES Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.1 First Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.2 Partitioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.2.1 Creating the /boot Partition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A31003-S5070-J100-12-7631, 02/2013
OpenScape UC Application V7 Installation and Upgrade, Installation Guide
115
116
119
119
123
125
Contents
4.2.2.2 Creating the swap Partition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.2.2.3 Creating the LVM2 partition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.2.4 Creating the Logical Volume Group OpenScape UC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.2.5 Creating the Logical Volume UC1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.2.6 Creating the Logical Volume UC2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.3 Selecting SLES Software Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.4 Network-related Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.5 No support of UEFI (Unified Extensible Firmware Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3 Checking the Partitioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4 Configuring Multiple Network Interface Cards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.1 With Bonding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.1.1 General Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.1.2 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.2 Without Bonding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5 Configuring the File System Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6 Using FQDNs for Very Large Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.1 General Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.2 FQDNs when using several Network Boards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.2.1 FQDN and Bonding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.2.2 FQDN without Bonding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.3 List of FQDNs to be resolved for every Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
127
129
131
133
136
139
151
162
163
165
165
165
167
180
181
184
184
184
184
185
186
5 Installing the OpenScape UC Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

5.1 Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
5.1.1 Verifying the Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
5.1.2 Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
5.1.3 Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
5.2 Configuring the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
5.2.1 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
5.2.2 Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
5.2.2.1 Example of Deployment Scenario Small Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
5.2.2.2 Example of Deployment Scenario Large Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
5.2.2.3 Example of Deployment Scenario Very Large Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
5.3 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
5.3.1 Providing the Installation Sources in an Installation Repository in osc-setup . . . . . . . . . . . . . . . . . . 234
5.3.1.1 Needed ISO Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
5.3.1.2 Creating a Repository in osc-setup by using local Installation Sources . . . . . . . . . . . . . . . . . . . 237
5.3.1.3 Creating a Repository in osc-setup by using remote Installation Sources . . . . . . . . . . . . . . . . . 243
5.3.2 Installing the Small Deployment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
5.3.3 Installing the Large Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
5.3.3.1 Installation on the Application Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
5.3.3.2 Requirements for Installing Additional Computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
5.3.3.3 Installation on the Frontend Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
5.3.3.4 Installation on the Media Server Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
5.3.3.5 Starting and Rebooting Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
5.3.3.6 Resolving Installation Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
5.3.4 Installing the Very Large Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
5.3.4.1 Installation on the Application Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
5.3.4.2 Requirements for Installing Additional Computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
5.3.4.3 Installation on the Frontend Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
5.3.4.4 Installation on the Media Server Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
5.3.4.5 Starting and Rebooting Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
A31003-S5070-J100-12-7631, 02/2013
Contents
5.3.4.6 Resolving Installation Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.4 Checking the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4.1 Initial Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4.2 Checking with Rapidstat UC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4.2.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4.2.2 Major Deployments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4.2.3 List of available Checks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4.2.4 Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4.2.5 Example Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5 Trouble Ticket . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
345
347
347
349
349
349
351
355
357
358
6 Configuring the OpenScape UC Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.1 Lists of the Ports to be opened . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1.1 Representation of the Port Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1.1.1 Basic Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1.1.2 Advanced Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1.2 Lists of the Ports to be opened for Integrated Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1.3 Lists of Ports to be opened for Small Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1.4 Lists of Ports to be opened for Large Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1.5 Lists of Ports to be opened for Very Large Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2 Routing Schemas between the Application Computer and Frontend Computer . . . . . . . . . . . . . . . . . . . .
6.3 Connecting an OpenScape Voice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1 Opening Port 1040 on the PBX Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.4 Connecting a HiPath 4000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.4.1 Connection of an OS UC Appl. via an OSV to a HiPath 4000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.5 Installing the Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.6 Creating the OpenScape UC Application Users in the CMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
359
359
360
360
360
363
386
411
444
476
479
480
484
484
485
485
7 Client Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487

7.1 OpenScape Extensions for Microsoft Outlook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487
7.1.1 Usage Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488
7.1.2 Installing the OpenScape Extensions for Microsoft Outlook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488
7.1.2.1 Requirements for Setting up OpenScape Extensions for Microsoft Outlook. . . . . . . . . . . . . . . . 489
7.1.2.2 Installation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489
7.1.2.3 Initial Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490
7.1.2.4 How to Perform the initial Configuration for Access via your OpenScape User Account . . . . . . 491
7.1.2.5 How to Perform the initial Configuration for Access via your Windows User Account . . . . . . . . 493
7.1.2.6 How to Configure Access via Single Sign-On Initially . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495
7.1.3 Installation in a Terminal Server Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497
7.1.3.1 Requirements for the Installation in a Terminal Server Environment . . . . . . . . . . . . . . . . . . . . . 497
7.1.3.2 How to Perform the Installation in a Terminal Server Environment. . . . . . . . . . . . . . . . . . . . . . . 497
7.1.3.3 User Configuration Files for Terminal Server Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498
7.1.4 Repairing, Upgrading and Uninstalling the OpenScape Extensions for Microsoft Outlook . . . . . . . . 498
7.1.4.1 How to Perform a Repair (Update) Installation for the OpenScape Extensions for Microsoft Outlook
499
7.1.4.2 How to Perform an Upgrade Installation for the OpenScape Extensions for Microsoft Outlook . 499
7.1.4.3 How to Uninstall the OpenScape Extensions for Microsoft Outlook . . . . . . . . . . . . . . . . . . . . . . 500
7.1.4.4 Repairing and Upgrading via msi-File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501
7.2 OpenScape Extensions for Lotus Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502
7.2.1 Installing the OpenScape Extensions for Lotus Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502
7.2.1.1 Requirements for Setting up OpenScape Extensions for Lotus Notes . . . . . . . . . . . . . . . . . . . . 503
7.2.1.2 Installation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503
7.2.1.3 Repairing, Upgrading and Uninstalling the OpenScape Extensions for Lotus Notes . . . . . . . . . 506
A31003-S5070-J100-12-7631, 02/2013
Contents
7.2.1.4 How to Perform a Repair Installation for the OpenScape Extensions for Lotus Notes. . . . . . . . . 506
7.2.1.5 How to Perform an Upgrade Installation for the OpenScape Extensions for Lotus Notes . . . . . . 507
7.2.1.6 How to Uninstall the OpenScape Extensions for Lotus Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . 508
7.3 OpenScape Desktop Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508
7.3.1 How to Install the OpenScape Desktop Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509
7.4 OpenScape Click-to-Dial-Browser-Plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510
7.4.1 OpenScape Click-to-Dial-Browser-Plug-in. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511
7.4.2 Setting up the OpenScape Click-to-Dial-Browser-Plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512
7.4.2.1 How to Perform the Default Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513
7.4.3 Changing the Setup, Updating and Uninstalling the OpenScape Click-to-Dial-Browser-Plug-in . . . . . 517
7.4.3.1 Modifying the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518
7.4.3.2 How to Uninstall the Firefox Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518
7.4.3.3 How to Install the Firefox Support Retrospectively. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519
7.4.3.4 Update Installation (Repair) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519
7.4.3.5 How to Perform an Update Installation (Repair). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520
7.4.3.6 Uninstalling the OpenScape Click-to-Dial-Browser-Plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521
7.4.3.7 How to Perform the Uninstallation via the Setup File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521
7.4.3.8 How to Perform the Uninstallation via the Windows Control Panel . . . . . . . . . . . . . . . . . . . . . . . 522
7.5 The OpenStage Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523
7.5.1 Installing OpenStage Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524
7.5.1.1 How to Install the OpenStage Client Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524
7.5.1.2 How to Install the Phonebook Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529
7.5.1.3 How to Install the Call Log Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531
7.5.1.4 How to Configure the DSS Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533
7.6 OpenScape Client Integrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537
7.6.1 OpenScape Client Integrations Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537
7.6.2 Supported Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538
7.6.3 Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538
7.6.4 Setup Adjustments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
7.6.5 Installing the OpenScape Client Integrations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540
7.6.6 Updating and Uninstalling via the Setup File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543
7.6.6.1 How to Change Program Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
7.6.6.2 How to Update or Repair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545
7.6.6.3 How to Uninstall the Program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546
8 Installing the Mobile Client Facade Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549
8.1 Supported Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551
8.2 Installing the Mobile Client Facade Server on SLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552
8.2.1 Installation with the Help of the Installation Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552
8.2.2 Diagnosing the Facade Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559
8.2.3 Deployment of the Mobile Client using the Facade Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560
8.3 Updating the Mobile Client Facade Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
8.4 Uninstalling the Mobile Client Facade Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
9 Installing the OpenScape Web Collaboration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563
10 Installing and Configuring OpenScape Fusion for Google Apps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
10.1 Installing OpenScape Fusion for Google Apps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
10.1.1 Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
10.1.2 Installation on the Application Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
10.1.3 Installation on the Google Apps Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
10.1.3.1 Installing the Java Runtime Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
10.1.3.2 Installing the Google Apps Computer Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566
A31003-S5070-J100-12-7631, 02/2013
Contents
10.1.3.3 Installing the Google Apps Presence Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

10.2 Configuring the OpenScape Fusion for Google Apps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.2.1 Configuration on the Application Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.2.1.1 Creating Users in OpenScape UC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.2.1.2 Creating a technical User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.2.1.3 Configuring the LongLivedStatements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.2.1.4 Configuring the LongLivedStatements on a Front-End Computer . . . . . . . . . . . . . . . . . . . . . .
10.2.2 Configuration on the Google Apps Computer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.2.2.1 Settings of the Poll Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.2.2.2 Configuring the Presence Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.2.2.3 Configuring the LongLivedStatements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.2.2.4 Configuring the Google Apps Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.2.3 Google Domain Authentication Token . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.3 Upgrading OpenScape Fusion for Google Apps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.3.1 Upgrade on the Application Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.3.2 Upgrade on the Google Apps Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.3.3 Upgrading the Google Apps Computer Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.3.3.1 Upgrading the Google Apps Presence Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
567
568
568
568
569
569
571
572
572
573
574
574
575
576
576
576
576
577
11 Connecting the Microsoft Office Communication Server/Microsoft Lync Server . . . . . . . . . . . . . . .

11.1 Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.2 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.3 Installing the UCMA Proxy Web Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.3.1 Checking the Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.3.2 Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.3.3 Uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.4 User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.5 Installation and Configuration of the OpenScape Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
579
580
582
582
583
589
590
592
593
12 Connecting Instant Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

12.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2 Infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.3 Installing the Openfire Server on the Application Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.4 Installing the Openfire Server on the Instant-Messaging Server Computer. . . . . . . . . . . . . . . . . . . . . . .
12.5 Initial Configuration of the Openfire Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.5.1 Initial Configuration for Integrated Deployment, Small Deployment and Large Deployment . . . . . .
12.5.2 Initial Configuration for Very Large Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.5.2.1 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.5.2.2 Preparing the MySQL Database for Use with Openfire. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.5.2.3 Initial Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.6 Configuring the Openfire Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.7 User Data Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.8 Configuring the OpenScape Clients. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.8.1 Configuring the OpenScape Desktop Client Enterprise Web Embedded Edition. . . . . . . . . . . . . . .
12.8.2 Configuring the OpenScape Web Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.8.3 Configuring the OpenScape Mobile Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.9 Updating, Upgrading and Uninstalling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.9.1 Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.9.1.1 Updating the Openfire Server on the Application Computer . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.9.1.2 Updating the Openfire Server on the Instant-Messaging Server Computer . . . . . . . . . . . . . . .
12.9.2 Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.9.3 Uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
595
595
596
599
600
602
602
607
607
608
610
615
616
616
616
616
616
617
617
617
617
622
622
A31003-S5070-J100-12-7631, 02/2013
Contents
13 Groupware Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623

13.1 General Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623
13.2 Connecting Microsoft Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624
13.3 Connecting IBM Lotus Domino . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624
13.3.1 Preparations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624
13.3.1.1 Installing the OpenScape UC Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624
13.3.1.2 Creating the Notes User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 626
13.3.1.3 Creating the Notes Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 629
13.3.2 Installing the Domino Connector Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633
13.3.2.1 Connection to the Domino Groupware Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635
14 Additional Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637
14.1 Installing additional RPM Packages of the OpenScape UC Application . . . . . . . . . . . . . . . . . . . . . . . . . 637
14.1.1 Local Retrospective Provision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637
14.1.2 Remote Retrospective Provision by using NFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 638
14.1.3 Remote Retrospective Provision by using HTTPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 638
14.2 Installing additional Voice Portal Languages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 639
14.3 Installing additional Frontend Computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647
14.4 Installing additional Media Server Computers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647
14.5 Additional Installation of the OpenStage Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 649
14.5.1 Preparations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 649
14.5.2 Small Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650
14.5.3 Large Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654
15 Updating, Upgrading and Migrating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 659
15.1 Determining the Source Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 662
15.1.1 Determining the version in the CMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 662
15.1.2 Determining the version using the productInventory.sh script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663
15.1.3 Determining the version by means of the rpm command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663
15.1.4 Evaluation of the results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 664
15.2 Update and Upgrade Preparations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 665
15.2.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 665
15.2.2 Providing the Update/Upgrade Sources in a Repository in osc-setup . . . . . . . . . . . . . . . . . . . . . . . 671
15.2.2.1 Needed ISO Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 672
15.2.2.2 Creating a Repository in osc-setup by using local Update/Upgrade Sources . . . . . . . . . . . . . 674
15.2.2.3 Creating a Repository in osc-setup by using remote Update/Upgrade Sources . . . . . . . . . . . 681
15.2.3 Database Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 699
15.2.4 Preparing to the syncUC Fallback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707
15.2.4.1 Introducing syncUC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707
15.2.4.2 syncUC Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707
15.2.4.3 Fallback Preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 710
15.3 Updating the Application Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 711
15.3.1 Updating to a new Fix Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 711
15.3.1.1 Integrated Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 711
15.3.1.2 Small Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 711
15.3.1.3 Large Deployment and Very Large Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 716
15.3.2 Installing a Hotfix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 727
15.3.2.1 Small Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 727
15.3.2.2 Large Deployment and Very Large Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 730
15.3.3 Updating using the CMP (UI Patching) instead of osc-setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733
15.3.3.1 General Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733
15.3.3.2 Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 734
15.4 Upgrade and Migration Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745
A31003-S5070-J100-12-7631, 02/2013
Contents
15.5 Upgrading V3 R2 or V6 R0 Integrated Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 749

15.6 Upgrading V3 R2 or V6 R0 Small and Large Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 749
15.6.1 Upgrading Small Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 750
15.6.2 Upgrading Large Deployment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 771
15.6.2.1 Upgrading on the Application Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 773
15.6.2.2 Upgrading on the Frontend Computer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 782
15.6.2.3 Upgrading on the Media Server Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 786
15.6.3 Fallback after Abandoning the Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 800
15.6.3.1 Falling back using syncUC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 800
15.6.3.2 Falling back through Restoration in the CMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 800
15.7 Smooth Update/Upgrade of V3 R2, V6 R0 or V7 R0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 803
15.7.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 803
15.7.1.1 General Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 803
15.7.1.2 Major Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 804
15.7.1.3 External and internal IP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 805
15.7.2 Preparing the FQDNs in the Response Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 807
15.7.2.1 Response File on the BE1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 807
15.7.2.2 Response File on the FE1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 808
15.7.2.3 Response File on the MS1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 809
15.7.3 Copying from SysUC1 to SysUC2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 810
15.7.3.1 Copying RPM from BE1 to BE2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 810
15.7.3.2 Copying the UC Database from BE1 to BE2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 817
15.7.3.3 Copying from FE1 to FE2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 820
15.7.3.4 Copying from MS1 to MS2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 825
15.7.4 Switching from SysUC1 to SysUC2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 830
15.7.5 Upgrading SysUC1 to the Target Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 833
15.7.6 Switching from SysUC2 to SysUC1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 834
15.8 Upgrading V3 R2 or V6 R0 Small Deployment including a Hardware Change . . . . . . . . . . . . . . . . . . . . 837
15.9 Upgrading V3 R2 or V6 R0 Large Deployment including a Hardware Change . . . . . . . . . . . . . . . . . . . . 838
15.10 Upgrading V3 R2 or V6 R0 Small Deployment in Case of an unavailable LVM2 . . . . . . . . . . . . . . . . . 839
15.11 Upgrading V3 R2 or V6 R0 Large Deployment in Case of an unavailable LVM2 . . . . . . . . . . . . . . . . . 851
15.12 Upgrading V3 R2 or V6 R0 Small Deployment in Case of only one available LVM2 Partition. . . . . . . . 862
15.12.1 Upgrading without changing the LVM2 partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 862
15.12.2 Adjusting the LVM2 partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 863
15.12.3 Adding a Partition only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 879
15.13 Upgrading V3 R2 or V6 R0 Large Deployment in Case of only one available LVM2 Partition . . . . . . . 885
15.14 Migration from V7 Integrated Deployment to V7 Small Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . 887
15.15 Migration from V7 Small Deployment to V7 Large Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 899
15.16 Migration from V7 Small Deployment to V7 Very Large Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . 916
15.17 Migration from V7 Large Deployment to V7 Very Large Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . 916
15.18 Upgrading a 32-bit System to a 64-bit System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 937
15.18.1 Preparations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 937
15.18.2 Ugrading HiPath 8000 Assistant V3.0 32-bit to OS UC Appl. V3 R2 with OSV V4 R1 DVD5 64-bit . .
938
15.18.2.1 Backing up Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 938
15.18.2.2 Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 938
15.18.2.3 Falling back to HiPath 8000 Assistant V3.0 32-bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 938
15.18.3 Upgrading from OS UC Appl. V3 R2 with OSV V3.1 R3 32-bit or OSV V4 R1 32-bit to 64-bit. . . . 940
15.18.3.1 Backing up Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 940
15.18.3.2 Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 941
15.18.3.3 Falling back to the original Version with 32-bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 943
15.19 Changing the Hardware for V7 Small Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 944
A31003-S5070-J100-12-7631, 02/2013
Contents
15.20 Changing the Hardware for V7 Large Deployment and Very Large Deployment . . . . . . . . . . . . . . . . . 954
15.21 Migration from OpenScape ComAssistant to OpenScape UC Application . . . . . . . . . . . . . . . . . . . . . . 965
15.21.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 965
15.21.2 General Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 967
15.21.3 Preparations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 968
15.21.3.1 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 968
15.21.3.2 Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 969
15.21.3.3 Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 970
15.21.3.4 Installing the Migration Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 974
15.21.3.5 Connecting to the OpenScape UC Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 977
15.21.3.6 Common Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 983
15.21.3.7 Database Exports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 986
15.21.4 Migrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 990
15.21.4.1 User Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 990
15.21.4.2 Personal Address Book Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1002
15.21.4.3 Shared Address Book Migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1006
15.21.4.4 Team Migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1016
15.21.4.5 Call Journal Migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1020
15.21.4.6 OpenScape Xpressions Access Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1024
15.21.4.7 Disconnecting CA users from the PBX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1028
15.21.4.8 Creating a Trouble Ticket . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1028
16 Uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1029
A Hardening the OpenScape UC Application Computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1031
A.1 Hardening Settings in the Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1032
A.1.1 Hardening Physical Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1032
A.1.1.1 Using Boot/Setup Passwords. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1032
A.1.1.2 Applying Security Fixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1032
A.1.1.3 Security-related RPM Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1032
A.1.1.4 Umask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1033
A.1.1.5 Links in the temp Folder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1033
A.1.2 Network Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1034
A.1.2.1 Internet Daemon, "R"-Daemons and telnet Daemon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1034
A.1.2.2 Trivial FTP (TFTP), FTP, redx, Samba, nfs, rsync etc. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1034
A.1.2.3 Hardening Shared Folders NFS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1035
A.1.2.4 Sendmail Daemon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1035
A.1.2.5 SNMP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1035
A.1.2.6 Deactivating X-Server, KDE and GNOME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1035
A.1.3 User Account Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1036
A.1.3.1 Assigning and Setting Up User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1036
A.1.3.2 Built-In Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1036
A.1.3.3 Secured Linux Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1036
A.1.4 Access Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1037
A.1.5 Monitoring and Auditing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1037
A.1.6 Virus Scanner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1037
A.2 Hardening Settings in the OpenScape UC Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1038
A.2.1 No TTS or ASR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1038
A.2.2 Configuring the Media Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1038
A.2.3 Deactivating User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1040
A.2.4 Configuring the Security Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1040
A.2.5 Backing up the Response File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1041
10
A31003-S5070-J100-12-7631, 02/2013
Contents
B Using YaST instead of zypper or rpm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.1 General Operation of YaST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B.2 yast instead of zypper Ir . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B.3 yast instead of zypper ar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B.4 yast instead of zypper rr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B.5 yast instead of zypper se or rpm -q . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B.6 yast instead of zypper in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1043
1044
1048
1050
1057
1060
1073
C Installing Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1075

C.1 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1075
C.2 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1076
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1093
A31003-S5070-J100-12-7631, 02/2013
11
Contents
12
A31003-S5070-J100-12-7631, 02/2013
IG_HistoryOfChange.fm
History of Changes
History of Changes
Date
Changes
2012-03-05
First draft of the setup and upgrade guide for OpenScape UC Application V7. It differs
from the documentation of the previous version among other things in the following:
2012-03-05
New deployment scenario Standard Duplex (very large) (see Section 2.1, Deployment FRN4402
Scenarios, on page 25). It uses the MySQL DB instead of the Solid DB (see for
example Section 5.1.3, Database, on page 194, step 11 on page 221 and Section
6.1.5, Lists of Ports to be opened for Very Large Deployment, on page 444)
2012-03-05
Update and upgrade updated (see Chapter 15, Updating, Upgrading and Migrating) FRN4513
2012-03-05
Section 15.14, Migration from V7 Integrated Deployment to V7 Small Deployment, on FRN4514

page 887andSection 15.15, Migration from V7 Small Deployment to V7 Large
Deployment, on page 899
2012-03-05
ISO files are the only installation source of the OpenScape UC Application (see Section FRN4567
5.2.2, Procedure, on page 198 and Section 5.3.1, Providing the Installation Sources
in an Installation Repository in osc-setup, on page 234).
2012-03-05
SLES 11 SP1 must have been installed on the application computer, the frontend
computers, and the media server computers (see for example point 1 on page 116).
FRN4828
2012-03-05
The Solid DB V4.5 has been replaced with V6.5 (see Section 5.1.3, Database, on
page 194).
FRN 5154
2012-03-05
The information about bonding does not only apply for the application computer but
FRN5018
also for possibly available frontend computers, media server computers, Mobile Client
Facade server computers, and Openfire server computers (see Section 4.4.1.1,
General Considerations, on page 165).
2012-03-05
List of required SLES RPM packages updated (see step 52 on page 140)
2012-03-05
Installation of the OpenScape UC Application using the osc-setup script (see

Section 5.3.1, Providing the Installation Sources in an Installation Repository in oscsetup, on page 234 and for example Section 5.3.2, Installing the Small Deployment,
on page 263)
2012-03-05
The RPM OpenScapeUC_ssdpaddons is always automatically included in the setup

(see for example step 10 on page 267).
2012-03-05
No support of UEFI (Unified Extensible Firmware Interface) as alternative to the BIOS CQ00199595
(see step 5c on page 46, Section 3.1.7, Installing the Operating System, on page 58
and step 92 on page 162)
2012-03-05
Connecting Lotus Domino is not released for Standard Duplex (very large) (see
Section 13.3, Connecting IBM Lotus Domino, on page 624).
2012-03-05
Information about fallback solutions (syncUC) and partitions updated:

Section 4.1, File System and Operating System, on page 116 updated.
Section 4.2, SLES Installation, on page 119 updated.
Section 15.2.4, Preparing to the syncUC Fallback, on page 707 added.
Section 15.6.3.1, Falling back using syncUC, on page 800 added.
2012-03-05
Configuration after upgrading the Openfire server added (see step 41 on page 769 and CQ00200560
step 38 on page 798)
2012-03-05
Uninstalling the OpenScape UC Application is not supported (see Chapter 16,

Uninstallation).
A31003-S5070-J100-12-7631, 02/2013
Reason
FRN4479
History of Changes
Date
Changes
Reason
2012-03-05
Port 9000 (default port) of the media server must be open for communication to the
system monitor (see Table 37 on page 365, Table 55 on page 388, Table 76 on page
426 and Table 96 on page 459).
2012-03-13
Added: Installation of the RPM packages for voice conferences (see for example Table
8 on page 235, step 16 on page 275, step 14 on page 306, step 14 on page 339, step
14 on page 753)
2012-03-25
Use of ISO files updated (see for example Section 5.3.1, Providing the Installation
Sources in an Installation Repository in osc-setup, on page 234)
2012-04-02
The Web Collaboration servers do not offer mutual reliability.
2012-04-02
If Thick Provision Lazy Zeroed can be applied while creating a virtual computer, this
option must be activated (see step 10 on page 52).
2012-04-06
OpenScape UC Application V7 R0 supports connections to OpenScape Voice V6 and FRN5144

V7 R0 but not to older OpenScape Voice versions (see Section 15.4, Upgrade and
Migration Tables, on page 745, Section 15.5, Upgrading V3 R2 or V6 R0 Integrated
Deployment, on page 749 and Section 15.14, Migration from V7 Integrated
Deployment to V7 Small Deployment, on page 887).
2012-04-06
Virtual computers are not supported for Standard Duplex (very large) (see Section 3.1,
Installing Virtual Computers, on page 33).
2012-04-06
Upgrading OpenScape UC Application V4 R0 to V7 R0 directly is not supported (see

Table 119 on page 745, Upgrade and Migration Table for Small Deployment and Large
Deployment and Section 15.6, Upgrading V3 R2 or V6 R0 Small and Large
Deployment, on page 749).
2012-04-06
Section 15.3.3, Updating using the CMP (UI Patching) instead of osc-setup, on page FRN4647
733 added. See also the note in step 6 on page 711 for example.
2012-04-06
Section 15.3.2, Installing a Hotfix, on page 727 updated.
2012-04-06
Mounting a USB stick added (see step 1 on page 198, step 1 on page 203, step 16 on
page 208, step 32 on page 213, step 1 on page 218, step 15 on page 223 and step 30
on page 228)
2012-04-06
Upgrading the Openfire server updated (see Section 12.9.2, Upgrade, on page 622) CQ00195116
CQ00204495
CQ00204715
2012-04-20
Using fsdik -l added to the description of how to mount a USB stick (see step 1 on
page 198, step 1 on page 203, step 16 on page 208, step 32 on page 213, step 1 on
page 218, step 15 on page 223 and step 30 on page 228)
2012-04-20
Note that referred to a load balancer arranged upstream of the Mobile Client Facade
server removed (see Chapter 8, Installing the Mobile Client Facade Server).
2012-04-20
Path on the Mobile Client Facade server computer changed (see step 11 on page 556, CQ00205358
step 13 on page 557, and step 17 on page 558)
CQ00201807
2012-04-20
Added: Important note for avoiding the error message with self-signed certificates (see CQ00201807
FRN4605
A31003-S5070-J100-12-7631, 02/2013
History of Changes
Date
Changes
Reason
2012-04-20
Openfire server and MySQL server

CQ00205991
The Openfire server is mandatory for Standard Duplex (very large). It must be
installed on a separate computer on which the MySQL server is set up also (see
step 10 on page 317 and Section 12.2, Infrastructure, on page 596).
Section 12.5, Initial Configuration of the Openfire Server, on page 602 updated.
Note regarding xmpp.cfg file usage removed. This file is no longer used (see step
4 on page 615).
2012-04-20
Upgrading OpenScape UC Application V4 R0 to V7 R0 directly is not supported:

Caption of Section 15.5, Upgrading V3 R2 or V6 R0 Integrated Deployment, on
page 749 and Section 15.6, Upgrading V3 R2 or V6 R0 Small and Large
Deployment, on page 749 changed.
First steps to updating the operating system on SLES 11 SP1 described (see step
1 on page 116 and step 1 on page 665)
Log files are deleted by updating or upgrading (see step 8 on page 669).
CQ00205786
2012-04-20
Two steps of creating a virtual computer have slightly changed for VMware ESXi 5.0
(see step 3 on page 42 and step 5 on page 44).
CQ00196353
2012-04-20
Sub-sections Phonebook application, Call log application and Configuring the DSS
keys of the OpenStage telephone added to section Chapter 7, Installing the
OpenStage Client.
2012-04-20
Update of the setup invocation parameters of the Mobile Client Facade server (see
step 2 on page 552).
2012-04-20
Update of the Mobile Client Facade servers using the -update parameter (see step 2 CQ00205277
on page 552).
2012-04-20
Description of the OCS status Offline updated (see Chapter 11, Connecting the
Microsoft Office Communication Server/Microsoft Lync Server)
2012-05-07
Several minor changes performed in Section 12.5, Initial Configuration of the

Openfire Server, on page 602.
Section Openfire authentication plug-in removed
Port 5222 replaced with port 5262 (see Section 6.1, Lists of the Ports to be
opened, on page 359).
2012-05-07
Information about Android mobile phones and iPhones changed as they are not
supported by OpenScape UC Application V7 R0 (see step 14 on page 557).
2012-05-07
Parameter serverName added in the properties.ini file for setting up the Mobile CQ00205276
Client Facade server (see step 11 on page 556).
2012-05-07
Several notes for using the xmpp.cfg file removed from the port tables. This file is no CQ00205991
longer used (see Section 6.1, Lists of the Ports to be opened, on page 359).
2012-05-07
In case of Standard Duplex (very large), the 64-bit version of the JRE must be installed CQ00208105
for the Openfire server (see steps 2 and 3 on page 600).
2012-05-07
In case of a setup on an OpenStage telephone the IP address of the load balancer

computer must be entered in the HTTP Server address field for Standard Duplex
(large and very large) (see step 9 on page 555, 15 on page 557 and 22 on page 559).
2012-05-07
Port 5262 need not be opened towards the Desktop client computer (see Section 6.1, CQ00207389
Lists of the Ports to be opened, on page 359).
A31003-S5070-J100-12-7631, 02/2013
CQ00208060
History of Changes
Date
Changes
Reason
2012-05-07
Video conferences for Standard Duplex (large and very large) require all media server
computers to support SSE2.x (Streaming SIMD Extension) among other things.
SSE4.x is no longer needed (see for example Chapter 4, Installing and Configuring
the Computer and Operating System).
2012-05-07
All required voice conference languages must be installed again after a migration to CQ00208636
Standard Duplex (large) or after an upgrade (see step 14 on page 753, step 12 on page
788 and step 50 on page 912).
2012-05-07
Connecting Lotus Domino is supported for Standard Duplex (very large) with
restrictions only (see Section 13.1, General Considerations, on page 623).
2012-05-07
After an update and upgrade, TTS and ASR must be started manually (see step 9 on CQ00208678
page 713 and step 34 on page 724).
2012-05-07
More detailed description of how to update the Openfire server to a fix release or a
CQ00208688
hotfix (see Section 12.9.1.2, Updating the Openfire Server on the Instant-Messaging
Server Computer, on page 617)
2012-05-07
Installation medium for the Mobile Client Facade server updated (see step 1 on page CQ00208590
552)
2012-05-23
Minor changes in Chapter 12, Connecting Instant Messaging
CQ00209849
2012-05-23
Section 8.3, Updating the Mobile Client Facade Server, on page 561 added.
CQ00208590
2012-05-23
Mobile Client Facade server:

Description of the properties.ini file updated (see step 11 on page 556).
A manual step for adding <Connector> in the server.xml file is no longer
required.
CQ00209548
2012-05-23
More information about the SI_DB_LOGON_PASSWORD parameter in configuration file

of the installation (see step 26 on page 226 and step 41 on page 231)
2012-05-23
The VMXNET 3 network adapter has a built-in driver for SLES 11 (see step 7 on page
49). As a result, section Replacing the Network Adapter has been removed.
2012-05-23
Updated migration command for the Migration from V7 Small Deployment to V7 Large
Deployment (see step 11 on page 902)
2012-05-23
Migration from V7 Large Deployment to V7 Very Large Deployment added:

Tables in Section 15.4, Upgrade and Migration Tables, on page 745 updated
Section 15.18, Migration from V7 Large Deployment to V7 Very Large
Deployment, on page 1028 updated.
2012-05-23
The following sections have been added:

CQ00208695
Section 15.10, Upgrading V3 R2 or V6 R0 Small Deployment in Case of an
unavailable LVM2, on page 839
Section 15.11, Upgrading V3 R2 or V6 R0 Large Deployment in Case of an
unavailable LVM2, on page 851
Section 15.12, Upgrading V3 R2 or V6 R0 Small Deployment in Case of only one
available LVM2 Partition, on page 862
Section 15.13, Upgrading V3 R2 or V6 R0 Large Deployment in Case of only one
available LVM2 Partition, on page 885
2012-05-23
Applications created with the Application Builder of the OpenScape UC Application

CQ00208628
V6 R0 must be removed before an upgrade to V7 R0 and recreated after the upgrade
(see step 3 on page 666, step 39 on page 768 and step 36 on page 797).
FRN5168, FRN4514
A31003-S5070-J100-12-7631, 02/2013
History of Changes
Date
Changes
2012-05-23
Setting up the Domino Connector server on the application computer is not supported
for Standard Duplex (very large) (see Section 13.1, General Considerations, on page
623 and Section 13.3, Connecting IBM Lotus Domino, on page 624).
2012-05-23
Information about the RPM packages you can install after migration from Integrated
Simplex to Standard Duplex (small) updated (see step 9d on page 890)
2012-06-15
Data restore step added to Section 15.10, Upgrading V3 R2 or V6 R0 Small

Deployment in Case of an unavailable LVM2, on page 839 and Section 15.11,
Upgrading V3 R2 or V6 R0 Large Deployment in Case of an unavailable LVM2, on
page 851 (see step 17 on page 848 and step 19 on page 860)
2012-06-15
Section 3.1.10, Using Virtual Appliance for Small Deployment, on page 69 added.
2012-06-15
Information about OpenScape Fusion for Google Apps added:

FRN5338
Table 37 on page 365 extended, Table 53 on page 385 added, Table 55 on page 388
extended, Table 72 on page 410 added, Table 73 on page 413 extended, Table 92
on page 443 added, Table 93 on page 447 extended and Table 113 on page 475
added
Section Installing and configuring OpenScape Fusion for Google Apps added
2012-06-15
Section 4.6, Using FQDNs for Very Large Deployment, on page 184 added.
2012-06-15

available LVM2 Partition, on page 862 changed or extended by minor aspects.
CQ00212203
2012-06-15
The XMPP domain name cannot be changed after the initial configuration anymore
(see step 8 on page 605, step 10 on page 609 and step 7 on page 612).
CQ00211706
2012-06-15
Openfire configuration steps changed, moved or deleted and screenshots updated

CQ002010218
(see Section 12.5.1, Initial Configuration for Integrated Deployment, Small
Deployment and Large Deployment, on page 602, Section 12.5.2.3, Initial
Configuration, on page 610, Section 12.6, Configuring the Openfire Server, on page
615 and Section 12.9.2, Upgrade, on page 622)
2012-06-15
ethereal library replaced with wireshark (see step 52 on page 140)
2012-06-15
CQ00212758
The following sections have been added:
Section 15.8, Upgrading V3 R2 or V6 R0 Small Deployment including a Hardware
Change, on page 837
Section 15.9, Upgrading V3 R2 or V6 R0 Large Deployment including a Hardware
Change, on page 838
Section 15.19, Changing the Hardware for V7 Small Deployment, on page 944
Section 15.20, Changing the Hardware for V7 Large Deployment and Very Large
Deployment, on page 954
2012-06-15
If you cannot upgrade to V7 R0 Integrated Simplex for subsequently migrating to

CQ00210483
V7 R0 Standard Duplex (small), migrate first to V6 R0 or older Standard Duplex (small)
and then upgrade to V7 R0 Standard Duplex (small) (see Section 15.14, Migration
from V7 Integrated Deployment to V7 Small Deployment, on page 887).
2012-06-15
Information about upgrade partition sizes moved (see step 12 on page 845, step 11 on
page 856, step 10 on page 868, step 10 on page 949 and step 10 on page 960)
2012-06-15
Added: Specifying the fully qualified domain name and the DNS servers to conclude
the operation system installation (see step 84 on page 159 to step 89 on page 160)
2012-06-15
Installation ISO file updated for OCS (see step 1 on page 589)
2012-06-15
Moved: Deleting the partition for file system backup (see step 1 on page 863)
2012-06-15
Added: Mounting a DVD (see step 1 on page 198 and step 1 on page 203 for example)
A31003-S5070-J100-12-7631, 02/2013
Reason
CQ00210847
FRN5060
History of Changes
Date
Changes
Reason
2012-06-15
We recommend using the fully qualified domain name (FQDN) of the computers (see
for example step 9 on page 201, step 10 on page 205, step 25 on page 210, step 26
on page 210, step 40 on page 215, step 41 on page 215, step 9 on page 220, step 23
on page 225, step 24 on page 225, step 38 on page 230, step 39 on page 230, step )
2012-06-15
If you use VMware ESXi V5, you need to deploy the network boards of type E1000 (see CQ00210186
Section 3.1, Installing Virtual Computers, on page 33 and step 7 on page 49).
2012-06-15
Scheduled tasks may have to be recreated after an update or upgrade (see step 5 on CQ00213287
2012-06-15
Uninstalling the OpenScape UC Application V7 R0 has been released for Integrated

Simplex only (see Chapter 16, Uninstallation).
2012-06-15
Information about the Web Collaboration server updated (see Chapter 9, Installing the FRN6040,
OpenScape Web Collaboration, step 40 on page 769 and step 37 on page 798)
CQ00211323
2012-06-15
Note for setting up the installation package for the Openfire server in one step removed CQ00213853
(see step 3 on page 600)
2012-06-15
For Standard Duplex (very large), the MySQL server and the MySQL client tools must CQ00214426
be installed before the Openfire server (see step 3 on page 600).
2012-06-15
Added: Reference to Section 4.2.5, No support of UEFI (Unified Extensible Firmware CQ00214447
Interface), on page 162 for avoiding problems when setting up SLES (see step 1 on
page 119)
2012-06-15
Upgrading the Mobile Client Facade server resets the properties.ini file to the
default values (see step 2h on page 554).
2012-06-15
For updates via the CMP, no proxies must be used for the application computer, the CQ00214598
frontend computers and the media server computers (see step 2 on page 734 and step
3 on page 735).
2012-06-15

available LVM2 Partition, on page 862 extended by Section 15.12.3, Adding a
Partition only, on page 879. See also step 5 on page 862.
2012-07-13
Data backup note updated (see before step 3 on page 840, before step 3 on page 852,
before step 1 on page 1029, before step 1 on page 944 and before step 1 on page 954)
2012-07-13
Using yast or zypper you may exclusively install SLES RPM packages. You must not CQ00215062
install any RPM packages of the OpenScape UC Application with yast or zypper. You
need to use osc-setup instead (see Chapter B, Using YaST instead of zypper or rpm
and Section B.6, yast instead of zypper in, on page 1073.
2012-07-13
To install the MySQL server and the MySQL client tools you need to use setup files of CQ00214426
the OpenScape UC Application setup DVD (see step 3 on page 600).
2012-07-13
Configuration after upgrading the Openfire server updated (see step 41 on page 769
CQ00214460
CQ00214286
CQ00215166
A31003-S5070-J100-12-7631, 02/2013
History of Changes
Date
Changes
Reason
2012-07-13
Links to steps replaced with the contents of such steps.

Examples:
Step 9 on page 751 to step 13 on page 752
Step 11 on page 787
Step 21 on page 905 and step 40 on page 910
CQ00215925
2012-07-13
Updating osc-setup updated (see step 7 on page 621 and step 7 on page 729)
CQ00216145
2012-07-13
For Standard Duplex (large and very large), specific setup steps of the Mobile Client
Facade server need not be executed for the application computer but for one of the
frontend computers (see step 2b on page 553, step 2c on page 553, step 3 on page
554 and step 11c on page 556).
CQ00214986
2012-07-13
syncUC is not supported if UUIDs (Universally Unique Identifier) are used in the /etc/ CQ00216415
fstab file (see step 2 on page 116 and Section 15.2.4, Preparing to the syncUC
Fallback, on page 707).
2012-07-13
If you wish to upgrade to an OpenScape UC Application V7 R0 connected to a HiPath FRN6067

4000 V6 R2, first upgrade the OpenScape UC Application to V7 R0 and then the
HiPath 4000 to V6 R2 (see footer 7 in Table 119 on page 745).
2012-07-13
The Openfire server version has been removed (see Section 12.1, Introduction, on
page 595 and step 2 on page 599).
2012-07-13
Changes concerning the Virtual Appliance:

When using Virtual Appliances, LVM2 partitions are created. syncUC can be used
(see Section 3.1.10.1, General Considerations, on page 69).
The Virtual Appliance can be used on VMware ESXi V5 but not on VMware ESXi
V4.x (see Section 3.1.10.1, General Considerations, on page 69).
The time zone of the application computer (OSUC_BE_Timezone) is required for
creating the vApp.iso file (see step 1j on page 72).
Users of virtual network boards of type E1000 (see step 20c on page 81))
Installation of the VMware tools (see step 21 on page 83)
2012-07-13
If HiPathCA services on the application computer communicate with HiPathCA

services on the frontend computers by Unicast and not by Multicast, not the community
name in the response file (see step 9 on page 205, step 24 on page 210, step 39 on
page 214, step 8 on page 220, step 22 on page 224, step 37 on page 230), but the
cluster name in the host.env file must be extended.
See step 14 on page 287, step 11 on page 294 and step 15 on page 296, step 14
on page 320, step 11 on page 327 and step 15 on page 329
See Section 6.2, Routing Schemas between the Application Computer and
Frontend Computer, on page 476
2012-07-13
If the OpenScape UC Application V7 shall be connected to an OpenScape Voice V7

after an upgrade, an operation must be performed in the CMP after the upgrade for
updating the version of the OpenScape Voice (see step 37 on page 768 and step 28
on page 792).
CQ00216690
2012-07-13
If the OpenScape UC Application is connected to an OpenScape Fusion client, an

operation must be performed in the CMP after upgrading the OpenScape UC
Application (see step 38 on page 768, step 29 on page 792).
CQ00216638
A31003-S5070-J100-12-7631, 02/2013
CQ00216679
History of Changes
Date
Changes
Reason
2012-07-13
OpenScape Desktop Client Enterprise Web Embedded Edition and OpenScape Web CQ00216567
Client need to log on with the user account and password of the OpenScape UC
Application (see Section 11.5, Installation and Configuration of the OpenScape
Clients, on page 593).
2012-07-13
When using an external USB hard disk for backing up the file system, do not mount the CQ00217396
entire hard disk as backup medium (see step 2 on page 181).
2012-07-13
Information about the reinstallation of the Openfire server as part of the Standard
CQ00217861
Duplex (large) migration to Standard Duplex (very large) updated (see step 25 on page
1039)
2012-07-13
In the chapter describing the Openfire server installation, Section 12.7, User Data
Import, on page 616 and Section 12.8, Configuring the OpenScape Clients, on page
616 have been updated.
2012-07-13
The commands for setting up the MySQL database and the MySQL client tools have
been changed (see step 3 on page 600).
2012-07-13
Section Installing and configuring OpenScape Fusion for Google Apps updated
2012-07-13
New note for avoiding interrupted SSH connections (see step 2 on page 311, step 2 on CQ00218753
2012-07-27
Port 5065 replaced with port 5062 and port 5066 replaced with port 5063 (see Table
37 on page 365, Ports to be opened on the Application Computer)
2012-07-27
Section 15.7, Smooth Update/Upgrade of V3 R2, V6 R0 or V7 R0, on page 803

added.
2012-07-27
Connecting Microsoft Office Communications Server has been released only project
specifically (see Chapter 11, Connecting the Microsoft Office Communication Server/
Microsoft Lync Server.
2012-07-27
An OpenScape UC Application V3 R2 or earlier with an OpenScape Voice V4 R1 or CQ00220105

earlier must first be upgraded to an OpenScape UC Application V3 R2 with
OpenScape Voice V5 before it can be upgraded to an OpenScape UC Application V7
(see Section 15.4, Upgrade and Migration Tables, on page 745).
2012-07-27
All clients of OpenScape UC Application V3 R2, V4 R0 and V6 R0 are supported. The FRN5573
new OpenScape UC Application V7 R1 features are not supported by these clients
(see Chapter 7, Client Installations).
2012-07-27
SLES 11 SP1 and SP2 are released for OpenScape UC Application V7 R1 (see for
example step 1 on page 116).
FRN5662
2012-07-27
The Common Management Portal has been renamed as Common Management

Platform.
FRN5833
2012-08-17
List of required SLES RPM packages updated (see step 52 on page 140)
2012-08-17
Section 6.3.1, Opening Port 1040 on the PBX Computer, on page 480 updated:
Port 1040 on the PBX computer opens automatically
Note for the NCPE tool (Node Configuration Parameter Editor) removed
2012-08-17
The PBX is upgraded after the OpenScape UC Application (see step 43 on page 770, CQ00220384
Section 15.6.2, Upgrading Large Deployment, on page 771 and step 40 on page
799).
2012-08-17
Configuration of the OpenScape Voice for the migration from Integrated Simplex to
Standard Duplex (small) updated (see step 23 on page 892)
10
CQ00218102
FRN5174
CQ00221038
CQ00219957
A31003-S5070-J100-12-7631, 02/2013
History of Changes
Date
Changes
Reason
2012-08-17
Note for status Away added for Microsoft OCS/Lync (see Chapter 11, Connecting the CQ00221477
Microsoft Office Communication Server/Microsoft Lync Server)
2012-08-17
The ports 77xx for Integrated Simplex need not be open on the application computer
(see Table 37 on page 365).
2012-08-17
Steps for updating via the CMP (UI Patching) added (see step 19 on page 743 to step
25 on page 744)
2012-08-17
The file /var/siemens/hp4kprovisioning/ConfigureBackup/

Configure.groovy is no longer needed for connecting a HiPath4000.
2012-08-17
The instructions in section Configuring the Address Translation Context in the

administrator documentation OpenScape UC Application Configuration and
Administration need to be followed only for an upgrade but not for an update.
2012-08-17
Section 14.3, Installing Voice Portal Speech on Integrated Deployment, on page 725 CQ00219988
updated.
2012-08-17
Section 15.1.3, Determining the version by means of the rpm command, on page 663 CQ00222164
updated.
2012-08-17
Port 80 on the Web Collaboration computer must be open for HTTP communication CQ00222416
with the computer on which the frontend services operate (see Table 37 on page 365,
Table 52 on page 383, Table 55 on page 388, Table 71 on page 408, Table 75 on page
422, Table 91 on page 441, Table 95 on page 456 and Table 111 on page 474).
2012-08-17
The directory /opt/siemens/common/conf/diagnostic_configurations

CQ00221617
must be backed up before a migration from Standard Duplex (large) to Standard
Duplex (very large) and subsequently restored (see step 10 on page 1032, step 18c on
page 1037, step 20a on page 1038 and 21c on page 1038).
2012-08-17
Command for migrating from Standard Duplex (small) to Standard Duplex (large)
updated (see step 11 on page 902)
2012-08-17
The instructions in Section 15.19, Changing the Hardware for V7 Small Deployment,
on page 944 and Section 15.20, Changing the Hardware for V7 Large Deployment
and Very Large Deployment, on page 954 are applicable even if the original and/or
target computer are virtual.
2012-08-17
Section 15.7, Smooth Update/Upgrade of V3 R2, V6 R0 or V7 R0, on page 803

completely revised.
2012-08-17
CQ00219547
Section 15.15, Migration from V7 Small Deployment to V7 Large Deployment, on
page 899 updated:
Step 5 on page 899 added
Link to the provision of ISO installation files moved (see step 10 on page 901)
Links to hotfix installation integrated (see step 13 on page 903, step 31 on page 907
Steps removed
Configuration of the media server after the migration extended (see step 56 on page
914)
2012-08-17
Renamings for the OpenScape UC Application, but not for the OpenScape Voice:
Integrated Simplex --> Integrated Deployment
Standard Duplex (small) --> Small Deployment
Standard Duplex (large) --> Large Deployment
Standard Duplex (very large) --> Very Large Deployment
A31003-S5070-J100-12-7631, 02/2013
CQ00220707
CQ00222627
11
History of Changes
Date
Changes
Reason
2012-08-17
Any SLES update or SLES upgrade requires executing the syncUC sync command CQ00223447
(see step 1 on page 116, step 1e on page 665 and Section 15.2.4.2, syncUC
Commands, on page 707).
2012-08-17
Prior to a migration, E/A Cockpit configuration files that may exist must be backed up CQ00222949
and restored (see step 6 on page 887, step 16 on page 891, step 8 on page 900, step
33 on page 908, step 11 on page 1033 and step 20b on page 1038).
2012-09-04
Installation and configuration of OpenScape Fusion for Google Apps updated.
2012-09-04
The agfa-fonts RPM package is needed for the menu of video conferences (see step CQ00222858
52 on page 140).
2012-09-04
If you upgrade from OpenScape UC Application V3 R2 to V7, stop Loquendo before

the upgrade (see step 6 on page 750 and step 8 on page 786).
2012-09-28
A hint to the administrator documentation OpenScape UC Application Configuration

CQ00220115
and Administration has been added in Section 14.4, Installing additional Media Server
Computers, on page 647.
2012-09-28
Certificates that have been signed by a trusted Root CA must be saved before a
migration from Large Deployment to Very Large Deployment and restored thereafter
(see step 3 on page 1029 and step 23 on page 1039).
2012-09-28
If you use HTTPS for provisioning via SPML instead of HTTP, use port 9943 (see
Chapter 6, Configuring the OpenScape UC Application).
2012-09-28
Only SP2 of SLES 11 is supported (see e. g. step 1 on page 116).
2012-09-28
In order to use cyrillic letters in mail notifications for missed calls, the parameter
CQ00226131
Mail.Charset in the JMailService.cfg file must be edited (see Table 10 on page
273, Table 11 on page 274, Table 12 on page 275, Table 13 on page 276, Table 14 on
page 277, Table 17 on page 303, Table 18 on page 305, Table 19 on page 305, Table
20 on page 306, Table 21 on page 307, Table 24 on page 336, Table 25 on page 338,
Table 26 on page 338, Table 27 on page 339, Table 28 on page 340, Table 123 on page
752 and Table 125 on page 788)
2012-09-28
Section 3.1.11, Using Virtual Appliance for Large Deployment, on page 84 added
2012-09-28
Mobile Client Facade Server:

The command facaded is used for manually starting, stopping, restarting and
showing the status of the Mobile Client Facade Server (see after step 4 on page
555).
The /usr/local/tomcat6/properties.ini file has been renamed and
moved to /usr/local/tomcat6/conf/facade.properties (see e. g. step
11 on page 556).
The installation script installFacadeServer.sh has two new parameters,
-httposconnection and -uninstall (see step 2 on page 552).
After the installation of the Mobile Client Facade Server, you are not asked anymore
to restart the system.
2012-09-28
The dejavu RPM must be installed on the computer where the media server is installed CQ00226245
in order to show cyrillic names in video conferences (see step 52 on page 140).
2012-09-28
Configuration step for upgrading OpenScape UC Application V4 R0 to V7 removed

(see Section 15.6.1, Upgrading Small Deployment, on page 750).
12
CQ00220804,
CQ00218104,
CQ00221242
CQ00222604
CQ00222259
CQ00227518
FRN5063
CQ00227547
A31003-S5070-J100-12-7631, 02/2013
History of Changes
Date
Changes
Reason
2012-09-28
Execute the instructions in Section 4.5, Configuring the File System Backup, on page CQ00223219
181 after an upgrade (see step 26 on page 760, step 21 on page 781, step 14 on page
784 to step 18 on page 785 and step 19 on page 791 to step 23 on page 791).
2012-09-28
The option Thick Provision Lazy Zeroed in the installation process of a virtual
computer must be activated only for the application and media server computer in
productive systems (see step 10 on page 52).
2012-09-28
Installation and configuration of OpenScape Fusion for Google Apps updated.
2012-09-28
Microsoft Lync Server mentioned at all references of Microsoft Office Communications CQ00229114
Server (OCS) (see Chapter 11, Connecting the Microsoft Office Communication
Server/Microsoft Lync Server)
2012-09-28
Chapter C, Installing Windows added
2012-10-31
Virtual Appliance for Large Deployment (see Section 3.1.11.1, General

Considerations, on page 84):
Four OVA files are used.
LVM2 and syncUC are not used on the instant-messaging server computer.
CQ00229536
2012-10-31
The command osc-setup up is not needed in Section 15.15, Migration from V7

Small Deployment to V7 Large Deployment, on page 899
CQ00229459
2012-10-31
Two more Openfire files must be copied for the migration from Large Deployment to
Very Large Deployment (see step 25c on page 1039).
CQ00230007
2012-10-31
The names of two MySQL RPMs for the Openfire installation for Very Large
Deployment have been changed (see step 3 on page 600).
2012-10-31
Stop/start an Openfire server before/after an update/upgrade (see step 3 on page 711, CQ00230683
step 11 on page 714, step 3 on page 717, step 9 on page 719, step 2 on page 728, step
14 on page 730, step 2 on page 731, step 7 on page 731, step 3 on page 750, step 33
on page 763, step 5 on page 773, step 23 on page 781).
2012-10-31
Virtual computers are supported for Very Large Deployment as well (see Section 3.1, CQ00231140
Installing Virtual Computers, on page 33).
2012-10-31
Transfer conferences must be reconfigured after a migration from Integrated

Deployment to Small Deployment and after a migration from Small Deployment to
Large Deployment (see step 26 on page 897 and step 56g on page 915).
A31003-S5070-J100-12-7631, 02/2013
CQ00227104,
CQ00220804
CQ00220115
13
History of Changes
Date
Changes
2012-10-31
Providing installation sources remotely is supported.

Section 5.3.1.3, Creating a Repository in osc-setup by using remote Installation
Sources, on page 243 has been added.
The list of needed SLES libraries has been extended (see step 52 on page 140, e. g.
footnotes 3 and 4 on page 141)
If NFS is used for remote provisioning of installation sources, port 111, port 2049 and
a dynamic port must be open (see e. g. step 15 on page 251 and Section 6.1, Lists
of the Ports to be opened, on page 359).
If HTTP is used for remote provisioning of installation sources, port 80 must be open
(see e. g. step 5 on page 259).
Section 5.3.1, Providing the Installation Sources in an Installation Repository in
osc-setup, on page 234 has been restructured.
Providing sources for an update or upgrade has been extended and moved to
Section 15.2.2, Providing the Update/Upgrade Sources in a Repository in oscsetup, on page 671
The OpenScape UC Application must be stopped before osc-setup is updated (see
2012-10-31
The directory of a linked repository in osc-setup on the Mobile Client Facade Server
computer has been updated (see step 1 on page 552 and step 2 on page 552).
2012-10-31
Information about SSE2.x updated (see footnote 6 in Table 2 on page 36, Chapter 4,
Installing and Configuring the Computer and Operating System, Section 5.3.3.4,
Installation on the Media Server Computer, on page 297, Section 5.3.4.4, Installation
on the Media Server Computer, on page 330, Chapter 15, Updating, Upgrading and
Migrating, Section 15.6.2.3, Upgrading on the Media Server Computer, on page 786)
2012-10-31
The library libgcc46-32bit can be used instead of libgcc43-32bit and libstdc++46-32bit CQ00231146
can be used instead of libstdc++43-32bit (see step 52 on page 140).
2012-10-31
Information about SMP (symmetric multiprocessing) removed. SMP is not supported

by SLES 11 SP2 (see step 5 on page 44 and Section 3.1.8, Installing the VMware
Tools, on page 62).
2012-10-31
If you install the Openfire server on the application computer, ensure that the
CQ00232629
OpenScape UC Application already is installed (see Section 12.2, Infrastructure, on
page 596).
2012-10-31
Information about the hard disk size, the RAM and the clock rate of the host etc. of
virtual computers are no longer to be found in the OpenScape UC Application Planning
Guide but in the OpenScape Solution Set Virtual Machine Resourcing and
Configuration Guide (see Section 3.1.2, Overview of the VM Configuration
Parameters, on page 35, step 5 on page 44, step 6 on page 48, step 10 on page 52,
step 3 on page 57, step 20a on page 81, step 20b on page 81, step 20f on page 82).
2012-10-31
It is recommended but not necessary to use LVM2 on virtual computers according to

step 2 on page 116 (see Section 3.1.2, Overview of the VM Configuration
Parameters, on page 35).
2012-10-31
VMware Virtual Machine 9 or higher is not supported (step 3 on page 42).
2012-10-31
Section 15.21, Migration from OpenScape ComAssistant to OpenScape UC

Application, on page 965 added
2012-10-31
Entering the IP addresses, subnet masks etc. for Virtual Appliance for the Large
Deployment added (see step 30 on page 102 and step 31 on page 103)
14
Reason
CQ00231161
FRN5574
A31003-S5070-J100-12-7631, 02/2013
History of Changes
Date
Changes
Reason
2012-11-30
If an Openfire server is installed on the application computer and you execute the
CQ00233698
instructions in Section 15.3.3, Updating using the CMP (UI Patching) instead of oscsetup, on page 733, the Openfire server must be restarted manually (see step 17 on
page 742).
2012-11-30
If you want to connect the OpenScape UC Application Large Deployment to a HiPath CQ00234552
4000, install the OpenScapeUC_4kaddons RPM (see step 7 on page 283).
2012-11-30
The files needed for Virtual Appliance are downloaded from the Software Supply
Server (SWS; see step 2 on page 74, step 3 on page 76, step 5 on page 92 and step
6 on page 94).
2012-11-30
Filling the XMPP Domain Name field for an Openfire server has been moved after
CQ00230916
testing the connection to the Openfire server (see step 8 on page 605). Otherwise the
field would be empty after the test.
2012-11-30
Virtual Appliance for Small Deployment updated (see sub-section Creating the
vApp.iso file on page 70, especially creating the vApp.iso file by editing an XML
file)
Virtual Appliance for Large Deployment updated (see sub-section Creating the
vApp.iso file on page 86, especially creating the vApp.iso file by editing an XML
file)
2012-11-30

Application, on page 965 updated, e. g.:
Section 15.21.2, General Restrictions, on page 967 added
Subsection Logging Configuration on page 985 added
Table 146 on page 996, Syntax Examples for skipping CA Users, added
Section 15.21.4.5, Call Journal Migration, on page 1020 added
Command run teamanalysis in Section 15.21.4.4, Team Migration, on page
1016 removed
2012-11-30
CQ00236564
Virtual Appliance for Large Deployment:
It is recommended to run the virtual computers created by the Virtual Appliance for
Large Deployment on the same VMware ESXi host (see Section 3.1.11.1, General
Considerations, on page 84 and 21 on page 100).
If the virtual computers reside on different VMware ESXi hosts, ensure that the ESXi
hosts time is synchronized (see sub-section Using the OVA file on page 93)
The VMware Tools are not installed per default (see step 31 on page 103).
2012-11-30
If you upgrade from OpenScape UC Application V3 R2 to V7, ensure that the users
have an instant-messaging address thereafter (see step 42 on page 769, step 39 on
page 798, step 20 on page 849 and step 22 on page 860).
2012-11-30
Start the MRCP service, the Nuance TTS and the Nuance ASR, if available, before
starting the OpenScape UC Application (see e. g. step 25 on page 83, step 4 on
page 635, step 12 on page 730, step 8 on page 802, step 3 on page 810, step 14
on page 832, step 14 on page 836, step 29 on page 878 and step 18 on page 891).
Stop the MRCP service, the Nuance TTS and the Nuance ASR, if available, after
stopping the OpenScape UC Application (see e. g. step 24 on page 680, step 5 on
page 830, step 3 on page 834, step 6 on page 840, step 4 on page 862, step 3b on
page 885, step 12 on page 891, step 4 on page 899, step 5 on page 1029).
2012-12-10
Small changes in section Section 3.1.11, Using Virtual Appliance for Large
Deployment, on page 84, e. g. in step 25 on page 100
A31003-S5070-J100-12-7631, 02/2013
CQ00236586
CQ00238491
15
History of Changes
Date
Changes
2012-12-10
The hint has been removed that it is recommended to have all virtual computers on one
VMware ESXi host for Virtual Appliance for Large Deployment (see Section 3.1.11.1,
General Considerations, on page 84 and step 21 on page 100).
2012-12-10
All references to the OpenScape Solution Set Virtual Machine Resourcing and
Configuration Guide have been replaced by references to the OpenScape UC
Application planning guide.
2012-12-10
Wording in one sentence in Section 8.2, Installing the Mobile Client Facade Server on CQ00238571
SLES, on page 552improved
2012-12-10
The installation file for the migration from the OpenScape ComAssistant to the
OpenScape UC Application must be downloaded from the software supply server (see
2012-12-10
Installing the Virtual Appliance without using the CDC tool has been removed (see
Section 3.1.10.3, Installation, on page 70 and Section 3.1.11.3, Installation, on page
86)
2012-12-10
Call parameter httposconnection for the facade server replaced by

httposcconnection (see step 2g on page 553)
2012-12-10
CQ00239142
Updating the Mobile Client Facade server overwrites the certificate /usr/local/
tomcat6/conf/OSC-Facade-Server-Default-Cert.p12 (see step 2h on page
554).
2012-12-10

Application, on page 965 updated:
The installation file for the migration from the OpenScape ComAssistant to the
OpenScape UC Application must be downloaded from the software supply server
(see step 1 on page 974).
Steps to create the LongLivedStatement updated (see Section 15.21.3.5,
Connecting to the OpenScape UC Application, on page 977)
Property WriteToUCServer added (see Table 137 on page 978)
Property caNamePattern added (see Table 142 on page 991)
The user_map.csv file is used as a filter for the owner and the members of a
shared address book (see Section 15.21.4.3, Shared Address Book Migration, on
page 1006).
Information about LDAP removed from Section 15.21.4.3, Shared Address Book
Migration, on page 1006.
Property ownerFilePrefix removed (see e. g. Table 147 on page 1007)
Section 15.21.4.8, Creating a Trouble Ticket, on page 1028
2013-01-31
SLES 11 SP2 is recommended, SLES 11 SP1 is supported as well (see Table 1 on

CQ00240757
page 28, step 1 on page 116, Section 8.1, Supported Operating Systems, on page
551, Section 8.2, Installing the Mobile Client Facade Server on SLES, on page 552,
Chapter 15, Updating, Upgrading and Migrating, step 1 on page 665, Section 15.6,
Upgrading V3 R2 or V6 R0 Small and Large Deployment, on page 749, Section
15.18.1, Preparations, on page 937, Section 15.18.3.2, Upgrade, on page 941).
2013-01-31
Under certain conditions you might need to try again to save the initial configuration of
the Openfire server (see step 15 on page 614).
16
Reason
CQ00239089
A31003-S5070-J100-12-7631, 02/2013
History of Changes
Date
Changes
2013-01-31
If you want to align the presence status of users between the Microsoft Office
Communication Server/Microsoft Lync Server and the OpenScape UC Application, the
connection from the Microsoft Office Communication Server/Microsoft Lync Server to
the OpenScape UC Application is needed (see step 10 on page 267, step 10 on page
284 and Chapter 11, Connecting the Microsoft Office Communication Server/
Microsoft Lync Server).
2013-01-31
The names of two Openfire presence files have been corrected that must be copied
under certain conditions when migrating from Large Deployment to Very Large
Deployment (see step 25c on page 1039)
2013-01-31
Mobile Client Facade Server: The ip parameter of the installFacadeServer.sh

script is even for Large Deployment the IP address of the application computer (see
step 2b on page 553).
2013-01-31
Upgrading OpenScape UC Application V3 R2 or V6 including a hardware change has

been extended by links to the V3 R2 documentation and V6 documentation (see step
2 on page 837 and step 2 on page 838).
2013-01-31
The value of SI_LOCAL_NAME in the configuration file knut.responsefile.txt of CQ00240597

the installation must not contain spaces (see e. g. step 1e on page 71, step 1e on page
87, step 2a on page 90, step 3a on page 91, step 10 on page 201, step 11 on page
206, step 27 on page 210, step 42 on page 215, step 10 on page 221, step 25 on page
225, step 40 on page 231, step 8 on page 841 and step 7 on page 853).
2013-01-31
If the instructions in Section 15.8, Upgrading V3 R2 or V6 R0 Small Deployment

CQ00241047
including a Hardware Change, on page 837 or Section 15.9, Upgrading V3 R2 or
V6 R0 Large Deployment including a Hardware Change, on page 838 are applied, you
need not upgrade the Web Collaboration server (see step 4 on page 837 and step 4
on page 838).
2013-01-31
The section Installing Voice Portal Speech on Integrated Deployment has been
moved to the OpenScape Voice documentation.
2013-01-31
Port 88 has to be open on all computers where the media server is installed (see Table CQ00243420
37 on page 365, Table 55 on page 388, Table 55 on page 388 and Table 55 on page
388).
2013-01-31
Create an endpoint in the PBX for the new media server after you have migrated from CQ00244057
Small Deployment to Large Deployment (see step 56a on page 914).
2013-01-31
If you have upgraded an OpenScape UC Application connected to a HiPath 4000 via CQ00244457
an OpenScape Voice, some additional steps must be executed (see step 11 on page
751, step 29 on page 761, step 9 on page 774 and step 31 on page 793).
2013-01-31
Information about SMP (symmetric multiprocessing) is only valid for SLES 11 SP1 (see CQ00231161
step 5a on page 45 up to step 5n on page 47 and Section 3.1.8, Installing the VMware
Tools, on page 62).
2013-01-31
A zypper se ... command has been replaced by an osc-setup se ...

command in step 7 on page 899 in section Section 15.15, Migration from V7 Small
Deployment to V7 Large Deployment, on page 899
2013-02-08
For the installation of Large Deployment and Very Large Deployment, the execution
order of the commands installlib.sh prerequisite.primaryReady and
installlib.sh createdar has been exchanged (see step 5 on page 292 and step
5 on page 325).
A31003-S5070-J100-12-7631, 02/2013
Reason
CQ00241291
CQ00240311
CQ00243861
17
History of Changes
Date
Changes
Reason
2013-02-08
The connection of the OpenScape UC Application Very Large Deployment to the

HiPath 4000 is supported (see step 7 on page 316, Table 119 on page 745 and step
22 on page 922).
FRN6556
CQ00243017
2013-02-08
The Client Installations chapter has been extended:

OpenScape Extensions for Microsoft Outlook
OpenScape Extensions for Lotus Notes
OpenScape Desktop Integration
OpenScape Click-to-Dial-Browser-Plug-in
OpenScape Client Integrations
2013-02-08
VMware Data Backup and VMware Data Recovery are released with restrictions (see FRN5575,
point VMware Data Backup and VMware Data Recovery on page 38 in Section 3.1.3, CQ00244192
VMware Features and OpenScape UC Application, on page 37).
2013-02-08
The reinstallation of the frontend computers and media server computers has been
FRN6474
removed from Section 15.17, Migration from V7 Large Deployment to V7 Very Large
Deployment, on page 916.
2013-02-28
When you upgrade the server and if you accept restrictions, you need not upgrade the FRN6812
clients (see e. g. Chapter 15, Updating, Upgrading and Migrating).
2013-02-28
Sub-sections Creating a repository in zypper on page 674 and Installing osc-setup on CQ00246316
page 676 added to Section 15.2.2.2, Creating a Repository in osc-setup by using local
Update/Upgrade Sources, on page 674
When upgrading OpenScape UCApplication, install the latest hotfix:
Small deployment: Sub-section Hotfix on page 757 and step 25 on page 759
Large Deployment: Sub-section Hotfix on page 778, step 20 on page 780, step 9 on
page 782 up to step 12 on page 783, step 14c on page 784, step 13 on page 788
up to step 16 on page 790 and step 18 on page 791
2013-02-28
Some steps for the smooth upgrade have been updated (see step 1 on page 817, step CQ00246759
2a on page 817 , step 4 on page 818 and step 6b on page 819 in Section 15.7.3.2,
Copying the UC Database from BE1 to BE2, on page 817)
2013-02-28
Section 15.1.4, Evaluation of the results, on page 664 updated
2013-02-28
If you want to install the OpenStage Client for Integrated Deployment, use the -CQ00238538
prefix=/enterprise option (step 10 on page 267, step 2 on page 650 and step 12
on page 715).
2013-02-28
Port 7778 and port 7788 are not needed anymore (see Section 6.1, Lists of the Ports CQ0248513
to be opened, on page 359).
2013-02-28
The perl-XML-XPath RPM is needed on all computers for all deployments (see step 52 CQ00246570
on page 140 and step 13 on page 920).
2013-02-28
New section for the client installations about the properties and their parameters
required for an update or upgrade installation via msi-file added.
2013-02-28
If a network management system on a separate computer should receive information CQ00247352

from both the SLES SNMP agent and the SNMP agent of the OpenScape UC
Application, the net-snmp RPM must be installed and the SNMP port configuration
needs to be updated (see step 52 on page 140 and step 91 on page 160).
2013-02-28
Step 6b on page 819 corrected.
18
CQ00244180
CQ00246759
A31003-S5070-J100-12-7631, 02/2013
IG_Introduction.fm
About This Guide
Target Group
1 About This Guide

IMPORTANT: This guide describes the installation process for OpenScape UC
Application V3 and components.
NOTE: This manual assumes that the requirements defined in the OpenScape
UC Application Planning Guide have been complied with.
1.1 Target Group

This guide is intended for the installation personnel of Siemens Enterprise
Communications GmbH & Co. KG, IT domain and enterprise administrators, and
others who help with the installation of OpenScape UC Application.
NOTE: We do not describe the setup of the deployment scenario Integrated
Deployment here (see also Section 2.1, Deployment Scenarios, on page 25).
1.2 How to Use This Guide

This guide is separated into several parts, each of which covers a different phase
of the installation process.
The first part provides an introduction to this documentation.
The second part covers the tasks required to ready the system environment for
installation of the OpenScape UC Application.
The third part describes the actual installation and configuration steps of the
OpenScape UC Application including the connection to OpenStage clients,
mobile clients, OpenScape Web Collaboration, Microsoft Office Communication
Server, instant messaging and groupware.
NOTE: The configuration information provided here does not comprise all
necessary steps. Please obtain details on this from the administrator documentation OpenScape UC Application configuration and Administration.
A31003-S5070-J100-12-7631, 02/2013
19
IG_Introduction.fm
About This Guide
Related Information
The fourth part describes how to perform updates, upgrades, migrations,

uninstallations and the installation of additional components such as languages
for the Voiceportal.
The annexes describe the protection of the Linux operating system, the
deployment of YaST, the installation of Windows and the acronyms used.
1.3 Related Information

The following information sources are available for OpenScape UC Application
V3:
20
OpenScape UC Application Planning Guide
OpenScape UC Application System Description
OpenScape UC Application Configuration and Administration, Administrator

Documentation
OpenScape UC Application Security Checklist, Service Documentation
OpenScape Common Management Platform Administration, Administrator

Documentation
OpenScape UC Application Client Applications, Operating Instructions
OpenScape Desktop Client Enterprise Web Embedded Edition, Operating

Instructions
OpenScape Desktop Client Enterprise Web Embedded Edition, Quick Guide
OpenScape Personal Edition, Operating Instructions
OpenScape Personal Edition, Quick Guide
OpenScape UC Application OpenScape Web Client, User Manual
OpenScape Web Client, Quick Guide
OpenScape UC Application Mobile Client, Operating Instructions
OpenScape Mobile Client, Quick Guide
OpenScape Web Collaboration, Installation and Upgrade, Installation Guide
OpenScape Web Collaboration, Operating Instructions
OpenScape Web Collaboration, Quick Guide
OpenScape UC Application Voice Portal Function Overview, Quick Guide
OpenScape UC Application Voice Portal with OpenScape Xpressions

PhoneMail, Quick Guide
A31003-S5070-J100-12-7631, 02/2013
IG_Introduction.fm
About This Guide
Related Information
OpenScape UC Application OpenScape Enterprise Edition, Data Sheet
OpenScape Personal Edition, Dats Sheet
Furthermore, the following information sources are available:
OpenScape Voice, Installation and Upgrades, Service Manual: Volume 1 ,

Installation Guide
OpenScape Voice Administrator Documentation
Common Management Platform Administrator Documentation
HiPath 4000 V5, Installation, Installation Guide
HiPath 4000 V6, Installation, Installation Guide
OpenScape Xpressions V7 Server Administration Manual, provides the

configuration and administration information for connecting Xpressions to the
OpenScape UC Application system.
A31003-S5070-J100-12-7631, 02/2013
21
IG_Introduction.fm
About This Guide
Documentation Feedback
1.4 Documentation Feedback

When you call or write, be sure to include the following information. This will help
identify which document you are having problems with.
Title: OpenScape UC Application V7 Installation and Upgrade, Installation

Guide
Order number: A31003-S5070-J100-1-31
1.4.1 In Countries other than the U.S.

Submit a trouble ticket to the International Case Tracking System (ICTS).
1.4.2 In the U.S.

To report a problem with this document, call your next level of support:
Customers should call the Customer Support Center (CSC) of the Siemens
Enterprise Communications GmbH & Co. KG.
Employees of Siemens Enterprise Communications GmbH & Co. KG should

call the Interactive Customer Engagement Team (i-CET).
1.5 Data Protection and Security

This system also processes and uses personal data for purposes such as billing,
displays, and customer data acquisition.
In Germany, the processing and use of such personal data is subject to various
regulations, including the regulations of the Federal Data Protection Law
(Bundesdatenschutzgesetz = BDSG). For other countries, please follow the
appropriate national laws.
The aim of data protection is to protect the rights of individuals being affected by
use of their personal data.
In addition, the aim of data protection is to prevent the misuse
22
A31003-S5070-J100-12-7631, 02/2013
IG_Introduction.fm
About This Guide
Data Protection and Security
of data when it is processed and to ensure that ones own interests and the
interests of other parties which need to be protected are not affected.
NOTE: The customer is responsible for ensuring that the system is installed,
operated and maintained in accordance with all applicable labor laws and regulations and all laws and regulations relating to data protection, privacy and safe
labor environment.
Members of the Siemens Enterprise Communications GmbH & Co. KG are
required
to observe business and data secrecy as a result of the companys work rules.
In order to ensure that the statutory requirements during service whether during
on-site service or during remote service are consistently met, you should
always observe the following rules. You will not only maintain the interests of your
and our customers, you will also avoid personal consequences.
A conscientious and responsible approach helps protect data and ensure
privacy:
Ensure that only authorized persons have access to customer data.
Take full advantage of password assignment options; do not allow

unauthorized persons to gain access to passwords by writing them down on
a piece of paper or via other means.
Ensure that no unauthorized person is able to process (store, modify,

transmit, disable, delete) or use customer data in any way.
Prevent unauthorized persons from gaining access to storage media, such as

backup diskettes or log printouts. This applies to service calls as well as to
storage and transport.
Ensure that storage media which are no longer required are completely
destroyed. Ensure that no sensitive documents are left unprotected.
Work closely with your customer contact; this promotes trust and reduces
your workload.
A31003-S5070-J100-12-7631, 02/2013
23
IG_Introduction.fm
About This Guide
Data Protection and Security
24
A31003-S5070-J100-12-7631, 02/2013
IG_PrepGeneral.fm
General Preparations
Deployment Scenarios
2 General Preparations
NOTE: This section of the Installation Guide should be made available to the
customers network administrator as a reference while preparing the installation
of the OpenScape UC Application.
IMPORTANT: Please consider in particular the instructions given in the service

documentation OpenScape UC Application Security Checklist.
2.1 Deployment Scenarios

The OpenScape UC Application can be installed in the following deployment
scenarios in order to meet a customers topology, scalability, and reliability
constraints:
Integrated Deployment
All components of the OpenScape UC Application and the PBX are installed
on the application computer.
IMPORTANT: In this deployment scenario the OpenScape UC Application
setup is a subitem of the PBX installation.
This is why we do not describe the setup of this deployment scenario in these
installation instructions but only mention it in scattered passages (for example
Section 6.1.2, Lists of the Ports to be opened for Integrated Deployment, on
page 363 and Chapter 15, Updating, Upgrading and Migrating). Please
obtain the information you require from the PBXs setup guide
Small Deployment
All components of the OpenScape UC Application are installed on the
application computer, the PBX, however, is set up on another computer.
Large Deployment
The frontend services of the OpenScape UC Application are installed on at
least one frontend computer. The media server is installed on at least one
media server computer. The remaining components of the OpenScape UC
Application are installed on the application computer. The PBX is installed on
another computer.
Very Large Deployment
A31003-S5070-J100-12-7631, 02/2013
25
IG_PrepGeneral.fm
Deployment Scenarios
If the system performance of Large Deployment is insufficient for a

communications solution, OpenScape UC Application can also be installed in
Very Large Deployment.
Very Large Deployment is based on single clusters used for gradually
increasing the system performance of a UC Application system beyond the
performance of Large Deployment.
For information and diagrams about the various deployment scenarios and
system requirements, refer to the OpenScape UC Application, Planning Guide.
The deployment scenario Standard Duplex (medium) was only supported up to
and inclusive V3 R0. A direct upgrade to V7 is not possible. First upgrade via
intermediate steps to V3 R2 Large Deployment (see Installation Guide
OpenScape UC Application Installation and Upgrade of V3 R2). Then upgrade to
V7.
Each of these deployment scenarios includes the following functional
components:
OpenScape UC Application (OpenScape Backend Services)
OpenSOA1 Framework
OpenSOA Common Services
OpenScape Frontend Services (FE)
OpenScape Media Server Services (MS)
Customer License Manager (CLM)
PBX
OpenScape Voice or
HiPath 4000 (not with Integrated Deployment)
OpenScape Voice Assistant (only when using the OpenScape Voice)
In the following deployment scenarios, NO OpenScape UC Application

components are installed, updated or upgraded. Therefore, these deployment
scenarios are not described in this documentation. Please obtain detailed
information from the PBX setup guide (e. g. OpenScape Voice, Installation and
Upgrades, Installation Guide).
Mediaserver Standalone
Mediaserver Standalone is used for playing announcements triggered from
the OpenScape Voice. The MGCP is used for the communication between
the media server and the OpenScape Voice. Mediaserver Standalone is not
related to the voice portal or conferences.
1. OpenSOA of the Siemens Enterprise Communications GmbH & Co. KG
26
A31003-S5070-J100-12-7631, 02/2013
IG_PrepGeneral.fm
Installation Process Overview
Multiple Communication Server Admin (Standard Duplex Voice)

OpenScape Voice Assistant, RG 8700 Assistant and CLM are installed on
one computer. The OpenScape Voice Duplex is on another computer. This
deployment scenario serves for managing several OpenScape Voice
systems.
NOTE: The Integrated Duplex deployment scenario is not supported by

OpenScape UC Application V7. First upgrade to V3 R2 Integrated Duplex and
migrate to V3 R2 Small Deployment (see Installation Guide OpenScape UC
Application Installation and Upgrade of V3 R2). Then upgrade to V7.
2.2 Installation Process Overview

Table 1 provides an overview of the complete OpenScape UC Application
installation process. Take into account the following points:
If you want to connect the OpenScape UC Application to OpenScape Xpressions,
OpenScape Xpressions is installed on a separate Windows Server.
If you want to connect OpenScape UC Application to a groupware (Microsoft
Exchange Server or IBM Lotus Domino) belonging to the customer domain, this
groupware has already been installed by the customer on one or more separate
computers.
You can install the OpenScape UC Application parallel to the PBX (OpenScape
Voice or HiPath 4000). However, the PBX setup (inclusive numbering plan) must
be complete before you start the OpenScape UC Application configuration (see
Chapter 6, Configuring the OpenScape UC Application).
IMPORTANT: The tasks and the task sequence may vary for your specific
deployment.
A31003-S5070-J100-12-7631, 02/2013
27
IG_PrepGeneral.fm
Step
Task
Information Resource
Ensure that you have all configuration data before you

start the installation. Obtain e. g. the customer data
worksheets and review any requirements.
Customer contact (see also Section No

2.3, Information Provision by the
Customer, on page 30)
Familiarize yourself with the deployment and logical flow OpenScape UC Application
diagrams.
Planning Guide
No
Before you begin, familiarize yourself with this guide.

Ensure that all of the related documents necessary for
your purposes are readily available to you.
Contents
Section 1.3, Related
Information, on page 20
No
Check hardware and environment requirements.
OpenScape UC Application
Planning Guide
Section 2.4, Domain System
Environment Preparation, on
page 32
Setup guide of the PBX
No
Obtain the OpenScape UC Application licenses.
To obtain the OpenScape UC

Application license, use the
licensing tool of the Siemens
Enterprise Communications GmbH
& Co. KG and retrieve the license
using the MAC address as the key
identifier.
No
Installing a VMware environment
Chapter 3, Providing Virtual

Computers
Yes
Install SLES 11 SP1 or SP2 on the application computer. Section 4.1, File System and
No
Deactivate the services of not required Linux
Operating System, on page 116
packages.
Section 4.2.2, Partitioning, on
Install the additional required Linux packages.
page 123
Verify the Linux installation.
Install additional network interface cards as applicable.
Section 4.4, Configuring Multiple

Network Interface Cards, on page
165
No
Configuring the File System Backup
Section 4.5, Configuring the File

System Backup, on page 181
No
10
Check the requirements and create the response file(s)

then.
Section 5.1, Installation

Requirements, on page 192
Section 5.2, Configuring the
Installation, on page 195
Section 5.3.3.2, Requirements
for Installing Additional
Computers, on page 290
Installati
ondepende
nt
11
Perform the OpenScape UC Application installation.
Section 5.3, Installation, on

page 233
Section 5.4, Checking the
Installation, on page 347
No
Table 1
28
Optional Initial
Installation Check List
A31003-S5070-J100-12-7631, 02/2013
IG_PrepGeneral.fm
Step
Task
12
Check for needed fix releases of hot-fixes and install them Section 15.3.1, Updating to a
if applicable.
new Fix Release, on page 711
Section 15.3.2, Installing a
Hotfix, on page 727
No
13
Start OpenScape UC Application.
No
14
Configure the OpenScape UC Application by the

Chapter 6, Configuring the
following steps among other things:
Check the ports to open in firewalls
Add the OpenScape Voice to the OpenScape UC
Application list of switches.
Configure the office codes.
Ensure that control of all office codes and extensions
is changed from the OpenScape Voice Assistant to the
OpenScape UC Application system during the
synchronization process.
If this process is not completed, you might not be able
to create the users (because only synchronized
devices can be assigned to users).
Configure the trunk line from the PBX to the
OpenScape Media Server.
Configure the toll number.
Configure the media server for Conferencing.
15
Configuring PBX subscribers

a
Create or check the settings for extensions used as

OpenScape ONS.
Configure the GNF replacement and adjust the routing

accordingly.
If a numbering plan is not provided to you, create a test

numbering plan for the OpenScape UC Application.
Small Deployment:
- Step 21 on page 280
Large Deployment:
Administrator documentation
Configuration and Administration
Optional Initial
No
No
No
Yes
16
Configure Nuance and prepare the media server and

voice portal
Chapter 6, Configuring the

17
Install OpenScape licenses and create user profiles.
Section 6.5, Installing the

No
Licenses, on page 485
Table 1
No
A31003-S5070-J100-12-7631, 02/2013
29
IG_PrepGeneral.fm
Information Provision by the Customer
Step
Task
18
Create the OpenScape UC Application users.
Section 6.5, Installing the

No
Licenses, on page 485
Please also read the user guide
Desktop Client on this.
19
Install the OpenScape UC Application Desktop Client.
OpenScape UC Application desktop Yes

client User Manual.
20
Install the clients.
Chapter Client Installations
Yes
21
Telephones
No
optiPoint phones: adjust phone settings.
OpenStage phones: adjust phone settings.
Optional Initial
No
22
Install the Mobile Client Facade server.
Chapter 8, Installing the Mobile

Client Facade Server
Yes
23
Install the OpenScape Web Collaboration.
Chapter 9, Installing the

OpenScape Web Collaboration
Yes
24
Install and configure OpenScape Fusion for Google Apps Chapter 10, Installing and
Configuring OpenScape Fusion for
Google Apps
25
Integrate Microsoft Office Communications Servers/

Microsoft Lync Servers.
Chapter 11, Connecting the

Microsoft Office Communication
Server/Microsoft Lync Server
Yes
26
Integrate the instant messaging.
Chapter 12, Connecting Instant

Messaging
Yes
27
Connect the groupware.
Chapter 13, Groupware

Connection
Yes
28
Import the mapping table between OpenScape UC users Administrator documentation

and IBM Lotus Domino or Microsoft Exchange users.
Integrate the voice mail application (OpenScape native or
Xpressions integration).
29
Table 1
Yes
Yes
Yes
2.3 Information Provision by the Customer

Prior to starting the OpenScape UC Application deployment you should be
provided a set of deployment worksheets or instructions from the customer
administrator or representative. These requirements are defined in the
OpenScape UC Application Planning Guide, which also contains setup overviews
and charts.
30
A31003-S5070-J100-12-7631, 02/2013
IG_PrepGeneral.fm
Information Provision by the Customer
The purpose of the deployment worksheets is to provide you with everything you
will need to know about your specific installation scenario so that you can perform
the installation without interruptions. For examplealong with many other things
the worksheets can provide information about:
Deployment scenario to be installed
Small Deployment
Large Deployment
Requirements concerning additional components or connections, e. g.:
Groupware connection (Microsoft Exchange or IBM Lotus Domino)
Instant-messaging connection
Web Collaboration
Additional data:
User data
Device data
Trunk information
Routing requirements
etc.
The worksheets are an important supplement, and they will provide you with the
data you need as you perform the procedures in this installation guide.
A31003-S5070-J100-12-7631, 02/2013
31
IG_PrepGeneral.fm
Domain System Environment Preparation
2.4 Domain System Environment Preparation

In OpenScape UC Application there is no specific domain or system environment
preparation required. The following requirements must be complied with:
1. All servers and workstations must be networked and a DNS server must be
able to resolve their fully qualified domain names and IP addresses.
NOTE: If no DNS is available, name resolution via a local /etc/hosts file
on the servers as well as on the client computers is also sufficient.
2. IMPORTANT: Check if the system time of all OpenScape UC Applicationrelated computers is synchronized with a maximum difference of one second.
If the system time difference between the computers and the telephones
exceeds one second, contact the IT person responsible for the network and
request that the system time be synchronized. The Network Time Protocol
(NTP) is often used for synchronizing the system time (YaST > Network
Services > NTP Configuration).
If you use SRTP, the time zone must be identical on all computers.
32
A31003-S5070-J100-12-7631, 02/2013
IG_PrepVirtualization.fm
Providing Virtual Computers
Installing Virtual Computers
3 Providing Virtual Computers

This chapter informs you about the following topics:
Operating System Update Consequences
3.1 Installing Virtual Computers

This chapter informs you about the following topics:
Requirements on the Host Hardware
Overview of the VM Configuration Parameters
VMware Features and OpenScape UC Application
Restriction of the Product Application and Features
Settings for creating a VM
VM Parameters under Edit Settings
Installing the Operating System
Installing the VMware Tools
Computer Time Synchronization
Using Virtual Appliance for Small Deployment
Using Virtual Appliance for Large Deployment
NOTE: Virtual computers are supported for Small Deployment, Large

Deployment and Very Large Deployment.
A31003-S5070-J100-12-7631, 02/2013
33
IMPORTANT: Acquaint yourself which VMware version you want to use. If you
use VMware ESXi V5, only value E1000 may be selected as network board type
(see step 7 on page 49), as long as VMware ESXi V5 loses UDP packages
smaller than or equal to 40 byte for network boards of type VMXNET3. A network
board of type E1000 is less efficient than a network board of type VMXNET3. If
you use VMare ESXi V4.1 or older, select value VMXNET 3. The VMXNET-3
adapter has a built-in driver in SLES 11.
See the following URL for details about losing UDP packages:
http://kb.vmware.com/selfservice/
search.do?cmd=displayKC&docType=kc&externalId=2019944&sliceId=1&docTypeID=DT_KB_1_1&dial
ogID=325576986&stateId=1%200%20325582624
34
A31003-S5070-J100-12-7631, 02/2013
3.1.1 Requirements on the Host Hardware

Based on the resource and configuration requirements on the VMs for
OpenScape UC Application please consider the following dependencies of the
host hardware on the installation:
CPU
CPU resources shall be reserved for each VM according to Section 3.1.2,
Overview of the VM Configuration Parameters, on page 35. Less powerful
CPU resources may be sufficient for a smaller number of users in a
deployment scenario.
RAM
RAM must be reserved for all OpenScape UC Application nodes according to
Section 3.1.2, Overview of the VM Configuration Parameters, on page 35.
This means that the VM RAM must exist as physical RAM in the host.
Backup
Hard disk storage must be reserved for each VM according to Section 3.1.2,
Overview of the VM Configuration Parameters, on page 35. This memory
may be available to the host either locally or on an SAN.
IMPORTANT: A VM for the OpenScape UC Application places demands on a

host just like a VM for the OpenScape Voice, a VM for OpenScape Xpressions, a
VM for DLS or a VM for any other application. Such demands may vary. If a host
fullfils the sum of these demands, all of these VMs can run on this host.
3.1.2 Overview of the VM Configuration Parameters

The following table lists the parameters required for configuring an OpenScape
UC Application node. It applies for a connection to an OpenScape Voice V6 or
V7 and for a connection to a HiPath 4000 V5 or V6.
NOTE: Please obtain information about the hard disk size, the RAM and the
clock rate of the host etc. of virtual computers from the OpenScape UC Application Planning Guide.
IMPORTANT: It is recommended but not necessary to use LVM2 on virtual

computers according to step 2 on page 116. If you do not wish to back up data
using LVM2, please heed the consequences outlined in step 2 on page 116.
A31003-S5070-J100-12-7631, 02/2013
35
RAM shares3
Small Deployment
Application computer5
High
Normal Yes
No
Large Deployment /
Application computer5
High
Normal Yes
No
Media server computer6 7
High
Normal No
Yes
Frontend computer
High
Normal No
No
Instant-messaging server computer (Openfire) Normal Normal No
No
Mobile Client Facade computer
Normal Normal No
No
Web Collaboration server computer8
High
No
Any
Table 2
1
2
3
4
5
6
7
8
9
36
Normal Yes or
No9
Support of the
VMware Data
Recovery
Nodes
Using manual MAC

address4
Deployment scenario1
CPU shares2
Overview of the VM Configuration Parameters
Virtualization is not supported for the deployment scenario Integrated Deployment.

See step 2 on page 56.
It is irrelevant for the VM configuration parameters of the application computer if an instant messaging server (Openfire) is installed
on the application computer or not (see Section 12.2, Infrastructure, on page 596).
Please note that special requirements might apply for the media server computers, e g. SSE2.x (Streaming SIMD Extension)
support. For details see the OpenScape UC Application Planning Guide.
The ESX(i) server must provide not more than 75% of the ESX(i) server host CPU for a virtual media server computer to operate
on this host.
The OpenScape Web Collaboration Web Client can also be installed on this computer (see Chapter 9, Installing the OpenScape
Web Collaboration).
The OpenScape Web Collaboration component uses licensing based on CLS. The licenses are therefore bound to the MAC
address of the CLM. If the CLM is installed on a VM, it must have a manual MAC address (see also 1 on page 55).
A31003-S5070-J100-12-7631, 02/2013
3.1.3 VMware Features and OpenScape UC

Application
Using OpenScape UC Application in a virtual environment results in the
following restrictions:
Please remember that the OpenScape UC Application is a real-time

application.
Dynamic resource management

In a clustered virtual environment, VMs must use the automation level
Partially Automated or Manual for OpenScape UC Application nodes. The
automation level Fully automated is not recommended (see restrictions on
vMotion) and can only be used at the customer's own risk.
VMotion
VMware vMotion is supported with restrictions:
IMPORTANT: If the radio button Change Host in the Migrate Virtual
Machine dialog in vMotion is activated, a running OpenScape UC Application
node is shifted from an ESX(i) host in the cluster to another ESX(i) host. This
feature is only supported with minimum or without load. We do not
recommend to perform this action during business hours as it may lead to
lost conferences, lost calls and problems with the voice quality in conferences
or when accessing the voice portal. The OpenScape UC Application node
may not be available for 10 or 20 seconds, however, it will return to its normal
operating state automatically.
IMPORTANT: If you use a VMotion-based feature, make sure that a

dedicated vMotion network between the ESX(i) hosts with a minimum transmission rate of 1 Gbit/s is available for this feature. Separate the vMotion
networks from the application networks. The migration of a running VM from
one ESX(i) host to another ESX(i) host is an example for a VMotion based
feature.
VMware fault tolerance

OpenScape UC Application cannot be used in a cluster with active VMware
fault tolerance (see step 10 on page 52).
VMware High Availability
A31003-S5070-J100-12-7631, 02/2013
37
VMware High Availability is supported. One or all OpenScape UC Application

nodes may run on VMs protected by VMware High Availability.
IMPORTANT: The customer service of Siemens Enterprise Communications
GmbH & Co. KG is not in charge of rectifying errors that result from high-availability events in the OpenScape UC Application and connected application
computers (VMs) such as a faulty file system of a virtual computer caused by
defective hardware. The customer service will therefore in particular not
create a trouble ticket. It is not an OpenScape UC Application error if a virtual
computer or an installation on real computers does not boot correctly after a
high-availability event - for example due to data inconsistencies. When this
unlikely event occurs, fallback solutions must be applied here. The responsibility for restoring the functionality after a defect (hardware replacement, data
backup and import) must be clarified by a maintenance agreement.
VMware Data Backup and VMware Data Recovery

VMare Data Backup and VMware Data Recovery are supported for
OpenScape UC Application with the following restrictions:
They are supported for all VMware versions that are supported for
OpenScape UC Application, i. e. currently VMware ESXi V4.0, V4.1, V5.0
and V5.1.
VMware ESXi is also known as VMware vSphere Hypervisor.
They are supported for all deployment scenarios except Integrated

Deployment.
If you want to execute a backup, execute the following major steps:
Check whether the OpenScape UC Application is running on the

application computer:
/etc/init.d/symphoniad status
If it is not running, start it:

/etc/init.d/symphoniad start
38
Execute the /usr/sbin/pre-freeze-script script on the

application computer. Consider the following:
This script is only available on the application computer.
It checks which database type (Solid database or MySQL database)

is used.
It creates a database checkpoint.
In case of no error, it returns a zero exit code.
A31003-S5070-J100-12-7631, 02/2013
In case of failure, either because the database type could not be

determined or the database checkpoint could not be created, it
returns a nonzero exit code and the checkpoint is not created.
As a final step, the script performs a Linux flush by executing a sync

call to the virtual computer.
Do not continue until the script has finished.
Execute the backup on the application computer according to the

VMware documentation, e. g. the VMware Virtual Machine Backup
Guide:
http://www.vmware.com/pdf/vsphere4/r40/
vsp_vcb_15_u1_admin_guide.pdf
For Large Deployment and Very Large Deployment, execute the backup
on the frontend computers and media server computers as well.
If you want to execute a data recovery, execute the following major steps:
Make sure that the OpenScape UC Application has been stopped.

/etc/init.d/symphoniad stop
Execute the data recovery on the application computer according to the

VMware documentation e. g. the VMware Data Recovery Administration
Guide:
http://www.vmware.com/support/pubs
Execute the data recovery according to the VMware documentation e. g.

the VMware Data Recovery Administration Guide, as well on the frontend
computers and the application computers.
Snapshots
When you take a snapshot of OpenScape UC Application in a VM before an
update or upgrade, you can quickly return to the state before these actions.
Please note that taking a snapshot of a VM creates modification files that
contain the changes compared to the last snapshot and are referenced during
the file access of the VM. This decreases the performance significantly.
IMPORTANT: We therefore urgently recommend to remove the snaphots
after checking the functionality of the updated or upgraded system, and thus
to integrate the modification files in the virtual harddisk and to delete them.
While snapshots may well be deployed in test and demo environments, they
should not be used in live operation except in the above update or upgrade
situation.
Never take more than one snapshot per VM.
VMware tools
A31003-S5070-J100-12-7631, 02/2013
39
We recommend to install the VMware Tools. For details see Section 3.1.8,
Installing the VMware Tools, on page 62.
3.1.4 Restriction of the Product Application and

Features
Some product applications and features are subject to restrictions.
3.1.4.1 Cold Stand-by Availability Model

The cold stand-by availability model, which provides a separate physical server,
is not required in a VMware environment and thus not supported.
You receive the same functionality when you start the VM of the application
computer on another host.
3.1.4.2 Warm Stand-by Availability Model

To obtain information on the Warm stand-by availability model using an additional
cluster software as e. g. IBM Tivoli Automation (TSA), contact the Professional
Services Center of Competence UC.
40
A31003-S5070-J100-12-7631, 02/2013
3.1.5 Settings for creating a VM

This section describes the settings we recommend when you create a new VM
on which a node of an OpenScape UC Application deployment scenario is found.
IMPORTANT: When you create a virtual computer for Small Deployment or
Large Deployment, you can follow the instructions in Section 3.1.10, Using
Virtual Appliance for Small Deployment, on page 69 or Section 3.1.11, Using
Virtual Appliance for Large Deployment, on page 84 alternatively to those in
- Section 3.1.5, Settings for creating a VM, on page 41,
- Section 3.1.6, VM Parameters under Edit Settings, on page 55,
- Section 3.1.7, Installing the Operating System, on page 58 and
- Section 3.1.9, Computer Time Synchronization, on page 65.
IMPORTANT: Virtual Appliance is not supported for Very Large Deployment.

1. Activate the Custom radio button under Configuration for defining individual
settings for the new VM.
A31003-S5070-J100-12-7631, 02/2013
41
2. Specify an individual name for the new VM.
3. Always activate the Virtual Machine Version 7 radio button under Virtual
Machine Version. If Virtual Machine 8 is offered, activate this radio button.
However, Virtual Machine 9 or higher is not supported.
42
A31003-S5070-J100-12-7631, 02/2013
4. Always activate the Linux radio button under Guest Operating System and
select version Suse Linux Enterprise 11 (64-bit).
A31003-S5070-J100-12-7631, 02/2013
43
5. Enter the number of CPU cores under CPUs according to the OpenScape UC
Application Planning Guide:
Depending on the VMware version used the following dialog is displayed. Set
the values in the fields Number of virtual sockets and Number of cores per
virtual socket in such a way that the value in the Total number of cores field
corresponds to the specifications in the OpenScape UC Application Planning
Guide.
44
A31003-S5070-J100-12-7631, 02/2013
IMPORTANT: The following sub-steps are only valid for SLES 11 SP1.If you
change the number of virtual processors after setting up the operating
system, the following applies:
When you switch from a single to a multiple processor while using SLES, set
the SMP kernel (symmetric multiprocessing) in the GRUB (Grand Unified
Bootloader). When you switch from a multiple to a single processor while
using SLES, set the default kernel (uni processor) in the GRUB. Execute the
following steps:
a) Execute the command uname -r to see which kernel is used.
Example output:
2.6.16.60-0.77.1-smp
or
2.6.16.60-0.42.5-default
smp indicates a multiple processor, default indicates a single
processor.
A31003-S5070-J100-12-7631, 02/2013
45
b) Execute the yast command.

NOTE: See Section B.1, General Operation of YaST, on page 1044 for
a YaST operation guide.
c) Open System > Boot Loader.
IMPORTANT: Please note that OpenScape UC Application UEFI

(Unified Extensible Firmware Interface) is not supported as alternative to
the BIOS. If required, follow the instructions in step 92 on page 162 to
ensure that UEFI is disabled.
d) Activate the check box associated to the kernel to be used after you have
changed the number of processors.
e) Select Set as Default.
f)
Select Finish.
g) Select Quit.
h) Stop the OpenScape UC components on the virtual computer.
i)
46
Shut down the virtual computer.
A31003-S5070-J100-12-7631, 02/2013
j)
Select the virtual computer in the vSphere client with the right
mousebutton.
k) Open Edit Settings... > Hardware > CPUs and set the desired number
of virtual processors.
l)
Click on the OK button.
m) Start the virtual computer.

n) Use the uname -r command to check whether the correct kernel is used.
In all other cases of changing the number of virtual CPUs there is nothing
special to heed when selecting a kernel. Virtual computers based on
Windows Server 2008 operating systems detect the number of virtual CPUs
automatically and install the required drivers in case of changes. The virtual
computer may have to be rebooted.
A31003-S5070-J100-12-7631, 02/2013
47
6. Set the workstation memory under Memory according to the OpenScape UC

Application Planning Guide:
IMPORTANT: In productive environments we urgently recommend the
physical presence of the RAM assigned to an OpenScape UC Application
node on the host and reserving it for the node (see also Section 3.1.6, VM
Parameters under Edit Settings, on page 55).
48
A31003-S5070-J100-12-7631, 02/2013
7. Network board
a) In the How many NICs do you want to connect? field select value 1.
b) Enter the name of the network the part of which is to become the VM in
the Network field.
c) If you use VMware ESXi V5, select value E1000 in the Adapter field as
long as VMware ESXi V5 loses UDP packages smaller than or equal to
40 byte for network boards of type VMXNET3. See the following URL for
details:
ogID=325576986&stateId=1%200%20325582624
NOTE: A network board of type E1000 is less efficient than a network
board of type VMXNET3.
If you use VMare ESXi V4.1 or older, select value VMXNET 3. The
VMXNET 3 adapter has a built-in driver in SLES 11.
A31003-S5070-J100-12-7631, 02/2013
49
NOTE: If you create a VM in a cluster, connect the network board with a

virtual IP switch that can be addressed by several VMs of several hosts within
this cluster. The network connection will otherwise get lost if the VM is started
on another host in the cluster.
8. Leave the defaults under SCSI Controller unchanged.
50
A31003-S5070-J100-12-7631, 02/2013
9. Activate the Create a new virtual disk radio button under Select the type of
disk to use for a new installation to create a new harddisk.
A31003-S5070-J100-12-7631, 02/2013
51
10. Specify the harddisk capacity under Create a Disk according to the
OpenScape UC Application Planning Guide:
NOTE: You can enlarge the harddisk capacity retrospectively under the
following conditions:
- The virtual computer is switched off.
- There are no backup points (snapshots).
NOTE: You cannot minimize the harddisk capacity.
NOTE: When operating in test and demonstration systems you can save
considerable amounts of memory by activating Allocate and commit space
on demand (Thin provisioning). This means that the virtual harddisk grows
with the actually required memory. This option is supported for all virtual
computers of OpenScape UC Application, but we do not recommend it for
the application and media server computer in productive systems.
If the VMware version allows using Thick Provision Lazy Zeroed, this option
must be activated for the application computer and media server computer in
productive systems.
NOTE: Leave the Support clustering features such as Fault Tolerance

check box deactivated.
52
A31003-S5070-J100-12-7631, 02/2013
Below the same dialog of another VMware version with Thick Provision
Lazy Zeroed.
A31003-S5070-J100-12-7631, 02/2013
53
11. Leave the defaults under Advanced Options unchanged.
12. Activate the Edit the virtual machine settings before completion radio
button under Ready to Complete for setting further VM parameters
according to Section 3.1.6, VM Parameters under Edit Settings, on page 55.
54
A31003-S5070-J100-12-7631, 02/2013
3.1.6 VM Parameters under Edit Settings

When you create a VM for OpenScape UC Application, you should change further
parameters as follows:
1. Table 2 on page 36 specifies whether the Manual radio button under
Hardware > New NIC (adding) > MAC Address must be activated and a
permanent MAC address needs to be entered for this VM.
Using a permanent MAC address ensures that the MAC address is not
changed by any VMware function. The permanent address is required for
license binding.
A31003-S5070-J100-12-7631, 02/2013
55
2. Under Resources > CPU > Shares, select the value according to the CPU
shares column of the Table 2 on page 36.
Value High ensures a higher percentage of intervals for time-critical
functionalities such as media server and call processing.
IMPORTANT: We urgently recommend to reserve the required amount of

CPU resources. You can determine the CPU frequency to be reserved by
multiplying the cores required for a node with the processor frequency
required for the VMware configuration.
Example: If eight cores are required for one Small Deployment node in a 2.66
GHz CPU according to specification, you need to reserve 21280 MHz
(82660 MHz).
56
A31003-S5070-J100-12-7631, 02/2013
3. Define the RAM to be reserved under Resources > Memory.

IMPORTANT: For customer environments the host platform should provide
at least as much real RAM as is specified by the RAM sum of all VMs
according to OpenScape UC Application Planning Guide.
A31003-S5070-J100-12-7631, 02/2013
57
3.1.7 Installing the Operating System

To install the operating system in the VM you need to configure the VM in a way
that it is booted by the operating system DVD/CD. The DVD/CD can be provided
as real DVD/CD as well as ISO image.
There are several options for booting from a DVD/CD. One of them is the
following:
1. Activate the radio button The next time the virtual machine boots, force
entry into the BIOS setup screen under Options > Advanced >
Boot Options > Force BIOS Setup.
The BIOS will then start first next time the VM is booted.
2. Click on the OK button.
3. Select the new entry for the VM with the right mousebutton and select
Power > Power On.
58
A31003-S5070-J100-12-7631, 02/2013
4. Select the new entry for the VM with the right mousebutton and select Open
Console or click on the Console tab.
A31003-S5070-J100-12-7631, 02/2013
59
5. Switch to the Boot tab and configure the CD-ROM drive as initial boot
medium, i. e. it must be in top position in the booting sequence list.
NOTE: Press the + or - key to change the position of the selected boot
medium in the boot sequence.
60
A31003-S5070-J100-12-7631, 02/2013
6. Select the DVD/CD or ISO file storage location from where booting is to be
performed.
7. Save the modifications and leave the BIOS. The VM boots from the selected
DVD/CD or from the ISO image.
8. Now you can install the operating system like setting it up on a real computer.
IMPORTANT: When installing the operating system please note
- Point 2 on page 116 (file system),
- Point 3 on page 118 (partition sizes) and
- Point 49 on page 140 (no X-server, no graphic desktops).
NOTE: You can set further points from Section 4.1, File System and
Operating System, on page 116 already during the SLES setup.
A31003-S5070-J100-12-7631, 02/2013
61
3.1.8 Installing the VMware Tools

The VMware tools contain several driver modules to be installed on Linux on the
VM to boost the performance and to improve operating the console in the
VMware vSphere client. These tools need to be installed upon creating a VM.
NOTE: Since the VMware tools to be installed depend on the version of the
SLES kernel in the VM, install any SLES service packs or SLES hotfixes before
setting up the VMware tools. Make sure to boot the VM after having installed a
new SLES kernel.
NOTE: The following information about SMP (symmetric multiprocessing) is only

valid for SLES 11 SP1: Before you install the VMware tools check whether an smp
kernel that supports multiple cores has already been installed. Use the uname
a command for displaying the installed kernel.
In some cases (e. g. if only one CPU core was initially assigned to the VM) an
SLES kernel is installed during the SLES setup that supports only one CPU core.
It does not support any additional CPU cores assigned at a later date. In this case
install the smp kernel using YaST.
uname -a
Linux mucoscvsrv26 2.6.16.60-0.62.1-smp #1 SMP Mon Apr 12
18:53:46 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux
Start the VMware tools setup by selecting Guest > Install/Upgrade VMware
Tools in the VM context menu. This function mounts a virtual CD with the VMware
tools in the installation format suitable for the operating system on the VM.
Confirm the message with a click on OK.
62
A31003-S5070-J100-12-7631, 02/2013
3.1.8.1 Installing the VMware Tools on SLES

How to set up the VMware tools on SLES:
1. Mount the CD as usual using the device name /dev/cdrom.
mkdir /mnt/cdrom
mount /dev/cdrom /mnt/cdrom
Output:
mount: block device /dev/hda is write-protected, mounting
read-only
List the contents of the directory:
ls /mnt/cdrom
Output:
VMwareTools-<version>.tar.gz
manifest.txt
2. Extract the TAR archive that contains the VMware tools in a temporary
directory:
cd /tmp
tar zxvf /mnt/cdrom/VMwareTools-<version>.tar.gz
vmware-tools-distrib/
vmware-tools-distrib/lib/
vmware-tools-distrib/lib/modules/
NOTE: Instead of the cd /tmp command you can also use command cd /
software, for example.
3. Execute the installation script:
cd vmware-tools-distrib/
bash vmware-install.pl
Output:
Creating a new VMware Tools installer database using the tar4
format.
Installing VMware Tools.
In which directory do you want to install the binary files?
[/usr/bin]
4. Press the enter key to confirm the suggested default value. Repeat this step
for the next suggested default values as well.
Output:
What is the directory that contains the init directories
(rc0.d/ to rc6.d/)?
[/etc/init.d] /my/directory
What is the directory that contains the init scripts?
[/etc/init.d]
In which directory do you want to install the daemon files?
[/usr/sbin]
In which directory do you want to install the library files?
A31003-S5070-J100-12-7631, 02/2013
63
[/usr/lib/vmware-tools]
The path "/usr/lib/vmware-tools" does not exist currently.
This program is going to create it, including needed parent
directories. Is this what you want?
[yes]
In which directory do you want to install the documentation
files?
[/usr/share/doc/vmware-tools]
The path "/usr/share/doc/vmware-tools" does not exist
currently. This program is going to create it, including
needed parent directories. Is this what you want?
[yes]
The installation of VMware Tools 4.0.0 build-208167 for Linux

completed successfully. You can decide to remove this
software from your system at any time by invoking the
following command: "/usr/bin/vmware-uninstall-tools.pl".
Before running VMware Tools for the first time, you need to
configure it by invoking the following command: /usr/bin/
vmware-config-tools.pl
Do you want this program to invoke the command for you now?
[yes]
Stopping VMware Tools services in the virtual machine:
...
The configuration of VMware Tools 4.0.0 build-208167 for
Linux for this running kernel completed successfully.
You must restart your X session before any mouse or graphics
changes take effect.
You can now run VMware Tools by invoking the following
command:
"/usr/bin/vmware-toolbox" during an X server session.
To enable advanced X features (e.g., guest resolution fit,
drag and drop, and file and text copy/paste), you will need
to do one (or more) of the following:
1. Manually start /usr/bin/vmware-user
2. Log out and log back into your desktop session; and,
3. Restart your X session.
Enjoy,
--the VMware team
Found VMware Tools CDROM mounted at /mnt/cdrom. Ejecting
device /dev/hda ... mucoscsrv211:/tmp/vmware-tools-distrib #
5. Deleting the installation files
The extracted installation files occupy a considerable amount of harddisk
memory. We recommend to remove these files from the temporary directory
when you have finished setting up the VMware tools.
64
A31003-S5070-J100-12-7631, 02/2013
3.1.9 Computer Time Synchronization

The NTP (Network Time Protocol) must be correctly configured for all
OpenScape UC Application nodes to have the same time and being operable
reliably.
How to configure the NTP:
Deactivating the Time Synchronization by VMware Tools
Configuring the NTP Service
3.1.9.1 Deactivating the Time Synchronization by VMware

Tools
The default settings of the VMware tools effect a time synchronization between
host and VM. Another time synchronization would be performed in parallel based
on the NTP configuration, so that the VM would attempt to synchronize itself with
two time sources. As a result, the system time would be instable.
Deactivate under Edit Settings... > Options > VMware Tools > Advanced the
Synchronize guest time with host check box. You can only do this when the
virtual computer is shut down.
Time synchronization is now performed by NTP only.

A31003-S5070-J100-12-7631, 02/2013
65
3.1.9.2 Configuring the NTP Service

To configure the NTP service, edit the NTP configuration file /etc/ntp.conf as
follows:
1. Comment the server and the fudge entry for the local clock so that the VM
does not execute a fallback.
## Undisciplined Local Clock. This is a fake driver intended for backup

## and when no outside source of synchronized time is available.
##
# server 127.127.1.0
# local clock (LCL)
# fudge 127.127.1.0 stratum 10
# LCL is unsynchronized
2. Configure the IP address or the host name of the time server and add the
burst and iburst option.
## information on the burst and iburst options

server 10.9.0.9
66
burst iburst
A31003-S5070-J100-12-7631, 02/2013
3. Editing the ntp.conf file leads to some inconsistencies in different

configuration files. To avoid this, enter command yast and open
Network Services > NTP Configuration.
A31003-S5070-J100-12-7631, 02/2013
67
4. Select Continue.
The table shows the value you have just edited in the /etc/ntp.conf file:
Example:
server 10.9.0.9
5. Activate the Now and On boot check box.
6. Select OK.
7. Select Quit.
8. Reboot the VM.
9. Check the /var/log/boot.msg file for error messages of the NTP start.
10. Check the output of the date command for a correct time display.
68
A31003-S5070-J100-12-7631, 02/2013
3.1.10 Using Virtual Appliance for Small Deployment

3.1.10.1 General Considerations
Virtual Appliances are pre-installed, pre-configured and immediately usable
applications and software solutions already compiled with an operating system in
a virtual computer.
The Virtual Appliance for OpenScape UC Application installs the SLES operating
system and the OpenScape UC Application, i. e. you need not follow the
instructions in Chapter 4, Installing and Configuring the Computer and Operating
System and in most sections of Chapter 5, Installing the OpenScape UC
Application.
NOTE: This Virtual Appliance has been released for Small Deployment and
Large Deployment only.
NOTE: You can use the Virtual Appliance on VMware ESXi V5 but not on
VMware ESXi V4.x because it was created using a virtual machine Version 8.
When using Virtual Appliances, LVM2 partitions are created. syncUC can be
used.
When using Virtual Appliances, an Openfire server can either be installed on the
application computer or on an separate computer, the instant-messaging
computer (see Section 12.2, Infrastructure, on page 596).
Update, upgrade or migration will be performed according to the instructions in
Chapter 15, Updating, Upgrading and Migrating at a later date.
The information in the following sections also applies for a virtual computer
created with Virtual Appliance:
Section 3.1.1, Requirements on the Host Hardware, on page 35
Section 3.1.2, Overview of the VM Configuration Parameters, on page 35
Section 3.1.3, VMware Features and OpenScape UC Application, on page

37
Section 3.1.4, Restriction of the Product Application and Features, on page

40
A31003-S5070-J100-12-7631, 02/2013
69
3.1.10.2 Major Steps

Using the Virtual Appliance is divided into the following major steps:
1. Creating a vApp.iso file
2. Creating a virtual computer by using an OVF or OVA file
3. Starting the virtual computer by using the vApp.iso file
3.1.10.3 Installation
Execute the following setup steps using Virtual Appliance:
Creating the vApp.iso file
The first major step is to create a vApp.iso file. This file only contains an XML
file that will contain configuration information about the OpenScape UC
Application, e. g. computer names, FQDNs, IP addresses, passwords etc. The
ISO file will be needed in step 18 on page 81 when starting the application
computer.
1. Collect the following data.
Mandatory data
a) Password of the Symphonia administrator (compare step 7 on page 200
for the installation without Virtual Appliance).
IMPORTANT: This password must comply with the security policies,
which are defaulted as follows:
- At least 8 characters
- At least one special character
- At least one number
- At least one capital letter
- Not more than 3 identical characters in a row
b) Password for user root of the operating system.
70
A31003-S5070-J100-12-7631, 02/2013
c) Community name for the OpenScape UC Application (compare step 8 on

page 200 for the installation without Virtual Appliance).
IMPORTANT: If several application computers are used in the network,
verify that the community names of these OpenScape UC Application
systems differ.
IMPORTANT: Verify that the Community names are identical on all

computers of an OpenScape UC Application system (application
computer and PBX computer).
IMPORTANT: The community name has nothing to do with the SNMP

Community String.
IMPORTANT: Capital letters "A-Z", small letters "a-z", digits "0-9" and the
underscore "_" are permitted. The latter must not appear at the beginning
or end of the name. The corresponding regular expression reads as
follows:
[A-Za-z0-9][A-Za-z0-9_]*[A-Za-z0-9]
Example:
99_Red_Balloons
d) Password of the Solid database administrator (compare step 11 on page
201 for the installation without Virtual Appliance). Due to security
concerns it should not be the default password (dba).
e) Name for indicating the application computer of the OpenScape UC
Application in the CMP (compare step 10 on page 201 for the installation
without Virtual Appliance).
IMPORTANT: This name (value of SI_LOCAL_NAME) must not contain
spaces.
f)
Fully qualified domain name of the application computer (compare step 9

on page 201 for the installation without Virtual Appliance)
g) IP address of the application computer (compare step 9 on page 201 for

the installation without Virtual Appliance)
h) Network mask of the application computer
i)
Default gateway of the application computer
A31003-S5070-J100-12-7631, 02/2013
71
j)
72
Time zone of the application computer
A31003-S5070-J100-12-7631, 02/2013
Use the values shown in the /usr/shared/zoneinfo directory or the Olson

IDs in the following table.
Time Zone
Olson ID
Offset to UTC
Honolulu
Pacific/Honolulu
UTC-10
Anchorage
America/Anchorage
UTC-9
Pacific Standard Time
US/Pacific
UTC-8
Moutain Standard Time
US/Mountain
UTC-7
Central Standard Time
US/Central
UTC-6
Eastern Standard Time
US/Eastern
UTC-5
Atlantic Standard Time
Canada/Atlantic
UTC-4
Sao Paulo
America/Sao_Paulo
UTC-3
South Georgia
Atlantic/South_Geogia UTC-2
Azores
Atlantic/Azores
UTC-1
Reykjavik
Atlantic/Reykjavik
UTC
London
Europe/London
UTC
Lisbon
Europe/Lisbon
UTC
Berlin
Europe/Berlin
UTC+1
Madrid
Europe/Madrid
UTC+1
Paris
Europe/Paris
UTC+1
Rome
Europe/Rome
UTC+1
Cairo
Africa/Cairo
UTC+2
Johannesburg
Africa/Johannesburg
UTC+2
Moscow
Europe/Moscow
UTC+3
Tehran
Asia/Tehran
UTC+3:30
Yerevan (Armenia)
Asia/Yerevan
UTC+4
Calcutta
Asia/Calcutta
UTC+5:30
Dhaka
Asia/Dhaka
UTC+6
Ho Chi Minh
Asia/Saigon
UTC+7
Hong Kong
Asia/Hong_Kong
UTC+8
Shanghai
Asia/Shanghai
UTC+8
Taipei
Asia/Taipei
UTC+8
Tokyo
Asia/Tokyo
UTC+9
Sydney (New South Wales) Australia/Sydney
UTC+10
Salomon Islands
Pacific/Guadalcanal
UTC+11
Auckland
Pacific/Auckland
UTC+12
Table 3
Examples for Olson IDs of Time Zones
A31003-S5070-J100-12-7631, 02/2013
73
k) IP address of the PBX computer

The IP address for the administrator access is needed, not the IP address
for e. g. SIP communication or MGCP communication.
l)
SRX user account name of the PBX computer, e. g. srx
m) Password for this SRX user account

Optional data
n) IP address of the first DNS server computer
o) Search domain used by this first DNS server
p) IP address of the second DNS server computer
q) Search domain used by this second DNS server
r)
IP address of the NTP server computer

IMPORTANT: The system time of all OpenScape UC Application-related
computers must be synchronized with a maximum difference of one
second. The system time can also be synchronized retrospectively (see
Section 3.1.9.2, Configuring the NTP Service, on page 66).
If SRTP is used, the time zone too must be the same on all computers.
s) First port number used on the NTP server

2. Fill the CDC tool with the data you collected in step 1 on page 70. Use the tool
to create the vApp.iso file.
This tool is an XLS file that can be downloaded from the Software Supply
Server (SWS) by using an account that has a BASIC role or higher.
IMPORTANT: A role with higher privileges (ADVANCED or EXPERT) is not
needed for this step but it might be needed for downloading the OVF or OVA
file depending on the project status (see step 3 on page 76). The role your
account has is shown at the top of the web page when you are logged in to
the SWS.
Please obtain information about using the CDC tool from e. g. the following
sections of the OpenScape Voice V7, Design and Planning Manual:
Customer Data Collection guide:
74
Standard Solution Configuration
OpenScape Virtual Appliance
Installation Common Configuration Data File (vApp)

A31003-S5070-J100-12-7631, 02/2013
Virtual Appliance Worksheet
Continue with step 3 on page 76.
A31003-S5070-J100-12-7631, 02/2013
75
Using the OVF file

3. Execute the following sub-steps to download the OVF or OVA file from the
Software Supply Server (SWS):
t)
Login to the SWS.

IMPORTANT: Check which role your SWS account has. It is shown at
the top of the web page when you are logged in to the SWS. Depending
on the project status, the BASIC role might not be sufficient for
downloading the OVA files. You might need the ADVANCED role or
EXPERT role.
u) Search for the product version <version> CMP vApps.

Example:
v) Download the OVF or OVA file.

An OVA (Open Virtual Archive) file is a TAR file with OVF files inside. OVF
(Open Virtualization Format) is an open standard to pack and distribute
Virtual Appliances for virtual computers.
The OVF or OVA file has about the size of 10 GB, i. e. they cannot be
stored on an FAT32-formatted USB stick.
4. Open File > Deploy OVF Template... in VMware vCenter Management Tool.
5. Enter the path to the OVF or OVA file in the Deploy from a file or URL field.
76
A31003-S5070-J100-12-7631, 02/2013
6. Click on Next.
7. Click on Next.
A31003-S5070-J100-12-7631, 02/2013
77
8. Enter the name of the virtual computer to be indicated in VMware in the Name
field.
9. Click on Next.
10. Select the cluster the virtual computer is to operate on.
78
A31003-S5070-J100-12-7631, 02/2013
11. Click on Next.
12. Select the host the virtual computer is to operate on.

13. Click on Next.
A31003-S5070-J100-12-7631, 02/2013
79
14. Activate the Thick provisioning format check box (compare with step 10 on
page 52 of the installation of a virtual computer without Virtual Appliance).
- There are no backup points (snapshots).
considerable disk space by activating Thin provisioned format. This means
that the virtual harddisk grows with the actually required memory. This option
is supported for all virtual computers of OpenScape UC Application, but we
do not recommend it for the application and media server computer in
productive systems.
15. Click on Next.
16. Click on Finish.
80
A31003-S5070-J100-12-7631, 02/2013
17. A new virtual computer is displayed in the inventory of the VMware vCenter
Management tool.
NOTE: If you click the right mouse button on the computer name in the
inventory of the VMware vCenter Management tool and open Edit
settings... > Resources > CPU > Shares, the value Custom is shown
instead of the value according to the CPU shares column of the Table 2 on
page 36. This is correct. There is no need to change it.
Starting
18. Provide the vApp.iso file you created in step 2 on page 74 to the virtual
computer as usual under Edit Settings... > Hardware > CD/DVD Drive in
the Datastore ISO file field.
In doing so make sure that the Connected and Connect at power on check
boxes are active in the Device Status section.
19. Start the virtual computer. Reconfiguration starts automatically.
20. Open Edit Settings... for the virtual computer and check the virtual computer
by the following sub-steps:
a) Set under Hardware > CPUs the number of CPU cores that the
OpenScape UC Application Planning Guide demands.
If the fields Number of virtual sockets and Number of cores per virtual
socket are displayed, set them in such a way that the value in the Total
number of cores field corresponds to the specifications in the
OpenScape UC Application Planning Guide.
IMPORTANT: If you change the number or virtual processors after
installing the operating system, the information in step 5 on page 44
applies.
b) Set the workstation memory under Hardware > Memory according to the
IMPORTANT: In productive environments we urgently recommend the
physical presence of the RAM assigned to an OpenScape UC Application
node on the host and reserving it for the node (see also Section 3.1.6,
VM Parameters under Edit Settings, on page 55).
c) Verify that value E1000 is displayed under Hardware > Network
Adapter > Adapter Type as long as VMware ESXi V5 loses UDP
packages less or equal to 40 byte for network boards of type VMXNET3.
See the following URL for details:
A31003-S5070-J100-12-7631, 02/2013
81
ogID=325576986&stateId=1%200%20325582624
A network board of type E1000 is less efficient than a network board of
type VMXNET3.
NOTE: If you create a VM in a cluster, connect the network board with a
virtual IP switch that can be addressed by several VMs of several hosts
within this cluster. The network connection will otherwise get lost if the VM
is started on another host in the cluster.
If required, delete the network board with a click on Remove and create
a new one with a click on Add....
d) Table 2 on page 36 specifies whether the Manual radio button under
Hardware > Network Adapter > MAC Address must be activated and a
permanent MAC address needs to be entered for this VM.
Using a permanent MAC address ensures that the MAC address is not
changed by any VMware function. The permanent address is required for
license binding.
If required, delete the network board with a click on Remove and create
a new one with a click on Add....
e) Under Resources > CPU > Shares, select the value according to the
CPU shares column of the Table 2 on page 36.
Value High ensures a higher percentage of intervals for time-critical
functionalities such as media server and call processing.
IMPORTANT: We urgently recommend to reserve the required amount
of CPU resources. You can determine the CPU frequency to be reserved
by multiplying the cores required for a node with the processor frequency
required for the VMware configuration.
Example: If eight cores are required for one Small Deployment node in a
2.66 GHz CPU according to specification, you need to reserve
21280 MHz (82660 MHz).
f)
Define the RAM to be reserved under Resources > Memory.

IMPORTANT: For customer environments the host platform should
provide at least as much real RAM as is specified by the RAM sum of all
VMs according to OpenScape UC Application Planning Guide.
82
A31003-S5070-J100-12-7631, 02/2013
g) Click on OK to save the changes.

21. Install the VMware tools according to Section 3.1.8, Installing the VMware
Tools, on page 62.
22. IMPORTANT: Please note that OpenScape UC Application UEFI (Unified
Extensible Firmware Interface) is not supported as alternative to the BIOS. If
required, follow the instructions in Section 4.2.5, No support of UEFI (Unified
Extensible Firmware Interface), on page 162 to ensure that UEFI is disabled.
23. Check whether the applications you need are installed (see step 6 on page
265) and install them if required (see step 9 on page 267).
24. Check whether the languages you need are installed (see step 12 on page
270) and install them if required (see step 13 on page 271 to step 20 on page
279).
25. Start the MRCP service, the Nuance TTS and the Nuance ASR, if available:
/etc/init.d/NSSservice start
26. Start OpenScape UC Application:
27. Check the OpenScape UC Application status:
Backup
28. Save the vApp.iso and the OVF file on a medium that can be accessed
even if the application computer is damaged beyond repair.
Check
29. Follow the instructions in Section 5.4, Checking the Installation, on page
347 and heed the information in Section 5.5, Trouble Ticket, on page 358.
Configuration
30. Execute the instructions given in Chapter 6, Configuring the OpenScape UC
Application.
Further components
31. If required, continue with the chapters that follow Chapter 6 in Part 3 Installation, Configuration, and Connections.
A31003-S5070-J100-12-7631, 02/2013
83
3.1.11 Using Virtual Appliance for Large Deployment

Virtual Appliances are pre-installed, pre-configured and immediately usable
applications and software solutions already compiled with an operating system in
a virtual computer.
The Virtual Appliance for OpenScape UC Application installs the SLES operating
system and the OpenScape UC Application, i. e. you need not follow the
instructions in Chapter 4, Installing and Configuring the Computer and Operating
System and in most sections of Chapter 5, Installing the OpenScape UC
Application.
NOTE: This Virtual Appliance has been released for Small Deployment and
There are four Virtual Appliances for Large Deployment for four types of
computers to be created:
- Application computer
- Frontend computer
- Media server computer
- Instant-messaging server computer (Openfire server computer).
NOTE: Virtual Appliance for Large Deployment requires an Openfire server that
is installed on a separate computer, the instant-messaging server computer. The
instant-messaging computer is mandatory for the installation by using Virtual
Appliance but the usage of the Openfire server after the installation is not a must.
The Openfire server must not be installed on the application computer (see
Section 12.2, Infrastructure, on page 596).
NOTE: You can use the Virtual Appliance on VMware ESXi V5 but not on
VMware ESXi V4.x because it was created using a virtual machine Version 8.
IMPORTANT: Using Virtual Appliance requires importing an OVA file. This

process might produce too much network load and a timeout error. Try the import
again at a time with generally low network load.
The Virtual Appliance uses e. g. 192.168.50.100 by default as the IP address of
the application computer. The front-end computers, the media server computers
and the instant-messaging server computer dynamically determine free IP
84
A31003-S5070-J100-12-7631, 02/2013
addresses within the 192.168.50.0 network using ARP. These IP addresses are
only used as a first step in order for the computers to perform their initial
communication. In a later step, the IP addresses that have been provided by the
CDC tool will be used. For the case that the default use of the 192.168.50.0 IP
address cannot be used, e. g. when all virtual appliances are not installed on the
same VMware ESXi host, the user may change the computers IP address,
subnet mask and default gateway during the computers first start up.
When using Virtual Appliances, LVM2 partitions are created. syncUC can be used
on the application computer, the frontend computers and the media server
computers. The instant-messaging computer uses neither LVM2 nor syncUC.
Update, upgrade or migration will be performed according to the instructions in
Chapter 15, Updating, Upgrading and Migrating at a later date.
The information in the following sections also applies for a virtual computer
created with Virtual Appliance:
Section 3.1.1, Requirements on the Host Hardware, on page 35
Section 3.1.2, Overview of the VM Configuration Parameters, on page 35
Section 3.1.3, VMware Features and OpenScape UC Application, on page

37
Section 3.1.4, Restriction of the Product Application and Features, on page

40

Using the Virtual Appliance is divided into the following major steps that are
described in detail in the sections below:
Manual Steps
1. Creating the vApp.iso file
This ISO file contains all information (IP addresses, computer names,
FQDNs, passwords, community names etc.) that is needed for the creation of
the application computer, the front-end computers, the media server
computers and the instant-messaging server computer.
2. Creating all virtual computers by using the four OVA files
3. Starting the application computer. For this step, the vApp.iso file must be
made available in the DVD drive of the application computer.
4. Starting the other computers
Automatic Actions
5. The other computers connect to the application computer and retrieve their
configuration provided by the vApp.iso file.
A31003-S5070-J100-12-7631, 02/2013
85
6. The other computers reconnect again to the application computer by using

the retrieved values.
7. The application computer reconfigures itself and restarts the OpenScape UC
Application.
8. The other computers reconfigure themselves in parallel by using the DAR file,
response files etc. and start the OpenScape UC Application services.
Creating the vApp.iso file
1. Collect the following data for the application computer. It is needed for
creating a vApp.iso.
Mandatory data
a) Password of the Symphonia administrator (compare step 7 on page 200
for the installation without Virtual Appliance).
IMPORTANT: This password must comply with the security policies,
which are defaulted as follows:
b) Password for user root of the operating system.
86
A31003-S5070-J100-12-7631, 02/2013
c) Community name for the OpenScape UC Application (compare step 8 on

page 200 for the installation without Virtual Appliance).
systems differ.
IMPORTANT: Verify that the Community names are identical on all

computers of an OpenScape UC Application system (application
computer and PBX computer).

Community String.
underscore "_" are permitted. The latter must not appear at the beginning
or end of the name. The corresponding regular expression reads as
follows:
[A-Za-z0-9][A-Za-z0-9_]*[A-Za-z0-9]
Example:
99_Red_Balloons
d) Password of the Solid database administrator (compare step 11 on page
201 for the installation without Virtual Appliance). Due to security
concerns it should not be the default password (dba).
e) Name for indicating the application computer of the OpenScape UC
without Virtual Appliance). You can leave the default value offboard
unchanged.
spaces.
f)
Fully qualified domain name of the application computer (compare step 9

g) IP address of the application computer (compare step 9 on page 201 for

A31003-S5070-J100-12-7631, 02/2013
87
h) Subnet mask of the application computer (compare step 82 on page 158

for the installation without Virtual Appliance)
88
i)
IP address of the default gateway for the application computer
j)
Time zone of the application computer
A31003-S5070-J100-12-7631, 02/2013
Use the values shown in the /usr/shared/zoneinfo directory or the Olson

IDs in the following table.
Time Zone
Olson ID
Offset to UTC
Honolulu
Pacific/Honolulu
UTC-10
Anchorage
America/Anchorage
UTC-9
US/Pacific
UTC-8
US/Mountain
UTC-7
US/Central
UTC-6
US/Eastern
UTC-5
Canada/Atlantic
UTC-4
Sao Paulo
America/Sao_Paulo
UTC-3
South Georgia
Azores
Atlantic/Azores
UTC-1
Reykjavik
Atlantic/Reykjavik
UTC
London
Europe/London
UTC
Lisbon
Europe/Lisbon
UTC
Berlin
Europe/Berlin
UTC+1
Madrid
Europe/Madrid
UTC+1
Paris
Europe/Paris
UTC+1
Rome
Europe/Rome
UTC+1
Cairo
Africa/Cairo
UTC+2
Johannesburg
Africa/Johannesburg
UTC+2
Moscow
Europe/Moscow
UTC+3
Tehran
Asia/Tehran
UTC+3:30
Yerevan (Armenia)
Asia/Yerevan
UTC+4
Calcutta
Asia/Calcutta
UTC+5:30
Dhaka
Asia/Dhaka
UTC+6
Ho Chi Minh
Asia/Saigon
UTC+7
Hong Kong
Asia/Hong_Kong
UTC+8
Shanghai
Asia/Shanghai
UTC+8
Taipei
Asia/Taipei
UTC+8
Tokyo
Asia/Tokyo
UTC+9
UTC+10
Salomon Islands
Pacific/Guadalcanal
UTC+11
Auckland
Pacific/Auckland
UTC+12
Table 4
A31003-S5070-J100-12-7631, 02/2013
89
k) IP address of the PBX computer

The IP address for the administrator access is needed, not the IP address
for e. g. SIP communication or MGCP communication.
l)
SRX user account name of the PBX computer, e. g. srx
m) Password for this SRX user account

Optional data
n) IP address of the DNS server computer
o) Search domain used by this first DNS server
p) IP address of the second DNS server computer
q) Search domain used by this second DNS server
r)
IP address of the NTP server computer

IMPORTANT: The system time of all OpenScape UC Application-related
computers must be synchronized with a maximum difference of one
second. The system time can also be synchronized retrospectively (see
s) First port number used on the NTP server

2. Collect the following data for each frontend computer. It is needed for creating
a vApp.iso.
Mandatory data
a) Display name of the frontend computer
Name for indicating the frontend computer of the OpenScape UC
spaces.
IMPORTANT: If you configure several frontend computers, enter an

individual name for each of them.
b) Fully qualified domain name of the frontend computer (compare step 26
90
A31003-S5070-J100-12-7631, 02/2013
c) IP address of the frontend computer (compare step 26 on page 210 for

d) Subnet mask of the frontend computer (compare step 82 on page 158 for
e) IP address of the default gateway for the frontend computer
f)
Time zone of the frontend computer

Use the values shown in the /usr/shared/zoneinfo directory or the
Olson ID (see Table 4 on page 89, Examples for Olson IDs of Time
Zones).
3. Collect the following data for each media server computer. It is needed for
creating a vApp.iso.
Mandatory data
a) Display name of the media server computer
Name for indicating the media server computer of the OpenScape UC
spaces.
b) FQDN of the media server computer
c) IP address of the media server computer
d) Subnet mask of the media server computer (compare step 82 on page
158 for the installation without Virtual Appliance)
e) IP address of the default gateway for the media server computer
f)
Time zone of the media server computer

Zones).
g) SIP listen port, typically 5060

h) MGCP listen port, typically 2727
4. Collect the data for the instant-messaging server computer (Openfire) in an
analog way.
a) Fully qualified domain name of the instant-messaging computer
b) IP address of the instant-messaging computer
A31003-S5070-J100-12-7631, 02/2013
91
c) Subnet mask of the instant-messaging computer

d) IP address of the default gateway for the instant-messaging computer
e) Time zone for the instant-messaging computer
Zones).
5. Use the CDC tool to create the vApp.iso file.
This tool is an XLS file that can be downloaded from the Software Supply
Server (SWS) by using an account that has a BASIC role or higher.
IMPORTANT: A role with higher privileges (ADVANCED or EXPERT) is not
needed for this step but it might be needed for downloading the OVA files
depending on the project status (see step 6 on page 94). The role your
account has is shown at the top of the web page when you are logged in to
the SWS.
Please obtain information about using the CDC tool from e. g. the following
sections of the OpenScape Voice V7, Design and Planning Manual:
Customer Data Collection guide:
Standard Solution Configuration
OpenScape Virtual Appliance
Installation Common Configuration Data File (vApp)
Virtual Appliance Worksheet
92
A31003-S5070-J100-12-7631, 02/2013
Using the OVA file

Step 6 on page 94 to step 26 on page 101 describe how to create a virtual
computer by using the appropriate OVA file. Then the other computers are
created.
IMPORTANT: If the virtual computers reside on different VMware ESXi hosts,
ensure that the ESXi hosts time is synchronized. See the VMware documentation for details. Otherwise, the Virtual Appliance configuration will fail due to
SSL failures.
A31003-S5070-J100-12-7631, 02/2013
93
6. Execute the following sub-steps to download the four OVA files from the
Software Supply Server (SWS):
a) Login to the SWS.
the top of the web page when you are logged in to the SWS. Depending
on the project status, the BASIC role might not be sufficient for
downloading the OVA files. You might need the ADVANCED role or
EXPERT role.
b) Search for the product version <version> CMP vApps.
Example:
c) Download the OVA files.

An OVA (Open Virtual Archive) file is a TAR file with OVF files inside. OVF
(Open Virtualization Format) is an open standard to pack and distribute
Virtual Appliances for virtual computers.
Please note that FAT32-formatted USB sticks have a maximum size of
10 GB.
7. Open File > Deploy OVF Template... in VMware vCenter Management Tool.
94
A31003-S5070-J100-12-7631, 02/2013
8. Enter the path to the OVA file you want to use in the Deploy from a file or
URL field.
9. Click on Next.
A31003-S5070-J100-12-7631, 02/2013
95
10. Click on Next.
11. Click on Accept.

12. Click on Next.
96
A31003-S5070-J100-12-7631, 02/2013
13. Enter the name of the virtual computer to be indicated in VMware in the Name
field and select the inventory location.
14. Click on Next.
15. Select the cluster the virtual computer is to operate on.
A31003-S5070-J100-12-7631, 02/2013
97
16. Click on Next.
17. Select the host the virtual computer is to operate on.

18. Click on Next.
98
A31003-S5070-J100-12-7631, 02/2013
19. Activate the Thick provisioning format check box (compare with step 10 on
page 52 of the installation of a virtual computer without Virtual Appliance).
- There are no snapshots.
considerable disk space by activating Thin provisioned format. This means
that the virtual harddisk grows with the actually required memory. This option
is supported for all virtual computers of OpenScape UC Application, but we
do not recommend it for the application and media server computer in
productive systems.
20. Click on Next.
A31003-S5070-J100-12-7631, 02/2013
99
21. Select the network to be used.

22. Click on Next.

IMPORTANT: This process might produce too much network load and a
timeout error. In this case, try this process again at a time with generally low
network load.
24. Make a snapshot of the virtual computer. Thus, you do not need to recreate
the virtual computer, if the next steps are not executed successfully. The
snapshot can be removed, when the entire installation of all virtual computers
will have been done successfully.
25. A new virtual computer is displayed in the inventory of the VMware vCenter
Management tool.
Click the right mouse button on the computer name in the inventory of the
VMware vCenter Management tool and open Edit settings... > Resources.
Check whether the values are set according to the Table 2 on page 36 and
the OpenScape UC Application Planning Guide.
NOTE: If you click the right mouse button on the computer name in the
inventory of the VMware vCenter Management tool and open Edit
settings... > Resources > CPU > Shares, the value Custom is shown
instead of the value according to the CPU shares column of the Table 2 on
100
A31003-S5070-J100-12-7631, 02/2013
page 36. This is correct. There is no need to change it.

26. IMPORTANT: Since Virtual Appliance for the Large Deployment uses
VMware ESXi V5, E1000 has been chosen as network board type. A network
board of type E1000 is less efficient than a network board of type VMXNET3,
but do not change the board type from E1000 to VMXNET3, as long as
VMware ESXi V5 loses UDP packages smaller than or equal to 40 byte for
network boards of type VMXNET3.
See the following URL for details about losing UDP packages:
ogID=325576986&stateId=1%200%20325582624
27. Repeat step 6 on page 94 to step 26 on page 101 for each frontend computer,
each media server computer and the instant-messaging server computer.
NOTE: Instead of creating a second, third or fourth front-end computer or a
second, third or fourth media server computer by using the OVA file, you may
choose to clone the first front-end computer or the first media server
computer by using the clone feature of the VMware vCenter Management
tool. Click the right mouse button on the computer name in the VMware
vCenter Management tool and select Clone.
A31003-S5070-J100-12-7631, 02/2013
101
Starting
28. Provide the vApp.iso file you created in step 5 on page 92 to the application
computer as usual under Edit Settings... > Hardware > CD/DVD Drive in
the Datastore ISO file field.
In doing so make sure that the Connect at power on check box is active in
the Device Status section.
29. Click the application computer in the inventory with the right mouse button
and select Open Console.
30. Start the application computer. The reconfiguration of this computer starts
automatically.
You have the following example output:
Example:
...
search for IP....
check if ip 192.168.55.250 is already in use
found ip: 192.168.55.250
OSConfigurator will use the following IP(s):
Local IP :192.168.55.250
Press ENTER to modify the values or wait 20 seconds to
proceed
After pressing ENTER yast will be called. Please modify your
networksettings and return.
The application computer now has the IP address 192.168.55.250. Wait more
than 20 seconds and continue with step 31 on page 103.
If you do not want to accept these values, e. g. because the virtual computers
are not all installed on the same VMware ESXi host, press the <Enter> key
within 20 seconds. The YaST Network Card Setup dialog opens.
102
A31003-S5070-J100-12-7631, 02/2013
Enter the IP address, subnet mask, default gateway etc.of the application
computer and save the changes.
IMPORTANT: Do not change the host name!
31. Click the frontend computers, the media server computers and the instantmessaging server computer in the inventory with the right mouse button and
select Open Console.
32. Start the frontend computers, the media server computers and the instantmessaging server computer.
NOTE: The VMware Tools are not installed and UEFI is deactivated by
default.
See Section 3.1.8, Installing the VMware Tools, on page 62 to install the
VMware Tools.
NOTE: The actions described below are done automatically. No manual

interaction is needed.
A31003-S5070-J100-12-7631, 02/2013
103
They get their IP addresses by ARP requests. They connect to the application
computer and retrieve their IP addresses, subnet masks etc. that have been
provided by the vApp.iso file. They reconnect to the application computer
with the new values. You can follow these actions on the VMware console of
the application computer.
NOTE: You cannot determine which computer gets which configuration data
provided by the vApp.iso file. This assignment is done automatically.
You have the following example output:
Example:
...
search for IP....
check if ip 192.168.55.250 is already in use
found ip: 192.168.55.250
Local IP :192.168.55.250
Backend IP:192.168.55.200
Press ENTER to modify the values or wait 20 seconds to
proceed
After pressing ENTER yast will be called. Please modify your
networksettings and return.
Wait more than 20 seconds. Continue with step 33 on page 105.
If you do not want to accept these values, e. g. because the virtual computers
are not all installed on the same VMware ESXi host, press the <Enter> key
within 20 seconds. The YaST Network Card Setup dialog opens.
104
A31003-S5070-J100-12-7631, 02/2013
Enter the IP address, subnet mask, default gateway etc. of the local computer
and save the changes.
IMPORTANT: Do not change the host name!
You are asked to enter the IP address of the application computer:
Please insert the BackendIP
BACKEND:
Enter it.
Example output:
Local IP :192.168.61.201
Backend IP:192.168.61.200
Shutting down network interfaces:
...
Found Symphonia enviroment
configurationID: StandardDuplexLarge
configurationName: Media Server
Starting Configuration for Media Server
Connect to "backend.uc"....................................
Repeat this procedure for all frontend computers, all media server computers
and the instant-messaging computer and continue with step 33 on page 105.
33. The application computer reconfigures itself by using the values provided by
the vApp.iso file.
Example for the output in the command line of the frontend computer:
...
configurationName: Frontend Server
Starting Configuration for Frontend Server
Connect to "backend.uc"..................................
Waiting for Server ...
Got OS reconfiguiration
do OS Configuration
Save Configuration as /tmp/OSUC1165490947488272608.temp
Socket will be closed
Socket closed
ENDING
Okay, I am FE 1
Change Root Password ...external: Changing password for root.
external: Password changed.
external ERR: New Password: Bad password: too simple
external ERR: Reenter New Password:
done
Change IP and Subnetmask ...done
Setting Default Gateway(Route) ...done
Setting hostname ....
Done
setting DNS_StaticListdone
setting DNS_SearchListdone
A31003-S5070-J100-12-7631, 02/2013
105
rewrite DNS-Filesdone
Restarting Network ...
...
external:
eth0
IP address: 10.10.10.20/24
...
external: ..doneSetting up service (localfs) network . . .
. . . . . . ...done
...
Generate New SSH-Fingerprints
...
Generate New SSH-Fingerprints DONE
Connect to "backend.uc".......
Waiting for Server ...
Got UC reconfiguiration order
do UC Configuration
34. The OpenScape UC Application starts on the application computer.
Example for the output in the command line of the application computer being
connected to one frontend computer, one mediaserver computer and the
instant-messaging computer:
...
Starting Solid for SymphoniaFW ... Running in standalone mode
configurationName: Backend Server
...
New connection from /10.10.10.30
Connection for CLIENT_MS established
...
CLIENT_MS 0 is done
CLIENT_MS 0:done sucessfully
CLIENT_FE 0:ongoing
CLIENT_OF 0:ongoing
Connection for CLIENT_OF established
...
CLIENT_OF 0 is done
CLIENT_FE 0:ongoing
CLIENT_OF 0:done sucessfully
Connection for CLIENT_FE established
...
CLIENT_FE 0 is done
CLIENT_FE 0:done sucessfully
CLIENT_OF 0:done sucessfully
...
106
A31003-S5070-J100-12-7631, 02/2013
external: [dbinstaller] INFO - using dbms.host: OSCBE.TestDomain.com
external: [executeAllInstallPluginAction] DEBUG - ExecuteAllInstallPluginAction:

Executing 'reconfigure' on /opt/siemens/servicetools/install/plugins/activemqplugin/
symphonia-activemqplugin-installplugin-current.jar
external: [executeAllInstallPluginAction] DEBUG - Reading properties from file /opt/
siemens/servicetools/install/conf/responsefile.txt
external: [executeAllInstallPluginAction] DEBUG - Reading properties from file /opt/
siemens/servicetools/install/conf/installsource.txt
external: [executeAllInstallPluginAction] DEBUG - Start adding System Properties
external: [executeAllInstallPluginAction] DEBUG - --------------------------------------external: [executeAllInstallPluginAction] DEBUG - System property Value
external: [executeAllInstallPluginAction] DEBUG - --------------------------------------external: [executeAllInstallPluginAction]
external: [executeAllInstallPluginAction]
...
OSCBE.TestDomain.com:4710
common/conf/.configured
siemens/common/conf/.reconfig_needed
DEBUG - CONFIG_NODETEMPLATE_NAME Backend Server

DEBUG - CONFIG_SCENARIO_ID StandardDuplexLarge
external:
external:
external:
external:
external:
external:
external:
external:
external:
external:
external:
external:
external:
DEBUG
DEBUG
DEBUG
DEBUG
DEBUG
DEBUG
DEBUG
DEBUG
DEBUG
DEBUG
DEBUG
DEBUG
DEBUG
[executeAllInstallPluginAction]
OSCBE.TestDomain.com
***
LiH63ae0raDsxdXN7MFOYDIx+MVcdLK+G+Ng0fBM
tools/install
...
DEBUG - PRIMARY.NODE.SVC.URI js-soc-ssl://

DEBUG - RESPONSEFILE.IS.READ true
DEBUG - RESPONSEFILE_VERSION 4
DEBUG - SFW_MARKERFILE_CONFIGURED /opt/siemens/
DEBUG - SFW_MARKERFILE_RECONFIG_NEEDED /opt/
SI_COMMUNITY_NAME NewCommunityName
SI_DB_HOST OSCBE.TestDomain.com
SI_DB_INSTALL_DIR /opt/siemens/solid
SI_DB_LOGON_NAME dba
SI_DB_LOGON_PASSWORD oeBZwwuObPc=
SI_DB_PORT 16760
SI_DB_SELECTION Solid
SI_FW_DB_MIGRATION false
SI_IS_HP8K 0
SI_IS_INSTALLED_VIA_IMAGING 1
SI_LOCAL_HOST OSCBE.TestDomain.com
SI_LOCAL_NAME offboardVM
SI_LOCAL_TYPE BACKEND
DEBUG - SI_MULTICAST false

DEBUG - SI_PRIMARY_NODE true
DEBUG - SI_PRIMARY_NODE_HOST
DEBUG - SI_SSL_ORGANIZATION *** not set ***
DEBUG - SI_SSL_ORGANIZATION_UNIT *** not set
DEBUG - SI_SYMPHONIA_ADMIN_NAME administrator
DEBUG - SI_SYMPHONIA_ADMIN_PASSWORD
DEBUG - SYMPHONIA_FW /opt/siemens/common
DEBUG - SYMPHONIA_HOME /opt/siemens
DEBUG - SYMPHONIA_INSTALL opt/siemens/service-
A31003-S5070-J100-12-7631, 02/2013
107
If you see the ouput Waiting for Clients to be done... in the

command line of the application computer, the reconfiguration of the
application computer has been finished and the frontend computers, the
media server computers and the instant-messaging computer start their
reconfiguration.
...
external:
external: BUILD SUCCESSFUL
external: Total time: 1 minute 0 seconds
external: INFO - Shutting down logging and log4j subsystem
Waiting for Clients to be done....
...
35. The front-end computers, the media server computers and the instantmessaging server computer reconfigure themselves in parallel, i. e. they
retrieve the DAR file, their response files etc.
...
Save DAR-file in /tmp/OSUC7467293134363942178.temp
start reconfiguration....
...
external:
[echo] 2012.11.09 : 11:25:09 CET :: BEGIN customize firstInstall: using
response.file: /tmp/OSConfigurator6754862592748472638OSI
external:
[echo] content of given responsefile: /tmp/
OSConfigurator6754862592748472638OSI
external:
[echo] ===================================================
external:
[echo] #
external:
[echo] # Siemens OpenSOA Response File - knut.responsefile.txt
external:
[echo] # for OpenScapeUC StandardDuplexLarge - Frontend node
external:
[echo] #
external:
[echo]
external:
[echo] #################################################################
external:
[echo] #################################################################
external:
[echo] # please adjust the first section only
external:
[echo] # please replace the <PLACEHOLDER_*> values.
external:
[echo] # please use the same value for all occurences of
<PLACEHOLDER_fqdn>.
external:
[echo]
external:
[echo] # Administrator logon password
external:
[echo] # please respect the password policy rules (...)
external:
[echo] SI_SYMPHONIA_ADMIN_PASSWORD=MyPassword.
external:
[echo]
external:
[echo] # Unique Identifier of the system, must have the same value for
all nodes
external:
[echo] # charset [A-Za-z0-9_], the '_' not at the front or the end
external:
[echo] SI_COMMUNITY_NAME=NewCommunityName
...
108
A31003-S5070-J100-12-7631, 02/2013
36. The OpenScape UC Application services on the front-end computers, the

media server computers and the instant-messaging server computer start.
Wai...
external:
[echo] 2012.11.09 : 11:26:14 CET :: BEGIN run action: 'reconfigure' for
install plugins ...
external: [executeAllInstallPluginAction] INFO - Processing action(s) "reconfigure" for
ll install plugin in directory "/opt/siemens/servicetools/install/plugins"
external: [executeAllInstallPluginAction] DEBUG - Getting parameter files
external: [executeAllInstallPluginAction] DEBUG - + /opt/siemens/servicetools/install/
conf/responsefile.txt
...
external: [executeAllInstallPluginAction] DEBUG - CONFIG_NODETEMPLATE_NAME Frontend
Server
...
OSCBE.TestDomain.com:4710
siemens/common/conf/.configured
siemens/common/conf/.reconfig_needed
OSUCFE1FQDN.TestDomain.com
OSCBE.TestDomain.com
Ge595kuksLhnCN/OVQk4rVbAWSF1oJObL2hqemvM
servicetools/install
...
DEBUG - CONFIG_SCENARIO_ID StandardDuplexLarge

DEBUG - PRIMARY.NODE.SVC.URI js-soc-ssl://
DEBUG - RESPONSEFILE.IS.READ true
DEBUG - RESPONSEFILE_VERSION 4
DEBUG - SFW_MARKERFILE_CONFIGURED /opt/
DEBUG - SFW_MARKERFILE_RECONFIG_NEEDED /opt/
DEBUG
DEBUG
DEBUG
DEBUG
DEBUG
DEBUG
DEBUG
DEBUG
DEBUG
SI_COMMUNITY_NAME NewCommunityName
SI_DB_HOST OSCBE.TestDomain.com
SI_DB_LOGON_NAME dba
SI_DB_LOGON_PASSWORD oeBZwwuObPc=
SI_DB_PORT 16760
SI_DB_SELECTION Solid
SI_IS_HP8K 0
SI_IS_INSTALLED_VIA_IMAGING 1
SI_LOCAL_HOST
DEBUG
DEBUG
DEBUG
DEBUG
DEBUG
SI_LOCAL_NAME frontend1
SI_LOCAL_TYPE FRONTEND
SI_MULTICAST false
SI_PRIMARY_NODE false
SI_PRIMARY_NODE_HOST
DEBUG - SI_SYMPHONIA_ADMIN_NAME administrator

DEBUG - SI_SYMPHONIA_ADMIN_PASSWORD
DEBUG - SYMPHONIA_FW /opt/siemens/common
DEBUG - SYMPHONIA_HOME /opt/siemens
DEBUG - SYMPHONIA_INSTALL /opt/siemens/
A31003-S5070-J100-12-7631, 02/2013
109
Waiting for server to close the connection...

Server closed the connection
Socket will be closed
ENDING
starting symphonia
Starting OpenSOA Framework..done
removing myself...
OSConfiguratorUC
0:off 1:off 2:off
OSConfiguratorUC
0:off 1:off 2:off
symphoniad
0:off 1:off 2:off
symphoniad
0:off 1:off 2:off
Starting system in 5 Seconds....
...
3:off
3:off
3:on
3:on
4:off
4:off
4:off
4:off
5:off
5:off
5:on
5:on
6:off
6:off
6:off
6:off
37. You must relogin to the frontend computers, t he media server computers and
the instant-messaging computer after they have reconfigured themselves.
38. The reconfiguration status of the frontend computers, the media server
computers and the instant-messaging computer is shown in the command
line of the application computer as well.
a) The instant-messaging computer has been reconfigured:
...
CLIENT_OF
CLIENT_MS
CLIENT_FE
CLIENT_OF
0 is done
0 :
ongoing
0:
ongoing
0:
done sucessfully
b) The frontend computer has been reconfigured:
CLIENT_FE
CLIENT_MS
CLIENT_FE
CLIENT_OF
0 is done
0:
ongoing
0:
done sucessfully
0:
done sucessfully
c) The media server computer has been reconfigured:
CLIENT_MS
CLIENT_MS
CLIENT_FE
CLIENT_OF
...
0 is done
0:
done sucessfully
0:
done sucessfully
0:
done sucessfully
39. Only the English language is installed for different purposes on the media
server computers. See step 10 on page 299 for purposes of the English
language indicated by the text uc-tts, uc-asr, announ or languagepack
in the names of the corresponding RPM package names.
NOTE: The actions described below must be done manually.
110
A31003-S5070-J100-12-7631, 02/2013
Backup
40. Save the vApp.iso and the OVA file on a medium that can be accessed
even if the application computer, the front-end computers, the media server
computers and the instant-messaging server computer are damaged beyond
repair.
Check
41. Follow the instructions in Section 5.4, Checking the Installation, on page
347 and heed the information in Section 5.5, Trouble Ticket, on page 358.
Configuration
42. VERY IMPORTANT: The firewalls on the application computer, the front-end
computers, the media server computers and the instant-messaging server
computer are deactivated and all ports are open. Consider the customers
requirements and the information provided in Chapter 6, Configuring the
OpenScape UC Application.
Further components
43. If required, continue with the chapters that follow Chapter 6.
A31003-S5070-J100-12-7631, 02/2013
111
3.2 Operating System Update Consequences

When installing SLES service packs or hotfixes, a new kernel can be set up on
the node. Since the VMware tools are configured for a specific kernel version,
their start will fail after a new kernel has been installed.
This is reported in the console as follows:
Failed services in runlevel 3: vmware-tools
NOTE: If the kernel was updated or upgraded, the VMXNET 3 network adapter
does not work anymore. Accessing the VM via the SSH protocol is therefore not
possible. You need to log on to the VM via the console of the VMware vSphere
client. Select the VM in the inventory and select in the menu Inventory > Virtual
Machine > Open Console for performing this.
The following command reconfigures the VMware tools and you can access the
network again:
/usr/bin/vmware-config-tools.pl
Guest operating system daemon: done
Unmounting HGFS shares: done
Guest filesystem driver: done
Guest memory manager: done
VM communication interface: done
The bld-2.6.16.60-0.54.5-x86_64smp-SLES10
loads perfectly into the running kernel.
The bld-2.6.16.60-0.54.5-x86_64smp-SLES10
The bld-2.6.16.60-0.54.5-x86_64smp-SLES10
The bld-2.6.16.60-0.54.5-x86_64smp-SLES10
The bld-2.6.16.60-0.54.5-x86_64smp-SLES10
The bld-2.6.16.60-0.54.5-x86_64smp-SLES10
The bld-2.6.16.60-0.54.5-x86_64smp-SLES10
The bld-2.6.16.60-0.54.5-x86_64smp-SLES10
- vmmemctl module
- vmmemctl module
- vmmemctl module
- vmmemctl module
- vmmemctl module
- vmmemctl module
- vmmemctl module
- vmmemctl module
Creating a new initrd boot image for the kernel.

Root device: /dev/sda2 (mounted on / as ext3)
Module list: vmxnet piix mptspi ide_generic processor thermal
fan jbd ext3 edd (xennet xenblk)
Kernel image: /boot/vmlinuz-2.6.16.60-0.62.1-smp
Kernel image: /boot/vmlinuz-2.6.16.60-0.62.1-smp
Shared libs:
lib64/ld-2.4.so
lib64/libacl.so.1.1.0
lib64/libattr.so.1.1.0
112
A31003-S5070-J100-12-7631, 02/2013
lib64/libblkid.so.1.0
lib64/libc-2.4.so
lib64/libcom_err.so.2.1
lib64/libdl-2.4.so
lib64/libext2fs.so.2.4
lib64/libhistory.so.5.1
lib64/libncurses.so.5.5
lib64/libpthread-2.4.so
lib64/libreadline.so.5.1
lib64/librt-2.4.so
lib64/libuuid.so.1.2
lib64/libnss_files-2.4.so
lib64/libnss_files.so.2
lib64/libgcc_s.so.1
Driver modules: ide-core ide-disk scsi_mod sd_mod vmxnet piix
scsi_transport_spi mptbase mptscsih mptspi ide-generic processor
thermal fan edd libata ahci ata_piix
Filesystem modules: jbd ext3
Including: initramfs fsck.ext3
Bootsplash: SuSE-SLES (800x600)
16873 blocks
No X install found.
File /etc/udev/rules.d/99-vmware-scsi-udev.rules is backed up to
/etc/udev/rules.d/99-vmware-scsi-udev.rules.old.0.
The file /etc/udev/rules.d/99-vmware-scsi-udev.rules that this
program was about to install already exists. Overwrite? [yes]
Checking acpi hot plug done
Switching to guest configuration: done
Paravirtual SCSI module: done
Guest memory manager: done
Guest operating system daemon: done
The configuration of VMware Tools 4.0.0 build-208167 for Linux
for this running kernel completed successfully.
You must restart your X session before any mouse or graphics
changes take effect.
You can now run VMware Tools by invoking the following command:
"/usr/bin/vmware-toolbox" during an X server session.
To enable advanced X features (e.g., guest resolution fit, drag
and drop, and file and text copy/paste), you will need to do one
(or more) of the following:
1. Manually start /usr/bin/vmware-user
2. Log out and log back into your desktop session; and,
3. Restart your X session.
Enjoy,
--the VMware team
A31003-S5070-J100-12-7631, 02/2013
113
114
A31003-S5070-J100-12-7631, 02/2013
IG_PrepComputers.fm
Installing and Configuring the Computer and Operating System
4 Installing and Configuring the Computer and Operating

System
IMPORTANT: For information and diagrams about the various OpenScape UC
Application deployment scenarios and system requirements, refer to the
OpenScape UC Application, Planning Guide.
This chapter describes the requirements to be met for the following computers:
Application computer
Media server computer (if any)
Frontend computer (if any)
NOTE: Please note that special requirements might apply for the media server
computers, e g. SSE2.x (Streaming SIMD Extension) support. For details see the
IMPORTANT: The media server supports IPv4 as well as IPv6. If you use TTS
or ASR, the media server must be available under an IPv4 address and at least
one IPv4 streaming route must have been configured in the media server. You
can obtain details from the administrator documentation OpenScape UC Application Configuration and Administration.
A31003-S5070-J100-12-7631, 02/2013
115
IG_PrepComputers.fm
File System and Operating System
4.1 File System and Operating System

Please heed the following points for the installation of the file system and the
operating system:
1. IMPORTANT: SuSE Linux Enterprise Server (SLES) 11 SP1 or SP2 in 64-bit
version must be installed on the application computer before you start setting
up the OpenScape UC Application (see Section 4.2, SLES Installation, on
page 119). SLES 11 SP2 is recommended.
NOTE: SLES 11 SP0 is not supported. Possibly existing versions of SLES
that are younger than SLES 11 SP2 are not supported either.
If frontend and media server computers exist, the same operating system
version must be installed on this computer as on the application computer.
If you wish to upgrade an older SLES version to SLES 11 SP1 or SP2,
execute the following sub-steps:
a) Execute the steps 1 on page 119 to 4 on page 121.
b) Activate the Update radio button.
c) Click on Next >.
d) Execute the further update steps.
IMPORTANT: If you execute command syncUC sync any time after setting
up the OpenScape UC Application and update or upgrade SLES at a later
date, you need to execute syncUC sync thereafter once more. While you
execute this command, the OpenScape UC Application is unavailable.
If you do not execute command syncUC sync once more, a possible
fallback of the OpenScape UC Application (command syncUC fallback)
may fail, because different SLES module paths and SLES kernel versions
may be stored on the active and passive partition.
2. IMPORTANT: The file system to be used on the application computer is ext3
on LVM2 (Logical Volume Manager 2). Only LVM2 enables backing up the file
system and compatibility with features such as fallback using syncUC and
automatic update using the CMP. The entire system should be configured
116
A31003-S5070-J100-12-7631, 02/2013
IG_PrepComputers.fm
to have only one partition, the root partition (/). The script that backs up data
secures only the root partition. All other partitions installed beside the root
partition (for example /opt) are not backed up.
IMPORTANT: syncUC is not supported if UUIDs (Universally Unique
Identifier) are used in the /etc/fstab file.
Section 4.2.2, Partitioning, on page 123 describes the creation of the
necessary partitions including the use of LVM2.
A31003-S5070-J100-12-7631, 02/2013
117
IG_PrepComputers.fm
3. Partition sizes
Table 5 on page 118 indicates the hard disk's minimum size and, depending
on this, the partitions' size. This table is valid for the application computer and
possibly available frontend and media server computers.
Partition
Partition
type
Name in the Partition size in GB

Documentation
example1
Calculation
Number
2
N3
300
Planning Guide
Section 4.2.2.1, Creating the /

boot Partition
Primary
Section 4.2.2.2, Creating the

swap Partition
Primary
N-4
296

LVM2 partition
Logical
volume
group
OpenScape
UC

Logical Volume Group
OpenScape UC
Root partition (/) in the

Logical
LVM2 memory for active
operation of the OpenScape
UC Application
UC1
(N-4)/3
98,7

Logical Volume UC1
Partition for fallback by

means of syncUC
Logical
UC2
(N-4)/3
98,7

Logical Volume UC2
Partition for file system

backup 4
Logical
0.9*(N-4)/3
88,8
Temporary snapshot 4
Logical
0.1*(N-4)/3
9,9
Hard disk capacity
Hard disk
/boot
Primary
Swap
LVM2 memory
Logical volume group
Table 5
1
2
3
4
Partition Sizes without using a USB Hard Disk for File System Backup
See Section 4.2, SLES Installation, on page 119.

For the minimum size of the 300 GB hard disk.
Hard disk size is defined as N.
This logical volume is created automatically when the file system is backed up for the first time. It need not be created manually.
NOTE: You can use other partition sizes for non-standard upgrades (see step 12
on page 845, step 11 on page 856, step 10 on page 868, step 10 on page 949
and step 10 on page 960).
118
A31003-S5070-J100-12-7631, 02/2013
IG_PrepComputers.fm
SLES Installation
4.2 SLES Installation

This section describes the SLES 11 installation inclusive creation of the required
partitions.
4.2.1 First Steps

1. Insert the SLES 11 DVD in the DVD drive and reboot the computer.
IMPORTANT: If the screenshot of step 2 on page 120 is displayed instead of

the one shown here, the boot sequence in the BIOS is set incorrectly. This
occurs in particular with IBM x3550 and IBM x3250 computers, which use
UEFI (Unified Extensible Firmware Interface) instead of the BIOS by default.
In this case, follow the instructions in Section 4.2.5, No support of UEFI
(Unified Extensible Firmware Interface), on page 162 before you execute
step 1 on page 119 once more and continue with step 2 on page 120.
A31003-S5070-J100-12-7631, 02/2013
119
IG_PrepComputers.fm
SLES Installation
2. Select Installation.
3. Activate the check box I Agree to the License Terms and click on Next.
120
A31003-S5070-J100-12-7631, 02/2013
IG_PrepComputers.fm
SLES Installation
4. Click on Next >.
5. Click on Next >.
6. If required, set the time and click on Next.
A31003-S5070-J100-12-7631, 02/2013
121
IG_PrepComputers.fm
SLES Installation
7. Click on Next >.
122
A31003-S5070-J100-12-7631, 02/2013
IG_PrepComputers.fm
SLES Installation
4.2.2 Partitioning
Two LVM2 logical volumes and one partition for backing up the file system are
required for performing a data backup and restore of the OpenScape UC
Application using syncUC. The logical volumes are not installed by default when
setting up SLES. Therefore, the following steps are necessary:
8. Click on Partitioning.
A31003-S5070-J100-12-7631, 02/2013
123
IG_PrepComputers.fm
SLES Installation
9. Leave the radio button Custom Partitioning (for experts) activated and click
on Next.
124
A31003-S5070-J100-12-7631, 02/2013
IG_PrepComputers.fm
SLES Installation
4.2.2.1 Creating the /boot Partition

10. Open linux > Hard Disks > sda in the navigator and click on Add.
11. Keep the setting Primary Partition and click on Next.
A31003-S5070-J100-12-7631, 02/2013
125
IG_PrepComputers.fm
SLES Installation
12. Enter the value for the Boot partition in the Size field according to Table 5 on
page 118 and click on Next.
13. Leave the File system field set to value Ext3.

14. Select value /boot in the Mount Point field.
126
A31003-S5070-J100-12-7631, 02/2013
IG_PrepComputers.fm
SLES Installation
4.2.2.2 Creating the swap Partition

16. Click on Add.
A31003-S5070-J100-12-7631, 02/2013
127
IG_PrepComputers.fm
SLES Installation
18. Enter the value for the Swap partition in the Size field according to Table 5 on
19. Set the File system field to value Swap.

The value in the Mount Point field changes automatically to value swap.
128
A31003-S5070-J100-12-7631, 02/2013
IG_PrepComputers.fm
SLES Installation
4.2.2.3 Creating the LVM2 partition

21. Click on Add.
23. Enter the value for the LVM2 memory in the Size field according to Table 5 on
A31003-S5070-J100-12-7631, 02/2013
129
IG_PrepComputers.fm
SLES Installation

25. Activate the Do not mount partition radio button.
130
A31003-S5070-J100-12-7631, 02/2013
IG_PrepComputers.fm
SLES Installation
4.2.2.4 Creating the Logical Volume Group OpenScape UC

27. Open linux > Volume Management in the navigator.
28. Click on Add... > Volume Group.

29. Enter the group's name in the Volume Group Name field, for example
OpenScapeUC.
30. Select the entry in the Available Physical Volumes section and click on
Add.
A31003-S5070-J100-12-7631, 02/2013
131
IG_PrepComputers.fm
SLES Installation
132
A31003-S5070-J100-12-7631, 02/2013
IG_PrepComputers.fm
SLES Installation
4.2.2.5 Creating the Logical Volume UC1

32. Open linux > Volume Manager > OpenScapeUC in the navigator.
33. Click on Add....
A31003-S5070-J100-12-7631, 02/2013
133
IG_PrepComputers.fm
SLES Installation
34. Enter the volume's name in the Logical Volume field, for example UC1 and
click on Next.
35. Activate the Manual Size radio button.
36. Enter the size of the UC partition 1 in the Manual Size field according to Table
5 on page 118 and click on Next.

38. Leave the Mount Point field set to value /.
134
A31003-S5070-J100-12-7631, 02/2013
IG_PrepComputers.fm
SLES Installation
A31003-S5070-J100-12-7631, 02/2013
135
IG_PrepComputers.fm
SLES Installation
4.2.2.6 Creating the Logical Volume UC2

click on Next.
136
A31003-S5070-J100-12-7631, 02/2013
IG_PrepComputers.fm
SLES Installation
43. Enter the size of the UC partition 2 in the Manual Size field according to Table
5 on page 118 and click on Next.

A31003-S5070-J100-12-7631, 02/2013
137
IG_PrepComputers.fm
SLES Installation
NOTE: When the SLES setup is complete, partition properties are displayed
under yast > System > Partitioner.
138
A31003-S5070-J100-12-7631, 02/2013
IG_PrepComputers.fm
SLES Installation
4.2.3 Selecting SLES Software Components
48. Click on Software.
A31003-S5070-J100-12-7631, 02/2013
139
IG_PrepComputers.fm
SLES Installation
49. Deactivate the following check boxes:

a) GNOME Desktop Environment for Server
b) KDE Desktop Environment for Server
c) X Window System
d) Print Server
Siemens Enterprise Communications GmbH & Co. KG recommends to
deactivate X-Server for saving resources and preventing negative influences
on the OpenScape UC Application performance. It is also a good idea to
deactivate desktop environments such as KDE or GNOME for minimizing
risks and saving system resources.
You can perform this deactivation also after an SLES setup by changing the
default runlevel to 3 using YaST (Yet another Setup Tool) or editing the /etc/
inittab file by opening it with the following command and the vi editor
vi /etc/inittab
Then look for the following line:
# The default runlevel is defined here
Change the ensuing line as follows:
id:3:initdefault:
Save the file and close the editor vi by entering :wq. This sets the default
runlevel to Full multiuser with network.
NOTE: If you need to run X-Server for local or remote administration, do not
use xhost admission control.
NOTE: X-Server is not required for starting e.g. IBM Lotus Domino Setup.
This may also occur by using SSH with X11 forwarding or Xauthority / xauth
to access the computer remotely.
50. Click on Details.
51. Click on the Search tab.
52. In this step, a check is performed as to whether necessary RPM packages
are installed on the computer.
The below list of necessary packages depends on one or several of the
following points:
140
OpenScape UC Application deployment scenario to be installed
A31003-S5070-J100-12-7631, 02/2013
IG_PrepComputers.fm
SLES Installation
Computer on which the installation is performed (application computer,

frontend computer or media server computer)
PBX to be connected (OpenScape Voice or HiPath)
Integrated Deployment, application computer
acl
apache2
agfa-fonts
dejavu
dump
expect
libgcc43-32bit1
libstdc++33-32bit
libstdc++43-32bit2
netcat
nfs-client3
nfs-kernel-server4
openssh
perl-XML-XPath
yast2-nfs-client3
yast2-nfs-server4
zip
1. If SLES 11 SP2 is used, libgcc46-32bit can be used instead.

2. If SLES 11 SP2 is used, libstdc++46-32bit can be used instead.
3. This RPM only is needed if you want to use provide ISO files or a repository in osc-setup via the
network and this computer should be the target computer for this action.
4. This RPM only is needed if you want to provide ISO files or a repository in osc-setup via the network and this computer should be the source computer for this action.
A31003-S5070-J100-12-7631, 02/2013
141
IG_PrepComputers.fm
SLES Installation
Small Deployment, application computer in case of connection to an

OpenScape Voice
acl
agfa-fonts
apache2
dejavu
dump
expect
libgcc43-32bit1
libqt4
libQtWebKit4
libstdc++33-32bit
libstdc++43-32bit2
netcat
net-snmp3
nfs-client4
nfs-kernel-server5
perl-XML-XPath
openssh
xorg-x11-server-extra
yast2-nfs-client4
yast2-nfs-server5
zip

3. This RPM only is needed, if a network management system on a separate computer wants to
receive information from both the SLES SNMP agent and the SNMP agent of the OpenScape
UC Application.
142
A31003-S5070-J100-12-7631, 02/2013
IG_PrepComputers.fm
SLES Installation
Small Deployment, application computer in case of connection to a

HiPath
acl
agfa-fonts
apache2
dejavu
dump
expect
libgcc43-32bit1
libqt4
libQtWebKit4
libstdc++33-32bit
libstdc++43-32bit2
netcat
net-snmp3
nfs-client4
nfs-kernel-server5
perl-XML-XPath
yast2-nfs-client4
yast2-nfs-server5
zip

UC Application.
A31003-S5070-J100-12-7631, 02/2013
143
IG_PrepComputers.fm
SLES Installation
Large Deployment and Very Large Deployment
acl
apache2
dump
expect
libstdc++33-32bit
netcat
net-snmp1
nfs-client2
nfs-kernel-server3
openssh
perl-XML-XPath
yast2-nfs-client2
yast2-nfs-server3
zip
Frontend computer
acl
dump
expect
libstdc++33-32bit
nfs-client2
perl-XML-XPath
yast2-nfs-client2
UC Application.
144
A31003-S5070-J100-12-7631, 02/2013
IG_PrepComputers.fm
SLES Installation
Media server computer
acl
agfa-fonts
dejavu
dump
expect
libgcc43-32bit1
libqt4
libQtWebKit4
libstdc++33-32bit
libstdc++43-32bit2
nfs-client3
perl-XML-XPath
yast2-nfs-client3

A31003-S5070-J100-12-7631, 02/2013
145
IG_PrepComputers.fm
SLES Installation
Description of the packages
acl
Command for manipulating POSIX access control lists
agfa-fonts
TrueType fonts that are needed for the menus of video conferences
apache2
This package is required only on the application computer for package
scs_httpd_config.
dejavu
This package must be installed on the computer where the media server
is installed in order to show cyrillic names of video conference
participants.
dump
Please obtain details about dump from Section 4.5, Configuring the File
System Backup, on page 181.
expect
This package is needed by the OpenScape Voice Assistant.
NOTE: This package needs to be installed on the application computer
only.
libgcc43-32bit (SLES 11 SP1 only)
libgcc43-32bit or libgcc46-32bit (SLES 11 SP2)

C compiler runtime library
libstdc++33-32bit and libstdc++43-32bit (SLES 11 SP1 only)
libstdc++33-32bit and libstdc++43-32bit or libstdc++46-32bit (SLES 11

SP2)
The standard C++ shared library
libqt4
Core components of the Qt-C++ program library
libQtWebKit4
Core components of the Qt-C++ program library
146
A31003-S5070-J100-12-7631, 02/2013
IG_PrepComputers.fm
SLES Installation
netcat
net-snmp
This RPM only is needed, if a network management system on a separate
computer should receive information from both the SLES SNMP agent
and the SNMP agent of the OpenScape UC Application.
This package contains the SNMP Daemon and also is required when you
use net-snmp commands such as snmpwalk for checking the
SharedServices-MIB on the application computer and thus the SSDP
functionality.
nfs-client
NFS client that is needed if a remote installation of the OpenScape UC
Application is done by using NFS
nfs-kernel-server
NFS server that is needed if a remote installation of the OpenScape UC
Application is done by using NFS
openssh
perl-XML-XPath
A set of modules for parsing and evaluating XPath statements.
This package contains additional X servers (Xdmx, Xephyr, Xnest and
Xvfb). The media server requires this package. This does not mean,
however, that the X server may be activated (see step 49 on page 140).
yast2-nfs-client and yast2-nfs-server

These libraries are needed for configuring the NFS client and NFS server
by using YaST. The NFS client and the NFS server only are needed, if a
remote installation of the OpenScape UC Application is done by using
NFS.
zip
A program for compressing files.
Optional packages
wireshark
The OpenScape UC Application does not require this package, but it can
be used for diagnosis purposes.
A31003-S5070-J100-12-7631, 02/2013
147
IG_PrepComputers.fm
SLES Installation
Example of a check for the RPM package acl:

Enter acl in the search field and click on Search.
NOTE: You can install the packages listed in this step also after setting up
the operating system using YaST > Software Management
(see Section B.6, yast instead of zypper in, on page 1073) or by zypper.
Example:
zypper in acl
Example of installing several packages by zypper simultaneously:
zypper in acl apache2 wireshark dump
You can use rpm to find out whether a package has been installed:
Example:
rpm -q apache2
Example output with installed program:
apache2-2.2.2.10-2.24.5
If something is put out that does not resemble the example output, then the
package is not installed.
Alternatively, you can use YaST for this purpose (see Section B.5, yast
instead of zypper se or rpm -q, on page 1060).
If entry acl in the field on the right hand side has not been activated with a
green tick, click on the corresponding check box to enable it. This may
automatically activate the check boxes of other packages also.
Check all other necessary packages analogously.
53. Java Business Delegates for Java 1.4.2 are no longer supported.
54. If you want to import data about users, passwords or contacts from an LDAP
directory into the OpenScape UC Application using SPML (Service
Provisioning Markup Language), JRE 1.5.x or higher or JDK 1.5.x or higher
must have been installed (see step 10 on page 267 and step 22 on page 280).
148
A31003-S5070-J100-12-7631, 02/2013
IG_PrepComputers.fm
SLES Installation
56. If required, click on the Continue button in the Changed Packages dialog.
57. Click on Install.
A31003-S5070-J100-12-7631, 02/2013
149
IG_PrepComputers.fm
SLES Installation
58. Click on Install.
59. After setting up the operating system select Boot from Hard Disk and push
the return key.
150
A31003-S5070-J100-12-7631, 02/2013
IG_PrepComputers.fm
SLES Installation
4.2.4 Network-related Properties

60. The following screen for configuring network-related properties is
automatically displayed:
61. Enter the password for user root, confirm it and select Next.
62. Enter the computer name in the Hostname field and the domain name in the
Domain Name field.
A31003-S5070-J100-12-7631, 02/2013
151
IG_PrepComputers.fm
SLES Installation
63. Deactivate the Change Hostname via DHCP check box for the network
board.
NOTE: This will prevent the media server from using the then generated
entry in /etc/hosts to generate a wrong IP address binding.
IMPORTANT: The system must be able to resolve the host name to a

permanent computer IP address with either DNS or a local /etc/hosts file .
64. Select Next.
65. Deactivate IPv6 (Internet Protocol Version 6).

66. Either deactivate the firewall or open the ports required by the OpenScape
UC Application (see Section 6.1, Lists of the Ports to be opened, on page
359).
IMPORTANT: Some devices like firewalls separate idle TCP connections
after a specific period without notice. Verify that no such device exists
between the frontend and application computer, because serious instabilities will otherwise occur during operation. This may become obvious by
e.g. the error message Service unavailable, temporarily impossible logins or
empty device lists.
Please note that these errors also occur when a firewall is set in a way that
transmissions via closed TCP connections are answered by sending RST
messages (Reset). Please also note that some firewalls separate idle sockets
152
A31003-S5070-J100-12-7631, 02/2013
IG_PrepComputers.fm
SLES Installation
without notice if they do not filter anything.

All devices must consequently allow unlimited timeouts for connections
between the frontend and application computer. Limited timeouts for inbound
client connections to fend off Denial-of-Service attacks from the internet or
intranet must still be possible, though.
NOTE: These port numbers are provided by the customer administrator or

representative. See Section 2.3, Information Provision by the Customer, on
page 30.
NOTE: If you wish to change firewall settings at a later date, execute

command yast firewall.
67. Select Next.
A31003-S5070-J100-12-7631, 02/2013
153
IG_PrepComputers.fm
SLES Installation
68. Activate the check box No, Skip This Test and select Next.
69. Verify that the CIM Server service is disabled and click on Next.
154
A31003-S5070-J100-12-7631, 02/2013
IG_PrepComputers.fm
SLES Installation
70. Select Next.
71. Enter a user name and its password. Confirm the password in the fourth field
and select Next.
A31003-S5070-J100-12-7631, 02/2013
155
IG_PrepComputers.fm
SLES Installation
72. Select Next.
73. Activate the Skip Configuration check box and select Next.
156
A31003-S5070-J100-12-7631, 02/2013
IG_PrepComputers.fm
SLES Installation
74. Select Finish.
75. When this dialog is displayed, select Continue.
76. Log in as user root with the password entered in step 61 on page 151.
77. Enter command yast.
A31003-S5070-J100-12-7631, 02/2013
157
IG_PrepComputers.fm
SLES Installation
78. Open Network Devices > Network Settings.
79. Enter <Alt> + i to configure the network board.
80. Enter <Alt> + t to activate the Statically assigned IP Address check box.
81. Enter the computer's IP address in the IP Address field.
82. Enter the subnet mask in the Subnet Mask field.
158
A31003-S5070-J100-12-7631, 02/2013
IG_PrepComputers.fm
SLES Installation
83. Select Next.

84. Enter <Alt> + s.
85. Enter <Alt> + t and edit the host name.

86. If required, enter <Alt> + d and edit the domain name.
87. If you use a DNS server, press the TAB key repeatedly until you reach the
Name Server 1 field in the Name Servers and Domain Search List section
and enter the IP address of the DNS server.
We recommend to connect the OpenScape server to a DNS server, for
example a Windows 200x domain controller on which this service operates.
You can then use fully qualified domain names of computers to identify
network components, for example the customer's Exchange server.
IMPORTANT: Ensure that each specified DNS server can be reached, so
that OpenScape UC Application can be executed correctly.
IMPORTANT: If you do not use any DNS servers and wish to install the Very
Large Deployment, you need to enter the fully qualified domain names of
computers in the /etc/hosts file on specific computers at a later date. See
Section 4.6, Using FQDNs for Very Large Deployment, on page 184 for
A31003-S5070-J100-12-7631, 02/2013
159
IG_PrepComputers.fm
SLES Installation
details.
NOTE: If you wish to change the host name or the DNS server at a later date,
execute command yast dns and the script changeSFWip.sh (see the
Administration for details).
88. If required, enter the IP addresses of further DNS servers in the Name Server
2 and Name Server 3 fields.
89. Select OK.
90. Select Quit.
91. Check whether the following conditions are met:
A network management system on a separate computer should receive

information from both the SLES SNMP agents and the SNMP agents of
the OpenScape UC Application.
You are on the application computer.
The net-snmp RPM had been installed on the application computer (see
You do not intend to install Integrated Deployment.
If all these conditions are met, execute the following sub-steps:

NOTE: These sub-steps can be executed at a later date. The only condition
is that net-snmp must be installed before. Even the OpenScape UC Application might be running.
a) Open the /etc/snmp/snmpd.conf file in an editor on the application
computer.
b) Search the following line:
rocommunity public 127.0.0.1
This line has been set by default. The default value only allows SNMP
requests with the SNMP community string public from the local system.
c) Replace this line by the following lines:
rocommunity public
proxy -v 2c -c public localhost:8167 .1.3.6.1.4.1.4329.2.45
160
A31003-S5070-J100-12-7631, 02/2013
IG_PrepComputers.fm
SLES Installation
This configures the port 8167 as the proxy port of the SLES SNMP agent.
This enables a network management system to receive SNMP messages
from both the SLES SNMP agent and the SNMP agent of the OpenScape
UC Application on port 161.
NOTE: Only V1 and V2 of SNMP are supported. Both versions are
covered by the command above.
d) Save the changes you made.
e) Start or restart the net-snmp daemon:
rcsnmpd restart
This command can be executed in any directory on the application
computer.
f)
There is no need to open port 8167 on the application computer in a

firewall (see Section 6.1, Lists of the Ports to be opened, on page 359).
92. IMPORTANT: Check if the system time of all OpenScape UC Applicationrelated computers is synchronized with a maximum difference of one second.
(NTP) is often used for synchronizing the system time (see Section 3.1.9.2,
Configuring the NTP Service, on page 66).
A31003-S5070-J100-12-7631, 02/2013
161
IG_PrepComputers.fm
SLES Installation
4.2.5 No support of UEFI (Unified Extensible

Firmware Interface)
IMPORTANT: UEFI is an alternative to the BIOS and supported by SLES 11.
If you use hardware that supports UEFI, you need to execute the following
example steps to set the Legacy Only flag at the top of the Boot Order list.
The BIOS is then used instead of UEFI.
IMPORTANT: These steps are examples. Depending on your hardware you

may have to execute other steps.
a) Reboot the computer and, while it is booting, push the F1 key to start the
setup utility.
b) Select Boot Manager.
c) Select Add Boot Option or Add WOL Boot Option.
d) Select Legacy Only.
e) Push the return key. The Legacy Only flag is set to the bottom of the Boot
Order list.
f)
Select Legacy Only and push the + key as often as it takes to position
Legacy Only at the top of the Boot Order list.
g) Push the return key.

h) Select Commit Changes.
162
i)
Push the return key.
j)
Leave the setup utility.
A31003-S5070-J100-12-7631, 02/2013
IG_PrepComputers.fm
Checking the Partitioning
4.3 Checking the Partitioning

After having concluded the SLES installation, you can always obtain information
on the partitions in a console by executing the commands vgdisplay, lvs, pvs
or df -T.
1. The vgdisplay command provides information on the volume group.
Example output:
--- Volume group --VG Name
System ID
Format
Metadata Areas
Metadata Sequence No
VG Access
VG Status
MAX LV
Cur LV
Open LV
Max PV
Cur PV
Act PV
VG Size
PE Size
Total PE
Alloc PE / Size
Free PE / Size
VG UUID
F1IE72
OpenScapeUC
lvm2
1
3
read/write
resizable
0
2
1
0
1
1
296.00 GB
4.00 MB
75776
71994 / 281.20 GB
3782 / 14.79 GB
Jcd6Ic-wINk-dbde-ToRK-GJSX-oD6r-
2. The lvs command provides the size of the logical partition.

Example output:
LV
UC1
UC2
VG
OpenScapeUC
OpenScapeUC
Attr
LSize Origin Snap%
-wi-ao 98.00G
-wi-a- 98.00G
Move Log Copy%
Convert
3. The pvs command provides the total size of a physical partition and the free
space on a partition.
Example output:
PV
/dev/sda3
VG
Fmt Attr PSize PFree
OpenScapeUC lvm2 a296.00G 14.79G
A31003-S5070-J100-12-7631, 02/2013
163
IG_PrepComputers.fm
Checking the Partitioning
4. The df -T command provides besides information on the space used on the

hard disk also the file system type.
164
A31003-S5070-J100-12-7631, 02/2013
IG_PrepComputers.fm
Configuring Multiple Network Interface Cards
4.4 Configuring Multiple Network Interface Cards

If the deployment scenario Small Deployment, Large Deployment or Very Large
Deployment shall be installed, OpenScape UC Application requires a higher
availability of the application computer network access. This is why two gigabit
Ethernet LAN network boards (NIC) are required.
NOTE: If you use several network boards, we recommend Linux Bonding.
4.4.1 With Bonding

NOTE: Bonding is also called NIC bonding, Channel bonding, Ethernet
bonding, Trunking , Link bundling or Link aggregation (LAG).
NOTE: This section does not only apply for the application computer but also for
possibly available frontend computers, media server computers, Mobile Client
Facade server computers and instant-messaging server computer (Openfire
server computer).
NOTE: There are no dependencies from specific PBX features or configurations.

If you equip the application computer with several real network boards (eth0,
eth1, ...), you can use Linux bonding for bundling these network boards to one
bonding network board (bond0). The application computer then appears to have
only this bonding network board and a single IP address in network. The bonding
network board is the master device, the real network boards are the slave
devices. The real network boards are also called eth-devices.
The entire data traffic is divided among the two real network boards. If one of the
real network boards fails, the remaining one takes care off the entire data traffic.
A31003-S5070-J100-12-7631, 02/2013
165
IG_PrepComputers.fm
The bonding network board and the real network boards all have the same MAC
address. If not otherwise configured, the bonding network board copies the MAC
address of the first slave device. This MAC address is then assigned to all other
slaves also and remains persistent even if the first slave device is removed. It
does not change until the bonding network board is disabled or reconfigured.
IMPORTANT: Verify that the real network board you bound a license to is the first
slave device. Only this way the network board keeps its MAC address upon
bonding and only then the CLA (Customer License Agent) accepts the license as
valid, because it is bound to the MAC address.
The bonding network board must carry the FDQN.
The bonding of two real network boards results e.g. in the following configuration:
# /sbin/ifconfig
bond0
Link encap:Ethernet HWaddr 00:C0:F0:1F:37:B4

inet addr:XXX.XXX.XXX.YYY Bcast:XXX.XXX.XXX.255 Mask:255.255.252.0
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:7224794 errors:0 dropped:0 overruns:0 frame:0
TX packets:3286647 errors:1 dropped:0 overruns:1 carrier:0
collisions:0 txqueuelen:0
eth0

UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
Interrupt:10 Base address:0x1080
eth1

UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
Interrupt:9 Base address:0x1400
166
A31003-S5070-J100-12-7631, 02/2013
IG_PrepComputers.fm
1. Open a command line as user root.
2. Execute the following command:
yast lan
NOTE: How you operate YaST in general is explained in Section B.1,

General Operation of YaST, on page 1044.
A31003-S5070-J100-12-7631, 02/2013
167
IG_PrepComputers.fm
3. Leave the Traditional Method with ifup radio button activated and select
Next.
4. Select a network board to be bonded. Select Edit.
168
A31003-S5070-J100-12-7631, 02/2013
IG_PrepComputers.fm
5. Activate the No IP Address (for Bonding Devices) radio button.
6. Select General.
A31003-S5070-J100-12-7631, 02/2013
169
IG_PrepComputers.fm
7. Move to the Device Activation field and push the button.
8. Select value Never.
170
A31003-S5070-J100-12-7631, 02/2013
IG_PrepComputers.fm
9. Select value Next.
10. Execute steps 4 to 9 for all further network boards to be bonded.
All network boards to be bonded are displayed in the list without IP address.
A31003-S5070-J100-12-7631, 02/2013
171
IG_PrepComputers.fm
11. Select Add.
172
A31003-S5070-J100-12-7631, 02/2013
IG_PrepComputers.fm
12. Move to the Device Type field and push the button.
13. Select Bond Network.
A31003-S5070-J100-12-7631, 02/2013
173
IG_PrepComputers.fm
14. Select Next.
15. Activate the Static Address Setup radio button.
174
A31003-S5070-J100-12-7631, 02/2013
IG_PrepComputers.fm
16. Enter the IP address of the bonding network board in the IP Address field.
The two existing network boards will be visible from the network only under
this one bonding IP address.
17. Check whether the subnet mask has the correct value.
A31003-S5070-J100-12-7631, 02/2013
175
IG_PrepComputers.fm
18. Move to the Bond Slaves field.
19. Push the key until you have selected a network board to be bonded and
push the Enter key to activate the check box of this network board.
176
A31003-S5070-J100-12-7631, 02/2013
IG_PrepComputers.fm
20. Execute step 19 for all other network boards to be bonded also.
21. Verify that value ...active-backup ... is selected in the Bond Driver Options
field.
A31003-S5070-J100-12-7631, 02/2013
177
IG_PrepComputers.fm
22. Select Next.
The bonding network board (bond0) is displayed with its IP address. The two
bonded network boards, however, appear without IP address.
178
A31003-S5070-J100-12-7631, 02/2013
IG_PrepComputers.fm
23. Select Finish.
A31003-S5070-J100-12-7631, 02/2013
179
IG_PrepComputers.fm
4.4.2 Without Bonding

NOTE: In the case of several LAN interfaces, for each of these interfaces there
has to be a different fully qualified domain name (FQDN).
Additionally, the following configuration rules must be checked carefully to avoid
installation and startup problems.
Display the output of uname -a, and ensure that the name displayed after Linux
in the output matches the host name entry for eth0 in /etc/hosts:
uname -a
Linux openscape-1 2.6.16.46-0.12-bigsmp #1 SMP Thu May 17
14:00:09 UTC 2007 i686 i686 i386 GNU/Linux
If the host name entry matches the host name entry for eth0 in /etc/hosts and
if the host name displayed by uname -a DOES NOT match the host name of the
eth0 IP address in /etc/hosts, start YaST > Network Devices > Network
Card > Network Manager > Network Card Configuration Overview > Edit >
Hostname and Name Server to adjust the host name to the host name entry for
eth0.
Restart the server:
shutdown -r now
NOTE: After copying the checkResponsefileOnLocalNode.sh script (see
e. g. step 3 on page 199), it will be possible to check the computer name binding
to the first network interface card (see e. g. step 13 on page 201).
180
A31003-S5070-J100-12-7631, 02/2013
IG_PrepComputers.fm
4.5 Configuring the File System Backup

NOTE: File system backup and syncUC are compatible.
The CMP provides a mechanism to back up the file system when the Dump RPM
is installed.
Execute the following steps for Small Deployment, Large Deployment and Very
Large Deployment to enable user sym to execute the files
lvBackupManagementUtility.sh and fsBackup.sh at a later date (NOT
NOW!) with root privileges. lvBackupManagementUtility.sh is a tool for
performing backups on an LVM2-based operating system or LVM2-based file
system. If the file system has not been configured with LVM2,
lvBackupManagentUtility.sh is ended with exit code 2 without an error
message being issued.
1. Log on to the application computer as root.
2. When the file system will be backed up and data restored at a later date (NOT
NOW!), the entire contents of the directory used for the file system backup will
be deleted. This is done independently from whether or not the files and
directories contained in this directory were already available before the file
system backup.
If an external USB hard disk is used for the file system backup (see for
example Table 127 on page 846, Partition Sizes when using a USB Hard
Disk for File System Backup), execute the following sub-steps to prevent that
the entire partition on the USB hard disk is mounted as backup medium:
a) List all sd devices:
ls /dev/sd*
Example output:
/dev/sda /dev/sda1 /dev/sda2 /dev/sda3
b) Connect the USB hard disk to the computer.
c) List all sd devices once again:
ls /dev/sd*
Example output:
/dev/sda /dev/sda1 /dev/sda2 /dev/sda3 /dev/sdf /dev/sdf1
The connected USB hard disk makes the difference between the two
outputs. In this example it is a USB hard disk (sdf) with one partition
(sdf1). If the USB hard disk had several partitions, sdf2, sdf3 etc. would
also be put out.
A31003-S5070-J100-12-7631, 02/2013
181
IG_PrepComputers.fm
You can also use the fdisk -l command. If a device is connected to the
USB interface, the line /dev/sdxx of this command's output shows the
connected USB device.
d) If the /media directory does not exist yet, create it:
mkdir /media
e) Mount the USB hard disk:
Example:
mount /dev/sdf1 /media
f)
If the /mnt directory does not exist yet, create it:

mkdir /media/backups
g) Mount the Repository ISO file on the USB hard disk:

mount --bind /media/backups /backups
3. Execute the following command in a command line:
cat /etc/sudoers
4. Look for the entries described in the administrator documentation
OpenScape Common Management Platform Administration in section How
to Back up manually the File System for Standard Duplex on a LVM-based
deployment. under Prerequisites.
If these entries are not available, create them. Do not use Microsoft Windows
Editor for this purpose. Proceed on SLES as follows:
a) Verify that you are logged in at a console as root.
b) Execute the following command:
visudo -f /etc/sudoers
The file opens in the vi.
c) Perform the modifications and save the file.
5. Check whether the Dump RPM is installed on the application computer by
executing the following command:
rpm -qa |grep dump
6. Search the command output for the following package:
dump-<version_number>
Example output:
dump-0.4b41-14.2
7. If the dump-RPM has not been installed, set it up by executing the following
command:
yast -i dump
182
A31003-S5070-J100-12-7631, 02/2013
IG_PrepComputers.fm
To this you need the SLES installation source (DVD or installation source in
the network).
If Large Deployment or Very Large Deployment is available, you need to execute
the following steps also:
IMPORTANT: If you do not execute these steps, restoring will fail.
8. Log on to all frontend computers as root and execute steps 3 on page 182 to
7 on page 182.
NOTE: You can execute these steps in parallel on all frontend computers, on
the application computer and all media server computers.
9. Log on to all media server computers as root and execute steps 3 on page
182 to 7 on page 182.
NOTE: You can execute these steps in parallel on all media server
computers, on the application computer and all frontend computers.
A31003-S5070-J100-12-7631, 02/2013
183
IG_PrepComputers.fm
Using FQDNs for Very Large Deployment
4.6 Using FQDNs for Very Large Deployment

4.6.1 General Considerations
Very Large Deployment requires the fully qualified domain names (FQDNs) of all
involved computers to be resolvalbe in IP addresses for any other computer and
vice versa.
This occurs by familiarizing a computer with a DNS server (YaST > Network
Devices > Network Settings > Hostname/DNS > Name Servers and Domain
Search List) or by making entries in the /etc/hosts file on this computer for
the other computers according to the following pattern:
<IP address> <domain name> <computer name>
Example of an entry for resolving the FQDN of a frontend computer in the /etc/
hosts file on the application computer:
10.1.42.207 docof02fe01.site docof01fe01
IMPORTANT: This necessity is independent from whether you use FQDNs,
computer names or IP addresses for setting up the OpenScape UC Application
(see Editing Response Files in Section 5.2.2, Procedure, on page 198).
NOTE: OpenScape Fusion clients and the Outlook plug-in must be able to
resolve FQDNs only if you use FQDNs instead of computer names or IP
addresses for installing the OpenScape UC Application (see Editing Respone
Files in Section 5.2.2, Procedure, on page 198).
4.6.2 FQDNs when using several Network Boards

4.6.2.1 FQDN and Bonding
If a computer has several network boards and uses bonding (see Section 4.4.1,
With Bonding, on page 165) and if other computers resolve FQDNs using a /
etc/hosts file, the IP address and the FQDN of the bonding network board are
used in this file.
184
A31003-S5070-J100-12-7631, 02/2013
IG_PrepComputers.fm
4.6.2.2 FQDN without Bonding

If a computer uses several network boards without bonding (see Section 4.4.2,
Without Bonding, on page 180) and if other computers resolve FQDNs using a
/etc/hosts file, the IP address and the FQDN of these network boards are
used in an appropriate manner.
Example: A media server computer has two network boards A and B. It uses A
for communicating with the application computer and B for communicating with
the PBX. If the application computer does not receive the FQDNs of the other
computers from the DNS server but resolves them via the /etc/hosts file on
the application computer, this file must contain an entry according to the following
pattern:
<IP address of A> <FQDN of A> <computer name of A>
Example:
10.1.42.123 docof02ms01if01.site docof02ms01if01
If the PBX computer resolves the FQDNs via the /etc/hosts file on the PBX
computer, this file must contain an entry according to the following pattern:
<IP address of B> <FQDN of B> <computer name of B>
Example:
10.1.42.124 docof02ms01if02.site docof02ms01if02
A31003-S5070-J100-12-7631, 02/2013
185
IG_PrepComputers.fm
4.6.3 List of FQDNs to be resolved for every

Computer
In the following we list for every computer involved in the OpenScape UC
Application which FQDNs it must resolve:
NOTE: Most of the following computers are optional. But if they are available,
they must be able to resolve the FQDNs of the specified other computers, inasfar
as these other computers exist too.
1. Application computer
The application computer must be able to resolve the FQDNs of the following
computers:
a) All frontend computers of the same cluster
b) All media server computers of the same cluster
c) PBX computer of the same cluster
a) Network board for SOAP communication
b) Network board for CSTA communication
d) XPR computer of the same cluster
e) All Mobile Client Facade computers of the same cluster
f)
All Web Collaboration server computers
g) Lotus Domino server computer

h) Microsoft OCS/Lync computer
i)
Instant-messaging server computer
j)
NTP server computer
k) Deployment service server computer

l)
LDAP server computer
m) Microsoft Exchange server computer

n) Google Apps computer
o) Further computers, from which the application computer is accessed by
SOAP or SPML interface if required (see the programming guides
OpenScape UC Application SOAP SDK and OpenScape UC Application
SPML SDK).
186
A31003-S5070-J100-12-7631, 02/2013
IG_PrepComputers.fm
Example of a /etc/hosts for an application computer:

127.0.0.1 localhost
# PBX
10.1.42.205 pbxsoapif.site pbxsoapif
10.1.42.206 pbxcstaif.site pbxcstaif
# Frontend computers
# Media server computers
10.1.42.210 docof02ms01.site docof02ms01
# Others
10.1.42.213
10.1.42.214
10.1.42.215
10.1.42.216
10.1.42.217
10.1.42.218
10.1.42.219
xpr7.mywindowsdomain xpr7
docof02facade.site docof02facade
webcollaboration.mywindowsdomain webcollaboration
lotusdomino.mywindowsdomain lotusdomino
ocs.mywindowsdomain ocs
openfire.site openfire
ntpserver.mywindowsdomain ntpserver
2. Frontend computer
a) Application computer of the same cluster
b) NTP server computer
3. Media server computer
a) Application computer of the same cluster
b) Network board for the SIP communication of the PBX computer of the
same cluster
c) NTP server computer
4. PBX computer
a) Optional: Application computer of the same cluster
b) Network board for the SIP communication of all media servers of the
same cluster
5. XPR computer
Windows computers resolve FQDNs via the
%Windir%\system32\drivers\hosts file.
a) Domain controller computer of its Windows domain
b) Application computer of the same cluster
c) PBX computer of the same cluster
A31003-S5070-J100-12-7631, 02/2013
187
IG_PrepComputers.fm
d) NTP server computer

6. Mobile Client Facade server computer
a) Application computer
b) NTP server computer
7. Web Collaboration server computer
b) The computer(s) for the MS SQL server cluster for OpenScape Web
Collaboration
c) Application computer of all clusters
d) NTP server computer
8. Lotus Domino server computer
b) Application computer of all clusters
9. Microsoft OCS/Lync computer
b) Application computer of all clusters
10. Instant-messaging computer
a) Application computer of all clusters
b) Computer on which the MySQL database is installed
Example:
10.1.42.208 docof02ofs.site docof02ofs openfire1
188
A31003-S5070-J100-12-7631, 02/2013
IG_PrepComputers.fm
11. Load balancer computer

b) All frontend computers of all clusters
12. Google Apps computer
a) Application computer of all clusters
b) Proxy server computer (see section Installation and Configuration of
OpenScape Fusion for Google Apps)
A31003-S5070-J100-12-7631, 02/2013
189
IG_PrepComputers.fm
190
A31003-S5070-J100-12-7631, 02/2013
IG_InstallOpenScape.fm
Installing the OpenScape UC Application
5 Installing the OpenScape UC Application

NOTE: To execute the steps described in this section you need to know which
deployment scenario you want to use (see OpenScape UC Application Planning
Guide).
This chapter describes the procedures for installing the OpenScape UC
Application. You find setup instructions for OpenScape Voice in the OpenScape
Voice Installation and Upgrades installation guide.
The software is supplied and installed as RPM package. Some software
components require more than one RPM.
The OpenScape UC Application installation process follows this general outline:
1. Configuring the installation
A sample of the response file is copied from the setup file
OpenScapeUcSuiteApps-Repository-<version>.iso
for the OpenScape UC Application to the respective computer and edited.
You find details on this major step in Section 5.2, Configuring the
Installation, on page 195.
2. Installation
You install OpenScape UC Application components using osc-setup.
IMPORTANT: You install osc-setup using zypper or yast. All other
OpenScape UC Application components are not installed by means of zypper
or yast.
You find details on this major step in Section 5.3, Installation, on page 233.
A31003-S5070-J100-12-7631, 02/2013
191
Installation Requirements
5.1 Installation Requirements

Ensure that all requirements are met before starting the OpenScape UC
Application installation.
5.1.1 Verifying the Installation Requirements

Table 6 describes the items you should verify before you start installing the
OpenScape UC Application. These are general requirements only. Additional,
component-specific items to be checked before installing that component are
listed in the respective chapters.
Requirements
Initial
Confirm the topology of the OpenScape UC Application system and verify that
the infrastructure components are the appropriate versions. Refer to the
Note:
The network topology at the customer site is the responsibility of the customers
IT organization.
Prior to starting the OpenScape UC Application Unified Communications Server
installation you should be provided a set of deployment worksheets or
instructions from the customer administrator or representative. See Section 2.3,
Information Provision by the Customer, on page 30.
If virtual computers are used, make sure that the values described in Table 2 on
page 36 are set.
Make sure that the computers have been duly prepared according to Chapter
4, Installing and Configuring the Computer and Operating System.
Make sure that users exist in the database and then map them, based on
topology, to the planned OpenScape UC Application users.
Check that preparation of all domains and systems as described in Part 2 Preparations is complete.
Check if the system time of all OpenScape UC Application-related computers is
synchronized with a maximum difference of one second.
Note:
(NTP) is often used for synchronizing the system time (YaST > Network
Services > NTP Configuration).
Note:
When using SRTP, the time zone has to be identical on all computers.
If you use an FSC RX330 as computer, sporadic leaps in time may occur when
deploying the BIOS default settings. To prevent this, set value Disabled in the
BIOS under Advanced > Advanced System Configuration > High Precision
Event Timer.
Table 6
192
Pre-check for OpenScape UC Application Installation
A31003-S5070-J100-12-7631, 02/2013
Requirements
Initial
Attention!
Validate the certificates assigned to the OpenScape UC Application-related
computers. You can obtain details on this from the administrator documentation
OpenScape UC Application Configuration and Administration.
Table 6
Pre-check for OpenScape UC Application Installation
5.1.2 Accounts
The following accounts exist in OpenScape UC Application:
NOTE: The following accounts are not created by OpenScape UC Application.
Solid administrator database account (dba).

Please be sure to set the password to a unique, secure value (refer e. g. to
the OpenScape Voice V4 R1 Installation and Upgrade Guide installation
guide). There is no Unix account associated with this account.
The OpenScape UC Application Management Administrator (administrator)

password is set up also during the configuration. Special rules regarding
complexity are enforced for this account password (see Section 6.6,
Creating the OpenScape UC Application Users in the CMP, on page 485).
There is no Unix account associated with this account.
After the installation, password complexity rules that match the customer's
password policy can be defined by the system administrator in a policy
settings file for all OpenScape UC Application user accounts.
A31003-S5070-J100-12-7631, 02/2013
193
5.1.3 Database
While OpenScape UC Application is being set up, a Solid database 6.5 is
automatically installed for Small Deployment and Large Deployment.
IMPORTANT: The solidDB console is an unsupported tool of the database
manufacturer (Solid Information Technology). In customer systems, it may be
used only with direct Global Vendor Support (GVS) or under supervision of the
Siemens Enterprise Communications GmbH & Co. KG development. Severe
database corruption can occur by using this tool to modify the database.
NOTE: Each SQL client tool that does not terminate transactions immediately
may decrease the Solid database performance significantly. Terminate these
tools immediately after job/lookup/... is through.
A MySQL database is installed for Very Large Deployment.
194
A31003-S5070-J100-12-7631, 02/2013
Configuring the Installation
5.2 Configuring the Installation

The installation is configured by creating response files.
IMPORTANT: Before creating response files, ensure that the customer administrator or representative has provided you with the necessary configuration data.
See Section 2.3, Information Provision by the Customer, on page 30.
You find an overview of the deployment scenarios also in the OpenScape UC
Application Planning Guide.
A31003-S5070-J100-12-7631, 02/2013
195
5.2.1 Preparation
NOTE: The application computer is the machine on which the OpenScape
backend services are installed. The media server computer is the machine on
which the OpenScape media services are installed, if they are not set up on the
application computer. The web server (Tomcat) is installed on the frontend
computer for accessing the application computer from the Desktop Client, Web
Client or Mobile Client, but not for accessing the CMP. This applies if the web
server is not installed on the application computer. Several entities may exist of
the media server computer and of the frontend computer.
The following table lists the components to be installed:
Component
Integrated
Deployment
Small
Deployment
Large Deployment and Very Large

Deployment
Application
computer
Application
computer
Application
computer
-1
-2
-2
Customer License Management (CLM)
Optional
Optional
Deployment License Server (DLS)
External3
External 3
Frontend
computer
Media server
computer
OpenScape backend services

PBX
OpenScape media services
OpenScape frontend services (web server;
Tomcat)
OpenScape Voice Assistant
CMP
RG 8700 Assistant
OpenSOA4 Framework
Solid Database5
ActiveMQ
Table 7
Components to be installed by the OpenScape UC Application Setup
1 In this deployment scenario, the OpenScape Voice is required on the application computer, but the OpenScape Voice installation is not
described in this guide.
2 In this deployment scenario, the PBX is required on a computer different from the application computer. The installation of the PBX is not
described in this guide.
3 This component operates on a separate Windows computer.
4 OpenSOA of the Siemens Enterprise Communications GmbH & Co. KG
5 MySQL database for Very Large Deployment
The following applies:
196
means that this component is mandatorily installed on the application

computer.
A31003-S5070-J100-12-7631, 02/2013
Optional means that this component can be installed on the application

computer.
External means that this component is never installed on the application

computer.
A31003-S5070-J100-12-7631, 02/2013
197
5.2.2 Procedure
5.2.2.1 Example of Deployment Scenario Small Deployment
1. Mount the Repository ISO file according to the following pattern:
mount -o loop <path>/OpenScapeUcSuiteApps-Repository-<version number>.iso /mnt
Example of a directory on the hard disk:

mount -o loop /tmp/shi/osuca7/OpenScapeUcSuiteApps-Repository-V7R1.0.0-130000.iso /mnt
If you do not wish to mount a Repository ISO file on the computer hard disk
but on a DVD, mount the DVD first by the mount /dev/cdrom /media
command and subsequently the ISO file by the following command:
mount -o loop <path>/OpenScapeUcSuiteApps-Repository-<version>.iso /mnt
Example:
mount -o loop /media/OpenScapeUcSuiteApps-Repository-V7R1.0.0-130000.iso /mnt
If you wish to mount the Repository ISO file on a USB stick instead of on the
computer hard disk, proceed as follows:
IMPORTANT: Only FAT32-formatted USB sticks are natively supported by
SLES 11. All ISO installation files are smaller than 4 GB and can thus be
processed by FAT32.
ls /dev/sd*
Example output:
b) Connect the USB stick to the computer.
ls /dev/sd*
Example output:
The connected USB stick makes the difference between the two outputs.
In this example it is a USB stick (sdf) with one partition (sdf1). If the USB
stick had several partitions, sdf2, sdf3 etc. would also be put out.
198
A31003-S5070-J100-12-7631, 02/2013
mkdir /media
e) Mount the USB stick:
Example:
f)

mkdir /mnt
g) Mount the Repository ISO file on the USB stick:

Example:
2. Execute the following command to copy the response file template:
Connection to OpenScape Voice:
cp /mnt/templates/knut.responsefile.txt.templ_StandardDuplexSmall /root/knut.responsefile.txt
Connection to HiPath 4000:
cp /mnt/templates/knut.responsefile.txt.templ_Small /root/knut.responsefile.txt
IMPORTANT: Copy the file as specified to the directory named /root but
not to the Root directory /.
3. Copy the checkResponsefileOnLocalNode.sh file from the
OpenScapeUcSuiteApps-Repository -<version>.iso file to the
computer as follows.
cp /mnt/support/checkResponsefileOnLocalNode.sh /root/
This script serves for checking the edited response file in step 13 on page
201.
4. Unmount the ISO file.
umount /mnt
5. Make the knut.repsonsefile.txt editable.
chmod +w /root/knut.responsefile.txt
A31003-S5070-J100-12-7631, 02/2013
199
6. Open the response file with an editor (for example with vi):
vi /root/knut.responsefile.txt
7. Look for the following line:
SI_SYMPHONIA_ADMIN_PASSWORD=<PLACEHOLDER_symphonia_admin_pass
word>
Replace <PLACEHOLDER_symphonia_admin_password> with the
password of the Symphonia administrator.
IMPORTANT: This password must comply with the security policies, which
are defaulted as follows:
SI_COMMUNITY_NAME=<PLACEHOLDER_community_name>
Replace <PLACEHOLDER_community_name> with the community name.
systems differ.
IMPORTANT: Verify that the community names on all computers of an

OpenScape UC Application system (application computer, frontend
computers, media server computers and the computer of the PBX are
identical.

Community String.
underscore "_" are permitted. The latter must not appear at the beginning or
end of the name. The corresponding regular expression reads as follows:
[A-Za-z0-9][A-Za-z0-9_]*[A-Za-z0-9]
Example:
99_Red_Balloons
200
A31003-S5070-J100-12-7631, 02/2013
9. Look for the following lines:

SI_PRIMARY_NODE_HOST=<PLACEHOLDER_fqdn>
SI_LOCAL_HOST=<PLACEHOLDER_fqdn>
SI_DB_HOST=<PLACEHOLDER_fqdn>
Replace <PLACEHOLDER_fqdn> with the fully qualified domain name
(FQDN) or the IP address of the application computer. We recommend using
the FQDN.
IMPORTANT: If two (or more) network interface cards are used, only one
interface card can be used to access the OpenScape UC Application on the
application computer from the clients.
Ensure that the application server name used in the response file is resolved
to the IP address of the network card used for the following clients:
- OpenScape UC Application Desktop Client
- OpenScape UC Application Web Client
- Clients that use the Outlook plug-in
The connectors may otherwise be started on the wrong network card (see
Section 4.4, Configuring Multiple Network Interface Cards, on page 165).
SI_LOCAL_NAME=offboard
If required, replace offboard with the name of the application computer to
be displayed in the CMP.
IMPORTANT: The value of SI_LOCAL_NAME must not contain spaces.
SI_DB_LOGON_PASSWORD=<PLACEHOLDER_dbms_dba_password>
h) Replace <PLACEHOLDER_dbms_dba_password> with the password of
the Solid database administrator. Due to security concerns it should not
be the default password (dba).
12. Save the response file.
13. Execute the file copied in step 3 on page 199:
bash /root/checkResponsefileOnLocalNode.sh
This script reads this response file and checks,
whether the IP address has been assigned to one of the network boards,
whether further SI_***_HOST definitions correspond to the local

computer configuration,
whether the administrator password corresponds to the password policy

and
A31003-S5070-J100-12-7631, 02/2013
201
whether the community name contains permitted characters only.
NOTE: This script checks the file /root/knut.responsefile.txt by

default. If you wish to check another file, specify the file name as parameter
of the script invocation.
Example output:
INFO:
INFO:
INFO:
INFO:
INFO:
INFO:
INFO:
INFO:
INFO:
INFO:
INFO:
INFO:
INFO:
INFO:
INFO:
INFO:
INFO:
INFO:
INFO:
using responsefile '/root/knut.responsefile.txt'.

testing hostname 'docof02osuc04' ...
found hostname: 'docof02osuc04' (10.9.30.96) on a local interface. ok.
testing 'SI_LOCAL_HOST' ...
'SI_LOCAL_HOST=10.9.30.96' matches this computer's hostname/IPaddress. ok.
testing 'SI_PRIMARY_NODE_HOST' ...
is a primary node
SI_LOCAL_HOST == SI_PRIMARY_NODE_HOST. ok
testing 'SI_DB_HOST' ...
SI_DB_HOST == SI_LOCAL_HOST. ok
testing 'SI_COMMUNITY_NAME' ...
'SI_COMMUNITY_NAME=community04' ok
testing 'SI_SYMPHONIA_ADMIN_PASSWORD' ...
- length: 10 ok
- digits: 1 ok
- special chars: 1 ok
- upper case letters: 1 ok
- maximum repeated chars ok
SI_SYMPHONIA_ADMIN_PASSWORD ok
14. Ensure that the response file is kept in a safe location. The response file is
not currently contained in the system backup sets, but it is needed to rebuild
the system during a crash recovery.
NOTE: The restore mechanism uses the database administrator password
from the original system, where the backup was taken, to access the Solid
database. If this password is not known, no recovery is possible. This
password is defined in the response file and that is why the response file must
be backed up in a safe location.
Continue with Section 5.3, Installation, on page 233.
202
A31003-S5070-J100-12-7631, 02/2013
5.2.2.2 Example of Deployment Scenario Large Deployment

Response file for the application computer
Execute the following steps on the application computer to create a response file
for the application computer.
Example:
Example:
processed by FAT32.
ls /dev/sd*
Example output:
ls /dev/sd*
Example output:
A31003-S5070-J100-12-7631, 02/2013
203
mkdir /media
Example:
f)

mkdir /mnt

Example:

cp /mnt/templates/knut.responsefile.txt.templ_Large_BE /root/knut.responsefile.txt
OpenScapeUcSuiteApps-Repository -<version>.iso file to the
computer as follows.
206.
umount /mnt
204
A31003-S5070-J100-12-7631, 02/2013
word>
9. Replace <PLACEHOLDER_community_name> with the community name.
systems differ.

identical.

Community String.
[A-Za-z0-9][A-Za-z0-9_]*[A-Za-z0-9]
Example:
99_Red_Balloons
A31003-S5070-J100-12-7631, 02/2013
205
the FQDN.
IMPORTANT: If two (or more) network cards are used, only one interface
card can be used to access the OpenScape UC Application on the application
computer from the clients.
If required, replace offboard with the name of the application computer to
be displayed in the CMP.
14. Execute the file copied in step 3 on page 204.
206


and
A31003-S5070-J100-12-7631, 02/2013

Example output:
INFO:
INFO:
INFO:
INFO:
INFO:
INFO:
INFO:
INFO:
INFO:
INFO:
INFO:
INFO:
INFO:
INFO:
INFO:
INFO:
INFO:
INFO:
INFO:

is a primary node
- length: 10 ok
- digits: 1 ok
password is defined in the response file and that is why the created response
file must be backed up in a safe location.
A31003-S5070-J100-12-7631, 02/2013
207
Response file for the frontend server

Execute the following steps on the frontend computer to create a response file for
the frontend computer.
Example:
processed by FAT32.
ls /dev/sd*
Example output:
ls /dev/sd*
Example output:
mkdir /media
Example:
208
A31003-S5070-J100-12-7631, 02/2013

f)

mkdir /mnt

Example:
cp /mnt/templates/knut.responsefile.txt.templ_Large_FE /root/knut.responsefile.txt
18. Copy the file .../support/checkResponsefileOnLocalNode.sh
from the file OpenScapeUcSuiteApps-Repository-<version>.iso to
the frontend computer in the same manner. This script serves for checking
the edited response file in step 30 on page 211.
umount /mnt
word>
IMPORTANT: The password must be identical with the one used on the
application computer (see step 7 on page 204).
A31003-S5070-J100-12-7631, 02/2013
209
24. Replace <PLACEHOLDER_community_name> with the community name.

systems differ.

identical.

Community String.
[A-Za-z0-9][A-Za-z0-9_]*[A-Za-z0-9]
Example:
99_Red_Balloons
the FQDN.
(FQDN) or the IP address of the frontend computer. We recommend using
the FQDN.
SI_LOCAL_NAME=<PLACEHOLDER_display_name>
210
A31003-S5070-J100-12-7631, 02/2013
Replace <PLACEHOLDER_display_name> with the name of this frontend

computer to be displayed in the CMP.

whether the application computer specified by the computer name (host

name), fully qualified domain name or IP address can be reached,


and

A31003-S5070-J100-12-7631, 02/2013
211
31. IMPORTANT: Ensure that the response file is kept in a safe location. The
response file is not currently contained in the system backup sets, but it is
needed to rebuild the system during a crash recovery.
password is defined in the response file and that is why this response file
must be backed up in a safe location.
212
A31003-S5070-J100-12-7631, 02/2013
Response file for the media server computer

Execute the following steps on the media server computer to create a response
file for the media server computer.
Example:
processed by FAT32.
ls /dev/sd*
Example output:
ls /dev/sd*
Example output:
mkdir /media
Example:
A31003-S5070-J100-12-7631, 02/2013
213

f)

mkdir /mnt

Example:
cp /mnt/templates/knut.responsefile.txt.templ_Large_MS /root/knut.responsefile.txt
from the setup file OpenScapeUcSuiteApps-Repository<version>.iso to the media server computer in the same manner. This
script serves for checking the edited response file in step 45 on page 216.
umount /mnt
word>
214
A31003-S5070-J100-12-7631, 02/2013

systems differ.

identical.

Community String.
[A-Za-z0-9][A-Za-z0-9_]*[A-Za-z0-9]
Example:
99_Red_Balloons
the FQDN.
Replace <PLACEHOLDER_fqdn> with the FQDN or the IP address of the
media server computer. We recommend using the FQDN.
A31003-S5070-J100-12-7631, 02/2013
215
Replace <PLACEHOLDER_display_name> with the name of this media

server computer to be displayed in the CMP.
IMPORTANT: If you configure several media server computers, enter an




and

216
A31003-S5070-J100-12-7631, 02/2013
A31003-S5070-J100-12-7631, 02/2013
217
5.2.2.3 Example of Deployment Scenario Very Large

Deployment
Response file for the application computer
Execute the following steps on the application computer to create a response file
for the application computer.
Example:
processed by FAT32.
ls /dev/sd*
Example output:
ls /dev/sd*
Example output:
mkdir /media
218
A31003-S5070-J100-12-7631, 02/2013

Example:
f)

mkdir /mnt

Example:

cp /mnt/templates/knut.responsefile.txt.templ_VeryLarge_BE /root/knut.responsefile.txt
OpenScapeUcSuiteApps-Repository -<version>.iso setup file to
the computer as follows.
221.
umount /mnt
word>
A31003-S5070-J100-12-7631, 02/2013
219

systems differ.

identical.

Community String.
[A-Za-z0-9][A-Za-z0-9_]*[A-Za-z0-9]
Example:
99_Red_Balloons
220
A31003-S5070-J100-12-7631, 02/2013

the FQDN.
IMPORTANT: If two (or more) network interface cards are used, only one
interface card can be used to access the OpenScape UC Application on the
application computer from the clients.
If the application computer is to appear in the CMP under a different name
than the default value offboard, replace offboard with the name to be
displayed.
Replace <PLACEHOLDER_dbms_dba_password> with the password of an
MySQL database user, for example user root.
NOTE: This is not the SLES user root but user root of the MySQL database.


and
A31003-S5070-J100-12-7631, 02/2013
221

Example output:
INFO:
INFO:
INFO:
INFO:
INFO:
INFO:
INFO:
INFO:
INFO:
INFO:
INFO:
INFO:
INFO:
INFO:
INFO:
INFO:
INFO:
INFO:
INFO:

is a primary node
- length: 10 ok
- digits: 1 ok
password is defined in the response file and that is why the created response
file must be backed up in a safe location.
222
A31003-S5070-J100-12-7631, 02/2013
Response file for the frontend server

Execute the following steps on the frontend computer to create a response file for
the frontend computer.
Example:
processed by FAT32.
ls /dev/sd*
Example output:
ls /dev/sd*
Example output:
mkdir /media
Example:
A31003-S5070-J100-12-7631, 02/2013
223

f)

mkdir /mnt

Example:
cp /mnt/templates/knut.responsefile.txt.templ_VeryLarge_FE /root/knut.responsefile.txt
from the setup file OpenScapeUcSuiteApps-Repository<version>.iso to the frontend computer in the same manner. This script
serves for checking the edited response file in step 28 on page 226.
umount /mnt
word>
224
A31003-S5070-J100-12-7631, 02/2013

systems differ.

identical.

Community String.
[A-Za-z0-9][A-Za-z0-9_]*[A-Za-z0-9]
Example:
99_Red_Balloons
the FQDN.
(FQDN) or the IP address of the frontend computer. We recommend using
the FQDN.
A31003-S5070-J100-12-7631, 02/2013
225
Replace <PLACEHOLDER_display_name> with the name of this frontend

computer to be displayed in the CMP.

NOTE: This must be the password you used on the application computer in
step 11 on page 221.



and

226
A31003-S5070-J100-12-7631, 02/2013
A31003-S5070-J100-12-7631, 02/2013
227
Response file for the media server computer

Execute the following steps on the media server computer to create a response
file for the media server computer.
30. In case of Very Large Deployment there are three types of media servers:
- Pure video media server
- Pure audio media server
- Mixed video and audio media server
You can set them by configuration. The response file is independent from the
Media server type.Mount the Repository ISO file according to the following
pattern:
Example:
processed by FAT32.
ls /dev/sd*
Example output:
ls /dev/sd*
Example output:
228
A31003-S5070-J100-12-7631, 02/2013

mkdir /media
Example:
f)

mkdir /mnt

Example:
cp /mnt/templates/knut.responsefile.txt.templ_VeryLarge_MS /root/knut.responsefile.txt
from the setup file OpenScapeUcSuiteApps-Repository<version>.iso to the media server computer in the same manner. This
script serves for checking the edited response file in step 43 on page 231.
umount /mnt
word>
A31003-S5070-J100-12-7631, 02/2013
229

systems differ.

identical.

Community String.
[A-Za-z0-9][A-Za-z0-9_]*[A-Za-z0-9]
Example:
99_Red_Balloons
the FQDN.
230
A31003-S5070-J100-12-7631, 02/2013

(FQDN) or the IP address of the media server computer. We recommend
using the FQDN.
Replace <PLACEHOLDER_display_name> with the name of this media
server computer to be displayed in the CMP.
IMPORTANT: If you configure several media server computers, enter an

NOTE: This must be the password you used on the application computer in
step 11 on page 221 and on the frontend computer in step 26 on page 226.



and
A31003-S5070-J100-12-7631, 02/2013
231

232
A31003-S5070-J100-12-7631, 02/2013
Installation
5.3 Installation
The OpenScape UC Application software is installed for Small Deployment,
Large Deployment and Very Large Deployment using the osc-setup script.
IMPORTANT: The installation must be done as root.
E/A Cockpit is set up as part of the Web Client installation by default. Except as
otherwise noted in the Web Client release notes you need not execute any
special installation steps.
The installation of the OpenScape UC Application V7 includes an installation of
the IBM JRE 1.6.
A31003-S5070-J100-12-7631, 02/2013
233
Installation
5.3.1 Providing the Installation Sources in an

Installation Repository in osc-setup
ISO files are the only installation source of the OpenScape UC Application. DVDs
are no longer used. The installation of the OpenScape UC Application is done by
using the osc-setup script. The following main steps that are described in detail
in the following sub-sections must be executed before:
1. Create a repository in zypper by using the ISO files.
This repository only is needed to install osc-setup.
2. Install osc-setup.
3. Create a repository in osc-setup by using the ISO files.
234
A31003-S5070-J100-12-7631, 02/2013
Installation
5.3.1.1 Needed ISO Files

Table 8 shows the purposes and computers the ISO files are needed for:
Setup file
Contents
Deployment scenario
Small
Large Deployment
Deployment and Very Large
Deployment
AC1
AC
FE2
MS3
OpenScapeUcSuiteApps-Repository<version>.iso
Installation scripts, Repository meta data, etc.
OpenScapeUcSuiteAppsBasePackage-<version>.iso
The actual OpenScape UC Application
OpenScapeUcSuiteAppsOptionalPackage-<version>.iso
Lotus Domino, Application Builder, Client

Integration, Lotus Notes Extensions, etc.
OpenScapeUcSuiteApps-English<version>.iso
Announcements in English, TTS, ASR, Auto

Attendant, voice conferencing, voice portal
and voice portal speech
OpenScapeUcSuiteApps-German<version>.iso5
Announcements in German, TTS, ASR, Auto

OpenScapeUcSuiteApps-Portuguese<version>.iso
Announcements in Portuguese and Brazilian,

TTS, Auto Attendant, voice conferencing and
voice portal
OpenScapeUcSuiteApps-Spanish<version>.iso
Announcements in Spanish, TTS, Auto

Attendant, voice conferencing and voice portal
OpenScapeUcSuiteApps-Italian<version>.iso
Announcements in Italian, TTS, Auto

OpenScapeUcSuiteApps-French<version>.iso
Announcements in French, TTS, Auto

OpenScapeUcSuiteApps-Chinese<version>.iso
Announcements in Chinese, TTS, Auto

OpenScapeUcSuiteAppsAdditonalLanguages<version>.iso
The remaining languages supported for

announcements (see Table 10 on page 273)
and voice conferencing (see step 16 on page
275)
Table 8
1
2
3
4
5
Using the ISO Setup Files of the OpenScape UC Application
Frontend computer
IMPORTANT: This file is always required for setting up, updating or upgrading any deployment scenario.
IMPORTANT: This file is always required for setting up, updating or upgrading Integrated Deployment.
A31003-S5070-J100-12-7631, 02/2013
235
Installation
NOTE: Example of a file name:

OpenScapeUcSuiteApps-Repository-V7R1.0.0-130000.iso
NOTE: The same applies for updating and upgrading.

Legend:
Icon
Meaning
You can use this ISO file for an installation on this computer.
This ISO file is not required for an installation on this computer.
Table 9
Legend for using the ISO Files
NOTE: The ISO files have a maximum size of 4 GB and can therefore be stored
on a USB stick formatted with FAT32.
The ISO files can be made available locally at the computer where osc-setup and
the OpenScape UC Application components will be installed or they can be made
available remotely over the network. The remote provision has the advantage that
the ISO files only must be available once on an arbitrary SLES 11 computer in the
network and need not be copied to each computer where OpenScape UC
Application components will be installed. The disadvantage is that more
preparation steps are needed.
NOTE: The ISO files remotely made available may be used for installing a
Mobile Client Facade Server or an Openfire server as well.
Continue either with Section 5.3.1.3, Creating a Repository in osc-setup by using
remote Installation Sources, on page 243 or Section 5.3.1.2, Creating a
Repository in osc-setup by using local Installation Sources, on page 237.
NOTE: If you want to install additional RPM packages follow the instructions in
Section 14.1, Installing additional RPM Packages of the OpenScape UC Application, on page 637.
236
A31003-S5070-J100-12-7631, 02/2013
Installation
5.3.1.2 Creating a Repository in osc-setup by using local

Logging to: /var/log/OpenScapeUC/osc-setup-2012-12-03_16:51:00.log
osc-setup version: "7.1.4-0"
SUSE VERSION: 11 SERVICEPACK: 2
Registered repository (url):
1 dir:///tmp/tmpRepo
Operation took: 0 seconds
Logfile: /var/log/OpenScapeUC/osc-setup-2012-12-03_16:51:00.log
Installation Sources
Creating a repository in zypper
1. Execute the following command to check which sources have been provided
in zypper:
zypper lr
Example output:
:
# | Alias
| Name | Enabled | Refresh
--+-----------------------------------------------------------+------+---------+-------1 | SUSE-Linux-Enterprise-Server-11-SP2 11.2.2-1.234 | SUSE-Linux-Enterprise-Server-11-SP2
11.2.2-1.234 | Yes
| No
2. Verify that only the SLES setup medium is registered.

3. If further setup media are registered, remove them with the following
command:
zypper rr <number>
<number> is the number you find in the first column of the zypper lr
output.
Example: zypper rr 2
4. Execute a command for registering the setup medium of the OpenScape UC
Application in zypper according to the following pattern:
zypper ar <URI> ucapp
Example of <URI> when using a local repository:
iso:/?iso=<path to ISO file>/OpenScapeUcSuiteApps-Repository-V7R1.0.0-130000.iso
Complete examples:
zypper ar iso:/?iso=/tmp/shi/osuca7/OpenScapeUcSuiteApps-Repository-V7R1.0.0-130000.iso
ucapp
The ar option represents add repository.
Example output:
A31003-S5070-J100-12-7631, 02/2013
237
Installation
Adding repository 'ucapp' [done]

Repository 'ucapp' successfully added
Enabled: Yes
Autorefresh: No
GPG check: Yes
URI: iso:///?iso=/tmp/shi/OpenScapeUcSuiteApps-Repository-V7R1.0.0-130000.iso
5. You can check the result of the action with the following command:
zypper lr
The lr option represents list repository.
6. This output follows:
:
# | Alias
--+------------------------------------+----------------------------+---------+-------1 | SUSE-Linux-Enterprise-Server-11-SP2 11.2.2-1.234 | SUSE-Linux-Enterprise-Server-11SP2 11.2.2-1.234 | Yes
| No
2| ucapp
| ucapp
| Yes
| No
7. Use the following command to check whether the repository was defined
correctly:
zypper ref
Example output:
Retrieving repository 'ucapp' metadata [\]
New repository or package signing key received:
Key ID: 9351C8D3C9172AE7
Key Name: SEN-HiPathApplication (Signing of RPMs) <e-swproduction-team.com@siemens.com>
Key Fingerprint: 03DF2920E8C51F91E2B6B4EB9351C8D3C9172AE7
Repository: ucapp
Do you want to reject the key, trust temporarily, or trus
always? [r/t/a/?] (r):
8. Enter a and push the return key.
Retrieving repository 'ucapp' metadata [done]
Building repository 'ucapp' cache [done]
All repositories have been refreshed.
osc-setup is now registered in zypper.
238
A31003-S5070-J100-12-7631, 02/2013
Installation
Installing osc-setup
9. Install the setup script osc-setup.
zypper in osc-setup
in zypper:
zypper lr
11. Remove the repository that provided osc-setup from zypper:
zypper rr <number>
output.
12. Enter the following command:
zypper se osc-setup
Example output:
Loading repository data...
Reading installed packages...
S | Name
| Summary
| Type
--+-----------+-----------------------------+-------i | osc-setup | Setup tools for OpenScapeUC | package
The i in the first column indicates that osc-setup is installed.
osc-setup lr
The following example output indicates that no installation repository has
been provided to the osc-setup yet:
Operation took: 1 second
A31003-S5070-J100-12-7631, 02/2013
239
Installation
Creating a repository in osc-setup

14. Create a directory for the temporary repository.
Example:
mkdir /tmp/tmpRepo
15. Provide the installation source OpenScapeUcSuiteApps-Repository<version>.iso> by the following command in osc-setup. This command
creates a new repository; it does not add an installation source to an existing
repository. The repository name may differ from the repository name in
zypper.
IMPORTANT: The following command creates a new repository, thus
deleting all repositories that may have already been provided.
osc-setup cr -l <path to the temporary repository> <path to the file

OpenScapeUcSuiteApps-Repository-<version>.iso>
Example:
osc-setup cr -l /tmp/tmpRepo /tmp/shi/osuca7/OpenScapeUcSuiteApps-Repository-V7R1.0.0130000.iso
NOTE: osc-setup does not use an alias.
IMPORTANT: This command creates a temporary, locally linked repository.

This repository can only be used as long as the ISO files used are not deleted
or moved and the computer is not rebooted.
You also provide several ISO files by one command.
OpenScapeUcSuiteApps-Repository-<version>.iso> <path to another ISO file>
Example:
osc-setup cr -l /tmp/tmpRepo /tmp/shi/osuca7/OpenScapeUcSuiteApps-Repository-V7R1.0.0130000.iso /tmp/shi/osuca7/OpenScapeUcSuiteApps-English-V7R1.0.0-130000.iso
IMPORTANT: One of the ISO files in the command must be the file
OpenScapeUcSuiteApps-Repository-<version>.iso.
If you wish to provide all ISO files in a directory by one command you need to
use option -b in addition.
240
A31003-S5070-J100-12-7631, 02/2013
Installation
osc-setup cr -b -l <path to the temporary repository> <path to the file

OpenScapeUcSuiteApps-BasePackage-<version>.iso>
Example:
osc-setup cr -b -l /tmp/tmpRepo /tmp/shi/osuca7/OpenScapeUcSuiteApps-BasePackageV7R1.0.0-130000.iso
Example output:
Logging to: /var/log/OpenScapeUC/osc-setup-2012-1203_16:50:00.log
checking Arguments
Option Base-directory: yes
/tmp/shi/osuca7/OpenScapeUcSuiteApps-BasePackage-V7R1.0.0130d000.iso
performing cleanup....
cleanup successfully done
using Loop device /dev/loop8
Splitrepository "addlang" integrated
Splitrepository "base" integrated
Splitrepository "zh" integrated
Splitrepository "en" integrated
Splitrepository "fr" integrated
Splitrepository "de" integrated
Splitrepository "it" integrated
Splitrepository "opt" integrated
Splitrepository "meta" integrated
Repository created successfully
removing all registered repositories
register new repository...done
CreateRepository end
Logfile: /var/log/OpenScapeUC/osc-setup-2012-1203_16:50:09.log
16. You can have the list of repositories registered in the osc-setup (not zypper!)
put out for checking purposes:
osc-setup lr
Example output:
A31003-S5070-J100-12-7631, 02/2013
241
Installation
17. Continue with one of the following sections:
242
Section 5.3.2, Installing the Small Deployment, on page 263
Section 5.3.3, Installing the Large Deployment, on page 281
Section 5.3.4, Installing the Very Large Deployment, on page 314
A31003-S5070-J100-12-7631, 02/2013
Installation
5.3.1.3 Creating a Repository in osc-setup by using remote

Installation Sources
There are two possibilities to remotely provide the ISO files as a repository in oscsetup:
Using NFS
The ISO files are provided in a directory on the source computer, this
directory is mounted via the network to the target computer by using NFS and
a linked repository in osc-setup is created on the target computer.
NOTE: This option is recommended.
Advantages:
osc-setup only must be installed on the target computer. No osc-setup

or repository (neither in zypper nor in osc-setup) is needed on the
source computer.
There is no need to create an exported repository (-e option) in oscsetup which would be more time consuming since depending on the
number of needed ISO files gigabytes of data might need to be
copied. However, you have the option to create an exported
repository instead, if you want to.
Disadvantages:
The NFS server must be installed on the source computer and the
NFS client must be installed on the target computer.
Port 111 (RPC), port 2049 (NFS) and a dynamic port for
RPC.MOUNTD must be open on the source computer and on the
target computer.
Using HTTP
A persistent repository in osc-setup is created on the source computer and is
accessed remotely from the target computer by using HTTP.
Advantages:
An exported repository must be used on the source computer, i. e. it

still is available if this computer rebooted. However, using NFS could
create an exported repository as well.
Only port 80 must be open the source computer and the target
computer.
No installation of NFS server and NFS client needed.
A31003-S5070-J100-12-7631, 02/2013
243
Installation
Disadvantages:
An exported repository (-e option) in osc-setup must be created on

the source computer. Creating an exported repository is much more
time cosuming than creating a linked repository (-l option) or a
repository without option.
osc-setup must be installed on the source computer and the target

computer.
It might be necessary to change the Apache server configuration on

the source computer. See the Apache server documentation for
details.
The source computer is the computer where the ISO installation files (using NFS)
or the repository (using HTTP) is provided. This computer can be the backend
computer of the OpenScape UC Application but it can be as well any SLES 11
computer in the network.
The target computer is the computer where the repository in osc-setup should be
provided and used for installing components of the OpenScape UC Application.
This computer can be the backend computer of the OpenScape UC Application,
the mobile client faade server computer, a front-end computer, a media server
computer or the instant-messaging (Openfire server) computer.
If you want to use NFS, continue with sub-section Option 1: Using NFS for
accessing ISO files on page 245. If you want to use HTTP, continue with subsection Option 2: Using HTTP for accessing a persistent repository on page 258.
244
A31003-S5070-J100-12-7631, 02/2013
Installation
Option 1: Using NFS for accessing ISO files

The following steps describe how to make ISO files available on the source
computer in order to create a repository on the target computer.
Execute the following steps on the source computer:
1. Copy the ISO files into the directory to be shared.
NOTE: Note down this directory, e. g. /tmp/shi/osuca7.
2. Check whether the nfs-kernel-server RPM and the yast2-nfs-server RPM are
installed on the source computer:
zypper se match-any nfs
Example output:
S | Name
| Summary
| Type
--+-----------------------+-----------------------------------------+----------i | limal-nfs-server
| LiMaL--NFS Server Library
| package
| limal-nfs-server
| srcpackage
i | limal-nfs-server-perl | LiMaL--NFS Server Library Perl Bindings | package
i | nfs-client
| Support Utilities for NFS
| package
i | nfs-doc
| package
i | nfs-kernel-server
| Support Utilities for Kernel nfsd
| package
| nfs-utils
| srcpackage
i | nfsidmap
| NFSv4 ID Mapping Library
| package
| nfsidmap
| srcpackage
| quota-nfs
| Disk Quota System on NFS
| package
| sblim-cmpi-nfsv3
| SBLIM CMPI NFSv3 Instrumentation
| package
| sblim-cmpi-nfsv3
| srcpackage
| sblim-cmpi-nfsv4
| package
| sblim-cmpi-nfsv4
| srcpackage
i | yast2-nfs-client
| YaST2 - NFS Configuration
| package
| yast2-nfs-client
| srcpackage
i | yast2-nfs-common
| YaST2 - NFS Configuration, common parts | package
i | yast2-nfs-server
| YaST2 - NFS Server Configuration
| package
| yast2-nfs-server
| srcpackage
The i in the first column indicates that the RPM in that line is installed.
If the nfs-kernel-server RPM and the yast2-nfs-server RPM are not installed,
install them:
zypper in nfs-kernel-server yast2-nfs-server
NOTE: You need the SLES 11 DVD in the DVD drive for this action.
A31003-S5070-J100-12-7631, 02/2013
245
Installation
3. Start YaST:
yast
4. Open Network Services > NFS Server.
246
A31003-S5070-J100-12-7631, 02/2013
Installation
5. Activate the check box Start in the NFS Server area.
6. Select the Next button.
A31003-S5070-J100-12-7631, 02/2013
247
Installation
7. Select Add Directory in the Directories to Export area.
8. Enter the absolute path to the ISO installation files into the Directory to
Export field, e. g. /tmp/shi/osuca7.
248
A31003-S5070-J100-12-7631, 02/2013
Installation
9. Select OK.
10. Select OK without changing the default value in the Host Wild Card field.
A31003-S5070-J100-12-7631, 02/2013
249
Installation
11. Select Finish.

NOTE: This action changes the /etc/exports file.
12. Select Quit.
13. Execute the more /etc/exports command to see the current contents of
the changed file.
Example output:
/tmp/shi/osuca7*(fsid=0,crossmnt,ro,root_squash,sync,no_subtree_check)
14. Ensure that the following default ports NFS uses are open on the source
computer (see Section 6.1, Lists of the Ports to be opened, on page 359):
a) RPC, (port 111, UDP and TCP)
b) NFS, (port 2049, UDP and TCP)
c) RPC.MOUNTD, (dynamic port, UDP and TCP)
250
A31003-S5070-J100-12-7631, 02/2013
Installation
Execute the following steps on the target computer:

15. Ensure that the following default ports NFS uses are open on the target
16. The directory on the source computer containing the ISO installation files will
be mounted to a local directory on the target computer. Ensure that this local
directory exist. If it does not exist yet, create it.
Example:
mkdir /tmp/shi/osuca7Net
17. Check whether the nfs-client RPM and the yast2-nfs-client RPM are installed
on the target computer:
zypper se match-any nfs-client
Example output:
S | Name
| Summary
| Type
--+------------------+---------------------------+----------i | nfs-client
| Support Utilities for NFS | package
i | yast2-nfs-client | YaST2 - NFS Configuration | package
| yast2-nfs-client | YaST2 - NFS Configuration | srcpackage
If the nfs-client RPM and the yast2-nfs-client RPM are not installed, install
them:
zypper in nfs-client yast2-nfs-client
A31003-S5070-J100-12-7631, 02/2013
251
Installation
18. Start YaST:

yast
19. Open Network Services > NFS Client.
252
A31003-S5070-J100-12-7631, 02/2013
Installation
20. Select Add.
A31003-S5070-J100-12-7631, 02/2013
253
Installation
21. Edit the following fields:

a) NFS Server Hostname: Enter the IP address, host name or FQDN of the
source computer, e. g. myOsuca.
NOTE: You might want to use the Choose option to find computers with
shared directories in the network.
254
A31003-S5070-J100-12-7631, 02/2013
Installation
b) Remote Directory: Enter the path of the ISO files on the source
computer, e. g. /tmp/shi/osuca7.
A31003-S5070-J100-12-7631, 02/2013
255
Installation
c) Mount Point (local): Enter the path of the directory on the target
computer where the ISO files on the source computer should be
mounted, e. g. /tmp/shi/osuca7Net.
NOTE: If the target computer is rebooted, the mount point is mounted as

well. If the target computer is rebooted and the NFS server on the source
computer is not reachable, the boot time of the target computer increases
significantly and the mount directory on the target computer is not
mounted.
256
A31003-S5070-J100-12-7631, 02/2013
Installation
22. Select OK.
23. Select OK.

24. Select Quit.
25. Check the mount point:
mount
Example output:
10.11.12.13:/tmp/shi/osuca7 on /tmp/shi/osuca7Net type nfs (rw,addr=10.11.12.13)
In this example, 10.11.12.13 is the IP address of the source computer.
26. Now, the ISO files are available on the target computer as if they would exist
in the local directory indicated by the mount point, e. g. /tmp/shi/
osuca7Net. Execute the instructions in Section 5.3.1.2, Creating a
Repository in osc-setup by using local Installation Sources, on page 237 with
this directory as <path to ISO file>.
A31003-S5070-J100-12-7631, 02/2013
257
Installation
Option 2: Using HTTP for accessing a persistent repository

Creating a repository in osc-setup on the source computer
1. Copy the ISO files into a directory (<path to ISO file>) on the source
2. Check whether the directory where the persistent repository should be
created (<path to persistent repository>) already exits. If not,
create it:
Example:
mkdir /software/persRepo
NOTE: Do not create the persRepo directory in the /tmp directory since a
persistent repository should be created and /tmp might be emptied during a
reboot of the computer.
3. Determine the directory (<apache path to repository>) on the source
computer that should be reachable by using HTTP via the network and that
should allow access to the repository. The Apache server configuration might
need to be configured for this purpose. See the Apache server documentation
for details.
4. Create a persistent repository in osc-setup on the source computer
according to Section 5.3.1.2, Creating a Repository in osc-setup by using
local Installation Sources, on page 237 without step 17 on page 242 by using
the directory stated above and the ISO file(s) you want to provide.
I. e. the actual repository is e. g. created by executing the following
command:
osc-setup cr -e <path to persistent repository> -b <path to ISO file>/OpenScapeUcSuiteAppsRepository-<version>.iso
IMPORTANT: The e option is a must to create a persistent repository. You
must not use no option or the l option.
Example
osc-setup cr -e /software/persRepo -b /tmp/shi/osuca7/OpenScapeUcSuiteApps-RepositoryV7R1.0.0-130000.iso
NOTE: This step might be time consuming since depending on the number
of used ISO files gigabytes of data have to be copied.
258
A31003-S5070-J100-12-7631, 02/2013
Installation
5. Ensure that port 80 (HTTP protocol) is open on the source computer and on
the target computer.
Creating a repository in zypper on the target computer
in zypper:
zypper lr
Example output:
:
# | Alias
--+-----------------------------------------------------------+------+---------+-------1 | SUSE-Linux-Enterprise-Server-11-SP2 11.2.2-1.234 | SUSE-Linux-Enterprise-Server-11-SP2 11.2.2-1.234 | Yes
| No

command:
zypper rr <number>
output.
Example of <URI>:
http://<Name of the source computer>/<apache path to repository>
Complete example:
zypper ar http://myOsuca//persRepo ucapp
zypper lr
# | Alias
--+------------------------------------+----------------------------+---------+-------1 | SUSE-Linux-Enterprise-Server-11--SP2 11.2.2-1.234 | SUSE-Linux-Enterprise-Server11--SP2 11.2.2-1.234 | Yes
| No
2| ucapp
| ucapp
| Yes
| No
A31003-S5070-J100-12-7631, 02/2013
259
Installation
correctly:
zypper ref
Example output:
Repository: ucapp
260
A31003-S5070-J100-12-7631, 02/2013
Installation
zypper in osc-setup
in zypper:
zypper lr
zypper rr <number>
output.
NOTE: You can also use command rpm -q osc-setup as alternative to
the command described here.
zypper se osc-setup
Example output:
S | Name
| Summary
| Type
osc-setup lr
A31003-S5070-J100-12-7631, 02/2013
261
Installation
Adding the remote repository in osc-setup

19. The repository on the source computer can be added to osc-setup on the
target computer:
osc-setup ar http://<Name of the source computer>/<apache path to repository>
Complete example:
osc-setup ar http://myOsuca/persRepo
20. Continue with one of the following sections:
262
A31003-S5070-J100-12-7631, 02/2013
Installation
5.3.2 Installing the Small Deployment

Installation
NOTE: When you execute the following command, all top level installation
packages of all deployment scenarios are displayed among other things:
zypper se --match-any OpenScapeUC_

The output reads e.g. as follows:
S | Name
| Summary
| Type
--+----------------------------------+-----------------------------------+-------...
| OpenScapeUC_IntegratedSimplex
| OpenScape UC - IntegratedSimplex
| package
...
| OpenScapeUC_Large_BE
| OpenScape UC - Large(BE)
| package
| OpenScapeUC_Large_FE
| OpenScape UC - Large(FE)
| package
| OpenScapeUC_Large_MS
| OpenScape UC - Large (MS)
| package
...
| OpenScapeUC_ProductVersion
| OpenScape UC - ProductVersion
| package
| OpenScapeUC_Small
| OpenScape UC - Small
| package
| OpenScapeUC_StandardDuplexSmall | OpenScape UC - StandardDuplexSmall | package
| OpenScapeUC_VeryLarge_BE
| OpenScape UC - VeryLarge(BE)
| package
| OpenScapeUC_VeryLarge_FE
| OpenScape UC - VeryLarge(FE)
| package
| OpenScapeUC_VeryLarge_MS
| OpenScape UC - VeryLarge (MS)
| package
...
1. Enter the following command on the application computer to start the setup.
With a connection to OpenScape Voice:

osc-setup in OpenScapeUC_StandardDuplexSmall
With a connection to HiPath 4000:

osc-setup in OpenScapeUC_Small
NOTE: OpenScapeUC_StandardDuplexSmall comprises

OpenScapeUC_Small and the Voice Assistant.
OpenScapeUC_StandardDuplexSmall is only used with a connection to
an OpenScape Voice, while OpenScapeUC_Small is only used with a
connection to a HiPath 4000.
2. In case of an error, always select the option with despite the inferior
architecture.
Example:
A31003-S5070-J100-12-7631, 02/2013
263
Installation
Problem: OpenScapeUC_StandardDuplexSmall-6.0_1.0.0-007.noarch requires OpenScapeUC_Small,

but this requirement cannot be provided
uninstallable providers: OpenScapeUC_Small-6.0_1.0.0007.noarch[270fc4d9389754e36bb4dbe2a725408d]
Solution 1: Following actions will be done:
install symphonia-6.0_1.5.0-058.i586 despite the inferior architecture
install symphonia-jre-ibm-6.0.9.2-4.i386 despite the inferior architecture
Solution 2: do not install OpenScapeUC_StandardDuplexSmall-6.0_1.0.0-007.noarch
Solution 3: break OpenScapeUC_StandardDuplexSmall by ignoring some of its dependencies
Choose from above solutions by number or cancel [1/2/3/c] (c):
3. Enter 1.
4. Push the y key and conclude with the return key.
NOTE: Executing this step takes some time.
5. You can chain several osc-setup in invocations to execute them
automatically in succession. For example, with a connection to an
OpenScape Voice, you may execute the automatic installation of
the OpenScape UC Application for Small Deployment,
South African English and Spanish for telephone prompts,
German and Spanish for the voice portal,
the German language package and the Brazilian language package for
the TTS engine,
the OpenBranch Assistant,
the CLM,
the Office Communicator Connector and
the connector for the HiPath User Management
. The command for this reads:

osc-setup in OpenScapeUC_StandardDuplexSmall mediaserver_announcements_en_za
mediaserver_announcements_es mediaserver_voiceportal_languagepack_DE-DE
mediaserver_voiceportal_languagepack_ES-ES uc-tts-de_de uc-tts-pt_br OpenBranchAssistant
CLM scs_osc_officecommunicator_be scs_provisioning-hpum
264
A31003-S5070-J100-12-7631, 02/2013
Installation
IMPORTANT: The lines of the example command are wrapped in this

documentation. When applying an osc-setup invocation make sure that no
line breaks occur in the command.
NOTE: Be sure to write commands and parameters correctly. Check whether

the languages to be installed are available in the installation repository
provided to the osc-setup.
NOTE: Interactive user queries are not automatically answered.

6. There are the following options for checking whether a specific RPM has
been installed:
zypper se --match-any <part of the RPM name>

Example:
Example output:

S | Name
| Summary
| Type
--+----------------------------------+-----------------------------------+-------...
i | OpenScapeUC_ProductVersion
| package
i | OpenScapeUC_Small
| package
i | OpenScapeUC_StandardDuplexSmall | OpenScape UC - StandardDuplexSmall | package
i | OpenScapeUC_frida_Small
| OpenScape UC - Fexible Installabl->| package
...
The i in the first column marks installed packages.
rpm -qa | grep <part of the RPM name>

or
rpm -q <RPM name>
Example:
rpm -qa | grep OpenScapeUC_
Example output:
OpenScapeUC_ProductVersion-7_0.0.0-080000
OpenScapeUC_frida_Small-6.0_1.0.0-021
OpenScapeUC_Small-6.0_1.0.0-021
OpenScapeUC_StandardDuplexSmall-6.0_1.0.0-021
osc-setup se <RPM name>
A31003-S5070-J100-12-7631, 02/2013
265
Installation
See Section B.5, yast instead of zypper se or rpm -q, on page 1060.
7. If you want to perform a connection to a HiPath 4000, you must install an

additional RPM:
osc-setup in OpenScapeUC_4kaddons
8. Check for a newer OpenScape UC Application hotfix version and install it
according to the corresponding version notes if applicable.
266
A31003-S5070-J100-12-7631, 02/2013
Installation
Adding optional applications

IMPORTANT: To process voicemails with the OpenScape UC Application, the
OpenScape UC Application must be connected to either
- a groupware (Microsoft Exchange or Lotus Domino,
see Chapter 13, Groupware Connection),
- OpenScape Xpressions (see the OpenScape
Xpressions setup guide) or
- another voicemail solution.
9. Execute the following command, for example, to list further available

applications that carry clm, office, OpenBranch or hpum in their names:
zypper se --match-any clm office OpenBranch hpum
The following is put out for example:
S | Name
| Summary
| Type
--+-------------------------------+--------------------------------+-------| CLM
| Customer License Manager
| package
i | OpenBranchAssistant
| OpenScape Branch Assistant
| package
| scs_osc_officecommunicator_be | Officecommunicator Integration | package
| scs_provisioning-hpum
| SCS - Provisioning HPUM
| package
10. If you want to install the CLM, for example, enter the following command:
osc-setup in CLM
If you want to install e. g. the Office Communicator Connector (see Chapter
11, Connecting the Microsoft Office Communication Server/Microsoft Lync
Server), enter the following command:
osc-setup in scs_osc_officecommunicator_be
NOTE: If you want to align the presence status of users between the
Microsoft Office Communication Server/Microsoft Lync Server and the
OpenScape UC Application, the connection from the Microsoft Office
Communication Server/Microsoft Lync Server to the OpenScape UC Application is needed. See the OpenScape UC Application Planning Guide for
details.
If you wish to install the Openfire server (Instant Messaging) (see Chapter 12,
Connecting Instant Messaging) e. g. on the application computer, use the
following command to check whether the RPM symphonia-jre-ibm is
installed:
zypper se --match-any symphonia-jre-ibm
A31003-S5070-J100-12-7631, 02/2013
267
Installation

S | Name
| Summary
| Type
--+-------------------------+-------------------------------+-------i | symphonia-jre-ibm
| Symphonia Framework - jre-ibm | package
| symphonia-jre-ibm-64bit | Symphonia Framework - jre-ibm | package
The output must feature an i in the first column. If not, install this RPM:
osc-setup in symphonia-jre-ibm
Then enter the following command:
osc-setup in symphonia-openfire-base symphonia-openfire
IMPORTANT: You may install either only
scs_osc_officecommunicator_be or only symphonia-openfirebase and symphonia-openfire. You may not install the Office Communicator Connector and the Openfire server.
NOTE: Connecting IBM Lotus Sametime is not supported.

Enter the following command if you want to install e.g. a connector for the
HiPath User Management (HPUM):
osc-setup in scs_provisioning-hpum
If you want to import user data, passwords or contacts from an LDAP directory
to the OpenScape UC Application via SPML (Service Provisioning Markup
Language), you can do this on a Windows or SLES computer. On SLES, you
must execute before the following command:
osc-setup in scs_provisioning-ldapprov<version>
In the /opt/siemens/servicetools/ldapprovisioning/ directory,
the ldapprov.sh file and the following subdirectories are created:
com
This directory contains the sources for the ID Mapper which maps the
LDAP ID to determined fields.
configurations
This directory is not required for the execution of the LDAP provisioning,
but is contains configuration file samples.
lib
This directory contains required components of the DirX Identity Light
Frameworks.
268
A31003-S5070-J100-12-7631, 02/2013
Installation
Refer to the programming guide OpenScape UC Application SPML SDK for

further details on SPML use.
If you want to install the OpenStage Client, execute the following command:
rpm -i CA2-OSIPP-STANDARD-<version>.rpm
If you want to install the OpenStage Client for Integrated Deployment, use the
following command instead:
rpm -i CA2-OSIPP-STANDARD-<version>.rpm --prefix=/enterprise
Copy the file CA2-OSIPP-STANDARD-<version>.rpm from the i586
directory of the installation repository e. g. to the /tmp directory of the
computer and execute the RPM command in this directory.
Example of the full name of the RPM package:
CA2-OSIPP-STANDARD-3.2_4.0.0-39.27668.i586.rpm
If you want to connect the OpenScape UC Application to OpenScape
Xpressions, enter the following command:
osc-setup in OpenScapeUC_xpraddons
This RPM installs optional components in the CMP for administering the
connection of the OpenScape UC Application to OpenScape Xpressions and
new features in the user management for creating new Xpressions resources
in a user-centered view.
A31003-S5070-J100-12-7631, 02/2013
269
Installation
Adding optional languages

The default installation up to and including step 4 on page 264 sets up only the
basic language English for the voice portal, media server telephone prompts and
the Nuance TTS. If you wish to install further languages, execute the following
steps:
11. Verify that the installation files (ISO files) you require for the languages you
wish to install are registered in osc-setup.
The tables in the ensuing steps show which ISO files you require for the
respective language. Table 8 on page 235 provides an overview of all
available ISO files. Section 5.3.1, Providing the Installation Sources in an
Installation Repository in osc-setup, on page 234 contains information about
the steps required for providing an ISO file in osc-setup.
12. Execute the following command to list the available languages:
zypper se --match-any announ uc-tts uc-asr languagepack
S | Name
| Summary
| Type
--+--------------+--------------------------------------------------------------+-------| mediaserver_announcements_ar | Mediaserver_announcements_ar
| package
| mediaserver_announcements_bg | Mediaserver_announcements_bg
| package
...
i | mediaserver_announcements_en_us | Mediaserver_announcements_en_us
| package
| mediaserver_announcements_en_za | Mediaserver_announcements_en_za
| package
...
| mediaserver_autoattendant_languagepack_DE-DE|
| mediaserver_autoattendant_languagepack_EN-GB|
i | mediaserver_autoattendant_languagepack_EN-US|
package
| mediaserver_autoattendant_languagepack_ES-ES|
package
Mediaserver AutoAttendant La->| package

Mediaserver AutoAttendant La-> |
...
|
|
i |
|
...
mediaserver_voiceportal_languagepack_DE-DE
mediaserver_voiceportal_languagepack_EN-GB
mediaserver_voiceportal_languagepack_EN-US
mediaserver_voiceportal_languagepack_ES-ES
|
|
|
|
Mediaserver
Mediaserver
Mediaserver
Mediaserver
VoicePortal
VoicePortal
VoicePortal
VoicePortal
->|
->|
->|
->|
package
package
package
package
| mediaserver_voiceportalspeech_languagepack_DE-DE | Mediaserver VoicePortalS->|

package
i | mediaserver_voiceportalspeech_languagepack_EN-US | Mediaserver VoicePortalS->|
package
...
| scs_conferencing_languagepack_en_gb
i | scs_conferencing_languagepack_en_us
| scs_conferencing_languagepack_es_es
...
270
| Conferencing Languagepac->| package

A31003-S5070-J100-12-7631, 02/2013
Installation
i |
|
i |
i |
...
uc-asr
uc-asr-de_de
uc-asr-en_us
uc-asrcore
|
|
|
|
Meta rpm to install all A->|

German speech recogniti-> |
American English speech -> |
Meta rpm to install Nua-> |
package
package
package
package
i |
|
|
i |
...
|
i |
uc-tts
uc-tts-de_de
uc-tts-en_gb
uc-asr-en_us
|
|
|
|
Meta rpm to install all ->

German tts voice.
British English tts voice.
American English speech ->
package
package
package
package
uc-tts-zh_cn
uc-ttscore
| Chinese Mandarin tts voi-> | package

| Meta rpm to install Nuan-> | package
|
|
|
|
NOTE: The i in the first column marks packages already installed.

13. Installing additional signaling tones and languages of the announcement
texts for the PBX
Execute the following command for installing another language for phone
prompt texts:
osc-setup in mediaserver_announcements_<language code>
Example:
osc-setup in mediaserver_announcements_en_za
NOTE: This language is used for the media server announcements provided
for the PBX.
You can install several languages by one command.
Example:
osc-setup in mediaserver_announcements_en_za mediaserver_announcements_es_es
An individual language package is supplied with the media server for every
supported country. Such a language package always contains the countryindividual signaling tones. Whether a language package also contains
country-individual system announcements depends on the respective
language package and thus on the respective country.
If a language package is installed for a language code on the media server
that contains individual tones as well as the individual system
announcements of the relevant country, the media server can automatically
play the signaling tones and system announcements of the respective
country. The "tone language" and announcement language correspond in this
case to the language code that the PBX invokes.
A31003-S5070-J100-12-7631, 02/2013
271
Installation
If the language package contains only the individual signaling tones of the
relevant country, the media server can only access the associated signaling
tones. So that system announcements can also be played for the relevant
language, you need to configure from which alternative language package
the media server is to use the system announcements. The announcement
language of this alternative language package is called fallback language.
The "tone language", in turn, corresponds in this case to the language code
that the PBX invokes; the announcement language does not it corresponds
to the fallback language.
The media server thus always uses the signaling tones of the language
package defined by the language code.
Consequently: The language package that corresponds to the required
signaling tone schema must always be installed in the media server for a
defined language code. The media server would otherwise play incorrect
tones. For example, the language package Spanish (Mexico) (es_mx) might
well be useful for some companies in the US; nonetheless it must not be used
outside of Mexico, because the media server would play signaling tones
specific to the country Mexico. These tones, however, are different from those
used in the US.
The following table provides information about the media server's country and
language support:
Column Country: Country for which the media server provides a

language package
Column Language: Announcement language
Column Language Code: Code under which the country-individual

language package is managed in the media server
Example: en_us in the package name
mediaserver_announcements_en_us
NOTE: The language package associated to a country must always be
installed in the media server. Only then will the media server play
signaling tones correct for the respective country
272
Column Individual System Announcement: Indicates whether a

language package contains country-individual system announcements
besides the signaling tones
Column Pre-configured Fallback Language: Lists the system

announcements of an alternative language recommended for
configuration if a language package does not contain any system
announcements itself. The specified alternative languages have already
been pre-set as fallback languages in the media server default settings.
Column ISO File: Partial name of the ISO file that contains the language.
A31003-S5070-J100-12-7631, 02/2013
Installation
Country
Language
Argentina
Australia
Brazil
Belgium
Bulgaria
BosniaHerzegovina
Chile
People's Republic
of China
Denmark
Germany
Ecuador
Estonia
Finland
France
Greece
Great Britain
Hongkong
India
Indonesia
Italy
Japan
Canada
Colombia
Korea
Croatia
Latvia
Lithuania
Malaysia
Morocco
Mexico
Netherlands
Norway
Austria
Peru
Philippines
Poland
Portugal
Romania
Russia
Sweden
Serbia
Spanish (Argentina)
English (AU)
Portuguese (Brazil)
Flemish
Bulgarian
Bosnian
Language Individual
Code
System
Announcements
es_ar
en_au
pt_br
nl_be
bg
bs
Spanish (Chile)
Chinese (simplified)
es_cl
zh
Danish
German
Spanish (Ecuador)
Estonian
Finnish
French
Greek
English (UK)
Chinese (Hongkong)
English (India)
Indonesian
Italian
Japanese
French (Canada)
Spanish (Colombia)
Korean
Croatian
Latvian
Lithuanian
Malay
French
Spanish (Mexico)
Dutch
Norwegian
German
Spanish (Peru)
English (Philippines)
Polish
Portuguese (Portugal)
Romanian
Russian
Swedish
Serbian
da
de
es_ec
et
fi
fr
el
en
zh_hk
en_in
id
it
Yes
fr_ca
es_co
ko
hr
lv
lt
ms
fr_ma
es_mx
nl
no
de_at
es_pe
en_ph
pl
pt
ro
ru2
sv
sr
Table 10
Pre-configured
Fallback
Language
en
nl
sr
es_ar
es_mx
en_us
en
en_us
en_us
es_mx
en_us
en
en_us
fr
de
en_mx
en_us
ISO File1
Spanish
English
Portuguese
AdditionalLanguages
AdditionalLanguages
AdditionalLanguages
Spanish
Chinese
AdditionalLanguages
German
Spanish
AdditionalLanguages
AdditionalLanguages
French
AdditionalLanguages
English
Chinese
English
AdditionalLanguages
Italian
AdditionalLanguages
French
Spanish
AdditionalLanguages
AdditionalLanguages
AdditionalLanguages
AdditionalLanguages
AdditionalLanguages
French
Spanish
AdditionalLanguages
AdditionalLanguages
German
Spanish
English
AdditionalLanguages
Portuguese
AdditionalLanguages
AdditionalLanguages
AdditionalLanguages
AdditionalLanguages
Supported Languages for Announcement Texts of the Media Server for PBXs
A31003-S5070-J100-12-7631, 02/2013
273
Installation
Country
Language
Singapore
Slovakia
Slovenia
Spain
South Africa
Taiwan
Thailand
Czech Republic
Turkey
Hungary
USA
Venezuela
United Arab
Emirates
Vietnam
Chinese (Singapore)
Slovakian
Slovenian
Spanish
English (ZA)
Chinese (Taiwan)
Thai
Czech
Turkish
Hungarian
English (US)
Spanish (Venezuela)
Arabian
Language Individual
Code
System
Announcements
zh_sg
sk
sl
es
en_za
zh_tw
th
cs
tr
hu
en_us
es_ve
ar
Vietnamese
vi
Table 10
Pre-configured
Fallback
Language
en_us
en
en_us
en_us
es_mx
en_us
ISO File1
Chinese
AdditionalLanguages
AdditionalLanguages
Spanish
English
Chinese
AdditionalLanguages
AdditionalLanguages
AdditionalLanguages
AdditionalLanguages
English
Spanish
AdditionalLanguages
AdditionalLanguages
1 This table indicates only part of the ISO file name that distinguishes the ISO files of an OpenScape UC Application setup medium, thus for
example English instead of OpenScapeUcSuiteApps-English-V7R1.0.0-130000.iso. In Table 8 on page 235 you find the list of all available
ISO files.
2 In order to use cyrillic letters in mail notifications for missed calls, ensure that the parameter Mail.Charset in the file /opt/siemens/
HiPathCA/config/services/default/JMailService/JMailService.cfg is set to the value iso-8859-5.
14. Installing additional Voice Portal Languages

Execute the following command for installing another language for the voice
portal (announcement texts for the OpenScape UC Application):
osc-setup in mediaserver_voiceportal_languagepack_<language code>
Example:
osc-setup in mediaserver_voiceportal_languagepack_DE-DE
Example:
osc-setup in mediaserver_voiceportal_languagepack_DEDE mediaserver_voiceportal_languagepack_ES-ES
You can obtain the supported language codes for voice portal languages from
the following table.
Language
Chinese (Mandarin)
German
English
English
Table 11
274
Country
China
Germany
Great Britain
USA
Language Code
ZH_CN
DE_DE
EN_GB
EN_US
ISO File1
Chinese
German
English
English
Language Codes of the supported Voice Portal Languages
A31003-S5070-J100-12-7631, 02/2013
Installation
Language
French
Italian
Portuguese
Portuguese
Russian
Country
France
Italy
Portugal
Brazil
Russia
Language Code
FR_FR
IT_IT
PT_PT
PT_BR
RU_RU2
Spanish
Spain
ES_ES
Table 11
ISO File1
French
Italian
Portuguese
Portuguese
AdditionalLa
nguages
Spanish
1 This table indicates only part of the ISO file name that distinguishes the ISO files of an
OpenScape UC Application setup medium, thus for example English instead of
OpenScapeUcSuiteApps-English-V7R1.0.0-130000.iso. In Table 8 on page 235 you find the list
of all available ISO files.
2 In order to use cyrillic letters in mail notifications for missed calls, ensure that the parameter
Mail.Charset in the file /opt/siemens/HiPathCA/config/services/default/
JMailService/JMailService.cfg is set to the value iso-8859-5.
15. Installing additional Auto Attendant languages

Execute the following command for installing another Auto Attendant
language:
osc-setup in mediaserver_autoattendant_languagepack_<language code>
Example:
osc-setup in mediaserver_autoattendant_languagepack_IT_IT
The following languages are supported: US English has already been
installed by default.
Language
Chinese (Mandarin)
German
English
English
French
Italian
Portuguese
Portuguese
Russian
Country
China
Germany
Great Britain
USA
France
Italy
Portugal
Brazil
Russia
Language Code
ZH_CN
DE_DE
EN_GB
EN_US
FR_FR
IT_IT
PT_PT
PT_BR
RU_RU2
Spanish
Spain
ES_ES
Table 12
ISO File1
Chinese
German
English
English
French
Italian
Portuguese
Portuguese
AdditionalLa
nguages
Spanish
Language Codes of the supported Auto Attendant Languages
16. Installing the voice conference languages

A31003-S5070-J100-12-7631, 02/2013
275
Installation
Execute the following command for installing another voice conference

language:
osc-setup in scs_conferencing_languagepack_<language code>
Example:
osc-setup in scs_conferencing_languagepack_it_it
The following languages are supported: American English is installed by
default.
Language
Chinese (Mandarin)
German
English
English
French
Italian
Portuguese
Portuguese
Spanish
Dutch
Country
China
Germany
Great Britain
USA
France
Italy
Portugal
Brazil
Spain
Netherlands
Language Code
zh_cn
de_de
en_gb
en_us
fr_fr
it_it
pt_pt
pt_br
es_es
nl_nl
Russian
Russia
ru_ru2
Turkish
Turkey
tr_tr
Table 13
ISO File1
Chinese
German
English
English
French
Italian
Portuguese
Portuguese
Spanish
AdditionalLangu
ages
AdditionalLangu
ages
AdditionalLangu
ages
Language Codes of the supported Conferencing Languages
17. Installing additional TTS languages

IMPORTANT: The media server supports IPv4 as well as IPv6. If you use
TTS or ASR, the media server must be available under an IPv4 address and
at least one IPv4 streaming route must have been configured in the media
server. You can obtain details from the administrator documentation
Execute the following command for installing another language for the
Nuance TTS:
osc-setup in uc-tts-<language code>
Example:
osc-setup in uc-tts-de_de
276
A31003-S5070-J100-12-7631, 02/2013
Installation

default.
Language
Chinese (Mandarin)
German
English
English
French
Italian
Portuguese (Brazil)
Russian
Country
China
Germany
Great Britain
USA
France
Italy
Portugal
Brazil
Russia
Language Code
zh_cn
de_de
en_gb
en_us
fr_fr
it_it
pt_pt
pt_br
ru_ru2
Spanish
Spain
es_es
Table 14
ISO File1
Chinese
German
English
English
French
Italian
Portuguese
Portuguese
AdditionalLan
guages
Spanish
Language Codes of the supported TTS Languages
1 This table indicates only part of the ISO file name that distinguishes the ISO files of an OpenScape
UC Application setup medium, thus for example English instead of OpenScapeUcSuiteAppsEnglish-V7R1.0.0-130000.iso. In Table 8 on page 235 you find the list of all available ISO files.

Example:
osc-setup in uc-tts-pt_br uc-tts-zh_cn
18. Installing additional ASR languages
Execute the following command for installing German as another language
for the automatic speech recognition (Nuance ASR):
osc-setup in uc-asr-de_de
This is the only ASR language which can be installed in addition to the
language installed by default US English.
Language
German
English
Table 15
Country
Germany
USA
Language Code
de_de
en_us
ISO File1
German
English
Language Codes of the supported ASR Languages
A31003-S5070-J100-12-7631, 02/2013
277
Installation
An ASR language must be installed with the following command to make it

available to the voice portal.
osc-setup in mediaserver_voiceportalspeech_languagepack-DE_DE
Language
German
English
Table 16
Country
Germany
USA
Language Code
DE_DE
EN_US
ISO File1
German
English
Language Codes of the supported Voiceportalspeech Languages
Deleting the repository

Execute the steps in this sub-section if you do not wish to install an RPM package
of the OpenScape UC Application anymore.
19. Delete the provision of the repository.
osc-setup cr --clean
Example output:
checking Arguments
Option clean: yes
removing old Repositorydir
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Remove Loop-Device "/dev/loop8"
278
A31003-S5070-J100-12-7631, 02/2013
Installation

20. Delete the directory of the temporary repository you created in step 14 on
page 240.
rm -R <path to the temporary repository>
Example:
rm -R /tmp/tmpRepo
A31003-S5070-J100-12-7631, 02/2013
279
Installation
Start
IMPORTANT: Ensure that all workarounds described in the Release Notes were
executed before you start the OpenScape UC Application for the first time. If you
do not perform these workarounds the system may adopt a defective state.
NOTE: When executing the following commands, verify that they are executed
by user root.
Perform the following steps:
If you have to stop these services later on, execute the following command:
/etc/init.d/NSSservice stop
22. Enter the following command for starting the OpenScape UC Application:
NOTE: You find information about the /var/siemens/common/log/
osgi.err and /var/siemens/common/log/osgi.log files and about
how to check whether the OpenScape UC Application system start was
successful in Section 5.4, Checking the Installation, on page 347.
If you need to end it at a later date, execute the following command:
Language), you can do this on a Windows or SLES computer. On SLES,
execute the following command:
/opt/siemens/servicetools/ldapprovisioning/ldapprov.sh <configuration_file>
If required, execute this command with different XML configuration files. In
the configurations subdirectory, you will find some configuration
examples. For further details, refer to the programming guide OpenScape UC
Application SPML SDK.
280
A31003-S5070-J100-12-7631, 02/2013
Installation
5.3.3 Installing the Large Deployment

IMPORTANT: Check if the system time of all OpenScape UC Application-related
computers is synchronized with a maximum difference of one second.
If the system time difference between the computers and the telephones exceeds
one second, contact the IT person responsible for the network and request that
the system time be synchronized. The Network Time Protocol (NTP) is often used
for synchronizing the system time (see Section 3.1.9.2, Configuring the NTP
Service, on page 66).
5.3.3.1 Installation on the Application Computer

Installation
IMPORTANT: The installation on the application computer has to be performed
before the installations on the frontend computers and media server computers.

S | Name
| Summary
| Type
--+----------------------------------+-----------------------------------+-------...
| package
...
| package
| package
| package
...
| package
| OpenScapeUC_Small
| package
| package
| package
| package
...
A31003-S5070-J100-12-7631, 02/2013
281
Installation
osc-setup in OpenScapeUC_Large_BE
architecture.
Example:
Problem: OpenScapeUC_Large_BE-6.0_1.0.0-007.noarch requires OpenScapeUC_Large_BE, but
this requirement cannot be provided
Solution 2: do not install OpenScapeUC_Large_BE-6.0_1.0.0-007.noarch
Solution 3: break OpenScapeUC_Large_BE by ignoring some of its dependencies
3. Enter 1.
automatically in succession. See step 5 on page 264 for an example.
6. There are two options for checking whether a specific RPM has been
installed:

Example:
Example output:

S | Name
| Summary
| Type
--+----------------------------------+-----------------------------------+-------...
| package
| package
...
282
A31003-S5070-J100-12-7631, 02/2013
Installation
or
rpm -q <RPM name>
Example:
Example output:

additional RPM:
8. Check for any newer fix release and hotfix versions for the OpenScape UC
Application and install them according to the corresponding version notes if
applicable.
A31003-S5070-J100-12-7631, 02/2013
283
Installation


applications that carry OpenBranch or hpum in their names:
zypper se --match-any OpenBranch hpum
S | Name
| Summary
| Type
--+-------------------------------+--------------------------------+-------| CLM
| package
| package
| package
10. If you want to install the OpenBranchAssistant, for example, enter the
following command:
osc-setup in OpenBranchAssistant
If you want to install e. g. the Office Communicator Connector (see Chapter
11, Connecting the Microsoft Office Communication Server/Microsoft Lync
Server), enter the following command:
NOTE: If you want to align the presence status of users between the
Microsoft Office Communication Server/Microsoft Lync Server and the
OpenScape UC Application, the connection from the Microsoft Office
Communication Server/Microsoft Lync Server to the OpenScape UC Application is needed. See the OpenScape UC Application Planning Guide for
details.
If you wish to install the Openfire server (Instant Messaging) (see Chapter 12,
Connecting Instant Messaging) e. g. on the application computer, use the
following command to check whether the RPM symphonia-jre-ibm is
installed:
284
A31003-S5070-J100-12-7631, 02/2013
Installation
zypper se --match-any symphonia-jre-ibm

S | Name
| Summary
| Type
--+-------------------------+-------------------------------+-------i | symphonia-jre-ibm
| Symphonia Framework - jre-ibm | package
| symphonia-jre-ibm-64bit | Symphonia Framework - jre-ibm | package
The output must feature an i in the first column. If not, install this RPM:
Then enter the following command:

com
configurations
lib
A31003-S5070-J100-12-7631, 02/2013
285
Installation

Frameworks.
If you want to install the OpenStage Client, execute the following command
on the application computer:
rpm -i CA2-OSIPP-BACKEND-<version>.rpm
Copy the file CA2-OSIPP-BACKEND-<version>.rpm from the i586
CA2-OSIPP-BACKEND-3.2_4.0.0-39.27668.i586.rpm
If you want to connect the OpenScape UC Application to OpenScape
Xpressions, enter the following command:
Example output:
checking Arguments
Option clean: yes
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
286
A31003-S5070-J100-12-7631, 02/2013
Installation
Unmounting...
Removing...
Unmounting...
Removing...
page 240.
Example:
rm -R /tmp/tmpRepo
13. If the application computer and frontend computers are in the same subnetwork, continue with step 15 on page 289. Otherwise, continue with step 14
on page 287.
Routing schemas Multicast and Unicast
14. The routing schema Multicast (point-to-multipoint connection) is used for the
communication between the HiPathCA service on the application computer
and the HiPathCA services on the frontend computers by default. However,
this is only possible if the application computer and the frontend computers
are in the same sub-network.
NOTE: An additional requirement is that the port used by Multicast in a
possible firewall between the application computer and the frontend
computers must be open. However, this requirment is complied with automatically, because all ports between the application computer and the frontend
computers must be open.
If Multicast cannot be used, the routing schema Unicast (point-to-point
connection) is deployed and you need to execute the following steps:
a) Open the /opt/siemens/HiPathCAconfig/host.env file on the
application computer in an editor, for example:
vi /opt/siemens/HiPathCAconfig/host.env
b) Look for the entry
CLUSTER=<clusterId>
A31003-S5070-J100-12-7631, 02/2013
287
Installation
In step 9 on page 205 you assigned a value to the SI_COMMUNITY_NAME

parameter in the /root/knut.responsefile.txt file on the
application computer. This value was automatically assigned to the
CLUSTER parameter during the OpenScape UC Application installation
c) Expand this value so that it corresponds to the following pattern:
<clusterId>@<application comuter name, FQDN or IP address>:4875
<application computer name, FQDN or IP address>:

computer name (host name), fully qualified domain name or IP
address of the application computer (not of the frontend computer!)
NOTE: If you use the computer name or the fully qualified domain name
of the application computer, ensure that the name can be resolved in all
other involved computers (compare Section 4.6, Using FQDNs for Very
Large Deployment, on page 184).
4875: 4875 is the default port, but you can also use another free port
NOTE: You need not check whether this port is opened in the firewall
(see Table 73 on page 413), because all ports between the application
computer and the frontend computer must be open.
d) Save the modification.
e) Continue with step 15 on page 289.
288
A31003-S5070-J100-12-7631, 02/2013
Installation
Start
by user root.
examples. Refer to the programming guide OpenScape UC Application
SPML SDK for further details on SPML use.
After having checked the requirements (see Section 5.3.3.2, Requirements for
Installing Additional Computers, on page 290) and having resolved issues that
might occur (seeSection 5.3.3.6, Resolving Installation Issues, on page 312),
continue with the installation of the frontend computer (see Section 5.3.3.3,
Installation on the Frontend Computer, on page 293).
A31003-S5070-J100-12-7631, 02/2013
289
Installation
5.3.3.2 Requirements for Installing Additional Computers

Before you can install further computers (frontend or media server computer), the
following requirements need to be met.
1. On the application computer, OpenScape UC Application must be up (Section
5.3.3.1, Installation on the Application Computer, on page 281) and running
before the installation of any additional computer can start.
NOTE: This is required because a service on the application computer is
contacted to obtain system-wide data (for example: configured computers
and certificates) during the installation of additional computers.
2. Wait for approximately 5 minutes after the OpenScape UC Application has
started on the application computer.
3. IMPORTANT: Check the system status of the OpenScape UC Application on
the application computer, before you start installing another computer.
Execute the following command in a command line on the application
computer:
bash /opt/siemens/servicetools/install/bin/installlib.sh prerequisite.primaryReady
If the OpenScape UC Application works correctly on the application

computer, the following is put out, for example:
Buildfile: /opt/siemens/servicetools/install/installlib.xml
-read.internal.responsefile:
[echo] reading response.file
/opt/siemens/servicetools/install/conf/responsefile.txt
prerequisite.primaryReady:
[echo] Checking if PRIMARY NODE is READY ....
[pingdeploymentsupportsvc] DEBUG - getting current ContextClassLoader ...
[pingdeploymentsupportsvc] INFO - log4j path for log files
SYMPHONIA_LOG: null
...
[echo] PRIMARY NODE is READY (DeploymentSupport service was successfully contacted :-) DEBUG
- DeploymentSupportDelegate.getPrimaryNodeSystemXml done.
DEBUG - restoring ContextClassLoader (java.net.URLClassLoader@7fc47fc4)
BUILD SUCCESSFUL
...
IMPORTANT: Do not continue until the command has returned BUILD

SUCCESSFUL.
290
A31003-S5070-J100-12-7631, 02/2013
Installation
4. Ensure that the login data for the administrator account and the database
login in the response file match the login data in the OpenScape UC
Application on the application computer.
There are the following error scenarios which cause the user credentials to
be invalid or inaccessible:
The installation program checks that the application computer can be

reached and aborts with an error if a connection is not possible.
A firewall blocks the data traffic between the new computer and the
application computer.
IMPORTANT: Some devices like firewalls separate idle TCP connections after a specific period without notice. Verify that no such device
exists between the frontend and application computer, because serious
instabilities will otherwise occur during operation. This may become
obvious by e.g. the error message Service unavailable, temporarily
impossible logins or empty device lists.
Please note that these errors also occur when a firewall is set in a way
that transmissions via closed TCP connections are answered by sending
RST messages (Reset). Please also note that some firewalls separate
idle sockets without notice if they do not filter anything.
between the frontend and application computer. Limited timeouts for
inbound client connections to fend off Denial-of-Service attacks from the
internet or intranet must still be possible, though.
Application computer and the new computer do not have the same
system time.
Check if the system time of all OpenScape UC Application-related
exceeds one second, contact the IT person responsible for the network
and request that the system time be synchronized. The Network Time
Protocol (NTP) is often used for synchronizing the system time (see
The functional range of the application computer service that supports the
setup on the new computer is partly or entirely unavailable.
Solution: Wait until this service is up an running or execute the steps in
Section 5.3.3.6, Resolving Installation Issues, on page 312.
The login data in the response file is incorrect (obsolete, for example).
A31003-S5070-J100-12-7631, 02/2013
291
Installation
Resolution: To create a valid response file refer to Section 5.2,

Configuring the Installation.
NOTE: One possible error scenario is that the original (generated)
password was changed on the application computer immediately after the
application computer was installed, and the original password is still
required for the installation of additional nodes.
The DAR file is obsolete. A DAR file must origin from the current setup of
the application computer. A DAR file of an older installation must not be
used.
IMPORTANT: The DAR file is not part of a backup. It can be re-created
on the application computer anytime. If the application computer is no
longer operable and no backup is available, thus a new installation must
be performed, a new DAR file is created that must also be used for all
frontend and media server computers.
Creating the DAR file

5. Execute the following command on the application computer to create the
DAR file for the frontend and media server computers:
bash /opt/siemens/servicetools/install/bin/installlib.sh createdar
-Dpath=/tmp/knut.file.dar
6. Copy the /tmp/knut.file.dar file to the /root directory on all frontend

and media server computers with help of scp, for example.
292
A31003-S5070-J100-12-7631, 02/2013
Installation
5.3.3.3 Installation on the Frontend Computer

NOTE: You can install one or several frontend or media server computers
parallel. Please obtain the number of frontend and media server computers
supported for this deployment scenario from the OpenScape UC Application
Planning Guide.
Installation
1. Verify that the response file has been created for the frontend computer (see
section Response file for the frontend server) and stored as /root/
knut.reponsefile.txt on the frontend computer.
2. Verify that the DAR file has been copied from the application computer to /
root/knut.file.dar on the frontend computer (see step 5 on page 292).
NOTE: The DAR file is identical for all frontend and media server computers.
3. Execute the steps described in Section 5.3.1, Providing the Installation
Sources in an Installation Repository in osc-setup, on page 234 on the
frontend computer.
4. On the frontend computer, execute the following command:
osc-setup in OpenScapeUC_Large_FE
architecture.
Example:
Problem: OpenScapeUC_Large_FE-6.0_1.0.0-007.noarch requires OpenScapeUC_Large_FE, but
Solution 2: do not install OpenScapeUC_Large_FE-6.0_1.0.0-007.noarch
Solution 3: break OpenScapeUC_SLarge_FE by ignoring some of its dependencies
6. Enter 1.
A31003-S5070-J100-12-7631, 02/2013
293
Installation
8. If you wish to install the OpenStage Client, execute the following command
on the frontend computer:
rpm -i CA2-OSIPP-FRONTEND-<version>.rpm
Copy the file CA2-OSIPP-FRONTEND-<version>.rpm from the i586
CA2-OSIPP-FRONTEND-3.2_4.0.0-39.27668.i586.rpm
applicable.
on page 294.
frontend computer in an editor, for example:
CLUSTER=<clusterId>
You assigned a value to the SI_COMMUNITY_NAME parameter in the /
root/knut.responsefile.txt file on the frontend computer. This
value was automatically assigned to the CLUSTER parameter during the
OpenScape UC Application installation on the frontend computer.
294
A31003-S5070-J100-12-7631, 02/2013
Installation

Use the same value you used on the application computer in step 14c on
page 288 . The following applies:

NOTE: Because there are no processes associated to HiPathCA on the
media server computers, there is no host.env file on these computers
either. Therefore, no action is performed on the media server computers that
would be analog to the step here.
Load balancer
12. If there is more than one frontend computer, a load balancer is always
required for Large Deployment. This load balancer is installed on a separate
computer. Please obtain the setup description for a load balancer from the
documentation for the load balancer product you use. You find the
configuration description in section "Configuring the Load Balancer" in the
Administration.
Start
13. After the installation has been successfully completed, execute the following
command on the frontend computer:
A31003-S5070-J100-12-7631, 02/2013
295
Installation
14. Execute steps 1 on page 293 to 9 on page 294 and step 13 on page 295 for
all frontend computers.
Configuration
15. If the application computer and the frontend computers are in different subnetworks, so that routing schema Unicast must be used instead of Multicast,
a) Log on to the CMP via web browser.
Because the frontend servers have just started, it may take several
minutes until this step is successful.
NOTE: The /etc/init.d/symphoniad status command delivering
the output WebClient running on a frontend computer does not signal
a fully operable frontend server.
b) Click under Maintenance > Inventory > Nodes & Applications >
Nodes > <name of the application computer> > Actions > Show
services status on the Show button.
c) Enter in the Filter field value JournalFacade or *Journal* and click
on Go.
d) Click on the JournalFacade entry. A dialog for the journal facade service
opens.
e) Enter the application computer's IP address in the Discover.IPAddress
field.
f)
Enter in the Discover.port field the port number of the port on the
application computer you entered in step 14c on page 288 and in step 11c
on page 294. The default port number is 4875.
g) Click on the Save button.

16. Continue with the installation on the media server computer (see Section
5.3.3.4, Installation on the Media Server Computer, on page 297).
296
A31003-S5070-J100-12-7631, 02/2013
Installation
5.3.3.4 Installation on the Media Server Computer

Planning Guide.
Installation
1. Verify that the response file has been created for the media server computer
(see section Response file for the media server computer) and stored as /
root/knut.reponsefile.txt on the media server computer.
root/knut.file.dar on the media server computer (see step 5 on page
292).
Sources in an Installation Repository in osc-setup, on page 234 on the media
server computer.
4. On the media server computer, execute the following command:
osc-setup in OpenScapeUC_Large_MS
architecture.
Example:
Problem: OpenScapeUC_Large_MS-6.0_1.0.0-007.noarch requires OpenScapeUC_Large_MS, but
Solution 2: do not install OpenScapeUC_Large_MS-6.0_1.0.0-007.noarch
Solution 3: break OpenScapeUC_StandardDuplexSmall by ignoring some of its dependencies
A31003-S5070-J100-12-7631, 02/2013
297
Installation
6. Enter 1.
applicable.
298
A31003-S5070-J100-12-7631, 02/2013
Installation

steps:
9. Verify that the installation files (ISO files) you require for languages you wish
to install are provided in osc-setup. xxx
the steps required for registering an ISO file in osc-setup.
A31003-S5070-J100-12-7631, 02/2013
299
Installation

S | Name
| Summary
| Type
| package
| package
...
| package
| package
...
package
package

...
| mediaserver_voiceportal_languagepack_DE-DE
package
| mediaserver_voiceportal_languagepack_EN-GB
package
i | mediaserver_voiceportal_languagepack_EN-US
package
| mediaserver_voiceportal_languagepack_ES-ES
package
...
| Mediaserver VoicePortal ->|


package
package
...
package
package
package
...
300
| Conferencing Languagepac->|
A31003-S5070-J100-12-7631, 02/2013
Installation
i | uc-asr
package
| uc-asr-de_de
package
| uc-asr-en_us
package
i | uc-asrcore
package
...
| Meta rpm to install all A->|
i | uc-tts
package
| uc-tts-de_de
package
| uc-tts-en_gb
package
| uc-asr-en_us
package
...
| uc-tts-zh_cn
package
i | uc-ttscore
package
| Meta rpm to install all ->|
| German speech recogniti->|

| American English speech ->|
| Meta rpm to install Nua-> |
| German tts voice.
| British English tts voice.|

| Chinese Mandarin tts voi->|
| Meta rpm to install Nuan->|

texts for the PBX
prompt texts:
Example:
for the PBX.
Example:
A31003-S5070-J100-12-7631, 02/2013
301
Installation

used in the US.
language support:

language package

302

A31003-S5070-J100-12-7631, 02/2013
Installation

Country
Language
Argentina
Australia
Brazil
Belgium
Bulgaria
BosniaHerzegovina
Chile
People's Republic
of China
Denmark
Germany
Ecuador
Estonia
Finland
France
Greece
Great Britain
Hongkong
India
Indonesia
Italy
Japan
Canada
Colombia
Korea
Croatia
Latvia
Lithuania
Malaysia
Morocco
Mexico
Netherlands
Norway
Austria
Peru
Spanish (Argentina)
English (AU)
Portuguese (Brazil)
Flemish
Bulgarian
Bosnian
Languag Individual
e Code System
Announcements
es_ar
en_au
pt_br
nl_be
bg
bs
Spanish (Chile)
es_cl
zh
Danish
German
Spanish (Ecuador)
Estonian
Finnish
French
Greek
English (UK)
Chinese (Hongkong)
English (India)
Indonesian
Italian
Japanese
French (Canada)
Spanish (Colombia)
Korean
Croatian
Latvian
Lithuanian
Malay
French
Spanish (Mexico)
Dutch
Norwegian
German
Spanish (Peru)
da
de
es_ec
et
fi
fr
el
en
zh_hk
en_in
id
it
Yes
fr_ca
es_co
ko
hr
lv
lt
ms
fr_ma
es_mx
nl
no
de_at
es_pe
Table 17
Pre-configured
Fallback
Language
en
nl
sr
es_ar
es_mx
en_us
en
en_us
en_us
es_mx
en_us
en
en_us
fr
de
en_mx
ISO File1
Spanish
English
Portuguese
AdditionalLanguages
AdditionalLanguages
AdditionalLanguages
Spanish
Chinese
AdditionalLanguages
German
Spanish
AdditionalLanguages
AdditionalLanguages
French
AdditionalLanguages
English
Chinese
English
AdditionalLanguages
Italian
AdditionalLanguages
French
Spanish
AdditionalLanguages
AdditionalLanguages
AdditionalLanguages
AdditionalLanguages
AdditionalLanguages
French
Spanish
AdditionalLanguages
AdditionalLanguages
German
Spanish
A31003-S5070-J100-12-7631, 02/2013
303
Installation
Country
Language
Philippines
Poland
Portugal
Romania
Russia
Sweden
Serbia
Singapore
Slovakia
Slovenia
Spain
South Africa
Taiwan
Thailand
Czech Republic
Turkey
Hungary
USA
Venezuela
United Arab
Emirates
Vietnam
Table 17
Polish
Romanian
Russian
Swedish
Serbian
Chinese (Singapore)
Slovakian
Slovenian
Spanish
English (ZA)
Chinese (Taiwan)
Thai
Czech
Turkish
Hungarian
English (US)
Spanish (Venezuela)
Arabian
Languag Individual
e Code System
Announcements
en_ph
pl
pt
ro
ru2
sv
sr
zh_sg
sk
sl
es
en_za
zh_tw
th
cs
tr
hu
en_us
es_ve
ar
Pre-configured
Fallback
Language
en_us
Vietnamese
vi
en_us
en_us
en
en_us
en_us
es_mx
ISO File1
English
AdditionalLanguages
Portuguese
AdditionalLanguages
AdditionalLanguages
AdditionalLanguages
AdditionalLanguages
Chinese
AdditionalLanguages
AdditionalLanguages
Spanish
English
Chinese
AdditionalLanguages
AdditionalLanguages
AdditionalLanguages
AdditionalLanguages
English
Spanish
AdditionalLanguages
AdditionalLanguages
1 This table indicates only part of the ISO file name that distinguishes the ISO files of an OpenScape UC Application setup medium, thus
for example English instead of OpenScapeUcSuiteApps-English-V7R1.0.0-130000.iso. In Table 8 on page 235 you find the list of all
available ISO files.

Example:
Example:
304
A31003-S5070-J100-12-7631, 02/2013
Installation
Language
Chinese (Mandarin)
German
English
English
French
Italian
Portuguese
Portuguese
Russian
Country
China
Germany
Great Britain
USA
France
Italy
Portugal
Brazil
Russia
Language Code
ZH_CN
DE_DE
EN_GB
EN_US
FR_FR
IT_IT
PT_PT
PT_BR
RU_RU2
Spanish
Spain
ES_ES
Table 18
ISO File1
Chinese
German
English
English
French
Italian
Portuguese
Portuguese
AdditionalLa
nguages
Spanish
OpenScapeUcSuiteApps-English-V7R1.0.0-130000.iso. In Table 8 on page 235 you find
the list of all available ISO files.

language:
Example:
Language
Chinese (Mandarin)
German
English
English
French
Italian
Portuguese
Portuguese
Russian
Country
China
Germany
Great Britain
USA
France
Italy
Portugal
Brazil
Russia
Language Code
ZH_CN
DE_DE
EN_GB
EN_US
FR_FR
IT_IT
PT_PT
PT_BR
RU_RU2
Spanish
Spain
ES_ES
Table 19
ISO File1
Chinese
German
English
English
French
Italian
Portuguese
Portuguese
AdditionalLa
nguages
Spanish
A31003-S5070-J100-12-7631, 02/2013
305
Installation

language:
Example:
default.
Language
Chinese (Mandarin)
German
English
English
French
Italian
Portuguese
Portuguese
Spanish
Dutch
Country
China
Germany
Great Britain
USA
France
Italy
Portugal
Brazil
Spain
Netherlands
Language Code
zh_cn
de_de
en_gb
en_us
fr_fr
it_it
pt_pt
pt_br
es_es
nl_nl
Russian
Russia
ru_ru2
Turkish
Turkey
tr_tr
Table 20
ISO File1
Chinese
German
English
English
French
Italian
Portuguese
Portuguese
Spanish
AdditionalLangu
ages
AdditionalLangu
ages
AdditionalLangu
ages
306
A31003-S5070-J100-12-7631, 02/2013
Installation

Nuance TTS:
Example:
default.
Language
Chinese (Mandarin)
German
English
English
French
Italian
Portuguese (Brazil)
Russian
Country
China
Germany
Great Britain
USA
France
Italy
Portugal
Brazil
Russia
Language Code
zh_cn
de_de
en_gb
en_us
fr_fr
it_it
pt_pt
pt_br
ru_ru2
Spanish
Spain
es_es
Table 21
ISO File1
Chinese
German
English
English
French
Italian
Portuguese
Portuguese
AdditionalLan
guages
Spanish

Example:
A31003-S5070-J100-12-7631, 02/2013
307
Installation

Language
German
English
Table 22
Country
Germany
USA
Language Code
de_de
en_us
ISO File1
3
1

Language
German
English
Table 23
Country
Germany
USA
Language Code
DE_DE
EN_US
ISO File1
3
1

Example output:
checking Arguments
Option clean: yes
308
A31003-S5070-J100-12-7631, 02/2013
Installation
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
page 240.
Example:
rm -R /tmp/tmpRepo
Start
19. Start the MRCP service, the Nuance TTS and the Nuance ASR:
Execute the following command on the media server computer to start the
OpenScape UC Application:
A31003-S5070-J100-12-7631, 02/2013
309
Installation
20. Perform the steps 1 on page 297 to 19 on page 309 for all media server
computers.
IMPORTANT: If more than one media server computer is available, we call
this collection a media server farm. You need to perform specific configurations on all media server computers of a media server farm such as configuring the SIP trunk, the voice portal and, if required, the conference portal.
More configuration steps must be executed on the second and every further
media server computer of a media server farm, such as configuring the voice
portal for the media server farm and, if required, also the conference portal.
Some of these steps require configurations on the PBX also. You can obtain
details on this from the administrator documentation OpenScape UC Application Configuration and Administration.
310
A31003-S5070-J100-12-7631, 02/2013
Installation
5.3.3.5 Starting and Rebooting Nodes

You can reboot
all OpenScape UC components on the application computer,
all OpenScape UC components on a frontend computer or
all OpenScape UC components on a media server computer
for yourself while the OpenScape UC components on all other computers

continue to operate.
However, if you wish to start or reboot OpenScape UC components on all of these
computers, please heed the following:
You can shut down the OpenScape UC components in any sequence or

parallel.
We urgently recommend to start the OpenScape UC components on the

application computer first, so that access to the database is provided for the
UC components on the other computers. Wait for a minute until you boot the
OpenScape UC components on the frontend computers and media server
computers in any sequence or parallel.
By executing a command you can reboot all OpenScape UC components on the

application computer, on all frontend computers and on all media server
computers:
1. If you wish to execute this, access the following directory on the application
computer:
/opt/siemens/servicetools/management/linux/
2. Execute the largeDeployRestart.sh script in one of the two following
manners:
IMPORTANT: If you use a remote connection (for example by SSH) to
access a computer, make sure that this connection is not aborted because
the command being executed on the remote computer may otherwise not be
fully carried out and an inconsistent state may set in.
You can avoid this problem by opening a local command line on the target
computer or using a program such as the Linux command screen for setting
up the connection to the remote target computer. This program allows moving
the connection session in the background after the command has been
executed and closing the actual input window (<CTRL>+A+D) to resume the
session at a later date (screen -r).
a) bash largeDeployRestart.sh -u <user name> -p <password>

Here, <user name> is e. g. administrator@system and
<password> is the password of this user.
A31003-S5070-J100-12-7631, 02/2013
311
Installation
Example:
bash largeDeployRestart.sh -u administrator@system -p Abc33?22
b) bash largeDeployRestart.sh
Enter the user name inclusive domain (example
administrator@system).
Enter the password.
Subsequently, the output reads:
You are about to restart the whole deployment system as
user administrator@system, please confirm (Y/N):
Enter Y.
NOTE: The largeDeployRestart.sh script does not immediately affect
the PBX.
NOTE: You can execute the script for Small Deployment also. It reboots all
OpenScape UC components on the application computer then.
3. The feedback Restart successful does not mean that all UC
components are operable. Execute the following command on every
computer to check the status of the main UC components on this computer:
5.3.3.6 Resolving Installation Issues

If the installation fails while installing an additional node, then first verify the
correct functionality on the application computer as follows:
1. Log on to the CMP and click on Operation & Maintenance > System Status
If the System Status page displays all the nodes that have already been
successfully installed (at least the application computer must be shown), it
verifies that the following services are working properly:
312
Logon
Domain
A31003-S5070-J100-12-7631, 02/2013
Installation
System Management Service
IMPORTANT: These three services are key to a successful communication

from the installer of the new node to the application computer.
a) There is a forth service called Deployment Support Service which is not
validated by displaying the System Status. It can be checked in the CMP
as follows:
Operation & Maintenance > Application Nodes > <name of the
application computer>
b) Sort the list of components by Name, and a status of all components is
displayed.
c) Search for Deployment Support Service and make sure that the status
is green, or execute the following command in a command line:
d) If the service restart does not produce the desired result, follow the
instructions given in Section 5.4, Checking the Installation, on page 347.
2. If the installation of the additional node fails at this point, you must execute
the following command:
NOTE: This command must not be executed on the application computer but
on the additional node concerned.
rpm -e symphonia
Perform the setup on the faulty node once more (osc-setup in ...).
A31003-S5070-J100-12-7631, 02/2013
313
Installation
5.3.4 Installing the Very Large Deployment

5.3.4.1 Installation on the Application Computer

Installation
IMPORTANT: The installation on the application computer has to be performed
before the installations on the frontend computers and media server computers.

S | Name
| Summary
| Type
--+----------------------------------+-----------------------------------+-------...
| package
...
| package
| package
| package
...
| package
| OpenScapeUC_Small
| package
| package
| package
| package
...
314
A31003-S5070-J100-12-7631, 02/2013
Installation
osc-setup in OpenScapeUC_VeryLarge_BE
architecture.
Example:
Problem: OpenScapeUC_VeryLarge_BE-6.0_1.0.0-007.noarch requires OpenScapeUC_VeryLarge_BE,
uninstallable providers: OpenScapeUC_VeryLarge_BE-6.0_1.0.0007.noarch[270fc4d9389754e36bb4dbe2a725408d]
Solution 2: do not install OpenScapeUC_VeryLarge_BE-6.0_1.0.0-007.noarch
Solution 3: break OpenScapeUC_SVeryLarge_BE by ignoring some of its dependencies
3. Enter 1.
6. There are two options for checking whether a specific RPM has been
installed:

Example:
Example output:

S | Name
| Summary
| Type
--+----------------------------------+-----------------------------------+-------...
| package
| package
...

or
A31003-S5070-J100-12-7631, 02/2013
315
Installation
rpm -q <RPM name>

Example:
Example output:

additional RPM:
316
A31003-S5070-J100-12-7631, 02/2013
Installation

IMPORTANT: For Very Large Deployment the OpenScape UC Application must

be connected to an OpenScape Xpressions (XPR). The RPM
OpenScapeUC_xpraddons required for this is not automatically installed.
zypper se --match-any OpenBranch hpum
S | Name
| Summary
| Type
--+-------------------------------+--------------------------------+-------| CLM
| package
| package
| package
following command:
IMPORTANT: Neither scs_osc_officecommunicator_be (Office
Communicator Connector, see Chapter 11, Connecting the Microsoft Office
Communication Server/Microsoft Lync Server) nor symphoniaopenfire-base or symphonia-openfire (Openfire server) must be
installed on the application computer. In case of Very Large Deployment, an
Openfire server must definitely be installed on a separate computer (see
Chapter 12, Infrastructure) on which the MySQL database is installed also.
A31003-S5070-J100-12-7631, 02/2013
317
Installation
com
configurations
lib
Frameworks.

IMPORTANT: For Very Large Deployment the OpenScape UC Application
must be connected to an OpenScape Xpressions (XPR). The RPM
Install this RPM with the following command:
318
A31003-S5070-J100-12-7631, 02/2013
Installation
Example output:
checking Arguments
Option clean: yes
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
page 240.
Example:
A31003-S5070-J100-12-7631, 02/2013
319
Installation
rm -R /tmp/tmpRepo
on page 320.
CLUSTER=<clusterId>
In step 8 on page 220 you assigned a value to the SI_COMMUNITY_NAME
parameter in the /root/knut.responsefile.txt file on the
application computer. This value was automatically assigned to the
CLUSTER parameter during the OpenScape UC Application installation

320
A31003-S5070-J100-12-7631, 02/2013
Installation
A31003-S5070-J100-12-7631, 02/2013
321
Installation
Start
by user root.
examples. Refer to the programming guide OpenScape UC Application
SPML SDK for further details on SPML use.
After having checked the requirements (see Section 5.3.4.2, Requirements for
Installing Additional Computers, on page 323) and having resolved issues that
might occur (seeSection 5.3.4.6, Resolving Installation Issues, on page 345),
continue with the installation of the frontend computer (see Section 5.3.4.3,
Installation on the Frontend Computer, on page 326).
322
A31003-S5070-J100-12-7631, 02/2013
Installation
5.3.4.2 Requirements for Installing Additional Computers

Before you can install further computers (frontend or media server computer), the
following requirements need to be met.
1. On the application computer, OpenScape UC Application must be up (Section
5.3.4.1, Installation on the Application Computer, on page 314) and running
before the installation of any additional computer can start.
2. Wait for approximately 5 minutes after the OpenScape UC Application has
computer:

SYMPHONIA_LOG: null
...
BUILD SUCCESSFUL
...
A31003-S5070-J100-12-7631, 02/2013
323
Installation

system time.
324
A31003-S5070-J100-12-7631, 02/2013
Installation

used.
Creating the DAR file


A31003-S5070-J100-12-7631, 02/2013
325
Installation
5.3.4.3 Installation on the Frontend Computer

Planning Guide.
Installation
1. Verify that the response file has been created for the frontend computer (see
section Response file for the frontend server) and stored as /root/
knut.reponsefile.txt on the frontend computer.
root/knut.file.dar on the frontend computer (see step 5 on page 325).
frontend computer.
osc-setup in OpenScapeUC_VeryLarge_FE
architecture.
Example:
Problem: OpenScapeUC_VeryLarge_FE-6.0_1.0.0-007.noarch requires OpenScapeUC_VeryLarge_FE,
uninstallable providers: OpenScapeUC_VeryLarge_FE-6.0_1.0.0007.noarch[270fc4d9389754e36bb4dbe2a725408d]
Solution 2: do not install OpenScapeUC_VeryLarge_FE-6.0_1.0.0-007.noarch
Solution 3: break OpenScapeUC_VeryLarge_FE by ignoring some of its dependencies
6. Enter 1.
326
A31003-S5070-J100-12-7631, 02/2013
Installation
8. If you wish to install the OpenStage Client, execute the following command
applicable.
on page 327.
frontend computer in an editor, for example:
CLUSTER=<clusterId>
In step 22 on page 224 you assigned a value to the
SI_COMMUNITY_NAME parameter in the /root/
knut.responsefile.txt file on the frontend computer. This value
was automatically assigned to the CLUSTER parameter during the
OpenScape UC Application installation on the frontend computer.
A31003-S5070-J100-12-7631, 02/2013
327
Installation

Use the same value you used on the application computer in step 14c on
page 320 . The following applies:

Load balancer
12. If there is more than one frontend computer, a load balancer is always
required for Very Large Deployment. This load balancer is installed on a
separate computer. Please obtain the setup description for a load balancer
from the documentation for the load balancer product you use. You find the
configuration description in section "Configuring the Load Balancer" in the
Administration.
Start
328
A31003-S5070-J100-12-7631, 02/2013
Installation
14. Execute steps 1 on page 326 to 9 on page 327 and step 13 on page 328 for
all frontend computers.
Configuration
15. If the application computer and the frontend computers are in different subnetworks, so that routing schema Unicast must be used instead of Multicast,
a) Log on to the CMP via web browser.
Because the frontend servers have just started, it may take several
minutes until this step is successful.
NOTE: The /etc/init.d/symphoniad status command delivering
the output WebClient running on a frontend computer does not signal
a fully operable frontend server.
b) Click under Maintenance > Inventory > Nodes & Applications >
Nodes > <name of the application computer> > Actions > Show
services status on the Show button.
c) Enter in the Filter field value JournalFacade or *Journal* and click
on Go.
d) Click on the JournalFacade entry. A dialog for the journal facade service
opens.
e) Enter the application computer's IP address in the Discover.IPAddress
field.
f)
Enter in the Discover.port field the port number of the port on the
application computer you entered in step 14c on page 320 and in step 11c
on page 327. The default port number is 4875.
g) Click on the Save button.

16. Continue with the installation on the media server computer (see Section
5.3.4.4, Installation on the Media Server Computer, on page 330).
A31003-S5070-J100-12-7631, 02/2013
329
Installation
5.3.4.4 Installation on the Media Server Computer

Planning Guide.
Installation
1. Verify that the response file has been created for the media server computer
(see section Response file for the media server computer) and stored as /
root/knut.reponsefile.txt on the media server computer.
root/knut.file.dar on the media server computer (see step 5 on page
325).
server computer.
osc-setup in OpenScapeUC_VeryLarge_MS
architecture.
Example:
Problem: OpenScapeUC_VeryLarge_MS-6.0_1.0.0-007.noarch requires OpenScapeUC_VeryLarge_MS,
uninstallable providers: OpenScapeUC_VeryLarge_MS-6.0_1.0.0007.noarch[270fc4d9389754e36bb4dbe2a725408d]
Solution 2: do not install OpenScapeUC_VeryLarge_MS-6.0_1.0.0-007.noarch
Solution 3: break OpenScapeUC_SVeryLarge_MS by ignoring some of its dependencies
330
A31003-S5070-J100-12-7631, 02/2013
Installation
6. Enter 1.
A31003-S5070-J100-12-7631, 02/2013
331
Installation

steps:
9. Verify that the installation files (ISO files) you require for the languages you
wish to install are registered in osc-setup.
the steps required for registering an ISO file in osc-setup.
332
A31003-S5070-J100-12-7631, 02/2013
Installation

S | Name
| Summary
| Type
--+------------------------------+----------------------------------------------+-------| mediaserver_announcements_ar | Mediaserver_announcements_ar
| package
| package
...
| package
| package
...
package
package

...
package
package
package
package
...


package
package
...
package
package
package
...
A31003-S5070-J100-12-7631, 02/2013
333
Installation
i | uc-asr
package
| uc-asr-de_de
package
| uc-asr-en_us
package
i | uc-asrcore
package
...
i | uc-tts
package
| uc-tts-de_de
package
| uc-tts-en_gb
package
| uc-asr-en_us
package
...
| uc-tts-zh_cn
package
i | uc-ttscore
package

| German tts voice.


texts for the PBX
prompt texts:
Example:
for the PBX.
Example:
334
A31003-S5070-J100-12-7631, 02/2013
Installation

used in the US.
language support:

language package


A31003-S5070-J100-12-7631, 02/2013
335
Installation

Country
Language
Argentina
Australia
Brazil
Belgium
Bulgaria
BosniaHerzegovina
Chile
People's Republic
of China
Denmark
Germany
Ecuador
Estonia
Finland
France
Greece
Great Britain
Hongkong
India
Indonesia
Italy
Japan
Canada
Colombia
Korea
Croatia
Latvia
Lithuania
Malaysia
Morocco
Mexico
Netherlands
Norway
Austria
Peru
Spanish (Argentina)
English (AU)
Portuguese (Brazil)
Flemish
Bulgarian
Bosnian
Languag Individual
e Code System
Announcements
es_ar
en_au
pt_br
nl_be
bg
bs
Spanish (Chile)
es_cl
zh
Danish
German
Spanish (Ecuador)
Estonian
Finnish
French
Greek
English (UK)
Chinese (Hongkong)
English (India)
Indonesian
Italian
Japanese
French (Canada)
Spanish (Colombia)
Korean
Croatian
Latvian
Lithuanian
Malay
French
Spanish (Mexico)
Dutch
Norwegian
German
Spanish (Peru)
da
de
es_ec
et
fi
fr
el
en
zh_hk
en_in
id
it
Yes
fr_ca
es_co
ko
hr
lv
lt
ms
fr_ma
es_mx
nl
no
de_at
es_pe
Table 24
336
Pre-configured
Fallback
Language
en
nl
sr
es_ar
es_mx
en_us
en
en_us
en_us
es_mx
en_us
en
en_us
fr
de
en_mx
ISO File1
Spanish
English
Portuguese
AdditionalLanguages
AdditionalLanguages
AdditionalLanguages
Spanish
Chinese
AdditionalLanguages
German
Spanish
AdditionalLanguages
AdditionalLanguages
French
AdditionalLanguages
English
Chinese
English
AdditionalLanguages
Italian
AdditionalLanguages
French
Spanish
AdditionalLanguages
AdditionalLanguages
AdditionalLanguages
AdditionalLanguages
AdditionalLanguages
French
Spanish
AdditionalLanguages
AdditionalLanguages
German
Spanish
A31003-S5070-J100-12-7631, 02/2013
Installation
Country
Language
Philippines
Poland
Portugal
Romania
Russia
Sweden
Serbia
Singapore
Slovakia
Slovenia
Spain
South Africa
Taiwan
Thailand
Czech Republic
Turkey
Hungary
USA
Venezuela
United Arab
Emirates
Vietnam
Polish
Romanian
Russian
Swedish
Serbian
Chinese (Singapore)
Slovakian
Slovenian
Spanish
English (ZA)
Chinese (Taiwan)
Thai
Czech
Turkish
Hungarian
English (US)
Spanish (Venezuela)
Arabian
Languag Individual
e Code System
Announcements
en_ph
pl
pt
ro
ru2
sv
sr
zh_sg
sk
sl
es
en_za
zh_tw
th
cs
tr
hu
en_us
es_ve
ar
Vietnamese
vi
Table 24
Pre-configured
Fallback
Language
en_us
en_us
en
en_us
en_us
es_mx
en_us
ISO File1
English
AdditionalLanguages
Portuguese
AdditionalLanguages
AdditionalLanguages
AdditionalLanguages
AdditionalLanguages
Chinese
AdditionalLanguages
AdditionalLanguages
Spanish
English
Chinese
AdditionalLanguages
AdditionalLanguages
AdditionalLanguages
AdditionalLanguages
English
Spanish
AdditionalLanguages
AdditionalLanguages
1 This table indicates only part of the ISO file name that distinguishes the ISO files of an OpenScape UC Application setup medium, thus
for example English instead of OpenScapeUcSuiteApps-English-V7R1.0.0-130000.iso. In Table 8 on page 235 you find the list of all
available ISO files.

Example:
Example:
A31003-S5070-J100-12-7631, 02/2013
337
Installation
Language
Chinese (Mandarin)
German
English
English
French
Italian
Portuguese
Portuguese
Russian
Country
China
Germany
Great Britain
USA
France
Italy
Portugal
Brazil
Russia
Language Code
ZH_CN
DE_DE
EN_GB
EN_US
FR_FR
IT_IT
PT_PT
PT_BR
RU_RU2
Spanish
Spain
ES_ES
Table 25
ISO File1
Chinese
German
English
English
French
Italian
Portuguese
Portuguese
AdditionalLa
nguages
Spanish

language:
Example:
Language
Chinese (Mandarin)
German
English
English
French
Italian
Portuguese
Portuguese
Russian
Country
China
Germany
Great Britain
USA
France
Italy
Portugal
Brazil
Russia
Language Code
ZH_CN
DE_DE
EN_GB
EN_US
FR_FR
IT_IT
PT_PT
PT_BR
RU_RU2
Spanish
Spain
ES_ES
Table 26
338
ISO File1
Chinese
German
English
English
French
Italian
Portuguese
Portuguese
AdditionalLa
nguages
Spanish
A31003-S5070-J100-12-7631, 02/2013
Installation

language:
Example:
default.
Language
Chinese (Mandarin)
German
English
English
French
Italian
Portuguese
Portuguese
Spanish
Dutch
Country
China
Germany
Great Britain
USA
France
Italy
Portugal
Brazil
Spain
Netherlands
Language Code
zh_cn
de_de
en_gb
en_us
fr_fr
it_it
pt_pt
pt_br
es_es
nl_nl
Russian
Russia
ru_ru2
Turkish
Turkey
tr_tr
Table 27
ISO File1
Chinese
German
English
English
French
Italian
Portuguese
Portuguese
Spanish
AdditionalLangu
ages
AdditionalLangu
ages
AdditionalLangu
ages
A31003-S5070-J100-12-7631, 02/2013
339
Installation

Nuance TTS:
Example:
default.
Language
Chinese (Mandarin)
German
English
English
French
Italian
Portuguese (Brazil)
Russian
Country
China
Germany
Great Britain
USA
France
Italy
Portugal
Brazil
Russia
Language Code
zh_cn
de_de
en_gb
en_us
fr_fr
it_it
pt_pt
pt_br
ru_ru2
Spanish
Spain
es_es
Table 28
ISO File1
Chinese
German
English
English
French
Italian
Portuguese
Portuguese
AdditionalLan
guages
Spanish

Example:
340
A31003-S5070-J100-12-7631, 02/2013
Installation

Language
German
English
Table 29
Country
Germany
USA
Language Code
de_de
en_us
ISO File1
German
English

Language
German
English
Table 30
Country
Germany
USA
Language Code
DE_DE
EN_US
ISO File1
German
English

Example output:
checking Arguments
Option clean: yes
A31003-S5070-J100-12-7631, 02/2013
341
Installation
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
page 240.
Example:
rm -R /tmp/tmpRepo
Start
Execute the following command on the media server computer to start the
342
A31003-S5070-J100-12-7631, 02/2013
Installation
20. Perform the steps 1 on page 330 to 19 on page 342 for all media server
computers.
IMPORTANT: If more than one media server computer is available, we call
this collection a media server farm. You need to perform specific configurations on all media server computers of a media server farm such as configuring the SIP trunk, the voice portal and, if required, the conference portal.
More configuration steps must be executed on the second and every further
media server computer of a media server farm, such as configuring the voice
portal for the media server farm and, if required, also the conference portal.
Some of these steps require configurations on the PBX also. You can obtain
details on this from the administrator documentation OpenScape UC Application Configuration and Administration.
A31003-S5070-J100-12-7631, 02/2013
343
Installation
5.3.4.5 Starting and Rebooting Nodes

You can reboot
all OpenScape UC components on the application computer,
all OpenScape UC components on a frontend computer or
all OpenScape UC components on a media server computer
for yourself while the OpenScape UC components on all other computers

continue to operate.
However, if you wish to start or reboot OpenScape UC components on all of these
computers, please heed the following:
You can shut down the OpenScape UC components in any sequence or

parallel.
We urgently recommend to start the OpenScape UC components on the

application computer first, so that access to the database is provided for the
UC components on the other computers. Wait for a minute until you boot the
OpenScape UC components on the frontend computers and media server
computers in any sequence or parallel.
By executing a command you can reboot all OpenScape UC components on the

application computer, on all frontend computers and on all media server
computers:
1. If you wish to execute this, access the following directory on the application
computer:
/opt/siemens/servicetools/management/linux/
2. Execute the largeDeployRestart.sh script in one of the two following
manners:
a) bash largeDeployRestart.sh -u <user name> -p <password>
Here, <user name> is e. g. administrator@system and
<password> is the password of this user.
Example:
bash largeDeployRestart.sh -u administrator@system -p Abc33?22
b) bash largeDeployRestart.sh
Enter the user name inclusive domain (example
administrator@system).
Enter the password.
Subsequently, the output reads:
344
A31003-S5070-J100-12-7631, 02/2013
Installation
You are about to restart the whole deployment system as

user administrator@system, please confirm (Y/N):
Enter Y.
NOTE: The largeDeployRestart.sh script does not immediately affect
the PBX.
NOTE: You can execute the script for Small Deployment also. It reboots all
OpenScape UC components on the application computer then.
3. The feedback Restart successful does not mean that all UC
components are operable. Execute the following command on every
computer to check the status of the main UC components on this computer:
5.3.4.6 Resolving Installation Issues

If the installation fails while installing an additional node, then first verify the
correct functionality on the application computer as follows:
1. Log on to the CMP and click on Operation & Maintenance> System Status
If the System Status page displays all the nodes that have already been
successfully installed (at least the application computer must be shown), it
verifies that the following services are working properly:
Logon
Domain
System Management Service
IMPORTANT: These three services are key to a successful communication

from the installer of the new node to the application computer.
a) There is a forth service called Deployment Support Service which is not
validated by displaying the System Status. It can be checked in the CMP
as follows:
Operation & Maintenance > Application Nodes > <name of the
application computer>
b) Sort the list of components by Name, and a status of all components is
displayed.
A31003-S5070-J100-12-7631, 02/2013
345
Installation
c) Search for Deployment Support Service and make sure that the status
is green, or execute the following command in a command line:
d) If the service restart does not produce the desired result, follow the
instructions given in Section 5.4, Checking the Installation, on page 347.
2. If the installation of the additional node fails at this point, you must execute
NOTE: This command must not be executed on the application computer but
on the concerned additional node only.
rpm -e symphonia
Perform the setup on the faulty node once more (osc-setup in ...).
346
A31003-S5070-J100-12-7631, 02/2013
Checking the Installation
5.4 Checking the Installation

5.4.1 Initial Check
IMPORTANT: After the startup of the OpenScape UC Application, you need to
wait for a few minutes until all services operate. You can monitor the start by the
following command:
tailf /var/siemens/common/log/osgi.log
Check the file osgi.log for the service startup sequence. It should show a clean
system startup. Furthermore, the startup sequence should not have been
interrupted by error messages. The /log/osgi.err file must be empty. We
recommend to delete both files before you start the system with the following
command:
NOTE: If the osgi.log file ends in the sentence "Starting all instances
done.", it still may take some time until the system is ready for logging in.
The following is an example of the /var/siemens/common/log/osgi.log
file after a normal start:
FrameworkLauncherMain: init.
DaemonContext=org.apache.commons.daemon.support.DaemonLoader$Con
text@41b041b0
CommandLine Arguments: -consolelog ||
FrameworkLauncherMain: start
log4j.configuration: file:/opt/siemens/common/conf/log4j.xml
*** Container Start ***, Actual JMXServer-UpTime in milli
seconds: 3366, JMXServer-StartTime was: 1272990109047, Tue May
04 18:21:49 CEST 2010, Actual Time: 1272990112413, Tue May 04
18:21:52 CEST 2010
Installing: symomcomponent
Installing dependency: discovery
Installing dependency: servicediscovery
Installing: connector
Installing dependency: spnego
Installing: spnegoiae
Installing dependency: xacml
Installing dependency: dom4j
Installing dependency: hibernate_reduced
Installing dependency: faultmanagement
Installing dependency: event
Installing dependency: attrlogistics
Installing: alarmhandler
A31003-S5070-J100-12-7631, 02/2013
347
Installing dependency: systemconfigmanager

Installing dependency: systemmanagement
Installing dependency: containerconfigmanager
Installing: systemmanager
Installing dependency: utils
Installing dependency: dsacommon
Installing dependency: provisioning
Installing dependency: domainimportexport
Installing dependency: traceappender
Installing dependency: syslogauditcomponent
Installing dependency: loggingconfigmanager
Installing dependency: componentstate
Installing dependency: snmpagent
Installing dependency: faulthandler
Installing dependency: jobbase
Installing dependency: common
...
Installing: napplugin
Installing: vcceventplugin
Installing: hostservice
Installing: symphoniaadaptor
Installing: hostconfigservice
Installing dependency: journalfacade
Installing: journalplugin
Installing dependency: commonservices
Installing dependency: adminmanagerjobs
Installing dependency: jobbase
Installing dependency: hipath8000facadecmds
Installing: assistantservices
Installing: hipath8000facade
Installing: snmpreceiver
Installing dependency: rgconnectionconfiguratorjobs
Installing dependency: dsahpum
Installing: adminappcontroller
Installing: rg8700connection
Installing: adminmanager
Installing: vdgwconnector
Installing dependency: gwbroker
Installing: groupware
Installing: licensegranting
Installing: ldapconnector
Tue May 04 18:22:27 CEST 2010** No more instances to start.
Startup done. **
Tue May 04 18:22:27 CEST 2010* Start processing all bundles
done. *
You find the log files of the components in the following directory:
/var/siemens/common/log/install/
You can display the installed components with the following command:
zypper se --match-any symphonia scs_ mediaserver CA2 Assistant CLM dls openscape uc-tts uc-asr
Instead of the zypper command, you can also use the yast command (see
Section B.5, yast instead of zypper se or rpm -q, on page 1060).
If there is a problem, open the INSTALL.txt file on the setup medium of the
OpenScape UC Application and check whether your problem is described in
section Known Problems.
348
A31003-S5070-J100-12-7631, 02/2013
If the problem persists, check whether the RPMs listed in the

Requirements.txt file on the setup medium of the OpenScape UC
Application are installed. This file is automatically updated with each build of the
setup medium.
5.4.2 Checking with Rapidstat UC

5.4.2.1 Introduction
The Rapidstat UC program serves to check some important system configuration
parameters and some basic functionalities (for example logging on to the
container, database availability) after a setup or before an upgrade.
After the program has been started, all checks can be performed, also only
partially. Each check delivers a description of what is being performed and - if
possible - provides notes for solving problems if the test has failed. In addition, a
log is maintained.
Start Rapidstat UC on the application computer. Also start it on all media server
and frontend computers in the deployment scenarios Large Deployment and Very
Large Deployment.
If the OpenScape UC Application has not been started, not all Rapidstat UC
features can be executed.
5.4.2.2 Major Deployments

List of all checks
All available tests are listed by the following command:
/opt/siemens/servicetools/sanitychk/sanityChk.pl -l -p <administrator password>
See Table 31 on page 355 for the meaning of <administrator password>.
NOTE: SLES interprets an exclamation mark (!) in a password as repetition of
the last command. To avoid this, you need to prefix each exclamation mark in the
password with the escape character (\) or the entire password must be enclosed
in single quotation marks.
Examples: Test\!01 and Test!01
NOTE: Use /enterprise/... instead of /opt/siemens/... if Integrated

Deployment is present.
In principle, we do not describe the Integrated Deployment setup in this instalA31003-S5070-J100-12-7631, 02/2013
349
lation guide but only mention it occasionally (see Section 2.1, Deployment
Scenarios, on page 25).
All checks
Execute the following command to perform all available checks:
/opt/siemens/servicetools/sanitychk/sanityChk.pl
These checks also comprise checks of the Container category, which demand
specifying the administrator password (see option -p in Table 31 on page 355).
The check results are displayed on the screen.
One check
If you want to perform only one check, use the following syntax:
/opt/siemens/servicetools/sanitychk/sanityChk.pl -f <check_name>
Example of the check as to whether sufficient disk space is available:
/opt/siemens/servicetools/sanitychk/sanityChk.pl -f chkDiskSpace
Only one or all checks can be started with one command. The following example
is not allowed
:
/opt/siemens/servicetools/sanitychk/sanityChk.pl -f chkDiskSpace | chkLogDirPermission
A check may return the following values:
OK
NotOK
Skipped
ApplNotInstalled
Off
You find details of possible checks in Section 5.4.2.3, List of available Checks,
on page 351.
Help texts
You receive a check description by using the following syntax:
/opt/siemens/servicetools/sanitychk/sanityChk.pl -d <check_name>
Example:
/opt/siemens/servicetools/sanitychk/sanityChk.pl -d chkDiskSpace
350
A31003-S5070-J100-12-7631, 02/2013
Log file
Executing the program is logged in the /var/siemens/common/log/
sanity_checks.log log file.
NOTE: /log/sanity_checks.log is used for Integrated Deployment.
In principle, we do not describe the Integrated Deployment setup in this installation guide but only mention it occasionally (see Section 2.1, Deployment
5.4.2.3 List of available Checks

All available checks are divided in the following categories:
Container
Database management system
Application
Operating system
Tomcat
Container
Container comprises all OpenSOA services for the OpenScape UC Application
as a whole. The PBX services are not included.
IMPORTANT: If you want to perform checks of the Container category, you
definitely need to apply the -p <administrator password> option (see
Table 31 on page 355).
chkEventContext
The configuration file .../common/conf/eventingContext.xml is
checked as to whether it contains the primary IP address in the
<constructor-arg> tag.
If Small Deployment is present, the <constructor-arg> tag may have
value localhost. The primary IP address or the primary name of the
application computer must have been entered in the deployment scenarios
Large Deployment and Very Large Deployment.
chkFileExist
A31003-S5070-J100-12-7631, 02/2013
351
A check is performed as to whether a defined set of configuration files of the

OpenScape UC Application exists. If one or several of the expected files do
not exist, the check delivers the result NotOK. The following files are currently
checked:
container-keystore_5da1e680-f1e0-11d9-bbed0002a5d5c51b-localhost.p12
chkGuidInjection
The configuration of the OpenScape UC Application uses GUIDs in almost
every configuration file. The configuration file names contain GUIDs, too.
Especially as some GUIDs are used in several configuration files it is
important that these GUIDs are consistent across all configuration files. Since
checking all GUIDs requires a deep mutual understanding of the GUIDs, a
manual check is very complex.
chkInstallParams
During the setup the system is configured according to the information in the
response file. This check tests all parameters of the responsefile.txt
file. You find this file in the /opt/siemens/servicetools/conf directory.
NOTE: The responsefile.txt file is not the response file created by the
configuration of the OpenScape UC Application setup (see Section 5.2,
Configuring the Installation, on page 195). The responsefile.txt file
was created during the setup.
chkIsConfiguredOK
The existence of the .config file is checked, as this file must be available
after a successful installation.
chkMajorAlarm
A logging procedure is performed at the container with the user account and
the password from the internal response file. The systemState service then
retrieves all alarms with priority MAJOR from the alarm database (Solid-DB).
If one or more of such priority MAJOR alarms were found, the result of the
check is value NotOK. If the database management system or/and the
container do not run, this check returns value Skipped.
In the Database management systems category there is a similar check
called chkAlarms, but this check is performed without using the OpenSOA
container.
chkSystemXml
The .../common/conf/system.xml file contains node information and is
a central file of the OpenScape UC Application. The node list in this file is
compared with the node list in the internal response file.
352
A31003-S5070-J100-12-7631, 02/2013
chkTime
A logging procedure is performed at the container with the user account and
the password from the internal response file. The systemState service then
retrieves the times of all nodes. These node times are compared with the
reference time, thus the time on the primary node. If the difference between
a node time and the reference time is greater than 500 ms, the check fails.
A node is here a computer on which container services, thus of the
OpenScape UC Application, are executed. If the PBX operates on an
individual computer, this computer is not part of the container. Nodes are thus
the following computers:
Deployment scenario Small Deployment
Deployment scenario Large Deployment
All media server computers
All frontend computers
Deployment scenario Very Large Deployment
All media server computers
All frontend computers
Database management system
chkAlarms
After logging in to the alarm database (Solid-DB) with the user account and
the password from the internal response file, this database is queried as to
whether it contains alarms of the MAJOR priority. When such an alarm was
found, the result of the check is value NotOK.
If the database management system does not run, this check is marked with
Skipped.
In the Container category there is a similar check called chkMajorAlarm, but
contrary to chkAlarms this check does not directly query the Solid database
but performs the query using the systemState service of the OpenSOA
container.
chkDBMSLogin
After logging in to the alarm database (Solid-DB) with the user account and
the password from the internal response file, the symuser table is retrieved
from this database for user symdb.
A31003-S5070-J100-12-7631, 02/2013
353
If the database management system does not run, this check is marked with
Skipped.
Application
chkDLS
The database connection string is checked in the .../WEB-INF/classes/
dboptions.properties file of the DLS web application used in Tomcat.
In case of a single-installation this string has the following value:
DLS_DB_CONNECTION_URL=jdbc:solid://<IP address of the
node>:<DB port>/dba/<password>
In addition, a connection is checked by use of the following command:
wget --no-check-certificate https://<IP address of the
node>:<DB port>/DeploymentService
chkRG8700
The .../common/conf/system.xml file is searched for an RG8700 entry
to check whether RG8700 was correctly installed.
Example:
<Node displayname="RG8700" guid="rg8700-responsibility-guid"
host="127.0.0.1" jGroupsPort="7800" serviceContainer="false"
type="RG8700"></Node>
Operating system
chkDiskSpace
The harddisk space is checked. At least 1024 MB must be available. This
value can be set. It is the recommended minimum space for successfully
performing an upgrade.
NOTE: Only the harddisk memory on the file system that hosts the
OpenScape UC Application is examined.
The value 1024 MB can be edited in the following line of the /opt/siemens/
servicetools/sanitychk/chksdir/os/chkDiskSpace.pm file:
$MIN_DISK_SPACE = "1024";
chkLogDirPermission
The OpenScape UC Container must have write privileges for user
<SYM_USER> and the group <SYM_GROUP> in the log file
<SYMPHONIA_LOG>. If these write privileges are not set, the OpenScape UC
Application has difficulty in booting.
<SYM_USER>, <SYM_GROUP> and <SYMPHONIA_LOG> are set in the /etc/
sysconfig/siemens/symphonia configuration file.
354
chkStackSize
A31003-S5070-J100-12-7631, 02/2013
The operating system command ulimit -s is executed to check whether

the stack size is unlimited. Value unlimited is not allowed since it may
strongly reduce the system's performance.
Tomcat
chkTomcat
The .../share/tomcat/shared/classes/SymProxy.properties
configuration file is checked whether it exists and if the connector for the
js_soc entry was set correctly in this file.
Example of a connector entry:
# Modified by SymProxy class during port or ip addr
reconfiguration
URI1=js-soc://218.1.12.229:4711
5.4.2.4 Options
The following table describes the options of the /opt/siemens/
servicetools/sanitychk/sanityChk.pl command.
Option
Description
No option. All checks of all categories are performed and important information (silent
mode) is put out on the screen. Even without option entries are made in the
<LOG_DIR>/sanity_checks.log log file.
These checks also comprise checks of the Container category, which demand specifying
the administrator password (see option -p).
-v
Comprehensive information is displayed on the monitor during the execution (verbose

mode). Information that goes further beyond is written in the <LOG_DIR>/
sanity_checks.log log file.
-c <category>
All checks of a category are performed. <category> may have value os, dbms,
container, tomcat or appl. This corresponds to the above categories operating
system, database management system, container, Tomcat and application.
Example: sanityCheck.pl -c os
The default value is all.
The -c option may be used only once per sanityCheck.pl invocation.
-l
List of all available checks
-f <check name>
Only the check named <check name> is performed.

Example: sanityCheck.pl -f chkStackSize
Table 31
Options of sanityCheck.pl
A31003-S5070-J100-12-7631, 02/2013
355
Option
Description
-d <check name>
or
-d <category>
No check is performed, but the help text for the check named <check name> is
displayed on the monitor.
Example: sanityCheck.pl -d chkStackSize
The -d option may be used only once per sanityCheck.pl -d <check name>
invocation.
If you specify a category name instead of a check name, the help texts of all checks of
this category are displayed on the monitor.
Example: sanityCheck.pl -d container
The -d option may be used only once per sanityCheck.pl -d <category>
invocation.
-p <administrator
password>
OpenSOA administrator password. This password is required for the container login.
If you want to perform checks of the Container category, you definitely need to apply the
-p <administrator password> option.
Note: SLES interprets an exclamation mark (!) in a password as repetition of the last
command. To avoid this, you need to prefix each exclamation mark in the password with
the escape character (\) or the entire password must be enclosed in single quotation
marks.
Examples: Test\!01 and Test!01
-o <output format>
Display of the check result either in table format (value table) or in color representation
(value color). The default value is table.
Example 1:
sanityCheck.pl -o table
Example 2:
sanityCheck.pl -o color
-h
Display of the options with a short description on the monitor.
-x
The output portion Result table over all Sanity Checks is not displayed on
the screen (see Section 5.4.2.5, Example Execution, on page 357).
This option applies for the current call only.
-t
Activating the debug mode to store detailed information in the /var/siemens/

common/log/sanity_checks.log file. This option delivers more details than the -v
option.
Table 31
356
Options of sanityCheck.pl
A31003-S5070-J100-12-7631, 02/2013
5.4.2.5 Example Execution

:/enterprise/servicetools/sanitychk # ./sanityChk.pl
###### Starting sanity checks
Using settings from internal responsefile '/enterprise/servicetools/install/conf /
responsefile.txt'.
Using Logfile '/log/sanity_checks.log'.
Run check
Run check
Run check
Run check
Run check
Run check
Run check
Run check
NotOK
Run check
Run check
Run check
Run check
Run check
Run check
Run check
Run check
Run check
'chkDLS'..... ApplNotInstalled
'chkRG8700'..... OK
'chkEventContext'..... OK
'chkFilesExist'..... OK
'chkGuidInjection'..... OK
'chkInstallParams'..... OK
'chkIsConfiguredOK'..... OK
'chkMajorAlarms'..... MajorAlarms detected, check logfile for details.
'chkSystemXml'..... OK
'chkTime'..... OK
'chkAlarms'..... OK
'chkDBMSLogin'..... OK
'chkDBMSLoginOld'..... OK
'chkDiskSpace'..... OK
'chkLogDirPermission'..... OK
'chkStackSize'..... NotOK
'chkTomcat'..... ApplNotInstalled
Result table over all Sanity Checks

04/23/09 15:45 Page : 1
---------------------------------------------------------------Check Category Checkname Result
---------------------------------------------------------------appl chkDLS.pm ApplNotInstalled
chkRG8700.pm OK
container chkEventContext.pm OK
chkFilesExist.pm OK
chkGuidInjection.pm OK
chkInstallParams.pm OK
chkIsConfiguredOK.pm OK
chkMajorAlarms.pm NotOK
chkSystemXml.pm OK
chkTime.pm OK
dbms chkAlarms.pm OK
chkDBMSLogin.pm OK
chkDBMSLoginOld.pm OK
os chkDiskSpace.pm OK
chkLogDirPermission.pm OK
chkStackSize.pm NotOK
tomcat chkTomcat.pm ApplNotInstalled
------------------------- End of Sanity Check results -----------
A31003-S5070-J100-12-7631, 02/2013
357
Trouble Ticket
5.5 Trouble Ticket

If you wish to create a trouble ticket, execute the following command on the
computer on which the error occurred:
bash /opt/siemens/servicetools/install/bin/collect.sh
Attach the result to the trouble ticket.
358
A31003-S5070-J100-12-7631, 02/2013
IG_ConfigOpenScape.fm
Configuring the OpenScape UC Application
Lists of the Ports to be opened
6 Configuring the OpenScape UC Application

1. Open the required firewall ports according to Section 6.1, Lists of the Ports
to be opened, on page 359.
2. Perform configurations according to Section 6.3, Connecting an OpenScape
Voice, on page 479 or Section 6.4, Connecting a HiPath 4000, on page
484.
Section 6.5, Installing the Licenses, on page 485and Section 6.6, Creating
the OpenScape UC Application Users in the CMP, on page 485 refer to
required information.
6.1 Lists of the Ports to be opened

This section lists port information for the following deployment scenarios:
Lists of the Ports to be opened for Integrated Deployment
Lists of Ports to be opened for Small Deployment
Lists of Ports to be opened for Large Deployment
Lists of Ports to be opened for Very Large Deployment
This information is provided as a first input for network and firewall administrators.
IMPORTANT: All remaining ports must be closed by the server administrator to
reduce vulnerability.
A31003-S5070-J100-12-7631, 02/2013
359
6.1.1 Representation of the Port Information

6.1.1.1 Basic Representation
The port information in the tables shown in the following sections marks the
endpoints of communication connections. A connection between any port on the
Web Client computer and port 8443 on the application computer is described as
follows in the respective tables:
Deployment Small Deployment: Application Computer
Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
Comment
TCP
Any
HTTPS access of the Web Client

to the CMP via the OpenScape
frontend services
If an HTTP connection is used instead of

an HTTPS connection, port 7789 must
be open instead of port 8443.
...
8443
Web Client
computer
...
Table 32
Ports to be opened on the Application Computer
1 Receive port (I), send port (O), receive and send port (I/O)
Deployment Scenario Small Deployment: Web Client Computer

Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
TCP
8443
HTTPS access for the Web Client

to the OpenScape frontend
services
Comment
...
Any
Table 33
Application
computer
Ports to be opened on the Web Client Computer
NOTE: Sometimes, the connections begin and end on the same computer.
6.1.1.2 Advanced Representation

In some cases additional information is given about software components and the
interface in which the connection begins or ends. The next two tables contain
details of a connection between the following endpoints:
360
A31003-S5070-J100-12-7631, 02/2013
Software component OpenScape Voice, which is found on the application

computer and can be addressed under the interface name sipsm_*_vip and
listens or sends to port 5060
NOTE: The * character in the interface name sipsm_*_vip is a wildcard for a
character string.
Software on the Desktop Client computer that listens and sends to port 5060.
Deployment Scenario Small Deployment: Application Computer

Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
Comment
I/O
5060
SIP Call control
Unencrypted connection
...
5060
UDP
(OpenS
cape
Voice;
sipsm_*
_vip)
Desktop
client
computer
...
Table 34
Deployment Scenario Integrated Deployment: Desktop Client Computer

Port
Trans
port
proto
col
I/O1 Partner
computer
5060
UDP
I/O
Partner
port
Application 5060
computer
(OpenScap
e Voice;
sipsm_*_vip
)
Protocol / use
Comment
SIP Call control
...
Table 35
Ports to be opened on the Desktop Client Computer
You find these entries again in Table 37 on page 365 and Table 40 on page 375.
A connection may start and end on the same computer:
A31003-S5070-J100-12-7631, 02/2013
361
Deployment Scenario Integrated Deployment: Application Computer

I/O1 Partner
computer
Partner
port
Protocol / use
Comment
5060
UDP
(OpenS
cape
Voice;
nafo1)
I/O
Application
computer
(OpenScap
e Media
Services)
5060
SIP Call control
5060
UDP
(OpenS
cape
Media
Service
s)
I/O
Application
computer
(OpenScap
e Voice;
nafo1)
5060
SIP Call control
Port
Trans
port
proto
col
...
...
Table 36
You find these entries again in Table 37 on page 365.
362
A31003-S5070-J100-12-7631, 02/2013
6.1.2 Lists of the Ports to be opened for Integrated

Deployment
The following figure shows the structure of the deployment scenario Integrated
Deployment:
OpenScape
Mobile Clients
OpenScape Clients
Web Conference System

PSTN and Internet
Facade Server
OpenScape
Web Client
Demilitarized Zone
(DMZ)
OpenScape
Desktop Client
OpenScape
Extensions
Telephones
Data Center Network

Data and
Voice Network
OpenScape
XPR System
Secure Netw
Directory Sys
Instant Mesaging Sys
Collaboration System (e.g. M
Groupware System (e.g. IBM Lotus D
Ba
Fro ck E CMP
nd
nt
En
Se
Me
dS
rvic
dia
erv
es
Op
Se
ice
rvic
enS
s
Vo
e
c
s
ice ape
A31003-S5070-J100-12-7631, 02/2013
Application Computer
(if applicable active & redundant )
363
In this section you find the following tables for the deployment scenario Integrated
Deployment:
364
Ports to be opened on the Mobile Client Facade Server Computer
Ports to be opened on the Admin Client Computer
Ports to be opened on the OpenScape UC Application Desktop Client

Computers
Ports to be opened on the Mobile Client Computer
Ports to be opened on the Deployment Service Server Computer
Ports to be opened on the Deployment Service Client Computer
Ports to be opened on Phones, Computers with a Softphone and Gateways
Ports to be opened on the LDAP Server Computer
Ports to be opened on the Exchange Server Computer
Ports to be opened on the Microsoft Office Communications Server/Microsoft

Lync Server Computer
Ports to be opened on the Lotus Domino Server Computer
Ports to be opened on the Instant-Messaging Server Computer
Ports to be opened on the NTP Server Computer
Ports to be opened on the Web Collaboration Computer
Ports to be opened on the Google Apps Computer
Ports to be opened on the CA MySQL Database Computer
A31003-S5070-J100-12-7631, 02/2013
The following table describes the ports that must have been opened on the
Port
Trans
port
proto
col
I/O1 Partner
computer
21
TCP
22
TCP
88
TCP
111
UDP
and
TCP
161
UDP
162
Partner
port
Protocol / use
Comment
FTP
If FTP server is activated (active mode)

SLES 11 SP2 default is active. The
application computer should not act as
FTP server. FTP is not required by the
Admin client Any

computer
SSH access to the OpenScape

UC Application server for
administration and service
This port needs to be opened only for

service technicians or Unix
administrators working for the customer.
Port 22 is the default port, which can be
configured in SLES differently.
(FTP/SFTP)
backup
server
computer
Port for the file transfer of a

backup of the system
Any
HTTP
Reserved for future purpose. This port

must not be used by any other
application.
111
RPC communication between

NFS server and NFS client
This port only must be open, if the NFS

server or NFS client is installed on the
application computer and if the
installation sources are provided
remotely according to Section 5.3.1.3,
Creating a Repository in osc-setup by
using remote Installation Sources, on
page 243).
Port, on which an SNMP agent

receives queries of the SNMP
manager
Generic SNMP receiver which receives

SNMP requests and forwards them to
the registered SNMP agents. 161 is the
default port for SNMP queries.
UDP
Port in the SNMP manager to

which SNMP traps of the agent
are sent
Generic UDP forwarder which receives

SNMP traps and forwards them to the
registered trap receivers. 162 is the
default port for SNMP traps.
443
TCP
Admin client Any

computer
HTTPS access with the web

browser to the CMP
443 is the default port for HTTPS. It is

required for SSDP, for example.
444
TCP
I/O
Any
HTTPS access to the Apache web

server to access software
provided for the OpenScape
Branch Assistant, software for
DLS, firmware for telephones etc.
Table 37
Any
Any
A31003-S5070-J100-12-7631, 02/2013
365

Port
Trans
port
proto
col
I/O1 Partner
computer
500
UDP
I/O
Partner
port
General
Protocol / use
Comment
IPSec
This port must only be opened if IPsec

(Internet Protocol Security) is used.
Attention: If the firewall uses filters on
the basis of the IP protocol, the data
traffic for the Encapsulating Security
Payload (ESP) and Authentication
Header protocols must be let pass. ESP
is displayed by the value 50 in the
Protocol field of the IP header, AH is
displayed by the value 51 in the
Protocol field of the IP header.
The SLES built-in firewall has a check
box to activate or deactivate IPsec.
514
UDP
2049
UDP
and
TCP
4444
TCP
4500
UDP
I/O
Any
2049
Syslog Port for Audit
This port is closed by default but must

be opened if an external audit
application is used.
NFS communication between


page 243).
Port to connect to the OpenScape

Voice User Management (HPUM)
Element Manager of Symphonia
for synchronization with the
HPUM.
General
IPsec control
This port must be opened only if IPsec

(Internet Protocol Security) is used and
the client is behind a NAT.
is displayed by value 50 in the Protocol
field of the IP header, AH is displayed by
value 51 in the Protocol field of the IP
header.
Table 37
366
A31003-S5070-J100-12-7631, 02/2013

Port
Trans
port
proto
col
I/O1 Partner
computer
4560
TCP
Connector for 3rd party tools (e.g. This port is closed per default, but must
chainsaw) to get logging
be opened for extended diagnostics at
information out of Symphonia.
the customer site.
4561
TCP
chainsaw) to connect to the online be opened for extended diagnostics at
trace service to get trace
the customer site.
4708
TCP
Mobile
Client
Facade
server
computer
Any
Optional SOAP/HTTP access of

the Mobile Client Facade server
computer to the application
computer
4708
TCP
Desktop
client
computer
Any

the Desktop Client to the
application computer
4709
TCP
Mobile
Client
Facade
server
computer
Any
Optional SOAP/HTTPS access of

computer
4709
TCP
Desktop
client
computer
Any
SOAP/HTTPS access of the

desktop client to the application
computer
4709 is the default port.
4709
TCP
Google
Apps
computer
Any

computer
4710
TCP
Instantmessaging
server
computer
Any
Secure IP connectivity between

the Openfire Authentication
provider and the application
computer by means of js-soc via
SSL or TLS
Required between Symphonia nodes.

The secure IP connectivity requires
appropriate certificates.
4711
TCP
Instantmessaging
server
computer
Any
Unencrypted IP connectivity
between the Openfire
Authentication provider and the
application computer by means of
js-soc via TCP
I/O
Application
computer
(OpenScap
e Media
Services)
5062
SIP Call control
5060
UDP
(OpenS
cape
Voice;
nafo1)
Table 37
Partner
port
Protocol / use
Comment
A31003-S5070-J100-12-7631, 02/2013
367

I/O1 Partner
computer
Partner
port
Protocol / use
Comment
5060
UDP
(OpenS
cape
Voice;
nafo1)
I/O
Devices
5060
SIP Call control
5060
UDP
(OpenS
cape
Voice;
sipsm_*
_vip)
I/O
Desktop
client
computer
5060
SIP Call control
5060
TCP
(OpenS
cape
Voice;
nafo1)
I/O
Application
computer
(OpenScap
e Media
Services)
5062
SIP Call control
5060
TCP
(OpenS
cape
Voice;
nafo1)
I/O
Devices
5060
SIP Call control
5060
TCP
(OpenS
cape
Voice;
sipsm_*
_vip)
I/O
Desktop
client
computer
5060
SIP Call control
5061
TCP
(OpenS
cape
Voice;
nafo1)
I/O
Application
computer
(OpenScap
e Media
Services)
5063
SIP Call control
Unencrypted connection (TLS)
5061
TCP
(OpenS
cape
Voice;
nafo1)
I/O
Devices
5061
SIP Call control
Encrypted connection (TLS)
5061
TCP
(OpenS
cape
Voice;
sipsm_*
_vip)
I/O
Desktop
client
computer
5061
SIP Call control
Port
Table 37
368
Trans
port
proto
col
A31003-S5070-J100-12-7631, 02/2013

I/O1 Partner
computer
Partner
port
Protocol / use
Comment
5062
UDP
(OpenS
cape
Media
Service
s)
I/O
Application
computer
(OpenScap
e Voice;
nafo1)
5060
SIP Call control
5062
TCP
(OpenS
cape
Media
Service
s)
I/O
Application
computer
(OpenScap
e Voice;
nafo1)
5060
SIP Call control
5063
TCP
(OpenS
cape
Media
Service
s)
I/O
Application
computer
(OpenScap
e Voice;
nafo1)
5061
SIP Call control
Unencrypted connection (TLS)
6155
UDP
ActiveMQ: Multicast;
This port is used for discovery and error

search.
7500
UDP
Jgroups multicast port for

diagnostics messages.
7800
TCP
Jgroups TCP port used for

Symphonia service registration
and discovery.
This port is used in cases in which

Multicast is deactivated in the
system.xml file for supporting different
sub-networks.
8070
TCP
Voice portal browser
Only local access to the OpenScape UC

Application server. This port can remain
closed in a firewall.
8080
TCP
HTTP connector for Tomcat.
This port is not used because the CMP

always uses HTTPS.
8099
TCP
I/O
HTTP connector for the

Symphonia SPML Provisioning
endpoint running in Tomcat.
If you use HTTPS instead of HTTP, use

port 9943.
8162
UDP
DSA trap recipient as registered

trap recipient (see above)
This port is configured in the

UDPForwarderConfig.xml file.
8167
UDP
Symphonia SNMP service as

registered SNMP agent

SNMPReceiverConfig.xml file.
8443
TCP

frontend services
If an HTTP connection is used instead of

an HTTPS connection, port 7789 must
Port
Table 37
Trans
port
proto
col
Web Client
computer
Any
A31003-S5070-J100-12-7631, 02/2013
369

Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
8768
TCP
Application
computer
Any
SOAP interface used by

OpenScape UC Application for
translating phone numbers
Any
Any
Communication from the system

monitor to the media server
The system monitor is an EXE file that

need not be installed but can be copied
to any computer. This monitor connects
to port 9000 of the media server by
default. Port 9000 can be configured in
the configuration file of the media
server.
HTTPS connector for the

If you use HTTP instead of HTTPS, use

port 8099.
9000
9943
TCP
I/O
10001
TCP
12345
TCP
16750
TCP
(FTP/SFTP)
backup
server
computer
20000- UDP
24999 2
(OpenS
cape
Media
Service
s)
I/O
Devices3
45566
Table 37
370
UDP
OpenScape
-Xpressions
server
computer
Comment
This port must be open for connections

coming from the OpenScape
Xpressions server
Used with HiPath SPA Assistant
Observer
HISPA Assistant Service port

Note: HISPA is not supported yet.

20000249992
RTP for payload transmission of

voice and video and
RTCP for controlling RTP
There is always an RTCP control

channel besides an RTP payload
channel, so that the total number of
channels is always an even number.
The port number range for RTP and
RTCP begins with 20000 by default.
2500 channels are reserved by default,
so that the ports 20000 to 24999 are
allocated. The start port number (20000)
as well as the number of channels can
be configured in the CMP.
JGroups multicast port for

and discovery.

Multicast is activated in the
system.xml file. This is the default
setting. JCS and JGroups are not
compatible, so JCS must use a port
different from the one JGroups uses.
A31003-S5070-J100-12-7631, 02/2013

Port
Trans
port
proto
col
I/O1 Partner
computer
45567
UDP
JCS multicast port for Symphonia This port is used in cases in which
service registration and discovery. Multicast is activated in the
system.xml file (default setting). JCS
and JGroups are not compatible, so JCS
must use a port different from the one
JGroups uses.
61616
TCP
Active MQ JMS messaging

system for sending and receiving
Symphonia events.
Any
TCP
Exchange
server
computer
25
SMTP access for OpenScape UC

application system e-mails sent
from the application computer to
the Exchange server computer
Any
TCP
Exchange
server
computer
443
HTTPS-WebDAV access to the

OWA server
Any
TCP
Exchange
server
computer
80
HTTP-WebDAV access to the

OWA server
Any
TCP
Any
TCP/
UDP
Any
Any
Table 37
Partner
port
Protocol / use
Comment
443 is the default port for HTTPS.
Web
80
Collaboratio
n computer
HTTP
In case a web conference was started in

a browser with a click on the Start web
conference (globe icon) button, the
computer on which the frontend
services operate acts as proxy server for
downloading the fastviewer.exe file.
This requires Port 80 to be open on the
Web Collaboration computer for an
HTTP communication.
NTP server
computer
123
Network Time Protocol
The NTP server computer might be e. g.

a Windows domain server.
TCP
Instantmessaging
server
computer
5262
Access to the instant-messaging 5262 is the Openfire default port for

server by means of XMPP/TCP or XMPP connectivity. Openfire can handle
XMPP/TLS
secure as well as insecure data traffic
via this port.
TCP
Lotus
Domino
server
computer
1352
NRPC (Notes-RPC)
A31003-S5070-J100-12-7631, 02/2013
371

Port
Trans
port
proto
col
I/O1 Partner
computer
Any
TCP
I/O
Partner
port
Microsoft
483
Office
Communica
tions
Server/
Protocol / use
Comment
Microsoft Office Communications

Port 483 is the default port. It can be

changed on the OpenScape UC
Application side.
RPC.MOUNTD communication
between NFS server and NFS
client
The port only must be open, if the NFS

page 243). The source port and the
destination port of this communication
are determined dynamically.
Microsoft
Lync
Server
computer
Any
Table 37
UDP
and
TCP
Any
Any
2 Default value that can be configured in the CMP
3 Devices are here RTP devices, thus phones, computers with a softphone and gateways.
372
A31003-S5070-J100-12-7631, 02/2013
The following table describes the ports that must have been opened on the Mobile
Client Facade server computer.
Deployment Scenario Integrated Deployment: Mobile Client Facade Server Computer
Port
Trans
port
proto
col
I/O1 Partner
computer
111
UDP
and
TCP
2049
UDP
and
TCP
8081
TCP
8443
Partner
port
Protocol / use
Comment
Any
111


mobile client facade server computer
and if the installation sources are
provided remotely according to Section
5.3.1.3, Creating a Repository in oscsetup by using remote Installation
Sources, on page 243).
Any
2049


Mobile
client
computer
Any
Optional HTTP access of the

Mobile Client to the OpenScape
services
TCP
Mobile
client
computer
Any
HTTPS access of the Mobile

Client to the OpenScape services
Any
TCP
Application
computer
4708

computer
Any
TCP
Application
computer
4709

computer
Any
UDP
and
TCP
Any
Any
client
Table 38

Sources, on page 243). The source
port and the destination port of this
communication are determined
dynamically.
A31003-S5070-J100-12-7631, 02/2013
373
The following table describes the ports that must have been opened on the admin
client computer.
Deployment Scenario Integrated Deployment: Admin Client Computer
Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
Comment
Any
TCP
Application
computer
22


Any
TCP
Application
computer
443

browser to the CMP

Any
TCP
Instantmessaging
server
computer
9090
Optional HTTP access from the

web browser to the Openfire
management
Any
TCP
Instantmessaging
server
computer
9091
HTTPS access from the web

browser to the Openfire
management
Table 39
374
A31003-S5070-J100-12-7631, 02/2013
client computer.
Port
Trans
port
proto
col
I/O1 Partner
computer
5060
UDP
I/O
5060
TCP
5061
20000249992
Protocol / use
Comment
Application 5060
computer
(OpenScap
e Voice;
sipsm_*_vip
)
SIP Call control
I/O
Application 5060
computer
(OpenScap
e Voice;
sipsm_*_vip
)
SIP Call control
TCP
I/O
Application 5061
computer
(OpenScap
e Voice;
sipsm_*_vip
)
SIP Call control
UDP
I/O
Application
computer
(OpenScap
e Media
Services)

voice and video and
Restriction: This port range needs to be

released only if a softphone is installed
on the desktop client computer.
Any
Any
Table 40
TCP
Partner
port
20000249992

allocated. The start port number
(20000) as well as the number of
channels can be configured in the CMP.
LDAP
server
computer
LDAP access
Web
80
Collaboratio
n server
computer
HTTP
Ports to be opened on the OpenScape UC Application Desktop Client Computers
A31003-S5070-J100-12-7631, 02/2013
375

Port
Trans
port
proto
col
I/O1 Partner
computer
Any
TCP
Web
443
Collaboratio
n server
computer
HTTPS
Any
TCP
Web
5000
Collaboratio
n server
computer
Proprietary OpenScape Web

Collaboration protocol
DLS server
computer
18443
Deployment service server

computer.
DLS client
8082
Server-client connection
Partner
port
Protocol / use
Any
TCP
Application
computer
4708

Any
TCP
Application
computer
4709

computer
Table 40
Comment
376
A31003-S5070-J100-12-7631, 02/2013
The following table describes the ports that must have been opened on the Web
Client computer.
Deployment Scenario Integrated Deployment: Web Client Computer
Port
Trans
port
proto
col
I/O1 Partner
computer
Any
TCP
Web
80
Collaboratio
n server
computer
HTTP
Any
TCP
Web
443
Collaboratio
n server
computer
HTTPS
Any
TCP
Web
5000
Collaboratio
n server
computer

Any
TCP
Application
computer
7789
HTTP access for the Web Client to

the OpenScape frontend services
Any
TCP
Application
computer
8443

services
Table 41
Partner
port
Protocol / use
Comment
A31003-S5070-J100-12-7631, 02/2013
377
Client computer.
Deployment Scenario Integrated Deployment: Mobile Client Computer
Port
Trans
port
proto
col
I/O1 Partner
computer
Any
TCP
Web
80
Collaboratio
n server
computer
HTTP
Any
TCP
Web
443
Collaboratio
n server
computer
HTTPS
Any
TCP
Web
5000
Collaboratio
n server
computer

Any
TCP
Mobile
Client
Facade
server
computer
8081

services
Any
TCP
Mobile
Client
Facade
server
computer
8443

Table 42
Partner
port
Protocol / use
Comment
The following table describes the ports that must have been additionally opened
on the Deployment Service server computer.
Deployment Scenario Integrated Deployment: Deployment Service Server Computer (DLS)
Port
18443
Table 43
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
Comment
Desktop
client
computer
378
A31003-S5070-J100-12-7631, 02/2013
on the Deployment Service client computer.
Deployment Scenario Integrated Deployment: Deployment Service Client Computer
Port
Trans
port
proto
col
I/O1 Partner
computer
8082
Partner
port
Desktop
client
computer
Table 44
Protocol / use
Comment
Server-client connection.
on devices (phones and gateways).
Deployment Scenario Integrated Deployment: Devices (Phones, Computers with a Softphone and Gateways)
Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
Comment
5060
UDP
I/O
Application
computer
(OpenScap
e Voice;
nafo1)
5060
SIP Call control
5060
TCP
I/O
Application
computer
(OpenScap
e Voice;
nafo1)
5060
SIP Call control
5061
TCP
I/O
Application
computer
(OpenScap
e Voice;
nafo1)
5061
SIP Call control
20000249992
UDP
I/O
Application
computer
(OpenScap
e Media
Services)
20000249992

voice and video and

Table 45
A31003-S5070-J100-12-7631, 02/2013
379
on the LDAP server computer.
Deployment Scenario Integrated Deployment: LDAP Server Computer
Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
UDP
Any
LDAP access
Table 46
Desktop
client
computer
Comment
on the Exchange server computer.
Deployment Scenario Integrated Deployment: Exchange Server Computer
Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
25
TCP
Application
computer
Any

443
TCP
Application
computer
Any

OWA server
80
TCP
Application
computer
Any

OWA server
Table 47
Comment
on the Microsoft Office Communications server/Microsoft Lync server computer.
Deployment Scenario Integrated Deployment: Microsoft Office Communications Server/Microsoft Lync Server
Computer
Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
483
TCP
I/O
Any

Table 48
Application
computer
Comment
Ports to be opened on the Microsoft Office Communications Server/Microsoft Lync Server Computer
on the Lotus Domino server computer.
380
A31003-S5070-J100-12-7631, 02/2013
Deployment Scenario Integrated Deployment: Lotus Domino Server Computer

Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
1352
TCP
Any
NRPC (Notes-RPC)
Table 49
Application
computer
Comment
on the instant-messaging server computer (XMPP) provided that this computer
exists (see Section 12.2, Infrastructure, on page 596).
Deployment Scenario Integrated Deployment: Instant-Messaging Server Computer (XMPP)
Port
Trans
port
proto
col
I/O1 Partner
computer
111
UDP
and
TCP
2049
UDP
and
TCP
5262
TCP
9090
9091
Table 50
Partner
port
Protocol / use
Comment
Any
111


Any
2049


Application
computer
Any

server by means of XMPP/TCP or XMPP connectivity. Openfire can
handle secure as well as insecure data
XMPP/TLS
traffic via this port.
TCP
Admin client Any

computer

management
TCP
Admin client Any

computer
HTTPS access to the web browser

to the Openfire management
A31003-S5070-J100-12-7631, 02/2013
381
Deployment Scenario Integrated Deployment: Instant-Messaging Server Computer (XMPP)

Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
Comment
Any
TCP
Application
computer
4710

SSL or TLS

Any
TCP
Application
computer
4711
js-soc via TCP
Any
UDP
and
TCP
Any
Any
client
Table 50

instant-messaging server computer and
if the installation sources are provided
on the NTP server computer.
Deployment Scenario Integrated Deployment: NTP Server Computer
Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
Comment
123
TCP/
UDP
Any
The NTP server computer might be

e. g. a Windows domain server.
Table 51
Application
computer
382
A31003-S5070-J100-12-7631, 02/2013
on the Web Collaboration server computer.
Deployment Scenario Integrated Deployment: Web Collaboration Server Computer

Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
802
TCP
Client
computer3
Any
HTTP
80
TCP
Application
computer
Any
HTTP
4432
TCP
Client
computer3
Any
HTTPS
1434
UDP
Web
Any
Collaboratio
n server
computer
Proprietary Microsoft protocol for

the communication from the nth
Web Collaboration server
computer to the first Web
Collaboration server computer
Restriction:
This port needs to be opened only on
the first of possibly several Web
Collaboration server computers.4
1500
TCP
Web
Any
Collaboratio
n server
computer

Restriction:
50002
TCP
Client
computer3
Any

5004
TCP
Application
computer
Any
XML-RPC
Any
UDP
Web
1434
Collaboratio
n server
computer

Restriction:
the second and on any further of
possibly several Web Collaboration
server computers.4
Any
TCP
Web
1500
Collaboratio
n server
computer

Restriction:
server computers.4
Table 52
Comment

services operate acts as proxy server
for downloading the fastviewer.exe
file. This requires Port 80 to be open on
the Web Collaboration computer for an
HTTP communication.
1 I: Inbound connection from the partner port on the partner computer to the port on the Web Collaboration server computer; O: Outbound
connection from the port on the Web Collaboration server computer to the partner port on the partner computer
A31003-S5070-J100-12-7631, 02/2013
383
2 Port 80 must always be open. Port 443 and Port 5000 are, in contrast, optional. A client first tries to connect port 5000 on the Web
Collaboration server computer via a proprietary OpenScape Web Collaboration protocol. If this attempt fails, the client tries to set up an
HTTPS connection with port 443 on the Web Collaboration server computer. If this fails, too, an HTTP connection with port 80 is established.
A connection with port 5000 is the most effective version, since the HTTP overhead or HTTPS overhead is left out.
3 For example, Desktop Client computer, Web Client computer and Mobile Client computer
4 If several Web Collaboration server computers are available, the one that hosts Microsoft SQL Server 2005 Express is the first one.
384
A31003-S5070-J100-12-7631, 02/2013
on the Google Apps computer.
Deployment scenario Integrated Deployment: Google Apps Computer

Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
Any
TCP
Application
computer
4709

computer
Any
TCP
Proxy
server
computer
8080
HTTP connector
Table 53
Comment
When migrating the OpenScape ComAssistant to the OpenScape UC

Application, the CA MySQL database can be on a different computer (the CA
MySQL database computer) than the CA migration computer (see Table 133 on
page 970). CA stands for OpenScapce ComAssistant. The following table
describes the ports that must have been additionally opened on the CA MySQL
database computer:
Deployment scenario Integrated Deployment: CA MySQL Database Computer
Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
3306
TCP
I/O
CA
migration
computer
Any
Database connector to the CA

MySQL database
8170
TCP
I/O
CA
migration
computer
Any
HiPath CAP management

communication over HTTP
This is used for importing and exporting

purposes, see step 4 on page 987 and
8470
TCP
I/O
CA
migration
computer
Any

communication over HTTPS

Table 54
Comment
A31003-S5070-J100-12-7631, 02/2013
385
6.1.3 Lists of Ports to be opened for Small

Deployment
The following figure shows the structure of the deployment scenario Small
Deployment:
OpenScape
Mobile Clients
OpenScape Clients

PSTN and Internet
Facade Server
OpenScape
Web Client
Demilitarized Zone
(DMZ)
OpenScape
Desktop Client
OpenScape
Extensions
Telephones
OpenScape Voice
or
HiPath 4000
Data and
Voice Network
Data Center Network
Co
mm
S y unic
ste
a
m tion
s
OpenScape
XPR System
Secure Network
Directory System (e.g. LDAP)
Collaboration System (e.g. Microsoft OCS)

Groupware System (e.g. IBM Lotus Domino)
Ba
CM
Fro ck-e
P
n
ntend d Ser
Me
vi
dia
Se
rvic ces
Se
rvic
es
es
386
A31003-S5070-J100-12-7631, 02/2013
In this section you find the following tables for the deployment scenario Small
Deployment:
Ports to be opened on the PBX Computers

Computers

A31003-S5070-J100-12-7631, 02/2013
387
Port
Trans
port
proto
col
I/O1 Partner
computer
21
TCP
22
TCP
Partner
port
Protocol / use
Comment
FTP

SLES 11 SP2 default is
deactivated. The application computer
should not act as FTP server. FTP is
not required by the OpenScape UC
Application.
Admin client Any

computer
SSH access to the OpenScape UC This port needs to be opened only for
Application server for
administrators working for the
customer.
(FTP/SFTP)
backup
server
computer
Port for the file transfer of a backup

of the system
88
TCP
111
UDP
and
TCP
161
UDP

manager
162
UDP

which SNMP traps of the agent are SNMP traps and forwards them to the
sent
443
TCP
Admin client Any

computer

browser to the CMP
444
TCP
I/O
Any

server to access software provided
for the OpenScape Branch
Assistant, software for DLS,
firmware for telephones etc.
Table 55
388
Any
Any
HTTP
111
RPC communication between NFS This port only must be open, if the NFS
server and NFS client
page 243).
Any

application.


A31003-S5070-J100-12-7631, 02/2013

Port
Trans
port
proto
col
I/O1 Partner
computer
500
UDP
I/O
Partner
port
General
Protocol / use
Comment
IPSec

Header protocols must be let pass.
ESP is displayed by the value 50 in the
514
UDP
1099
TCP
2049
UDP
and
TCP
24273
UDP
I/O
4444
TCP
Table 55
Application
computer

ActiveMQ
Must be open between Symphonia

nodes only.
Any
2049
NFS communication between NFS This port only must be open, if the NFS
server and NFS client
page 243).
Computer
of the PBX
(nafo1)
27272
Port used by the MGCP protocol.

The OpenScape Media Services
listen to requests from the PBX's
greeting server.
Voice/HiPath 4000 User
Management (HPUM) Element
Manager of Symphonia for
synchronization with the HPUM.
A31003-S5070-J100-12-7631, 02/2013
389

Port
Trans
port
proto
col
I/O1 Partner
computer
4500
UDP
I/O
Partner
port
General
Protocol / use
Comment
IPsec control

Header protocols must be let pass.
ESP is displayed by value 50 in the
displayed by value 51 in the Protocol
field of the IP header.
This port is closed per default, but must
the customer site.
4560
TCP
Connector for 3rd party tools (e.g.

4561
TCP
the customer site.
4708
TCP
Mobile
Client
Facade
server
computer
Any

computer
4708
TCP
Desktop
client
computer
Any

4709
TCP
Mobile
Client
Facade
server
computer
Any

computer
4709
TCP
Desktop
client
computer
Any

computer
4709
TCP
Google
Apps
computer
Any

computer
4710
TCP
Instantmessaging
server
computer
Any

SSL or TLS

Table 55
390
A31003-S5070-J100-12-7631, 02/2013

Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
Comment
4711
TCP
Instantmessaging
server
computer
Any
js-soc via TCP
5060
UDP
(OpenS
cape
Media
Service
s)
I/O
Computer
of the PBX
(nafo1)
5060
SIP Call control
5060
TCP
(OpenS
cape
Media
Service
s)
I/O
Computer
of the PBX
(nafo1)
5060
SIP Call control
TCP
5061
(OpenS
cape
Media
Service
s)
I/O
Computer
of the PBX
(nafo1)
5061
SIP Call control
6155
UDP
ActiveMQ: multicast.

search.
7500
UDP

7789
TCP
7800
TCP

and discovery.

system.xml file for supporting
different sub-networks.
8070
TCP
Only accessed locally on OpenScape

UC Application server. This port can
remain closed in a firewall.
8080
TCP

always uses HTTPS.
Table 55
Web Client
computer
Any
HTTP access of the Web Client to In the /enterprise/HiPathCA/

the OpenScape frontend services config/common/ports.cfg file this
port can be changed to HTTP1_PORT.If
an HTTPS connection is used instead
of an HTTP connection, port 8443 must
A31003-S5070-J100-12-7631, 02/2013
391

Port
Trans
port
proto
col
I/O1 Partner
computer
8099
TCP
8162
Protocol / use
Comment
I/O


port 9943.
UDP


8167
UDP
Symphonia SNMP Service as

registered SNMP agent.

8443
TCP
9000
Web Client
computer
Any
HTTPS access of the Web Client to If an HTTP connection is used instead

the CMP via the OpenScape
of an HTTPS connection, port 7789
frontend services
must be open instead of port 8443.
Any
Any


server.


port 8099.
9943
TCP
I/O
10001
TCP
12345
TCP
16750
TCP
(FTP/SFTP)
backup
server
computer
I/O
Devices4
20000- UDP
24999 3
(OpenS
cape
Media
Service
s)
Table 55
392
Partner
port
OpenScape
Xpressions
computer

Xpressions server
Observer

Port for the file transfer of a backup

of the system
20000249993

voice and video and

A31003-S5070-J100-12-7631, 02/2013

Port
Trans
port
proto
col
I/O1 Partner
computer
45566
UDP
45567
Protocol / use
Comment

and discovery.

compatible, so JCS must use another
port.
UDP
and JGroups are not compatible, so
JCS must use another port.
61616
TCP
Active MQ JMS messaging system

for sending and receiving
Symphonia events.
Any
TCP
PBX
computer
1040
CSTA connection to the PBX

access
Any
TCP
PBX
computer
22
SSH access to the PBX for

administrator and service
Any
TCP
PBX
computer
22
SSH access of OpenScape UC

Application server to the admin
interface of the PBX (access with
account srx)
Any
TCP
Exchange
server
computer
25

Any
TCP
Exchange
server
computer
443

OWA server
Any
TCP
Exchange
server
computer
80

OWA server
Any
TCP
Table 55
Partner
port
Web
80
Collaboratio
n computer
HTTP
In case a web conference was started

in a browser with a click on the Start
web conference (globe icon) button,
the computer on which the frontend
HTTP communication.
A31003-S5070-J100-12-7631, 02/2013
393

Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
Any
TCP
Instantmessaging
server
computer
5262
Access to the instant-messaging

5262 is the Openfire default port for
XMPP/TLS
Any
TCP
I/O
PBX
computer
8767
Access of the assistant via SOAP

to the admin interface (bound
interface) of the PBX
Any
TCP
I/O
PBX
computer
8768

Any
TCP
I/O
PBX
computer
8769
SOAP
Any
TCP
I/O
PBX
computer
8770
SOAP
Any
TCP/
UDP
NTP server
computer
123
Any
TCP
Lotus
Domino
server
computer
1352
NRPC (Notes-RPC)
Any
TCP
I/O
483
Microsoft
Office
Communica
tions
Server/
Comment



Application side.
client

Microsoft
Lync
Server
computer
Any
Table 55
1
2
3
4
UDP
and
TCP
Any
Any
Receive port (I), send port (O), receive and send port (I/O)
Default value, which can be configured in the PBX
Default value that can be configured in the CMP
Devices are here RTP devices, thus phones, computers with a softphone and gateways.
394
A31003-S5070-J100-12-7631, 02/2013
The following table describes the ports that must be open in the deployment
scenario Small Deployment on the PBX computer in addition to those mentioned
in the notes for the PBX.
Deployment Scenario Small Deployment: PBX Computer
Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
22
TCP
Application
computer
Any

account srx)
1040
TCP
Application
computer
Any
27272
(nafo1)
UDP
I/O
Application
computer
24273
Port used by the MGCP protocol

required by the PBX greeting
server to access the OpenScape
Media Services.
5060
(nafo1)
UDP
I/O
Application
computer
(OpenScap
e Media
Services)
5060
SIP Call control
5060
(nafo1)
UDP
I/O
Devices
5060
SIP Call control
UDP
5060
(sipsm_
*_vip)
I/O
Desktop
client
computer
5060
SIP Call control
5060
(nafo1)
TCP
I/O
Application
computer
(OpenScap
e Media
Services)
5060
SIP Call control
5060
(nafo1)
TCP
I/O
Devices
5060
SIP Call control
5060
TCP
(sipsm_
*_vip)
I/O
Desktop
client
computer
5060
SIP Call control
5061
(nafo1)
TCP
I/O
Application
computer
(OpenScap
e Media
Services)
5061
SIP Call control
5061
(nafo1)
TCP
I/O
Devices
5061
SIP Call control
Table 56
Comment
A31003-S5070-J100-12-7631, 02/2013
395
Deployment Scenario Small Deployment: PBX Computer

I/O1 Partner
computer
Partner
port
Protocol / use
Comment
5061
TCP
(sipsm_
*_vip)
I/O
Desktop
client
computer
5061
SIP Call control
8767
TCP
I/O
Application
computer
Any
Access of the assistantvia SOAP

8768
TCP
I/O
Application
computer
Any

8769
TCP
I/O
Application
computer
Any
SOAP
8770
TCP
I/O
Application
computer
Any
SOAP
Port
Table 56
Trans
port
proto
col
2 Default value, which can be configured in the PBX
396
A31003-S5070-J100-12-7631, 02/2013
Deployment Scenario Small Deployment: Mobile Client Facade Server Computer
Port
Trans
port
proto
col
I/O1 Partner
computer
111
UDP
and
TCP
2049
UDP
and
TCP
8081
TCP
8443
Partner
port
Protocol / use
Comment
Any
111


page 243).
Any
2049


page 243).
Mobile
client
computer
Any

services
TCP
Mobile
client
computer
Any

Any
TCP
Application
computer
4708

computer
Any
TCP
Application
computer
4709

computer
Any
UDP
and
TCP
Any
Any
client
Table 57

dynamically.
A31003-S5070-J100-12-7631, 02/2013
397
client computer.
Deployment Scenario Small Deployment: Admin Client Computer
Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
Comment
Any
TCP
Application
computer
22


Any
TCP
Application
computer
443

browser to the CMP

Any
TCP
Instantmessaging
server
computer
9090

management
Any
TCP
Instantmessaging
server
computer
9091

Table 58
398
A31003-S5070-J100-12-7631, 02/2013
client computer.
Deployment Scenario Small Deployment: Desktop Client Computer
Port
Trans
port
proto
col
I/O1 Partner
computer
5060
UDP
I/O
5060
TCP
5061
20000249992
Protocol / use
Comment
Computer
5060
of the PBX
(sipsm_*_vi
p)
SIP Call control
I/O
Computer
5060
of the PBX
(sipsm_*_vi
p)
SIP Call control
TCP
I/O
Computer
5061
of the PBX
(sipsm_*_vi
p)
SIP Call control
UDP
I/O
Application
computer
(OpenScap
e Media
Services)

voice and video and

Any
Partner
port
20000249992

LDAP
server
computer
LDAP access
Any
TCP
Web
80
Collaboratio
n server
computer
HTTP
Any
TCP
Web
443
Collaboratio
n server
computer
HTTPS
Any
TCP
Web
5000
Collaboratio
n server
computer

Table 59
A31003-S5070-J100-12-7631, 02/2013
399
Deployment Scenario Small Deployment: Desktop Client Computer

Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
DLS server
computer
18443

computer.
DLS client
8082
Any
TCP
Application
computer
4708

Any
TCP
Application
computer
4709

computer
Table 59
Comment
400
A31003-S5070-J100-12-7631, 02/2013
Client computer.
Deployment Scenario Small Deployment: Web Client Computer
Port
Trans
port
proto
col
I/O1 Partner
computer
Any
TCP
Web
80
Collaboratio
n server
computer
HTTP
Any
TCP
Web
443
Collaboratio
n server
computer
HTTPS
Any
TCP
Web
5000
Collaboratio
n server
computer

Any
TCP
Application
computer
7789

Any
TCP
Application
computer
8443

services
Table 60
Partner
port
Protocol / use
Comment
A31003-S5070-J100-12-7631, 02/2013
401
Client computer.
Deployment Scenario Small Deployment: Mobile Client Computer
Port
Trans
port
proto
col
I/O1 Partner
computer
Any
TCP
Web
80
Collaboratio
n server
computer
HTTP
Any
TCP
Web
443
Collaboratio
n server
computer
HTTPS
Any
TCP
Web
5000
Collaboratio
n server
computer

Any
TCP
Mobile
Client
Facade
server
computer
8081

services
Any
TCP
Mobile
Client
Facade
server
computer
8443

Table 61
Partner
port
Protocol / use
Comment
Deployment Scenario Small Deployment: Deployment Service Server Computer (DLS)
Port
18443
Table 62
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
Comment
Desktop
client
computer
on the Deployment Service client computer (DLS).
402
A31003-S5070-J100-12-7631, 02/2013
Deployment Scenario Small Deployment: Deployment Service Client Computer (DLS)

Port
8082
Table 63
Trans
port
proto
col
I/O1 Partner
computer
Desktop
client
computer
Partner
port
Protocol / use
Comment
A31003-S5070-J100-12-7631, 02/2013
403
on devices (phones and gateways).
Deployment Scenario Small Deployment: Devices (Phones, Computers with a Softphone and Gateways)
Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
Comment
5060
UDP
I/O
Computer
of the PBX
(nafo1)
5060
SIP Call control
5060
TCP
I/O
Computer
of the PBX
(nafo1)
5060
SIP Call control
5061
TCP
I/O
Computer
of the PBX
(nafo1)
5061
SIP Call control
20000249992
UDP
I/O
Application
computer
(OpenScap
e Media
Services)
20000249992

voice and video and

Table 64
Deployment Scenario Small Deployment: LDAP Server Computer
Port
Table 65
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
UDP
Any
LDAP access
Desktop
client
computer
Comment
404
A31003-S5070-J100-12-7631, 02/2013
Deployment Scenario Small Deployment: Exchange Server Computer
Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
25
TCP
Application
computer
Any

443
TCP
Application
computer
Any

OWA server
80
TCP
Application
computer
Any

OWA server
Table 66
Comment
Deployment Scenario Small Deployment: Microsoft Office Communications Server/Microsoft Lync Server Computer
Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
483
TCP
I/O
Any

Table 67
Application
computer
Comment
Deployment Scenario Small Deployment: Lotus Domino Server Computer

Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
1352
TCP
Any
NRPC (Notes-RPC)
Table 68
Application
computer
Comment
A31003-S5070-J100-12-7631, 02/2013
405
Deployment Scenario Small Deployment: Instant-Messaging Server Computer (XMPP)
Port
Trans
port
proto
col
I/O1 Partner
computer
111
UDP
and
TCP
2049
UDP
and
TCP
5262
TCP
9090
Partner
port
Protocol / use
Comment
Any
111


instant-messaging computer and if the
page 243).
Any
2049


page 243).
Application
computer
Any

XMPP/TLS
TCP
Admin client Any

computer

management
9091
TCP
Admin client Any

computer

Any
TCP
Application
computer

SSL or TLS
Table 69
406
4710

A31003-S5070-J100-12-7631, 02/2013
Deployment Scenario Small Deployment: Instant-Messaging Server Computer (XMPP)

Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
Any
TCP
Application
computer
4711
js-soc via TCP
Any
UDP
and
TCP
Any
Any
client
Table 69
Comment

Deployment Scenario Small Deployment: NTP Server Computer
Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
Comment
123
TCP/
UDP
Any

Table 70
Application
computer
A31003-S5070-J100-12-7631, 02/2013
407
Deployment Scenario Small Deployment: Web Collaboration Server Computer

Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
802
TCP
Client
computer3
Any
HTTP
80
TCP
Application
computer
Any
HTTP
4432
TCP
Client
computer3
Any
HTTPS
1434
UDP
Web
Any
Collaboratio
n server
computer

Restriction:
1500
TCP
Web
Any
Collaboratio
n server
computer

Restriction:
50002
TCP
Client
computer3
Any

5004
TCP
Application
computer
Any
XML-RPC
Any
UDP
Web
1434
Collaboratio
n server
computer

Restriction:
server computers.4
Any
TCP
Web
1500
Collaboratio
n server
computer

Restriction:
server computers.4
Table 71
Comment

HTTP communication.
408
A31003-S5070-J100-12-7631, 02/2013
A31003-S5070-J100-12-7631, 02/2013
409
Deployment scenario Small Deployment: Google Apps Computer

Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
Any
TCP
Application
computer
4709

computer
Any
TCP
Proxy
server
computer
8080
HTTP connector
Table 72
Comment
410
A31003-S5070-J100-12-7631, 02/2013
6.1.4 Lists of Ports to be opened for Large

Deployment
The following figure shows the structure of the deployment scenario Large
Deployment:
OpenScape
Mobile Clients
OpenScape Clients

PSTN and Internet
Facade Server
OpenScape
Web Client
Demilitarized Zone
(DMZ)
OpenScape
Desktop Client
OpenScape
Extensions
Telephones
Data Center Network
OpenScape Voice
or HiPath 4000
Data and
Voice Network
Media Server Computer

1...4 active in
N+1 redundancy
Me
dia
Front -end Computer

1...4 active in
N+1 redundancy
Fro
nten
dS
Load
Balancer
Co
m
S y mun
ste ica
ms tion
s
OpenScape
XPR System
erv
ice
s
Secure Net
Directory Sy
Collaboration System (e.g. M
Se
rvic
es
Groupware System (e.g. IBM Lotus D
Ba
CM
ck
-en
P
dS
erv
ice
s
IMPORTANT: In the deployment scenario Large Deployment, the OpenScape

frontend services communicate with the OpenScape backend services via
variable, dynamically allocated protocol ports. For this reason, no firewall must be
configured in this deployment scenario between the application computer and the
frontend computer that inhibits this type of communication.
IMPORTANT: Some devices like firewalls separate idle TCP connections after a
specific period without notice. Verify that no such device exists between the
frontend and application computer, because serious instabilities will otherwise
occur during operation. This may become obvious by e.g. the error message
Service unavailable, temporarily impossible logins or empty device lists.
Please note that these errors also occur when a firewall is set in a way that transmissions via closed TCP connections are answered by sending RST messages
(Reset). Please also note that some firewalls separate idle sockets without notice
if they do not filter anything.
A31003-S5070-J100-12-7631, 02/2013
411
All devices must consequently allow unlimited timeouts for connections between
the frontend and application computer. Limited timeouts for inbound client
connections to fend off Denial-of-Service attacks from the internet or intranet
must still be possible, though.
In this section you find the following tables for Large Deployment:
412
Ports to be opened on the Frontend Computers
Ports to be opened on the Media Server Computers

Computers

A31003-S5070-J100-12-7631, 02/2013
Deployment Scenario Large Deployment: Application Computer
Port
Trans
port
proto
col
I/O1 Partner
computer
21
TCP
22
TCP
111
UDP
and
TCP
161
UDP
162
444
Table 73
Protocol / use
Comment
FTP

SLES 11 SP2 default is deactivated.
The application computer should not act
as FTP server. FTP is not required by
Admin client Any

computer


(FTP/SFTP)
backup
server
computer

Any
Partner
port


page 243).

manager

UDP

are sent

TCP
I/O
Any
111
Any

A31003-S5070-J100-12-7631, 02/2013
413

Port
Trans
port
proto
col
I/O1 Partner
computer
500
UDP
I/O
Partner
port
General
Protocol / use
Comment
IPSec

514
UDP
1099
TCP
2049
UDP
and
TCP
4444
TCP
4500
UDP
I/O
Application
computer
Any
2049

ActiveMQ

nodes only.


page 243).

General
IPsec control

header.
Table 73
414
A31003-S5070-J100-12-7631, 02/2013

Port
Trans
port
proto
col
I/O1 Partner
computer
4560
TCP
the customer site.
4561
TCP
the customer site.
4708
TCP
Mobile
Client
Facade
server
computer
Any

computer
4708
TCP
Desktop
client
computer
Any

4709
TCP
Mobile
Client
Facade
server
computer
Any

computer
4709
TCP
Desktop
client
computer
Any

computer
4709
TCP
Google
Apps
computer
Any

computer
4710
TCP
Instantmessaging
server
computer
Any

SSL or TLS

4711
TCP
Instantmessaging
server
computer
Any
js-soc via TCP
6155
UDP
7500
UDP

Table 73
Partner
port
Protocol / use
Comment

search.
A31003-S5070-J100-12-7631, 02/2013
415

Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
Comment
7800
TCP
3000055000
JGroups TCP port used for

and discovery.

8080
TCP

always uses HTTPS.
8099
TCP
I/O


port 9943.
8162
UDP


8167
UDP


9943
TCP
I/O


port 8099.
10001
TCP
12345
TCP
16750
TCP
(FTP/SFTP)
backup
server
computer
16760
TCP
I/O
Media
server
computer
Any
Database connector to the

SolidTech database.
This port must also be open for

connections coming from the frontend
server. This is not explicitly mentioned
here, since all ports must be open
between the application and frontend
computer (see below).
3000055000
TCP
Frontend
computer,
media
server
computer
7800

and discovery.

39399
TCP
I/O
Media
server
computer
4711
between two computers by means
of js-soc via TCP
Table 73
416
Frontend
computer,
media
server
computer

Xpressions server
OpenScape
Xpressions
computer
Observer


A31003-S5070-J100-12-7631, 02/2013

Port
Trans
port
proto
col
I/O1 Partner
computer
45566
UDP
45567
Protocol / use
Comment

and discovery.

port.
UDP
61616
TCP

Symphonia events.
Any
TCP
PBX
computer
1040
Any
TCP
PBX
computer
22

Any
TCP
PBX
computer
22

account srx)
Any
TCP
Media
server
computer
8070
Any
TCP
Exchange
server
computer
25

Any
TCP
Exchange
server
computer
443

OWA server
Any
TCP
Exchange
server
computer
80

OWA server
Any
TCP,
UDP
I/O
Frontend
computer
Any
Table 73
Partner
port
In the deployment scenario Large

Deployment, the OpenScape
frontend services communicate with
the OpenScape backend services via
variable, dynamically allocated
protocol ports. Therefore no firewall
must be configured between these
two OpenScape components since it
hinders this type of communication.
A31003-S5070-J100-12-7631, 02/2013
417

Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
Any
TCP
I/O
PBX
computer
8767

Any
TCP
I/O
PBX
computer
8768

Any
TCP
I/O
PBX
computer
8769
SOAP
Any
TCP
I/O
PBX
computer
8770
SOAP
Any
TCP/
UDP
NTP server
computer
123
Any
TCP
Lotus
Domino
server
computer
1352
NRPC (Notes-RPC)
Any
TCP
I/O
483
Microsoft
Office
Communica
tions
Server/

Comment


Application side.
Microsoft
Lync
Server
computer
Any
Table 73
418
TCP
Instantmessaging
server
computer
5262

XMPP/TLS
A31003-S5070-J100-12-7631, 02/2013

Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
Comment
Any
UDP
4875
OpenScape UC Application uses

multicasting for enabling
communication between the
frontend server and the
234.8.7.5 is the multicasting address

the frontend computer knows as
multicasting address also.
234.8.7.5
Port 4875 on 234.8.7.5 is the default

port. A different port may also be
configured.
The same IP address and port must be
selected as target as from the frontend
computer (see Table 75 on page 422).
This multicast is completely
independent from the multicast in the
setup configuration).
No receive port that monitors
connections coming from 234.8.7.5
needs to be open on the application
computer, since these connections
appear on the application computer as if
they originated from the frontend
computer.
If the routing schema Multicast is not
possible, you need to follow the
instructions in Section 6.2, Routing
Schemas between the Application
Computer and Frontend Computer, on
page 476 for Unicast. No specific ports
need to open, since in the deployment
scenario Large Deployment all ports
between the application computer and
the frontend computer must be open.
Any
Table 73
UDP
and
TCP
Any
Any
client

A31003-S5070-J100-12-7631, 02/2013
419
scenario Large Deployment on the PBX computer in addition to those mentioned
in the notes for the PBX.
Deployment Scenario Large Deployment: PBX Computer
Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
22
TCP
Application
computer
Any

account srx)
1040
TCP
Application
computer
Any
CSTA connection from the

application computer to the PBX
27272
(nafo1)
UDP
I/O
Media
server
computer
24273

Media Services.
5060
(nafo1)
UDP
I/O
Media
server
computer
5060
SIP Call control
5060
(nafo1)
UDP
I/O
Devices
5060
SIP Call control
5060
UDP
(sipsm_
*_vip)
I/O
Desktop
client
computer
5060
SIP Call control
5060
(nafo1)
TCP
I/O
Media
server
computer
5060
SIP Call control
5060
(nafo1)
TCP
I/O
Devices
5060
SIP Call control
5060
TCP
(sipsm_
*_vip)
I/O
Desktop
client
computer
5060
SIP Call control
5061
(nafo1)
TCP
I/O
Media
server
computer
5061
SIP Call control
5061
(nafo1)
TCP
I/O
Devices
5061
SIP Call control
5061
TCP
(sipsm_
*_vip)
I/O
Desktop
client
computer
5061
SIP Call control
8767
I/O
Application
computer
Any

Table 74
420
TCP
Comment
A31003-S5070-J100-12-7631, 02/2013
Deployment Scenario Large Deployment: PBX Computer

Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
8768
TCP
I/O
Application
computer
Any

8768
TCP
I/O
Frontend
computer
Any
SOAP interface for translating

phone numbers
8768
TCP
I/O
Media
server
computer
Any

phone numbers
8769
TCP
I/O
Application
computer
Any
SOAP
8770
TCP
I/O
Application
computer
Any
SOAP
4900066000
TCP
I/O
Media
server
computer
50603
SIP Call control
Table 74
Comment
A31003-S5070-J100-12-7631, 02/2013
421
frontend computers.
Deployment Scenario Large Deployment: Frontend Computer
Port
Trans
port
proto
col
I/O1 Partner
computer
22
TCP
111
UDP
and
TCP
443
TCP
2029
UDP
and
TCP
4708
TCP
4709
7789
Table 75
422
Partner
port
(FTP/SFTP)
backup
server
computer
Any
Protocol / use
Comment



frontend computer and if the installation
sources are provided remotely
according to Section 5.3.1.3, Creating
a Repository in osc-setup by using
remote Installation Sources, on page
243).
Admin client Any

computer

browser to the CMP
Any
2049


243).
Mobile
Client
Facade
server
computer
Any

computer
TCP
Mobile
Client
Facade
server
computer
Any

computer
TCP
Web Client
computer
Any

111
A31003-S5070-J100-12-7631, 02/2013

Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
Comment
7800
TCP
I/O
Application
computer,
frontend
computer,
media
server
computer
3000055000

and discovery.

8443
TCP
Web Client
computer
Any

frontend services
If an HTTP connection is used instead

16750
TCP
(FTP/SFTP)
backup
server
computer
3000055000
TCP
I/O
Application
computer,
frontend
computer,
media
server
computer
7800
Any
TCP,
UDP
I/O
Application
computer
Any
Any
TCP
Table 75

Web
80
Collaboratio
n computer

and discovery.

In the deployment scenario Large

Deployment, the OpenScape
HTTP

HTTP communication.
A31003-S5070-J100-12-7631, 02/2013
423

Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
Comment
Any
UDP
4875


the application computer knows as
234.8.7.5

configured.
selected as target as from the
application computer (see Table 73 on
page 413).
needs to be open on the frontend
appear on the frontend computer as if
they originated from the application
computer.
scenario Large Deployment all ports
between the application computer and
the frontend computer must be open.
Any
TCP
Any
UDP
and
TCP
Table 75
424
I/O
PBX
computer
8768

phone numbers
Any
Any
client

243). The source port and the
A31003-S5070-J100-12-7631, 02/2013
A31003-S5070-J100-12-7631, 02/2013
425
The following table describes the ports that must have been opened on the media
server computers.
Deployment Scenario Large Deployment: Media Server Computer
Port
Trans
port
proto
col
I/O1 Partner
computer
22
TCP
88
TCP
111
UDP
and
TCP
2049
UDP
and
TCP
4708
TCP
4709
2000
Table 76
426
Partner
port
(FTP/SFTP)
backup
server
computer
Protocol / use
Comment

Any
HTTP

application.
Any
111


media server computer and if the
page 243).
Any
2049


page 243).
Mobile
Client
Facade
server
computer
Any

computer
TCP
Mobile
Client
Facade
server
computer
Any

computer
TCP
I/O
Media
server
computer
2000
Replication of the greeting sound Restriction: This port must only be

files available on a media server open if there are more than one
computer to another media server media server computers.
Computer.
2000 is the preset port. It may have
been changed in the IP port for file
replication field in the Prompt
Replication Group Definition dialog
A31003-S5070-J100-12-7631, 02/2013

Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
24273
UDP
I/O
Computer
of the PBX
(nafo1 or
ncs_ip_alia
s_1)
27272

listen to and send upon requests
from the greeting server in the
PBX.
4711
TCP
I/O
Application
computer
39399
of js-soc via TCP
50603
UDP
I/O
Computer
of the PBX
(nafo1)
5060
SIP Call control
50603
TCP
I/O
Computer
of the PBX
(nafo1)
5060
SIP Call control
50603
TCP
I/O
Computer
of the PBX
(nafo1)
4900066000
SIP Call control
50613
TCP
I/O
Computer
of the PBX
(nafo1)
5061
SIP Call control
7800
TCP
I/O
Application
computer,
frontend
computer,
media
server
computer
3000055000

and discovery.

8070
TCP
Application
computer
Any
HTTP
Any
Any


server.
Media
server
computer
11110
Control of the greeting audio file

Restriction: This port must only be
replication from one media server open if there are more than one
computer.
been changed in the IP port field in the
Prompt Replication Group Definition
dialog
9000
111103
Table 76
TCP
I/O
Comment
A31003-S5070-J100-12-7631, 02/2013
427

Port
Trans
port
proto
col
I/O1 Partner
computer
16750
TCP
(FTP/SFTP)
backup
server
computer
20000249993
UDP
I/O
Devices4
20000249993

voice and video and

3000055000
TCP
I/O
Application
computer,
frontend
computer,
media
server
computer
7800

and discovery.

Any
TCP
I/O
PBX
computer
8768

phone numbers
Any
TCP
I/O
Application
computer
16760
Database connector to the

SolidTech database.
Any
UDP
and
TCP
Any
Any
client
Table 76
1
2
3
4
Partner
port
Protocol / use
Comment


428
A31003-S5070-J100-12-7631, 02/2013
Deployment Scenario Large Deployment: Mobile Client Facade Server Computer
Port
Trans
port
proto
col
I/O1 Partner
computer
111
UDP
and
TCP
2049
UDP
and
TCP
8081
TCP
8443
Partner
port
Protocol / use
Comment
Any
111


Any
2049


Mobile
client
computer
Any

services
TCP
Mobile
client
computer
Any

Any
TCP
Application
computer
4708

computer
Any
TCP
Frontend
computer
4708

computer
Any
TCP
Media
server
computer
4708

computer
Any
TCP
Application
computer
4709

computer
Any
TCP
Frontend
computer
4709

computer
Table 77
A31003-S5070-J100-12-7631, 02/2013
429
Deployment Scenario Large Deployment: Mobile Client Facade Server Computer

Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
Any
TCP
Media
server
computer
4709

computer
Any
UDP
and
TCP
Any
Any
client
Table 77
Comment

dynamically.
430
A31003-S5070-J100-12-7631, 02/2013
client computer.
Deployment Scenario Large Deployment: Admin Client Computer
Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
Comment
Any
TCP
Application
computer
22


Any
TCP
Frontend
computer
443

browser to the CMP
Any
TCP
Instantmessaging
server
computer
9090

management
Any
TCP
Instantmessaging
server
computer
9091

Table 78
A31003-S5070-J100-12-7631, 02/2013
431
client computer.
Deployment Scenario Large Deployment: Desktop Client Computer
Port
Trans
port
proto
col
I/O1 Partner
computer
5060
UDP
I/O
5060
TCP
5061
20000249992
Partner
port
Protocol / use
Comment
Computer
5060
of the PBX
(sipsm_*_vi
p)
SIP Call control
I/O
Computer
5060
of the PBX
(sipsm_*_vi
p)
SIP Call control
TCP
I/O
Computer
5061
of the PBX
(sipsm_*_vi
p)
SIP Call control
UDP
I/O
Media
server
computer

voice and video and

20000249992

Any
LDAP
server
computer
LDAP access
DLS server
computer
18443

computer.
DLS client
8082
Any
TCP
Web
80
Collaboratio
n server
computer
HTTP
Any
TCP
Web
443
Collaboratio
n server
computer
HTTPS
Table 79
432
A31003-S5070-J100-12-7631, 02/2013
Deployment Scenario Large Deployment: Desktop Client Computer

Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
Any
TCP
Application
computer
4708

Any
TCP
Application
computer
4709

computer
Any
TCP
Web
5000
Collaboratio
n server
computer
Table 79
Comment

A31003-S5070-J100-12-7631, 02/2013
433
Client computer.
Deployment Scenario Large Deployment: Web Client Computer
Port
Trans
port
proto
col
I/O1 Partner
computer
Any
TCP
Web
80
Collaboratio
n server
computer
HTTP
Any
TCP
Web
443
Collaboratio
n server
computer
HTTPS
Any
TCP
Web
5000
Collaboratio
n server
computer

Any
TCP
Frontend
computer
7789

Any
TCP
Frontend
computer
8443

services
Table 80
Partner
port
Protocol / use
Comment
434
A31003-S5070-J100-12-7631, 02/2013
Client computer.
Deployment Scenario Large Deployment: Mobile Client Computer
Port
Trans
port
proto
col
I/O1 Partner
computer
Any
TCP
Web
80
Collaboratio
n server
computer
HTTP
Any
TCP
Web
443
Collaboratio
n server
computer
HTTPS
Any
TCP
Web
5000
Collaboratio
n server
computer

Any
TCP
Mobile
Client
Facade
server
computer
8081

services
Any
TCP
Mobile
Client
Facade
server
computer
8443

Table 81
Partner
port
Protocol / use
Comment
Deployment Scenario Large Deployment: Deployment Service Server Computer (DLS)
Port
18443
Table 82
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
Comment
Desktop
client
computer
A31003-S5070-J100-12-7631, 02/2013
435
Deployment Scenario Large Deployment: Deployment Service Client Computer (DLS)
Port
Trans
port
proto
col
I/O1 Partner
computer
8082
Partner
port
Desktop
client
computer
Table 83
Protocol / use
Comment
on devices (phones, computers with a softphone and gateways).
Deployment Scenario Large Deployment: Devices (Phones, Computers with a Softphone and Gateways)
Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
Comment
5060
UDP
I/O
Computer
of the PBX
(nafo1)
5060
SIP Call control
5060
TCP
I/O
Computer
of the PBX
(nafo1)
5060
SIP Call control
5061
TCP
I/O
Computer
of the PBX
(nafo1)
5061
SIP Call control
20000249992
UDP
I/O
Application
computer
(OpenScap
e Media
Services)
20000249992

voice and video and

Table 84
436
A31003-S5070-J100-12-7631, 02/2013
Deployment Scenario Large Deployment: LDAP Server Computer

Port
Table 85
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
UDP
Any
LDAP access
Desktop
client
computer
Comment
A31003-S5070-J100-12-7631, 02/2013
437
Deployment Scenario Large Deployment: Exchange Server Computer
Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
25
TCP
Application
computer
Any

443
TCP
Application
computer
Any

OWA server
80
TCP
Application
computer
Any

OWA server
Table 86
Comment
Deployment Scenario Large Deployment: Microsoft Office Communications Server/Microsoft Lync Server Computer
Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
483
TCP
I/O
Any

Table 87
Application
computer
Comment
Deployment Scenario Large Deployment: Lotus Domino Server Computer

Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
1352
TCP
Any
NRPC (Notes-RPC)
Table 88
Application
computer
Comment
438
A31003-S5070-J100-12-7631, 02/2013
Deployment Scenario Large Deployment: Instant-Messaging Server Computer (XMPP)
Port
Trans
port
proto
col
I/O1 Partner
computer
111
UDP
and
TCP
2049
UDP
and
TCP
5262
TCP
9090
Partner
port
Protocol / use
Comment
Any
111


page 243).
Any
2049


Application
computer
Any

XMPP/TLS
TCP
Admin client Any

computer

management
9091
TCP
Admin client Any

computer

Any
TCP
Application
computer

SSL or TLS
Table 89
4710

A31003-S5070-J100-12-7631, 02/2013
439
Deployment Scenario Large Deployment: Instant-Messaging Server Computer (XMPP)

Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
Any
TCP
Application
computer
4711
js-soc via TCP
Any
UDP
and
TCP
Any
Any
client
Table 89
Comment

Deployment Scenario Large Deployment: NTP Server Computer
Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
Comment
123
TCP/
UDP
Any

Table 90
Application
computer
440
A31003-S5070-J100-12-7631, 02/2013
Deployment Scenario Large Deployment: Web Collaboration Server Computer

Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
802
TCP
Client
computer3
Any
HTTP
80
TCP
Frontend
computer
Any
HTTP
4432
TCP
Client
computer3
Any
HTTPS
1434
UDP
Web
Any
Collaboratio
n server
computer

Restriction:
1500
TCP
Web
Any
Collaboratio
n server
computer

Restriction:
50002
TCP
Client
computer3
Any

5004
TCP
Application
computer
Any
XML-RPC
Any
UDP
Web
1434
Collaboratio
n server
computer

Restriction:
server computers.4
Any
TCP
Web
1500
Collaboratio
n server
computer

Restriction:
server computers.4
Table 91
Comment

HTTP communication.
A31003-S5070-J100-12-7631, 02/2013
441
442
A31003-S5070-J100-12-7631, 02/2013
Deployment scenario Large Deployment: Google Apps Computer
Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
Any
TCP
Application
computer
4709

computer
Any
TCP
Proxy
server
computer
8080
HTTP connector
Table 92
Comment
A31003-S5070-J100-12-7631, 02/2013
443
6.1.5 Lists of Ports to be opened for Very Large

Deployment
The following figure shows the structure of a cluster of the deployment scenario
Very Large Deployment:
PSTN and Internet
OpenScape Clients
OpenScape
Web Client
OpenScape
Mobile Clients
OpenScape
Extensions
In N+1 redundancy
MS SQL Server
Cluster for
OpenScape Web
Collaboration
OpenScape
Desktop Client
Demilitarized Zone
(DMZ)
Telephones
Facade Server in
N+1 redundancy
Data and Voice

Network
Front -end Computer
1...4 active in
N+1 redundancy
Media Server Computer

1...5 active in
N+1 redundancy
Op
e
V o nSc
ice ape
Fro
nten
dS
erv
ice
s
Openfire System
Collaboration System
(e.g. Microsoft OCS)
OpenScape
XPR System
Vid
Me eo a
nd/
dia
o
Se
rvic r Aud
io
es
Directory System (e.g. LDAP)
Cluster-overlapping
Components
Data Center Network
Cluster
Load Balancer
Ba
CM
cken
P
dS
erv
ice
s
Cluster-individual
Components
(if applicable activ & redundant )
Please obtain details about the meaning of a cluster from the OpenScape UC
Application Planning Guide.
444
A31003-S5070-J100-12-7631, 02/2013
IMPORTANT: In the deployment scenario Very Large Deployment, the

OpenScape frontend services communicate with the OpenScape backend
services via variable, dynamically allocated protocol ports. For this reason, no
firewall must be configured in this deployment scenario between the application
computer and the frontend computer that inhibits this type of communication.
IMPORTANT: Some devices like firewalls separate idle TCP connections after a
specific period without notice. Verify that no such device exists between the
frontend and application computer, because serious instabilities will otherwise
occur during operation. This may become obvious by e.g. the error message
Service unavailable, temporarily impossible logins or empty device lists.
Please note that these errors also occur when a firewall is set in a way that transmissions via closed TCP connections are answered by sending RST messages
(Reset). Please also note that some firewalls separate idle sockets without notice
if they do not filter anything.
All devices must consequently allow unlimited timeouts for connections between
the frontend and application computer. Limited timeouts for inbound client
connections to fend off Denial-of-Service attacks from the internet or intranet
must still be possible, though.
A31003-S5070-J100-12-7631, 02/2013
445
In this section you find the following tables for Very Large Deployment:
446

Computers

Ports to be opened on the computer for MS SQL server cluster for

A31003-S5070-J100-12-7631, 02/2013
Deployment Scenario Very Large Deployment: Application Computer
Port
Trans
port
proto
col
I/O1 Partner
computer
21
TCP
22
TCP
111
UDP
and
TCP
161
UDP
162
444
Table 93
Protocol / use
Comment
FTP

SLES 11 SP2 default is deactivated.
The application computer should not act
as FTP server. FTP is not required by
Admin client Any

computer


(FTP/SFTP)
backup
server
computer

Any
Partner
port


page 243).

manager

UDP

are sent

TCP
I/O
Any
111
Any

A31003-S5070-J100-12-7631, 02/2013
447

Port
Trans
port
proto
col
I/O1 Partner
computer
500
UDP
I/O
Partner
port
General
Protocol / use
Comment
IPSec

514
UDP
1099
TCP
2049
UDP
and
TCP
3306
TCP
Application
computer
I/O

ActiveMQ

nodes only.
page 243).
Any
2049

Media
server
computer
Any
Database connector to the MySQL This port must also be open for
database.
connections coming from the frontend
server. This is not explicitly mentioned
here, since all ports must be open
between the application and frontend
computer (see below).
Port 3306 is specified by parameter
SI_DB_PORT in the /root/
knut.responsefile.txt file. This
file was edited in step 6 on page 219.
4444
Table 93
448
TCP

A31003-S5070-J100-12-7631, 02/2013

Port
Trans
port
proto
col
I/O1 Partner
computer
4500
UDP
I/O
Partner
port
General
Protocol / use
Comment
IPsec control

header.
4560
TCP
the customer site.
4561
TCP
the customer site.
4708
TCP
Mobile
Client
Facade
server
computer
Any

computer
4708
TCP
Desktop
client
computer
Any

4709
TCP
Mobile
Client
Facade
server
computer
Any

computer
4709
TCP
Desktop
client
computer
Any

computer
4709
TCP
Google
Apps
computer
Any

computer
4710
TCP
Instantmessaging
server
computer
Any

SSL or TLS

Table 93
A31003-S5070-J100-12-7631, 02/2013
449

Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
4711
TCP
Any
js-soc via TCP
6155
UDP
7500
UDP

7800
TCP
8080
TCP
8099
Instantmessaging
server
computer

search.

and discovery.


always uses HTTPS.
TCP
I/O


port 9943.
8162
UDP


8167
UDP


9943
TCP
I/O


port 8099.
10001
TCP
12345
TCP
16750
TCP
(FTP/SFTP)
backup
server
computer
3000055000
TCP
Frontend
computer,
media
server
computer
7800

and discovery.
39399
TCP
I/O
Media
server
computer
4711
of js-soc via TCP
Table 93
450
Frontend
computer,
media
server
computer
3000055000
Comment
OpenScape
Xpressions
computer

Xpressions server
Observer



A31003-S5070-J100-12-7631, 02/2013

Port
Trans
port
proto
col
I/O1 Partner
computer
45566
UDP
45567
Protocol / use
Comment

and discovery.

port.
UDP
61616
TCP

Symphonia events.
Any
TCP
PBX
computer
1040
Any
TCP
PBX
computer
22

Any
TCP
PBX
computer
22

account srx)
Any
TCP
Media
server
computer
8070
Any
TCP
Exchange
server
computer
25

Any
TCP
Exchange
server
computer
443

OWA server
Any
TCP
Exchange
server
computer
80

OWA server
Any
TCP,
UDP
I/O
Frontend
computer
Any
Table 93
Partner
port
In the deployment scenario Very

Large Deployment, the OpenScape
A31003-S5070-J100-12-7631, 02/2013
451

Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
Any
TCP
I/O
PBX
computer
8767

Any
TCP
I/O
PBX
computer
8768

Any
TCP
I/O
PBX
computer
8769
SOAP
Any
TCP
I/O
PBX
computer
8770
SOAP
Any
TCP/
UDP
NTP server
computer
123
Any
TCP
Lotus
Domino
server
computer
1352
NRPC (Notes-RPC)
Any
TCP
I/O
483
Microsoft
Office
Communica
tions
Server/

Comment


Application side.
Microsoft
Lync
Server
computer
Table 93
452
A31003-S5070-J100-12-7631, 02/2013

Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
Any
TCP
Instantmessaging
server
computer
5262

XMPP/TLS
Any
UDP
234.8.7.5
4875

Comment

the frontend computer knows as
configured.
selected as target as from the frontend
computer (see Table 75 on page 422).
needs to be open on the application
appear on the application computer as if
they originated from the frontend
computer.
scenario Very Large Deployment all
ports between the application computer
and the frontend computer must be
open.
Table 93
A31003-S5070-J100-12-7631, 02/2013
453
scenario Very Large Deployment on the PBX computer in addition to those
mentioned in the notes for the PBX.
Deployment Scenario Very Large Deployment: PBX Computer
Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
22
TCP
Application
computer
Any

account srx)
1040
TCP
Application
computer
Any
CSTA connection from the

application computer to the PBX
27272
(nafo1)
UDP
I/O
Media
server
computer
24273

Media Services.
5060
(nafo1)
UDP
I/O
Media
server
computer
5060
SIP Call control
5060
(nafo1)
UDP
I/O
Devices
5060
SIP Call control
5060
UDP
(sipsm_
*_vip)
I/O
Desktop
client
computer
5060
SIP Call control
5060
(nafo1)
TCP
I/O
Media
server
computer
5060
SIP Call control
5060
(nafo1)
TCP
I/O
Devices
5060
SIP Call control
5060
TCP
(sipsm_
*_vip)
I/O
Desktop
client
computer
5060
SIP Call control
5061
(nafo1)
TCP
I/O
Media
server
computer
5061
SIP Call control
5061
(nafo1)
TCP
I/O
Devices
5061
SIP Call control
5061
TCP
(sipsm_
*_vip)
I/O
Desktop
client
computer
5061
SIP Call control
8767
I/O
Application
computer
Any

Table 94
454
TCP
Comment
A31003-S5070-J100-12-7631, 02/2013
Deployment Scenario Very Large Deployment: PBX Computer

Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
8768
TCP
I/O
Application
computer
Any

8768
TCP
I/O
Frontend
computer
Any

phone numbers
8768
TCP
I/O
Media
server
computer
Any

phone numbers
8769
TCP
I/O
Application
computer
Any
SOAP
8770
TCP
I/O
Application
computer
Any
SOAP
4900066000
TCP
I/O
Media
server
computer
50603
SIP Call control
Table 94
Comment
A31003-S5070-J100-12-7631, 02/2013
455
frontend computers.
Deployment Scenario Very Large Deployment: Frontend Computer
Port
Trans
port
proto
col
I/O1 Partner
computer
22
TCP
111
UDP
and
TCP
443
TCP
2049
UDP
and
TCP
4708
TCP
4709
7789
Table 95
456
Partner
port
(FTP/SFTP)
backup
server
computer
Any
Protocol / use
Comment



243).
Admin client Any

computer

browser to the CMP
Any
2049


243).
Mobile
Client
Facade
server
computer
Any

computer
TCP
Mobile
Client
Facade
server
computer
Any

computer
TCP
Web Client
computer
Any

111
A31003-S5070-J100-12-7631, 02/2013

Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
Comment
7800
TCP
I/O
Application
computer,
frontend
computer,
media
server
computer
3000055000

and discovery.

8443
TCP
Web Client
computer
Any

frontend services
If an HTTP connection is used instead

16750
TCP
(FTP/SFTP)
backup
server
computer
3000055000
TCP
I/O
Application
computer,
frontend
computer,
media
server
computer
7800
Any
TCP,
UDP
I/O
Application
computer
Any
Any
TCP
Table 95

Web
80
Collaboratio
n computer

and discovery.

In the deployment scenario Very

Large Deployment, the OpenScape
HTTP

HTTP communication.
A31003-S5070-J100-12-7631, 02/2013
457

Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
Comment
Any
UDP
4875


the application computer knows as
234.8.7.5

configured.
selected as target as from the
application computer (see Table 73 on
page 413).
needs to be open on the frontend
appear on the frontend computer as if
they originated from the application
computer.
scenario Very Large Deployment all
ports between the application computer
and the frontend computer must be
open.
Any
Table 95
TCP
I/O
PBX
computer
8768

phone numbers
458
A31003-S5070-J100-12-7631, 02/2013
The following table describes the ports that must have been opened on the media
server computers.
Deployment Scenario Very Large Deployment: Media Server Computer
Port
Trans
port
proto
col
I/O1 Partner
computer
22
TCP
88
TCP
111
UDP
and
TCP
2049
UDP
and
TCP
4708
TCP
4709
2000
Table 96
Partner
port
(FTP/SFTP)
backup
server
computer
Protocol / use
Comment

Any
HTTP

application.
Any
111


page 243).
Any
2049


page 243).
Mobile
Client
Facade
server
computer
Any

computer
TCP
Mobile
Client
Facade
server
computer
Any

computer
TCP
I/O
Media
server
computer
2000
Replication of the greeting sound Restriction: This port must only be

files available on a media server open if there are more than one
Computer.
been changed in the IP port for file
replication field in the Prompt
Replication Group Definition dialog
A31003-S5070-J100-12-7631, 02/2013
459

Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
24273
UDP
I/O
Computer
of the PBX
(nafo1 or
ncs_ip_alia
s_1)
27272

listen to and send upon requests
from the greeting server in the
PBX.
4711
TCP
I/O
Application
computer
39399
of js-soc via TCP
50603
UDP
I/O
Computer
of the PBX
(nafo1)
5060
SIP Call control
50603
TCP
I/O
Computer
of the PBX
(nafo1)
5060
SIP Call control
50603
TCP
I/O
Computer
of the PBX
(nafo1)
4900066000
SIP Call control
50613
TCP
I/O
Computer
of the PBX
(nafo1)
5061
SIP Call control
7800
TCP
I/O
Application
computer,
frontend
computer,
media
server
computer
3000055000

and discovery.

8070
TCP
Application
computer
Any
HTTP
Any
Any


server.
Media
server
computer
11110
Control of the greeting audio file

Restriction: This port must only be
replication from one media server open if there are more than one
computer.
been changed in the IP port field in the
Prompt Replication Group Definition
dialog
9000
111103
Table 96
460
TCP
I/O
Comment
A31003-S5070-J100-12-7631, 02/2013

Port
Trans
port
proto
col
I/O1 Partner
computer
16750
TCP
(FTP/SFTP)
backup
server
computer
20000249993
UDP
I/O
Devices4
20000249993

voice and video and

3000055000
TCP
I/O
Application
computer,
frontend
computer,
media
server
computer
7800

and discovery.

Any
TCP
I/O
Application
computer
3306
Database connector to the MySQL Port 3306 is specified by parameter

database.
SI_DB_PORT in the /root/
knut.responsefile.txt file. This
file was edited in step 6 on page 219.
Any
TCP
I/O
PBX
computer
8768

phone numbers
Table 96
1
2
3
4
Partner
port
Protocol / use
Comment

A31003-S5070-J100-12-7631, 02/2013
461
Deployment Scenario Very Large Deployment: Mobile Client Facade Server Computer
Port
Trans
port
proto
col
I/O1 Partner
computer
111
UDP
and
TCP
2049
UDP
and
TCP
8081
TCP
8443
Partner
port
Protocol / use
Comment
Any
111


Any
2049


Mobile
client
computer
Any

services
TCP
Mobile
client
computer
Any

Any
TCP
Application
computer
4708

computer
Any
TCP
Frontend
computer
4708

computer
Any
TCP
Media
server
computer
4708

computer
Any
TCP
Application
computer
4709

computer
Table 97
462
A31003-S5070-J100-12-7631, 02/2013
Deployment Scenario Very Large Deployment: Mobile Client Facade Server Computer
Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
Any
TCP
Frontend
computer
4709

computer
Any
TCP
Media
server
computer
4709

computer
Table 97
Comment
A31003-S5070-J100-12-7631, 02/2013
463
client computer.
Deployment Scenario Very Large Deployment: Admin Client Computer
Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
Comment
Any
TCP
Application
computer
22


Any
TCP
Frontend
computer
443

browser to the CMP
Any
TCP
Instantmessaging
server
computer
9090

management
Any
TCP
Instantmessaging
server
computer
9091

Table 98
464
A31003-S5070-J100-12-7631, 02/2013
client computer.
Deployment Scenario Very Large Deployment: Desktop Client Computer
Port
Trans
port
proto
col
I/O1 Partner
computer
5060
UDP
I/O
5060
TCP
5061
20000249992
Partner
port
Protocol / use
Comment
Computer
5060
of the PBX
(sipsm_*_vi
p)
SIP Call control
I/O
Computer
5060
of the PBX
(sipsm_*_vi
p)
SIP Call control
TCP
I/O
Computer
5061
of the PBX
(sipsm_*_vi
p)
SIP Call control
UDP
I/O
Media
server
computer

voice and video and

20000249992

Any
LDAP
server
computer
LDAP access
DLS server
computer
18443

computer.
DLS client
8082
Any
TCP
Web
80
Collaboratio
n server
computer
HTTP
Any
TCP
Web
443
Collaboratio
n server
computer
HTTPS
Table 99
A31003-S5070-J100-12-7631, 02/2013
465
Deployment Scenario Very Large Deployment: Desktop Client Computer

Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
Any
TCP
Application
computer
4708

Any
TCP
Application
computer
4709

computer
Any
TCP
Web
5000
Collaboratio
n server
computer
Table 99
Comment

466
A31003-S5070-J100-12-7631, 02/2013
Client computer.
Deployment Scenario Very Large Deployment: Web Client Computer
Port
Trans
port
proto
col
I/O1 Partner
computer
Any
TCP
Web
80
Collaboratio
n server
computer
HTTP
Any
TCP
Web
443
Collaboratio
n server
computer
HTTPS
Any
TCP
Web
5000
Collaboratio
n server
computer

Any
TCP
Frontend
computer
7789

Any
TCP
Frontend
computer
8443

services
Table 100
Partner
port
Protocol / use
Comment
A31003-S5070-J100-12-7631, 02/2013
467
Client computer.
Deployment Scenario Very Large Deployment: Mobile Client Computer
Port
Trans
port
proto
col
I/O1 Partner
computer
Any
TCP
Web
80
Collaboratio
n server
computer
HTTP
Any
TCP
Web
443
Collaboratio
n server
computer
HTTPS
Any
TCP
Web
5000
Collaboratio
n server
computer

Any
TCP
Mobile
Client
Facade
server
computer
8081

services
Any
TCP
Mobile
Client
Facade
server
computer
8443

Table 101
Partner
port
Protocol / use
Comment
Deployment Scenario Very Large Deployment: Deployment Service Server Computer (DLS)
Port
18443
Table 102
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
Comment
Desktop
client
computer
468
A31003-S5070-J100-12-7631, 02/2013
Deployment Scenario Very Large Deployment: Deployment Service Client Computer (DLS)
Port
Trans
port
proto
col
I/O1 Partner
computer
8082
Partner
port
Desktop
client
computer
Table 103
Protocol / use
Comment
on devices (phones, computers with a softphone and gateways).
Deployment Scenario Very Large Deployment: Devices (Phones, Computers with a Softphone and Gateways)
Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
Comment
5060
UDP
I/O
Computer
of the PBX
(nafo1)
5060
SIP Call control
5060
TCP
I/O
Computer
of the PBX
(nafo1)
5060
SIP Call control
5061
TCP
I/O
Computer
of the PBX
(nafo1)
5061
SIP Call control
20000249992
UDP
I/O
Application
computer
(OpenScap
e Media
Services)
20000249992

voice and video and

Table 104
A31003-S5070-J100-12-7631, 02/2013
469
Deployment Scenario Very Large Deployment: LDAP Server Computer

Port
Table 105
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
UDP
Any
LDAP access
Desktop
client
computer
Comment
470
A31003-S5070-J100-12-7631, 02/2013
Deployment Scenario Very Large Deployment: Exchange Server Computer
Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
25
TCP
Application
computer
Any

443
TCP
Application
computer
Any

OWA server
80
TCP
Application
computer
Any

OWA server
Table 106
Comment
Deployment Scenario Very Large Deployment: Microsoft Office Communications Server/Microsoft Lync Server
Computer
Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
483
TCP
I/O
Any

Table 107
Application
computer
Comment
Deployment Scenario Very Large Deployment: Lotus Domino Server Computer

Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
1352
TCP
Any
NRPC (Notes-RPC)
Table 108
Application
computer
Comment
A31003-S5070-J100-12-7631, 02/2013
471
Deployment Scenario Very Large Deployment: Instant-Messaging Server Computer (XMPP)
Port
Trans
port
proto
col
I/O1 Partner
computer
111
UDP
and
TCP
2049
UDP
and
TCP
5262
TCP
9090
Partner
port
Protocol / use
Comment
Any
111


page 243).
Any
2049


page 243).
Application
computer
Any

XMPP/TLS
TCP
Admin client Any

computer

management
9091
TCP
Admin client Any

computer

Any
TCP
Application
computer
4710

SSL or TLS
Any
TCP
Application
computer
4711
js-soc via TCP
Table 109

472
A31003-S5070-J100-12-7631, 02/2013
Deployment Scenario Very Large Deployment: NTP Server Computer
Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
Comment
123
TCP/
UDP
Any

Table 110
Application
computer
A31003-S5070-J100-12-7631, 02/2013
473
The following table describes the ports that must be open on the Web
Collaboration server computer additionally.
Deployment Scenario Very Large Deployment: Web Collaboration Server Computer

Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
802
TCP
Client
computer3
Any
HTTP
80
TCP
Frontend
computer
Any
HTTP
4432
TCP
Client
computer3
Any
HTTPS
50002
TCP
Client
computer3
Any

5004
TCP
Application
computer
Any
XML-RPC
Any
UDP
Computer
1433
for MS SQL
server
cluster for
OpenScape
Web
Collaboratio
n
Any
TCP
Computer
Configur Proprietary Microsoft protocol for
for MS SQL ed
communication from the Web
server
Collaboration server computer to
cluster for
the Microsoft SQL server
OpenScape
Web
Collaboratio
n
Table 111
Comment

HTTP communication.

474
A31003-S5070-J100-12-7631, 02/2013
The following table describes the ports that must be open on the computer for MS
SQL server cluster for OpenScape Web Collaboration additionally.
Deployment Scenario Very Large Deployment: Computer for MS SQL Server Cluster for OpenScape Web
Collaboration
Port
Trans
port
proto
col
I/O1 Partner
computer
1433
UDP
Web
Any
Collaboratio
n server
computer

Configu TCP
red
Web
Any
Collaboratio
n server
computer

Table 112
Partner
port
Protocol / use
Comment
Ports to be opened on the computer for MS SQL server cluster for OpenScape Web Collaboration
1 I: Inbound connection from the partner port on the partner computer to the port on the computer for MS SQL server cluster for OpenScape
Web Collaboration; O: Outbound connection from the port on the computer for MS SQL server cluster for OpenScape Web Collaboration
to the partner port on the partner computer
Deployment scenario Very Large Deployment: Google Apps Computer
Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
Any
TCP
Application
computer
4709

computer
Any
TCP
Proxy
server
computer
8080
HTTP connector
Table 113
Comment
A31003-S5070-J100-12-7631, 02/2013
475
Routing Schemas between the Application Computer and Frontend Computer
6.2 Routing Schemas between the Application Computer and Frontend

Computer
NOTE: The instructions in this section apply for Large Deployment and Very
The HiPathCA service on the application computer communicates with the
HiPathCA service on the frontend computers using the routing schema Multicast
(point-to-multipoint connection) by default. However, this might not be possible
because:
The application computer and the frontend computers are in different subnetworks.
The steps required in this case are described in former sections.
NOTE: Multicast works between computers in the same sub-network only.
An additional requirement is that the port used by Multicast in a possible
firewall between the application computer and the frontend computers must
be open. However, this requirment is complied with automatically, because all
ports between the application computer and the frontend computers must be
open.
Of the PBX configuration

The steps required in this case are described in this section.
In these cases the Unicast (point-to-point connection) is used and the following
steps must be executed:
1. Log on to the CMP via web browser.
2. Click under Maintenance > Inventory > Nodes & Applications > Nodes >
<name of the application computer> > Actions > Show services status
on the Show button and execute the following sub-steps:
a) Enter in the Filter field value JournalFacade or *Journal* and click
on Go.
b) Click on the JournalFacade entry.
A dialog for the journal facade service opens.
c) Enter the application computer's IP address in the Discover.IPAddress
field.
d) Enter in the Discover.port field the port number of a free port on the
application computer. The default port number is 4875.
476
A31003-S5070-J100-12-7631, 02/2013
e) Click on the Save button.

3. Use the following command to shut down the OpenScape frontend services
/etc/init.d/symphoniad stop WebClient_FE
4. Execute step 3 on all other probably available frontend computers.
5. Shut down the OpenScape UC Application on the application computer with
6. Open the /opt/siemens/HipathCA/config/host.env file on the
frontend computer.
a) Look for the entry
CLUSTER=<clusterId>
During the OpenScape UC Application installation, a value was assigned
to parameter SI_COMMUNITY_NAME in the /root/
knut.responsefile.txt file on the frontend computer. This value
was automatically assigned to parameter Cluster in the host.env file
on the frontend computer during the OpenScape UC Application
installation.
b) Expand this value so that it corresponds to the following pattern:

4875: Enter the port number you entered in step 2d on page 476.
A31003-S5070-J100-12-7631, 02/2013
477
c) Save the modification.

NOTE: Be sure to enter the IP address of the application computer and not
the IP address of the frontend computer. Also verify that you enter the same
port as on the first frontend computer.
8. Execute step 6 on the application computer.
NOTE: Be sure to enter the IP address of the application computer and not
the IP address of the frontend computer. Also verify that you enter the same
port as on the frontend computers.
9. Start the OpenScape UC Application on the application computer with the
following command:
10. Use the following command to start the OpenScape frontend services on the
frontend computer:
/etc/init.d/symphoniad start WebClient_FE
478
A31003-S5070-J100-12-7631, 02/2013
Connecting an OpenScape Voice
6.3 Connecting an OpenScape Voice

If the OpenScape UC Application shall be connected to an OpenScape Voice, the
OpenScape Voice is configured via the OpenScape Voice Assistant after a
successful installation. The OpenScape Voice Assistant is integrated in the CMP.
The CMP provides a single point of administration of subscriber and system
information for all the bundled components.
You access the CMP, incl. OpenScape Voice Assistant, via web browser provided
the OpenScape UC Application (OpenScape backend services) were started
previously.
You find detailed configuration information in the

Administration
OpenScape Voice Administrator Documentation
the Common Management Platform Administrator Documentation.
A31003-S5070-J100-12-7631, 02/2013
479
6.3.1 Opening Port 1040 on the PBX Computer

Port 1040 on the PBX computer opens automatically if a PBX is added in the CMP
or the Refresh Switch Data button is enabled under Configuration >
OpenScape Voice. If such operations fail to open the port, the following
instructions can be executed.
You need to open port 1040 on the PBX computer for Small Deployment, Large
Deployment and Very Large Deployment. This enables CSTA access from the
application computer to the PBX computer. The following steps are examples of
this:
NOTE: The computer names mucoscv05 and mucoscsrv04 as well as the IP
addresses are only examples.
1. Execute startCli on the PBX computer.
RTP Command Line Interface
Copyright (C) Fujitsu Siemens Computers GmbH 1999 - 2009
All Rights Reserved
Copyright (C) 2000-2008 Siemens Network Convergence LLC.
All rights reserved.
NOTE:
You may use this software only in accordance with the
terms of your license agreement, located on any of the instal
lation CDs for this product.
(This process is running as "RtpAdmCli01")
2. Log on as sysad.
Login: sysad
Management session established for user "sysad" on
"mucoscv05"
Main Menu:
Configuration Management.......................1
Fault Management...............................2
Performance Management.........................3
Security Management............................4
System Management..............................5
Application-level Management...................6
Open Logfile............................94
Show Callback Output....................95
Wait for Callbacks......................96
Change Password.........................97
Expert Mode.............................98
Exit....................................99
3. Enter 6.
Application-level Management:
Softswitch Management..........................1
Signaling Management...........................2
Media Gateway Management.......................3
Rate Area and Class of Service.................4
Zone Management................................5
Translation/Routing Management.................6
Feature Management.............................7
Network Element Security Management............8
480
A31003-S5070-J100-12-7631, 02/2013
Network Traffic Management.....................9

Service Broker Management.....................10
PCL Management................................11
Return..................................99
4. Enter 8.
Network Element Security Management:
IPSec Profile Management.......................1
IKE Profile Management.........................2
Kerberos Profile Management....................3
Packet Filter Rules Security Management........4
Secure EndPoint Device Security Management.....5
Return..................................99
5. Enter 4.
Packet Filter Rules Security Management (methods):
Create.........................................1
Modify.........................................2
Remove.........................................3
Display........................................4
Return..................................99
6. Enter 1.
Packet Filter Rule Name <Max Length 63 (max length: 63)>
(default: ):
7. Enter CSTA-mucoscsrv04. This is the name for identifying the packet filter
rule for a special server.
Description <Max Length 63 (max length: 63)> (default: ):
8. Push the <ENTER> key.
Remote FQDN <Max Length 63 (max length: 63)> (default: ):
Remote IP Address <Max Length 50 (max length: 50)> (default:
):
10. Enter the IP address of the application computer, for example
10.25.100.104.
Remote NetMask <Max Length 50 (max length: 15)> (default:
255.255.255.255):
Transport Protocol <1 = icmp, 2 = udp, 3 = tcp, 4 = all, 5 =
esp, 6 = ah, 7=sctp, 8=icmpv6> (default: 4):
12. Enter 3.
Remote Port Begin <0 = All Ports>:
13. Enter 0.
Direction <1 = incoming, 2 = outgoing, 3 = bothways>
(default: 1):
14. Enter 1.
A31003-S5070-J100-12-7631, 02/2013
481
Local Host <Max Length 63 (max length: 63)> (default: ):

15. Enter csta_ip_alias_1.
Local Port Begin <0 = All Ports> (default: 0):
16. Enter 1040.
Local Port End <0 = Only Local Port Begin Valid> (default:
0):
Action
<1 = Allow, 2 = Drop> (default: 1):
18. Enter 1.
Do you want to execute this action? <y/n> (default: yes):
19. Enter y.
Operation successful
Press <Return> to continue
Packet Filter Rules Security Management (methods):
Create.........................................1
Modify.........................................2
Remove.........................................3
Display........................................4
Return..................................99
21. Enter 4.
Packet Filter Rule Name <Max Length 63 (max length: 63)>
(default: ):
22. Enter CSTA-mucoscsrv04.
Do you want to execute this action? <y/n> (default: yes):
Total Number of Packet Filter Rules Retrieved :
1
Packet Filter Rule Name:
CSTA-mucoscsrv04
Description:
Remote FQDN:
Remote IP Address:
10.25.100.104
Remote NetMask:
255.255.255.255
Remote Port Begin:
0
Remote Port End:
0
Direction:
InComing
Local Host :
csta_ip_alias_1
Local Port Begin:
1040
Local Port End:
0
Transport Protocol:
TCP
Action :
Allow
------------------------------------------------------------Packet Filter Rules Security Management (methods):
Create.........................................1
Modify.........................................2
Remove.........................................3
Display........................................4
Return..................................99
482
A31003-S5070-J100-12-7631, 02/2013
24. Enter 4.
25. After you have configured the CSTA connection and the offices codes as
shown above, stop and restart the OpenScape UC Application on the
and
As alternative, you can execute the following command:
/etc/init.d/symphoniad restart
A31003-S5070-J100-12-7631, 02/2013
483
Connecting a HiPath 4000
6.4 Connecting a HiPath 4000

You find detailed HiPath 4000 configuration information in the

Administration
administrator documentation HiPath 4000 Assistant, Configuration

Management,
the Common Management Platform Administrator Documentation.
NOTE: Connecting a HiPath 4000 is not supported for Integrated Deployment

and Very Large Deployment.
6.4.1 Connection of an OS UC Appl. via an OSV to a

HiPath 4000
IMPORTANT: For information and diagrams about the various OpenScape UC
Application deployment scenarios and system requirements, refer to the
From OpenScape UC Application V4 R0 on, a HiPath 4000 can be connected
directly to the OpenScape UC Application. For OpenScape UC Application V3 R2
however, this option does not exist. For this version, a HiPath 4000 can only be
connected to the OpenScape UC Application via an OpenScape Voice (OSV).
The information in this section apply for this connection type and for the case that
such an OpenScape UC Application is upgraded to V7.
The only additional feature of such a connection is the option to monitor the media
presence status of HiPath 4000 phone numbers. Furthermore, this feature can
only be used under the following conditions:
To each OpenScape UC Application user, an OpenScape Voice phone

number must be assigned as an ONS number.
To each OpenScape UC Application user, a HiPath 4000 phone number must

be assigned as Associated Device.
If applicable, ensure that OpenScape Voice is configured for HiPath 4000 interoperability. You find instructions in the OpenScape Voice configuration manual
(for example OpenScape Voice Administrator Documentation) and in the HiPath
4000 documentation.
484
A31003-S5070-J100-12-7631, 02/2013
Installing the Licenses
Please obtain information about connecting the HiPath 4000 from the
Administration, e. g. section Connecting a HiPath-4000 System.
6.5 Installing the Licenses

Which licenses are required for the respective features can be obtained from the
Information about installing licenses is contained in the administrator
documentation OpenScape UC Application Configuration and Administration.
6.6 Creating the OpenScape UC Application Users in the CMP

Information about the following topics has been moved to the administrator
documentation OpenScape UC Application Configuration and Administration:
Description of the PassphrasePolicyConfig.xml Password Policy File
Manual Configuration of the OpenScape UC Application Users
Exporting and Importing User Data with a CSV File
Assigning the ONS Resource to a User
Configuring Call Forwarding Dependable for ONS Subscribers
A31003-S5070-J100-12-7631, 02/2013
485
Creating the OpenScape UC Application Users in the CMP
486
A31003-S5070-J100-12-7631, 02/2013
Client Installations
7 Client Installations
Description of the OpenScape UC Application clients installation.
In this chapter you find a compilation of installation instructions for OpenScape
UC Application clients that have their own setup.
NOTICE: All clients of the OpenScape UC Application V3 R2, V4
R0 and V6 R0 support all OpenScape UC Application features in
such versions. Only the new OpenScape UC Application V7 R1
features are not supported by these clients. Using the new
features requires setting up a current client version (version
V7R1).
In this chapter we detail the installation of the following clients:
OpenStage Client
7.1 OpenScape Extensions for Microsoft Outlook

General Description of the OpenScape Extensions for Microsoft Outlook.
Installing the OpenScape Extensions for Microsoft Outlook provides features in
Microsoft Outlook that let you plan server-based Meet Me conferences via
meeting request in the Microsoft Outlook calendar. Such server-based conferences comprise:
Audio conferences
Web conferences
Video conferences
When the conference extensions are installed, the button

Add OpenScape conference
is displayed in the toolbar of the dialog for scheduling an appointment.
The conference is performed via the OpenScape UC Application server.
NOTICE: The default system configuration plays a short signal
tone audible to all conference participants when a conference
participant joins or leaves the conference. In case of a larger
number of conference participants joining or leaving, this signal
A31003-S5070-J100-12-7631, 02/2013
487
tone may become annoying to the others. It is therefore not played

anymore when the number of conference participants exceeds
15.
Conferences created via OpenScape Extensions for Microsoft Outlook are also
displayed in the conferences lists of OpenScape Web Client and OpenScape
Desktop Client Enterprise Web Embedded Edition and can be edited via such
clients.
7.1.1 Usage Requirements

Usage requirements for the OpenScape Extensions for Microsoft Outlook.
The OpenScape Extensions for Microsoft Outlook has been released for specific
Windows operating systems and Office versions only.
You find current and detailed information about the supported operating systems
and versions of usable Outlook clients in the OpenScape UC Application Planning
Guide.
7.1.2 Installing the OpenScape Extensions for Microsoft Outlook

General information about setting up the OpenScape Extensions for Microsoft
Outlook.
The OpenScape Extensions for Microsoft Outlook is installed by launching the
setup file setup.exe from the setup directory OpenScape4Outlook.
NOTICE: Please note that the setup file setup.exe on the
operating system Windows 7 must not be started from the Ziparchive. Because of modifications to the Microsoft Windows 7
rights management the installation would otherwise fail. Unpack
the archive and start the installation then from the unpacked
directory via the context menu item Run as administrator.
The dialog language in which the OpenScape Extensions for Microsoft Outlook is
installed on your system corresponds to the language of your currently installed
Microsoft Outlook application.
Unlike previous versions, the setup files are not installed in the AppData directory
of the user anymore but in a directory under Program Files (x86). Consequently,
the OpenScape Extensions for Microsoft Outlook need not be installed separately
for each user who deploys the extension on this system. The administrator installs
the extensions once for all users. This enables performing the installation as mass
rollout too.
488
A31003-S5070-J100-12-7631, 02/2013
7.1.2.1 Requirements for Setting up OpenScape Extensions for Microsoft Outlook

Installation requirements for the OpenScape Extensions for Microsoft Outlook.
Because you cannot combine the installation of the required .Net Framework 4.0
components with the OpenScape Extensions for Microsoft Outlook setup, you
need to install such components manually before setting up OpenScape Extensions for Microsoft Outlook.
NOTICE: Use the .NET Framework 4 redistributable package for
retroinstalling the .Net Framework 4.0 components.
For .Net Framework 4.0 component setup details, refer to:
http://www.microsoft.com/en-us/download/
details.aspx?id=17718
7.1.2.2 Installation Process

Description of the OpenScape Extensions for Microsoft Outlook setup process.
To perform the setup, proceed as follows:
Step by Step
1) Shut down Microsoft Outlook.
2) Start the setup.exe with administrative privileges. In case of Microsoft
Windows Vista or Microsoft Windows 7 you do this via the Run
as administrator context menu item.
NOTICE: When you install the Microsoft Outlook component via
a network directory you encounter a security prompt that you
need to confirm with a click on the Run button.
Depending on the operating system and the currently installed operating
system components, some setup steps may follow to prepare the system for
the installation of the OpenScape Extensions for Microsoft Outlook.
After you have installed these components, the dialog OpenScape Extensions for Outlook opens for the OpenScape Extensions for Microsoft
Outlook setup.
3) Click on Next.
The welcome dialog of the setup wizard opens.
4) Click on Next to initiate the setup process.
The licensing dialog opens.
A31003-S5070-J100-12-7631, 02/2013
489
5) Give your consent by setting the I accept the license agreement option.
NOTICE: You can have the license contract printed out via the
Print button.
6) Click on Next.
The dialog for changing the setup directory (if required) opens. Click on the
Change button to select another setup directory.
7) Click on Next.
The setup confirmation dialog box opens.
8) Click the Install button.
A new dialog opens that allows tracing the setup process:
Another dialog opens, which marks the end of the installation.
9) Click on the Finish button in this dialog.
The installation is complete and the setup assistant is closed.
10) Start Microsoft Outlook under the user account that was installed for this
component.
The Initial Configuration dialog for the OpenScape Extensions for
Microsoft Outlook opens. Depending on the login procedure specify here
your user and connection data initially for logging on to the OpenScape
environment.
You can now perform the initial configuration depending on the login procedure
used.
7.1.2.3 Initial Configuration

Initial configuration for server access.
During the initial configuration and depending on the login procedure you specify
your user and connection data for logging on to the OpenScape environment
once. At the next Microsoft Outlook start, the OpenScape environment is
connected automatically.
NOTICE: You learn the login and connection data from your
system administrator.
The dialog in which you need to perform the initial configuration opens directly
after the OpenScape Extensions for Microsoft Outlook installation when you start
Microsoft Outlook for the first time again.
490
A31003-S5070-J100-12-7631, 02/2013
If you wish to perform the initial installation at a later date, close the configuration
dialog. You can then perform the initial configuration in Microsoft Outlook some
time later. How to reach the configuration dialog:
Microsoft Outlook 2007 or 2010:

You reach the configuration dialog via File > OpenScape > doubleclick on
Configuration > Network tab.
Microsoft Outlook 2003:

You reach the configuration dialog via the Microsoft Outlook menu. Select in
the menu of Microsoft Outlook Tools > Options > tab OpenScape Extensions for Microsoft Outlook > Configuration button > Network tab.
Which data you need for logging on and which computer (application or front-end
computer) must be connected depends on the selected login procedure and on
the structure of the OpenScape environment. Depending on the OpenScape
setting the following login procedures can be deployed:
Login via your OpenScape user account.
Login via your Windows user account (i. e. your workstation's user account).
Login via Single Sign-On (SSO). With SSO, logging on occurs automatically
with your Windows login user data if you are already logged in at your
workstation.
7.1.2.4 How to Perform the initial Configuration for Access via your OpenScape User
Account
Initial configuration for accessing the OpenScape environment via your
OpenScape user account.
To configure the default access initially after the installation, proceed as follows:
A31003-S5070-J100-12-7631, 02/2013
491
Step by Step
component.
The Initial Configuration for the OpenScape Extensions for Microsoft
Outlook dialog opens.
2) In the OpenScape Server - Access Data section, enter the following logon
data for logging on with your OpenScape user account:
a) User ID
Specify here your OpenScape user ID in the format <user ID@domain>.
b) Password
Enter here the OpenScape password you use for logging on to the
OpenScape server.
c) Use Windows Authentication
This option is not set for default access.
d) Use Single Sign On (SSO)
This option is not set for default access.
3) In the OpenScape Server - Network Configuration section specify the data
required for connecting your workstation to the application computer:
492
A31003-S5070-J100-12-7631, 02/2013
a) OpenScape Server - Host Address

Depending on the OpenScape scenario, enter here the complete network
address (FQDN) of the application computer. In doing so please heed the
following computer assignment:
Integrated Deployment: FQDN of the application computer
Small Deployment: FQDN of the application computer
Large Deployment: FQDN of the front-end computer
Very Large Deployment: FQDN of the front-end computer
b) OpenScape Server - Port
Enter here the network port via which the communication to the application computer is configured.
Performing the initial configuration for access via your OpenScape user account
is now complete.
NOTICE: If the OpenScape environment cannot be connected by
specifying the user data, the network address and the port, the
OpenScape Extensions for Microsoft Outlook cannot be fully
configured. When invoking the configuration dialog merely the
Network tab is displayed for connecting the OpenScape
environment.
You can now configure your conferences via a Microsoft Outlook meeting
request.
7.1.2.5 How to Perform the initial Configuration for Access via your Windows User
Account
Initial configuration for accessing the OpenScape environment via your Windows
user account.
Prerequisites
Windows authentication must be active in your OpenScape environment.
This logon variant allows you to log on to the OpenScape environment with your
Windows user account, thus the user account of your workstation.
To configure access via your Windows user account initially after the installation,
proceed as follows:
Step by Step
component.
A31003-S5070-J100-12-7631, 02/2013
493
2) In the OpenScape Server - Access Data section, enter the following logon
data for logging on to the OpenScape environment with your Windows user
account:
a) User ID
Specify here your Windows user account. Use the input format
<domain\user ID>.
b) Password
Enter here the Windows password you use for logging on to your
workstation.
c) Use Windows Authentication
Select this option to apply Windows authentication.
d) Use Single Sign On (SSO)
When selecting Windows authentication you cannot set this option.
494
A31003-S5070-J100-12-7631, 02/2013

Depending on the OpenScape scenario, enter here the complete network
address (FQDN) of the application computer. In doing so please heed the
following computer assignment:
Integrated Deployment: FQDN of the application computer
Small Deployment: FQDN of the application computer
Large Deployment: FQDN of the front-end computer
Very Large Deployment: FQDN of the front-end computer
Initial configuration for Windows authentication is now complete.
environment.
request.
7.1.2.6 How to Configure Access via Single Sign-On Initially

Initial configuration for accessing the OpenScape environment via Single Sign-On
(SSO).
Prerequisites
Single Sign-On must be active in your OpenScape environment.
This login variant lets you log on to the OpenScape environment automatically if
you are already logged in at your workstation.
To perform the initial configuration for access via Single Sign-On after the installation, proceed as follows:
Step by Step
component.
A31003-S5070-J100-12-7631, 02/2013
495
2) In the OpenScape Server - Network Access section select Use Single Sign
On (SSO) for logging on to the OpenScape environment via Single Sign-On.
The input lines for User ID and Password are blocked and displayed shaded
gray.
Enter here the fully qualified network address (FQDN) of the application
computer.
You are now finished performing the initial configuration for access via Single
Sign-On.
environment.
request.
496
A31003-S5070-J100-12-7631, 02/2013
7.1.3 Installation in a Terminal Server Environment

Installing the OpenScape Extensions for Microsoft Outlook in a terminal server/
Citrix environment.
The setup process may be run through only once in terminal server or Citrix
environments. Setup therefore requires administrative privileges.
The program files are installed in the Program Files directory instead of in
the local user directory under Application Data.
The newly added registry keys are automatically applied for all users, so that all
users at the terminal server can deploy the OpenScape Extensions for Microsoft
Outlook.
7.1.3.1 Requirements for the Installation in a Terminal Server Environment

Requirements for setting up the OpenScape Extensions for Microsoft Outlook in
a terminal server environment.
The following requirements must be complied with for the setup:
The option for local users to log on to the terminal server must be temporarily
inactive.
All user must be logged off.
The setup mode must have been released.
7.1.3.2 How to Perform the Installation in a Terminal Server Environment

Installing the OpenScape Extensions for Microsoft Outlook in a terminal server
environment.
Setup requires the following steps:
Step by Step
1) Start the command prompt (Start > Run > cmd).
2) Enter the following command in the command prompt:
change logon /disable
3) Log all users off of the system.
change user /install
5) Install OpenScape Extensions for Microsoft Outlook via the provided setup
package.
change user /execute
A31003-S5070-J100-12-7631, 02/2013
497

change logon /enable
Setting up the Outlook conference extension in a terminal server environment is
now complete.
7.1.3.3 User Configuration Files for Terminal Server Environments

Configuring user configuration files for a terminal server environment.
In case of a standard setup, the user configuration is stored in a local user
directory:
...\Documents and Settings\<user profile>\Local
Settings\Application Data\Siemens\UCSolutions
These directories are not replicated to other servers in a terminal server
environment (with or without Citrix). Therefore, users are prompted to specify
their configuration data each time they log on to a new terminal server.
To avoid this, the system administrator can determine during the OpenScape
Extensions for Microsoft Outlook setup that the configuration data is copied to a
directory available in the entire system:
...\Documents and Settings\<user profile>\Application
Data\Siemens\UCSolutions
For this purpose, the setup directory contains the following file: UseSysAppData.reg
Using this file, the installation can be performed in a way that the user configuration data is stored in this directory and the access path addresses this directory
system-wide.
To restore the default behavior, you can use the following file: UseLocalAppData.reg
It is also contained in the setup directory.
7.1.4 Repairing, Upgrading and Uninstalling the OpenScape Extensions for

Microsoft Outlook
Introductory description of how to repair (update), upgrade (installing a subsequent version) or uninstall the OpenScape Extensions for Microsoft Outlook.
You can update, upgrade or uninstall the client application OpenScape Extensions for Microsoft Outlook also via the setup program (setup.exe).
498
A31003-S5070-J100-12-7631, 02/2013
7.1.4.1 How to Perform a Repair (Update) Installation for the OpenScape Extensions for
Microsoft Outlook
Repairing (updating) the OpenScape Extensions for Microsoft Outlook.
If a current version of the OpenScape Extensions for Microsoft Outlook shall be
repaired after the installation, proceed as follows:
Step by Step
2) Start the current setup.exe of the installation program for OpenScape
Extensions for Microsoft Outlook.
3) Click on the Next button in the setup's welcome dialog.
The following dialog opens:
4) Click on the Repair button in this dialog.

The confirmation dialog for the update installation opens.
5) Click on the Repair button in this confirmation dialog.
The setup process starts and a new dialog opens that allows tracing the setup
process. Another dialog opens, which marks the end of the installation.
The update installation is complete and the setup assistant is closed.
7.1.4.2 How to Perform an Upgrade Installation for the OpenScape Extensions for
Microsoft Outlook
Installing a more recent OpenScape Extensions for Microsoft Outlook version.
A31003-S5070-J100-12-7631, 02/2013
499
If a current version of the OpenScape Extensions for Microsoft Outlook is to be

set up after the installation, proceed as follows:
Step by Step
4) Click on the Upgrade button in this dialog.

The confirmation dialog for the upgrade installation opens.
The upgrade installation is complete and the setup assistant is closed.
7.1.4.3 How to Uninstall the OpenScape Extensions for Microsoft Outlook

Uninstalling the OpenScape Extensions for Microsoft Outlook.
If you wish to remove the application OpenScape Extensions for Microsoft
Outlook from your local system, proceed as follows:
Step by Step
1) Close Microsoft Outlook.
500
A31003-S5070-J100-12-7631, 02/2013

4) Click on the Remove button in this dialog.

The confirmation dialog for removing the application opens.
5) Click on the Remove button in this confirmation dialog.
The uninstallation process starts and a new dialog opens in which you can
observe this process. Another dialog opens, which marks the end of the
uninstallation.
The uninstallation is complete and the setup assistant is closed.
7.1.4.4 Repairing and Upgrading via msi-File

Update and upgrade installation by mass rollout via msi-file.
Repairing (updating) or installing a successor version (upgrading) for the
OpenScape Extensions for Microsoft Outlook via mass rollout can simply be done
using the appropriate msi-file.
As the product code mostly (update installation) and partly (upgrade installation)
remains unchanged, the following properties with the specified parameters must
be additionally transferred via command line for an installation via msi-file:
reinstall=all
reinstallmode=vomus
These properties will ensure a trouble-free installation by msi-file. For this

purpose, expand the command line entry by the following properties:
reinstall=all reinstallmode=vomus
A31003-S5070-J100-12-7631, 02/2013
501
7.2 OpenScape Extensions for Lotus Notes

General Description of the OpenScape Extensions for Lotus Notes.
After you have installed the OpenScape Extensions for Lotus Notes, the IBM
Lotus Notes client provides features for scheduling server-based Meet Me conferences via a meeting request in the IBM Lotus Notes calendar. Among serverbased conferences you find:
Audio conferences
Web conferences
Video conferences
When the conference extensions are installed, the button

Add OpenScape conference
is displayed in the toolbar of the dialog for scheduling an appointment.
The conference is performed via the OpenScape UC Application server.
NOTICE: The default system configuration plays a short signal
tone audible to all conference participants when a conference
participant joins or leaves the conference. In case of a larger
number of conference participants joining or leaving, this signal
tone may become annoying to the others. It is therefore not played
anymore when the number of conference participants exceeds
15.
7.2.1 Installing the OpenScape Extensions for Lotus Notes

General information about setting up the OpenScape Extensions for Lotus Notes.
NOTICE: You need to perform some configurations on the Lotus
Domino server for installing the OpenScape Extensions for Lotus
Notes. You find information about these preparations in the
manual "OpenScape UC Application V6 Configuration and
Administration" in Chapter "Configuring the Lotus Domino Server
for the OpenScape Conference Extension".
The OpenScape Extensions for Lotus Notes is installed by launching the setup
file setup.exe from the setup directory OpenScape4LotusNotes.
NOTICE: The dialog language in which the OpenScape Extensions for Lotus Notes is installed on your system corresponds to
the language of your currently installed IBM Lotus Notes application.
502
A31003-S5070-J100-12-7631, 02/2013
7.2.1.1 Requirements for Setting up OpenScape Extensions for Lotus Notes

Installation requirements for the OpenScape Extensions for Lotus Notes.
Setting up the OpenScape Extensions for Lotus Notes requires the .NET
Framework to be present on the system where the installation shall take place in
the most recent version.
A user with administrative privileges installs the OpenScape Extensions for Lotus
Notes once on the desired workstation. In this process, no entries are written in
the registry under HKCU or in the user directory of the current user.
7.2.1.2 Installation Process

Description of the OpenScape Extensions for Lotus Notes setup process.
Step by Step
1) Close the IBM Lotus Notes client.
2) Start the setup.exe.
NOTICE: When you install the IBM Lotus Notes component via a
network directory, you encounter a security prompt that you need
to confirm with a click on the Run button.
3) Click on Next.
4) Click on Next to initiate the setup process.
The licensing dialog opens.
5) Set the I accept the terms of the license agreement option.
6) Click on Next.
The setup confirmation dialog box opens.
7) Click the Install button.
A new dialog opens that allows tracing the setup process.
Another dialog opens, which marks the end of the installation.
The installation is complete and the setup assistant is closed.
9) Start your IBM Lotus Notes client.
A31003-S5070-J100-12-7631, 02/2013
503
The Initial Configuration dialog opens. Enter here initially the user data for
your access to the OpenScape server and the data for connecting the
OpenScape server. At the next start of your IBM Lotus Notes client, the
OpenScape server is connected automatically.
NOTICE:
You reach this settings dialog via the configuration settings also.
Click in the IBM Lotus Notes dialog Calendar on the
Configuration
504
button.
A31003-S5070-J100-12-7631, 02/2013
In the OpenScape Server - Access Data section you need to make the
following entries for logging on to your OpenScape user account:
OpenScape User ID
Specify here your user ID for the OpenScape UC Application in the form
<user ID@domain>.
OpenScape Password
Enter the password you use to log on to the OpenScape server.
In the OpenScape Server - Network Configuration section, the following
entries are required for connecting the OpenScape server from your
workstation:
OpenScape Server - Host Address
Enter here the fully qualified network address (FQDN) of the application
computer.
OpenScape Server - Port
Enter here the network port via which the connection to the OpenScape
server is configured.
NOTICE: If you do not know the Logon or connection data,
please contact your system administrator.
Setup with the initial configuration for immediately connecting the OpenScape
server is now complete.
NOTICE: If the OpenScape server cannot be connected after you
have specified the user data, the network address and the port of
the OpenScape server, the OpenScape Extensions for Lotus
A31003-S5070-J100-12-7631, 02/2013
505
Notes cannot be configured. When invoking the configuration

dialog merely the Network tab is displayed for connecting the
OpenScape server.
You can now configure your conferences via a new calendar entry in IBM Lotus
Notes.
7.2.1.3 Repairing, Upgrading and Uninstalling the OpenScape Extensions for Lotus
Notes
Introductory description of how to repair (update), upgrade (installing a subsequent version) or uninstall the OpenScape Extensions for Lotus Notes.
You can update, upgrade or uninstall the client application OpenScape Extensions for Lotus Notes also via the setup program (setup.exe).
7.2.1.4 How to Perform a Repair Installation for the OpenScape Extensions for Lotus
Notes
Repairing the OpenScape Extensions for Lotus Notes.
If a current version of the OpenScape Extensions for Lotus Notes shall be
repaired after the installation, proceed as follows:
Step by Step
Extensions for Lotus Notes.
506
A31003-S5070-J100-12-7631, 02/2013
4) Click on the Repair button in this dialog.

The confirmation dialog for the update installation opens.
5) Click on the Repair button in this confirmation dialog.
The repair installation is complete and the setup assistant is closed.
7.2.1.5 How to Perform an Upgrade Installation for the OpenScape Extensions for Lotus
Notes
Installing a more recent OpenScape Extensions for Lotus Notes version.
If a current version of the OpenScape Extensions for Lotus Notes is to be set up
after the installation, proceed as follows:
Step by Step

The confirmation dialog for the upgrade installation opens.
5) Click on the Upgrade button in this confirmation dialog.
A31003-S5070-J100-12-7631, 02/2013
507

The update installation is complete and the setup assistant is closed.
7.2.1.6 How to Uninstall the OpenScape Extensions for Lotus Notes

Uninstalling the OpenScape Extensions for Lotus Notes.
If you wish to remove the application OpenScape Extensions for Lotus Notes from
your local system, proceed as follows:
Step by Step
4) Click on the Remove button in this dialog.

The confirmation dialog for removing the application opens.
5) Click on the Remove button in this confirmation dialog.
The uninstallation process starts and a new dialog opens in which you can
observe this process. Another dialog opens, which marks the end of the
uninstallation.
The uninstallation is complete and the setup assistant is closed.
7.3 OpenScape Desktop Integration

General Description of the OpenScape Desktop Integration
508
A31003-S5070-J100-12-7631, 02/2013
Using the information on the DesktopIntegration tab from the General Settings
menu of the OpenScape Web Client you can install a small program on your
workstation that allows calling a subscriber from any application.
An example: A Word document you have opened contains a phone number.
Select this phone number in the text and enable the hotkey you have defined for
this purpose. A call to this number is immediately initiated.
Furthermore, incoming calls and instant messages are signalled via the
OpenScape Desktop Integrationapplication even if the OpenScape Web Client
screen is closed.
In the OpenScape Desktop Integration application you can set further options for
the startup behavior, the OpenScape Web Client display and the notification
options.
NOTICE: To use this application program the OpenScape Web
Client need not be started.
7.3.1 How to Install the OpenScape Desktop Integration

Installing the OpenScape Desktop Integration.
The following work steps are required for using the OpenScape Desktop
Integration:
Step by Step
1) Start the OpenScape Web Client.
2) Open the DesktopIntegration tab. You reach this settings dialog via menu > General -> Common -> DesktopIntegration tab.
A31003-S5070-J100-12-7631, 02/2013
509
3) On the DesktopIntegration tab, click the Download or Download (x64)

button, if a 64-bit operating system is installed on your workstation.
The file download dialog opens.
4) Click on the Save button.
The file selection dialog for storing files opens.
5) Save the OSCwebDI.exe file on the desktop or in any directory.
6) Open the desktop or the directory in which you have stored the application via
the Explorer. Doubleclick OSCwebDI.exe.
The application starts.
After the start, the task bar displays the
icon.
7) Click with the right mouse button on the icon in the task bar to invoke the
features of this application and the OpenScape Desktop Integration settings
dialogs.
7.4 OpenScape Click-to-Dial-Browser-Plug-in

Calling with the OpenScape Click-to-Dial-Browser-Plug-in directly from HTML
Pages.
510
A31003-S5070-J100-12-7631, 02/2013
The OpenScape Click-to-Dial-Browser-Plug-in is a program which allows to dial

directly a phone number displayed on any HTML page by clicking this number in
the web browser. Dialable phone numbers are highlighted on the HTML pages
and displayed with the flag of the country corresponding to their country code.
The installation of the application can be accomplished in several ways:
Via the OpenScape Web Client.

The installation file stored on the server is downloaded and installed manually.
You can find the download button in the OpenScape Web Client under menu
> General > Common > Browser Integration tab.
Via the OpenScape Desktop Client Enterprise Web Embedded Edition.

During the OpenScape Desktop Client Enterprise Web Embedded Edition
installation, the OpenScape Click-to-Dial-Browser-Plug-in is also installed
automatically.
NOTICE: If the OpenScape Click-to-Dial-Browser-Plug-in has
been installed via the OpenScape Desktop Client Enterprise Web
Embedded Edition, it is initially inactive by default. Before using
this feature, the user has to activate the application first. See the
Configuration paragraph of this chapter.
Via the program OpenScape Client Integrations.

This installation program allows you to use OpenScape Click-to-DialBrowser-Plug-in without installing another CTI client like the OpenScape
Desktop Client Enterprise Web Embedded Edition or the OpenScape Web
Client. You find more detailed information on this installation program in
chapterOpenScape Client Integrations of this manual.
7.4.1 OpenScape Click-to-Dial-Browser-Plug-in

OpenScape Click-to-Dial-Browser-Plug-in features.
Using the OpenScape Click-to-Dial-Browser-Plug-ins you can select a phone
number contained on any HTML page and directly initiate a call to this number.
The following browsers support this function:
Internet Explorer Integration

Provides the call functionality in the Microsoft Internet Explorer.
Mozilla Firefox Integration

Enables calling by mouseclick via your Mozilla Firefox web browser.
A31003-S5070-J100-12-7631, 02/2013
511
7.4.2 Setting up the OpenScape Click-to-Dial-Browser-Plug-in

General information about setting up the OpenScape Click-to-Dial-Browser-Plugin.
NOTICE: This section contains information that applies only for
setting up the OpenScape Click-to-Dial-Browser-Plug-in via the
OpenScape Web Client. If the plug-in shall be used in combination with the OpenScape Desktop Client Enterprise Web
Embedded Edition, it is included in the OpenScape Desktop
Client Enterprise Web Embedded Edition setup.
The system administrator or any user of a computer who has administrator privileges can install the OpenScape Click-to-Dial-Browser-Plug-in. The OpenScape
Click-to-Dial-Browser-Plug-in is installed for all users of this computer.
NOTICE: The OpenScape Click-to-Dial-Browser-Plug-in is
automatically initialized and activated upon the first invocation of
the web browser.
The following three files are available for setting up the OpenScape Click-to-DialBrowser-Plug-in:
512
BrowserIntegration.msi
Installs the OpenScape Click-to-Dial-Browser-Plug-in for the desired web
browser - Internet Explorer or Mozilla Firefox.
InstallBrowserIntegration.exe
Executes the BrowserIntegration.msi file. In this process, the configuration parameters specified in the config.ini file are used. You launch
setup alterations, updates and the OpenScape Click-to-Dial-Browser-Plug-in
uninstallation via this file also.
config.ini
You can enter the following configuration parameters that will be transferred
to the BrowserIntegration.msi file by executing the InstallBrowserIntegration.exe file during the installation.
WebClientAddress
This parameter defines the OpenScape Web Client URL and optionally
the port used. For example:
http://10.1.2.130:8443
or
https://oswebclient.siemens-enterprise.com
CommandLine
At this point you can enter command line parameters that affect the setup.
For example, /qn specifies that the installation shall be performed
automatically, i. e. without user interaction and setup dialogs. This type of
installation definitely requires the OpenScape Web Client URL to be
A31003-S5070-J100-12-7631, 02/2013
specified in the config.ini file. Both features - Internet Explorer

Integration and Mozilla Firefox Integration - are installed and can be used
by all users of the system.
NOTICE: The Firefox Integration feature is only included in the
setup if the Mozilla Firefox web browser has been installed on the
system.
NOTICE: The config.ini file may only be changed under the

instructions given by your system administrator.
7.4.2.1 How to Perform the Default Installation

Default installation of the OpenScape Click-to-Dial-Browser-Plug-in.
IMPORTANT: Installing OpenScape Desktop Client Enterprise
Web Embedded Edition with OpenScape Click-to-Dial-BrowserPlug-in and the default installation described in the following are
incompatible. The default installation terminates with a corresponding message if the OpenScape Desktop Client Enterprise
Web Embedded Edition with integrated OpenScape Click-to-DialBrowser-Plug-in has already been installed on the system.
NOTICE: The setup dialogs are displayed in English language.

Step by Step
1) Shut down the web browser (Internet Explorer or Mozilla Firefox) currently
used.
2) Start the file InstallBrowserIntegration.exe.
A31003-S5070-J100-12-7631, 02/2013
513
3) Click on the Next button to initiate the installation.

The following dialog appears:
4) Enter your name and the name of your organization. Then click on Next.
The next dialog that opens lists the features to be installed.
514
A31003-S5070-J100-12-7631, 02/2013
5) Decide whether the Firefox Integration feature shall be included in the installation.
NOTICE: The IE Integration is always enclosed in the setup by
default.
NOTICE: The Firefox Integration feature is only available for

selection if the Mozilla Firefox web browser has been installed on
the system.
Click on the
icon to the left of the Firefox Integration feature to display
the following menu:
Will be installed on local drive.

Select this option to install the Firefox Integration on the local computer.
Entire feature will be installed on local hard drive.

Select this option if both features shall be installed.
A31003-S5070-J100-12-7631, 02/2013
515
Entire feature will be unavailable.

If you select this option, the Firefox Integration feature will not be installed
on the local computer.
6) Click on Next >.

7) Enter the OpenScape Web Client URL.

You check the specified URL via the Check server address button.
If the URL is correct, the login mask of the OpenScape Web Client appears in
your Internet Explorer. Click on Next.
Click on OK here to close this message and to continue the installation
process.
If the URL is incorrect, a message points this out.
Click on OK here. The message window closes. You can now correct the URL
and then continue the installation process.
8) Click on Next. The installation process starts. A new dialog opens that allows
you to observe the installation process.
When the installation is done, the following dialog informs you accordingly.
516
A31003-S5070-J100-12-7631, 02/2013
9) Click on Finish.
The installation wizard closes.
Setting up the OpenScape Click-to-Dial-Browser-Plug-in is now complete.
7.4.3 Changing the Setup, Updating and Uninstalling the OpenScape Clickto-Dial-Browser-Plug-in
Introductory description of how to perform a setup change, repair (update) or
uninstall the OpenScape Click-to-Dial-Browser-Plug-in.
You start modifications to the existing setup, updates and the program's uninstallation via the following dialog. This dialog opens when you execute the setup file
from the setup directory of the application. The name of the setup file is:
You can customize the program as follows:
A31003-S5070-J100-12-7631, 02/2013
517
Via Modify
Installing/uninstalling a Firefox integration
Via Repair
Installing a more recent program version.
Via Remove
Uninstalling the program.
7.4.3.1 Modifying the Installation

Options for adjusting the OpenScape Click-to-Dial-Browser-Plug-in setup.
After you have installed the OpenScape Click-to-Dial-Browser-Plug-in you can
perform the following setup modifications:
If you have not integrated Firefox yet, you can do it retrospectively.
If you have integrated Firefox already, you can uninstall the Firefox support
again.
7.4.3.2 How to Uninstall the Firefox Support

Uninstalling the Firefox integration for the OpenScape Click-to-Dial-BrowserPlug-in.
How to uninstall the Firefox Integration without removing the entire program:
Step by Step
1) Make sure that Mozilla Firefox has terminated.
2) Start the file:
3) Select the Modify option in the opened dialog pictured above.
4) Click on Next.
The dialog for selecting the feature to be installed appears.
5) Click on
to the left of the Firefox Integration feature.
6) Select the Entire feature will be unavailable option.

7) Click on Next in this dialog.
The uninstallation routine starts. A new dialog opens which allows you to
observe the uninstallation process.
8) When the uninstallation is complete, a new dialog opens that you can close
via the Finish button.
Calling from the web browser Mozilla Firefox is not possible anymore.
518
A31003-S5070-J100-12-7631, 02/2013
7.4.3.3 How to Install the Firefox Support Retrospectively

Installing the Firefox integration for the OpenScape Click-to-Dial-Browser-Plug-in
retrospectively.
If you wish to use the call functionality from your Firefox web browser after a
default installation of the OpenScape Click-to-Dial-Browser-Plug-in, proceed as
follows:
Step by Step
1) Make sure that Mozilla Firefox has terminated.
2) Start the file:
3) Select the Modify option in the opened dialog pictured above.
4) Click on Next.
The dialog for selecting the feature to be installed appears.
5) Select the Firefox Integration feature and click on Next.
The dialog for entering the OpenScape Web Client URL opens.
6) Click on Next >.
The installation process begins.
7) Click on Finish when the setup is complete.
The process ends and the setup wizard closes.
NOTICE: After the Mozilla Firefox reboot you are informed about
the newly installed plug-in (add-on) in a dialog. Click on Refresh
to copy the changes and close this dialog.
Installing the Firefox integration for the OpenScape Click-to-Dial-Browser-Plug-in
retrospectively is now accomplished.
7.4.3.4 Update Installation (Repair)

Update installation (repair) for the OpenScape Click-to-Dial-Browser-Plug-in.
The Repair function is used for the following actions:
If a more recent version of the OpenScape Click-to-Dial-Browser-Plug-in is to

be installed after the setup.
If the OpenScape server URL needs to be adjusted after the setup.
If a malfunction has occurred in the currently installed application.
A31003-S5070-J100-12-7631, 02/2013
519
7.4.3.5 How to Perform an Update Installation (Repair)

Performing an update installation (repair) for the OpenScape Click-to-DialBrowser-Plug-in.
If an update installation is required, proceed as follows:
Step by Step
1) Shut down the web browser currently used.
2) Start the current version of the setup program for the OpenScape Browser
Integration.
3) Select the Repair option in the opened dialog pictured above.
4) Click on Next.
The following dialog opens.
5) Enter the OpenScape Web Client URL.

6) Click on the Check server address button.
This checks the entered URL.
If the URL is correct, the login mask of the OpenScape Web Client appears in
your Internet Explorer. Click on Next.
7) Click on Next.
A new dialog opens that allows tracing the setup process.
8) Another dialog opens, which marks the end of the installation. Click on the
Finish button in this dialog.
The repair installation is complete and the setup assistant is closed.
520
A31003-S5070-J100-12-7631, 02/2013
7.4.3.6 Uninstalling the OpenScape Click-to-Dial-Browser-Plug-in

Uninstalling the OpenScape Click-to-Dial-Browser-Plug-in.
NOTICE: For a system on which several users deploy the
OpenScape Click-to-Dial-Browser-Plug-in in the Microsoft
Internet Explorer please note that the function WebClient Call
must be manually removed for these users during the OpenScape
Click-to-Dial-Browser-Plug-in uninstallation. Open the Search
Options menu in the Microsoft Internet Explorer and select
Manage Search Providers. Select the WebClient Call feature in
the displayed list. Finally, click on the Remove button.
You can use the following options to remove the OpenScape Click-to-DialBrowser-Plug-in application from your local system:
Uninstallation via executing the InstallBrowserIntegration.exe file
Uninstallation via the Windows Start menu
7.4.3.7 How to Perform the Uninstallation via the Setup File

Uninstalling the OpenScape Click-to-Dial-Browser-Plug-in via the setup file.
To uninstall the OpenScape Click-to-Dial-Browser-Plug-in via executing the
InstallBrowserIntegration.exe file, proceed as follows:
Step by Step
2) Start the current version of the setup program for the OpenScape Browser
Integration.
A31003-S5070-J100-12-7631, 02/2013
521
3) Select the Remove option in the opened dialog pictured above.

4) Click on Next.
A confirmation dialog opens.
5) Click on Next in this dialog.
The uninstallation process begins. A new dialog opens that allows tracing the
uninstallation process:
6) Another dialog opens, which marks the end of the uninstallation. Click on the
Finish button in this dialog.
The OpenScape Click-to-Dial-Browser-Plug-in is thus uninstalled and the
uninstallation wizard closes.
7.4.3.8 How to Perform the Uninstallation via the Windows Control Panel
Uninstalling the OpenScape Click-to-Dial-Browser-Plug-in via the Windows
control panel.
To uninstall the OpenScape Click-to-Dial-Browser-Plug-in via the control panel,
proceed as follows:
Step by Step
2) Click on start and select the Control Panel > Programs and Features
option.
3) Select the OpenScape Browser Integration entry in the displayed list.
4) Then click on the Remove button.
5) Click on Yes in the open confirmation dialog.
522
A31003-S5070-J100-12-7631, 02/2013
The OpenStage Client
The uninstallation starts.

The OpenScape Click-to-Dial-Browser-Plug-in is thus uninstalled.
7.5 The OpenStage Client

The OpenStage Client is a server application that can be used on telephones of
type OpenStage 60/80 for setting frequently required communications functions
of the OpenScape UC Application.
Some important OpenScape UC Application functions, normally used via the
OpenScape Web Client, the OpenScape Desktop Client Enterprise Web
Embedded Edition or the OpenScape Mobile Client, can be operated by
telephones of type OpenStage 60 or OpenStage 80 via the application
OpenStage Client.
NOTICE: You find detailed operating instructions for the
OpenStage telephone in the manuals OpenStage 60 or
OpenStage 80.
The following OpenScape UC Application features are available via the
OpenStage Client:
Access to the presence function
The telephone displays your currently set presence status.
You can change your presence status via telephone.
Access to your preferred device

NOTICE: Depending on your profile settings in the CMP you may
not have the privilege to change your preferred device. The
system will then always use the ONS number as preferred device.
The telephone displays your currently set device.
You can change your preferred device via telephone.
Access to contact search in the available address books
You can look for contacts in the available address books.
You can directly call the found contact.
Access to your contact list
You can search your contact list for contacts.
You can directly call contacts from your contact list.
Access to your call journal
You can have your call journal displayed. The call journal lists all inbound
and outbound calls.
You can directly call the subscribers (callers and callees) listed in the call
journal.
You can filter the display of call journal entries by date and time.
A31003-S5070-J100-12-7631, 02/2013
523
Access to conferences
You can have your conference list displayed.
You can start conferences you have created yourself.
7.5.1 Installing OpenStage Client

General information about setting up OpenStage Client.
A user can access OpenScape UC Application features from an OpenStage 60 or
OpenStage 80 phone. The installation on the server side required for the
OpenStage Client is described in a previous chapter of this manual.
To access OpenScape UC Application features via the OpenStage 60/80 phones,
configuration works must be performed on the OpenStage 60/80 phones. You
must perform the ensuing steps by accessing the CMP (Common Management
Portal) or the OpenStage 60/80 phone via browser.
7.5.1.1 How to Install the OpenStage Client Application

Description of the process of setting up the main application "OpenStage Client"
on an OpenStage phone.
You must execute the following configuration steps for accessing OpenScape
UC Application features via the OpenStage Client:
Step by Step
1) Check the following in the CMP (Common Management Portal): The
OpenStage phone has been assigned to an OpenScape UC Application user
and has an ONS number. The required licenses are available for this user.
a) To do this, open in the CMP Users Management > Administration >
Users & Resources.
b) Select the relevant user with a click.
c) Open the Resources tab.
524
A31003-S5070-J100-12-7631, 02/2013
2) Make sure that the OpenStage phones and the application computer can
communicate with each other via port 7789. This port may not be blocked by
a firewall.
3) Enter the following address in a browser:
https://<IP_address_of_the_OpenStage_phone>
A31003-S5070-J100-12-7631, 02/2013
525
4) Switch to the Administrator Pages tab.
5) Enter the password and click the Login button.

6) Click on the Applications link in the selection menu on the left.
7) Click the XML Applications entry.
8) Click on the Add application entry.
526
A31003-S5070-J100-12-7631, 02/2013
9) Enter the following values in the opened mask:

a) Display name:
Enter an arbitrary name, e. g. OS UC Appl..
This name appears on the tab that provides the OpenScape
UC Application features on the OpenStage phone.
b) Application name:
A31003-S5070-J100-12-7631, 02/2013
527
Enter exactly the following value:

openstage-client
c) HTTP Server Address:
For a Small Deployment scenario: Enter the IP address of the application
computer.
For a Large Deployment or Very Large Deployment scenario: Enter the IP
address of the load balancer computer.
d) HTTP Server port:
Enter value 7789.
e) Protocol:
Keep value http.
f)
Program name on server:

openstage-client/main.ipp
10) Click the Submit button.

11) Push key
on the OpenStage phone for displaying the Applications tab
on the OpenStage phone.
You may have to push this key repeatedly to move from the current to the
required tab.
The OpenStage phone display shows an OS UC Appl. entry on the
Applications tab.
12) Select this entry and push the OK key.
The OpenStage Client of the OpenScape UC Application starts and a tab
called OS UC Appl. is created. We used this name above as example of
specifying the display name.
528
A31003-S5070-J100-12-7631, 02/2013
NOTICE: Updating the OpenStage Client on the server side is

included in the osc-setup up command (see the chapter on
updating, upgrading and migrating). In there you also find a
description of only updating the OpenStage Client.
7.5.1.2 How to Install the Phonebook Application

Installing the Phonebook application for the OpenStage phone.
You can use the OSIPP to replace the Phonebook application on the OpenStage
phone. Instead of the local phonebook the user can see the contact list and the
directory search by enabling the keys to the right of the display.
Installing the Phonebook application requires the following work steps:
Step by Step
1) Open the configuration dialog of your OpenStage phone via web browser. See
the section about installing the main application on this.
2) Click the Applications entry.
4) Click the Add phonebook application entry.
Specify the following values:
A31003-S5070-J100-12-7631, 02/2013
529
a) Display name:
Enter an arbitrary name, e. g. Phonebook.
openstage-client-pb
Small Deployment: Enter the IP address of the application computer.
Large Deployment and Very Large Deployment: Enter the IP address of
the load balancer computer.
Enter value 7789.
e) Protocol:
Keep value http.
f)

openstage-client/phonebook.ipp
g) Use Proxy:
Set the value to No.
h) XML Trace enabled:
i)
Number of tabs:
Set the value to 2.
j)
Tab 1 Display name:

Enter an arbitrary name, e. g. Contact List.
k) Tab 1 Application name:

openstage-client-pb
l)
Tab 2 Display name:

Enter an arbitrary name, e. g. Directory Search.
m) Tab 1 Application name:

openstage-client-ds
530
A31003-S5070-J100-12-7631, 02/2013
If a phonebook application has been configured beforehand, an error

message is now issued. In this case, open Applications > XML
Applications > Modify/Delete application and change the values according
to the above sub-steps.
6) Push key
on the OpenStage phone for displaying the Applications tab.
required tab.
The display of the OpenStage phone shows the Phonebook entry on the
Applications tab.
The OpenStage client of the OpenScape UC Application starts and a
Phonebook tab is created.
7.5.1.3 How to Install the Call Log Application

Installing the Call Log application for the OpenStage phone.
You can use the OSIPP to replace the Call Log application on the OpenStage
phone. Instead of the local call log the user can see the OpenScape journal by
enabling the keys to the right of the display.
Installing the Call Log application requires the following work steps:
Step by Step
4) Click the Add phonebook application entry.
A31003-S5070-J100-12-7631, 02/2013
531
a) Display name:
Enter an arbitrary name, e. g. Call Log.
openstage-client-jrn
Large Deployment and Very Large Deployment: Enter the IP address of
the load balancer computer.
Enter value 7789.
e) Protocol:
Keep value http.
f)

openstage-client/journal.ipp
g) Use Proxy:
h) XML Trace enabled:
i)
Number of tabs:
Set the value to 0.

If a call log application has been configured beforehand, an error message is
now issued. In this case, open Applications > XML Applications > Modify/
Delete application and change the values according to the above sub-steps.
6) Push key
on the OpenStage phone for displaying the Applications tab.
required tab.
The display of the OpenStage phone shows the Call Log entry on the Applications tab.
The OpenStage client of the OpenScape UC Application starts and a Call
Log tab is created.
532
A31003-S5070-J100-12-7631, 02/2013
7.5.1.4 How to Configure the DSS Keys

Configuring the DSS keys on the OpenStage phone.
You can use the keys on the OpenStage phone to the right of the display as
shortcut for invoking specific features.
Configuring the DSS keys requires the following work steps:
Step by Step
3) Click the System entry.
4) Click the Features entry.
5) Click the Program Keys entry.
6) Select the Send URL value from a combo box still unused and click on Edit
to the right of the combo box.
A31003-S5070-J100-12-7631, 02/2013
533
a) Key label:
Enter an arbitrary name, e. g. Contact List.
b) Protocol:
Keep value http.
c) Web Server address:
Enter the IP address of the application computer.
d) Port:
Enter value 7789.
e) Path:
f)
Parameters:
rfscp=true&p=<ONS number>
NOTICE: For the <ONS number> parameter enter the
normalized ONS number without + sign of the user for this
OpenStage phone.
g) Method:
Set the value to GET.
534
A31003-S5070-J100-12-7631, 02/2013

8) Select the Send URL value from another idle combo box and click on Edit to
the right of the combo box.
9) Specify the following values:
A31003-S5070-J100-12-7631, 02/2013
535
a) Key label:
Enter an arbitrary name, e. g. Directory Search.
b) Protocol:
Keep value http.
c) Web Server address:
Enter the IP address of the application computer.
d) Port:
Enter value 7789.
e) Path:
f)
Parameters:
rfsc=true&p=<ONS number>
NOTICE: For the <ONS number> parameter enter the
normalized ONS number without + sign of the user for this
OpenStage phone.
g) Method:
Set the value to GET.
You can now use the two newly allocated keys to the right of the display for
invoking your Contact List via the first key and the Directory Search
via the second key.
IMPORTANT: If you have problems with implementing the steps
in this section, check whether the latest software version is
installed on your OpenStage phone.
536
A31003-S5070-J100-12-7631, 02/2013
7.6 OpenScape Client Integrations

General Information about OpenScape Client Integrations
After installing OpenScape Client Integrations you can use the Click-to-Dial
function independently of setting up the CTI client OpenScape Desktop Client
Enterprise Web Embedded Edition. You can thus implement this function in many
clients and use it there.
7.6.1 OpenScape Client Integrations Features

Features of the OpenScape Client Integrations.
OpenScape Client Integrations allows initiating a phone call via any journal
entries from within specific clients (click-to-dial) for which this function has been
installed.
The following functions are provided via the OpenScape Client Integrations:
Callback to originators of any messages.
Direct call, for example via any contact, calendar and task entries that contain
contact information.
After initiating the call, the call control in the OpenScape Web Client opens
automatically if the URL of the OpenScape Web Client is entered in the Client
Integration setup and the "Use Click to Communicate" option has been set.
Direct call via selected phone numbers on internet pages for the browsers
Microsoft Internet Explorer and Mozilla Firefox.
A31003-S5070-J100-12-7631, 02/2013
537
7.6.2 Supported Clients

List of clients via which the OpenScape Client Integrations features can be used.
You can install the OpenScape Client Integrations features using the OpenScape
Client Integrations setup for the following clients:
Microsoft Outlook
IBM Lotus Notes

NOTICE: You can use the click-to-dial feature in IBM Lotus Notes
for contact entries only.
Sametime Connect
Microsoft Internet Explorer
Mozilla Firefox
You find the latest information about the supported clients and their versions in
the OpenScape UC Application Planning Guide manual.
7.6.3 Installation Requirements

Requirements for setting up the OpenScape Client Integrations.
The following requirements must be met for installing the OpenScape Client
Integrations:
The .Net Framework 3.5 must have been installed on the workstation.
The installation requires administrative privileges on the workstation where

the installation shall be performed.
The OpenScape Client Integrations is always set up for all users who deploy
this workstation.
Before you start the setup you need to shut down the application for which you
wish to install the OpenScape Client Integrations. Otherwise, an error
message will inform you that the application concerned is still active and must
be shut down before the installation can be performed.
Furthermore, you need to heed the following points:
538
Only those OpenScape Client Integrations components for which an appropriate client application is already available are provided in the setup for
installation.
Only those OpenScape Client Integrations components that are not yet
present on the workstation are provided in the setup for installation.
If the OpenScape Client Integrations components have already been installed

in the course of the OpenScape Desktop Client Enterprise Web Embedded
Edition setup, their installation via the OpenScape Client Integrations setup is
blocked. The setup then terminates with a corresponding error message.
A31003-S5070-J100-12-7631, 02/2013
If the OpenScape Click-to-Dial-Browser-Plug-in has already been installed

via the OpenScape Web Client, missing components can be additionally
installed during the OpenScape Client Integrations setup.
You find the setup files required for the OpenScape Client Integrations on the
setup DVD in path:
win32\ClientIntegrations.zip
7.6.4 Setup Adjustments

Adjustments for setting up the OpenScape Client Integrations.
As a rule, setup adjustments are not required. In case of an automatic installation,
the required parameters are applied by group policy instead of manipulating the
msi-files. In this context, the values for the domino server name and the Web
Client URL are set via registry keys. The following parameters can be set via
group policy:
Domino server name: [Type String]

HKEY_LOCAL_MACHINE\Software\Siemens\NotesConfiguration\Servername
Web Client URL: [Type String]

HKEY_CLASSES_ROOT\mmo\WebURL
For some commands it is possible to transfer parameters to the .msi setup

package directly via the Config.ini. The following commands can be transferred via the config.ini:
WebClientAddress=
Transfers the OpenScape Web Client URL directly to the msi-package.
CommandLine=
Transfers the parameters allowed for executing the Windows Installer. For
example, with Commandline=\qn the setup is performed automatically
without user interaction (silent mode).
Activation=0
NOTICE: This command must be manually supplemented in the
[WiseInstaller] category.
Supplement this command if the Click-to-Dial browser plug-in shall at first be
disabled. Activation must then occur via the configuration dialog of the
respective browser application (Microsoft Internet Explorer or Mozilla Firefox).
RequestString=
Without significance here.
A31003-S5070-J100-12-7631, 02/2013
539
7.6.5 Installing the OpenScape Client Integrations

Process of setting up the OpenScape Client Integrations.
NOTICE: The setup dialogs are in English language only.
How to install the OpenScape Client Integrations for the previously mentioned
clients:
Step by Step
1) Start the setup file InstallClientIntegrations.exe. The following
dialog opens:
2) Click on Next > to start the installation. The following dialog opens:
540
A31003-S5070-J100-12-7631, 02/2013
3) Enter your name in the Full Name field and the company name in the Organization field. Then click on Next >. The following dialog opens:
4) Select the client application for which the OpenScape Client Integrations shall
not be installed. The OpenScape Client Integrations installation is selected for
all available client applications by default.
To exclude a component from installation, click in the list field on the arrow
icon and select the Entire feature will be unavailable option in the
context menu.
You can use the Reset button to return to the default after having
performed a setting.
With a click on the Disk Cost button you can display the drive
environment of this system to detect possibly available memory.
You can install the following components:
Microsoft Outlook
Lotus Notes
Sametime Connect
Sametime Connect for Notes 8
Microsoft Internet Explorer
Mozilla Firefox
Setup always occurs in the ...\Program Files\Siemens directory be

default.
A31003-S5070-J100-12-7631, 02/2013
541
5) After you have specified your setup defaults, click on Next >. The following
configuration dialog opens:
6) Enter the URL for your Web Client in the input line under OpenScape Web
Client host address. The call is initiated via the OpenScape Web Client. To
specify the host address you can use the IP address (example: http://
100.100.100.100:7789) or the server name (example: https://
webclient.company.com).
7) Click on the Check server address button. If the entered server address is
valid, the following message of success is issued:
If the entered server address is invalid, the following error message is issued:
8) The Use Click To Communicate option lets you determine that the
OpenScape Web Client call control opens automatically when a call is
initiated via the Click-to-Dial feature.
9) Enter in the next input line the path to the directory server for connecting a
Lotus Notes server. Make this entry in the format <domain/server> (example:
Sametime/Data). This enables dialing directly from the default Notes
directory without any previous configuration.
542
A31003-S5070-J100-12-7631, 02/2013
10) Click on Next > to start the installation. The next dialog displays the installation progress.
A click on the Cancel button abandons the installation process.

11) When the installation is done, the following dialog appears:
12) Click on the Finish button to conclude the installation.

Setting up the OpenScape Client Integrations for the selected client applications
is now complete.
7.6.6 Updating and Uninstalling via the Setup File

Performing a modification, repairing or uninstalling the application.
After the installation you can invoke the setup routine once more for performing
maintenance tasks:
Changing the setup settings that were performed during the initial installation.
A31003-S5070-J100-12-7631, 02/2013
543
Repairing the application if program errors occur or a new program version is

to be installed.
Uninstalling the application.
After you have started the setup routine anew, a dialog opens for selecting and
performing the desired action.
The following actions are available:
Modify: Select this option if you wish to change application settings you
performed during the previous setup.
Repair: Select this option if the application does not work properly because
files are damaged or missing. The application will then completely be
reinstalled.
Remove: Select this option if you wish to remove the application from your
workstation.
7.6.6.1 How to Change Program Settings

Changing application parameters of OpenScape Client Integrations via the setup.
How to change the settings performed during the OpenScape Client Integrations
setup:
544
A31003-S5070-J100-12-7631, 02/2013
Step by Step
maintenance dialog opens:
2) Select the maintenance option Modify.

3) Click on Next > to initiate the selected action.
You are guided through the installation steps you ran through during the initial
installation and can adjust your settings.
7.6.6.2 How to Update or Repair

Updating or repairing OpenScape Client Integrations via the setup.
How to install a more recent version of the application or perform a new installation because of errors in the application:
A31003-S5070-J100-12-7631, 02/2013
545
Step by Step
2) Select the maintenance option Repair.

The setup routine starts. The application will then completely be reinstalled.
7.6.6.3 How to Uninstall the Program

Uninstalling OpenScape Client Integrations via the setup.
NOTICE: OpenScape Client Integrations should be uninstalled in
the usual manner via Control Panel > Programs and Features.
How to completely remove the application from your workstation via the setup:
546
A31003-S5070-J100-12-7631, 02/2013
Step by Step
2) Select the maintenance option Remove.

The uninstallation routine starts and the application is completely removed from
your system.
A31003-S5070-J100-12-7631, 02/2013
547
548
A31003-S5070-J100-12-7631, 02/2013
IG_InstallFacadeServer.fm
Installing the Mobile Client Facade Server
8 Installing the Mobile Client Facade Server

IMPORTANT: We recommend using FSecure V 5.54 as virus scan for the Mobile
Client Facade server on SLES. No directories must be excluded from a virus
scan.
A Facade server is necessary to support the OpenScape Mobile Client.
The OpenScape UC Application Mobile Client is an OpenScape Desktop Client
Enterprise Web Embedded Edition with a reduced feature set, running on mobile
devices (e.g. BlackBerry/RIM, Nokia/Symbian, PDA/Windows Mobile). This client
communicates with the OpenScape UC Application infrastructure using mobile
data services (GPRS, UMTS). To use the mobile clients, the OpenScape UC
Application users need to order a data option for their mobile contract.
On the OpenScape UC Application side a DMZ with internet connectivity is
required. Within the DMZ, a so-called Facade server is installed which is the
endpoint of the incoming internet connection from the client. This connection
requires only one port to be open in the outer firewall.
Requirements:
Additional Facade server computer acting as application layer proxy located

in a DMZ
IP address with associated Internet DNS host name
Port forwarding for one port to the faade server

The firewall between the internet and the Facade server computer must be
set to enable forwarding the default ports 8081 (HTTP) and/or 8443 (HTTPS)
to the Facade server computer.
Dedicated ports (4708 and 4709) open in interior firewall for communication
between the Facade server and the application computer.
For Large Deployment these ports need also to be open on all existing
frontend computers and on and all existing media server computers to allow
communication between these computers and the Facade server computer.
See also Table 38 on page 373, Table 57 on page 397, Table 75 on page 422,
Table 76 on page 426 and Table 77 on page 429.
IMPORTANT: We strongly recommend to install the Facade server on a

separate computer in the DMZ, because it is a terminating point for connections
from the Internet.
A31003-S5070-J100-12-7631, 02/2013
549
The Facade server computer may have two network boards. In this case one
network board is connected to the network the internet is connected to, and the
other network board is connected to the network in which you find the OpenScape
UC Application. Verify that the routing table has the correct entries. The routing
table is displayed in a command line by the route command.
If the OpenScape UC Application is connected to groupware (IBM Lotus Domino,
Microsoft Exchange Server), the Active Directory can be searched for contacts
from the OpenScape Mobile Client. No configuration on the Mobile Client Facade
server is required for this purpose. This is independent from whether the Facade
server has been installed on SLES or Windows.
550
A31003-S5070-J100-12-7631, 02/2013
Supported Operating Systems
8.1 Supported Operating Systems

New installation
The Mobile Client Facade server can be newly set up on the following operating
system:
SLES 11 SP1 and SP2 in the 64-bit version. SP2 is recommended.
Upgrade
The Mobile Client Facade server can be upgraded on the following operating
systems:
SLES 11 SP1 and SP2 in the 64-bit version
NOTE: For upgrades, back up the properties.ini file and the conf directory
in the Tomcat setup directory (for example
D:\Program Files\Apache Software Foundation\Tomcat 6.0\),
install the Facade server on SLES, rename the properties.ini file to
facade.properties, copy the backed up directory to the new Tomcat setup
directory (/usr/local/tomcat6) and copy facade.properties to /usr/
local/tomcat6/conf. Possible certificates must also be backed up and
copied.
A31003-S5070-J100-12-7631, 02/2013
551
Installing the Mobile Client Facade Server on SLES
8.2 Installing the Mobile Client Facade Server on SLES

Requirements:
The computer should meet the hardware requirements specified in the

OpenScape UC Application, Planning Guide. If you are using a virtual
computer, you will find the settings for this virtual computer in Table 2 on page
36 in this installation and upgrade guide.
SLES 11 SP1 and SP2 in the 64-bit version has been installed. SP2 is
recommended.
Login as root.
8.2.1 Installation with the Help of the Installation

Script
Installation
1. Provide the Repository ISO file and the BasePackage ISO file according to
Section 5.3, Installation, on page 233 and, if required, install or update oscsetup.
The files available in these two ISO files are thus provided in the directory that
you assigned by using the -l option when creating the repository in osc-setup
(see e. g. step 15 on page 240):
Example:
/tmp/tmpRepo
The following file from the Repository ISO file is required for setting up the
support/installFacadeServer.sh
The following file from the BasePackage ISO file is required for setting up the
contrib/FacadeServerSoftware-<version>.zip
2. Execute a command according to the following pattern in the directory that is
assigned to the linked repository in osc-setup:
bash installFacadeServer.sh ip=<IP address> [servername=<server name>] [source=<path>]
[httpport=<HTTP port>] [httpsport=<HTTPS port>] [-update]
552
A31003-S5070-J100-12-7631, 02/2013
executed and closing the actual input window (<CTRL>+A+D) to resume the
a) The parameter sequence is irrelevant.
b) <IP address>
IP address of the application computer, even for Large Deployment
c) <server name>
Fully qualified name (FQDN) of the computer the IP address of which you
used in the previous step. If you use Large Deployment or Very Large
Deployment, please be sure to deploy exactly the same frontend
computer.
This computer name is used for the NAT. Leave this parameter empty if
the FQDN is unavailable.
d) <path>
Path to the mounted ISO file. If you do not use the source parameter, the
script assumes to have been invoked in the support directory of the ISO
file.
e) <HTTP port>
This parameter is used for changing the default HTTP port (8081) on the
Mobile Client Facade Server computer for connections to the internet. If
this parameter is empty (httpport=), the HTTP connector is inactive.
f) <HTTPS port>
This parameter is used for changing the default HTTPS port (8443) on the
Mobile Client Facade Server computer for connections to the internet. If
this parameter is empty (httpsport=), the HTTPS connector is inactive.
g) -httposcconnection
If you use this parameter, the Mobile Client Facade Server computer is
connected to the application computer by using HTTP (default port 4708
on the application computer) instead of the default protocol HTTPS
(default port 4709 on the application computer).
For Large Deployment port 4708 or port 4709 also needs to be open on
all existing frontend computers and on and all existing media server
computers to allow communication between these computers and the
Mobile Client Facade Server computer.
A31003-S5070-J100-12-7631, 02/2013
553
h) -update
IMPORTANT: If you use this parameter, the /usr/local/tomcat6/
conf/facade.properties file is reset to the default values. For
example, the use of HTTP is reset to the use of HTTPS. Therefore, back
up the facade.properties file before using this parameter and restore
the facade.properties file after using this parameter.
IMPORTANT: If the original certificate /usr/local/tomcat6/conf/

OSC-Facade-Server-Default-Cert.p12 had been replaced by a
custom certificate, save it to a different location before updating the
mobile client facade server since it would be overwritten. Restore it after
the update.
This parameter is used if an update (e. g. by a hotfix) is performed instead
of an installation. In this case, a JRE is only installed if it is of a newer
version than the one already installed.
i)
-uninstall
This parameter uninstalls the Mobile Client Facade Server.
Example command:
bash installFacadeServer.sh -uninstall
Example output:
installFacadeServer.sh version 1.1
Uninstalling OpenScape Mobile Facade Server ...
Stopping Tomcat ...
Deleting files and folders: /usr/local/facade /usr/local/
tomcat6 /etc/init.d/catalinad$ /etc/init.d/facaded ...
Uninstalling JRE ...
Deleting user sym ...
OpenScape Mobile Facade Server was uninstalled
successfully!
Example command:
bash installFacadeServer.sh source=/mnt/OpenScape ip=10.9.132.4 httpport=80 httpsport=
-update
3. Confirm the listed specifications by entering yes and subsequently pushing
the return key.
NOTE: The Tomcat server is installed in a sub-directory of /usr/local/
facade/, for example /usr/local/facade/apache-tomcat-6.0.32.
554
A31003-S5070-J100-12-7631, 02/2013
4. The computer reboots and the Mobile Client Facade Server starts
automatically after the installation.
If you need to start the server manually, use the following command:
/etc/init.d/facaded start
If you need to stop it, use the option stop. The option restart restarts it and
the option status shows its status.
If you wish to use HTTPS between the Mobile Client Facade server computer and
the application computer, continue with step 5 on page 556. If you wish to use
HTTP, continue with step 17 on page 558.
A31003-S5070-J100-12-7631, 02/2013
555
Connection via HTTPS

5. Execute the following command on the application computer after the
Mobile Client Facade server computer has been rebooted:
/opt/siemens/servicetools/install/bin/installlib.sh createdar -Dpath=osc-trustore.zip
NOTE: Use /enterprise/... instead of /opt/siemens/... for
6. Copy the osc-trustore.zip file thus created to the Mobile Client Facade
server computer. In the following, we call the path to the directory in which the
file is stored <certificate path>.
7. Copy the /contrib/FacadeServerSoftware-<version>.zip file from
the ISO file into the /tmp directory on the Mobile Client Facade server
computer.
NOTE: If using Blackberry mobile clients causes problems, use the file
ClientSoftware-<version>.zip instead of the file
FacadeServerSoftware-<version>.zip.
8. Unpack the file to /tmp/FacadeServerSoftware-<version>:
cd /tmp
unzip FacadeServerSoftware-<version>.zip
9. Copy the files importTrust.sh and cert-import-tool.jar into the
<certificate path> directory.
cd /tmp/FacadeServerSoftware-<version>/linux_environment
cp importTrust.sh <certificate path>
cp cert-import-tool.jar <certificate path>
10. Execute the following command to import the certificates:
bash importTrustCA.sh <certificate path>/osc-trustore.zip
11. The following applies for the /usr/local/tomcat6/conf/
facade.properties file:
a) serverPort=4709
This is a default setting to be changed only if required.
b) https = true
This is a default setting to be changed only if required.
c) If you did not use the servername parameter in step 2 on page 552 when
invoking the installation script, set now the serverName parameter that
contains the fully qualified name (FQDN) of the computer the IP address
556
A31003-S5070-J100-12-7631, 02/2013
of which you used in step 2b on page 553 file.

This computer name is used for the NAT.
Leave this parameter empty if the FQDN is unavailable.
NOTE: The parameter of the installation script reads servername, but
the parameter in the facade.properties reads serverName.
Example:
serverName=mcfs1.site
NOTE: This parameter is used for setting the host property in the SOAP
command.
NOTE: /usr/local/tomcat6/ is a symbolic link to /usr/local/

apache-tomcat-<version>/.
12. Save the modifications.
13. Copy the default certificate from the FacadeServerSoftware<version>.zip file unpacked in step 8 on the Mobile Client Facade server
computer:
cp /tmp/FacadeServerSoftware-<version>/OSC-Facade-Server-Default-Cert/OSC-Facade-ServerDefault-Cert.p12 /usr/local/tomcat6/conf/
14. Messages about self-signed certificates being used will appear on the mobile
clients.
NOTE: Please obtain details of Android mobile phones and iPhones from the
documentation OpenScape Mobile (not OpenScape UC Application Mobile
Client!).
You can avoid this on all mobile clients also. Copy the file .../OSCFacade-Server-Default-Cert/OBSO.cer from the file
FacadeServerSoftware-<version>.zip unpacked in step 8 on page
556 to the mobile client.
15. Reboot the Mobile Client Facade server computer.
16. Setting up the Mobile Client Facade server is now complete.
A31003-S5070-J100-12-7631, 02/2013
557
Connection via HTTP

17. Perform the following settings in the /usr/local/tomcat6/conf/
facade.properties file:
a) serverPort=4708
Do not use 4709, because you cannot deploy the JRE used for HTTPS
without further steps.
b) https=false
19. In the CMP, click under Maintenance > Inventory > Nodes &
Applications > Nodes > <name of the application computer> >
Actions > Show services status on the Show button.
20. Enter value Connector HTTP protocol in the Filter field and click on Go.
21. Activate the check box that precedes Connector HTTP protocol and click on
Start/Stop.
22. Close the window.
23. Click on Close.
24. Check whether you can access the OpenScape UC Application with the
mobile client.
Setting up the Mobile Client Facade server is now complete.
558
A31003-S5070-J100-12-7631, 02/2013
8.2.2 Diagnosing the Facade Server
You find the Tomcat log files in the /usr/local/tomcat6/logs directory.
The current end of catalina.out can be displayed to the console with:

tail -f catalina.out
NOTE: The Facade server produces, on reaching the maxLogFileSize, a
new log file, facade_{1..9}.log.
The default directory of the Facade log files is /usr/local/tomcat6/

logs. You can configure this path in the following file:
/usr/local/tomcat6/conf/facade.properties
To do this, edit the logfile parameter.
Example:
logfile = ../logs/facade_{1..9}.log
NOTE: {1..9} is a regular expression.
The current end of facade_{1..9}.log can be displayed in the console

with:
tail -f facade_{1..9}.log
A31003-S5070-J100-12-7631, 02/2013
559
8.2.3 Deployment of the Mobile Client using the

Facade Server
This package is part of the Facade-Installation and it contains the Web site for
Client deployment using the Web browser.
A new directory /download/ is created under the default ROOT path. The
index.htm file contains the information for the clients to be deployed: for
BlackBerry, Nokia, or Windows Mobile Devices.
To access this page use the address http://<IP address of the Mobile
Client Facade server>:8081/download. For installation of the client from
this site, the link to this page must be opened using the device's web browser.
IMPORTANT: Direct installation is not supported for Blackberry devices!
The direct installation from the device's Web-browser is possible only for Nokia
and Windows Mobile Devices.
For Blackberry devices, the applicable client package must be fetched using a
desktop PC, and the new software must be installed by the Blackberry Desktop
Manager. For additional information, refer to the OpenScape UC Application
Mobile Client operating instructions.
For the client deployment via Web-for-Windows mobile devices, the Facade
server must support the extensions .cab and .CAB within the MIME mapping.
Check the mime-mapping in the facade configuration ...\Tomcat
6\conf\web.xml. If the cab or CAB extension is missing in the Web.xml file,
add the following Web.xml content:
...
<mime-mapping>
<extension>cab</extension>
<mime-type>application/octet-stream</mime-type>
</mime-mapping>
<mime-mapping>
<extension>CAB</extension>
<mime-type>application/octet-stream</mime-type>
</mime-mapping>
...
560
A31003-S5070-J100-12-7631, 02/2013
Updating the Mobile Client Facade Server
8.3 Updating the Mobile Client Facade Server

You update the server like installing it, but you must use the parameter -update
(see step 2h on page 554).
8.4 Uninstalling the Mobile Client Facade Server

You uninstall the server like installing it, but you must use the parameter
-uninstall (see step 2i on page 554).
Example command:
bash installFacadeServer.sh -uninstall
Example output:
installFacadeServer.sh version 1.1
Uninstalling OpenScape Mobile Facade Server ...
Stopping Tomcat ...
Deleting files and folders: /usr/local/facade /usr/local/tomcat6
/etc/init.d/catalinad$ /etc/init.d/facaded ...
Uninstalling JRE ...
Deleting user sym ...
OpenScape Mobile Facade Server was uninstalled successfully!
A31003-S5070-J100-12-7631, 02/2013
561
Uninstalling the Mobile Client Facade Server
562
A31003-S5070-J100-12-7631, 02/2013
IG_InstallWebCollaboration.fm
Installing the OpenScape Web Collaboration
9 Installing the OpenScape Web Collaboration

Setting up the OpenScape Web Collaboration is outlined in the installation guide
OpenScape Web Collaboration, Installation and Upgrade.
You find the OpenScape Web Collaboration configuration in the administrator

A31003-S5070-J100-12-7631, 02/2013
563
IG_InstallWebCollaboration.fm
Installing the OpenScape Web Collaboration
564
A31003-S5070-J100-12-7631, 02/2013
Installing and Configuring OpenScape Fusion for Google Apps

Installing OpenScape Fusion for Google Apps
10 Installing and Configuring OpenScape Fusion for

Google Apps
Google Apps is a Google service that offers independently adjustable versions of
different Google products under an adjusted domain name. Amongst other things,
the service provides different web applications with similar functionalities as you
know them from traditional office suites such as Gmail, Google Groups, Google
Calendar and Google Docs.
The functions of OpenScape Fusion for Google Apps are provided via Google
Gadgets. This denotes web-based applications implemented in the user interfaces of the Google Mail and Google Calendar applications.
NOTICE: Please obtain further information from the operating
guide OpenScape UC Application V7 Client Applications.
10.1 Installing OpenScape Fusion for Google Apps

You install OpenScape Fusion for Google Apps on a separate computer in a DMZ
to gain access to the OpenScape UC Application in the corporate network
(intranet) from the Google domain in the internet.
10.1.1 Requirements
Please refer to the OpenScape UC Application V7 Planning Guide for the
supported hardware and software requirements.
10.1.2 Installation on the Application Computer

No further installations are required on the application computer.
10.1.3 Installation on the Google Apps Computer

10.1.3.1 Installing the Java Runtime Environment
Download the latest Java6 run-time environment (jre-6u<version>-linuxx64-rpm.bin) from the internet and copy the file into the /tmp directory. If it
does not exist yet, create it.
1. Switch to the /tmp directory.
cd /tmp
2. Modify the access privileges of the Java setup package.
A31003-S5070-J100-12-7631, 02/2013
565

chmod 755 jre-6u<version>-linux-x64-rpm.bin

Example
chmod 755 jre-6u31-linux-x64-rpm.bin
3. Execute the following command to perform the Java installation:

./ jre-6u<version>-linux-x64-rpm.bin
Example
./ jre-6u23-linux-x64-rpm.bin
4. Switch to the /usr/java directory.
cd /usr/java
5. Create a symbolic link for the Java setup directory to facilitate the update
procedure at a later date.
ln -s <absolute Java directory> java6
Example
ln -s /usr/java/jrel.6.0_31 java6
Execute the java -version command to check the installation of the Java runtime environment. This example's output reads:java version "1.6.0_31"
Java(TM) SE Runtime Environment (build 1.6.0_31-b04) Java
HotSpot(TM) 64-Bit Server VM(build 20.6-b01, mixed mode)
10.1.3.2 Installing the Google Apps Computer Application

You install the Google Apps computer software via the fusion-webapp<version>.zip file. You can download this file from the Software Supply Server.
1. Create a directory named software in the root directory.
mkdir /software
2. Switch to the /software directory.
cd /software
3. Copy the file fusion-webapp-<version>.zip into the newly created directory

and unpack it.
unzip fusion-webapp-<version>.zip
Example
unzip fusion-webapp-1.1.11.0.zip
List of the example's unpacked files:
566
apache-tomcat.tar.gzr
EULA_OpenScape_Fusion_for_Google_Apps.pdf
install_googleapps.sh
webapp-bin.zip
webapp-conf.zip
webapp-etc.zip
webapp-libs.zip
webapp-ui-calendarsidebar.war
webapp-ui-google-mail.war
webapp-ui-mainsidebar.war
A31003-S5070-J100-12-7631, 02/2013

WebAppUcServlet.war
4. Modify the access privileges of the install_googleapps.sh file.
chmod 755 install_googleapps.sh
5. Install the RPM package.
./install_googleapps.sh | tee /software/install.log
10.1.3.3 Installing the Google Apps Presence Service

You find the files required for installing the Presence service in the ZIP file
GooglePresenceSync_<version>.zip. You can download this file from the
Software Supply Server.
cd /software
2. Create a directory named pres.
mkdir pres
3. Copy the file GooglePresenceSync_<version>.zip into the newly created

directory and unpack it.
unzip GooglePresenceSync_<version>.zip
Example
unzip GooglePresenceSync_1.1.11.0.zip
init.d
plugins
sysconfig
ApacheLicense.txt
CommonConfig.xml
config.ini
fusion-webapp-product-info.dat
install.sh
log4j-PresenceSync.xml
osgi.bat
osgi.sh
ProductInfo.txt
readme.txt
uninstall.sh
4. Modify the access privileges of the install.sh file.
chmod 755 install.sh
5. Install the RPM package.
./install.sh GooglePresenceSync_<version>.zip | tee /

software/pres/install.log
A31003-S5070-J100-12-7631, 02/2013
567

Configuring the OpenScape Fusion for Google Apps
10.2 Configuring the OpenScape Fusion for Google Apps

You perform the configuration on the application computer and on the Google
Apps computer. The configuration includes creating and modifying configuration
files.
10.2.1 Configuration on the Application Computer

10.2.1.1 Creating Users in OpenScape UC
GoogleApps users who wish to use OpenScape UC features must be assigned
an appropriate user account in OpenScape UC.
When you create a GoogleApps user, a unique OpenID is assigned to him/her.
The OpenID is part of the e-mail address. When a user logs on to the Google
domain, he/she is automatically logged on to OpenScape UC.
If you wish to add a GoogleApps user in OpenScape UC, you need to assign an
ExternalID with the Google e-mail address to the OpenScape UC. The
ExternalID is specified in a file and imported via the CMP.
To create a user in the Google Domain and in OpenScape UC you need to heed
the following rule:
Google user name = OpenScape UC user name

Example: GoogleApps user e-mail address: muller@ucdomain.de,
OpenScape UC user e-mail address: muller@system. In this case the
ExternalID muller is used by OpenScape UC automatically.
You can specify exceptions and manual ExternalIDs if you cannot apply the
"user rule". To do this you can create a csv-file with the following content:
csv - file
##ExternalId
externalId
assignedUserIdentity
assignedExternalSystemId
externalId
muller@ucdoma peter.muller@sy FusionWebApp

in.de
stem
isContactMaster isProvisioningMaster
false
additionalInfoExternalId
false
Google user muller@ucdomain.de is assigned to OpenScape UC user

peter.muller@system. The csv-file with the ExternalID is then imported in
OpenScape UC via the CMP. You find further information about the CMP in the
OpenScape Common Management Platform V7, Administrator Documentation
manual.
NOTICE: You cannot edit the ExternalID. If you have imported
a faulty ExternalID, delete the faulty record. Correct the faulty
ExternalId in the csv-file and import this file anew.
568
A31003-S5070-J100-12-7631, 02/2013

10.2.1.2 Creating a technical User

The GoogleApps server needs a technical user account for evaluating the
presence statuses of the OpenScape UC Application.
1. Log on to the CMP as administrator.
2. Select the Configuration tab.
3. Click on the Unified Communications button.
4. Click on Add.
The Add User.
5. Enter the user name in the Login name and Display Name fields. For
example: Uc_TechUser.
6. Click on the Password/PIN tab.
7. Enter a password and activate the Login password never expires: check
box.
8. Click on the Contact Information tab.
9. Enter the user name next to Last name:. For example: Uc_TechUser.
10. Enter the user_name@<domain> next to IM Address:. For example:
Uc_TechUser@system.
11. Click on the Profiles tab.
12. Activate the check box in the Assigned to user column for Team,
OpenScape UC App.
13. Click on Save.
The technical user is now created.
NOTICE: You must not assign a device to the user. No further
privileges are assigned either.
10.2.1.3 Configuring the LongLivedStatements

A LongLivedStatement.txt file must be created. You find the required files
in the fusion-webapp-osc-<version>.zip package, which you can download
from the Software Supply Server. You need to copy the package into a specific
directory and unpack it there.
To do this, execute the following steps on the application computer:
1. Create a directory named software in the root directory.
mkdir /software
2. Copy the file fusion-webapp-osc<version>.zip into the newly created

unzip fusion-webapp-osc-<version>.zip
Example
unzip fusion-webapp-osc-1.1.4.0.zip
A31003-S5070-J100-12-7631, 02/2013
569

commons-collections-3.2.1.jar
commons-configuration-1.6.jar
commons-lang-2.5.jar
createLongLivedStatement_be.sh
createServiceStatement_fe.sh
EULA_OpenScape_Fusion_for_Google_Apps.pdf
GenerateStatement.jar
3. Create the /software/service-statement directory.

mkdir /software/service-statement
cd /software
5. Modify the user privileges of the createLongLivedStatement_be.sh file.
chmod 755 createLongLivedStatement_be.sh
6. Modify the user privileges of the createServiceStatement_fe.sh file.
chmod 755 createServiceStatement_fe.sh
7. Copy the createLongLivedStatement_be.sh file into the /software/
service-statement directory.
cp createLongLivedStatement_be.sh /software/servicestatement
8. Switch to the /service-statement directory.
cd service-statement
9. Execute the createLongLivedStatement_be.sh file.
./createLongLivedStatement_be.sh
The SymphoniaStatement.cfg file is created and stored in the directory in
which the command was executed.
IMPORTANT: For Large Deployment the files SymphoniaStatement.cfg and fusion-webapp-osc-<version>.zip must be
copied into the same directory on a frontend computer. Please
read chapter Configuring the LongLivedStatements on a FrontEnd Computer on this.
cd /software
11. Create the /software/long-lived-statement directory.
mkdir /software/long-lived-statement
12. You now need to copy the following files from the /software directory into
the /software/long-lived-statement directory:
570
A31003-S5070-J100-12-7631, 02/2013

13. Copy the SymphoniaStatement.cfg file into the /software/longlived-statement directory.

cp /software/service-statement/SymphoniaStatement.cfg /
software/long-lived-statement
./createServiceStatement_fe.sh
The following message is put out:
LongLivedStatement successfully created
LongLivedStatement copied into file LongLivedStatement.txt
The LongLivedStatement.txt is created in the same directory.
10.2.1.4 Configuring the LongLivedStatements on a Front-End Computer

In providing the following instructions we assume that you have executed the
steps in chapter Configuring the LongLivedStatements on the application
computer and that the SymphoniaStatement.cfg file has been created.
1. Create a directory named software in the root directory of the front-end
computer.
mkdir /software
2. Copy the file fusion-webapp-osc<version>.zip into the newly created

unzip fusion-webapp-osc-<version>.zip
Example
unzip fusion-webapp-osc-1.1.4.0.zip
3. Copy the SymphoniaStatement.cfg file from the application computer to the

frontend computer.
cd /software
5. Create the /software/long-lived-statement directory.
mkdir /software/long-lived-statement
6. You now need to copy the following files from the /software directory into
the /software/long-lived-statement directory.
7. Copy the SymphoniaStatement.cfg file into the /software/longlived-statement directory.
cp /software/SymphoniaStatement.cfg /software/longlived-statement
8. Modify the user privileges of the createServiceStatement_fe.sh file.
chmod 755 createServiceStatement_fe.sh
A31003-S5070-J100-12-7631, 02/2013
571


./createServiceStatement_fe.sh
The following message is put out:
LongLivedStatement successfully created
LongLivedStatement copied into file LongLivedStatement.txt
The LongLivedStatement.txt is created in the same directory.
10.2.2 Configuration on the Google Apps Computer

IMPORTANT: After you have completed all configurations, you
need to restart the Google Apps computer. To do this, you can use
the reboot command.
10.2.2.1 Settings of the Poll Interval

The presence synchronization service has the following properties to determine
how the Google events shall be polled. You find the parameters in the
CommonConfig.xml.
p0
t0
t1
pollCalendarMillis
The entered value is given in milliseconds. The entered default value is
3.600.000 milliseconds (1 hour). The value determines the interval of reading
a user's calendar entries twice and specifies the minimum time slot in which
the presence synchronization service searches for the start of a planned
event. For example, if one hour is set as interval, the presence synchronization service will poll events that start within the next hour every hour. The
following sketch represents a sequence.
p1
t2
p2
t3
time
p1 p0
p0, p1 and p2 are points in time at which Google polls events. At t0, the user
plans a new event that starts at t1 and ends at t3. Because start time t1 is
before the next polling, the presence synchronization service will not detect
this event. If the user plans an event at t0 that starts at t2 and ends at t3, the
presence synchronization service will detect this event.
572
additiveCalendarMillis
The entered value is given in milliseconds. The entered default value is
3.600.000 milliseconds (1 hour). The value determines an additional time of
a calendar entry a user has made. The specified time is added to the interval
in which the presence synchronization service searches for the start of an
A31003-S5070-J100-12-7631, 02/2013

event. If pollCalendarMillis has value p milliseconds and additiveCalendarMillis has value a milliseconds, the presence synchronization service will
intercept every event that starts in p+a milliseconds.
10.2.2.2 Configuring the Presence Service

The Presence service synchronizes the Google Apps and application computer.
Do not confuse the Presence service with the presence status, which indicates
the user status.
To configure the Presence service, edit the /opt/siemens/presencesync/
CommonConfig.xml file.
In the XML element <com.siemens.fusion.idmapper.configurable.impl.ConfigurableSubjectMapperImpl> you find the XML
element <replacement>. Specify your domain behind "$1@".
In the XML element <com.siemens.fusion.imapper.openscape.impl.OpenScapeSubjectMapperImpl> you find the XML element <srcEmailDomain>. Enter your domain in there.
You now need to edit the XML element
<com.siemens.fusion.openscape.connector.impl.OpenScapeConnectorImpl>.
<authStmt>: Enter the content of the LongLivedStatement.txt file
<serverAddr>: Enter the IP address or DNS name of the application

computer
<serverPort>: Enter the port. The default value is 4709.
<serverProtocol>: Enter the protocol type. The default value is https.
Further configuration is to be performed at the XML element

<com.siemens.fusion.presencesync.source.google.impl.GoogleSourceAdaptorImpl>.
<additiveCalendarMillis> Specify here the time in milliseconds.

Please read section Poll Interval Settings on this.
<googleDomain>: Enter your Google domain
<googleDomainToken> Enter your Google authentication code

Please read section Google Domain Authentication Token to learn how to
obtain the Google authentication code.
<pollCalendarMillis> Specify here the time in milliseconds. Please read

section Poll Interval Settings on this.
The next configuration is to be performed at the XML element

<com.siemens.fusion.presencesync.target.openscape.impl.openscapeTargetAdaptorImpl>.
<validBeginOscState> Enter here the presence status your user is to

have after the login. AVAILABLE is entered by default. The following
presence statuses are possible:
UNKNOWN
NO_INTERRUPTIONS
A31003-S5070-J100-12-7631, 02/2013
573

BE_RIGHT_BACK
UNAVAILABLE
BUSY
IN_MEETING
AVAILABLE is entered by default.
If you wish to provide several presence statuses to your user proceed as follows.
Copy the following three lines from the CommonConfig.xml:
<arryItem>
<oscType type="com.siemens.fusion.openscape.connector.UserPresenceState">BUSY</oscType>
</arryItem>
Paste the lines in the XML-tag <validBeginOscStates> right behind the first
XML-tag <arrayItem>.
<arryItem>
</arryItem>
<arryItem>
</arryItem>
Edit the presence status. Repeat the process with every presence status to be
provided to your user.
10.2.2.3 Configuring the LongLivedStatements

Copy the LongLivedStatement.txt file from the computer on which the
OpenScape Frontend services are installed into the /usr/tomcat7/conf
directory on the Google Apps computer.
10.2.2.4 Configuring the Google Apps Computer

You need to edit the /usr/tomcat7/conf/fusion-webapp-config.dat
file for configuring the Google Apps computer.
You can edit fields indicated by (default). You need not edit any other fields.
Search the configuration file fusion-webapp-conf.dat for the parameters listed in
the table under Parameter Name and assign them the values you find in the
Parameter Value column.
574
A31003-S5070-J100-12-7631, 02/2013

Parameter Name
Parameter Value
Client
googleMailShowContactsMax
conferenceSourceId
GoogleApps
conferenceMustRecordName
false
conferenceLeaderActivation
true
WebAppUcServlet (Edit the following 5 parameters only if you use a Proxy server.
useProxy
false (default)
proxyHost
172.28.12.5 (default)
proxyPort
8080 (default)
nonProxyHosts
172.30.243.194|172.30.243.194:4709 (default)
BaseService
openScapeServer
<IP address or DNS name of the application computer>
openScapeServerPort
4709 (default)
openScapeServerProtocol
https (default)
useSslForBCom
true
openScapeFusionWebappAdminUser
<technical account>@system
openScapeFusionWebappAdminUserPassword
<password>
googleDomain
<google domain>
googleDomainToken1 on this.
<token>
userIdAndEmailIdentical
true
persistedUserInfoFileName
/opt/siemens/fusion-webapp/user-info.dat
UserInitServiceImpl
persistedUserListFileName
/opt/siemens/fusion-webapp/user-list.dat
1 You find the value of the parameter in your Google Apps domain. Please read section Google Domain Authentication Token
10.2.3 Google Domain Authentication Token

You find the Google authentication code in your Google Apps domain. Proceed
as follows:
1. Log on to your Google Apps domain with your administrator access.
2. Click on Advanced Tools in the menu bar of your Google Apps domain web
page.
3. Click on Manage OAuth domain key in the Authentication section.
4. Activate the check box next to Enable this consumer key.
5. Note down the entry to the right of OAuth consumer secret.
A31003-S5070-J100-12-7631, 02/2013
575

Upgrading OpenScape Fusion for Google Apps
6. Activate the check box next to Two-legged OAuth access control to allow
accessing all APIs.
7. Click on the Save Changes button to save the settings.
10.3 Upgrading OpenScape Fusion for Google Apps

OpenScape Fusion for Google Apps is exclusively upgraded on the Google Apps
computer.
10.3.1 Upgrade on the Application Computer

No further upgrades are required on the application computer.
10.3.2 Upgrade on the Google Apps Computer

To perform an upgrade on the Google Apps computer you need the software
packages fusion-webapp-<version>.zip and
GooglePresenceSyn_<version>.zip.
10.3.3 Upgrading the Google Apps Computer Application

You upgrade the Google Apps computer software via the fusion-webapp<version>.zip file. You can download this file from the Software Supply Server.
1. Go into the binary directory of Tomcat.
cd /usr/tomcat7/bin
2. Stop the Tomcat server.
./shutdown.sh
3. Wait until the Tomcat service has shut down. If required, stop the Tomcat
service manually.
cd /software
5. Unpack the fusion-webapp-<version>.zip file.
unzip fusion-webapp-<version>.zip
6. Modify the access privileges of the install_googleapss.sh file.
chmod 755 install_googleapps.sh
./install_googleapps.sh | tee /software/install.log
8. Switch to the binary directory of Tomcat again.
cd /usr/tomcat7/bin
9. Start the Tomcat server.
576
./startup.sh
A31003-S5070-J100-12-7631, 02/2013

10.3.3.1 Upgrading the Google Apps Presence Service

You find the files required for upgrading the Presence service in the ZIP file
GooglePresenceSync_<version>.zip. You can download this file from the
Software Supply Server.
1. Copy the file GooglePresenceSync_<version>.zip into the /software/
pres directory.
2. Unpack the file GooglePresenceSync_<version>.zip.
unzip GooglePresenceSync_<version>.zip
3. Switch to the /software/pres directory.
cd /software/pres
4. Modify the access privileges of the install.sh file.
chmod 755 install.sh
./install.sh GooglePresenceSync_<version>.zip | tee /

software/pres/install.log
A31003-S5070-J100-12-7631, 02/2013
577

578
A31003-S5070-J100-12-7631, 02/2013
IG_ConnectOcs.fm
Connecting the Microsoft Office Communication Server/Microsoft Lync Server
11 Connecting the Microsoft Office Communication

In the following we describe the connection to the Microsoft Office
Communication Server (OCS 2007 R2)/Microsoft Lync Server.
IMPORTANT: Connecting Microsoft Office Communications Server/Microsoft
Lync Server has been released only project specifically.
NOTE: If you want to align the presence status of users between the Microsoft
Office Communication Server/Microsoft Lync Server and the OpenScape UC
Application, the connection from the Microsoft Office Communication Server/
Microsoft Lync Server to the OpenScape UC Application is needed. See the
OpenScape UC Application Planning Guide for details.
For this connection, the following statuses are supported:
Online
Be right back
Busy
Do not disturb
Away
NOTE: Besides the listed default presence statuses, the OCS/Lync system also
features status Offline. However, no user can set this status in any OpenScape
client. Also, the OpenScape system cannot control the presence status of an
OpenScape user on the grounds of whether or not he/she is logged in at the
system with an OpenScape client. As soon as the Microsoft OCS/Lync connector
of OpenScape UC Application has connected to the Microsoft OCS/Lync system,
all OpenScape users in the OCS/Lync system are considered online.
IMPORTANT: When a Microsoft OCS/Lync client logs out of the server or

switches to the Auto-Away status, the status of the relevant OpenScape user
changes to Away and cannot be altered in the OpenScape client as long as the
Microsoft OCS/Lync client is in the described state.
A31003-S5070-J100-12-7631, 02/2013
579
IG_ConnectOcs.fm
Requirements
In OCS/Lync, user contacts are addressed like in any other external source.
There is no way to automatically synchronize OpenScape and OCS/Lync contact
lists. You cannot save contacts of an OpenScape user in OCS/Lync.
If OpenScape UC Application is used with Instant Messaging (IM), the clients will
show whether a user is available for a chat. The possible states are:
Available
Unavailable
Unknown
The IM status is determined on the server side and derived from the user status.
11.1 Requirements
IMPORTANT: Microsoft Office Communications Server 2007/Microsoft Lync
Server, Microsoft Office Communicator Web Access and Active Directory must be
installed. Please refer to the Microsoft documentation on this.
IMPORTANT: Microsoft Office Communications Server/Microsoft Lync Server

may only be connected if Openfire is not connected (see Chapter 12, Connecting
Instant Messaging). Consequently, the symphonia_openfire_base and
symphonia_openfire RPM packages must not have been installed (see steps
10 on page 267 and 10 on page 284).
Reason: The settings of a probably available Openfire connection would be
overwritten. This applies, for example, to the Deployment Mode field in the CMP.
To access this field, select in the CMP Operation & Maintenance > Root
Cluster <application node>, click on Presence Service to open the Edit Service
Configuration dialog. This applies also vice versa. If Openfire is connected, the
settings of a possibly available Microsoft Office Communications Server
connection are overwritten.
580
A31003-S5070-J100-12-7631, 02/2013
IG_ConnectOcs.fm
Requirements
Since the Very Large Deployment needs an Openfire server, it cannot be

connected to a Microsoft Office Communications Server/Microsoft Lync Server.
IMPORTANT: You can install Microsoft Office Communications Server 2007 R2/
Microsoft Lync Server on Windows Server 2008 R2 following the instructions of
the Microsoft Knowledge Database (see http://support.microsoft.com/kb/
982021).

All OpenScape users must be created as OCS/Lync users.
A31003-S5070-J100-12-7631, 02/2013
581
IG_ConnectOcs.fm
Installation
11.2 Installation
The installation is described in step 10 on page 267 or in step 10 on page 284 in
Chapter 5, Installing the OpenScape UC Application:
As soon as the OpenScape UC Application has been set up, you can also install
the Microsoft Communication Server retrospectively by executing this osc-setup
command.
11.3 Installing the UCMA Proxy Web Service
Presence Service
Virtual Directory
Service
OCS Integration
OpenScape
Connector Service
Instance Message
Service
Linux Server
The following image provides an overview of the components involved in the

connection to OCS/Lync:
SSL
UCMA Proxy
Computer System
UCMA SDK
SOAP
Windows Domain
UCMA Proxy
Web Service
Microsoft Office
Communications
Server
OCS Computer
System
The following is available:
582
There is an OSC integration connector service in addition to the common

services on the OpenScape application computer.
UCMA proxy web service, which accesses the Microsoft Office

Communications server/Microsoft Lync Server via the UCMA SDK. UCMA is
short for Unified Communications Managed API.
An installation of the Microsoft Office Communications Servers 2007 R2/

Microsoft Lync Server and the Active Directory. These are installed and
configured conforming to the customer's requirements. Please obtain details
from the Microsoft documentation.
A31003-S5070-J100-12-7631, 02/2013
IG_ConnectOcs.fm
Installing the UCMA Proxy Web Service
The UCMA proxy web service, which uses the Microsoft Internet Information
Server (IIS), must be installed on a separate Windows computer. The following
operating systems are supported:
Windows Server 2003 R2 Standard Edition x64
Windows Server 2008 SP2 Standard Edition 64-bit

We recommend this operating system.
Windows Server 2008 R2 Standard Edition

IMPORTANT: This operating system does not support synchronizing the
user presence status from the OCS/Lync to the OpenScape UC Application.
Since the setup on Windows Server 2003 R2 Standard Edition differs partly from
the installation on Windows Server 2008, the following description considers the
different cases.
11.3.1 Checking the Requirements

1. The UCMA proxy computer and the OCS/Lync computer must be in the same
Windows domain.
2. Verify on the domain controller computer that the domain user account that is
used for installing the UCMA proxy web service is at least member of the
RTCUniversalServerAdmins group.
a) Open Start > Administrative Tools > Active Directory Users and
Computers.
b) Open <Domain name> > Users.
c) Double-click on RTCUniversalServerAdmins.
d) Select the Members tab.
e) Check whether the domain user account that is used for installing the
UCMA proxy web service is member in list shown in this dialog or in a
higher group.
3. If you use Windows Server 2003, be sure to set up the following software
packages in the following sequence before you install the UCMA proxy web
service.
a) Launch Start > Control Panel > Add or Remove Programs > Add/
Remove Windows Components > Application Server.
b) In the Internet Information Services (IIS) Management window open
the Web Service Extension entry.
A31003-S5070-J100-12-7631, 02/2013
583
IG_ConnectOcs.fm
a) Select the ASP.NET v2.0.50727 entry.

b) Click on the Allow button.
c) In the Internet Information Services (IIS) Management window
rightclick the Application Pools entry.
a) Select Properties.
b) On the Recycling tab deactivate the Recycle worker processes (in
minutes) check box.
c) Click on the OK button.
4. If you use Windows Server 2008, be sure to set up the following software
packages in the given sequence before you install the UCMA proxy web
service.
a) Launch Start > Control Panel > Administrative Tools > Server
Manager.
b) In the right-hand section of the Server Manager window click on the Add
Roles link.
c) Select the Server Roles entry.
d) Activate the Web Server (IIS) check box.
e) Click on Add Required Features.
f)
Select the Web Server (IIS) > Role Services entry.
g) Activate the check box Web Server > Application Development >
ASP.NET.
h) Click on Add Required Role Services.
i)
Activate the check box Management Tools > IIS 6 Management

Compatibility.
j)
Click on Next.
k) Click on Install.
The roles are installed.
l)
Click on Close.
m) Open Start > Administrative Tools > Internet Information Services

(IIS) Manager.
The Internet Information (IIS) Manager window opens.
n) Open <Computer name>(<Domain name of user>) > Application
Pools.
o) Select one of the entries in the Application Pools section.
584
A31003-S5070-J100-12-7631, 02/2013
IG_ConnectOcs.fm
p) In the right-hand section of the Internet Information (IIS) Manager

window select the Recycling... entry.
q) In the Edit Application Pool Recycling Settings dialog, section Fixed
Intervals, you find the Regular time intervals (in minutes) check box.
Deactivate it.
r)
Click on Next.
s) Click on Finish.
t)
Close the Internet Information (IIS) Manager window.
5. Insert the Microsoft OCS/Lync DVD into the DVD drive:

6. Execute the following sub-step in order to install NET Framework 3.5 SP1:
IMPORTANT: For setting up .NET Framework 3.5 SP1 you need to upgrade
your operating system to Windows Server 2008 SP2.
a) Double-click the <CD drive>\Setup\amd64\dotnetfx35.exe file.
b) Activate the I have read and ACCEPT the terms of License Agreement
check box.
c) Click on Install.
d) Click on Exit.
7. Execute the following sub-step in order to install Microsoft SQL Native Client.
a) Double-click the <CD drive>\Setup\amd64\sqlncli_x64.msi file.
a) Click on Next.
b) Activate the I accept the terms of license agreement check box.
c) Click on Next.
d) Enter your name and the name of your organization.
e) Click on Next.
f)
Click on Next.
g) Click on Install.
h) Click on Finish.
8. Execute the following sub-step in order to install Microsoft Visual C++ 2008
Redistributable x 64.
A31003-S5070-J100-12-7631, 02/2013
585
IG_ConnectOcs.fm
a) Double-click the <CD drive>\Setup\amd64\vcredist_x64.exe

file.
b) Click on Next.
c) Activate the I have read and accept the terms of license agreement
check box.
d) Click on Next.
e) Click on Finish.
9. The Microsoft Lync Server 2010, Core Components installation requires that
Microsoft PowerShell 2.0 or higher is installed. Therefore, execute the
following sub-steps to check whether Windows PowerShell is installed, in
which version it is installed and download and install version 2.0, if necessary:
a) Open Start > Administrative Tools > Server Manager.
b) In the right-hand section of the Server Manager window select the Add
Features link.
c) Activate the Windows PowerShell check box, if possible.
d) Click Next.
e) Click Install.
f)
Click Close.
g) Start > All programs > Windows PowerShell 1.0 > Windows
PowerShell.
h) Enter $Host.Version.
Example output:
Major
----1
Minor
----0
Build
----0
Revision
-------0
You only can upgrade Windows PowerShell 1.0 to a higher version, if you
have Windows PowerShell 1.0 RTM. If you have Windows PowerShell
1.0 CTP, Beta, RC etc., you must uninstall it before you install Windows
PowerShell 2.0.
i)
To uninstall Windows PowerShell, open Start > Administrative Tools >

Server Manager.
j)
In the right-hand section of the Server Manager window select the

Remove Features link.
k) Deactivate the Windows PowerShell check box.

l)
Click Next.
m) Click Remove.
586
A31003-S5070-J100-12-7631, 02/2013
IG_ConnectOcs.fm
n) Click Close.
o) Reboot the computer to complete the removal of Windows PowerShell
1.0.
p) After the reboot click Close in the Server Manager window again.
q) Retrieve the Windows PowerShell 2.0 e. g. by downloading the Windows
Management Core Package (Windows6.0-KB968930-x64.msu) from
the following web page:
http://support.microsoft.com/?kbid=968930
The Windows Management Core Package not only contains Windows
PowerShell 2.0 but also Windows Remote Management 2.0 (WinRM).
r)
Double-click the MSU file in the Windows Explorer.
s) Click OK.
t)
After the installation, you are asked to restart the computer. Click Restart.
u) After the restart of the computer, open Start > All programs >
Accessories > Windows PowerShell > Windows PowerShell.
The Windows PowerShell window opens.
v) Enter $Host.Version.
Example output:
Major
----2
Minor
----0
Build
-----1
Revision
--------1
w) Close this window.

10. Execute the following sub-steps in order to install Microsoft Office
Communications Server 2007 R2/Microsoft Lync Server and Microsoft
Unified Communications Managed API 2.0 Core Redist 64-bit.
a) Double-click the <CD drive>\Setup\amd64\setup\ocscore.msi
file.
b) Click on Next.
c) Click on I accept the terms in the License Agreement.
d) Click on Next.
e) Click on Next.
f)
Click on Install.
A31003-S5070-J100-12-7631, 02/2013
587
IG_ConnectOcs.fm
g) Click on Finish.
IMPORTANT: If you installed and configured Microsoft Internet Information
Services after setting up the .NET Framework, you need to register ASP.NET in
a command line manually by executing the following command:
C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\
aspnet_regiis -i
The path may have to be adjusted to match the settings on your computer.
588
A31003-S5070-J100-12-7631, 02/2013
IG_ConnectOcs.fm
11.3.2 Installation
1. Mount the OptionalPackage ISO setup file of the OpenScape UC Application
(see Table 8 on page 235):
OpenScapeUcSuiteApps-OptionalPackage-<version number>.iso
Example:
OpenScapeUcSuiteApps-OptionalPackage-V7R1.0.0-130000.iso
2. Unpack the file contrib/
scs_osc_officecommunicator_ucmaproxy-<version>.zip in this
ISO setup file.
3. Start the UcmaProxyWS.msi file.
4. Click on Next.
5. Accept the license agreement by activating the I agree radio button and click
on Next.
6. Leave the defaults for the setup address unchanged and click on Next.
7. Click on Next to start the installation.
8. Click on Close to end the installation.
9. Check whether the setup has created the files in the following table:
Directory
File
Comment
C:\Inetpub\wwwroot\UcmaProxyWS
Uccproxy.asmx
Definition file of the web service
Web.config
Configuration file of the web service
C:\Inetpub\wwwroot\UcmaProxyWS\bin ApplicationProvisioning.dll
Library for accessing the Active Directory
log4net.dll
Library for logging
Microsoft.Rtc.Collaboration.dll
Microsoft library
Microsoft.Rtc.Internal.Media.dll
Microsoft library
sipeps.dll
Microsoft library
UccProxyWS.dll
OpenScape proxy web service
C:\Program Files(x86)\UcmaProxyTools ApplicationProvisioning.dll
Library for accessing the Active Directory
License_Terms_OpenScape_UcmaPro UCMA proxy license file

xy_V1_d-e.rtf
Table 114
Installed Files of the UCMA Proxy Web Service
10. Check the UCMA proxy web service function by entering the following
address in a web browser on the UCMA proxy computer:
http://localhost/UcmaProxyWS/UccProxy.asmx
A31003-S5070-J100-12-7631, 02/2013
589
IG_ConnectOcs.fm
11. The browser should deliver the following output:
12. Check whether the same output is displayed when you start the web browser
on a different computer and enter the following address:
http://<Proxy>/UcmaProxyWS/UccProxy.asmx
Replace <Proxy> with the computer name, the fully qualified domain name
(FQDN) or the IP address of the UCMA proxy computer.
11.3.3 Uninstallation
Uninstall the UCMA proxy web service as follows:
1. Open a command line and switch to the following directory:
C:\Program Files\(x86)\UcmaProxyTools
2. Execute the following command to remove the trust relationship:
MakeTSE.exe -remove
3. If you use Windows Server 2003, launch Start > Control Panel > Add or
Remove Programs.
590
A31003-S5070-J100-12-7631, 02/2013
IG_ConnectOcs.fm
a) Select the UcmaProxyWebService entry.

b) Click on the Remove button and follow the instructions.
4. If you use Windows Server 2008, launch Start > Control Panel > Programs
and Features.
a) Select the UcmaProxyWebService entry.
b) Click on the Uninstall button and follow the instructions.
A31003-S5070-J100-12-7631, 02/2013
591
IG_ConnectOcs.fm
User Management
11.4 User Management

The OpenScape UC Application provides a directory service for clients to receive
contact information in external directories. It is used to grant access to global
directories.
The same service is used to grant access to the private contacts of the respective
user that are stored on the Microsoft Office Communications Server/Microsoft
Lync Server side. The required configuration of virtual directory connectors on the
server side has been completely performed with the OpenScape UC Application
installation. Additional configurations are required in the OpenScape Web Client
and OpenScape Desktop Client Enterprise Web Embedded Edition.
Execute the configuration steps for connecting the Microsoft Office
Communications Server/Microsoft Lync Server in the Administrator
Documentation OpenScape UC Application Configuration and Administration.
All OpenScape users must be created as OCS/Lync users.
Create in the Active Directory a user as OCS/Lync user named openscape, for
example. A user becomes an OCS/Lync user when you, among other things,
activate the Enable user for Office Communications Server check box in the
user properties dialog. A user also named openscape must be created on the
OpenScape UC Application side. Enter this user name in the OCS Dummy User
Account field (refer to the OCS/Lync connection configuration chapter in the
Administrator Documentation OpenScape UC Application Configuration and
Administration). This user is internally deployed by the OpenScape UC
Application services.
592
A31003-S5070-J100-12-7631, 02/2013
IG_ConnectOcs.fm
Installation and Configuration of the OpenScape Clients
11.5 Installation and Configuration of the OpenScape Clients

OpenScape Desktop Client Enterprise Web Embedded Edition and OpenScape
Web Client need to log on with the user account and password of the OpenScape
UC Application.
Ensure for OpenScape UC Application web clients that in the file
<SYMPHONIA_HOME>/HiPathCA/config/services/default/AddressService/dbserver/SYMCS.cfg
the entry
DBEnv.ConnectorIds = svc-contactlist, svc-globalcontactlist
is modified as follows:
DBEnv.ConnectorIds = svc-contactlist, svc-globalcontactlist,
svc-virtualdirectoryconnectorocs
The outlines used to present these items in the web client UI are defined as:
DBEnv.DisplayName.svc-virtualdirectoryconnectorocs = EN:OCS Contacts; DE:OCS-Kontakte
A31003-S5070-J100-12-7631, 02/2013
593
IG_ConnectOcs.fm
Installation and Configuration of the OpenScape Clients
594
A31003-S5070-J100-12-7631, 02/2013
IG_ConnectInstantMessaging.fm
Connecting Instant Messaging
Introduction
12 Connecting Instant Messaging

12.1 Introduction
OpenScape UC Application supports Openfire, an XMPP-conformable instantmessaging server. This server enables OpenScape UC Application users to
directly communicate with one or several users via the instant-messaging
method. Thus, the user can choose between the communication forms voice, email and instant messaging to communicate with his/her contacts. The
OpenScape Desktop Client Enterprise Web Embedded Edition and the
OpenScape Web Client show the instant messaging presence states of the
contacts.
NOTE: Openfire may only be connected if Microsoft Office Communications
Server/Microsoft Lync Server is not and vice versa. This means that the RPM
package scs_osc_officecommunicator_be must not have been installed (see
step 10 on page 267 and 10 on page 284).
NOTE: For Very Large Deployment, an Openfire server is mandatory in a data

center. For cluster and data center details see the OpenScape UC Application
Planning Guide.
A31003-S5070-J100-12-7631, 02/2013
595
Infrastructure
12.2 Infrastructure
The following applies for the Openfire server:
The Openfire server software is in the OptionalPackage ISO file (see Table 8
on page 235) of the OpenScape UC Application.
Computer for the setup
Integrated deployment
The Openfire server must be installed on a separate computer.
NOTE: We do not describe the setup of the deployment scenario
Integrated Deployment here (see also Section 2.1, Deployment
Small Deployment and Large Deployment

If you use the Small Deployment or Large Deployment, the connection to
an Openfire server is optional.
You can install the Openfire server either on the application computer
(see Section 2.1, Deployment Scenarios, on page 25) or on a separate
computer, the instant-messaging server computer. If specific conditions,
described in the OpenScape UC Application Planning Guide, are met, we
strongly recommend setting up the Openfire server on a separate
computer.
IMPORTANT: If you install the Openfire server on the application
computer, ensure that the OpenScape UC Application already is installed.
NOTE: If you use Virtual Appliance for Small Deployment, you are not
obliged to installed the Openfire server. You can install it either on the
application computer or on the instant-messaging computer. To do so,
execute the installation instructions in this chapter.
NOTE: If you use Virtual Appliance for Large Deployment, the Openfire
server must be installed but you are not obliged to use it. It must be
installed on the instant-messaging server computer. To do so, do not
execute the installation instructions in this chapter but the instructions in
Section 3.1.11, Using Virtual Appliance for Large Deployment, on page
84. In this case the Openfire server must not be installed on the application computer.
596
A31003-S5070-J100-12-7631, 02/2013
Infrastructure
In case of an installation on the application computer, this computer does

not need any additional hardware (RAM, hard disk etc.) despite the
Openfire server.

The Openfire server is mandatory but must not be set up on the
application computer. You need to install it on a separate computer, the
instant-messaging server computer.
Since the Very Large Deployment needs an Openfire server, it cannot be
connected to a Microsoft Office Communications Server/Microsoft Lync
Server.
An Openfire server connected to an OpenScape UC Application V4 R0 or

older always used to be set up on the instant-messaging server computer. If
you upgrade this OpenScape UC Application to V7, you cannot upgrade this
Openfire server. You need to uninstall the server and subsequently set it up
anew.
To start IM sessions and to send and receive instant messages, the OpenScape
clients contact the instant-messaging service which contacts Openfire via an
XMPP.connector.
IMPORTANT: If you install an OpenScape UC Application and wish to connect it
to an Openfire server that has not been installed according to a setup and
upgrade guide of the OpenScape UC Application and that was never connected
to an OpenScape UC Application, you need a project-specific release.
Such a project-specific release is required for an installation, but not for an update
or upgrade. An update or upgrade must be preceded by an installation for which
a project-specific release has already been granted. This section provides information about installing an Openfire server. You find information about updating
and upgrading in Section 12.9, Updating, Upgrading and Uninstalling, on page
617
IMPORTANT: An Openfire server set up according to an installation and upgrade

guide of the OpenScape UC Application can be connected to another, second
Openfire server that has not been set up according to an installation and upgrade
guide of the OpenScape UC Application and that has never been and will never
be connected to an OpenScape UC Application. Configuring the connection of
the second Openfire server to the first Openfire server is no part of this
A31003-S5070-J100-12-7631, 02/2013
597
Infrastructure
documentation. Please read the Openfire documentation by Jive Software

instead.
This has nothing to do with a project-specific release (see above).
NOTE: Verify that the required ports are open on the computer on which the
instant-messaging server is installed (see Table 50 on page 381, Table 69 on
page 406 and Table 89 on page 439).
598
A31003-S5070-J100-12-7631, 02/2013
Installing the Openfire Server on the Application Computer
12.3 Installing the Openfire Server on the Application Computer

IMPORTANT: Do not execute the steps in this section for Very Large
Deployment, because, if you do, the Openfire server must be mandatorily
installed on a separate computer. Instead, execute the steps in Section 12.4,
Installing the Openfire Server on the Instant-Messaging Server Computer, on
page 600.
1. Using the following command, check whether the Java runtime environment
is installed:
rpm -q symphonia-jre-ibm
If this RPM has not been installed, install it:
2. The installation of the Openfire server on the application computer is
accomplished as described in step 10 on page 267 or 10 on page 284 through
The package symphonia-openfire-base contains the Openfire server
software, the package symphonia-openfire contains the extensions of
the Siemens Enterprise Communications GmbH & Co. KG.
3. Start the Openfire server:
/etc/init.d/openfire start
When the computer boots, the Openfire server is started automatically.
If required, it can be stopped by using the following command:
/etc/init.d/openfire stop
A31003-S5070-J100-12-7631, 02/2013
599
Installing the Openfire Server on the Instant-Messaging Server Computer
12.4 Installing the Openfire Server on the Instant-Messaging Server

Computer
Section 5.3, Installation, on page 233 and, if required, install osc-setup.
2. If you install Very Large Deployment, you need to check whether the 32-bit
version of the Java runtime environment is set up:
rpm -qa | grep symphonia-jre-ibm
If this is the case, uninstall it:
rpm -e --nodeps symphonia-jre-ibm-<version>.rpm
3. The installation of the Openfire server is accomplished through the following
commands:
Small Deployment and Large Deployment

osc-setup in symphonia-openfire-base
osc-setup in symphonia-openfire

osc-setup in symphonia-jre-ibm-64bit
osc-setup in MySQL-client
osc-setup in MySQL-server
osc-setup in symphonia-openfire-base
osc-setup in symphonia-openfire
The commands osc-setup in MySQL-client and osc-setup in
MySQL-server install the MySQL client tools and the MySQL server.
The command osc-setup in symphonia-jre-... installs the Java

runtime environment.
The command osc-setup in symphonia-openfire-base installs the
Openfire server software and the command osc-setup in symphoniaopenfire installs the extensions of the Siemens Enterprise
Communications GmbH & Co. KG.
IMPORTANT: Make sure that the commands are executed in this exact
order.
4. Execute the following sub-steps.
a) Delete the provision of the repository.
Example output:
600
A31003-S5070-J100-12-7631, 02/2013
Installing the Openfire Server on the Instant-Messaging Server Computer
checking Arguments
Option clean: yes
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
b) Delete the directory of the temporary repository.
Example:
rm -R /tmp/tmpRepo
When the computer boots, the Openfire server is started automatically.
If required, it can be stopped by using the following command:
A31003-S5070-J100-12-7631, 02/2013
601
Initial Configuration of the Openfire Server
12.5 Initial Configuration of the Openfire Server

12.5.1 Initial Configuration for Integrated
Deployment, Small Deployment and Large
Deployment
Execute the following steps for Integrated Deployment, Small Deployment and
Large Deployment. In case of these deployment scenarios, the Solid DB is used.
1. Open the CMP login page in a browser.
https://<IP address of the application computer>
602
A31003-S5070-J100-12-7631, 02/2013
2. Log in.
A31003-S5070-J100-12-7631, 02/2013
603
3. Open Configuration > Unified Communications > Configuration >

Presence & IM Configuration.
NOTE: You find the fields shown in this dialog and further ones also in the
CMP: Click under Maintenance > Inventory > Nodes & Applications >
Nodes on the node name of the application computer ( offboard by default).
Then, next to Show service status, click on the Show button. Eventually,
click on the Presence XMPP Integration - Connector and ConnectionManager entry.
4. Enter in the XMPP Server IP Address field the IP address of the computer
on which the Openfire server has been installed.
NOTE: This can be the application computer or another computer without
any OpenScape components (see Section 12.2, Infrastructure, on page
596).
604
A31003-S5070-J100-12-7631, 02/2013
5. If the port for the administrator access is different from the default value 9091,
enter the corresponding value in the Admin Port field. Port 9090 for HTTP
(unsecured) and Port 9091 for HTTPS (secured) are the default ports.
IMPORTANT: Make sure that this port is open in the firewalls between the
computer on which the Openfire server has been installed and the computers
from which the Openfire server is accessed per admin access (compare
Section 6.1, Lists of the Ports to be opened, on page 359).
6. Click the Test button to test whether the Openfire server can be reached via
the port configured.
7. If the test is completed successfully, a check mark is displayed and the Start
Openfire Preconfiguration button is active. Otherwise, an error message
appears.
8. In the XMPP Domain Name field, enter the name of the XMPP domain.
IMPORTANT: Once the initial configuration is complete, a value entered in
this field cannot be changed anymore.
9. Select value Embedded-DB in the Openfire Database deployment field.
10. Click the Start Openfire Preconfiguration button to complete the default
configuration. This is indicated through a corresponding message. The
Openfire server is restarted with the new configuration values.
A31003-S5070-J100-12-7631, 02/2013
605
IMPORTANT: If you wish to enable the Start Openfire Preconfiguration

button at a later date, be sure to open the /opt/openfire/conf/
openfire.xml file beforehand and set the value of the <setup> tag to
false. Only then the Start Openfire Preconfiguration button will become
active.
11. Click on the Close button.
12. Click on the Save button.
13. The administrator documentation OpenScape UC Application Configuration
and Administration contains detailed information about the Openfire server
configuration.
606
A31003-S5070-J100-12-7631, 02/2013
12.5.2 Initial Configuration for Very Large

Deployment
Execute the following steps for Very Large Deployment. In case of this
deployment scenario, the MySQL database is used instead of the Solid DB. You
must not install the Openfire server on the application computer. The Openfire
server and the MySQL database are installed on the same computer: the instantmessaging server computer.
12.5.2.1 Requirements
1. Verify that the OpenScape UC Application and the Openfire server know each
other's IP address or the fully qualified domain name (FQDN). You can do this
by one of the following sub-steps:
a) The application computer and instant-messaging computer must have
the same DNS server (see the entry in YaST under Network Devices >
Network Settings > Hostname/DNS > Name Servers and Domain
Search List).
b) The IP address and the fully qualified domain name (FQDN) of the
instant-messaging server computer must have been entered in the /
etc/hosts file on the application computer.
The IP address and the fully qualified domain name (FQDN) of the
application computer must have been entered in the /etc/hosts file on
the instant-messaging server computer.
2. Check whether the MySQL packages have been installed:
rpm -qa | grep MySQL
Alternatively:
zypper se --match-any MySQL
A31003-S5070-J100-12-7631, 02/2013
607
12.5.2.2 Preparing the MySQL Database for Use with Openfire

1. Make sure that the Openfire server is running:
/etc/init.d/openfire status
Output:
openfire is running
2. Start the MySQL server:
/etc/init.d/mysql start
3. Set the MySQL password for user root:
mysqladmin -u root password <MySQL root password>
4. Connect to the MySQL server as user root and deploy the password just
defined:
mysql -u root -p<MySQL root password>
5. The prompt in your command line changes to mysql> because you are now
in MySQL mode.
6. Create the Openfire database on the MySQL server:
CREATE DATABASE <MySQL Openfire DB>;
Example:
CREATE DATABASE openfire_db;
7. Create a MySQL user who may access this database according to the
following pattern:
GRANT ALL ON <MySQL-Openfire-DB>.* TO <MySQL Openfire user>@<IP address> IDENTIFIED
BY <MySQL Openfire password>;
The command GRANT creates and configures the MySQL Openfire user.
<MySQL Openfire DB> is the name of the just created MySQL

database.
<MySQL Openfire user> is a MySQL user name.
<IP address> is the IP address of the computer on which the MySQL

server operates.
<MySQL Openfire password> is the password of this user.

The password may comprise 1 to 25 characters. The following characters
are permitted:
1234567890qwertyuiopasdfghjklzxcvbnmQWERTYUIOPASDFGHJKLZXC
VBNM!@#$%^*.
Example:
608
A31003-S5070-J100-12-7631, 02/2013
GRANT ALL ON openfire_db.* TO ofuser@10.1.42.207 IDENTIFIED BY ofpass;

8. Leave the mySQL mode:
exit
The mysql> prompt is no longer displayed.
9. Open the /etc/hosts file in an editor:
Example:
vi /etc/hosts
10. Enter the IP address, the fully qualified name (FQDN) and the XMPP domain
name of the computer on which the MySQL server is installed (instantmessaging server computer) in a new line.
Example:
10.1.42.207 docof02ofs.site docof02ofs openfire1
IMPORTANT: The XMPP domain name is also used elsewhere in this
manual (see step 7 on page 612) and cannot be changed there after it has
been saved.
A31003-S5070-J100-12-7631, 02/2013
609
12.5.2.3 Initial Configuration

1. Open the CMP login page in a browser.
2. Log in.
610
A31003-S5070-J100-12-7631, 02/2013
3. Open Configuration > Unified Communications > Configuration >

Presence & IM Configuration.
NOTE: You find the fields shown in this dialog and further ones also in the
CMP: Click under Maintenance > Inventory > Nodes & Applications >
Nodes on the node name of the application computer (offboard by default).
Then, next to Show service status, click on the Show button. Eventually,
click on the Presence XMPP Integration - Connector and ConnectionManager entry.
4. Enter in the XMPP Server IP Address field the IP address of the computer
on which the Openfire server has been installed. You specified this IP address
in step 10 on page 609 also.
5. If the port for the administrator access is different from the default value 9091,
enter the corresponding value in the Admin Port field. Port 9090 for HTTP
(unsecured) and Port 9091 for HTTPS (secured) are the default ports.
IMPORTANT: Make sure that this port is open in the firewalls between the
computer on which the Openfire server has been installed and the computers
from which the Openfire server is accessed per admin access (compare
A31003-S5070-J100-12-7631, 02/2013
611
Section 6.1, Lists of the Ports to be opened, on page 359).

6. Click the Test button to test whether the Openfire server can be reached via
the port configured.
If the test is completed successfully, a check mark is displayed and the Start
Openfire Preconfiguration button is active. Otherwise, an error message
appears.
NOTE: In a network environment with several OpenScape UC Application
systems connected to the same Openfire server, the pre-configuration script
may have already been previously executed by another OpenScape UC
Application system. In this case the Start Openfire Preconfiguration button
appears inactive and you need not enable this button again. Click on Save
and continue with step Section 12.6, Configuring the Openfire Server, on
page 615.
7. Enter the name of the XMPP domain you also specified in step 10 on page
609 in the XMPP Domain Name field.
IMPORTANT: Once the initial configuration is complete, a value entered in
this field cannot be changed anymore.
8. Select value MySQL in the Openfire Database deployment field.
612
A31003-S5070-J100-12-7631, 02/2013
9. Enter the IP address or the fully qualified name (FQDN) of the computer on
which the MySQL server is installed in the MySQL Host field. The IP address
is the value you entered in step 7 on page 608 for the <IP address>
wildcard.
Because the MySQL and Openfire server are installed on the same computer,
the IP address in the MySQL Host field is identical with the IP address in the
XMPP Server IP Address field.
10. Enter the database name you specified in step 6 on page 608 for the <MySQL
Openfire DB> wildcard in the MySQL database name field.
11. Enter the MySQL user you specified in step 7 on page 608 for the <MySQL
Openfire user> wildcard in the MySQL User field.
12. Enter the MySQL user password you specified in step 7 on page 608 for the
<MySQL Openfire password> wildcard in the MySQL Password field.
13. Click the Start Openfire Preconfiguration button to complete the default
configuration. This is indicated through a corresponding message. The
Openfire server is restarted with the new configuration values.
IMPORTANT: If you wish to enable the Start Openfire Preconfiguration

button at a later date, be sure to open the /opt/openfire/conf/
openfire.xml file beforehand and set the value of the <setup> tag to
false. Only then the Start Openfire Preconfiguration button will become
active.
A31003-S5070-J100-12-7631, 02/2013
613

In case the Openfire server is restarting right now due to the configuration
done in the previous steps you may receive an error message indicating that
the XMPP server IP address cannot be reached. In this case wait 30
secondes and repeat this step.
614
A31003-S5070-J100-12-7631, 02/2013
Configuring the Openfire Server
12.6 Configuring the Openfire Server

1. Increase the number of allowed sockets in the /etc/security/
limits.conf file by specifying the maximum number of logged-in Openfire
users through adding the following lines:
*
soft
nofile
20000
hard
nofile
20000
NOTE: To change this file, root privileges are required.

3. In the CMP, open Configuration > Unified Communications >
Configuration > Presence & IM Configuration.
4. Click on the Start Openfire Admin UI button.

NOTE: This button is only active after the preconfiguration (see above).
The administration GUI for Openfire opens in a new window. Please follow
the instructions in the administrator documentation OpenScape UC
Application Configuration and Administration.
A31003-S5070-J100-12-7631, 02/2013
615
User Data Import
5. Please note the ports in the firewall to be opened on the application computer
and on the instant-messaging server computer (if any) (see Section 6.1, Lists
of the Ports to be opened, on page 359).
12.7 User Data Import

You need not execute any steps manually here. This occurs automatically now.
12.8 Configuring the OpenScape Clients

12.8.1 Configuring the OpenScape Desktop Client
Enterprise Web Embedded Edition
XMPP is only supported by the OpenScape Desktop Client Enterprise Web
Embedded Edition, but not by the Personal Edition.
You need not execute any steps for the OpenScape Desktop Client Enterprise
Web Embedded Edition manually anymore. This occurs automatically now.
12.8.2 Configuring the OpenScape Web Client

You need not execute any steps for the OpenScape Web Client manually
anymore. This occurs automatically now.
12.8.3 Configuring the OpenScape Mobile Client

Instant messaging is not supported for the OpenScape Mobile Client.
616
A31003-S5070-J100-12-7631, 02/2013
Updating, Upgrading and Uninstalling
12.9 Updating, Upgrading and Uninstalling

12.9.1 Update
12.9.1.1 Updating the Openfire Server on the Application
Computer
If the Openfire server has been installed on the application computer (see Section
12.2, Infrastructure, on page 596), updating is part of the OpenScape UC
Application update. Steps that go beyond the instructions in Chapter 15,
Updating, Upgrading and Migrating are not required.
12.9.1.2 Updating the Openfire Server on the InstantMessaging Server Computer

NOTE: The instructions in this section apply for all deployment scenarios that
support an Openfire server on an instant-messaging server computer.
Updating to a new fix release

NOTE: This section describes the update to a fix release on the instantmessaging server computer using commands in a command line. Updating to a
fix release on the instant-messaging computer using the CMP (see Section
15.3.3, Updating using the CMP (UI Patching) instead of osc-setup, on page
733) is not supported.
Execute the following steps on the instant-messaging server computer:
1. Log on with user name root.
Section 5.3, Installation, on page 233 and, if required, install or update oscsetup.
3. Stop the Openfire server:
4. Check the Openfire server status:
Output:
openfire is not running
A31003-S5070-J100-12-7631, 02/2013
617
5. Update the Openfire server:

osc-setup up
6. Execute the following sub-steps.
Example output:
checking Arguments
Option clean: yes
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Example:
rm -R /tmp/tmpRepo
618
A31003-S5070-J100-12-7631, 02/2013

Output:
openfire is running
A31003-S5070-J100-12-7631, 02/2013
619
Updating to a new hotfix

NOTE: This section describes how to install a hotfix on the instant-messaging
server computer with the help of commands in a command line. Installing a hotfix
on the instant-messaging computer using the CMP (see Section 15.3.3,
Updating using the CMP (UI Patching) instead of osc-setup, on page 733) is not
supported.
A hotfix is provided to you as ISO file. It is always a single hotfix ISO file.
Example:
OpenScapeUcSuiteApps_PATCH-V7R1.0.0-130001.iso
The hotfix ISO file is already a YUM repository. It need not be combined to a
repository with other ISO files by means of osc-setup cr ....
Execute the following steps on the instant-messaging computer:
IMPORTANT: Check whether the Release Notes contain a procedure that differs
from the steps outlined here.
2. Stop the Openfire server:
Output:
openfire is not running
4. If the ISO file is present on a DVD and not on the computer, mount the DVD:
mount /dev/cdrom /media
5. If the ISO file is available on a USB stick and not on the computer, proceed
as follows:
SLES 11. All ISO files of the OpenScape UC Application are smaller than
4 GB and can thus be processed by FAT32.
ls /dev/sd*
Example output:
620
A31003-S5070-J100-12-7631, 02/2013

ls /dev/sd*
Example output:
mkdir /media
6. Provide the hotfix:
Sample:
osc-setup ar iso:/?iso=<path>/OpenScapeUcSuiteApps_PATCH-<version>.iso
Example of an ISO file on a USB stick:
osc-setup ar iso:/?iso=/media/OpenScapeUcSuiteApps_PATCH-V7R1.0.0-130001.iso
Example of an ISO file on the computer:
osc-setup ar iso:/?iso=/tmp/shi/oscuca7d8/OpenScapeUcSuiteApps_PATCH-V7R1.0.0-130001.iso
7. Update osc-setup:
osc-setup up osc-setup
8. Install the hotfix:
osc-setup up
9. Delete the repository from the osc-setup:
osc-setup rr <number>
<number> is the number of the entry you wish to delete.
10. Unmount the USB stick:
umount /media
11. After installing the hotfix, start the Openfire server:
A31003-S5070-J100-12-7631, 02/2013
621
Output:
openfire is running
12.9.2 Upgrade
Upgrade from V3 R2 to V7
An Openfire server connected to an OpenScape UC Application V4 R0 or older
always used to be set up on the instant-messaging server computer. If you
upgrade an OpenScape UC Application V3 R2 or older to V7, you cannot
upgrade this Openfire server. You need to uninstall the server and subsequently
set it up anew.
Execute the instructions in Section 12.5, Initial Configuration of the Openfire
Server, on page 602 after you have performed the uninstallation and new
installation on the instant-messaging computer.
You cannot upgrade the Openfire server from V4 R0 to V7 because upgrading
from V4 R0 to V7 of the OpenScape UC Application directly has not been
released (see Section 15.4, Upgrade and Migration Tables, on page 745, for
example footer 5 in Table 119 on page 745:Upgrading OpenScape UC Application
V4 R0 to V7 directly is not supported. First upgrade to V6 R0 (see installation and
upgrade instructions for OpenScape UC Application V6 R0). Then upgrade from
V6 R0 to V7. Then migrate from Small Deployment to Large Deployment.).
When upgrading to V7 please heed the instructions in step 41 on page 769 or
12.9.3 Uninstallation
Uninstalling the Openfire server, like uninstalling the OpenScape UC Application
V7, is not supported (see Chapter 16, Uninstallation).
622
A31003-S5070-J100-12-7631, 02/2013
IG_ConnectGroupware.fm
Groupware Connection
General Considerations
13 Groupware Connection
13.1 General Considerations
IMPORTANT: OpenScape UC Application can only be connected to one
groupware at the same time. This may be either IBM Lotus Domino or Microsoft
Exchange.
IMPORTANT: Setting up the Domino Connector server is not supported for Very
Large Deployment. Consequently, Section 13.3, Connecting IBM Lotus
Domino, on page 624 does not apply for Very Large Deployment.

When installing the OpenScape UC Application according to Chapter 5,

Installing the OpenScape UC Application, the following RPM packages are
always installed automatically.
scs_gwbeshared
scs_groupware
NOTE: The RPM package scs_groupware of OpenScape UC Application V7
does not contain the same components as the RPM package
scs_groupware of the OpenScape UC Application V4 R0 or earlier.
scs_groupwareportlet
scs_gwbeexch
A31003-S5070-J100-12-7631, 02/2013
623
Connecting Microsoft Exchange
The first three packages are used for every kind of groupware connection. The
fourth package is only used for the connection to Microsoft Exchange.
IMPORTANT: An uninstallation of one of these packages or all of these
packages has not been released.
13.2 Connecting Microsoft Exchange

You find information about connecting the Microsoft Exchange Server in the
Administration.
13.3 Connecting IBM Lotus Domino

IMPORTANT: Setting up the Domino Connector server is not supported for Very
Large Deployment. Consequently, Section 13.3, Connecting IBM Lotus
Domino, on page 624 does not apply for Very Large Deployment.
The connector component (provider) of the OpenScape UC Application does not
directly access the user data of the productive Lotus Domino server 7.0.x or 8.0.x
(Domino groupware server). Instead, it accesses the Notes API of a Lotus
Domino server (Domino Connector server) which must be installed on the
application computer. This Domino Connector server is connected to the Domino
Groupware server.
IMPORTANT: The Domino Connector server only needs to be installed if the
OpenScape UC Application is to be connected to Lotus Domino.
The Domino Connector server is installed, configured, then started and shut
down once, but will not be started again.
13.3.1 Preparations
13.3.1.1 Installing the OpenScape UC Application
Install and configure the OpenScape UC Application V7 according to Section ,
General Preparations, on page 25 to Section , Configuring the OpenScape UC
Application, on page 359.
624
A31003-S5070-J100-12-7631, 02/2013
Connecting IBM Lotus Domino
This will also install the packages mentioned in Section 13.1, General
Considerations, on page 623 and the packages concerning the groupware.
A31003-S5070-J100-12-7631, 02/2013
625
13.3.1.2 Creating the Notes User

NOTE: The operation of YaST is described in Section B.1, General Operation
of YaST, on page 1044.
To install the connector server you need a Linux user and a Linux group that you
create by the following steps:
1. Enter the yast command in a console.
2. Use the key to navigate to the Security and Users entry.

3. Push the key.
4. Use the key to navigate to the User Management entry.
626
A31003-S5070-J100-12-7631, 02/2013
5. Push the return key.
6. Enter the ALT + A key combination.
A31003-S5070-J100-12-7631, 02/2013
627
7. In the fields Users Full Name and Username, enter the value notes. To
navigate between the fields, use the TAB key.
8. In the fields Password and Confirm Password, enter the same password.
628
A31003-S5070-J100-12-7631, 02/2013
13.3.1.3 Creating the Notes Group

10. Enter the ALT + G key combination.
A31003-S5070-J100-12-7631, 02/2013
629
12. In the Group Name field, enter the value notes.

13. In the fields Password and Confirm Password, enter the same password.
14. Push the TAB key. The Group Members field is selected.
15. Push the key several times until the notes check box is selected.
630
A31003-S5070-J100-12-7631, 02/2013
The user notes is assigned to the group notes.
A31003-S5070-J100-12-7631, 02/2013
631
18. Enter the ALT + F key combination.

19. Enter the ALT + Q key combination.
632
A31003-S5070-J100-12-7631, 02/2013
13.3.2 Installing the Domino Connector Server

How to install the Domino connector server:
1. Open a command line on the application computer as root.
2. Create access to the installation source (OptionalPackage ISO file (see Table
8 on page 235) of the OpenScape UC Application).
3. Start the installation by executing the file ./linux/domino/install of the
unpacked archive.
4. Push the TAB key.
5. Push the TAB key once after each of the next two console outputs.
The following question appears.
Do you agree to the terms of the license agreement? [Yes]
Do you agree to install data directories only? [No]
The following output appears.
Select Setup type: [Domino Enterprise Server]
Do you agree to install all template files for this Domino
Server? [Yes]
Do you agree to configure this server with ASP? [No]
Current program directory setting: /opt/ibm/lotus
Do you want to run more than one server based on this
installation? [No]
A31003-S5070-J100-12-7631, 02/2013
633
Current data directory setting: /local/notesdata

Current UNIX user setting: notes
NOTE: If you do not have configured the Linux user under the name notes
(see Section 13.3.1, Preparations, on page 624), push the return key. Then
enter the name you used in the administrator documentation OpenScape UC
Application Configuration and Administration in the Creating User and Group
section.
Current UNIX group setting: notes
NOTE: If you do not have configured the Linux user under the name notes
(see Section 13.3.1, Preparations, on page 624), push the return key. Then
enter the name you used in the administrator documentation OpenScape UC
Application Configuration and Administration in the Creating User and Group
section.
Select server setup method: [Manual Server Setup]
The settings you have made are displayed and can be checked.
19. If all settings are correct, push the TAB key.
The installation starts. The progress of the setup procedure is displayed with
a progress bar.
634
A31003-S5070-J100-12-7631, 02/2013
20. To execute this step, please follow the instructions in the administrator
documentation OpenScape UC Application Configuration and Administration:
a) Configure the Domino Connector server.
The values you enter in the configuration may be dummy values. They
are only required for the unique start of the Domino Connector server in
the next substep. They are not required for the later connection to the
Domino Groupware server.
b) Start the Domino Connector server.
c) Stop the Domino Connector server.
13.3.2.1 Connection to the Domino Groupware Server

1. Make sure that the Domino Groupware server has been installed and is
running.
2. Make sure that the ports listed in the following tables on the Lotus Domino
server and the corresponding ports on the application computer are open:
Small Deployment: Table 68 on page 405
Large Deployment: Table 88 on page 438
Very Large Deployment: Table 108 on page 471
3. Use the following command to install the connector component (provider) of

the OpenScape UC Application:
osc-setup in scs_gwbenotes
4. For the Small Deployment, execute the following command on the application
computer to start the MRCP service, the Nuance TTS and the Nuance ASR,
if available:
A31003-S5070-J100-12-7631, 02/2013
635
6. Perform the configuration of the connection according to the administrator

636
A31003-S5070-J100-12-7631, 02/2013
IG_AdditionalInstallation.fm
Additional Installation
Installing additional RPM Packages of the OpenScape UC Application
14 Additional Installation
14.1 Installing additional RPM Packages of the OpenScape UC Application
IMPORTANT: Providing an ISO file as repository retrospectively deletes the
provision of the current repository. Install all required RPMs (see the ensuing
sections) from the repository to be deleted before removing it.
Execute the instructions of one of the following sub-sections depending on how
you provide the ISO files:
Section 14.1.1, Local Retrospective Provision, on page 637
Section 14.1.2, Remote Retrospective Provision by using NFS, on page 638
Section 14.1.3, Remote Retrospective Provision by using HTTPS, on page

638
Then execute the appropriate installation steps you find in one of the following
sections:
14.1.1 Local Retrospective Provision

If osc-setup is installed, a repository has been provided and you wish to provide
another ISO file in osc-setup, you need to follow the instructions in Section
15.2.2.2, Creating a Repository in osc-setup by using local Update/Upgrade
Sources, on page 674 and, in doing so, replace step 20 on page 677 by
osc-setup ar <path to the ISO file>
Provision example of the ISO file for Portuguese and Brazilian:
osc-setup ar /tmp/shi/osuca7/OpenScapeUcSuiteApps-Portuguese-V7R1.0.0-130000.iso
A31003-S5070-J100-12-7631, 02/2013
637
Installing additional RPM Packages of the OpenScape UC Application

Adding repository '74ef3c865f55a72c64b599e6f08c8983' [......done]
Repository '74ef3c865f55a72c64b599e6f08c8983' successfully added
Enabled: Yes
Autorefresh: No
URI: iso:///?iso=/tmp/shi/osuca7/OpenScapeUcSuiteApps-Portuguese-V7R1.0.0-130000.iso
14.1.2 Remote Retrospective Provision by using NFS

another ISO file in osc-setup, you need to follow the instructions in Option 1:
Using NFS for accessing ISO files on page 683 and, in doing so, replace step 27
on page 695 by executing the following command:
osc-setup ar <path to the ISO file>
Provision example of the ISO file for Portuguese and Brazilian:
osc-setup ar /tmp/shi/osuca7/OpenScapeUcSuiteApps-Portuguese-V7R1.0.0-130000.iso
14.1.3 Remote Retrospective Provision by using

HTTPS
another ISO file in osc-setup, you need to follow the instructions in Option 2:
Using HTTP for accessing a persistent repository on page 697.
638
A31003-S5070-J100-12-7631, 02/2013
Installing additional Voice Portal Languages
14.2 Installing additional Voice Portal Languages

In the following you learn how to install missing languages after an OpenScape
UC Application setup.
1. The voice portal (product name: OpenScape UC Voice Portal) operates as
web application:
/opt/siemens/mediaserver/application_host/providers/tomcat/tomcat-home/webapps/voiceportal/
NOTE: See also step 14 on page 274 and step 12 on page 304 for installing
voice portal languages retrospectively.
2. You need to assign additional values to the keys ttsLanguages and
guessLanguages.
A new address binding need not be performed. You find detailed information
about address bindings in the administrator documentation OpenScape UC
ttsLanguages
Using the text-to-speech feature of OpenScape UC Application, users
can have texts read out. In this process the user can optimize the text
output quality by selecting the text-to-speech engine in the voice portal
TUI that is optimized for the language of the respective text.
ttsLanguages specifies for which languages text-to-speech engines
can be selected in the voice portal TUI.
ttsLanguages can only be configured for the voice portal user access
but not for the portal's guest access.
guessLanguages
Using the text-to-speech feature of OpenScape UC Application, users
can have texts read out. In this process the system can automatically
optimize the voice output by analyzing the message text sentence-wise
and using the text-to-speech engine for the recognized language.
guessLanguages defines as regards which languages the text-tospeech feature analyses message texts.
guessLanguages can only be configured for the voice portal user
access but not for the portal's guest access.
The keys ttsLanguages and guessLanguages can be configured in a file

(see from step 3 on page 639) as well as via the CMP (see from step 8 on
page 642).
3. Open the following file in an editor.
A31003-S5070-J100-12-7631, 02/2013
639
/opt/siemens/mediaserver/application_host/binders/terminal/bindings/voiceportal.xml
Example:
<?xml version="1.0" encoding="UTF-8"?>
<terminals>
<terminal appletURI="application:/VoicePortal#start" id="voice-portal-start">

<line address="regexp:sip:100@.*">
<property key="symLanguage">EN-US</property>
<property key="symDomain">system</property>
<property key="operator">0</property>
<property key="transferTimeout">30</property>
<property key="thirdPartyVMNumber">4711</property>
<property key="xprNumber">4712</property>
<property key="voicePortalNumber">+4924043411036</property>
<property key="xprTrustedTransferDomain">49</property>
<property key="xprTrustedTransferParam">p0v1p1v2p2v1p3v4p4v4p5v2p6v1</property>
<property key="ttsLanguages">en-US,de-DE,zh-CN</property>
<property key="guessLanguages">en-US,en-GB,de-DE,zh-CN</property>
<property key="useSubjectSuffix">no</property>
<property key="subjectSuffix">Example text for message subject line suffix to be replaced</
property>
</line>
</terminal>
<terminal appletURI="application:/VoicePortal#guest" id="voice-portal-guest">
<line address="regexp:sip:200@.*">
<property key="symLanguage">EN-US</property>
<property key="voicePortalNumber">+4924043411036</property>
<property key="useSubjectSuffix">no</property>
<property key="subjectSuffix">Example text for message subject line suffix to be replaced</
property>
</line>
</terminal>
</terminals>
All properties defined in a file can also be configured via the CMP.
4. Look for the property element, whose attribute key features value
ttsLanguages.
Example:
<property key="ttsLanguages">en-US,de-DE,zh-CN</property>
5. Add the language to be additionally installed to this element, for example:
640
de-DE for German (Germany),
en-GB for English (UK)
en-US for English (USA) or
A31003-S5070-J100-12-7631, 02/2013
zh-CN for Chinese (Mandarin).
You can obtain the complete list of possible values from Table 14 on page
277.
Multiple values are separated by commas.
Example: de-DE,en-GB,en-US,zh-CN
6. Look for the property element, whose attribute key features value
guessLanguages.
Example:
<property key="guessLanguages">en-US,de-DE,zh-CN</property>
7. Add the language to be additionally installed to this element, for example:
de-DE for German (Germany),
en-GB for English (UK),
en-US for English (USA),
es_ES for Spanish (Spain),
fr_FR for French (France),
it_IT for Italian (Italy),
pt_PT for Portuguese (Portugal),
pt_BR for Portuguese (Brazil) or
zh-CN for Chinese (Mandarin).
You can obtain the complete list of possible values from Table 14 on page
277.
Multiple values are separated by commas.
Example: de-DE,en-GB,en-US,zh-CN
A31003-S5070-J100-12-7631, 02/2013
641
8. You can configure the keys ttsLanguages and guessLanguages also in

the CMP. Open the following address in the browser:
https://<Hostname>/management
9. Log in.
642
A31003-S5070-J100-12-7631, 02/2013
10. Click on Configuration > Unified Communications > Configuration >

Media Server.
11. Click on the media server you want to add a language to.
A31003-S5070-J100-12-7631, 02/2013
643
12. Click on the Terminals tab.
13. If the Terminal column does not display value voice-portal-start, browse to
the next page.
644
A31003-S5070-J100-12-7631, 02/2013
14. Click on the entry voice-portal-start. This is the entry for the voice portal user
access. As mentioned above, the guessLanguages key cannot be
configured for the voice portal guest access (entry voice-portal-guest).
15. Click on the Optional Properties button.
A31003-S5070-J100-12-7631, 02/2013
645
16. Click on the small triangle to the right of the guessLanguages entry.
17. Select Edit....
18. Edit the Value field as described in step 7 on page 641.

23. In case of the deployment scenario Large Deployment, execute the steps 1
on page 639 to 22 on page 646 for all other media server computers also.
646
A31003-S5070-J100-12-7631, 02/2013
Installing additional Frontend Computers
14.3 Installing additional Frontend Computers

Execute the steps described in Section 5.3.3.3, Installation on the Frontend
Computer, on page 293 on every additional frontend computer.
IMPORTANT: Please consider the necessary requirements in the previous
sections, in particular in Response file for the frontend server, Section 5.3.1,
Providing the Installation Sources in an Installation Repository in osc-setup, on
page 234, creating the DAR file (see step 5 on page 292 or step 5 on page 325)
and Section 5.3.3.2, Requirements for Installing Additional Computers, on page
290.
Please be sure to use the template of the response file for a frontend computer
and not the one for the application computer or media server computer.
14.4 Installing additional Media Server Computers

Execute the steps described in Section 5.3.3.4, Installation on the Media Server
Computer, on page 297 on every additional media server computer.
Copy the directory
/opt/siemens/mediaserver/application_host/resources/waveRoot/voiceportalgreetings
of an already existing media server computer into the same path on the new
media server computer. This makes already created greetings available on the
new media server computer also.
IMPORTANT: Please consider the necessary requirements in the previous
sections, in particular in Response file for the media server computer, Section
5.3.1, Providing the Installation Sources in an Installation Repository in oscsetup, on page 234, creating the DAR file (see step 5 on page 292 or step 5 on
page 325) and Section 5.3.3.2, Requirements for Installing Additional
Computers, on page 290.
A31003-S5070-J100-12-7631, 02/2013
647
Installing additional Media Server Computers
Please be sure to use the template of the response file for a media server
computer and not the one for the application computer or frontend computer.
IMPORTANT: Consider the instructions in the administrator documentation

OpenScape UC Application Configuration and Administration concerning the
configuration of a media server, especially concerning the subject Media Server
Farm.
648
A31003-S5070-J100-12-7631, 02/2013
Additional Installation of the OpenStage Client
14.5 Additional Installation of the OpenStage Client

14.5.1 Preparations
1. Check in the CMP whether the OpenStage telephone was assigned to an
OpenScape UC Application user and has an ONS number and whether the
required licenses are available for this user.
Open Users Management > Administration > Users & Resources for this
purpose. Click on the user. Click on the Resources tab.
2. Make sure that communication between the OpenStage phones and the
application computer can be handled via port 7789. This port may not be
blocked by a firewall.
A31003-S5070-J100-12-7631, 02/2013
649
14.5.2 Small Deployment

An additional installation of the OpenStage Client must be performed on the
application computer and on the OpenStage phone.
1. You need the following RPM file:
CA2-OSIPP-STANDARD-<version>.rpm
directory of the BasePackage ISO file (see Table 8 on page 235) e. g. to the
/tmp directory of the computer and execute the following RPM command in
this directory.
2. Execute the following command on the application computer:
/etc/init.d/symphoniad stop WebClient
rpm -i CA2-OSIPP-STANDARD-<version>.rpm
/etc/init.d/symphoniad start WebClient
If you want to install the OpenStage Client for Integrated Deployment, use the
following commands instead:
/etc/init.d/symphoniad stop WebClient
rpm -i CA2-OSIPP-STANDARD-<version>.rpm --prefix=/enterprise
/etc/init.d/symphoniad start WebClient
3. Enter the following address in a browser:
650
A31003-S5070-J100-12-7631, 02/2013
4. Click the Administrator Pages tab.
5. Enter the password and click the Login button.
A31003-S5070-J100-12-7631, 02/2013
651
Main application
6. Click the Applications entry.
7. Click the XML Applications entry.
8. Click the Add application entry.
9. Specify the following values:

a) Display name: Enter an arbitrary name, e. g. OS UC Appl.. In step 11
on page 653, a tab with this name will be created on the OpenStage
phone.
b) Application Name: Enter exactly the following value:
openstage-client
652
A31003-S5070-J100-12-7631, 02/2013
Large Deployment and Very Large Deployment: Enter the IP address

of the load balancer computer.
d) HTTP Server port: Enter the value 7789.

e) Protocol: Keep the value http.
f)
Program name on server: Enter exactly the following value:

Click the Submit button.

10. Push the following key on the OpenStage phone to display the Applications
tab:
If required, push this key again to change from one tab to another.
11. In the OpenStage phone display, the OS UC Appl. entry is displayed on the
Applications tab.
Select this entry and push the OK key.
The OpenStage Client of the OpenScape UC Application is started. The
OS UC Appl. tab is created.
NOTE: The command osc-setup up includes updating the OpenStage Client

on the server side (see step 6 on page 711, step 6 on page 718 and step 17 on
page 720). Updating only the OpenStage Client is described in step 12 on page
715 or step 10 on page 719 and step 22 on page 721.
A31003-S5070-J100-12-7631, 02/2013
653
14.5.3 Large Deployment

If you use Large Deployment, the additional installation of the OpenStage Client
must be performed on the application computer, the frontend computer and the
OpenStage phone.
1. You need the following RPM files:
CA2-OSIPP-BACKEND-<version>.rpm
CA2-OSIPP-FRONTEND-<version>.rpm
directory of the BasePackage ISO file (see Table 8 on page 235) e. g. into the
/tmp directory of the application computer, copy the file CA2-OSIPPFRONTEND-<version>.rpm e. g. into the /tmp directory of the frontend
computers and execute the RPM commands in this directory in the following
steps.
Example of the full names of the RPM packages:
2. Execute the following commands on the application computer:
/etc/init.d/symphoniad stop WebClient_BE
/etc/init.d/symphoniad start WebClient_BE
3. Execute the following commands on each frontend computer:
654
A31003-S5070-J100-12-7631, 02/2013
4. Enter the following address in a browser:

5. Click the Administrator Pages tab.
6. Enter the password and click the Login button.
A31003-S5070-J100-12-7631, 02/2013
655
Main application
7. Click the Applications entry.
8. Click the XML Applications entry.
9. Click the Add application entry.
10. Specify the following values:

a) Display name: Enter an arbitrary name, e. g. OS UC Appl.. In step 11
on page 653, a tab with this name will be created on the OpenStage
phone.
b) Application Name: Enter exactly the following value:
openstage-client
656
A31003-S5070-J100-12-7631, 02/2013
Large Deployment and Very Large Deployment: Enter the IP address

of the load balancer computer.
d) HTTP Server port: Enter the value 7789.

e) Protocol: Keep the value http.
f)
Program name on server: Enter exactly the following value:

Click the Submit button.

11. Push the following key on the OpenStage phone to display the Applications
tab:
If required, push this key again to change from one tab to another.
12. In the OpenStage phone display, the OS UC Appl. entry is displayed on the
Applications tab.
Select this entry and push the OK key.
The OpenStage Client of the OpenScape UC Application is started. The
OS UC Appl. tab is created.
NOTE: The command osc-setup up includes updating the OpenStage Client

on the server side (see step 6 on page 711 and step 17 on page 720). Updating
only the OpenStage Client is described in step 12 on page 715 or step 10 on page
719 and step 22 on page 721.
A31003-S5070-J100-12-7631, 02/2013
657
658
A31003-S5070-J100-12-7631, 02/2013
IG_UpdateUpgradeMigration.fm
Updating, Upgrading and Migrating
15 Updating, Upgrading and Migrating

We differentiate updating, upgrading and migrating as follows:
Update
An update is set to be performed when a new fix release or hotfix has been
released to update an installed version of the OpenScape UC Application.
Example:
An OpenScape UC Application V7 was installed in version FR1 (Fix Release
1) and FR2 or FR2 HF1 is released for V7.
Changing from OpenScape UC Application V7 R0 to OpenScape UC
Application V7 R1 is an update too.
Upgrade
If, in contrast, an OpenScape UC Application V6 R0 has been installed and a
V7 setup medium is to be used for updating the OpenScape UC Application,
we actually talk about an upgrade.
IMPORTANT: You can upgrade the OpenScape UC Application on the application computer, the frontend computers, the media server computers etc. to
V7 R1 but leave the clients in their old version. However, software problems
that may result from differing versions are not patched, which restricts the
support that can be provided in this situation. Upgrading the clients is recommended in this case.
Migration
Migration has two meanings:
Migration is a change of the deployment scenario.
Migration from OpenScape ComAssistant to OpenScape UC Application,

see on page 965
A31003-S5070-J100-12-7631, 02/2013
659
IMPORTANT: SLES 11 SP0 is not supported. Possibly existing versions of SLES

that are younger than SLES 11 SP2 are not supported either.
IMPORTANT: SLES 11 SP1 and SP2 in 64-bit version are the operating system
for the
- application computer,
- media server computer,
- frontend computer.
SLES 11 SP2 is recommended.
On the application computer, frontend computer, media server computer and the
Mobile Client Facade server computer the same operating system versions must
be installed.
NOTE: Check if the system time of all OpenScape UC Application-related

IMPORTANT: Upgrading OpenScape UC Application V3 R2 Beta to OpenScape

UC Application V7 has not been released.
660
A31003-S5070-J100-12-7631, 02/2013
IMPORTANT: In the following deployment scenarios, NO OpenScape UC Application components are installed, updated or upgraded. Therefore, these
deployment scenarios are not described in this documentation. Please obtain the
necessary information from the OpenScape Voice Installation Guide (for example
OpenScape Voice, Installation and Upgrades, Installation Guide).
Mediaserver Standalone
Multiple Communication Server Admin (Standard Duplex Voice)

In this deployment scenario, OpenScape Voice Assistant, RG 8700 Assistant
and CLM are installed on one computer. No OpenScape backend services
are set up. The OpenScape Voice Duplex is on another computer. This
deployment scenario serves for managing several OpenScape Voice
systems. Only OpenScape Voice components are installed in this deployment
scenario.
NOTE: The Integrated Duplex deployment scenario is not supported by

OpenScape UC Application V7. First upgrade to V3 R2 Integrated Duplex and
migrate to V3 R2 Small Deployment (see Installation Guide OpenScape UC
Application Installation and Upgrade of V3 R2). Then upgrade to V7.
IMPORTANT: You can use the unchanged hardware of the source version for an
upgrade (see Section 15.1, Determining the Source Version, on page 662).
However, video conferencing is then not supported and the scaling limits (for
example the number of supported users etc.) apply.
A31003-S5070-J100-12-7631, 02/2013
661
Determining the Source Version
15.1 Determining the Source Version

You can follow three different paths for determining the installed version of
15.1.1 Determining the version in the CMP

Open Maintenance > Inventory > Nodes & Applications > Nodes.
Click on an entry of type Application or click on the computer named offboard.

NOTE: offboard is the default name of the application computer in the CMP.
Your application computer may be named differently.
A new window opens.
The Applications section displays the version of OpenScape UC Application in

the Software Version field.
662
A31003-S5070-J100-12-7631, 02/2013
Example: V7 R1.0.0
15.1.2 Determining the version using the

productInventory.sh script
Execute one of the following commands in a command line:
/opt/siemens/common/bin/productInventory.sh
-t
a list
a list | grep OpenScapeUC_ProductVersion
a list L
Example output:
OpenScapeUC_ProductVersion:
'OpenScape UC - ProductVersion' 'V7 R1.0.0'
15.1.3 Determining the version by means of the rpm

command
Execute the following command:
rpm -qi OpenScapeUC_ProductVersion
Example output:
Name
: OpenScapeUC_ProductVersion
Relocations: /opt/siemens
Version
: 7_1.0.0 Vendor: Siemens Enterprise Communications GmbH & Co KG, Munich,
Germany
Release
: 120000 Build Date: Wed Nov 21 18:58:46 2012
Install Date: Wed Nov 21 19:58:46 2012 Build Host: prodstore.alsdorf.cycos.com
Group
: Productivity/Networking/Telecommunication
Source RPM:
OpenScapeUC_ProductVersion-7_1.0.0-120000.src.rpm
Size
: 510945
License: Copyright (c) 2012 by Siemens
Enterprise Communications GmbH & Co KG, All Rights Reserved
Signature
: DSA/SHA1, Wed Nov 21 18:58:46 2012, Key ID 9751c8e3c9182aa7
Packager
: repocreator-0.9-b2
URL
: http://www.openscape.net
Summary
: OpenScape UC - ProductVersion
Description:
OpenScape Unified Communication - ProductVersion
Distribution: OpenScapeUC 4.1
Alternatively, you can use the following command:
rpm -qa | grep OpenScapeUC_ProductVersion
Example output:
A31003-S5070-J100-12-7631, 02/2013
663
15.1.4 Evaluation of the results

A version number a_b.c.d-efghij_klm is composed as follows:
a: Major release
b: Minor release
c: Fix release
d: Hotfix
efghij: Six-digit build number.

The six-digit build number is often simplified to the first two digits, e. g. build
130002 is called build 13. The first two digits were called DVD number in
previous versions of the OpenScape UC Application.
klm: Three-digit patch number. _klm is optional.
The product is called Va Rb FRc HFd Pklm.

Examples:
Build 1 of OpenScape UC Application V7 R0:

7_0.0.0-010000
Build 12 of OpenScape UC Application V7 R1:

7_1.0.0-120000
Hotfix 3 for OpenScape UC Application V7 R1 (V7 R1 HF3):

7_1.0.3-120003
Fix release 1 of OpenScape UC Application V7 R1 (V7 R1 FR1):

7_1.1.0-130000
Hotfix 2 for fix release 1 of OpenScape UC Application V7 R1 (V7 R1 FR1

HF2):
7_1.1.2-130002
Patch 901 for hotfix 2 for fix release 1 of OpenScape UC Application V7 R1

(V7 R1 FR1 HF2 P901):
7_1.1.2-130002_901
664
A31003-S5070-J100-12-7631, 02/2013
Update and Upgrade Preparations
15.2 Update and Upgrade Preparations

Be sure to execute the steps in this section before an update (see Section 15.3,
Updating the Application Computer, on page 711) and an upgrade (see Section
15.6.1, Upgrading Small Deployment, on page 750 or Section 15.6.2,
Upgrading Large Deployment, on page 771):
15.2.1 General
Verify that the requirements described in Section 4.1, File System and Operating
System, on page 116 have been complied with. This refers in particular to the
following requirements:
1. Verify that the OpenScape UC Application on SLES 11 SP1 or SP2 operates
with 64 bit (see point 1 on page 116 and Section 15.18, Upgrading a 32-bit
System to a 64-bit System, on page 937).
Use the following command for determining the SLES version used:
cat /etc/SuSE-release
The output reads for example:
SUSE Linux Enterprise Server 11 (x86_64)
VERSION = 11
PATCHLEVEL = 2
Using the following command you can check whether the SLES setup
medium is available:
zypper lr
NOTE: The availability of the OpenScape UC Application setup medium is
checked in Section 15.3.1.2, Small Deployment, on page 711 and Section
15.3.1.3, Large Deployment and Very Large Deployment, on page 716.
If you wish to upgrade an older SLES version to SLES 11 SP1 or SP2,
a) Execute the steps 1 on page 119 to 4 on page 121.
b) Activate the Update radio button.
c) Click on Next >.
d) Execute the further update steps.
e) IMPORTANT: If you execute command syncUC sync any time after
setting up the OpenScape UC Application and update or upgrade SLES
at a later date, you need to execute syncUC sync thereafter once more.
A31003-S5070-J100-12-7631, 02/2013
665
While you execute this command, the OpenScape UC Application is

unavailable.
fallback of the OpenScape UC Application (command
syncUC fallback) may fail, because different SLES module paths and
SLES kernel versions may be stored on the active and passive partition.
2. The SLES libraries mentioned in step 52 on page 140 must have been
installed before you start an OpenScape UC Application update or upgrade.
If they are missing, install them from the SLES setup medium. Step 1 on page
665 describes how to check whether the SLES setup medium is available.
Once these SLES libraries are installed, the SLES setup medium is no longer
required for updating or upgrading the OpenScape UC Application.
Application Builder
3. For an upgrade only:
Applications created with the Application Builder of the OpenScape UC
Application V6 R0 (see the operating instructions OpenScape UC Application
V6 Application Builder) cannot be used for the OpenScape UC Application
V7.
Therefore, delete such applications by executing in the CMP the instructions
provided in section Removing an Application from the OpenScape Media
Server in the administrator documentation OpenScape Media Server V6.
IMPORTANT: Do not delete the call flows and workspace!
The applications will be recreated in step 39 on page 768 or step 36 on page
797.
666
A31003-S5070-J100-12-7631, 02/2013
CMP
4. Using the CMP, back up the data and the file system according to the
Administration, section Backing up and restoring OpenScape System
Components.
IMPORTANT: The software version (fix release, patchset and hotfix) of
OpenScape UC Application must be the same when backing up and restoring
data. Restoring data on a software version different from the one used for
backing up data is not supported.
NOTE: Please also note Section 15.2.4, Preparing to the syncUC Fallback,
on page 707.
5. Check before you update or upgrade whether there are scheduled backup or
export tasks (see the administrator documentation OpenScape Common
Management Platform).
Backup unit names may get lost during an update or upgrade. Such
scheduled tasks must therefore be recreated after an update or upgrade at a
later date (see for example step 10 on page 713).
A31003-S5070-J100-12-7631, 02/2013
667
Backing up the CLM Access Configuration

6. The file /opt/licenses/clm/ApacheTomcat/ClmSettings.xml
contains the CLM (Customer License Manager) access configuration. Copy
this file to a safe location.
IMPORTANT: This location must not be found on the application computer.
Backing up the E/A Cockpit configuration files

7. If E/A Cockpit is installed, the following applies:
IMPORTANT: Table 115 shows the OpenScape UC Application and
OpenScape Voice versions that can be updated or upgraded without any
specialties as regards E/A Cockpit ( ). You can also see in which case an
additional step must be performed (W) and in which case updating or
upgrading cannot be performed without loss of data (-).
with
OpenScape
Voice V5 R0
DVD6
DVD5 HF7
DVD6 RC1
DVD set 5 HF3
DVD5
with
OpenScape
Voice V4 R1
DVD4 FR2 or later
OpenScape Voice:
DVD1, patchset/fix
release, hotfix
DVD3 FR1
with
OpenScape
Voice
version
DVD3
OpenScape
UC
Application
version
V3 R2 or
earlier
V3.1 R1 or
earlier
DVD8 PS5 HF3 or

earlier
V3 R2
V4 R1
DVD5
W W W W W W W
DVD5 HF3
DVD5 HF7
DVD6 RC1
DVD6
DVD3
W W
DVD3 FR1
DVD4 FR2 or later
-/
V5 R0
Table 115
Updating and upgrading E/A Cockpit
1 DVD9 of OpenScape UC Application V6 R0 is identical with Fix Release 1 (FR1) of this V6 R0. As
of this DVD number, using DVD numbers ceases and fix release numbers are used instead.
668
A31003-S5070-J100-12-7631, 02/2013
IMPORTANT: W means that E/A Cockpit (ending .eag) deletes already

existing files during the update or upgrade. In these cases the EAG files must
be backed up before the update or upgrade. This additional step is required
for all E/A Cockpit versions up to and inclusive 3.2_133.x (see Table 116). You
find the EAG files for Small Deployment on the application computer and for
Large Deployment and Very Large Deployment on the frontend computer in
the directory /opt/siemens/HiPathCA/WebSpace/Portal/webapps/
eacockpit-osc/WEBINF/groups.
Table 116 shows which E/A Cockpit version is installed by which OpenScape
UC Application version.
OpenScape UC
Application
version
with OpenScape
Voice version
DVD1, patchset/
fix release,
hotfix
E/A Cockpit version
V3 R2 or earlier
V3.1 R3 or earlier
DVD8 PS5 HF3
V1.0-021-104.0.0-37.25089
V3 R2 or later
V4 R1
DVD5
3.2_127.0.0-39.24483
DVD5 HF3
3.2_135.0.0-39.25105
DVD5 HF7
3.2_135.4.0-39.25504
DVD6 (obsolete)
3.2_135.0.0-39.25105
DVD6 RC1
3.2_135.4.0-39.25504
DVD6
3.2_135.8.0-39.26052
DVD3
3.2_127.0.0-39.24483
DVD3 FR1
3.2_133.0.0-39.24968
DVD4 FR2
3.2_135.0.0-39.25105
DVD4 FR2 HF2
3.2_135.4.0-39.25504
DVD5 FR3
3.2_135.4.0-39.25504
DVD5 FR3 HF2
3.2_135.8.0-39.26052
V5 R0
Table 116
E/A Cockpit Versions
1 DVD9 of OpenScape UC Application V6 R0 is identical with Fix Release 1 (FR1) of this V6 R0. As
of this DVD number, using DVD numbers ceases and fix release numbers are used instead.
Log files
8. When new log names are introduced, delete the old ones. Existing log files
are deleted by updating or upgrading. If required, back up the log files before
updating or upgrading.
Checks
9. Execute the Rapidstat UC program on the application computer to check the
configuration performed so far and basic features (see Section 5.4.2,
Checking with Rapidstat UC, on page 349).
A31003-S5070-J100-12-7631, 02/2013
669
10. When you update or upgrade Large Deployment or Very Large Deployment,
a) Execute step 9 on all media server computers.
b) Execute step 9 on all frontend computers.
670
A31003-S5070-J100-12-7631, 02/2013
15.2.2 Providing the Update/Upgrade Sources in a

Repository in osc-setup
ISO files are the only update and upgrade source of the OpenScape UC
Application. DVDs are no longer used. The update or upgrade of the OpenScape
UC Application is done by using the osc-setup script. The following main steps
that are described in detail in the following sub-sections must be executed before:
1. Update osc-setup.
2. Create a repository in osc-setup by using the ISO files.
A31003-S5070-J100-12-7631, 02/2013
671
15.2.2.1 Needed ISO Files

Table 117 shows the purposes and computers the ISO files are needed for:
Setup file
Contents
Deployment scenario
Small
Large Deployment
Deployment and Very Large
Deployment
AC1
AC
FE2
MS3
OpenScapeUcSuiteApps-Repository<version>.iso
Installation scripts, Repository meta data, etc.
OpenScapeUcSuiteAppsBasePackage-<version>.iso
The actual OpenScape UC Application
OpenScapeUcSuiteAppsOptionalPackage-<version>.iso
Lotus Domino, Application Builder, Client

Integration, Lotus Notes Extensions, etc.
OpenScapeUcSuiteApps-English<version>.iso
Announcements in English, TTS, ASR, Auto

OpenScapeUcSuiteApps-German<version>.iso5
Announcements in German, TTS, ASR, Auto

OpenScapeUcSuiteApps-Portuguese<version>.iso
Announcements in Portuguese and Brazilian,

TTS, Auto Attendant, voice conferencing and
voice portal
OpenScapeUcSuiteApps-Spanish<version>.iso
Announcements in Spanish, TTS, Auto

OpenScapeUcSuiteApps-Italian<version>.iso
Announcements in Italian, TTS, Auto

OpenScapeUcSuiteApps-French<version>.iso
Announcements in French, TTS, Auto

OpenScapeUcSuiteApps-Chinese<version>.iso
Announcements in Chinese, TTS, Auto

OpenScapeUcSuiteAppsAdditonalLanguages<version>.iso
The remaining languages supported for

announcements and voice conferencing
Table 117
1
2
3
4
5
Using the ISO Setup Files of the OpenScape UC Application
Frontend computer
IMPORTANT: This file is always required for setting up, updating or upgrading any deployment scenario.
IMPORTANT: This file is always required for setting up, updating or upgrading Integrated Deployment.
NOTE: Example of a file name:

OpenScapeUcSuiteApps-Repository-V7R1.0.0-130000.iso
Legend:
672
A31003-S5070-J100-12-7631, 02/2013
Icon
Meaning
You can use this ISO file for an installation on this computer.
This ISO file is not required for an installation on this computer.
Table 118
Legend for using the ISO Files
NOTE: The ISO files have a maximum size of 4 GB and can therefore be stored
on a USB stick formatted with FAT32.
The ISO files can be made available locally at the computer where osc-setup and
the OpenScape UC Application components will be updated/upgraded or they
can be made available remotely over the network. The remote provision has the
advantage that the ISO files only must be available once on an arbitrary SLES 11
computer in the network and need not be copied to each computer where
OpenScape UC Application components will be installed. The disadvantage is
that more preparation steps are needed.
NOTE: The ISO files remotely made available may be used for updating or
upgrading a Mobile Client Facade Server or an Openfire server as well.
Continue either with Section 15.2.2.2, Creating a Repository in osc-setup by
using local Update/Upgrade Sources, on page 674 or Section 15.2.2.3, Creating
a Repository in osc-setup by using remote Update/Upgrade Sources, on page
681.
NOTE: If you want to install additional RPM packages follow the instructions in
Section 14.1, Installing additional RPM Packages of the OpenScape UC Application, on page 637.
A31003-S5070-J100-12-7631, 02/2013
673
15.2.2.2 Creating a Repository in osc-setup by using local

Update/Upgrade Sources
Creating a repository in zypper
1. Check which update/upgrade sources are registered in osc-setup.
osc-setup lr
If the following expression is put out, continue with step 2 on page 674. If not,
continue with step 16 on page 677.
-bash: osc-setup: command not found
in zypper:
zypper lr
Example output:
:
# | Alias
--+-----------------------------------------------------------+------+---------+-------1 | SUSE-Linux-Enterprise-Server-11-SP2 11.2.2-1.234 | SUSE-Linux-Enterprise-Server-11-SP2
11.2.2-1.234 | Yes
| No

command:
zypper rr <number>
output.
Example of <URI> when using a local repository:
iso:/?iso=<path to ISO file>/OpenScapeUcSuiteApps-Repository-V7R1.0.0-130000.iso
Complete examples:
zypper ar iso:/?iso=/tmp/shi/osuca7/OpenScapeUcSuiteApps-Repository-V7R1.0.0-130000.iso
ucapp
Example output:
674
A31003-S5070-J100-12-7631, 02/2013
Adding repository 'ucapp' [done]

Repository 'ucapp' successfully added
Enabled: Yes
Autorefresh: No
GPG check: Yes
URI: iso:///?iso=/tmp/shi/OpenScapeUcSuiteApps-Repository-V7R1.0.0-130000.iso
zypper lr
:
# | Alias
--+------------------------------------+----------------------------+---------+-------1 | SUSE-Linux-Enterprise-Server-11-SP2 11.2.2-1.234 | SUSE-Linux-Enterprise-Server-11SP2 11.2.2-1.234 | Yes
| No
2| ucapp
| ucapp
| Yes
| No
correctly:
zypper ref
Example output:
Repository: ucapp
A31003-S5070-J100-12-7631, 02/2013
675
zypper in osc-setup
in zypper:
zypper lr
zypper rr <number>
output.
zypper se osc-setup
Example output:
S | Name
| Summary
| Type
osc-setup lr
15. Continue with step 19 on page 677.
676
A31003-S5070-J100-12-7631, 02/2013
Deleting old repositories

16. Check which update/upgrade sources are registered in osc-setup.
osc-setup lr
Example output 1:
Registered repositories (url):
No repository is registered in osc-setup. Continue with step 19 on page
677 in this case.
Example output 2:
Registered repositories (url):
1
dir:///tmp/tmpRepo
This output indicates that a repository is registered in osc-setup.
Continue with step 17 in this case.
17. Execute the following command to remove the first registration from the list:
osc-setup rr 1
18. Execute step 17 as often as is necessary to receive an output analog to the
following:
Repository removed successfully
Repository 1 not found by alias, number or URI.
Operation took: 1seconds
Provision
19. Create a directory for the temporary repository.
Example:
mkdir /tmp/tmpRepo
20. Provide the update/upgrade source osc-setup. The repository name may
differ from the repository name in zypper.
IMPORTANT: The following command creates a new repository, thus
deleting all repositories that may have already been provided.

OpenScapeUcSuiteApps-Repository-<version>.iso>
Example:
A31003-S5070-J100-12-7631, 02/2013
677
osc-setup cr -l /tmp/tmpRepo /tmp/shi/osuca7/OpenScapeUcSuiteApps-Repository-V7R1.0.0130000.iso

NOTE: osc-setup does not use an alias.
IMPORTANT: This command creates a temporary, locally linked repository.

This repository can only be used as long as the ISO files used are not deleted
or moved and the computer is not rebooted.
You also provide several ISO files by one command.
OpenScapeUcSuiteApps-Repository-<version>.iso> <path to another ISO file>
Example:
osc-setup cr -l /tmp/tmpRepo /tmp/shi/osuca7/OpenScapeUcSuiteApps-Repository-V7R1.0.0130000.iso /tmp/shi/osuca7/OpenScapeUcSuiteApps-English-V7R1.0.0-130000.iso
IMPORTANT: One of the ISO files in the command must be the file
OpenScapeUcSuiteApps-Repository-<version>.iso.
If you wish to register all ISO files in a directory by one command you need
to use option -b in addition.
osc-setup cr -b -l <path to the temporary repository> <path to the file
OpenScapeUcSuiteApps-BasePackage-<version>.iso>
Example:
osc-setup cr -b -l /tmp/tmpRepo /tmp/shi/osuca7/OpenScapeUcSuiteApps-BasePackageV7R1.0.0-130000.iso
Example output:
checking Arguments
Option Base-directory: yes
/tmp/shi/osuca7/OpenScapeUcSuiteApps-BasePackage-V7R1.0.0130000.iso
678
A31003-S5070-J100-12-7631, 02/2013

Splitrepository "addlang" integrated
Splitrepository "base" integrated
Splitrepository "zh" integrated
Splitrepository "en" integrated
Splitrepository "fr" integrated
Splitrepository "de" integrated
Splitrepository "it" integrated
Splitrepository "opt" integrated
Splitrepository "meta" integrated
Repository created successfully
removing all registered repositories
register new repository...done
21. You can have the list of repositories registered in the osc-setup (not zypper!)
put out for checking purposes:
osc-setup lr
Example output:
22. Check whether the repository has been defined correctly:
osc-setup ref
Example output:
Verbosity: 1
Initializing Target
Specified repositories:
Checking whether to refresh metadata for
71222b2273ffb64c070265e76768dbda
Repository '71222b2273ffb64c070265e76768dbda' is up to date.
Refresh end
A31003-S5070-J100-12-7631, 02/2013
679
Updating osc-setup
23. Stop the OpenScape UC Application:
24. Stop the MRCP service, the Nuance TTS and the Nuance ASR, if available:
25. Use the following command to check whether the current update/upgrade
source of the OpenScape UC Application is used. If required, osc-setup is
updated automatically.
Example output:
Building repository '36775188f3b177bb47bb16464f14b1ee' cache
[....done]
No update candidate for 'osc-setup'.
Resolving package dependencies...
Nothing to do.
26. If the output reveals a successful update, continue with step 27. If, however,
an error is put out, execute the following command to update osc-setup
manually:
zypper-osc in osc-setup
27. If you want to upgrade the OpenScape UC Application from V3 R2 to V7
continue with Section 15.2.3, Database Check, on page 699, if you want to
upgrade from V6 to V7 or if you want to update, continue with Section 15.2.4,
Preparing to the syncUC Fallback, on page 707.
680
A31003-S5070-J100-12-7631, 02/2013
15.2.2.3 Creating a Repository in osc-setup by using remote

Update/Upgrade Sources
There are two possibilities to provide the ISO files as a repository in osc-setup
over the network:
Using NFS
The ISO files are provided in a directory on the source computer, this
directory is mounted via the network to the target computer by using NFS and
a linked repository in osc-setup is created on the target computer.
NOTE: This option is recommended.
Advantages:
osc-setup only must be installed on the target computer. No osc-setup

or repository (neither in zypper nor in osc-setup) is needed on the
source computer.
There is no need to create an exported repository (-e option) in oscsetup which would be more time consuming since depending on the
number of needed ISO files gigabytes of data might need to be
copied. However, you have the option to create an exported
repository instead, if you want to.
Disadvantages:
The NFS server must be installed on the source computer and the
NFS client must be installed on the target computer.
Port 111 (RPC), port 2049 (NFS) and a dynamic port for
RPC.MOUNTD must be open on the source computer and on the
target computer.
Using HTTP
A persistent repository in osc-setup is created on the source computer and is
accessed remotely from the target computer by using HTTP.
Advantages:
An exported repository must be used on the source computer, i. e. it

still is available if this computer rebooted. However, using NFS could
create an exported repository as well.
Only port 80 must be open the source computer and the target
computer.
No installation of NFS server and NFS client needed.
Disadvantages:
A31003-S5070-J100-12-7631, 02/2013
681
An exported repository (-e option) in osc-setup must be created on

the source computer. Creating an exported repository is much more
time cosuming than creating a linked repository (-l option) or a
repository without option.
osc-setup must be installed on the source computer and the target

computer.
It might be necessary to change the Apache server configuration on

the source computer. See the Apache server documentation for
details.
The source computer is the computer where the ISO installation files (using NFS)
or the repository (using HTTP) is provided. This computer can be the backend
computer of the OpenScape UC Application but it can be as well any SLES 11
computer in the network.
The target computer is the computer where the repository in osc-setup should be
provided and used for installing components of the OpenScape UC Application.
This computer can be the backend computer of the OpenScape UC Application,
the mobile client faade server computer, a front-end computer, a media server
computer or the instant-messaging (Openfire server) computer.
If you want to use NFS, continue with sub-section Option 1: Using NFS for
accessing ISO files on page 683. If you want to use HTTP, continue with subsection Option 2: Using HTTP for accessing a persistent repository on page 697.
682
A31003-S5070-J100-12-7631, 02/2013
Option 1: Using NFS for accessing ISO files

The following steps describe how to make ISO files available on the source
computer in order to create a linked repository on the target computer.
Execute the following steps on the source computer:
1. Copy the ISO files into the directory to be shared.
NOTE: Note down this directory, e. g. /tmp/shi/osuca7.
2. Check whether the nfs-kernel-server RPM and the yast2-nfs-server RPM are
installed on the source computer:
zypper se match-any nfs
Example output:
S | Name
| Summary
| Type
--+-----------------------+-----------------------------------------+----------i | limal-nfs-server
| package
| limal-nfs-server
| srcpackage
i | limal-nfs-server-perl | LiMaL--NFS Server Library Perl Bindings | package
i | nfs-client
| package
i | nfs-doc
| package
i | nfs-kernel-server
| package
| nfs-utils
| srcpackage
i | nfsidmap
| package
| nfsidmap
| srcpackage
| quota-nfs
| Disk Quota System on NFS
| package
| sblim-cmpi-nfsv3
| package
| sblim-cmpi-nfsv3
| srcpackage
| sblim-cmpi-nfsv4
| package
| sblim-cmpi-nfsv4
| srcpackage
i | yast2-nfs-client
| package
| yast2-nfs-client
| srcpackage
i | yast2-nfs-common
| YaST2 - NFS Configuration, common parts | package
i | yast2-nfs-server
| package
| yast2-nfs-server
| srcpackage
If the nfs-kernel-server RPM and the yast2-nfs-server RPM are not installed,
install them:
zypper in nfs-kernel-server yast2-nfs-server
A31003-S5070-J100-12-7631, 02/2013
683
3. Start YaST:
yast
4. Open Network Services > NFS Server.
684
A31003-S5070-J100-12-7631, 02/2013
5. Activate the check box Start in the NFS Server area.
6. Select the Next button.
A31003-S5070-J100-12-7631, 02/2013
685
7. Select Add Directory in the Directories to Export area.
8. Enter the absolute path to the ISO installation files into the Directory to
Export field, e. g. /tmp/shi/osuca7.
686
A31003-S5070-J100-12-7631, 02/2013
9. Select OK.
10. Select OK without changing the default value in the Host Wild Card field.
A31003-S5070-J100-12-7631, 02/2013
687
11. Select Finish.

NOTE: This action changes the /etc/exports file.
12. Select Quit.
13. Execute the more /etc/exports command to see the current contents of
the changed file.
Example output:
/tmp/shi/osuca7*(fsid=0,crossmnt,ro,root_squash,sync,no_subtree_check)
14. Ensure that the following default ports NFS uses are open on the source
688
A31003-S5070-J100-12-7631, 02/2013
Execute the following steps on the target computer:

15. Ensure that the following default ports NFS uses are open on the target
16. The directory on the source computer containing the ISO installation files will
be mounted to a local directory on the target computer. Ensure that this local
directory exist. If it does not exist yet, create it.
Example:
mkdir /tmp/shi/osuca7Net
17. Check whether the nfs-client RPM and the yast2-nfs-client RPM are installed
on the target computer:
zypper se match-any nfs-client
Example output:
S | Name
| Summary
| Type
--+------------------+---------------------------+----------i | nfs-client
| Support Utilities for NFS | package
i | yast2-nfs-client | YaST2 - NFS Configuration | package
| yast2-nfs-client | YaST2 - NFS Configuration | srcpackage
If the nfs-client RPM and the yast2-nfs-client RPM are not installed, install
them:
zypper in nfs-client yast2-nfs-client
A31003-S5070-J100-12-7631, 02/2013
689
18. Start YaST:

yast
19. Open Network Services > NFS Client.
690
A31003-S5070-J100-12-7631, 02/2013
20. Select Add.
A31003-S5070-J100-12-7631, 02/2013
691
21. Edit the following fields:

a) NFS Server Hostname: Enter the IP address, host name or FQDN of the
source computer, e. g. myOsuca.
NOTE: You might want to use the Choose option to find computers with
shared directories in the network.
692
A31003-S5070-J100-12-7631, 02/2013
b) Remote Directory: Enter the path of the ISO files on the source
A31003-S5070-J100-12-7631, 02/2013
693
c) Mount Point (local): Enter the path of the directory on the target
computer where the ISO files on the source computer should be
mounted, e. g. /tmp/shi/osuca7Net.
NOTE: If the target computer is rebooted, the mount point is mounted as

well. If the target computer is rebooted and the NFS server on the source
computer is not reachable, the boot time of the target computer increases
significantly and the mount directory on the target computer is not
mounted.
694
A31003-S5070-J100-12-7631, 02/2013
22. Select OK.
23. Select OK.

24. Select Quit.
25. Check the mount point:
mount
Example output:
10.11.12.13:/tmp/shi/osuca7 on /tmp/shi/osuca7Net type nfs (rw,addr=10.11.12.13)
In this example, 10.11.12.13 is the IP address of the source computer.
26. Check whether the directory for the repository already exists. If it does not
exist yet, create it:
Example:
mkdir /tmp/tmpRepo
27. Create the osc-setup repository as usual. You might use no option, the l
option, the e option or the b option.
Example:
osc-setup cr -l /tmp/tmpRepo -b /tmp/shi/osuca7Net/OpenScapeUcSuiteApps-RepositoryV7R1.0.0-080000.iso
A31003-S5070-J100-12-7631, 02/2013
695

696
A31003-S5070-J100-12-7631, 02/2013
Option 2: Using HTTP for accessing a persistent repository

1. Copy the ISO files into a directory (<path to ISO file>) on the source
2. Check whether the directory where the persistent repository should be
created (<path to persistent repository>) already exits. If not,
create it:
Example:
mkdir /software/persRepo
NOTE: Do not create the persRepo directory in the /tmp directory since a
persistent repository should be created and /tmp might be emptied during a
reboot of the computer.
3. Determine the directory (<apache path to repository>) on the source
computer that should be reachable by using HTTP via the network and that
should allow access to the repository. The Apache server configuration might
need to be configured for this purpose. See the Apache server documentation
for details.
4. Create a persistent repository in osc-setup on the source computer by using
the directory stated above and the ISO file(s) you want to provide. The
corresponding command is e. g.:
osc-setup cr -e <path to persistent repository> -b <path to ISO file>/OpenScapeUcSuiteAppsReposirtory-<version>.iso
IMPORTANT: The e option is a must to create a persistent repositoy. You
must not use no option or the l option.
Example
osc-setup cr -e /software/persRepo -b /tmp/shi/osuca7/OpenScapeUcSuiteApps-RepositoryV7R1.0.0-130000.iso
NOTE: This step might be time consuming since depending on the number
of used ISO files gigabytes of data have to be copied.
5. Ensure that port 80 (HTTP protocol) is open on the source computer and on
the target computer.
6. This repository can be added to osc-setup on the target computer:
osc-setup ar http://<Name of the source computer>/<apache path to repository>
A31003-S5070-J100-12-7631, 02/2013
697

698
A31003-S5070-J100-12-7631, 02/2013
15.2.3 Database Check

NOTE: You need to follow the instructions in this section only when upgrading
from V3 R2 to V7 but not for upgrading from V6 to V7 or for an update.
If you upgrade to the OpenScape UC Application from V3 R2 to V7, the Solid DB
is migrated implicitly from the resource management database model to the
device management database model. Before you do this, you need to execute a
script checking the database for inconsistent or incomplete data records for which
such a migration is not possible. This will prevent data loss during migration. This
script only reads the database, it does not change the database.
If you upgrade from V6 R0 to V7, migration from the resource management
database model to the device management database model does not take place
because V6 R0 uses the device management database model already.
Requirements
1. Checking the database is only supported for upgrading from OpenScape UC
Application V3 R2 to OpenScape UC Application V7.
2. Be sure to have access to the INF-12-000111 in the G-DMS.
Procedure
3. Execute the following sub-steps to check whether the TellMeWhen database
has duplicate user entries and remove them if required.
a) Check whether duplicate user entries are available:
/opt/siemens/solid/bin/solsql -t -a tcp localhost 16760 dba '<password>' <path>/
find_duplicate_entries.sql
Replace <password> by the password of the Solid DB that had been

introduced as parameter SI_DB_LOGON_PASSWORD in the response file
knut.responsefile.txt during the OpenScape UC Application
installation. Due to security concerns it should not be the default
password (dba). The straight single quotation mark (') before and after
the password is needed, if the password contains special characters. Do
not use the normal (typographic) single quotation mark () instead.
Replace <path> with the path of the directory in which you have stored
the find_duplicate_entries.sql file. You receive this file from your
support (INF-12-000111).
b) If duplicate user entries are available, remove them:
/opt/siemens/solid/bin/solsql -t -a tcp localhost 16760 dba '<password>' <path>/
remove_duplicate_entries.sql
A31003-S5070-J100-12-7631, 02/2013
699
Again, replace <password> by the password of the Solid DB that had

been introduced as parameter SI_DB_LOGON_PASSWORD in the
response file knut.responsefile.txt during the OpenScape UC
Replace <path> with the path of the directory in which you have stored
the remove_duplicate_entries.sql file. You receive this file from
your support (INF-12-000111).
4. Mount the Repository ISO file (see Table 117 on page 672) according to the
following pattern:
Example:
5. Perform the database check:

bash /mnt/support/Domain/checkResourcesDBConsistency.sh
The execution of this command may take several minutes.
6. Analyzing the overview report
Two check reports are created: one overview report and one detailed report.
The overview report is put out in the console.
Example of an output in the console:
Writing report to file
/tmp/scs_domain-checkResourcesDB-report-20101224_2015.log
-----------------------------------------------Checking communication systems:
19 - 11 ERRORS
Checking BC federations:
10 - 6 ERRORS
Checking media servers:
0
Checking office codes:
10 - 9 ERRORS,
1 WARNINGS
Checking private number codes:
8 - 6 ERRORS
Checking phones:
16 - 11 ERRORS
Checking conferences:
16 - 15 ERRORS
Checking voice portals:
32 - 7 ERRORS
Checking allocated phones:
2 - 1 ERRORS
Checking call queues:
6 - 3 ERRORS
Checking voicemail:
2 - 1 ERRORS
-----------------------------------------------The following output line indicates that c objects of a data structure named "x"
have been found in the database, but e of them have an error and w have a
warning:
Checking x:
c - e ERRORS, w WARNINGS
The following output line indicates that all objects of a data structure are OK
and can be migrated without data loss:
Checking x:
c - OK
The detailed report provides more information.
700
A31003-S5070-J100-12-7631, 02/2013
7. Analyzing the detailed report

The detailed report is written in a report file. The location of this report file is
indicated in the first line of the console output.
Example of a report file path:
/tmp/scs_domain-checkResourcesDB-report-20101224_2015.log
The object types that may be checked can be divided in two categories:
resource groups and resources:
Resource groups
Communications system
BC federation
Media server
Office code
Private number code
Resources
Phone
Voice portal
Conference
Allocated phone
Call queue
Voicemail
Resource group entries in the report file are either error entries or warnings.
Each resource group entry containing at least one error message cannot be
migrated. A warning does not mean that the corresponding resource group
cannot be migrated.
Example of an error message and of a warning:
id: OfficeCodeH8K_-191
[ERROR] Missing CountryCode
[WARN] Missing OutsideLineInt
Like resource groups, resources can create errors or warnings. An error
indicates that the resource cannot be migrated. A warning indicates that the
resource is possibly in an inconsistent state after its migration and may have
to be configured for being used by the OpenScape UC Application.
Example of an error:
ERROR voicemails that have no normalized number set: 1
492404501125@ExtSystem_-441
A31003-S5070-J100-12-7631, 02/2013
701
Example of a warning:
[WARN] 1 phone contains warnings
15629872231@2
Phone is ONS device but has no BCOM federation
assigned. It will therefore no longer be set as ONS after
migration!
Extract from an example report file:
CHECKING RESOURCE GROUPS:
__________________________________________________
Checking communication systems (resource group type 1)
Found 19
ERRORS exist. Only 8 would be migrated
Containing errors: 11
id: SwitchH4K_-109
[ERROR] Missing subtype
id: SwitchH4K_-111
id: SwitchH4K_-113
id: SwitchH4K_-141, Type: HiPath4000
[ERROR] Missing CSTAAddressMain
[ERROR] Missing CSTAPortMain
[ERROR] Missing SubApplId
id: SwitchH8K_-63
[ERROR] Missing CSTAAddressMain
id: my2Mediaserver_-17
Checking BC federations (resource type 2)
Found 10
id: BCFed2Ms_-19
[ERROR] Missing
id: BCFed2Ms_-21
[ERROR] Missing
id: BCFed2Ms_-23
[ERROR] Missing
id: BCFed2Ms_-25
[ERROR] Missing
id: BCFed2Ms_-27
[ERROR] Missing
id: BCFed2Ms_-29
[ERROR] Missing
communication system
BcomHomeResponsibility
BcomHomeResponsibility
ComProviderResponsibility
Checking media server (resource group type 6)

Found none
702
A31003-S5070-J100-12-7631, 02/2013
Checking office codes (resource group type 3)

Found 10
[ERROR] Missing communication system
[ERROR] Missing LocalOfficeCode
id: OfficeCodeMS_+296
[ERROR] Missing Overlap
id: OfficeCodeMS_+308
[ERROR] Missing OutsideLineInt
Containing warnings: 1
Checking private number codes (resource group type 9)
Found 11
Containing errors 5 of 11
id: PrivateCodeH4K_-314
[ERROR] Missing Layer0Code
[WARN] Missing BarrierCode
id: PrivateCodeMS_+337
[ERROR] Missing Overlap
id: PrivateCodeMS_+340
[ERROR] Missing BarrierCode
CHECKING RESOURCE GROUPS:
__________________________________________________
Checking phones (resource type 3)
Found 8
[ERROR] 4 phones that have no communication system set
and
have no public or private extension
set: 4
492404501123@SwitchH8K_-347
492404501123@SwitchH8K_-355
492404501123@SwitchH8K_-371
492404501123@SwitchH8K_-403
These phones will not be migrated when updating to
A31003-S5070-J100-12-7631, 02/2013
703
version 6.0
To make sure that they can be migrated, assign them to
a communication system or assign them to a public or
private extension.
[ERROR] 1 phones that have no public or private extension
set: 1
492404501123@SwitchH8K_-405
These phones will not be migrated when updating to
version 6.0
a public or private extension.
[ERROR] 1 phones that have a private extension but not
private number code set: 1
0123@SwitchH4K_-437
Checking conferences (resource type 5)
Found 16
[ERROR] 2 conferences that have no communication system
set
and no normalized number set: 2
492404501127@myMediaserver_-445
To make sure that they can be migrated, assign them a
communication system.
[ERROR] 3 conferences that have no public or private
extension set
public or private extension.
[ERROR] 1 conferences that have a public extension but no
office code
an
office code.
Checking voice portals (resource type 10)
Found 32
[ERROR] 5 voice portals that have not normalized number
set
To make sure that they can be migrated, give them a
normalized number.
[ERROR] 2 voice portals that have no public or private
extension set
public or private extension.
Check allocated phones (resource type 9)
Found 2
704
A31003-S5070-J100-12-7631, 02/2013
[ERROR] 1 allocated phones that have no normalized number

set
492404501124@ExtSystem_-439
normalized number.
Checking call queues (resource type 8)
Found 6
OK, all would be migrated
Checking voicemails (resource type 7)
Found 2
[ERROR] 1 voicemails that have no normalized number set
492404501125@ExtSystem_-441
normalized number.
The resource group sections comprise a Notes section in which error
messages and warnings are explained in detail.
A normalized number is a unique identifier for a resource. It must therefore
not be assigned to another resource. If such a collision occurs just the same,
it is specified in the report file.
Collisions may occur with resources but not with resource groups.
We differentiate three collision types:
Collisions of phones
Several phones have the same normalized phone number.
Example of a phones' collision:
Found 8657
...
[ERROR]
4 phones with duplicate normalized numbers
+24086622307 Phone Id: 24086622307@2
Phone Id: 24086622307@25
+24088392913 Phone Id: 24088392913@25
Phone Id: 24088392913@2
If several phones have the same normalized phone number, they are
migrated under the following conditions only:
1. The phones are in the same domain.
2. The phones are all assigned to the same user.
Example:
5 phones with the IDs Phone1, Phone2, Phone3, Phone4 and Phone5 have
the same normalized phone number +12345. If Phone1 is assigned to a
user and Phone2 to Phone5 are not assigned to a user, the first migratable
phone is migrated and assigned to the user. If Phone1 cannot be migrated but
Phone2 is migratable, the latter is migrated and assigned to the user.
Collisions of other resources of the same type
A31003-S5070-J100-12-7631, 02/2013
705
Other resources of the same type have collided when two specimen of
another resource (for example Voicemail1 and Voicemail2) have the same
normalized phone number but no other resource (for example no nonVoicemail) has this normalized phone number.
In this case, of the resources of a normalized phone number only the first
migratable resource found is migrated. All further resources with the same
normalized phone number are not migrated. The users assigned to these
further resources are assigned to the first migratable resource found and
migrated. If no resource can be migrated, no resource of this collision is
migrated and none of the users assigned to the resources of this collision
either.
Example of a voicemails' collision:
Checking voicemails (resource type 7)
Found 10
ERRORS exist. Only 1 would be migrated.
[ERROR]
1 voicemails with duplicate normalized numbers
19727562864@2 same n.n. as +19727562864@25
(n.n. +19727562864)
Collisions of resources of different type
Resources of different type have collided when specimen of different
resources have the same normalized phone number, for example a phone
and an allocated phone. No resource, inclusive the one found first, is
migrated.
Example:
Found 8657
...
[ERROR] 3 phones with the same n.n. as a different resource
type
+17709579134 17709579134@2 (used as phone)
17709579134@25 (used as phone)
17709579134 (used as allocated phone)
+551100005551 551100005551@25 (used as phone)
+551100005551 (used as voicemail)
8. Use the CMP to repair the objects which are required in the OpenScape UC
Application V7 but cannot be migrated. You can obtain details from the
Administration.
9. Repeat step 3 on page 699 to step 8 on page 706 until the objects required
in the OpenScape UC Application V7 are not listed with errors neither in the
overview report nor in the detailed report.
706
A31003-S5070-J100-12-7631, 02/2013
15.2.4 Preparing to the syncUC Fallback

IMPORTANT: You can use syncUC only after installing OpenScape UC Application V7 or after upgrading to this version.
IMPORTANT: syncUC is not supported if UUIDs (Universally Unique Identifier)

are used in the /etc/fstab file.
15.2.4.1 Introducing syncUC

There are the following fallback options:
syncUC
syncUC uses a partition of the local hard disk. The OpenScape UC
Application is installed in this Root partition of the LVM2 memory. The syncUC
script enables synchronizing this installation on the free memory in the LVM2
(command syncUC sync). Both OpenScape UC Application installations are
fully equivalent. After a computer reboot you can start the OpenScape UC
Application on the Root partition or the synchronized version of the
OpenScape UC Application. You can start the synchronized version if the
installation on the Root partition was performed on the grounds of one of the
following situations:
Faulty upgrade
Faulty installation of a fix release or hotfix
Configuration error, for example deletion of large numbers of users
Software problems, for example Solid database crash
You find details about using syncUC in Section 15.2.4.2, syncUC

Commands, on page 707.
File system backup

It serves for restoring files after a catastrophic situation. It is executed by the
lvBackupManagementUtility.sh script (see Section 4.5, Configuring
the File System Backup, on page 181)
15.2.4.2 syncUC Commands

You can use syncUC as follows:
syncUC sync
A31003-S5070-J100-12-7631, 02/2013
707
The syncUC sync command synchronizes the currently active partition

towards the passive partition (fallback partition).
IMPORTANT: If you execute command syncUC sync any time after setting
up the OpenScape UC Application and update or upgrade SLES at a later
date, you need to execute syncUC sync thereafter once more. While you
execute this command, the OpenScape UC Application is unavailable.
fallback of the OpenScape UC Application (command syncUC fallback)
may fail, because different SLES module paths and SLES kernel versions
may be stored on the active and passive partition.
1. When executing syncUC initially it realizes that no configuration is
available yet. The following is put out:
Do you want to configure and enable partitioning now?
Please enter yes or no (default = no):
2. Enter yes and push the return key.
3. The following is displayed for example:
Found logical volumes:
1 ) /dev/OpenScapeUC/UC1 [actually mounted to /]
2 ) /dev/OpenScapeUC/UC2 [actually not mounted]
Please enter the first partition (Number or devicefile ,
default: 1):
syncUC has detected the two displayed partitions and asks for the
partition on which the OpenScape UC Application is installed.
OpenScape UC Application should have been installed on the partition
you have set up in Section 4.2.2.5, Creating the Logical Volume UC1,
on page 133.
NOTE: You find the names of the Logical Volume Group (example:
OpenScapeUC) and of the logical partitions (logcial volumes) (examples:
UC1 and UC2) again in Table 5 on page 118 and Table 127 on page 846.
Perform one of the following actions:
a) You need not do anything if the partition suggested as default solution
is the correct one.
b) If a solution different from the default is correct, enter the
corresponding digit.
c) Enter the complete path of the correct partition. This path is for
example put out by the lvdisplay command for this partition.
Example:
...
708
A31003-S5070-J100-12-7631, 02/2013
- Logical volume LV Name /dev/OpenScapeUC/UC1

VG Name UCVolumeGroup
LV UUID E1zTel-MtSn-Okmt-J1ud-Fhpk-o4G=-EUNryH
...
The following is put out:
Please enter the second partition (Number or devicefile ,
default: 2):
5. Specify analog to step 3 on page 708 the partition created as fallback
partition for the OpenScape UC Application in Section 4.2.2.6, Creating
the Logical Volume UC2, on page 136.
The configuration has been saved.
NOTE: You find an overview of the partitions on the computer in Table 5 on
page 118 and Table 127 on page 846.
syncUC query
The syncUC query command delivers the current status of the active and
passive partition. In this way you can see which of the partitions is active and
which is passive.
Example:
Logging to: /var/log/OpenScapeUC/syncUC-2012-06-14_09-00-17.log

SyncUC - 1.4.8-1
Active version is 7_0.0.2-130002 (V7 R0.0.2 BUILD 13 HF 2.0) installed on Wed Jun 13
13:58:28 2012 located on /dev/OpenScapeUC/UC1.
Passive version is 7_0.0.1-130001 (V7 R0.0.1 BUILD 13 HF 1.0) installed on Wed Jun 6
17:19:32 2012 located on /dev/OpenScapeUC/UC2 which was synchronized on Mon Jun 11
17:10:42 EDT 2012.
Please wait for post processing to complete......
Logfile: /var/log/OpenScapeUC/syncUC-2012-06-14_09-00-17.log
If no system has been configured, the following is put out for example:
Active version is package OpenScapeUC_ProductVersion is not installed (package
OpenScapeUC_ProductVersion is not installed) installed on package
OpenScapeUC_ProductVersion is not installed located on /dev/OpenScapeUC/UC1.
Passive version is package OpenScapeUC_ProductVersion is not installed (package
OpenScapeUC_ProductVersion is not installed) installed on package
OpenScapeUC_ProductVersion is not installed located on /dev/OpenScapeUC/UC2 which was
synchronized on unknown date.
syncUC fallback
A31003-S5070-J100-12-7631, 02/2013
709
Executing the syncUC fallback command marks the active partition as

passive and the passive partition as active. When you reboot the computer, it
boots from the partition marked as active, i. e. this partition becomes active
and the partition marked as passive becomes passive.
15.2.4.3 Fallback Preparation

1. Check whether the active partition has already been synchronized to the
passive partition with syncUC.
syncUC query
Example output:
Logging to: /var/log/OpenScapeUC/syncUC-2012-06-14_09-00-17.log
SyncUC - 1.4.8-1
Active version is 7_0.0.2-130002 (V7 R0.0.2 BUILD 13 HF 2.0) installed on Wed Jun 13
13:58:28 2012 located on /dev/OpenScapeUC/UC1.
Passive version is 7_0.0.1-130001 (V7 R0.0.1 BUILD 13 HF 1.0) installed on Wed Jun 6
17:19:32 2012 located on /dev/OpenScapeUC/UC2 which was synchronized on Mon Jun 11
17:10:42 EDT 2012.
Please wait for post processing to complete......
Logfile: /var/log/OpenScapeUC/syncUC-2012-06-14_09-00-17.log
2. If this level of the passive partition is the level the OpenScape UC Application
is to fall back on after a possibly failed update, upgrade, migration or
installation of a hotfix, you need not become active here.
If, in contrast, the OpenScape UC Application is to fall back on the current
level of the OpenScape UC Application, execute the following command:
syncUC sync
710
A31003-S5070-J100-12-7631, 02/2013
Updating the Application Computer
15.3 Updating the Application Computer

15.3.1 Updating to a new Fix Release
Read the latest OpenScape UC Application Release Notes containing
information on the current OpenScape UC Application fix releases.
Be sure to execute the following important steps:
1. Verify that the instructions given in Section 15.2, Update and Upgrade
Preparations, on page 665 were carried out.
2. Save the old response file in a separate directory. It will be needed in case of
a restoration.
15.3.1.1 Integrated Deployment

This is described in the OpenScape Voice documentation.
15.3.1.2 Small Deployment

NOTE: Updating the OpenStage client on the server side is contained in the
command osc-setup up in step 6 on page 711. However, if only the
OpenStage Client should be updated, you can execute instead of step 1 on page
711 to step 11 on page 714 step 12 on page 715.
Execute the following update steps:
2. Follow the instructions in Section 15.2.2, Providing the Update/Upgrade
Sources in a Repository in osc-setup, on page 671 to provide all required
ISO setup files as repository in osc-setup and to update osc-setup if required.
3. If an Openfire server is installed on the application computer, stop it:
4. Stop the OpenScape UC Application by executing the following command:
6. Perform the actual update:
A31003-S5070-J100-12-7631, 02/2013
711
osc-setup up
IMPORTANT: We describe an alternative to this command in Section 15.3.3,
Updating using the CMP (UI Patching) instead of osc-setup, on page 733.
Updating is performed fully automatically and overrides configuration files.
However, except for the files described in step 7 on page 668, such
configuration files are previously backed up automatically so that there is no
need to back them up manually before the update.
7. Restore the E/A Cockpit configuration files that may have been backed up in
step 7 on page 668.
8. Execute the following sub-steps if you do not wish to install an RPM package
Example output:
checking Arguments
Option clean: yes
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
712
A31003-S5070-J100-12-7631, 02/2013
Example:
rm -R /tmp/tmpRepo
10. Start the OpenScape UC Application when the update process is finished by
If you noticed in step 5 on page 667 that there were scheduled backup or
export tasks to be executed before the update, you need to recreate them
now (see the administrator documentation OpenScape Common
Management Platform), because backup unit names may get lost during an
update.
If you have updated to the OpenScape UC Application V7 and connected the

OpenScape UC Application to an OpenScape Voice, the following applies:
A31003-S5070-J100-12-7631, 02/2013
713
The OpenScape Voice resources (extensions, office codes, private

number codes) of all business groups are transmitted to OpenScape UC
Application only if the Use Domain to Business Group Mapping check
box in the CMP under Configuration > CMP > System Settings is
inactive.
If the OpenScape Voice resources of only one business group shall be

transmitted to the OpenScape UC Application, the Use Domain to
Business Group Mapping check box in the CMP under
Configuration > CMP > System Settings must be active and, also in the
CMP but under Configuration > OpenScape Voice > Business Group
List > <BG ...> > General, you need to set the Domain field to value
system manually. If you fail to do so, synchronization between the
OpenScape UC Application and the OpenScape Voice will not work.
11. If an Openfire server is installed on the application computer, start it:

714
A31003-S5070-J100-12-7631, 02/2013
12. Updating the OpenStage client on the server side is contained in the
command osc-setup up in step 6 on page 711. However, if only the
OpenStage Client should be updated, you can execute instead of step 1 on
page 711 to step 11 on page 714 this step 12.
a) Stop the frontend server (WebClient):
/etc/inid.d/symphoniad stop WebClient
b) Update the OpenStage Client on the server side:
rpm -U CA2-OSIPP-STANDARD-<version>.rpm
If you want to update the OpenStage Client for Integrated Deployment,
use the following command instead:
rpm -U CA2-OSIPP-STANDARD-<version>.rpm --prefix=/enterprise
c) Start the frontend server:
/etc/inid.d/symphoniad start WebClient
A31003-S5070-J100-12-7631, 02/2013
715
15.3.1.3 Large Deployment and Very Large Deployment

We divide updating Large Deployment and Very Large Deployment into the
following major steps, detailing them further down the text:
Stopping all server components of the OpenScape UC Application on all

computers (application computer, frontend computers, media server
computers etc.)
Updating OpenScape UC Application on the application computer
Starting OpenScape UC Application on the application computer
Updating the frontend servers on all frontend computers
Updating the media servers on all media server computers
Starting the frontend servers on all frontend computers and the media servers
on all media server computers
NOTE: In order to update the OpenStage Client, an update must be performed

on the application computer, on the frontend computer and on the OpenStage
phone. The osc-setup up in step 6 on page 718 and step 17 on page 720
contains the update on the application computer and on the frontend computer.
However, if only the OpenStage Client should be updated on the application
computer, you can execute instead of step 1 on page 717 to step 9 on page 719
step 10 on page 719. This applies similarly to step 22 on page 721 on the frontend
computer.
716
A31003-S5070-J100-12-7631, 02/2013
Stopping the OpenScape UC Application

1. Log on to the application computer, the frontend computers and the media
server computers with the user name root.
ISO setup files as repository in osc-setup and to install or update osc-setup if
required.
4. Stop the server components of the OpenScape UC Application on the
frontend and media server computers:
NOTE: You can execute these commands on different computers at the
same time.
On the frontend computers:

NOTE: /etc/init.d/symphoniad stop WebClient_FE is not
sufficient.
On the media server computers:

Stop the MRCP service, the Nuance TTS and the Nuance ASR, if
available:
5. Stop the OpenScape UC Application by executing the following command on

the application computer:
A31003-S5070-J100-12-7631, 02/2013
717
Update on the application computer

IMPORTANT: Execute the steps described here on the application computer first
before updating the frontend or media server computer.
osc-setup up
IMPORTANT: We describe an alternative to this command in Section 15.3.3,
Updating using the CMP (UI Patching) instead of osc-setup, on page 733.
This alternative reduces considerably the number of steps to be executed
manually.
The update process is fully automatic and since no configuration files are
overridden you need not back up these files before the update.
Example output:
checking Arguments
Option clean: yes
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
718
A31003-S5070-J100-12-7631, 02/2013

Example:
rm -R /tmp/tmpRepo
8. Start the OpenScape UC Application when the update process is finished by
10. To update the OpenStage client you need to perform an update on the
application computer (this step 10), the frontend computer (see step 22 on
page 721) and on the OpenStage telephone. The osc-setup up command
in step 6 on page 718 contains the update on the application computer.
However, if only the OpenStage Client should be updated on the application
computer, you can execute instead of step 1 on page 717 to step 9 on page
719 this step 10.
a) Stop the backend component of the frontend server (WebClient):
/etc/inid.d/symphoniad stop WebClient_BE
b) Update the OpenStage Client on the application computer:
rpm -U CA2-OSIPP-BACKEND-<version>.rpm
application computer and execute the RPM command in this directory.
c) Start the backend component of the frontend server:
/etc/inid.d/symphoniad start WebClient_BE
A31003-S5070-J100-12-7631, 02/2013
719
Update on the frontend computer

NOTE: You can update the frontend and media server computer in parallel.
11. Verify that the OpenScape UC Application has been updated on the
12. Verify that the OpenScape UC Application has been started on the application
computer. The server components of the OpenScape UC Application must
have been stopped on all other computers (for example media server
computer).
13. Please wait about 5 minutes before you start updating on the frontend
computer. You should be able to log on to the CMP of the OpenScape
backend services.
required.
16. Execute the following command to stop a probably still operating frontend
server:
osc-setup up
18. Updating is performed fully automatically and overrides configuration files.
However, except for the files described in step 7 on page 668, such
configuration files are previously backed up automatically so that there is no
need to back them up manually before the update.
Restore the E/A Cockpit configuration files that may have been backed up in
step 7 on page 668.
Example output:
checking Arguments
720
A31003-S5070-J100-12-7631, 02/2013
Option clean: yes

Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Example:
rm -R /tmp/tmpRepo
20. Perform the steps 11 on page 720 to 19 on page 720 for all frontend
computers.
21. Do not restart the frontend servers yet.
22. To update the OpenStage client you need to perform an update on the
application computer (see step 10 on page 719), the frontend computer (this
step 22) and on the OpenStage telephone. The osc-setup up command in
step 17 on page 720 contains the update on the frontend computer. However,
if only the OpenStage Client should be updated on the frontend computer, you
can execute instead of step 11 on page 720 to step 20 on page 721 this step
22.
a) Stop the frontend component of the frontend server (WebClient):
/etc/inid.d/symphoniad stop WebClient_FE
A31003-S5070-J100-12-7631, 02/2013
721
b) Update the OpenStage Client on the frontend computer:

rpm -U CA2-OSIPP-FRONTEND-<version>.rpm
frontend computer and execute the RPM command in this directory.
c) Start the frontend component of the frontend server:
/etc/inid.d/symphoniad start WebClient_FE
d) Execute the substeps a to c on all frontend computers.
722
A31003-S5070-J100-12-7631, 02/2013
Update on the media server computer

NOTE: You can update the frontend and media server computer in parallel.
23. Verify that the OpenScape UC Application has been updated on the
have been stopped on all other computers (for example frontend computer).
25. Please wait about 5 minutes before you start updating on the media server
backend services.
required.
28. Execute the following command to stop a probably still operating media
server:
osc-setup up
Updating occurs fully automatically and since no configuration files are
overridden you need not back up these files before the update.
31. The Nuance TTS default installation installs only the language package for
American English. If you want to add packages for other languages, execute
the steps 9 on page 299 and 15 on page 307.
A31003-S5070-J100-12-7631, 02/2013
723

Example output:
checking Arguments
Option clean: yes
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Example:
rm -R /tmp/tmpRepo
Reboot
33. Start all frontend servers by executing the following command on all frontend
computers:
34. Start the MRCP service on all media server computers, the Nuance TTS and
the Nuance ASR:
724
A31003-S5070-J100-12-7631, 02/2013
35. Start all media servers by executing the following command on all media
server computers:
Configuration
36. If you noticed in step 5 on page 667 that there were scheduled backup or
export tasks to be executed before the update or upgrade, you need to
recreate them now (see the administrator documentation OpenScape
Common Management Platform), because backup unit names may get lost
during an update.
37. If you have updated to the OpenScape UC Application V7 and connected the
OpenScape UC Application to an OpenScape Voice, the following applies:

inactive.
A31003-S5070-J100-12-7631, 02/2013
725
726

A31003-S5070-J100-12-7631, 02/2013
15.3.2 Installing a Hotfix

NOTE: This section describes how to install a hotfix with the help of commands
in a command line. See Section 15.3.3, Updating using the CMP (UI Patching)
instead of osc-setup, on page 733 for setting up a hotfix using the CMP, which
reduces considerably the number of steps to be executed manually in particular
for Large Deployment and Very Large Deployment).
A hotfix is provided to you as ISO file. It is always a single hotfix ISO file.
Example:
repository with other ISO files by means of an osc-setup cr ... command.
The ISO file contains
New RPM packages for the application computer, the frontend computers
and the media server computers and
New software for Desktop Client, Web Collaboration, Nuance etc.
Please refer to the Release Notes to learn which of the above modifications are
contained in the respective hot-fix.
15.3.2.1 Small Deployment

The usual procedure for installing the application computer RPM packages is as
follows:
from the one outlined here.
1. Check before you install the hotfix whether there are scheduled backup or
Backup unit names may get lost during a hotfix installation. Such scheduled
tasks must therefore be recreated after the hotfix installation at a later date
A31003-S5070-J100-12-7631, 02/2013
727

If the ISO file is available on a USB stick and not on the computer, proceed
as follows:
ls /dev/sd*
Example output:
728
A31003-S5070-J100-12-7631, 02/2013

ls /dev/sd*
Example output:
mkdir /media
Sample:
osc-setup up
9. Delete the repository from the osc-setup:
osc-setup rr <number>
<number> is the number of the entry you wish to delete.
10. Unmount the USB stick:
umount /media
11. Restore the E/A Cockpit configuration files that may have been backed up in
step 7 on page 668.
A31003-S5070-J100-12-7631, 02/2013
729
13. Start the OpenScape UC Application after the hot-fix installation by executing
export tasks to be executed before the hotfix installation, you need to recreate
them now (see the administrator documentation OpenScape Common
Management Platform), because backup unit names may get lost during a
hotfix installation.
15.3.2.2 Large Deployment and Very Large Deployment

The usual procedure for installing the application computer RPM packages is as
follows:
from the one outlined here.
1. Check before you install the hotfix whether there are scheduled backup or
Backup unit names may get lost during a hotfix installation. Such scheduled
tasks must therefore be recreated after the hotfix installation at a later date
730
A31003-S5070-J100-12-7631, 02/2013

3. Stop all server components of the OpenScape UC Application on all
computers etc.)
5. Execute steps 5 on page 728 to 10 on page 729 on the application computer.
6. After you have installed the hotfix, execute the following command on the
8. Execute steps 5 on page 728 to 10 on page 729 on all frontend computers.
9. IMPORTANT: If applicable, one of the frontend computers hosted the E/A
Cockpit configuration files backed up in step 7 on page 668. Restore it.
10. Execute steps 5 on page 728 to 10 on page 729 on all media server
computers.
A31003-S5070-J100-12-7631, 02/2013
731
11. Start the frontend server on all frontend computers and the media servers on
all media server computers.
export tasks to be executed before the hotfix installation, you need to recreate
them now (see the administrator documentation OpenScape Common
Management Platform), because backup unit names may get lost during the
hotfix installation.
732
A31003-S5070-J100-12-7631, 02/2013
15.3.3 Updating using the CMP (UI Patching) instead

of osc-setup
IMPORTANT: Updating via the CMP (UI Patching) is only supported for Small
Deployment, Large Deployment and Very Large Deployment but not for
Integrated Deployment.
IMPORTANT: Updating using the CMP (UI patching) is only supported for an
OpenScape UC Application update but not for an upgrade.
You can replace the actual update of the osc-setup up by actions in the CMP.
This reduces the number of steps to be executed for Large Deployment and Very
Large Deployment considerably, because only actions are performed manually
on the application computer but not the actual update steps on the frontend
computers and media server computers.
The feature update via CMP (UI Patching) is always included in the OpenScape
UC Application V7 setup but disabled by default. It must be activated by
executing the prepareUpdate.sh script (see below).
NOTE: You find further details of updating in the CMP in the administrator
documentation OpenScape Common Management Platform, Administration.
A31003-S5070-J100-12-7631, 02/2013
733
15.3.3.2 Procedure
This section describes the installation of a hotfix for Small Deployment as update
example. The steps for updating to a new fix release or Large Deployment and
Very Large Deployment are executed analog.
In this section, perform all command invocations in command lines on the
1. Ensure that the instructions given in Section 15.2, Update and Upgrade
Preparations, on page 665 have been carried out.
If an HTTP proxy is configured for the application computer, the frontend
computers, the media server computers and for other computers, these settings
must be restricted to such an extent that the application computer, the frontend
computers and the media server computers do not use an HTTP proxy when
communicating with each other. To do this, execute either step 2 on page 734
(use of YaST) or step 3 on page 735 (editing the /etc/sysconfig/proxy file).
2. Execute the following sub-steps:
a) Execute the yast command.
b) Open the Network Services > Proxy.
734
A31003-S5070-J100-12-7631, 02/2013
c) Add the fully qualified domain names of the application computer, the
frontend computers and the media server computers in the No Proxy
Domains field.
NOTE: You receive the FQDN of a computer by executing the
hostname -f command on this computer.
d) Select Finish.
e) Select Quit.
f)
3. Execute the following sub-steps:

a) Open the /etc/sysconfig/proxy file in an editor, for example:
vi /etc/sysconfig/proxy
b) Add the fully qualified domain names (FQDN) of the application computer,
the frontend computers and the media server computers to the value of
the NO_PROXY parameter.
c) Save the /etc/sysconfig/proxy file.
d) Continue with step 4 on page 735.
4. Open Maintenance > Inventory > Nodes & Applications > Applications >
OpenScape UC in the CMP. Click on the small triangle to the right of
OpenScape UC and select Software activation....
A31003-S5070-J100-12-7631, 02/2013
735
The feature update via CMP (UI patching) is not yet activated.
This feature is not yet activated.
5. Log on with user name root in a command line on the application computer.
6. Perform the activation:
bash /opt/siemens/servicetools/install/bin/prepareUpdate.sh
Example output:
736
A31003-S5070-J100-12-7631, 02/2013
2012/03/28-19:52:33 # INFO = #################### EXECUTION OF /opt/siemens/

servicetools/install/bin/prepareUpdate.sh STARTS ####################
2012/03/28-19:52:33 # INFO = Reading deployment from response file
2012/03/28-19:52:33 # INFO = Deployment StandardDuplexSmall is supported, continue...
2012/03/28-19:52:33 # INFO = Local path to installation media is not specified, skip
YUM repository setup
2012/03/28-19:52:33 # INFO = Reading backend node (BE) info: 10.235.200.23
2012/03/28-19:52:33 # INFO = No frontend nodes (FE) found
2012/03/28-19:52:33 # INFO = No media server nodes (MS) found
2012/03/28-19:52:33 # INFO = Checking for YUM repositories...
2012/03/28-19:52:33 # INFO = OSC Update repository does not exist, create directory /
OSCupdate.
2012/03/28-19:52:33 # INFO = OSC Base repository does not exist, create directory /
OSbase.
2012/03/28-19:52:33 # INFO = Feature is not activated (prepare run for first time or
last run was unsuccessful)
2012/03/28-19:52:33 # INFO = Checking if trusted ssl connections already exist...
2012/03/28-19:52:33 # INFO = Only BE node found, no FE/MS to check trusted connections
2012/03/28-19:52:33 # INFO = Allo sym user run updateAllNodes.sh script as root
user
2012/03/28-19:52:33 # INFO = Http configuration file created to setup base/update
repositories
2012/03/28-19:52:33 # INFO = Http configurations applied successfully
2012/03/28-19:52:33 # INFO = HTTP access to /OSCbase repository verified
2012/03/28-19:52:33 # INFO = HTTP access to /OSCupdate repository verified
2012/03/28-19:52:33 # INFO = Feature installed successfully, create lock file to mark
activation
servicetools/install/bin/prepareUpdate.sh ENDED SUCCESSFULLY ####################
A31003-S5070-J100-12-7631, 02/2013
737
7. The CMP displays the following now:
8. If you use syncUC as fallback solution (see Section 15.2.4, Preparing to the
syncUC Fallback, on page 707), we recommend activating the check box
Synchronize Active to Passive partitions in the Synchronize section.
When you do this, the active partition is automatically copied to the passive
partition before the update to be prepared for a fallback.
9. The hotfix was provided to you as ISO file. It is always a single hotfix ISO file.
Example:
repository with other ISO files by means of osc-setup cr ....
This does not apply for an update to a new fix release for which several ISO
files are delivered. They must be combined to a repository according to
Section 15.2.2, Providing the Update/Upgrade Sources in a Repository in
osc-setup, on page 671.
10. Mount the ISO file according to the following example:
mount -o loop <path>/OpenScapeUcSuiteApps-Patch-<version number>.iso /mnt
Example of a directory on the hard disk:
738
A31003-S5070-J100-12-7631, 02/2013
mount -o loop /tmp/shi/osuca7/OpenScapeUcSuiteApps-Patch-V7R1.0.0-130001.iso /mnt
If you do not wish to mount an ISO file on the computer hard disk but on a
DVD, mount the DVD first by the mount /dev/cdrom /media command
and subsequently the ISO file by the following command:
mount -o loop /media/OpenScapeUcSuiteApps-Patch-V7R1.0.0-130001.iso /mnt
If you wish to mount the ISO file on a USB stick instead of on the computer
hard disk, proceed as follows:
ls /dev/sd*
Example output:
ls /dev/sd*
Example output:
mkdir /media
e) Mount the USB stick.
Example:
f)

mkdir /mnt
g) Mount the ISO file on the USB stick:
A31003-S5070-J100-12-7631, 02/2013
739
mount -o loop <path>/OpenScapeUcSuiteApps-Patch-<version>.iso /mnt

Example:
mount -o loop /media/OpenScapeUcSuiteApps-Patch-V7R1.0.0-130001.iso /mnt
The hotfix RPM is for example:
/mnt/noarch/OpenScapeUC_ProductVersion-8_0.0.0-080001.noarch.rpm
11. Enter the mount path to the hotfix ISO file in the CMP in the Path field of the
Repository Path section without the file's name.
Example:
/mnt
In case of an update to a new fix release specify the path under which the
created repository of all ISO files used was provided.
12. Click on Start in the CMP.
740
A31003-S5070-J100-12-7631, 02/2013

IMPORTANT: Your CMP session is closed. All components of the
OpenScape UC Application on the application computer and - if available - on
the frontend and media server computers are shut down.
14. Enter the following command in a command line on the application computer:
tailf /var/siemens/common/log/install/uipatching/updateAllNodes.log
The last lines of this log file are always displayed.
15. Wait for the following message that indicates the successful update:
...
Starting OpenSOA Framework..done
2012/03/29-01:16:56 # INFO = 10.235.200.23 (BACKEND): Symphonia started successfully
after successful update
2012/03/29-01:16:56 # INFO = Message of the day restored on 10.235.200.23
2012/03/29-01:16:56 # INFO = Collecting local backen logs
2012/03/29-01:16:56 # INFO = Update successful (error code 0)
servicetools/install/bin/updateAllNodes.sh ENDED ####################
16. After a login, the CMP indicates the successful performance:
Example of Large Deployment:
A31003-S5070-J100-12-7631, 02/2013
741

export tasks to be executed before the update, you need to recreate them
update.
742
A31003-S5070-J100-12-7631, 02/2013
19. If you use Small Deployment and backed up E/A Cockpit configuration files in
step 7 on page 668, execute the following sub-steps:
a) Stop the OpenScape UC Application on the application computer:
b) Restore the E/A Cockpit configuration files.
c) Start the OpenScape UC Application on the application computer:
20. If you use Small Deployment and the /etc/init.d/NSService file is
available on the application computer, execute the following command:
/etc/init.d/NSService start
21. If you use Small Deployment, updating via the CMP (UI Patching) is herewith
complete.
You need to execute the following steps for Large Deployment and Very
22. If the /etc/init.d/NSService file is available on the application
computer, execute the following command:
23. If you backed up E/A Cockpit configuration files in step 7 on page 668,
A31003-S5070-J100-12-7631, 02/2013
743
a) Stop the OpenScape UC Application on the frontend computer that used

to host the E/A Cockpit configuration files:
b) Restore the E/A Cockpit configuration files.
c) Start the OpenScape UC Application on this frontend computer:
24. Check on all media server computers whether the /etc/init.d/
NSService file is available. If this file is available on a computer, execute the
following command on this computer:
steps 9 on page 299 and 15 on page 307 on all media server computers.
744
A31003-S5070-J100-12-7631, 02/2013
Upgrade and Migration Tables
15.4 Upgrade and Migration Tables

The following tables show the options for an upgrade and migration to
OpenScape UC Application V7 R1.
Supported is always an upgrade from the last two versions of a solution to the
current version of this solution.
Upgrade and Migration for Small Deployment and Large Deployment
Source version1 of the OpenScape UC Application to be
upgraded or migrated
Upgrade/migration target: OS UC Application

V7 R1
Small
Deployment
with OSV V6,
OSV V7 R0,
HiPath 4000 V5
or HiPath V62
Large
Deployment
with OSV V6,
OSV V7 R0,
HiPath 4000 V5
or HiPath V62
Very Large
Deployment
with OSV V6 or
OSV V7 R0 or
HiPath V5 or
HiPath V62
OS UC Appl. V3 R0 with OSV V3.1 R2 or

OS UC Appl. V3 R1 with OSV V3.1 R3 or
OS UC Appl. V3 R2 with OSV V3.1 R3 or V4 R1
3
All deployment scenarios

OS UC Appl. V3 R2 with OSV V5 R0
Small Deployment
+ sm. --> la.
Large Deployment
+
sm. --> la. +
la. --> v. la.
+
la. --> v. la.
OS UC Appl. V4 R0 with HiPath 4000 V5 or V6

Small Deployment
OS UC Appl. V6 R0 with one of the following PBXs:

OSV V4 R1, V5 R0 or V6 or HiPath 4000 V5 or V6
Small Deployment
+ sm. --> la.
Large Deployment
+
sm. --> la. +
la. --> v. la.
7+
la. --> v. la.
OS UC Appl. V7 R1 with one of the following PBXs:

OSV V7 or HiPath 4000 V5 or V6
Small Deployment
Large Deployment
Table 119
sm. --> la.
sm. --> la. +

la. --> v. la.
la. --> v. la.
Upgrade and Migration Table for Small Deployment and Large Deployment
1 See Section 15.1, Determining the Source Version, on page 662.

2 Changing the HiPath 4000 connection to an OpenScape Voice connection is not the subject of this documentation.
3 First upgrade to OpenScape UC Application V3 R2, see installation and upgrade instructions for OpenScape UC Application V3 R2. Then
upgrade to OpenScape UC Application V7 R1. One or several migrations may be required thereafter.
A31003-S5070-J100-12-7631, 02/2013
745
4 Upgrading OpenScape UC Application V4 R0 to V7 R1 directly is not supported. First upgrade to V6 R0 (see installation and upgrade
instructions for OpenScape UC Application V6 R0). Then upgrade from V6 R0 to V7 R1.
5 Upgrading OpenScape UC Application V4 R0 to V7 directly is not supported. First upgrade to V6 R0 (see installation and upgrade
instructions for OpenScape UC Application V6 R0). Then upgrade from V6 R0 to V7. Then migrate from Small Deployment to Large
Deployment.
6 Upgrading OpenScape UC Application V4 R0 to V7 directly is not supported. First upgrade to V6 R0 (see installation and upgrade
instructions for OpenScape UC Application V6 R0). Then upgrade from V6 R0 to V7. Then migrate from Small Deployment to Large
Deployment. Then migrate from Large Deployment to Very Large Deployment.
7 IMPORTANT: If you wish to upgrade to an OpenScape UC Application V7 R1 connected to a HiPath 4000 V6 R2, first upgrade the
OpenScape UC Application to V7 R1 and then the HiPath 4000 to V6 R2. If you do not follow this sequence, the connection between the
OpenScape UC Application and the HiPath 4000 will be lost.
Upgrade and migration for Integrated Deployment

Source version 1 2 of the OpenScape UC Application to be Upgrade/migration target: OS UC Application V7 R1
upgraded or migrated
Integrated
Small
Large
Very Large
Deployment Deployment Deployment Deployment
with OSV
with OSV V6 with OSV V6 with OSV V6
V7 R0
or V7 R0
or V7 R0
or V7 R0
OS UC Application V3 R0 with OSV V3.1 R2
34
34
OS UC Application V3 R2 with OSV V3.1 R3 or V4 R1
34
OS UC Application V3 R2 with OSV V5 R0
4 or
imaging
Imaging +
sim. --> sm.
Imaging +
Imaging +
sim. --> sm. + sim. --> sm. +
sm. --> la.
sm. --> la. +
la. --> v. la.
Imaging
Imaging +
sim. --> sm.
Imaging +
Imaging +
sim. --> sm. + sim. --> sm. +
sm. --> la.
sm. --> la. +
la. --> v. la.
sim. --> sm.
sim. --> sm. + sim. --> sm. +

sm. --> la.
sm. --> la. +
la. --> v. la.
OS UC Application V6 R0 with OSV V6

OS UC Application V7 with OSV V7

Table 120
Upgrade and Migration Table for Integrated Deployment

2 In this table, the source version is always Integrated Deployment which does not support a connection to HiPath 4000. Therefore, only
connections to an OSVoice are mentionned in this table.
3 First, upgrade to OS UC Application V3 R2 (see the installation and upgrade guide of the OS UC Application V3 R2) and upgrade the OSV
to V4 R1 or V5 R0 (see the installation and upgrade guide of the OSV). Then upgrade the OS UC Application to V7 and the OSV to V7.
One or several migrations may be required thereafter.
4 OS UC Application V7 Integrated Deployment is supported for a connection to OSV V6 or V7 only.
746
A31003-S5070-J100-12-7631, 02/2013
Upgrade and migration for Integrated Duplex

The Integrated Duplex deployment scenario is not supported by OpenScape UC
Application V7. Using migration and upgrade you can bring V3 R2 Integrated
Duplex to V7 Small Deployment (see Table 121).
Source version 1 2 of the OpenScape UC
Application to be upgraded or migrated
Upgrade/migration target: OS UC Application V7 R1

Integrated
Deployment
with OSV
V7 R0
Small
Deployment
with OSV V6 or
V7 R0
Large
Deployment
with OSV V6 or
V7 R0
Very Large
Deployment
with OSV V6 or
V7 R0

34
Integrated Duplex
34
+
sm. --> la.
34
+
sm. --> la. +
la. --> v. la.

Integrated Duplex
34
34
+
sm. --> la.
34
+
sm. --> la. +
la. --> v. la.
34
34+
sm. --> la.
34+
sm. --> la. +
la. --> v. la.
OS UC Appl. V3 R2 with
OSV V3.1 R3 or V4 R1
Integrated Duplex
OS UC Application V3 R2 with OSV V5 R0

4
Integrated Duplex
+
sm. --> la.
+
sm. --> la. +
la. --> v. la.
OS UC Application V6 R0, V7 R0 or V7 R1
Integrated Duplex5
Table 121
Upgrade and Migration Table for Integrated Duplex

2 In this table, the source version is always Integrated Duplex which does not support a connection to HiPath 4000. Therefore, only
connections to an OpenScape Voice are mentionned in this table.
3 First, upgrade to the latest OS UC Application V3 R2 (see the installation and upgrade guide of the OS UC Application V3 R2) and upgrade
the OSV to V4 R1 or V5 R0 (see the installation and upgrade guide of the OSV).
4 For OS UC Application:
Create the export.tar file from the OS UC Application V3 R2/OSV V4 R1 (see OSV documentation). Then migrate to OS UC Application
V3 R2 Small Deployment (see the installation and upgrade guide of the OS UC Application V3 R2). Then upgrade the OS UC Application
from V3 R2 to V7 (see Section 15.6.1, Upgrading Small Deployment, on page 750)
For OSV:
Create the export.tar file from the OS UC Application V3 R2/OSV V4 R1 (see the OSV documentation). Install the latest OSV V6 or
V7 Standard Duplex and execute the OSV migration using the toolkit (see OSV documentation).
5 Integrated Duplex is supported neither for OpenScape UC Application V6 R0 nor for V7.
A31003-S5070-J100-12-7631, 02/2013
747
Legend
Description
Meaning
No upgrade, since it is the same version1 and the same deployment

scenario2.
Upgrading or migrating from the source version1 to the target version is
not possible at all or only via an intermediate version of OpenScape UC
Application.
If such a detour via an intermediate version is possible, it is outlined by
footers.
Direct upgrade is supported.
Imaging
Upgrade using imaging for the deployment scenario Integrated

Deployment to a new version of the OpenScape UC Application without
changing the deployment scenario Please obtain details from the
OpenScape Voice documentation.
Several actions are performed in succession.
sim. --> sm.
Change of the deployment scenario from Integrated Deployment to

Small Deployment described in Section 15.14, Migration from V7
Integrated Deployment to V7 Small Deployment, on page 887.
sm. --> la.
Change of the deployment scenario from Small Deployment to Large

Deployment described in Section 15.15, Migration from V7 Small
Deployment to V7 Large Deployment, on page 899.
sm. --> v. la.
This change of the deployment scenario has not been released yet.
la. --> v. la.
Change of the deployment scenario from Large Deployment to Very

Large Deployment described in Section 15.17, Migration from V7 Large
Deployment to V7 Very Large Deployment, on page 916.
Table 122
Key for the Upgrade and Migration Table
1 See Section 15.1, Determining the Source Version, on page 662

2 See Section 2.1, Deployment Scenarios, on page 25.
IMPORTANT: For OpenScape UC Application V3 R2, a connection to Netviewer

is supported project-specifically. For V6 R0 and later versions this connection is
not supported anymore. Execute the following command to uninstall the corresponding RPM package (see step 7 on page 751 or step 2 on page 773):
rpm -e scs_osc_netviewer_be
748
A31003-S5070-J100-12-7631, 02/2013
Upgrading V3 R2 or V6 R0 Integrated Deployment
15.5 Upgrading V3 R2 or V6 R0 Integrated Deployment

For Integrated Deployment, you can only upgrade from OpenScape UC
Application V3 R2 or V6 R0 to OpenScape UC Application V7 Integrated
Deployment. You can only upgrade to a connection to OpenScape Voice V6 or
V7. This is described in the OpenScape Voice documentation.
15.6 Upgrading V3 R2 or V6 R0 Small and Large Deployment

You can upgrade from OpenScape UC Application V3 R2 or V6 R0 only. If you
want to upgrade an earlier version to V7, upgrade to V3 R2 first. If you want to
upgrade V4 R0 to V7, upgrade to V6 R0 first.
IMPORTANT: SLES 10 and SLES 11 SP0 are not supported. Verify that the
OpenScape UC Application on SLES 11 SP1 or SP2 operates with 64 bit before
you upgrade it to V7 (see point 1 on page 116, step 1 on page 665 and Section
15.18, Upgrading a 32-bit System to a 64-bit System, on page 937). SP2 is
recommended.
Use the following command for determining the deployed SLES version:
VERSION = 11
PATCHLEVEL = 2
A31003-S5070-J100-12-7631, 02/2013
749
Upgrading V3 R2 or V6 R0 Small and Large Deployment
15.6.1 Upgrading Small Deployment

Only the application computer is involved in the upgrade.
IMPORTANT: You can upgrade the OpenScape UC Application on the application computer to V7 R1 but leave the clients in their old version. However,
software problems that may result from differing versions are not patched, which
restricts the support that can be provided in this situation. Upgrading the clients
is recommended in this case.
Preparation
Preparations, on page 665 were carried out. When upgrading V3 R2 to V7
make sure that in particular the instructions given in Section 15.2.3,
Database Check, on page 699 are carried out.
6. If you upgrade from OpenScape UC Application V3 R2, determine by
executing the following commands whether Loquendo is running:
/etc/init.d/LoquendoManagementContextd status
/etc/init.d/LoquendoTrapManagerd status
If this is the case, stop Loquendo:
/etc/init.d/LoquendoManagementContextd stop
/etc/init.d/LoquendoTrapManagerd stop
750
A31003-S5070-J100-12-7631, 02/2013
7. For OpenScape UC Application V3 R2, a connection to Netviewer is

supported project-specifically. For V7, this connection is not supported any
more. Execute the following command to uninstall the corresponding RPM
package:
Upgrade
8. Use the following command to find out which voice conference languages are
installed and note them down to reinstall them after the upgrade:
zypper se -i --match-any scs_conferencing_languagepack
S | Name
| Summary
| Type
--+--------------+------------------------------------------------------------+-------...
...
ISO setup files as repository in osc-setup and to upgrade osc-setup if
required.
10. Perform the upgrade:
osc-setup dup
Upgrading is performed fully automatically and overrides configuration files.
However, except for the E/A Cockpit configuration files, such configuration
files are previously backed up automatically so that there is no need to back
them up manually before the upgrade.
11. If the OpenScape UC Application you had upgraded had been connected via
an OpenScape Voice to a HiPath 4000 (see Section 6.4.1, Connection of an
OS UC Appl. via an OSV to a HiPath 4000, on page 484), execute the
following command:
Some configuration steps that are needed in this situation as well will be done
later (see step 29 on page 761).
12. Restore the E/A Cockpit configuration files that may have been backed
manually.
A31003-S5070-J100-12-7631, 02/2013
751
American English. If you want to add further packages of other languages,
execute the following sub-steps.
a) Verify that the installation files (ISO files) you require for the languages
you wish to install are registered in osc-setup.
available ISO files. Section 15.2.2, Providing the Update/Upgrade
Sources in a Repository in osc-setup, on page 671 contains information
about the steps required for providing an ISO file in osc-setup.
b) Installing additional TTS languages
TTS or ASR, the media server must be available under an IPv4 address
and at least one IPv4 streaming route must have been configured in the
media server. You can obtain details from the administrator documentation OpenScape UC Application Configuration and Administration.
Nuance TTS:
Example:
The following languages are supported:
Language
Chinese (Mandarin)
German
English
English
French
Italian
Portuguese (Brazil)
Russian
Country
China
Germany
Great Britain
USA
France
Italy
Portugal
Brazil
Russia
Language Code
zh_cn
de_de
en_gb
en_us
fr_fr
it_it
pt_pt
pt_br
ru_ru2
Spanish
Spain
es_es
Table 123
ISO File1
Chinese
German
English
English
French
Italian
Portuguese
Portuguese
AdditionalLan
guages
Spanish
JMailService/JMailService.cfg is seet to the value iso-8859-5.
752
A31003-S5070-J100-12-7631, 02/2013

Example:
Install all required audio conference languages that were installed before the
upgrade (see step 8 on page 751):
NOTE: If you do not execute this step now but after the first start of the
upgraded OpenScape UC Application, you need to reconfigure the address
bindings of the voice conference languages also.
language:
Example:
15. This step only needs to be executed if the OpenScape UC Application was
connected to Lotus Domino before upgrading.
During the upgrade the following groupware-related packages were
upgraded or installed:
scs_gwbeshared
scs_groupware
scs_gwbeexch
Perform the following actions:

a) Make sure that the Domino Groupware server is running.
b) Upgrade the connection to Lotus Domino:
The old configuration of the connection to Lotus Domino is applied
automatically with this command.
16. If you upgrade from the OpenScape UC Application V3 R2, the Solid DB is
implicitly migrated from the resource management database model to the
device management database model (compare Section 15.2.3, Database
Check, on page 699).
This migration is logged in the following file:
A31003-S5070-J100-12-7631, 02/2013
753
/var/siemens/common/log/install/scs_domain_be-resourcesDBmigration.log
Example report file:

Migrating from resourcemanagement to devicemanagement on
database schema 2.5.0.
MIGRATING RESOURCE GROUPS:
__________________________________________________
Migrate communication systems (resource group type 1)
Found 356
ERRORS exist. Only 13 was migrated
Migrated: 13
id: SwitchH4K, Type: HiPath4000
id: SwitchH4KV6, Type: HiPath4000
id: SwitchH8KV40V, Type: HiPath8000
id: my2Mediaserver
id: myMediaserver
id: SwitchH4KV6_-171
...
In this migration the following CSV file is created containing data the migration
of which has failed.
/var/siemens/common/log/resourcesDBmigration-notMigratedElements.csv
IMPORTANT: The CSV file cannot state whether one of the following
resource groups or resources have not been migrated:
- Media server
- Communication system (without CSType)
- Phone (not connected to an OpenScape Voice or HiPath 4000)
- Voice portal
- Conference
- Call queue
See step 7 on page 701 for a complete list of all resource groups and
resources.
754
A31003-S5070-J100-12-7631, 02/2013
The sections indicated with <<...>> were empty or faulty and must be
corrected.
Example:
##DPPublic;id;domain;internationalPrefix;internationalExitCode;nationalPrefix;nationalExi
tCode;subscriberPrefix;subscriberExitCode;switchId
DPPublic;1248723;system;011;8;1;8;;;<<
XXXXX
switchId
>>
DPPublic;14104536;system;011;8;1;8;;;<<
XXXXX
switchId
>>
The corresponding entries in the report file read as follows:
id: 1248723 [ERROR] Missing CommunicationSystem
Using the CMP the changed CSV file is imported in the Solid DB to keep the
data stored in the Solid DB to date. To do this, select in the CMP
Maintenance > Import & Export > Import. You find detailed information on
the import of CSV files e. g. in the Importing User Assignments section of the
OpenScape UC Application Configuration and Administration administrator
documentation.
17. If the OpenScape UC Application is connected to OpenScape Xpressions,
enter the following command:
You can install optional components retrospectively, analog to the following
OpenBranch Assistant example.
A31003-S5070-J100-12-7631, 02/2013
755
OpenBranch Assistant
The OpenBranch Assistant is an optional component of the OpenScape Voice V4
R1. Since this component does not exist in the OpenScape Voice V3.1 R3, it is
not automatically installed with an upgrade.
Execute steps 18 to 27 on the application computer.
applications:
zypper se --match-any clm office OpenBranch
S | Name
| Summary
| Type
--+-------------------------------+--------------------------------+-------| CLM
| package
| package
following command:
If you want to install the CLM, for example, enter the following command:
osc-setup in CLM
If you want to install the Office Communicator Connector, for example, enter
756
A31003-S5070-J100-12-7631, 02/2013
Hotfix
If not stated otherwise, install the lastest hotfix by executing step 20 on page 757
up to step 23 on page 758.
as follows:
ls /dev/sd*
Example output:
ls /dev/sd*
Example output:
mkdir /media
Sample:
A31003-S5070-J100-12-7631, 02/2013
757
osc-setup up
758
A31003-S5070-J100-12-7631, 02/2013

24. Execute the following sub-steps if you do not wish to upgrade an RPM
package of the OpenScape UC Application anymore.
Example output:
checking Arguments
Option clean: yes
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Example:
rm -R /tmp/tmpRepo
25. If the latest hotfix has been installed by using a USB stick (see step 20 on
page 757 up to step 23 on page 758), unmount the USB stick:
umount /media
A31003-S5070-J100-12-7631, 02/2013
759
Backup
26. Execute the instructions in Section 4.5, Configuring the File System Backup,
on page 181.
760
A31003-S5070-J100-12-7631, 02/2013
Start and configuration

28. Start the OpenScape UC Application when the upgrade process is finished by
an OpenScape Voice to a HiPath 4000, you have installed the
OpenScapUC_4kaddons RPM after the upgrade (see step 11 on page 751).
Configure a CSTA connection to the HiPath 4000 system on the OpenScape
UC Application side according to section Connecting a HiPath-4000 System
in the administrator documentation OpenScape UC Application Configuration
and Administration.
export tasks to be executed before the upgrade, you need to recreate them
upgrade.
A31003-S5070-J100-12-7631, 02/2013
761
31. If you have upgraded to the OpenScape UC Application V7 and connected

the OpenScape UC Application to an OpenScape Voice, the following
applies:
762

inactive.

A31003-S5070-J100-12-7631, 02/2013
32. IMPORTANT: Follow the instructions in section Configuring the Address

Translation Context in the administrator documentation OpenScape UC
34. Configuration for transfer conferences (Merge Calls)
NOTE: This step applies in case of the OpenScape UC Application being
connected to an OpenScape Voice only.
You can obtain details from section Configuring Transfer Conferences of the
Administration.
NOTE: You can execute this step before or after an upgrade. The CMP must
be operable at this time.
A31003-S5070-J100-12-7631, 02/2013
763
a) Open in the CMP Configuration > Unified Communications >

Configuration > Media Server.
b) Click on a media server entry.
c) Click on the Address Binding tab.
764
A31003-S5070-J100-12-7631, 02/2013
d) In the TerminalID column, click on the entry that displays value

LocalParkSlot in the Address column.
e) Verify that either the Single number or Number range radio button is
active.
The Regular expression radio button is displayed but in inactive state.
f)
If required, enter an appropriate value in the Address-expression field.
g) Save the changed settings.

h) Execute steps b on page 76434 to g on page 76534 for all further possibly
available media servers.
35. Phone number clashes for voice conference languages
You have installed voice conference languages in step 14 on page 753. This
automatically configures address bindings for such languages. Execute the
following sub-steps to see the address bindings:
A31003-S5070-J100-12-7631, 02/2013
765

766
A31003-S5070-J100-12-7631, 02/2013
The following voice conference languages can be displayed:

Display in the CMP
Meaning
Address
Terminal ID
933
conferencing-meetnow
980
conferencing-gb
English (UK)
981
conferencing-de
German
982
conferencing-fr
French
983
conferencing-us
English (US)
984
conferencing-it
Italian
985
conferencing-es
Spanish
986
conferencing-pt
Portuguese
987
conferencing-br
Brazilian
988
conferencing-ru
Russian
989
conferencing-nl
Dutch
990
conferencing-tr
Turkish
991
conferencing-cn
Chinese
998
conferencing-default
Table 124
Address Bindings of the Audio Conference Languages for Small

Deployment
The Address column shows the phone numbers of the address bindings. If
you have installed at least one voice conference language, phone number
933 is used for conferencing-meetnow and 998 for conferencing-default. In
addition, values according to the above table are used for the phone numbers
of the installed languages by default.
A31003-S5070-J100-12-7631, 02/2013
767
If these phone numbers are already used for other purposes, the phone
numbers of these languages must be reconfigured to other phone numbers.
To do this, click on the small triangle to the right of the corresponding
language entry, select Edit..., enter the new phone number in the Addressexpression field and click on Save.
36. Follow the instructions in section How to map Symphonia permissions to
CMP permissions for Upgrades to v6 in the administrator documentation
OpenScape Common Management Portal V6 Administration.
37. IMPORTANT: If the OpenScape UC Application shall be connected to an
OpenScape Voice V7 after the upgrade, be sure to click on the Refresh
Switch Data button in the CMP under Configuration > OpenScape Voice
after the upgrade. When you then open Configuration > Unified
Communication > Configuration > Connections > OS Voice, click on the
small triangle to the right of the connection entry and select Edit..., the
Version field displays the correct version of the OpenScape Voice.
38. There are the following OpenScape Fusion clients, for example:
OpenScape Fusion V1 for IBM Lotus Notes
OpenScape Fusion V1 for Microsoft Outlook
OpenScape Fusion V1 for Microsoft Lync
If an OpenScape UC Application V6 R0 connected to one of these clients has

been upgraded to V7, execute the following sub-steps:
a) In the CMP, click under Maintenance > Inventory > Nodes &
b) Enter value Presence Service in the Filter field and click on Go.
c) Click on the PresenceService entry. A dialog for the presence service
opens.
d) Set the Eventing Backwards Compatible to value true.
39. Application Builder
If you upgrade from V6 R0 to V7 and have deleted the applications created
with the Application Builder of the OpenScape UC Application V6 R0 in step
3 on page 666, you need to execute the following sub-steps:
a) Provide the file OpenScapeUcSuiteApps-OptionalPackage<Version>.iso on the computer on which the Application Builder for
OpenScape UC Application V6 R0 was installed (this is not the
application computer!) (see Table 117 on page 672). To do this you can
768
A31003-S5070-J100-12-7631, 02/2013
use VirtualCloneDrive for example.

b) Copy the file WIN32\APPLICAT.ZIP from this ISO file to the computer
and unpack it. This results in the application_builder_setup.exe
file.
c) Start this file and install the Application Builder.
d) Start the Application Builder and load the old workspace in this process.
e) Provide the applications you wish to use anew by following the
instructions in the operating guide OpenScape UC Application V7,
Application Builder, section Providing an Application.
f)
Load these applications in the media server by following the instructions

in the administrator documentation OpenScape Media Server V7, section
Importing an Application.
40. You need not upgrade the Web Collaboration server.

41. If the OpenScape UC Application is connected to an Openfire server and the
OpenScape UC Application as well as the Openfire server were upgraded,
you need to execute the following steps:
Presence & IM.
b) Click on the Save button.
c) Click on the Start Openfire Admin UI button.
d) Log on to the Openfire server.
NOTE: The default values are as follows:
- User name: admin, Password: 01*Test!
- User name: administrator, Password: 8ABWnmppzEOuxu1q
e) Open Server Settings > Connection Manager.
f)
Select Enabled.
g) Enter pass as password.

h) Enter 5262 as port if this has not been done automatically.
i)
Click on the Save button.
42. If you have upgraded from OpenScape UC Application V3 R2, consider that
the OpenScape UC Application users perhaps had no instant-messaging
address before the upgrade but they must have one after the upgrade.
This does not mean that an instant-messaging server must be installed. The
instant-messaging address of a user might be a dummy address.
A31003-S5070-J100-12-7631, 02/2013
769
You set the instant-messaging address of a user in the CMP at

Configuration > Unified Communications > Accounts > List > <user
name> > Contact Information or User Management > Administration >
Users & Resources > <user name> > Contact.
As an alternative to this step, e. g. if you must change a large number of

users, you can use the import feature of the CMP at Maintenance > Import
& Export > Import. If you use this feature, ensure that only the modified
contact data is imported but not the user data containing e. g. passwords and
PINs.
You find detailed information on the import of CSV files e. g. in the Importing
User Assignments section of the OpenScape UC Application Configuration
and Administration administrator documentation.
43. If required or desired, upgrade the PBX on the PBX's computers (see, for
example, the setup guide OpenScape Voice Installation and Upgrades).
770
A31003-S5070-J100-12-7631, 02/2013
15.6.2 Upgrading Large Deployment

The following computers are involved in the upgrade:
This is the computer on which the OpenScape backend services of the
OpenScape UC Application are to be installed.
Frontend computer
This is the computer on which a web server (Tomcat, among other things) is
to be installed.

This is the computer on which a media server is to be installed.
We divide upgrading Large Deployment into the below major steps, detailing
them further down the text:
Stopping all server components of the OpenScape UC Application on all

computers etc.)
Upgrading OpenScape UC Application on the application computer
Starting OpenScape UC Application on the application computer
Upgrading the frontend servers on all frontend computers
Upgrading the media servers on all media server computers
Starting the frontend servers on all frontend computers and the media servers
on all media server computers
If required or desired, upgrade the PBX on the PBX's computers (see the
installation guide OpenScape Voice Installation and Upgrades.
IMPORTANT: The upgrade on the application computer must be performed

before the upgrade on the frontend computer and media server computer. You
can upgrade the frontend and media server computers in parallel.
A31003-S5070-J100-12-7631, 02/2013
771
IMPORTANT: You can upgrade the OpenScape UC Application on the application computer, the frontend computers, the media server computers etc. to
V7 R1 but leave the clients in their old version. However, software problems that
may result from differing versions are not patched, which restricts the support that
can be provided in this situation. Upgrading the clients is recommended in this
case.

772
A31003-S5070-J100-12-7631, 02/2013
15.6.2.1 Upgrading on the Application Computer

IMPORTANT: First, execute the steps described here for upgrading the application computer. Then perform the upgrade on the frontend or media server
computer.
Preparations, on page 665 were carried out. When upgrading V3 R2 to V7
make sure that in particular the instructions given in Section 15.2.3,
Database Check, on page 699 are carried out.
2. For OpenScape UC Application V3 R2, a connection to Netviewer is
supported project-specifically. For V6 R0 and later versions this connection is
not supported anymore. Execute the following command to uninstall the
corresponding RPM package:
3. Log on to the application computer, the frontend computers and the media
server computers with the user name root.
required.
6. Stop the server components of the OpenScape UC Application on the
frontend and media server computers:
NOTE: You can execute these commands on different computers at the
same time.
On the frontend computers:

NOTE: /etc/init.d/symphoniad stop WebClient_FE is not
sufficient.
On the media server computers:

A31003-S5070-J100-12-7631, 02/2013
773
Stop the MRCP service, the Nuance TTS and the Nuance ASR, if
available:
osc-setup dup
The upgrade process is fully automatic and since no configuration files are
overridden you need not back up these files before the upgrade.
an OpenScape Voice to a HiPath 4000 (see Section 6.4.1, Connection of an
OS UC Appl. via an OSV to a HiPath 4000, on page 484), execute the
following command:
Some configuration steps that are needed in this situation as well will be done
later (see step 31 on page 793).
10. This step only needs to be executed if the OpenScape UC Application was
connected to Lotus Domino before upgrading.
During the upgrade in step 3, the following groupware-related packages were
upgraded or installed:
scs_gwbeshared
scs_groupware
scs_gwbeexch
Perform the following actions:

a) Make sure that the Domino Groupware server is running.
b) Upgrade the connection to Lotus Domino:
The old configuration of the connection to Lotus Domino is applied
automatically with this command.
11. During the upgrade, the Solid DB is migrated implicitly from the resource
management database model to the device management database model
(compare Section 15.2.3, Database Check, on page 699).
This migration is logged in the following file:
/var/siemens/common/log/install/scs_domain_be-resourcesDBmigration.log
774
A31003-S5070-J100-12-7631, 02/2013
Example report file:

Migrating from resourcemanagement to devicemanagement on
database schema 2.5.0.
MIGRATING RESOURCE GROUPS:
__________________________________________________
Migrate communication systems (resource group type 1)
Found 356
ERRORS exist. Only 13 was migrated
Migrated: 13
id: my2Mediaserver
id: myMediaserver
...
In this migration the following CSV file is created containing data the migration
of which has failed.
/var/siemens/common/log/resourcesDBmigration-notMigratedElements.csv
IMPORTANT: The CSV file cannot state whether one of the following
resource groups or resources have not been migrated:
- media server
- communication system (without CSType)
- phone (not connected to an OpenScape Voice or HiPath 4000)
- voice portal
- conference
- call queue
See step 7 on page 701 for a complete list of all resource groups and
resources.
The sections indicated with <<...>> were empty or faulty and must be
corrected.
A31003-S5070-J100-12-7631, 02/2013
775
Example:
##DPPublic;id;domain;internationalPrefix;internationalExitCode;nationalPrefix;nationalExi
tCode;subscriberPrefix;subscriberExitCode;switchId
DPPublic;1248723;system;011;8;1;8;;;<<
XXXXX
switchId
>>
DPPublic;14104536;system;011;8;1;8;;;<<
XXXXX
switchId
>>
The corresponding entries in the report file read as follows:
Using the CMP the changed CSV file is imported in the Solid DB to keep the
data stored in the Solid DB to date. To do this, select in the CMP
Maintenance > Import & Export > Import. You find detailed information on
the import of CSV files e. g. in the Importing User Assignments section of the
OpenScape UC Application Configuration and Administration administrator
documentation.
12. If the OpenScape UC Application is connected to OpenScape Xpressions,
enter the following command:
You can install optional components retrospectively, analog to the following
OpenBranch Assistant example.
OpenBranch Assistant
The OpenBranch Assistant is an optional component of the OpenScape Voice V4
R1. Since this component does not exist in the OpenScape Voice V3.1 R3, it is
not automatically installed with an upgrade.
Execute steps 13 on page 776 to 23 on page 781 on the application computer.
applications:
zypper se --match-any clm office OpenBranch
S | Name
| Summary
| Type
--+-------------------------------+--------------------------------+-------| CLM
| package
| package
776
A31003-S5070-J100-12-7631, 02/2013
following command:
If you want to install the CLM, for example, enter the following command:
osc-setup in CLM
If you want to install the Office Communicator Connector, for example, enter
A31003-S5070-J100-12-7631, 02/2013
777
Hotfix
If not stated otherwise, install the lastest hotfix by executing step 15 on page 778
up to step 18 on page 779.
as follows:
ls /dev/sd*
Example output:
ls /dev/sd*
Example output:
mkdir /media
Sample:
778
A31003-S5070-J100-12-7631, 02/2013
osc-setup up
A31003-S5070-J100-12-7631, 02/2013
779

19. Execute the following sub-steps if you do not wish to upgrade an RPM
package of the OpenScape UC Application anymore.
Example output:
checking Arguments
Option clean: yes
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Example:
rm -R /tmp/tmpRepo
20. If the latest hotfix has been installed by using a USB stick (step 15 on page
778 up to step 18 on page 779), unmount the USB stick:
umount /media
780
A31003-S5070-J100-12-7631, 02/2013
Backup
21. Execute the instructions in Section 4.5, Configuring the File System Backup,
on page 181 except step 8 on page 183 and step 9 on page 183.
Start
22. Start the OpenScape UC Application when the upgrade process is finished by
A31003-S5070-J100-12-7631, 02/2013
781
15.6.2.2 Upgrading on the Frontend Computer

IMPORTANT: You can upgrade the frontend and media server computers in
parallel.
1. Verify that the OpenScape UC Application has been upgraded on the
have been stopped on all other computers (for example media server
computer).
3. Please wait for about 5 minutes before you start upgrading on the frontend
backend services.
required.
6. Execute the following command to stop a probably still operating frontend
server:
osc-setup dup
8. The upgrade process is fully automatic and since no configuration files are
overridden you need not back up these files before the upgrade. Exception:
Restore the E/A Cockpit configuration files that may have been backed up.
9. If not stated otherwise, install the lastest hotfix by executing step 9 on page
782 up to step 12 on page 783.If the ISO file is present on a DVD and not on
the computer, mount the DVD:
as follows:
782
A31003-S5070-J100-12-7631, 02/2013

ls /dev/sd*
Example output:
ls /dev/sd*
Example output:
mkdir /media
Sample:
osc-setup up
A31003-S5070-J100-12-7631, 02/2013
783

Example output:
checking Arguments
Option clean: yes
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Example:
rm -R /tmp/tmpRepo
c) If the latest hotfix has been installed by using a USB stick (step 9 on page
umount /media
cat /etc/sudoers
784
A31003-S5070-J100-12-7631, 02/2013

rpm -qa |grep dump
Example output:
dump-0.4b41-14.2
command:
yast -i dump
the network).
19. Execute the steps described in this section so far for all frontend computers.
20. Do not reboot the frontend servers yet.
A31003-S5070-J100-12-7631, 02/2013
785
15.6.2.3 Upgrading on the Media Server Computer

IMPORTANT: You can upgrade the frontend and media server computers in
parallel.
1. Verify that the OpenScape UC Application has been upgraded on the
have been stopped on all other computers (for example frontend computer).
3. Please wait for about 5 minutes before you start upgrading on the media
server computer. You should be able to log on to the CMP of the OpenScape
backend services.
required.
6. Execute the following command to stop a probably still operating media
server:
8. If you upgrade from OpenScape UC Application V3 R2, determine by
executing the following commands whether Loquendo is running:
/etc/init.d/LoquendoManagementContextd status
/etc/init.d/LoquendoTrapManagerd status
If this is the case, stop Loquendo:
/etc/init.d/LoquendoManagementContextd stop
/etc/init.d/LoquendoTrapManagerd stop
9. Use the following command to find out which voice conference languages are
installed and note them down to reinstall them after the upgrade:
zypper se -i --match-any scs_conferencing_languagepack
786
A31003-S5070-J100-12-7631, 02/2013

S | Name
| Summary
| Type
--+--------------+--------------------------------------------------------------+-------...
...
osc-setup dup
The upgrade process is fully automatic and since no configuration files are
overridden you need not back up these files before the upgrade.
the steps 9 on page 299 and 15 on page 307.
a) Verify that the installation files (ISO files) you require for languages you
wish to install are provided in osc-setup.
available ISO files. Section 15.2.2, Providing the Update/Upgrade
Sources in a Repository in osc-setup, on page 671 contains information
about the steps required for registering an ISO file in osc-setup.
b) Installing additional TTS languages
TTS or ASR, the media server must be available under an IPv4 address
and at least one IPv4 streaming route must have been configured in the
media server. You can obtain details from the administrator documentation OpenScape UC Application Configuration and Administration.
Nuance TTS:
Example:
The following languages are supported:
A31003-S5070-J100-12-7631, 02/2013
787
Language
Chinese (Mandarin)
German
English
English
French
Italian
Portuguese (Brazil)
Russian
Country
China
Germany
Great Britain
USA
France
Italy
Portugal
Brazil
Russia
Language Code
zh_cn
de_de
en_gb
en_us
fr_fr
it_it
pt_pt
pt_br
ru_ru2
Spanish
Spain
es_es
Table 125
ISO File1
Chinese
German
English
English
French
Italian
Portuguese
Portuguese
AdditionalLan
guages
Spanish

Example:
12. Install all required voice conference languages that were installed before the
upgrade (see step 9 on page 786):
Example:
osc-setup in scs_conferencing_languagepack_en_us
upgraded OpenScape UC Application, you need to reconfigure the address
13. If not stated otherwise, install the lastest hotfix by executing step 13 on page
788 up to step 16 on page 790.If the ISO file is present on a DVD and not on
the computer, mount the DVD:
788
A31003-S5070-J100-12-7631, 02/2013
as follows:
ls /dev/sd*
Example output:
ls /dev/sd*
Example output:
mkdir /media
Sample:
A31003-S5070-J100-12-7631, 02/2013
789
osc-setup up
Example output:
checking Arguments
Option clean: yes
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Example:
rm -R /tmp/tmpRepo
790
A31003-S5070-J100-12-7631, 02/2013
18. If the latest hotfix has been installed by using a USB stick (step 13 on page
umount /media
Backup
cat /etc/sudoers
rpm -qa |grep dump
Example output:
dump-0.4b41-14.2
command:
yast -i dump
the network).
24. Execute the steps described in this section so far for all media server
computers.
Reboot
25. Start all frontend servers by executing the following command on all frontend
computers:
A31003-S5070-J100-12-7631, 02/2013
791
26. Start the MRCP service on all media server computers, the Nuance TTS and
the Nuance ASR:
27. Start all media servers by executing the following command on all media
server computers:
Configuration
28. IMPORTANT: If the OpenScape UC Application shall be connected to an
OpenScape Voice V7 after the upgrade, be sure to click on the Refresh
Switch Data button in the CMP under Configuration > OpenScape Voice
after the upgrade. When you then open Configuration > Unified
Communication > Configuration > Connections > OS Voice, click on the
small triangle to the right of the connection entry and select Edit..., the
Version field displays the correct version of the OpenScape Voice.
29. There are the following OpenScape Fusion clients, for example:
OpenScape Fusion V1 for IBM Lotus Notes
OpenScape Fusion V1 for Microsoft Outlook
OpenScape Fusion V1 for Microsoft Lync
If an OpenScape UC Application V6 R0 connected to one of these clients has

been upgraded to V7, execute the following sub-steps:
a) In the CMP, click under Maintenance > Inventory > Nodes &
b) Enter value Presence Service in the Filter field and click on Go.
c) Click on the PresenceService entry. A dialog for the presence service
opens.
d) Set the Eventing Backwards Compatible to value true.
30. If you noticed that there were scheduled backup or export tasks to be
executed before the upgrade, you need to recreate them now (see the
administrator documentation OpenScape Common Management Platform),
because backup unit names may get lost during an upgrade.
792
A31003-S5070-J100-12-7631, 02/2013
31. If the OpenScape UC Application you had upgraded had been connected to
an OpenScape Voice with HiPath 4000 media presence functionality, you
have installed the OpenScapUC_4kaddons RPM after the upgrade (see step
9 on page 774).
Configure a CSTA connection to the HiPath 4000 system on the OpenScape
UC Application side according to section Connecting a HiPath-4000 System
in the administrator documentation OpenScape UC Application Configuration
and Administration.
32. If you have upgraded to the OpenScape UC Application V7 and connected
the OpenScape UC Application to an OpenScape Voice, the following
applies:

inactive.
A31003-S5070-J100-12-7631, 02/2013
793

33. IMPORTANT: Follow the instructions in section Configuring the Address

Translation Context in the administrator documentation OpenScape UC
794
A31003-S5070-J100-12-7631, 02/2013
34. Configuration for transfer conferences (Merge Calls)

NOTE: This step applies in case of the OpenScape UC Application being
connected to an OpenScape Voice only.
You can obtain details from section Configuring Transfer Conferences of the
Administration.
NOTE: You can execute this step before or after an upgrade. The CMP must
be operable at this time.
A31003-S5070-J100-12-7631, 02/2013
795
d) In the TerminalID column, click on the entry that displays value

LocalParkSlot in the Address column.
796
A31003-S5070-J100-12-7631, 02/2013
e) Verify that either the Single number or Number range radio button is
active.
The Regular expression radio button is displayed but in inactive state.
f)
If required, enter an appropriate value in the Address-expression field.
g) Save the changed settings.

h) Execute steps 34b on page 795 to 34g on page 797 for all further possibly
available media servers.
35. Follow the instructions in section How to map Symphonia permissions to
CMP permissions for Upgrades to v6 in the administrator documentation
OpenScape Common Management Portal V6 Administration.
36. Application Builder
If you upgrade from V6 R0 to V7 and have deleted the applications created
with the Application Builder of the OpenScape UC Application V6 R0 in step
3 on page 666, you need to execute the following sub-steps:
a) Provide the file OpenScapeUcSuiteApps-OptionalPackage<Version>.iso on the computer on which the Application Builder for
OpenScape UC Application V6 R0 was installed (this is not the
application computer!) (see Table 117 on page 672). To do this you can
use VirtualCloneDrive for example.
b) Copy the file WIN32\APPLICAT.ZIP from this ISO file to the computer
and unpack it. This results in the application_builder_setup.exe
file.
c) Start this file and install the Application Builder.
d) Start the Application Builder and load the old workspace in this process.
e) Provide the applications you wish to use anew by following the
instructions in the operating guide OpenScape UC Application V7,
Application Builder, section Providing an Application.
f)
Load these applications in the media server by following the instructions

in the administrator documentation OpenScape Media Server V7, section
Importing an Application.
A31003-S5070-J100-12-7631, 02/2013
797

38. If the OpenScape UC Application is connected to an Openfire server and the
OpenScape UC Application as well as the Openfire server were upgraded,
you need to execute the following steps:
Presence & IM.
b) Click on the Save button.
c) Click on the Start Openfire Admin UI button.
d) Log on to the Openfire server.
NOTE: The default values are as follows:
- User name: admin, Password: 01*Test!
- User name: administrator, Password: 8ABWnmppzEOuxu1q
e) Open Server Settings > Connection Manager.
f)
Select Enabled.
g) Enter pass as password.

h) Enter 5262 as port if this has not been done automatically.
i)
798
A31003-S5070-J100-12-7631, 02/2013

PINs.
40. If required or desired, upgrade the PBX on the PBX's computers (see, for
example, the setup guide OpenScape Voice Installation and Upgrades).
A31003-S5070-J100-12-7631, 02/2013
799
15.6.3 Fallback after Abandoning the Upgrade

15.6.3.1 Falling back using syncUC
If you use a fallback solution by means of syncUC execute the following
command:
syncUC fallback
See Section 15.2.4.2, syncUC Commands, on page 707 for details.
15.6.3.2 Falling back through Restoration in the CMP

You wish to upgrade Small Deployment or Large Deployment to V7 and keep the
deployment scenario. If this upgrade is abandoned, you need to execute the
following steps to return to the previously installed version.
We assume that a backup by means of the CMP, a backup of the access
configuration to the CLM (Customer License Manager) and, if required, a backup
of the E/A Cockpit configuration files is available (see Section 15.2, Update and
Upgrade Preparations, on page 665).
Installing the operating system
1. Check the version of the installed operating system:
VERSION = 11
PATCHLEVEL = 1
Using the following command you can check whether the SLES setup
medium is available:
zypper lr
Example output:
# | Alias
| Name
| Enabled | Refresh
--+-------------------------------------------------+-----------------+---------+-------1 | SUSE-Linux-Enterprise-Server-11-SP2 11.2.2-1.234 | SUSE-Linux-Enterprise-Server-11-SP2
11.2.2-1.234 | Yes
| No
2. Consult the documentation of the previously installed version of the

OpenScape UC Application to find out which operating system is required.
800
A31003-S5070-J100-12-7631, 02/2013
a) Install the required operating system if it has not been set up yet.
b) If the required operating system has already been installed, uninstall the
OpenScape UC Application and all associated applications.
3. Execute the instructions given in the documentation of the corresponding
OpenScape UC Application version to set up the previously installed version
again.
Restoring using the CMP
4. Using the CMP, restore the data according to the administrator
documentation OpenScape UC Application Configuration and Administration,
section Backing up and restoring OpenScape System Components.
NOTE: A Container Configuration files warning during the restore process

does not pose any problem. The demanded actions WARN Pre/Post Action
and Please restart the container are performed after the data restore.
Restoring the CLM access configuration

5. Open the backed up file ClmSettings.xml with the CLM access
configuration.
6. Execute the following commands to create a new file /opt/licenses/
clm/ApacheTomcat/ClmSettings.xml and to update the database:
cd /opt/licenses/clm
bash remoteAccess.sh <IP address 1>,<IP address 2>,<IP address>,<IP address n>
<IP address 1>,<IP address 2>,<IP address >,<IP address
n> are here the IP addresses displayed in the ClmSettings.xml file in the
AllowedClients field.
IMPORTANT: All IP addresses listed in the AllowedClients field must be
restored.
Example:
A31003-S5070-J100-12-7631, 02/2013
801
bash remoteAccess.sh
10.235.200.113,10.235.200.28,10.235.65.221
IMPORTANT: Make sure no blanks are entered between the IP addresses.
The backed up file ClmSettings.xml was in a directory (/opt/
siemens/clm/ApacheTomcat/) different from the one that includes the
file ClmSettings.xml created here.
Restoring the E/A Cockpit configuration files
7. Restore the E/A Cockpit configuration files that may have been backed up.
Start
8. For the Small Deployment, execute the following command on the application
computer to start the MRCP service, the Nuance TTS and the Nuance ASR,
if available:
10. Wait several minutes before logging on to the CMP.
If you cannot log on, terminate the OpenScape UC Application, restart it, wait
several minutes and log on to the CMP.
802
A31003-S5070-J100-12-7631, 02/2013
Smooth Update/Upgrade of V3 R2, V6 R0 or V7 R0
15.7 Smooth Update/Upgrade of V3 R2, V6 R0 or V7 R0

15.7.1 Introduction
In the following we describe a method of bringing the OpenScape UC Application
to a target version where, compared to normal upgrades, the unavailability period
is reduced considerably but more time is spent on preparations and hardware
requirements are higher.
IMPORTANT: Smooth updating/upgrading is not supported for Integrated
Deployment.
IMPORTANT: Though we shall almost exclusively speak of a smooth upgrade in

the following, you can apply this method to a smooth update to a fix release or to
a smooth hotfix installation also. The steps for a smooth update to a fix release or
for a smooth hotfix installation are identical with the steps for a smooth upgrade
except for the actual update step (see Section 15.7.5, Upgrading SysUC1 to the
Target Version, on page 833).
In this documentation we describe the upgrade of an OpenScape UC Application
with an application computer (BE1), a frontend computer (FE1) and a media
server computer (MS1). We shall call this system SysUC1 in the following. A
smooth upgrade requires a double for each of these computers, thus a second
application computer (BE2), a second frontend computer (FE2) and a second
media server computer (MS2). We shall call this system SysUC2 in the following.
BE2 , FE2 and MS2 are empty computers without operating system at first.
Except for the IP addresses used, an exact copy of SysUC1 is installed on
SysUC2. SysUC2 serves as replacement for SysUC1 to provide an operable
substitute OpenScape UC Application while SysUC1 is being upgraded.
You can perform a smooth upgrade for virtual and real computers. You can also
perform it when a SAN is connected.
This documentation describes a smooth upgrade for Large Deployment and Very
Large Deployment. The procedure for Small Deployment is only different in so far
as the steps described for FE1, FE2, MS1 and MS2 need not be executed. In
addition, the instructions given in the corresponding analog sections must be
followed instead of those described in Section 15.7.5, Upgrading SysUC1 to the
Target Version, on page 833.
A31003-S5070-J100-12-7631, 02/2013
803

The upgrade is divided in the major steps listed in Table 126. In the sections that
follow we will describe these major steps in detail.
Major
step
Operation/Status
Initial status: SysUC1 is operable in the original OpenScape UC Application version. SysUC2 consists of empty
computers only.
Section 15.7.1.3, External and internal IP Addresses, on page 805

Section 15.7.3.1, Copying RPM from BE1 to BE2, on page 810
SysUC1 is operable in the original OpenScape UC Application version.
SysUC2 is not operable. Specific OpenScape UC Application directories and the RPM packages found on BE1 are
available on BE2.
Section 15.7.3.2, Copying the UC Database from BE1 to BE2, on page 817
Section 15.7.3.3, Copying from FE1 to FE2, on page 820
Section 15.7.3.4, Copying from MS1 to MS2, on page 825
SysUC2 is not operable. Specific OpenScape UC Application directories and the RPM packages found on BE1 are
available on BE2. Likewise, the same database (Solid DB or MySQL DB) that exists on BE1 is present on BE2.
Specific OpenScape UC Application directories and the RPM packages found on FE1 are available on FE2.
Specific OpenScape UC Application directories and the RPM packages found on MS1 are available on MS2.
Section 15.7.4, Switching from SysUC1 to SysUC2, on page 830

SysUC1 cannot be reached under the external IP addresses anymore. However, BE1, FE1 and MS1 can
communicate with each other via the internal IP addresses.
SysUC2 is now operable under the same (external) IP addresses and in the same original OpenScape UC
Application version as SysUC1 was previously, i. e. no difference can be noticed from outside. For example, the CMP
is now accessed for SysUC2 under the same (external) IP address as previously for SysUC1.
Section 15.7.5, Upgrading SysUC1 to the Target Version, on page 833

SysUC1 is now upgraded to the target version of the OpenScape UC Application but not operable yet, because the
internal IP addresses are still used.
Section 15.7.6, Switching from SysUC2 to SysUC1, on page 834

SysUC1 is now operable under the same (external) IP addresses as at the start of the smooth upgrade but has the
target version of the OpenScape UC Application.
SysUC2 is installed but not upgraded and not operable either because of the internal IP addresses used on the
computers.
Table 126
804
Major steps of a smooth upgrade
A31003-S5070-J100-12-7631, 02/2013
15.7.1.3 External and internal IP Addresses

The SysUC1 IP addresses must be used e. g. when the following software
accesses the OpenScape UC Application:
Access to the CMP from a web browser
Access of the ODC to the OpenScape UC Application
Access of the Web Client to the OpenScape UC Application
Configuration of the PBX to determine the IP address of the web conference

server
We shall call these IP addresses external IP addresses in the following.

These external IP addresses of SysUC1 will be disabled for the smooth upgrade
and replaced with other IP addresses. These other IP addresses are called
internal IP addresses.
The external IP addresses are assigned to BE2, FE2 and MS2 upon their
creation. SysUC2 thus takes on the function of SysUC1. With SysUC2 an
OpenScape UC Application is available that, seen from outside, provides the
same functionality under the same IP addresses as SysUC1 did previously.
Then, SysUC1 will be upgraded.
After the upgrade SysUC1 will lose the internal IP addresses and adopt the
external IP addresses, so that SysUC1 is available under the same IP addresses
as at the beginning of the smooth upgrade, but has the target version of the
IMPORTANT: The external IP addresses of BE1 and BE2 are identical. Parallel
to this, the external IP addresses of FE1 and FE2 are identical and the external
IP addresses of MS1 and MS2 are identical. Because of the IP addresses'
identity, we shall exclusively speak of external BE addresses, external FE
addresses and external MS addresses in the following.
Network boards with identical IP addresses must never be connected to the
network simultaneously.
NOTE: Instead of using one network board that, depending on the situation, you
assign an internal or external IP address on each computer, you can also use two
network boards per computer. One of them has then an internal IP address and
the other one the external IP address. However, only one network board may be
active per computer, the second network board must be disabled.
You disable a network board with the command ifdown <network board
name> and activate it with ifup <network board name>.
Examples:
ifdown eth0
A31003-S5070-J100-12-7631, 02/2013
805
ifup eth1
Using the command ifconfig you can check which network board is active and
which IP address has been assigned to this network board, as this command's
output contains active network boards only.
806
A31003-S5070-J100-12-7631, 02/2013
15.7.2 Preparing the FQDNs in the Response Files

If you use FQDNs instead of computer names (host names) or IP addresses on
BE1, FE1 and MS1 in the response file /opt/siemens/servicetools/
install/conf/responsefile.txt for the parameters
SI_PRIMARY_NODE_HOST, SI_LOCAL_HOST and SI_DB_HOST, continue with
Section 15.7.3, Copying from SysUC1 to SysUC2, on page 810. Otherwise,
continue with the instructions in this section.
15.7.2.1 Response File on the BE1

Execute the following steps on BE1:
2. Copy the response file.
cp /opt/siemens/servicetools/install/conf/responsefile.txt /root/knut.responsefile.txt
3. Open the copied file:

vi /root/knut.reponsefile.txt
4. Replace the values of the following parameters with the FQDN of the
application computer and save the file.
SI_LOCAL_HOST
SI_DB_HOST
5. Check the response file:

/opt/siemens/servicetools/install/bin/installib.sh reconfiguration.iponly
-Dresponse.file=/root/knut.responsefile.txt
In the event of success, the output ends as follows:

BUILD SUCCESSFUL
Total time: XX minutes YY seconds
INFO - Shutting down logging and log4j subsystem
8. Check the result in the file /opt/siemens/servicetools/install/
conf/responsefile.txt.
A31003-S5070-J100-12-7631, 02/2013
807
15.7.2.2 Response File on the FE1

Execute the following steps on FE1.

SI_DB_HOST
5. Replace the values of the following parameter with the FQDN of the frontend
computer.
SI_LOCAL_HOST
6. Save the file.


BUILD SUCCESSFUL
808
A31003-S5070-J100-12-7631, 02/2013
15.7.2.3 Response File on the MS1

Execute the following steps on MS1.

SI_DB_HOST
5. Replace the values of the following parameter with the FQDN of the media
server computer.
SI_LOCAL_HOST
6. Save the file.


BUILD SUCCESSFUL
A31003-S5070-J100-12-7631, 02/2013
809
15.7.3 Copying from SysUC1 to SysUC2

15.7.3.1 Copying RPM from BE1 to BE2
1. Initial status: BE1 is a computer with installed OpenScape UC Application,
BE2 is a computer without operating system.
2. Because the computers of the OpenScape UC Application will have different
IP addresses depending on the installation step, the file /etc/hosts must
be used on the application computer (BE1), the frontend computer (FE1) and
the media server computer (MS1) for resolving computer names (host
names), fully qualified domain names (FQDNs) and IP addresses.
<Ext. BE IP address>
<Ext. FE IP address>
<Ext. MS IP address>
<Ext. BE host name>

<Ext. FE host name>
<Ext. MS host name>
<Ext. BE FQDN>
<Ext. FE FQDN>
<Ext. MS FQDN>
Example:
10.1.10.1 BE BE.site
10.1.10.2 FE FE.site
10.1.10.3 MS MS.site
NOTE: The sequence of IP address, FQDN and computer name (host name)
in one line is of no significance.

3. Check whether the OpenScape UC Application on BE1, FE1, and MS1 is
operating by executing the following command on each of these computers:
If required, start the OpenScape UC Application on BE1, FE1 and MS1 by
executing the following command on the respective computer:
If required, start the MRCP service, the Nuance TTS and the Nuance ASR on
MS1:
4. Log on to the CMP and back up the database.
5. Perform a functionality check.
6. If you use an SAN, install the operating system on BE2 and configure the
mount points for OpenScape UC Application in the SAN. Then continue with
Section 15.7.3.2, Copying the UC Database from BE1 to BE2, on page 817.
810
A31003-S5070-J100-12-7631, 02/2013
If you do not use an SAN, continue with step 7 on page 811.

7. If you do not use a SAN and BE1 and BE2 are virtual computers, use the
functions of VMware ESX(i) to clone the computer BE1 to BE2. Be sure to
remove the network board in the cloned computer and add a new network
board to avoid identical MAC addresses. Continue in this case with the
instructions in Section 15.7.3.3, Copying from FE1 to FE2, on page 820.
If you do not use a SAN and BE1 and BE2 are real computers, continue with
step 8 on page 811.
8. Install the operating system on BE2 considering the following points (see
Chapter 4, Installing and Configuring the Computer and Operating System):
a) Do not assign the (external) IP address of BE1 to BE2 but use another IP
address (internal IP address), for example 192.168.2.1.
b) Apart from that, BE2 is to be identical with BE1 inclusive host and domain
name of the computer.
c) Use the internal IP addresses instead of the external ones for FE2 and
MS2 also, i. e. the /etc/hosts file on BE2 must contain the following
lines:
<Int. BE2 IP address>
<Int. FE2 IP address>
<Int. MS2 IP address>
<Ext. BE host name>

<Ext. FE host name>
<Ext. MS host name>
<Ext. BE FQDN>
<Ext. FE FQDN>
<Ext. MS FQDN>
Example:
192.168.2.1 BE BE.site
192.168.2.2 FE FE.site
192.168.2.3 MS MS.site
9. Make sure that the operating system versions inclusive service packs are
identical on BE1 and BE2. You check the operating system versions by
executing either the more /etc/issue or cat /etc/SuSE-release
command.
Example output of more /etc/issue:
Welcome to SUSE Linux Enterprise Server 11 SP1 (x86_64) Kernel \r (\).
Example output of cat /etc/SuSE-release:
VERSION = 11
PATCHLEVEL = 1
A31003-S5070-J100-12-7631, 02/2013
811
10. If you use the MySQL database (Very Large Deployment), execute the
following sub-steps:
a) Follow the instructions in Section 5.3.1, Providing the Installation
Sources in an Installation Repository in osc-setup, on page 234 for the
following ISO installation files:
Repository
BasePackage
English

osc-setup in symphonia-mysqldbms
11. The following sub-steps will check whether different RPM packages are
installed on BE1 and BE2.
a) Execute the following commands on BE1 to create an rpms_be1.txt
file that contains a sorted list of all RPM packages created on BE1.
cd /tmp
rpm -qa | sort > rpms_be1.txt
b) Execute the following commands on BE2 to create an rpms_be2.txt
file that contains a sorted list of all RPM packages created on BE2.
cd /tmp
rpm -qa | sort > rpms_be2.txt
c) Copy the rpms_be1.txt file into the directory on BE2 that contains the
rpms_be2.txt file.
Example (Execution on BE1):
scp /tmp/rpms_be1.txt root@<internal BE2 FQDN>:/tmp/
NOTE: If you are logged in on BE1 as user root you do not need root@.
d) Execute the following command on BE2 to indicate the differences
between the files rpms_be1.txt and rpms_be2.txt.
diff rpms_be1.txt rpms_be2.txt | less
If the output is empty, the same RPM packages are installed on BE1 and
BE2. Continue with step 14 on page 814 in this case.
If the output of the diff command contains the following lines and these
lines begin with the < or > character, the libraries installed on BE1 and
BE2 only differ in the OpenScape UC Application libraries.
CA2CLM-
812
A31003-S5070-J100-12-7631, 02/2013
HiPath8000AssistantOpenBranchAssistantRG8700AssistantOpenScapeUC_
Media server
openscape
scs_
symphoniassdpsymphonia
um_usermanagement
uc_commons
HiPath8000AssistantUmSupport-oscosc-setup
gpg-pubkeyssdp-service-plugin
In this case the content of the /var/lib/rpm directory on BE1 must be
copied to the same directory on BE2.
e) To leave the diff mode of the command line, enter q.
12. If the diff command delivers the non-empty output shown in step 11d on
page 812, execute the following sub-steps:
a) Execute the following commands on BE1:
cd /var/lib
tar cvf rpms_be.tar ./rpm
All RPM packages installed on the computer are represented using the /
var/lib/rpm directory. The above tar command compresses this
directory in the /var/lib/rpms_be.tar file.
b) Verify that the /var/lib/rpms_be.tar file has been created on BE1.
c) Only after that continue with step 14 on page 814.
13. If the diff command delivers neither an empty output nor the non-empty
output shown in step 11d on page 812, a smooth upgrade is not possible in
this state of BE1 and BE2. Execute the following sub-steps in this case:
a) BE1 and BE2 must be brought to the same version of the operating
system by installing, upgrading or uninstalling the different RPM
packages. Then check whether there are still different RPM packages by
step 11.
b) Execute step a as often as it takes to eliminate all different RPM
packages.
A31003-S5070-J100-12-7631, 02/2013
813
14. Execute the following command on BE1:

bash /opt/siemens/servicetools/install/bin/coldStandby.sh -s
Example output:
INFO: Saved user and group information in file '/etc/sysconfig/siemens/sym_user_group_id'
INFO: checking for: /etc/sysconfig/siemens/solid
INFO: checking for: /etc/sysconfig/siemens/symdb
INFO: Backup of the following files:
/etc/sysconfig/siemens/symphonia /etc/sysconfig/siemens/solid /etc/sysconfig/siemens/
symdb
INFO: handle extensions
INFO: =-=-=-= done =-=-=-=
INFO:
INFO: Attention:
INFO: Location for saved files is '/var/siemens/coldStandby'
INFO: This location is needed when restoring on the second node.
INFO: Please write down this information to have it available when calling this script on
the second node.
INFO:
INFO: Done!
15. If you created the file /var/lib/rpms.tar in step 12 on page 813, execute
the following command on BE1 to copy this file into the same directory on
BE2.
scp /var/lib/rpms_be.tar <internal BE2 FQDN>:/var/lib/
Replace <internal BE2 FQDN> with the internal BE2 FQDN.
Check whether the /var/lib/rpms_be.tar file is available on BE2.
16. Execute the following commands:
rsync -avz /etc/group <internal BE2 FQDN>:/etc/group
rsync -avz /etc/passwd <internal BE2 FQDN>:/etc/passwd
rsync -avz /etc/shadow <internal BE2 FQDN>:/etc/shadow
17. Execute the following command on BE1 to copy the /var/siemens
directory including its sub-directories into the same directory on BE2.
rsync -avz --exclude 'siemens/common/log/*' --exclude 'siemens/symdb/*' --exclude
'siemens/mysqldbms/*' --exclude 'siemens/backup/*' /var/siemens <internal BE2 FQDN>:/var/
Check whether the /var/siemens directory is available on BE2.
18. Execute the following command on BE1 to copy the start scripts to BE2.
scp symphoniad NSService openfire solidSYM <internal BE2 FQDN>:/etc/init.d
19. Execute the following command on BE1 to copy the UC configuration to BE2.
rsync -avz /etc/sysconfig/siemens <internal BE2 FQDN>:/etc/sysconfig
814
A31003-S5070-J100-12-7631, 02/2013
20. Execute the following command on BE1 to copy the /var/opt directory
including its sub-directories into the same directory on BE2.
rsync -avz /opt/siemens <internal BE2 FQDN>:/opt
Check whether the /opt/siemens directory is available on BE2.
21. If Small Deployment is installed, execute the following command on BE1 to
copy Nuance to BE2.
rsync -avz /usr/local/Nuance <internal BE2 FQDN>:/usr/local
Check whether the /usr/local/Nuance directory is available on BE2.
If Large Deployment or Very Large Deployment is installed, this step is
executed when copying the media server (see step 13 on page 828).
22. If the Openfire server (see Section 12.2, Infrastructure, on page 596) is
installed on BE1, execute the following command on BE1 to copy the
Openfire server to BE2.
rsync -avz /opt/openfire <internal BE2 FQDN>:/opt/
Check whether the /usr/openfire directory is available on BE2.
23. If you created the file /var/lib/rpms_be.tar in step 12 on page 813,
execute the following commands on BE2 to replace the RPM packages on
BE2 with the RPM packages of BE1.
NOTE: Replacing the RPM packages overrides files in the /var/lib/rpm
directory on BE2. If required, save the /var/lib/rpm directory before this
operation on BE2.
cd /var/lib
tar xvf rpms_be.tar
A31003-S5070-J100-12-7631, 02/2013
815
24. Execute the following command on BE2:

bash /opt/siemens/servicetools/install/bin/coldStandby.sh -r /var/siemens/coldStandby
INFO: Restore environment is ok!
INFO: running checkUID_GUID
INFO: CURRENT_GUID: 1000
INFO: CURRENT_UID: 1001
INFO: XX: running restoreSYM_UID_GUID
INFO: ***** Restore of config files ****
INFO: Checked directory '/etc/sysconfig/siemens' exists.
insserv: warning: script 'S01NSSservice' missing LSB tags and overrides
insserv: warning: script 'K01openfire' missing LSB tags and overrides
insserv: warning: script 'NSSservice' missing LSB tags and overrides
insserv: warning: script 'openfire' missing LSB tags and overrides
symphoniad 0:off 1:off 2:off 3:on 4:off 5:on 6:off
solidSYM 0:off 1:off 2:off 3:on 4:off 5:on 6:off
INFO: =-=-=-= done =-=-=-=
INFO: Done!
25. Status
SysUC2 is not operable. Specific OpenScape UC Application directories and
the RPM packages found on BE1 are available on BE2.
26. If you use a SAN, execute the following sub-steps:
a) Stop the SAN replication between BE1 and BE2.
b) Mount the SAN directories on BE2 also.
c) Continue with the instructions in Section 15.7.3.3, Copying from FE1 to
FE2, on page 820.
27. If you do not use a SAN, continue with step Section 15.7.3.2, Copying the
UC Database from BE1 to BE2, on page 817.
816
A31003-S5070-J100-12-7631, 02/2013
15.7.3.2 Copying the UC Database from BE1 to BE2

Follow the instructions in this section only if you do not use a SAN. If you use an
SAN, continue with the instructions in Section 15.7.3.3, Copying from FE1 to
FE2, on page 820.
1. Create the /solidbackup directory on BE1.
mkdir /solidbackup
chmod -R 0707 /solidbackup
2. If you use a Solid DB, execute the following sub-steps to perform a database
backup:
a) Start the Solid DB backup.
echo "admin command 'backup dir /solidbackup'" | /opt/siemens/solid/bin/solsql
"tcp 16760" dba '<password>'
Replace <password> by the password of the Solid DB that had been
installation. Due to security concerns it should not be the default
password (dba). The straight single quotation mark (') before and after
the password is needed, if the password contains special characters. Do
not use the normal (typographic) single quotation mark () instead.
b) Use the following command to check whether this backup has been
already completed:
echo "admin command 'status backup' " | /opt/siemens/solid/bin/solsql "tcp 16760" dba
'<password>'
Again, replace <password> by the password of the Solid DB that had
been introduced as parameter SI_DB_LOGON_PASSWORD in the
response file knut.responsefile.txt during the OpenScape UC
Backup has been successfully completed when the following is put out:
Connected to 'tcp 16760'.
Execute SQL statements terminated by a semicolon.
Exit by giving command: exit;
RC TEXT
-- ---0 SUCCESS
1 rows fetched.
SOLID SQL Editor exiting.
3. If you use a MySQL database (Very Large Deployment), execute the
following command to back up the database:
mysqldump -p --all-databases --single-transaction --flush-privileges > /var/siemens/
backup/mysql.all
A31003-S5070-J100-12-7631, 02/2013
817
You will be prompted for the password to access the MySQL database. Enter
the password used as parameter SI_DB_LOGON_PASSWORD in the response
file knut.responsefile.txt during the OpenScape UC Application
installation.
IMPORTANT: From this point in time the loss of data begins. However, the
OpenScape UC Application is still available.
4. Copy the data to BE2.
'siemens/mysqldbms/*' /var/siemens <internal BE2 FQDN>:/var
rsync -avz /opt/siemens <internal BE2 FQDN>:/opt
In case you use the Solid DB, run also the following command:
rsync -avz /solidbackup/* <internal BE2 FQDN>:/var/siemens/backup
Replace <internal BE2 FQDN> with the fully qualified domain name
(FQDN) of BE2. You can also use the IP address or the computer name (host
name) be we recommend the FQDN.
5. If you use the Solid DB, execute the following sub-steps to restore the
database on BE2:
a) Stop the Solid DB.
/etc/init.d/solidSYM stop
b) Replace the log files that exist on BE2 with the log files you copied from
BE1 to BE2.
rm -f /var/siemens/symdb/SYMDBlog/*
mv /var/siemens/backup/*.log /var/siemens/symdb/SYMDBlog
c) Replace the database files that exist on BE2 with the database files you
copied from BE1 to BE2.
rm -f /var/siemens/symdb/SYMDB/*.db
mv /var/siemens/backup/*.db /var/siemens/symdb/SYMDB
d) Execute the following command in a command line:
i=1; while [ $i -le 50 ]; do file=`printf /var/siemens/symdb/SYMDB/solid%02d.db $i`;
echo $file; if [ ! -f "$file" ]; then touch $file; fi;i=`expr $i + 1`;done
e) Start the Solid DB:
/etc/init.d/solidSYM start
6. If you use the MySQL DB (Very Large Deployment), execute the following
sub-steps to restore the database on BE2:
818
A31003-S5070-J100-12-7631, 02/2013
a) Start MySQL.
/etc/init.d/mysqldbms start
b) Restore the database.
mysql -uroot -p'<password>' </var/siemens/backup/mysql.all
Replace <password> by the password of the database that had been
installation. The straight single quotation mark (') before and after the
password is needed, if the password contains special characters. Do not
use the normal (typographic) single quotation mark () instead.
7. Do not yet start the OpenScape UC Application on BE2.
8. Status
the RPM packages found on BE1 are available on BE2. Likewise, the same
database is available on BE2 as on BE1.
A31003-S5070-J100-12-7631, 02/2013
819
15.7.3.3 Copying from FE1 to FE2

1. Install the operating system on FE2 considering the following points (see
a) Do not assign the (external) IP address of FE1 to FE2 but use another IP
address (internal IP address). Use the IP address (for example
192.168.2.2) you already used for FE2 in step 8 on page 811 in the /
etc/hosts file on BE2.
b) Apart from that, FE2 is to be identical with FE1 inclusive host and domain
c) Use the internal IP addresses instead of the external ones for BE2 and
MS2 also, i. e. the /etc/hosts file on FE2 must contain the following
lines:
<Ext. BE host name>

<Ext. FE host name>
<Ext. MS host name>
<Ext. BE FQDN>
<Ext. FE FQDN>
<Ext. MS FQDN>
Example:
192.168.2.1 BE BE.site
192.168.2.2 FE FE.site
192.168.2.3 MS MS.site
identical on FE1 and FE2. You check the operating system versions by
command.
VERSION = 11
PATCHLEVEL = 1
installed on FE1 and FE2.
a) Execute the following commands on FE1 to create an rpms_fe1.txt
file that contains a sorted list of all RPM packages created on FE1.
cd /tmp
rpm -qa | sort > rpms_fe1.txt
b) Execute the following commands on FE2 to create an rpms_fe2.txt
file that contains a sorted list of all RPM packages created on FE2.
cd /tmp
rpm -qa | sort > rpms_fe2.txt
820
A31003-S5070-J100-12-7631, 02/2013
c) Copy the rpms_fe1.txt file into the directory on FE2 that contains the
rpms_fe2.txt file.
Example (Execution on FE1):
scp /tmp/rpms_fe1.txt <internal FE2-FQDN>:/tmp/
d) Execute the following command on FE2 to indicate the differences
between the files rpms_fe1.txt and rpms_fe2.txt.
diff rpms_fe1.txt rpms_fe2.txt | less
If the output is empty, the same RPM packages are installed on FE1 and
FE2. Continue with step 6 on page 822 in this case.
lines begin with the < or > character, the libraries installed on FE1 and
FE2 only differ in the OpenScape UC Application libraries.
CA2CLMHiPath8000AssistantOpenBranchAssistantRG8700AssistantOpenScapeUC_
Media server
openscape
scs_
um_usermanagement
uc_commons
In this case the content of the /var/lib/rpm directory on FE1 must be
copied to the same directory on FE2.
a) Execute the following commands on FE1:
cd /var/lib
tar cvf rpms_fe.tar ./rpm
directory in the /var/lib/rpms_fe.tar file.
b) Verify that the /var/lib/rpms_fe.tar file has been created on FE1.
A31003-S5070-J100-12-7631, 02/2013
821
output shown in step 3d on page 821, a smooth upgrade is not possible in this
state of FE1 and FE2. Execute the following sub-steps in this case:
a) FE1 and FE2 must be brought to the same version of the operating
step 3 on page 820.
packages.
6. Execute the following command on FE1:
Example output:
symdb
INFO: =-=-=-= done =-=-=-=
INFO:
INFO: Attention:
the second node.
INFO:
INFO: Done!
7. If you created the file /var/lib/rpms_fe.tar in step 4 on page 821,
execute the following command on FE1 to copy this file into the same
directory on FE2.
scp /var/lib/rpms_fe.tar <internal FE2 FQDN>:/var/lib/
Replace <internal FE2 FQDN> with the internal FE2 FQDN.
Check whether the /var/lib/rpms_fe.tar file is available on FE2.
8. Execute the following command on FE1 to copy the /var/siemens
directory including its sub-directories into the same directory on FE2.
'siemens/mysqldbms/*' --exclude 'siemens/backup/*' /var/siemens <internal FE2 FQDN>:/var/
Check whether the /var/siemens directory is available on FE2.
822
A31003-S5070-J100-12-7631, 02/2013
9. Execute the following command on FE1 to copy the start scripts

symphoniad, NSService and solidSYM to FE2 if they are available in your
scp symphoniad NSService solidSYM <internal FE2 FQDN>:/etc/init.d
10. Execute the following command on FE1 to copy the UC configuration to FE2.
rsync -avz /etc/sysconfig/siemens <internal FE2 FQDN>:/etc/sysconfig
11. Execute the following command on FE1 to copy the /var/opt directory
including its sub-directories into the same directory on FE2.
rsync -avz /opt/siemens <internal FE2 FQDN>:/opt
Check whether the /opt/siemens directory is available on FE2.
12. If you created the file /var/lib/rpms_fe.tar in step 4 on page 821,
execute the following commands on FE2 to replace the RPM packages on
FE2 with the RPM packages of FE1.
directory on FE2. If required, back up the /var/lib/rpm directory before
this operation on FE2.
cd /var/lib
tar xvf rpms_fe.tar
A31003-S5070-J100-12-7631, 02/2013
823
13. Execute the following command on FE2:

INFO: =-=-=-= done =-=-=-=
INFO: Done!
14. Do not yet start the OpenScape UC Application on FE2.
15. Status
database is available on BE2 as on BE1. Specific OpenScape UC Application
directories and the RPM packages found on FE1 are available on FE2.
824
A31003-S5070-J100-12-7631, 02/2013
15.7.3.4 Copying from MS1 to MS2

1. Install the operating system on MS2 considering the following points (see
a) Do not assign the (external) IP address of MS1 to MS2 but use another
IP address (internal IP address). Use the IP address (for example
192.168.2.3) you already used for MS2 in step 8 on page 811 in the /
etc/hosts file on BE2.
b) Apart from that, MS2 is to be identical with MS1 inclusive host and domain
c) Use the internal IP addresses instead of the external ones for BE2 and
FE2 also, i. e. the /etc/hosts file on MS2 must contain the following
lines:
<Ext. BE host name>

<Ext. FE host name>
<Ext. MS host name>
<Ext. BE FQDN>
<Ext. FE FQDN>
<Ext. MS FQDN>
Example:
192.168.2.1 BE BE.site
192.168.2.2 FE FE.site
192.168.2.3 MS MS.site
identical on MS1 and MS2. You check the operating system versions by
command.
VERSION = 11
PATCHLEVEL = 1
installed on MS1 and MS2.
a) Execute the following commands on MS1 to create an rpms_ms1.txt
file that contains a sorted list of all RPM packages created on MS1.
cd /tmp
rpm -qa | sort > rpms_ms1.txt
b) Execute the following commands on MS2 to create an rpms_ms2.txt
file that contains a sorted list of all RPM packages created on MS2.
cd /tmp
rpm -qa | sort > rpms_ms2.txt
A31003-S5070-J100-12-7631, 02/2013
825
c) Copy the rpms_ms1.txt file into the directory on MS2 that contains the
rpms_ms2.txt file.
Example (Execution on MS1):
scp /tmp/rpms_ms1.txt <internal MS2 FQDN>:/tmp/
d) Execute the following command on MS2 to indicate the differences
between the files rpms_ms1.txt and rpms_ms2.txt.
diff rpms_ms1.txt rpms_ms2.txt | less
If the output is empty, the same RPM packages are installed on MS1 and
MS2. Continue with step 6 on page 827 in this case.
lines begin with the < or > character, the libraries installed on MS1 and
MS2 only differ in the OpenScape UC Application libraries.
CA2CLMHiPath8000AssistantOpenBranchAssistantRG8700AssistantOpenScapeUC_
Media server
openscape
scs_
um_usermanagement
uc_commons
In this case the content of the /var/lib/rpm directory on MS1 must be
copied to the same directory on MS2.
a) Execute the following commands on MS1:
cd /var/lib
tar cvf rpms_ms.tar ./rpm
directory in the /var/lib/rpms_ms.tar file.
b) Verify that the /var/lib/rpms_ms.tar file has been created on MS1.
826
A31003-S5070-J100-12-7631, 02/2013
output shown in step 3d on page 826, a smooth upgrade is not possible in this
state of MS1 and MS2. Execute the following sub-steps in this case:
a) MS1 and MS2 must be brought to the same version of the operating
step 11.
packages.
6. Execute the following command on MS1:
Example output:
symdb
INFO: =-=-=-= done =-=-=-=
INFO:
INFO: Attention:
the second node.
INFO:
INFO: Done!
7. If you created the file /var/lib/rpms_ms.tar in step 4 on page 826,
execute the following command on MS1 to copy this file into the same
directory on MS2.
scp /var/lib/rpms_ms.tar <internal MS2-FQDN>:/var/lib/
Replace <internal MS2 FQDN> with the internal MS2 FQDN.
Check whether the /var/lib/rpms_ms.tar file is available on MS2.
8. Execute the following commands:
rsync -avz /etc/group <internal BE2 FQDN>:/etc/group
rsync -avz /etc/passwd <internal BE2 FQDN>:/etc/passwd
rsync -avz /etc/shadow <internal BE2 FQDN>:/etc/shadow
9. Execute the following command on MS1 to copy the /var/siemens
directory including its sub-directories into the same directory on MS2.
A31003-S5070-J100-12-7631, 02/2013
827

'siemens/mysqldbms/*' --exclude 'siemens/backup/*' /var/siemens <internal MS2 FQDN>:/var/
Check whether the /var/siemens directory is available on MS2.
10. Execute the following command on MS1 to copy the start scripts
symphoniad, NSService and solidSYM to MS2 if they are available in
your OpenScape UC Application.
scp symphoniad NSService solidSYM <internal MS2 FQDN>:/etc/init.d
11. Execute the following command on MS1 to copy the UC configuration to MS2.
rsync -avz /etc/sysconfig/siemens <internal MS2 FQDN>:/etc/sysconfig
12. Execute the following command on MS1 to copy the /var/opt directory
including its sub-directories into the same directory on MS2.
rsync -avz /opt/siemens <internal MS2 FQDN>:/opt
Check whether the /opt/siemens directory is available on MS2.
13. Execute the following command on MS1 to copy Nuance to MS2.
rsync -avz /usr/local/Nuance <internal MS2 FQDN>:/usr/local
Check whether the /usr/local/Nuance directory is available on MS2.
14. If you created the file /var/lib/rpms_ms.tar in step 4 on page 826,
execute the following commands on MS2 to replace the RPM packages on
MS2 with the RPM packages of MS1.
directory on MS2. If required, back up the /var/lib/rpm directory before
this operation on MS2.
cd /var/lib
tar xvf rpms_ms.tar
15. Execute the following command on MS2:
828
A31003-S5070-J100-12-7631, 02/2013

INFO: =-=-=-= done =-=-=-=
INFO: Done!
16. Do not yet start the OpenScape UC Application on MS2.
17. Status
database is available on BE2 as on BE1. On FE2, specific directories of the
OpenScape UC Application and the same RPM packages as on FE1 are
available. On MS2, specific directories of the OpenScape UC Application and
the same RPM packages as on MS1 are available.
A31003-S5070-J100-12-7631, 02/2013
829
15.7.4 Switching from SysUC1 to SysUC2

1. The IP addresses are currently assigned as follows:
a) The /etc/hosts files on BE1, FE1 and MS1 contain the following lines
based on step 2 on page 810:
<Ext. BE host name>

<Ext. FE host name>
<Ext. MS host name>
<Ext. BE FQDN>
<Ext. FE FQDN>
<Ext. MS FQDN>
Example:
b) The /etc/hosts files on BE2, FE2 and MS2 include the following lines
based on step 8 on page 811, step 1 on page 820 and step 1 on page 825:
<Ext. BE host name>

<Ext. FE host name>
<Ext. MS host name>
<Ext. BE FQDN>
<Ext. FE FQDN>
<Ext. MS FQDN>
Example:
192.168.2.1 BE BE.site
192.168.2.2 FE FE.site
192.168.2.3 MS MS.site
IMPORTANT: The following step disables SysUC1, no OpenScape UC Application is thus available anymore.
2. Stop the OpenScape UC Application on BE1, FE1 and MS1 by executing the
following command on all of these computers:
3. Stop the MRCP service, the Nuance TTS and the Nuance ASR, if available,
on MS1:
4. Execute the following sub-steps on BE1:
a) Enter command yast.
b) Open Network Devices > Network Settings.
c) Enter <Alt> + i to configure the network board.
IMPORTANT: Enter the computer's internal IP address in the IP
Address field. Please note that the internal IP addresses of BE1, FE1
and MS1 must differ from the internal IP addresses of BE2, FE2 and MS2.
830
A31003-S5070-J100-12-7631, 02/2013
Example of BE1: 192.168.1.1

d) Select Next.
e) Select OK.
f)
Select Quit.
5. Execute step 4 on page 830 on FE1 using 192.168.1.2 for example.

6. Execute step 4 on page 830 on MS1 using 192.168.1.3 for example.
7. Check whether the external IP addresses mentioned in step 1a on page 830
have been replaced with internal IP addresses in the /etc/hosts files on
BE1, FE1 and MS1:
<Ext. BE host name>

<Ext. FE host name>
<Ext. MS host name>
<Ext. BE FQDN>
<Ext. FE FQDN>
<Ext. MS FQDN>
Example:
192.168.1.1 BE BE.site
192.168.1.2 FE FE.site
192.168.1.3 MS MS.site
IMPORTANT: Make sure that these internal IP addresses are not identical
with the internal IP addresses of BE2, FE2 and MS2.
Enter the computer's external IP address in the IP Address field.
d) Select Next.
e) Select OK.
f)
Select Quit.

A31003-S5070-J100-12-7631, 02/2013
831
11. Check whether the internal IP addresses of BE2, FE2 and MS2 mentioned in
step 1b on page 830 have been replaced with external IP addresses in the /
etc/hosts files on BE2, FE2 and MS2:
<Ext. BE host name>

<Ext. FE host name>
<Ext. MS host name>
<Ext. BE FQDN>
<Ext. FE FQDN>
<Ext. MS FQDN>
Example:
12. Start the OpenScape UC Application on BE2.
IMPORTANT: Be sure to execute this step before the next two steps.
13. Start the OpenScape UC Application on FE2.
NOTE: You can execute this step simultaneously with the next step.
14. Start the MRCP service, the Nuance TTS and the Nuance ASR on MS2, if
available:
15. Start the OpenScape UC Application on MS2.
16. Check the status of the OpenScape UC Application on BE2, FE2 and MS2.
17. Status
SysUC1 cannot be reached under the external IP addresses anymore.
However, BE1, FE1 and MS1 can communicate with each other via the
internal IP addresses.
SysUC2 is now operable under the same (external) IP addresses and in the
same original OpenScape UC Application version as SysUC1 was previously,
i. e. no difference can be noticed from outside. For example, the CMP is now
accessed for SysUC2 under the same (external) IP address as previously for
SysUC1.
IMPORTANT: The data loss and unavailability period has come to an end.
832
A31003-S5070-J100-12-7631, 02/2013
15.7.5 Upgrading SysUC1 to the Target Version

1. Upgrade BE1, FE1 and MS1 according to Section 15.6.2, Upgrading Large
Deployment, on page 771 and considering the following points:
a) The instructions in Section 15.2, Update and Upgrade Preparations, on
page 665
b) You can perform the following operations simultaneously:
Upgrading FE1
Upgrading MS1
If you wish to perform an update instead of an upgrade, follow the instructions

in Section 15.3.1.3, Large Deployment and Very Large Deployment, on
page 716. Please also consider the instructions in Section 15.2, Update and
Upgrade Preparations, on page 665.
If you wish to install a hotfix instead of performing an upgrade, follow the
instructions in Section 15.3.2.2, Large Deployment and Very Large
Deployment, on page 730. Please also consider the instructions in Section
15.2, Update and Upgrade Preparations, on page 665.
In case of an update, you can also follow the instructions in Section 15.3.3,
Updating using the CMP (UI Patching) instead of osc-setup, on page 733
instead of those in the above sections.
2. Status
SysUC1 is now upgraded to the target version but not operable yet, because
the internal IP addresses are still used.
A31003-S5070-J100-12-7631, 02/2013
833
15.7.6 Switching from SysUC2 to SysUC1

1. The IP addresses are currently assigned as follows:
a) The /etc/hosts files on BE2, FE2 and MS2 include the following lines
based on step 8 on page 831, step 9 on page 831 and step 10 on page
831:
<Ext. BE host name>

<Ext. FE host name>
<Ext. MS host name>
<Ext. BE FQDN>
<Ext. FE FQDN>
<Ext. MS FQDN>
Example:
b) The /etc/hosts files on BE1, FE1 and MS1 include the following lines
based on step 4 on page 830, step 5 on page 831 and step 6 on page 831:
<Ext. BE host name>

<Ext. FE host name>
<Ext. MS host name>
<Ext. BE FQDN>
<Ext. FE FQDN>
<Ext. MS FQDN>
Example:
192.168.1.1 BE BE.site
192.168.1.2 FE FE.site
192.168.1.3 MS MS.site
IMPORTANT: The following step disables SysUC2, no OpenScape UC Application is thus available anymore.
2. Stop the OpenScape UC Application on BE2, FE2 and MS2 by executing the
following command on all of these computers:
on MS2:
d) Enter the computer's internal IP address in the IP Address field.
e) Select Next.
834
A31003-S5070-J100-12-7631, 02/2013
f)
Select OK.
g) Select Quit.
7. Check whether the external IP addresses mentioned in step 4a on page 834
have been replaced with internal IP addresses in the /etc/hosts files on
BE2, FE2 and MS2:
<Ext. BE host name>

<Ext. FE host name>
<Ext. MS host name>
<Ext. BE FQDN>
<Ext. FE FQDN>
<Ext. MS FQDN>
Example:
192.168.2.1 BE BE.site
192.168.2.2 FE FE.site
192.168.2.3 MS MS.site
IMPORTANT: Make sure that these internal IP addresses are not identical
with the internal IP addresses of BE1, FE1 and MS1.
d) Enter the computer's external IP address in the IP Address field.
e) Select Next.
f)
Select OK.
g) Select Quit.
11. Check whether the internal IP addresses of BE1, FE1 and MS1 mentioned in
step 4b on page 834 have been replaced with external IP addresses in the /
etc/hosts files on BE1, FE1 and MS1:
<Ext. BE host name>

<Ext. FE host name>
<Ext. MS host name>
A31003-S5070-J100-12-7631, 02/2013
<Ext. BE FQDN>
<Ext. FE FQDN>
<Ext. MS FQDN>
835
Example:
12. Start the OpenScape UC Application on BE1.
IMPORTANT: Be sure to execute this step before the next two steps.
13. Start the OpenScape UC Application on FE1.
NOTE: You can execute this step simultaneously with the next step.
14. Start the MRCP service, the Nuance TTS and the Nuance ASR on MS1, if
available:
15. Start the OpenScape UC Application on MS1.
16. Check the status of the OpenScape UC Application on BE1, FE1 and MS1.
17. Status
SysUC1 is now operable under the same (external) IP addresses as at the
start of the smooth upgrade but has the target version of the OpenScape UC
Application.
SysUC2 is installed but not upgraded and not operable either because of the
internal IP addresses used on the computers.
IMPORTANT: The unavailability period has now come to an end.
18. Check the functionality of the OpenScape UC Application target version on
SysUC1.
19. If you use a SAN, execute the following sub-steps:
a) Start the SAN replication between BE1 and BE2.
b) Mount the SAN directories on BE2 also.
20. The smooth upgrade is now complete.
836
A31003-S5070-J100-12-7631, 02/2013
Upgrading V3 R2 or V6 R0 Small Deployment including a Hardware Change
15.8 Upgrading V3 R2 or V6 R0 Small Deployment including a Hardware

Change
An upgrade from V3 R2 or V6 to V7 may only be possible in combination with a
hardware change, because the old V7 hardware is not supported. In case of
Small Deployment, proceed as follows:
1. Please consult the OpenScape UC Application V7 Planning Guide to see
which hardware you need for V7 Small Deployment.
2. If you want to upgrade V3 R2, execute the instructions in section Hardware
Change for V3 R2 Standard Duplex (small) in the installation guide
OpenScape UC Application V3 Installation and Upgrade Thus, you receive a
V3 R2 that operates on a hardware supported by V7 R1.
If you want to upgrade V6, execute the instructions in section Hardware
Change for V6 Standard Duplex (small) in the installation guide OpenScape
UC Application V6 Installation and Upgrade. Thus, you receive a V6 that
operates on a hardware supported by V7 R1.
3. Follow the instructions according to the following sections:
a) Section 15.1, Determining the Source Version, on page 662
b) Section 15.2, Update and Upgrade Preparations, on page 665
c) Section 15.6.1, Upgrading Small Deployment, on page 750
Please heed the information in Table 119 on page 745, Upgrade and
Migration Table for Small Deployment and Large Deployment.
A31003-S5070-J100-12-7631, 02/2013
837
Upgrading V3 R2 or V6 R0 Large Deployment including a Hardware Change
15.9 Upgrading V3 R2 or V6 R0 Large Deployment including a Hardware

Change
An upgrade from V3 R2 or V6 to V7 may only be possible in combination with a
hardware change, because the old V7 hardware is not supported. In case of
Large Deployment, proceed as follows:
1. Please consult the OpenScape UC Application V7 Planning Guide to see
which hardware you need for V7 Large Deployment.
2. If you want to upgrade V3 R2, execute the instructions in section Hardware
Change for V3 R2 Standard Duplex (large) in the installation guide
OpenScape UC Application V3 Installation and Upgrade Thus, you receive a
V3 R2 that operates on a hardware supported by V7 R1.
If you want to upgrade V6, execute the instructions in section Hardware
Change for V6 Standard Duplex (large) in the installation guide OpenScape
UC Application V6 Installation and Upgrade. Thus, you receive a V6 that
operates on a hardware supported by V7 R1.
3. Follow the instructions according to the following sections:
a) Section 15.1, Determining the Source Version, on page 662
b) Section 15.2, Update and Upgrade Preparations, on page 665
c) Section 15.6.2, Upgrading Large Deployment, on page 771
Please heed the information in Table 119 on page 745, Upgrade and
Migration Table for Small Deployment and Large Deployment.
838
A31003-S5070-J100-12-7631, 02/2013
Upgrading V3 R2 or V6 R0 Small Deployment in Case of an unavailable LVM2
15.10 Upgrading V3 R2 or V6 R0 Small Deployment in Case of an

unavailable LVM2
This section describes an upgrade from the OpenScape UC Application in the
event that the application computer does not have an LVM2 storage location yet.
If the application computer on which you wish to upgrade the OpenScape UC
Application already has an LVM2 storage location with at least two logical LVM2
partitions (see Table 5 on page 118, Partition Sizes without using a USB Hard
Disk for File System Backup), follow the instructions in Section 15.6.1,
Upgrading Small Deployment, on page 750.
Application has only one LVM2 partition, follow the instructions in Section 15.12,
Upgrading V3 R2 or V6 R0 Small Deployment in Case of only one available
LVM2 Partition, on page 862.
The major upgrade steps are:
Upgrading to V7
Backing up data of the OpenScape UC Application (no file system backup)
Complete reinstallation of the OpenScape UC Application V7 including

SLES and LVM2 partitions
Restoring the OpenScape UC Application data
NOTE: All steps must be executed as root.
Upgrading without changing the LVM2 partitions

1. Follow the instructions in Section 15.1, Determining the Source Version, on
page 662 and Section 15.2, Update and Upgrade Preparations, on page
665 but without Section 15.2.4, Preparing to the syncUC Fallback, on page
707 as preparation.
2. Execute the instructions given in Section 15.6.1, Upgrading Small
A31003-S5070-J100-12-7631, 02/2013
839
Backing up Data
IMPORTANT: In the following you will be repeatedly prompted to back
up data (for example backing up data using the CMP, backing up of
FQDNs, IP addresses and personal greeting prompts). Be sure not to
back up such data on the application computer but on a separate
computer as the application computer plus operating system will be
completely reinstalled.
3. Be sure to use the setup medium you deployed for upgrading to Small
Deployment (see step 2 on page 839) for the installation also.
4. Check whether you have the password of the Symphonia administrator,
which was used upon setting up Small Deployment (see step 7 on page 200).
7. Back up data of the OpenScape UC Application according to section Backing
up and restoring general OpenScape System Components of the
administrator documentation of the OpenScape UC Application Configuration
and Administration.
IMPORTANT: Be sure to back up data (select value Data in the Select
backup type field) and not a file system (value System in the Select backup
type field) in the CMP.
840
A31003-S5070-J100-12-7631, 02/2013
NOTE: Since the application computer is newly installed, using syncUC (see
Section 15.2.4.2, syncUC Commands, on page 707) instead of a data
backup is not advisable.
8. Note down the following application computer data:
IP address
Host name
FQDN
Community name
Community String.
Display name of the computer in the CMP (see step 10 on page 201 for
example)
Standard assignment: SI_LOCAL_NAME=offboard
A31003-S5070-J100-12-7631, 02/2013
841
You can obtain such values from e. g. the following response file on any of
these computers:
/root/knut.responsefile.txt
You will need such values when installing these computers anew.
9. Determine whether optional applications are installed on the application
computer.
Example:
zypper se -i --match-any hpum
This command determines whether a package has been installed that carries
hpum in its name. Compare sub-section Adding optional applications on page
267 on this.
10. Use the following command on the application computer to determine which
languages have been installed and note them down for use in step 15 on
page 848:
zypper se -i --match-any announ uc-tts uc-asr languagepack
842
A31003-S5070-J100-12-7631, 02/2013

S | Name
| Summary
| Type
| package
| package
...
| package
| package
...
| mediaserver_autoattendant_languagepack_DE-DE| Mediaserver AutoAttendant La->| package
| mediaserver_autoattendant_languagepack_EN-GB| Mediaserver AutoAttendant La->| package
i | mediaserver_autoattendant_languagepack_EN-US| Mediaserver AutoAttendant La-> |
package
| mediaserver_autoattendant_languagepack_ES-ES| Mediaserver AutoAttendant La-> |
package
...
package
package
package
package
...
package
package
...
package
package
package
...
A31003-S5070-J100-12-7631, 02/2013
843
i | uc-asr
package
| uc-asr-de_de
package
| uc-asr-en_us
package
i | uc-asrcore
package
...
i | uc-tts
package
| uc-tts-de_de
package
| uc-tts-en_gb
package
| uc-asr-en_us
package
...
| uc-tts-zh_cn
package
i | uc-ttscore
package

| German tts voice.


11. The directory
/opt/siemens/mediaserver/application_host/deployment/userresources/res/
on the application computer contains possibly available personal welcome
prompts for OpenScape UC Application users. Back up the contents of this
directory. It will be copied to the newly installed application computer in a later
step.
844
A31003-S5070-J100-12-7631, 02/2013
Preparing the installations

IMPORTANT: Verify that the backup copies you created in the previous
steps do not exist on the computers to be newly installed.
12. Prepare the application computer according to the following sections for a
new installation of the OpenScape UC Application:
NOTE: Use during the preparations the IP address, the computer name and
the FQDN you noted down in step 8 on page 841.
a) Chapter 2, General Preparations
b) Chapter 3, Providing Virtual Computers
c) Chapter 4, Installing and Configuring the Computer and Operating
System
If no computer with a hard disk of the size according to Table 5 on page
118 is available, a local, external USB hard disk serves as storage
location for the file system backup. Table 127 on page 846 indicates the
partition sizes for this case.
IMPORTANT: The local, external USB hard disk must have been
formatted with ext3, because NTFS is not natively supported by SLES 11
and FAT32 does not support files bigger than 4 GB.
A31003-S5070-J100-12-7631, 02/2013
845
Partition
Partition
type

Documentation
example1
Calculation Number
2
On the computer
Hard disk for syncUC
Hard disk
N3
160
Planning Guide
/boot
Primary

boot Partition
Swap
Primary

swap Partition
LVM2 memory
Primary
N-4
156

LVM2 partition
Logical
volume
group
OpenScape
UC

OpenScape UC

Logical
operation of the
UC1
0.95*(N-4)/2 74,1

Logical Volume UC1

means of syncUC
Logical
UC2
0.95*(N-4)/2 74,1

Logical Volume UC2
Temporary snapshot
Logical
0.1*(N-4)/2
0.9*0.95*(N- 66,7
4)/2
7,8
On the USB hard disk

Hard disk for file system backup Hard disk
Table 127
Partition Sizes when using a USB Hard Disk for File System Backup
1 See Section 4.2, SLES Installation, on page 119.

2 For the minimum size of the 160 GB hard disk.
3 Hard disk size is defined as N.
Always configure partitions in such a way that the preparation for a

fallback by means of syncUC (see Section 15.2.4, Preparing to the
syncUC Fallback, on page 707) as well as for a fallback by means of file
system backup (see Section 4.5, Configuring the File System Backup,
on page 181) is possible.
d) Section 5.1, Installation Requirements, on page 192
e) Section 5.2.1, Preparation, on page 196
846
A31003-S5070-J100-12-7631, 02/2013
Configuring the installations

13. Configure the installation for the application computer according to Section
5.2.2.1, Example of Deployment Scenario Small Deployment, on page 198.
In doing so be sure to use the data you noted down in step 8 on page 841.
Step 8 on page 200
Step 9 on page 201
Step 10 on page 201
A31003-S5070-J100-12-7631, 02/2013
847
Installations
14. Execute the instructions given in Section 5.3.1, Providing the Installation
Sources in an Installation Repository in osc-setup, on page 234.
15. Execute the instructions given in Section 5.3.2, Installing the Small
In doing so heed the following:
a) Install the optional applications that were installed on the application
computer (see step 9 on page 842) before the OpenScape UC
Application V7 was set up, too.
b) In section Adding optional languages on page 270 be sure to install the
languages you noted down in step 10 on page 842.
c) Copy the content of the directory backed up in step 11 on page 844
into the same path on the application computer. Personal welcome
prompts that probably existed before the installation will then still be
available.
16. Follow the instructions in the following sections:
Section 5.4, Checking the Installation, on page 347
Chapter 6, Configuring the OpenScape UC Application
Heed the information in section Section 5.5, Trouble Ticket, on page 358.
17. Restore the data backed up in step 7 on page 840 according to section
Backing up and restoring OpenScape System Components in the
and Administration.
18. If a Mobile Client Facade server has been installed and HTTPS is used, the
certificate of the new OpenScape UC Application must be imported, i. e. you
need to execute the instructions in sub-section Connection via HTTPS on
page 556 again.
848
A31003-S5070-J100-12-7631, 02/2013
19. If the OpenScape UC Application is connected to an Openfire server, execute

the instructions in Section 12.5.1, Initial Configuration for Integrated
Deployment, Small Deployment and Large Deployment, on page 602.
Then perform the Openfire configuration according to the administrator
for example section Configuring the Instant-Messaging Connection.

PINs.
A31003-S5070-J100-12-7631, 02/2013
849
21. The upgrade is now complete.
850
A31003-S5070-J100-12-7631, 02/2013
Upgrading V3 R2 or V6 R0 Large Deployment in Case of an unavailable LVM2
15.11 Upgrading V3 R2 or V6 R0 Large Deployment in Case of an

unavailable LVM2
This section describes an upgrade from the OpenScape UC Application in the
event that the application computer, the frontend computers and the media server
computers do not have an LVM2 storage location yet.
If the application computer, the frontend computers and media server computers
on which you wish to upgrade the OpenScape UC Application already have an
LVM2 storage location with at least two logical LVM2 partitions (see Table 5 on
page 118, Partition Sizes without using a USB Hard Disk for File System
Backup), follow the instructions in Section 15.6.2, Upgrading Large
If the application computer, the frontend computers and media server computers
on which you wish to upgrade the OpenScape UC Application have only one
LVM2 partition, follow the instructions in Section 15.13, Upgrading V3 R2 or
V6 R0 Large Deployment in Case of only one available LVM2 Partition, on page
885.
The major upgrade steps are:
Upgrading to V7
Backing up data of the OpenScape UC Application (no file system backup)
Complete reinstallation of the OpenScape UC Application V7 including

SLES and LVM2 partitions

707 as preparation.
2. Execute the instructions given in Section 15.6.2, Upgrading Large
A31003-S5070-J100-12-7631, 02/2013
851
Backing up Data
up data (for example backing up data using the CMP, backing up of
FQDNs, IP addresses and personal greeting prompts). Be sure to back
up such data on a separate computer and not on the application
computer, on the frontend computers or media server computers as
such computers plus operating system will be completely reinstalled.
3. Be sure to use the setup medium you deployed for upgrading to Large
Deployment (see step 2 on page 851) for the installation also.
which was used upon setting up Large Deployment (see step 7 on page 204).
up and restoring OpenScape System Components of the administrator
documentation of the OpenScape UC Application Configuration and
Administration.
852
A31003-S5070-J100-12-7631, 02/2013
NOTE: Since the application computer, the frontend computers and media
server computers are newly installed, using syncUC (see Section 15.2.4.2,
syncUC Commands, on page 707) instead of a data backup is not
advisable.
7. Note down the following data of the application computer, the frontend
computers and media server computers:
IP addresses
Host names
FQDN
Community names
Community String.
Port
This refers to the port specified in the response file in the event that the
application computer and the frontend computer(s) are installed in
different sub-networks (see step 8 on page 205 for example).
A31003-S5070-J100-12-7631, 02/2013
853
example)
these computers:
You will need such values when installing these computers anew (see steps
computer.
Example:
zypper se -i --match-any hpum
284 on this.
9. Use the following command on the media server computer to determine
which languages have been installed and note them down for use in step 17
on page 859:
zypper se -i --match-any announ uc-tts uc-asr languagepack
854
A31003-S5070-J100-12-7631, 02/2013

S | Name
| Summary
| Type
| package
| package
...
| package
| package
...
package
package
...
package
package
package
package
...
package
package
...
package
package
package
...
| uc-asr-de_de
package
| uc-asr-en_us
package
i | uc-asrcore
package
...
i | uc-tts
package
| uc-tts-de_de
package
| uc-tts-en_gb
package
| uc-asr-en_us
package
| Meta rpm to install all A->| package

| German tts voice.

...
A31003-S5070-J100-12-7631, 02/2013
855
i | uc-asr
| uc-tts-zh_cn
package
i | uc-ttscore
package


10. The directory
on the media server computers contains possibly available personal welcome
directory. It will be copied to the newly installed media server computer in step
17 on page 859.
IMPORTANT: You need to execute this step before starting the export in the
next step.

11. Prepare the application computer, the frontend computers and media server
computers according to the following sections for a new installation of the
NOTE: Use during the preparations the IP addresses, the computer names
and the FQDNs you noted down in step 7 on page 853.
System
856
A31003-S5070-J100-12-7631, 02/2013

Partition
Partition
type

Documentation
example1
Calculation Number
2
On the computer
Hard disk
N3
160
Planning Guide
/boot
Primary

boot Partition
Swap
Primary

swap Partition
LVM2 memory
Primary
N-4
156

LVM2 partition
Logical
volume
group
OpenScape
UC

OpenScape UC

Logical
operation of the
UC1
0.95*(N-4)/2 74,1

Logical Volume UC1

means of syncUC
Logical
UC2
0.95*(N-4)/2 74,1

Logical Volume UC2
Temporary snapshot
Logical
0.1*(N-4)/2
0.9*0.95*(N- 66,7
4)/2
7,8

Table 128


A31003-S5070-J100-12-7631, 02/2013
857

12. Configure the installation for the application computer, all frontend computers
and all media server computers according to Section 5.2.2.2, Example of
Deployment Scenario Large Deployment, on page 203.
In doing so be sure to use the data you noted down in step 7 on page 853 in
the following sub-steps.
a) Response file for the application computer on page 203
Step 8 on page 205
Step 10 on page 205
Step 11 on page 206
b) Response file for the frontend server on page 208
Step 24 on page 210
Step 25 on page 210
Step 26 on page 210
Step 27 on page 210
c) Response file for the media server computer on page 213
858
Step 39 on page 214
Step 40 on page 215
Step 41 on page 215
Step 42 on page 215
A31003-S5070-J100-12-7631, 02/2013
Installations
14. Execute the instructions given in Section 5.3.3.1, Installation on the
Application Computer, on page 281.
IMPORTANT: The installation on the application computer must be
performed before the installations on the frontend computer and media server
computer.
Install the optional applications that were installed on the application
computer before the migration (see step 8 on page 854) also.
15. Execute the instructions in Section 5.3.3.2, Requirements for Installing
Additional Computers, on page 290.
16. Execute the instructions in Section 5.3.3.3, Installation on the Frontend
Computer, on page 293 for all frontend computers.
17. Execute the instructions in Section 5.3.3.4, Installation on the Media Server
Computer, on page 297 for all media server computers.
In doing so please heed the following sub-steps:
a) In section Adding optional languages on page 299 be sure to install the
b) Copy the content of the directory backed up in step 10 on page 856
into the same path on all media server computers. Personal welcome
prompts that probably existed before the migration will then still be
available.
Section 5.3.3.5, Starting and Rebooting Nodes, on page 311
A31003-S5070-J100-12-7631, 02/2013
859
Please heed the information in the following sections:
Section 5.3.3.6, Resolving Installation Issues, on page 312
Section 5.5, Trouble Ticket, on page 358
and Administration.
page 556 again.
860
A31003-S5070-J100-12-7631, 02/2013

PINs.
23. The upgrade is now complete.
24. If you wish to use more frontend or media server computers in Large
Deployment than were available before the upgrade, you need to follow the
instructions in Section 14.3, Installing additional Frontend Computers, on
page 647 or Section 14.4, Installing additional Media Server Computers, on
page 647.
A31003-S5070-J100-12-7631, 02/2013
861
Upgrading V3 R2 or V6 R0 Small Deployment in Case of only one available LVM2 Partition
15.12 Upgrading V3 R2 or V6 R0 Small Deployment in Case of only one

available LVM2 Partition
This section describes an OpenScape UC Application upgrade for the event that
only one LVM2 partition was used in the LVM2 storage location.
Upgrading Small Deployment, on page 750.
Application does not have an LVM2 partition, follow the instructions in Section
15.10, Upgrading V3 R2 or V6 R0 Small Deployment in Case of an unavailable
LVM2, on page 839.
15.12.1 Upgrading without changing the LVM2

partitions
707 as preparation.
2. Execute the instructions given in Section 15.6.1, Upgrading Small
5. If the partition size must now be adjusted for the OpenScape UC Application
as well as the partition added for the fallback using syncUC, follow the
instructions in Section 15.12.2, Adjusting the LVM2 partitions, on page 863.
If, however, only the partition for the fallback using syncUC must be added,
follow the instructions in Section 15.12.3, Adding a Partition only, on page
879.
862
A31003-S5070-J100-12-7631, 02/2013
15.12.2 Adjusting the LVM2 partitions

This section describes the partition size adjustment for the OpenScape UC
Application and adding the partition for the fallback using syncUC.
1. If there is a partition for backing up a file system (for example /backups),
execute the following sub-steps to delete it.
a) Unmount the partition of the file system backup.
Example:
umount /backups
b) Execute the lvdisplay command:
The following is e. g. put out for the partition of the Volume Group
(example: OpenScapeUC) file system backup of the OpenScape UC
Application:
...
--- Logical volume --LV Name
/dev/OpenScapeUC/backups
VG Name
OpenScapeUC
LV UUID
Upi8lc-IyML-O5Qj-X3EE-OdJz-NQsTg9OWhc
LV Write Access
read/write
LV Status
available
# open
1
LV Size
xx.00 GB
Current LE
12800
Segments
1
Allocation
inherit
Read ahead sectors
auto
- currently set to
1024
Block device
253:2
c) Remove the partition of the file system backup.
Example:
lvremove /dev/OpenScapeUC/backups
Do you really want to remove active logical volume
"backups"? [y/n]:
d) Push the y key.
Logical volume "backups" successfully removed
e) Remove from the /etc/fstab file the line in which this file system has
been configured for permanent mounting. In the following example this is
the last line.
A31003-S5070-J100-12-7631, 02/2013
863
/dev/sda1
swap
/dev/OpenScapeUC/UC /
/dev/sda2
/boot
proc
/proc
sysfs
/sys
debugfs
/sys/kernel/debug
usbfs
/proc/bus/usb
devpts
/dev/pts
/dev/OpenScapeUC/backups /backups
swap
ext3
ext3
proc
sysfs
debugfs
usbfs
devpts
ext3
defaults
acl,user_xattr
acl,user_xattr
defaults
noauto
noauto
noauto
mode=0620,gid=5
acl,user_xattr
0
1
1
0
0
0
0
0
1
0
1
2
0
0
0
0
0
2
The partition of the file system backup and the entry in the /etc/fstab
file will be automatically created again when you back up the file system
the next time.
2. Insert the SLES 11 DVD in the DVD drive and reboot the computer.
864
A31003-S5070-J100-12-7631, 02/2013
3. Select Installation.
4. Activate the check box I Agree to the License Terms and click on Next.
A31003-S5070-J100-12-7631, 02/2013
865
5. Click on Next >.
6. Activate the Repair Installed System radio button and click on Next.
866
A31003-S5070-J100-12-7631, 02/2013
7. Click on Expert Tools.
8. Click on Start Partitioning Tool.
A31003-S5070-J100-12-7631, 02/2013
867
9. Select in the navigator linux > Volume Management > <name of the
volume group> > <name of the volume> and click on Resize....
10. Use the New Logical Volume Size (in GB) field to set the value of the root
partition (/) in the LVM2 storage location for active OpenScape UC Application
operation according to Table 5 on page 118.
If no computer with a hard disk of the size according to Table 5 on page 118
is available, a local, external USB hard disk serves as storage location for the
file system backup. Table 129 on page 869 indicates the partition sizes for this
case.
IMPORTANT: The local, external USB hard disk must have been formatted
with ext3, because NTFS is not natively supported by SLES 11 and FAT32
does not support files bigger than 4 GB.
868
A31003-S5070-J100-12-7631, 02/2013
Partition
Partition
type

Documentation
example1
Calculation Number
2
On the computer
Hard disk
N3
160
Planning Guide
/boot
Primary

boot Partition
Swap
Primary

swap Partition
LVM2 memory
Primary
N-4
156

LVM2 partition
Logical
volume
group
OpenScape
UC

OpenScape UC

Logical
operation of the
UC1
0.95*(N-4)/2 74,1

Logical Volume UC1

means of syncUC
Logical
UC2
0.95*(N-4)/2 74,1

Logical Volume UC2
Temporary snapshot
Logical
0.1*(N-4)/2
0.9*0.95*(N- 66,7
4)/2
7,8

Table 129

A31003-S5070-J100-12-7631, 02/2013
869
Always configure partitions in such a way that the preparation for a fallback
by means of syncUC (see Section 15.2.4, Preparing to the syncUC
Fallback, on page 707) as well as for a fallback by means of file system
backup (see Section 4.5, Configuring the File System Backup, on page 181)
is possible.
870
A31003-S5070-J100-12-7631, 02/2013
A31003-S5070-J100-12-7631, 02/2013
871
13. Click on No.
872
A31003-S5070-J100-12-7631, 02/2013
14. Click on Apply.

IMPORTANT: Minimizing the partition takes quite a while. No progess bar is
displayed. Do not abandon the minimizing process and do not perform any
other actions on this computer in parallel.
15. Click on linux > Volume Management > <name of the volume group>.
A31003-S5070-J100-12-7631, 02/2013
873
click on Next.
874
A31003-S5070-J100-12-7631, 02/2013
19. Enter the size of the partition for falling back using syncUC in the Manual Size
field according to Table 5 on page 118 and click on Next.
case.
is possible.

A31003-S5070-J100-12-7631, 02/2013
875
876
A31003-S5070-J100-12-7631, 02/2013
24. Click on No.
25. Click on Apply.
A31003-S5070-J100-12-7631, 02/2013
877
27. Select Boot from Hard Disk.
28. Log on as user root.

The OpenScape UC Application starts automatically.
Upgrading V3 R2 or V6 R0 Small Deployment with only one available LVM2
partition is now complete.
878
A31003-S5070-J100-12-7631, 02/2013
15.12.3 Adding a Partition only

If you wish to add an LVM2 partition to the computer - even while the OpenScape
UC Application is running -, follow the instructions in this section.
1. Execute the yast command.
2. Open System > Partitioner.
A31003-S5070-J100-12-7631, 02/2013
879
3. Select Yes.
4. Select <computer name> > Volume Management.

5. Push the + key.
6. Select <computer name> > Volume Management > <LVM2-VolumeGroup>.
880
A31003-S5070-J100-12-7631, 02/2013
8. Select Add....
9. Enter the name of the volume, for example UC2, and select Next.
NOTE: This step and the following ones are analog to the instructions in
Section 4.2.2.6, Creating the Logical Volume UC2, on page 136
A31003-S5070-J100-12-7631, 02/2013
881
10. Activate the Manual Size check box.

11. Enter the size of the partition for falling back using syncUC in the Size field
according to Table 5 on page 118 and click on Next.
case.
is possible.
882
A31003-S5070-J100-12-7631, 02/2013
12. Select Finish.
13. Select Next.
A31003-S5070-J100-12-7631, 02/2013
883
14. Select Finish.
15. Select Quit.

Upgrading V3 R2 or V6 R0 Small/Large Deployment with only one available
LVM2 partition is now complete.
884
A31003-S5070-J100-12-7631, 02/2013
Upgrading V3 R2 or V6 R0 Large Deployment in Case of only one available LVM2 Partition
15.13 Upgrading V3 R2 or V6 R0 Large Deployment in Case of only one

available LVM2 Partition
This section describes an OpenScape UC Application upgrade for the event that
only one LVM2 partition was used in the LVM2 storage location.
Upgrading Large Deployment, on page 771.
Application does not have an LVM2 partition, follow the instructions in Section
15.11, Upgrading V3 R2 or V6 R0 Large Deployment in Case of an unavailable
LVM2, on page 851.

707 as preparation.
2. Execute the instructions given in Section 15.6.2, Upgrading Large
LVM2 partitions
3. If the partition size must now be adjusted for the OpenScape UC Application
as well as the partition added for the fallback using syncUC on the computers,
a) Terminate the OpenScape UC Application on the media server
computers:
b) Stop the MRCP service, the Nuance TTS and the Nuance ASR, if
available, on the media server computers:
c) Terminate the OpenScape UC Application on the frontend computers:
d) Terminate the OpenScape UC Application on the application computer:
A31003-S5070-J100-12-7631, 02/2013
885
Upgrading V3 R2 or V6 R0 Large Deployment in Case of only one available LVM2 Partition
e) Execute the instructions given in Section 15.12.2, Adjusting the LVM2

partitions, on page 863 on the application computer.
f)
Follow the instructions in Section 15.12.2, Adjusting the LVM2

partitions, on page 863 on the frontend computers.
g) Follow the instructions in Section 15.12.2, Adjusting the LVM2

partitions, on page 863 on the media server computers.
4. If, however, only the partition for the fallback using syncUC must be added on
the computers, execute the following sub-steps:
a) Execute the instructions given in Section 15.12.3, Adding a Partition
only, on page 879 on the application computer.
b) Follow the instructions in Section 15.12.3, Adding a Partition only, on
page 879 on the frontend computers.
c) Follow the instructions in Section 15.12.3, Adding a Partition only, on
page 879 on the media server computers.
886
A31003-S5070-J100-12-7631, 02/2013
Migration from V7 Integrated Deployment to V7 Small Deployment
15.14 Migration from V7 Integrated Deployment to V7 Small Deployment

IMPORTANT: OpenScape UC Application V7 Integrated Deployment supports
only a connection to OpenScape Voice V6 or V7. Migrating OpenScape UC Application V7 Integrated Deployment with OpenScape Voice V6 or V7 to OpenScape
UC Application V7 Small Deployment with OpenScape Voice V6 or V7 R0 is
supported.
In contrast, migrating OpenScape UC Application V6 R0 or earlier Integrated
Deployment with OpenScape Voice to OpenScape UC Application V7 Small
Deployment with OpenScape Voice V6 or V7 directly is not supported. Instead,
migrate to OpenScape UC Application V7 Integrated Deployment and then
migrate to OpenScape UC Application V7 Small Deployment.
If, however, you cannot upgrade to OpenScape UC Application V7 Integrated
Deployment because the old V7 hardware is not supported, migrate to V6 R0 or
older Small Deployment including a simultaneous hardware change and then
upgrade to V7 Small Deployment.
Table 120 on page 746 provides an overview of upgrading and migrating options
for Integrated Deployment.
1. Provide as target system the application and PBX computer that comply with
the requirements described in the planning guide.
2. Contact the support to obtain the latest version of the UNSPmigration<version number>.rpm file.
3. Note down the password of the Solid DB of the installed Integrated
Deployment. You will need it later in step 9b on page 890 when installing the
Small Deployment.
4. Follow the instructions given in Section 15.3, Updating the Application
Computer, on page 711 for updating to the current version (fix release,
hotfix).
5. Follow the instructions given in Section 5.4.2, Checking with Rapidstat UC,
on page 349 to check whether some important system configuration
container, database availability) work correctly.
6. As the case may be, you find E/A Cockpit configuration files on the application
computer. Store the following of them in a safe location lest they are deleted
or overwritten during the migration.
a) Store files with the .eag extension in the following directory:
/opt/siemens/HiPathCA/WebSpace/Portal/webapps/eacockpit-osc/WEBINF/groups
A31003-S5070-J100-12-7631, 02/2013
887
b) The following file:

/opt/siemens/HiPathCA/WebSpace/Portal/webapps/eacockpit-osc/WEBINF/eacockpit.properties
7. Backing up private welcome prompts

The directory
/enterprise/mediaserver/application_host/deployment/userresources/res/
contains possibly available personal welcome prompts for OpenScape UC
Application users. Back up the contents of this directory in a safe location lest
it is deleted or overwritten during migration.
888
A31003-S5070-J100-12-7631, 02/2013
Migrating the PBX

8. Please obtain the instructions for migrating the OpenScape Voice from the
setup and upgrade guide of the OpenScape Voice (OpenScape Voice
Service Manual, Volume 1, Installation and Upgrades).
NOTE: In the appropriate passages, it refers to Section 15.14, Migration
from V7 Integrated Deployment to V7 Small Deployment, on page 887 of the
setup and upgrade guide of the OpenScape UC Application V7.
Migrating the PBX from the old application computer to the new PBX
computer includes
the data export from the PBX to the old application computer,
the new installation of the PBX and
the data import in the PBX on the new computer.
NOTE: The data to be exported is not only used for import in the new PBX
but also for import in the new OpenScape UC Application.
NOTE: When migrating the OpenScape UC Application from the deployment

scenario Integrated Deployment to Small Deployment, the PBX deployment
scenario changes from Integrated Simplex to Standard Duplex.
A31003-S5070-J100-12-7631, 02/2013
889
Installing the new OpenScape UC Application

9. When installing OpenScape UC Application on the new application computer
according to sections Chapter 2, General Preparations up to and including
Chapter 5, Installing the OpenScape UC Application, please heed the
following points:
a) Install exactly the same version (fix release, patchset, hotfix) you updated
in step 4 on page 887 and from which you exported data in step 8 on page
889.
b) When editing the response file /root/knut.responsefile.txt in
step 11 on page 201 be sure to enter the same password you noted down
in step 3 on page 887.
c) Perform the installation according to Section 5.3.2, Installing the Small
d) In sections Adding optional languages on page 270 and Adding optional
applications on page 267 you can install any supported RPM packages
for which you have a license.
Perform this installation now.
890
A31003-S5070-J100-12-7631, 02/2013
Importing data in the new OpenScape UC Application

10. Log on to the new application computer as root.
11. Stop OpenScape UC Application:
13. If you exported data in step 8 on page 889 via USB stick, mount it on the
14. Copy the export.tar file created in step 8 on page 889 from the directory
of the old application computer or USB stick to the /tmp directory on the new
15. Import the data by the following command:
/opt/siemens/servicetools/install/bin/customizeImage.sh -v migrate <response path> <TAR
path> 2>&1 | tee migration.log
<response path> is the absolute path to the /root/

knut.responsefile.txt response file created in step 9 on page 890.
<TAR path> is the absolute path to the export.tar file copied in step
14 on page 891.
Example:
/opt/siemens/servicetools/install/bin/customizeImage.sh -v migrate /root/
knut.responsefile.txt /tmp/export.tar 2>&1 | tee migration.log
16. As the case may be, E/A Cockpit configuration files (backed up in step 6 on
page 887) were on the application computer before the migration. Restore
them.
17. Restoring the private Welcome Prompts
Copy the private welcome prompts backed up in step 7 on page 888 to the
following directory:
A31003-S5070-J100-12-7631, 02/2013
891
Configuring the new OpenScape UC Application

20. Wait several minutes before logging on to the CMP. If you cannot log on,
terminate the OpenScape UC Application, reboot it, wait several minutes and
log on to the CMP.
21. Verify that the ports listed in Table 55 on page 388 are open on the application
computer and the ports listed in Table 56 on page 395 are open on the PBX
computers.
22. Execute the instructions given in Section 6.3.1, Opening Port 1040 on the
PBX Computer, on page 480.
23. Open Configuration > OpenScape Voice > General > Switches > <name
of the PBX> > General in the CMP.
a) Click on the Change IP Address button.
b) Enter the IP address of the PBX's computer in the IP address of node 1
field.
c) Enter the password of user srx in the srx password field.
d) Click on the Save button.
e) Click on the Test Connection button to test the connection to the first
node. If the test fails, check whether the access is allowed by executing
the instructions in the setup guide of the OpenScape Voice in section
Verify Remote Access for srx Account in a Standard Duplex. After the
check, click on the Test Connection again. Click on the Save button after
a successful test.
f)
24. SIP Trunk between OpenScape Voice and the media server
For the media server side:
892
A31003-S5070-J100-12-7631, 02/2013

b) Click on the small triangle to the right of the connection entry and select
Edit... or click on the Media Server entry in the Name column.
c) Click on IP Telephony (SIP).
A31003-S5070-J100-12-7631, 02/2013
893
d) In the SIP Servers section, click on the entry in the ID column. If no entry
is available yet, click on the Add... button.
894
A31003-S5070-J100-12-7631, 02/2013
e) If the following command is executed as user root in a command line on

the OpenScape Voice computer, the IP addresses of the signaling
managers for LSM, CSTA, SIP, CCM and SIP TLS of every OpenScape
Voice computer are put out.
#/unisphere/srx3000/srx/startup/srxqry
Execute this command on the OpenScape Voice computer.
Example output:
LSM
Vip: 10.235.10.22
Up
CSTA
Vip: 10.235.12.115 Up
SIP
Vip: 10.235.12.102 Up
CCM 0.5
Vip: 10.235.12.109 Up
SIP TLS Auth Vip: 10.235.12.104 Up

The IP address of the SIP signaling manager (in the example
10.235.12.102) is required in the next step.
If the OpenScape Voice is a duplex system, a second IP address is
required for SIP. This is the IP address of the SIP signaling manager of
the second OpenScape Voice computer, which will be used in the
Alternative SIP servers section in the next step.
f)
Enter the IP address of the SIP signaling manager of the OpenScape

Voice in the Remote Host Name (FQDN / IP Address) field.
A31003-S5070-J100-12-7631, 02/2013
895
If you have clicked on the Add... button, enter an input ID in the ID field
additionally.
If the OpenScape Voice has a second computer, click in the Alternative
SIP servers section on the entry (if available) or on the Add... button and
enter the IP address of the SIP signaling manager of the second
computer.
Save all modifications.
For the PBX side:
g) See the administrator documentation OpenScape UC Application
Configuration and Administration, section Configuring the SIP Trunk in
OpenScape Voice.
25. BCOM for CSTA access from the application computer to the PBX computer
a) Open Configuration > Unified Communications > Configuration >
Connections > OS Voice in the CMP.
b) Click on the small triangle to the right of the connection entry and select
Edit... or click on the PBX entry in the Name column.
896
A31003-S5070-J100-12-7631, 02/2013
c) In the CSTA access configuration section, enter the IP address of the

PBX computer(s) in the IP/Hostname field and, if required, also in the IP/
Hostname (alternative) field.
e) If the name of the connection to the OpenScape Voice in the CMP under
Configuration > Unified Communications > Configuration >
Connections > OS Voice does not correspond to the OpenScape Voice
name displayed in the CMP under Configuration > OpenScape Voice >
General > Switches, activate under Configuration > OpenScape
Voice > General > Switches the check box that precedes the
OpenScape Voice name and click on the Refresh Switch Data button.
Open Configuration > Unified Communications > Configuration >
Connections > OS Voice and check whether the correct name of the
connection to the OpenScape Voice is now displayed.
26. You cannot use transfer conferences after the migration. You must delete and
reconfigure them. Therefore, execute the instructions in the section
Configuring the Transfer Conference in the administrator documentation
A31003-S5070-J100-12-7631, 02/2013
897
Check
27. Follow the instructions given in Section 5.4.2, Checking with Rapidstat UC,
on page 349 to check whether some important system configuration
container, database availability) work correctly.
898
A31003-S5070-J100-12-7631, 02/2013
Migration from V7 Small Deployment to V7 Large Deployment
15.15 Migration from V7 Small Deployment to V7 Large Deployment

This section describes the migration of V7 Small Deployment to V7 Large
Deployment with only one frontend computer and only one media server
computer. If you wish to use several frontend or media server computers in Large
Deployment, you need to subsequently follow the instructions given in Section
14.3, Installing additional Frontend Computers, on page 647 or Section 14.4,
Installing additional Media Server Computers, on page 647.
Preparations
1. Verify that the setup medium you want to use for migrating was also deployed
for setting up, updating or upgrading to Small Deployment, from which you
now wish to migrate.
It will be required in step 21 on page 905.
on the media server computers:
5. When the Openfire server is installed, execute the following command on the
computer that hosts the Openfire server:
6. Back up the entire system (harddisk and database). Please obtain the
instructions for performing the backup from Section 15.2.4.2, syncUC
Commands, on page 707 or from the administrator documentation
OpenScape UC Application Configuration and Administration, section
Backing up and restoring the System.
7. Use the following command to determine which languages have been
installed and note them down for using them in step 49 on page 912:
osc-setup se -i --match-any announ uc-tts uc-asr languagepack
If this command fails, make sure that a repository in osc-setup is provided
(see Section 15.2.2, Providing the Update/Upgrade Sources in a Repository
in osc-setup, on page 671).
A31003-S5070-J100-12-7631, 02/2013
899

S | Name
| Summary
| Type
| package
| package
...
| package
| package
...
i | mediaserver_autoattendant_languagepack_EN-US| Mediaserver AutoAttendant L-> | package
| mediaserver_autoattendant_languagepack_ES-ES| Mediaserver AutoAttendant L-> | package
...
| Mediaserver VoicePortal->| package
...
| mediaserver_voiceportalspeech_languagepack_DE-DE| Mediaserver VoicePortalS->| package
i | mediaserver_voiceportalspeech_languagepack_EN-US| Mediaserver VoicePortalS->| package
...
...
i | uc-asr
| Meta rpm to install all A->| package
| uc-asr-de_de
| German speech recogniti->| package
| uc-asr-en_us
| American English speech ->| package
i | uc-asrcore
| Meta rpm to install Nua-> | package
...
i | uc-tts
| Meta rpm to install all ->| package
| uc-tts-de_de
| German tts voice.
|
package ts-en_gb
| British English tts voice.| package
| uc-asr-en_us
| American English speech ->| package
...
| uc-tts-zh_cn
| Chinese Mandarin tts voi->| package
i | uc-ttscore
| Meta rpm to install Nuan->| package

8. As the case may be, you find E/A Cockpit configuration files on the application
computer. Store the following of them in a safe location lest they are deleted
or overwritten during the migration.
a) Store files with the .eag extension in the following directory:
/opt/siemens/HiPathCA/WebSpace/Portal/webapps/eacockpit-osc/WEBINF/groups
b) The following file:

/opt/siemens/HiPathCA/WebSpace/Portal/webapps/eacockpit-osc/WEBINF/eacockpit.properties
900
A31003-S5070-J100-12-7631, 02/2013
9. The directory
contains possibly available personal welcome prompts for OpenScape UC

Application users. Copy the content of this directory to a temporary directory
lest it is deleted or overwritten during the migration. It will be copied to the
media server computer in step 52 on page 913.
IMPORTANT: You need to execute this step before the migration script is
started in step 11 on page 902.
10. Execute the instructions given in Section 15.2.2, Providing the Update/
Upgrade Sources in a Repository in osc-setup, on page 671 on the
A31003-S5070-J100-12-7631, 02/2013
901
Migration on the application computer

IMPORTANT: The migration on the application computer must be performed
before the installations on the frontend computer and media server computer.
11. Execute the migration script:
cd /opt/siemens/servicetools/install/bin/migration
bash migrateSmallToLarge.sh migrate
executed and closing the actual input window (<Ctrl>+A+D) to resume the
The script executes the following actions:
a) It prompts you for the display and computer name of the frontend and
media server computer.
The display name in the CMP corresponds to the variable
SI_LOCAL_NAME in the response file /tmp/
knut.responsefile.txt <computer name> to be created by the
script.
The computer name corresponds to the variable SI_LOCAL_HOST in this
file (compare step 26 on page 210 and step 41 on page 215 of the Large
Deployment setup. Contrary to the setup, the response file is not edited
manually here but only the names written in the response file by the script
are mentioned .
b) It creates a response files for the frontend and media server computers
(/tmp/knut.responsefile.txt <computer name>).
c) It creates the /tmp/knut.file.dar file required for the setup on the
d) It adds the frontend and media server computer to the opt/siemens/
common/conf/system.xml file.
902
A31003-S5070-J100-12-7631, 02/2013
12. IMPORTANT: Be sure to store the internal response file

of Large Deployment in a safe location. The response file is not currently
contained in the system backup sets, but it is needed to rebuild the system
during a crash recovery.
Back up the internal response file
/opt/siemens/servicetools/install/conf/responsefile.txt.sav
of the previously installed Small Deployment in a safe location.

according to Section 15.3.2.1, Small Deployment, on page 727 if applicable.
Example output:
checking Arguments
Option clean: yes
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
A31003-S5070-J100-12-7631, 02/2013
903
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Example:
rm -R /tmp/tmpRepo
IMPORTANT: This step is mandatory prior to performing the setup on the
frontend or media server computer.

904
A31003-S5070-J100-12-7631, 02/2013
Installation on the frontend computer

NOTE: You can perform the installation on the frontend and media server
computer parallel.
16. Execute the instructions given in Section 5.3.3.2, Requirements for Installing
17. Log on to the frontend computer as root.
18. The following command copies the DAR file created in step 11c on page 902
from the application computer to the frontend computer:
scp <name of the application computer>:/tmp/knut.file.dar /root/knut.file.dar
19. The following command copies the response file created in step 11b on page
902 from the application computer to the /root directory on the frontend
computer and renames it as knut.responsefile.txt.
IMPORTANT: Make sure you copy the response file that carries the name of
this frontend computer in its file name (<name of the frontend
computer>) you have entered in step 11a on page 902 for this frontend
computer.
In step 11b on page 902, a response file was created for the frontend and
media server computer each.
scp <name of the application computer>:/tmp/knut.responsefile.txt_<name of the frontend

computer> /root/knut.responsefile.txt
SI_SYMPHONIA_ADMIN_PASSWORD=<PLACEHOLDER_symphonia_admin_password>
A31003-S5070-J100-12-7631, 02/2013
905
- At least one digit

23. Find out which of the following installation files provided on the setup medium
of the OpenScape UC Application you need.
24. Mount the required Repository ISO file according to the following pattern:
Example:

bash /mnt/support/checkResponsefileOnLocalNode.sh



and

default. If you wish to check another file, use the file name as parameter of
the script invocation.
26. Unmount the installation source:
umount /mnt
906
A31003-S5070-J100-12-7631, 02/2013
frontend computer.
osc-setup in OpenScapeUC_Large_FE
osc-setup now determines the packages required for the installation.
Restoring system sources...
Parsing metadata for oscD1...
Parsing RPM database...
Summary:
<install> [S1:0][package]symphonia-2.2_5.3.1-060.i586
<install> [S1:0][package]symphonia-activemq-2.2_5.3.1-060.noarch
<install> [S1:0][package]CA2-OSC-WEB-FRONTEND-3.2_109.0.0-39.23184.i586
<install> [S1:0][package]scs_eventbroker-2.2_5.3.1-060.noarch
...
<install> [S1:0][package]OpenScapeUC_Large_FE-3.2_0.9.0-151.noarch
<install> [S1:0][package]scs_conferencing_common-3.1_7.13.0-790.noarch
Continue? [y/n]:
according to Section 15.3.2.2, Large Deployment and Very Large
Deployment, on page 730 if applicable.
Example output:
A31003-S5070-J100-12-7631, 02/2013
907

checking Arguments
Option clean: yes
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Example:
rm -R /tmp/tmpRepo
33. As the case may be, E/A Cockpit configuration files (backed up in step 8 on
page 900) were on the application computer before the migration. Restore
them now on a frontend computer.
IMPORTANT: Remember that these files are now on a computer the IP
address of which differs from the one of the computer that hosted the files
before the migration. Please obtain the necessary reconfiguration steps from
the installation guide OpenScape UC Application Executive/Assistant
Cockpit.
908
A31003-S5070-J100-12-7631, 02/2013
A31003-S5070-J100-12-7631, 02/2013
909
Installation on the media server computers

NOTE: You can perform the installation on the frontend and media server
computer parallel.
35. Execute the instructions given in Section 5.3.3.2, Requirements for Installing
36. Log on to the media server computer as root.
37. The following command copies the DAR file created in step 11c on page 902
from the application computer to the media server computer:
scp <name of the application computer>:/tmp/knut.file.dar /root/knut.file.dar
38. The following command copies the response file created in step 11b on page
902 from the application computer to the /root directory on the media
server computer and renames it as knut.responsefile.txt.
IMPORTANT: Make sure you copy the response file that carries the name of
this media server computer in its file name (<name of the media server
computer>) you have entered in step 11a on page 902 for this media server
computer.
In step 11b on page 902, a different response file was created for every
frontend and media server computer.
scp <name of the application computer>:/tmp/knut.responsefile.txt_<name of the media

server computer> /root/knut.responsefile.txt
word>
910
A31003-S5070-J100-12-7631, 02/2013

mount -o loop OpenScapeUcSuiteApps-Repository-<version number>.iso /mnt
Example:

bash /mnt/support/checkResponsefileOnLocalNode.sh



and

default. If you wish to check another file, use the file name as parameter of
the script invocation.
44. Unmount the installation source:
umount /mnt
A31003-S5070-J100-12-7631, 02/2013
911
server computer.
osc-setup in OpenScapeUC_Large_MS
osc-setup now determines the packages required for the installation.
Restoring system sources...
Parsing metadata for oscD1...
Parsing RPM database...
Summary:
<install> [S1:0][package]LoquendoManagementConsole-7.1.13-0.i386
<install> [S1:0][package]mediaserver_voiceportal-1.2_0.16.0-14.i586
<install> [S1:0][package]scs_faultmgmt_base-2.2_5.3.1-060.noarch
<install> [S1:0][package]LoquendoSpeechSuite-7.0.6-0.i386
<install> [S1:0][package]LoquendoRTPProvider-7.4.11-0.i386
...
<install> [S1:0][package]LoquendoMRCPv1Server-7.4.12-0.i386
<install> [S1:0][package]symphonia-2.2_5.3.1-060.i586
<install> [S1:0][package]LoquendoTTS-en-7.4.1-1.i386
<install> [S1:0][package]symphonia-loquendo-all-0.1-2.i386
<install> [S1:0][package]symphonia-loquendo-tts-0.1-2.i386
<install> [S1:0][package]symphonia-loquendo-0.1-2.i386
Continue? [y/n]:
49. If you found out while executing step 7 on page 899 that additional languages
were installed for the voice portal before the migration, you need to reinstall
them now. Execute the instructions given in Section 14.2, Installing
additional Voice Portal Languages, on page 639 for these languages.
50. Install all required voice conference languages that were installed before the
migration (see step 7 on page 899):
912
A31003-S5070-J100-12-7631, 02/2013
Example:
osc-setup in scs_conferencing_languagepack_en_us
migrated OpenScape UC Application, you need to reconfigure the address
according to Section 15.3.2.2, Large Deployment and Very Large
Deployment, on page 730 if applicable.
52. Copy the content of the directory backed up in step 9 on page 901
to the same path on the media server computer. Personal welcome prompts
that probably existed before the migration will then still be available.
Example output:
checking Arguments
Option clean: yes
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
A31003-S5070-J100-12-7631, 02/2013
913

Example:
rm -R /tmp/tmpRepo
54. On the media server computer, start the MRCP service, the Nuance TTS and
the Nuance ASR:
55. Execute the following command on the media server computer:
56. Perform the media server configuration according to the administrator
Execute in particular the following sub-steps:
a) Follow the instructions in section Configuring the SIP Trunk in

OpenScape Voice.
b) Follow the instructions in section Configuring the SIP Trunk in the

OpenScape Media Server.
c) You need to reconfigure all address bindings, for example conferencingdefault, LocalParkSlot, voiceportal-guest and voiceportal-start,
under CMP > Configuration > Unified Communications > Media
Server > Address Binding.
d) Add further applications possibly available and created with the
Application Builder.
e) You need to reconfigure the trusted transfer of the OpenScape
Xpressions under CMP > Configuration > Unified Communications >
Media Server > Applications > Voiceportal > start (Voice Portal
access) > Operation Mode.
914
A31003-S5070-J100-12-7631, 02/2013
f)
In the OpenScape Xpressions server, you need to change the phone

number of the remote trusted domain according to the phone number
displayed in the OpenScape UC Application under CMP >
Configuration > Unified Communications > Media Server > Address
Binding > voiceportal-start in the Address-expression field.
See the administrator documentation OpenScape Xpressions Server
Administration for details about the phone number of the remote trusted
domain.
g) You cannot use transfer conferences after the migration. You must delete
and reconfigure them. Therefore, execute the instructions in the section
Configuring the Transfer Conference in the administrator
documentation OpenScape UC Application Configuration and
Administration.
A31003-S5070-J100-12-7631, 02/2013
915
Migration from V7 Small Deployment to V7 Very Large Deployment
15.16 Migration from V7 Small Deployment to V7 Very Large Deployment

This migration is not yet supported.
15.17 Migration from V7 Large Deployment to V7 Very Large Deployment

This section describes the migration of V7 Large Deployment to V7 Very Large
Deployment with only one frontend computer and only one media server
computer.
We divide this migration in the following major steps:
Export on the application computer and backing up further data
New installation of the OpenScape UC Application including the operating

system and the partitions on the application computer
NOTE: Uninstalling the OpenScape UC Application is not supported.
Import on the application computer and restoring further data
Applying the new response files and the new DAR file on all frontend
computers and media server computers.
NOTE: There is no need anymore to make a new installation of the
OpenScape UC Application on all frontend computers and all media server
computers.
916
A31003-S5070-J100-12-7631, 02/2013
Migration from V7 Large Deployment to V7 Very Large Deployment
Migration preparations
up data (for example backing up using the CMP, backing up of FQDNs,
IP addresses and personal greeting prompts). Be sure to back up such
data on a separate computer and not on the application computer as
this computer plus operating system will be completely reinstalled.
1. Verify that the setup medium you want to use for migrating was also deployed
for setting up, updating or upgrading to Large Deployment, from which you
now wish to migrate.
2. Determine the version of the currently installed OpenScape UC Application
according to Section 15.1, Determining the Source Version, on page 662. It
is especially important whether a hotfix is installed since this will cause some
additional steps when reinstalling the OpenScape UC Application. Note down
the exact version (major release, minor release, fix release, hotfix and build
number).
4. OpenScape UC Application uses automatically generated self-signed
certificates per default. If you use them, no special step for these certificates
has to be done now since these certificates are automatically regenerated
during the migration.
However, if you use certificates signed by a trusted Root CA, save these
certificates and all PKI material (Public Key Infrastructure), i. e. private keys
etc., to a separate computer now. They need to be restored after the migration
See Appendix A, Configuring a Certificate Strategy, in the administrator
manual OpenScape UC Application Configuration and Administration, for
details about certificates.
the application computer, on all frontend computers and all media server
computers:
on the media server computers:
A31003-S5070-J100-12-7631, 02/2013
917
7. Back up the entire system (harddisk and database). The administrator

section Backing up and restoring the System, describes how to perform this
backup.
NOTE: Since the application computer will be newly installed, using syncUC
(see Section 15.2.4.2, syncUC Commands, on page 707) is not advisable.
IP addresses
Host names
FQDN
Community names
Community String.
Port
example)
these this computers:
You will need such values when creating new response files for the new
application computer or the frontend computers and media server computers
computer.
Example:
osc-setup se -i --match-any hpum
918
A31003-S5070-J100-12-7631, 02/2013

317 on this.
10. Store the content of the following directory you find on the application
computer in a safe location lest it is overwritten during the migration:
/opt/siemens/common/conf/diagnostic_configurations
IMPORTANT: This location must not be on the application computer.
11. Export the OpenScape UC Application on the application computer:
bash /opt/siemens/servicetools/install/bin/migration/exportToVeryLarge.sh <path>
<path> is an already existing directory in which the export file
OpenScapeLarge_Export.tar is created.
If you do not use the <path> parameter the export file
OpenScapeLarge_Export.tar is created in the /tmp directory.
executed and closing the actual input window (<Ctrl>+A+D) to resume the
12. Back up this file. It will be imported after the new installation of the application
computer.
A31003-S5070-J100-12-7631, 02/2013
919
Preparing the installation

steps do not exist on the computer to be newly installed.
new installation of exactly the same version (major release, minor release, fix
release, hotfix and build number) of the OpenScape UC Application as it was
before the migration:
NOTE: Your are not redirected to this section here when you have gone
through the chapters and sections indicated by the following links. This is
valid for other links in this section here as well.
If you use the Acrobat Reader, the key combination <ALT> + <Left arrow key>
goes to the previous page.
System
Ensure especially that the perl-XML-XPath RPM is installed on the
application computer, the frontend computers and the media server
computers (see step 52 on page 140).
920
A31003-S5070-J100-12-7631, 02/2013

14. Make sure that the needed information that you noted down in step 8 on page
918, has been copied to locations outside the /root/knut.* files on the
application computer, all frontend computers and all media server computers.
15. Delete the response files on the application computer, all frontend computers
and all media server computers:
rm /root/knut.*
If there are no /root/knut.* files, an error message is displayed. Ignore it.
and all media server computers by creating the appropriate response files
according to Section 5.2.2.3, Example of Deployment Scenario Very Large
Deployment, on page 218, especially the following steps:
NOTE: Your are not redirected to this section here when you have gone
through the chapters and sections indicated by the following links. This is
valid for other links in this section here as well.
Step 8 on page 220
Step 9 on page 220
Step 10 on page 221
Step 22 on page 224
Step 23 on page 225
Step 24 on page 225
Step 25 on page 225
Step 37 on page 230
Step 38 on page 230
Step 39 on page 230
Step 40 on page 231
A31003-S5070-J100-12-7631, 02/2013
921
Migration on the Application Computer

17. Make sure that the reponsefile that you have created in step 16a on page 921
is available as /root/knut.responsefile.txt on the application
computer.
18. Execute the instructions given in Section 15.2.2, Providing the Update/
Upgrade Sources in a Repository in osc-setup, on page 671.
IMPORTANT: Make sure that you provide a repository for creating exactly
the same version of the OpenScape UC Application that existed before the
migration. If any hotfix was installed, it is especially important that exactly the
same hotfix can now be installed again.
osc-setup in OpenScapeUC_VeryLarge_BE
21. If you want to check whether a package has been installed, execute a
command according to the following pattern:
osc-setup se -i --match-any <part of the RPM name>
Example:
osc-setup se -i --match-any OpenScapeUC_
additional RPM:
922
A31003-S5070-J100-12-7631, 02/2013

IMPORTANT: Install the optional applications that were installed on the application computer before the migration (see step 9 on page 918) also.

IMPORTANT: For Very Large Deployment the OpenScape UC Application must

be connected to an OpenScape Xpressions (XPR). The RPM
osc-setup se --match-any OpenBranch hpum
S | Name
| Summary
| Type
--+-------------------------------+--------------------------------+-------| CLM
| package
| package
| package
following command:
IMPORTANT: Neither scs_osc_officecommunicator_be (Office
Communicator Connector, see Chapter 11, Connecting the Microsoft Office
Communication Server/Microsoft Lync Server) nor symphoniaA31003-S5070-J100-12-7631, 02/2013
923
openfire-base or symphonia-openfire (Openfire server) must be

installed on the application computer. In case of Very Large Deployment, an
Openfire server must definitely be installed on a separate computer (see
Chapter 12, Infrastructure) on which the MySQL database is installed also.

com
configurations
lib
Frameworks.

924
A31003-S5070-J100-12-7631, 02/2013
IMPORTANT: For Very Large Deployment the OpenScape UC Application
must be connected to an OpenScape Xpressions (XPR). The RPM
Install this RPM with the following command:
A31003-S5070-J100-12-7631, 02/2013
925

If you do not wish to install an RPM package of the OpenScape UC Application
anymore and if you need not search for an RPM package, execute the steps in
this sub-section.
Example output:
checking Arguments
Option clean: yes
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
Unmounting...
Removing...
26. Delete the directory of the temporary repository.
Example:
rm -R /tmp/tmpRepo
926
A31003-S5070-J100-12-7631, 02/2013
on page 928.
A31003-S5070-J100-12-7631, 02/2013
927

CLUSTER=<clusterId>
You assigned a value to the SI_COMMUNITY_NAME parameter in the /
root/knut.responsefile.txt file on the application computer. This
value was automatically assigned to the CLUSTER parameter during the
OpenScape UC Application installation on the application computer.

928
A31003-S5070-J100-12-7631, 02/2013
Migration
29. Execute the data import, i. e. the actual migration:
bash /opt/siemens/servicetools/install/bin/migration/importToVeryLarge.sh <path>
<path> is the absolute path to the OpenScapeLarge_Export.tar file you

backed up in step 10 on page 919.
30. Restore the content of the following directory you backed up in step 10 on
page 919 on the application computer:
/opt/siemens/common/conf/diagnostic_configurations
31. Start the OpenScape UC Application on the application computer:
A31003-S5070-J100-12-7631, 02/2013
929
Post-Processing
Before you can migrate on the frontend computers or media server computers,
the following requirements need to be met.
32. On the application computer, OpenScape UC Application must be up and
running.
Wait for approximately 5 minutes after the OpenScape UC Application has
computer:

SYMPHONIA_LOG: null
...
BUILD SUCCESSFUL
...
IMPORTANT: Do not continue until the command has returned BUILD

SUCCESSFUL.
930
A31003-S5070-J100-12-7631, 02/2013

system time.
A31003-S5070-J100-12-7631, 02/2013
931

used.
932
A31003-S5070-J100-12-7631, 02/2013
Migration on the Frontend Computers

NOTE: You can execute the steps on the frontend computers and media server
computers in parallel.
37. Start the OpenScape UC Application on all frontend computers:
38. Create a repository in osc-setup without any hotfix on all frontend
computers and media server computers according to Section 5.3.1,
Providing the Installation Sources in an Installation Repository in osc-setup,
on page 234. You need at least the Repository ISO file and the Base ISO file.
39. If a hotfix was installed before the migration, copy the entire hotfix ISO file
onto the hard disk of all frontend computers.
40. Make sure that the response files that you have created in step 16b on page
921 and the DAR file that you have copied in step 36 on page 932 are in the
/root directory on all frontend computers.
41. Execute the actual migration on all frontend computers:
bash /opt/siemens/servicetools/install/bin/migration/migrateLargeToVeryLarge.sh <path>
Only if a hotfix had been installed for the OpenScape UC Application before
the migration, the <path> parameter is needed. It is the path to the hotfix ISO
file (OpenScapeUcSuiteApps_PATCH-<version>.iso).
42. Start the OpenScape UC Application on all frontend computers.
A31003-S5070-J100-12-7631, 02/2013
933
Migration on the Media Server Computers

NOTE: You can execute the steps on the frontend computers and media server
computers in parallel.
43. Start the OpenScape UC Application on all media server computers:
44. Create a repository in osc-setup without any hotfix on all media server
computers according to Section 5.3.1, Providing the Installation Sources in
an Installation Repository in osc-setup, on page 234. You need at least the
Repository ISO file and the Base ISO file.
45. If a hotfix was installed before the migration, copy the entire hotfix ISO file
onto the hard disk of all media server computers.
46. Make sure that the response files that you have created in step 16c on page
921 and the DAR file that you have copied in step 36 on page 932 are in the
/root directory on all media server computers.
47. Execute the actual migration:
bash /opt/siemens/servicetools/install/bin/migration/migrateLargeToVeryLarge.sh <path>
Only if a hotfix had been installed for the OpenScape UC Application before
the migration, the <path> parameter is needed. It is the path to the hotfix ISO
file (OpenScapeUcSuiteApps_PATCH-<version>.iso).
48. Start the OpenScape UC Application on all media server computers.
934
A31003-S5070-J100-12-7631, 02/2013
Restarting, Checking and Configuring

NOTE: Your are not redirected to this section here when you have gone through
the chapters and sections indicated by the following links. This is valid for other
links in this section here as well.
50. OpenScape UC Application uses automatically generated self-signed

certificates per default. If you use them, no special step for these certificates
has to be done now since these certificates automatically have been
regenerated during the migration.
However, if you use certificates signed by a trusted Root CA, you have saved
these certificates and all PKI material (Public Key Infrastructure), i. e. private
keys etc., to a separate computer in step 4 on page 917 before the migration.
They need to be restored now. As an alternative, you can create new
certificates.
See Appendix A, Configuring a Certificate Strategy, in the administrator
manual OpenScape UC Application Configuration and Administration, for
details about certificates.
page 556 again.
52. Openfire server
a) Very Large Deployment requires the OpenScape UC Application to be
mandatorily connected to an Openfire server.
The Openfire server must have been installed on a separate computer
(see Section 12.2, Infrastructure, on page 596). If this has not been
done yet, follow the instructions in Section 12.4, Installing the Openfire
Server on the Instant-Messaging Server Computer, on page 600.
A31003-S5070-J100-12-7631, 02/2013
935
b) Even if the Openfire server was installed on a separate computer before

the migration, you need to perform a new installation according to Section
12.4, Installing the Openfire Server on the Instant-Messaging Server
Computer, on page 600. A Solid database was used before the migration
but a MySQL database after the migration.
c) If the OpenScape UC Application was connected to an Openfire server
before the migration, you need to import the presence data for Openfire:
Unpack the OpenScapeLarge_Export.tar file:
tar -xvf <path>/OpenScapeLarge_Export.tar
Copy the presence data from the presence sub-directory of unpacked
files:
cp
cp
cp
cp
presence/SYMPRESENCE_SYMACL.dat /opt/openfire/preconfig/solid-backup
presence/SYMPRESENCE_SYMACL.ctr /opt/openfire/preconfig/solid-backup
presence/SYMPRESENCE_SYMPRESENCESTATUS.dat /opt/openfire/preconfig/solid-backup
presence/SYMPRESENCE_SYMPRESENCESTATUS.ctr /opt/openfire/preconfig/solid-backup
d) Follow the instructions in the following sections:
Section 12.5, Initial Configuration of the Openfire Server, on page

602
Section 12.6, Configuring the Openfire Server, on page 615
e) Follow the instructions in the following sections of the administrator

documentation OpenScape UC Application Configuration and
Administration:
Creating Packet Filter Rules in OpenScape Voice
Configuring an IM Address for OpenScape Users
Creating and synchronizing Openfire User Accounts
Configuring the Cluster Networking for Very Large Deployment
53. Migration is now complete.

54. If you wish to use more frontend or media server computers in Very Large
Deployment than were available before the migration, you need to follow the
page 647.
936
A31003-S5070-J100-12-7631, 02/2013
Upgrading a 32-bit System to a 64-bit System
15.18 Upgrading a 32-bit System to a 64-bit System

This section describes how to back up and subsequently restore an OpenScape
UC Application with Small Deployment and Large Deployment on a new
operating system for upgrading from a 32-bit operating system to a 64-bit
operating system.
15.18.1 Preparations
1. Check whether the requirements in Section 4.1, File System and Operating
System, on page 116 can be complied with for the operating system SLES
11 SP1 or SP2 to be installed in the 64-bit version.
IMPORTANT: Do not follow the instructions given Section 4.1, File System
and Operating System, on page 116 yet!
Use the following command for determining the SLES version used:
VERSION = 11
PATCHLEVEL = 1
2. We recommend to execute the Rapidstat UC program on the application
computer to check the configuration performed so far and basic features (see
Section 5.4.2, Checking with Rapidstat UC, on page 349).
A31003-S5070-J100-12-7631, 02/2013
937
15.18.2 Ugrading HiPath 8000 Assistant V3.0 32-bit to

OS UC Appl. V3 R2 with OSV V4 R1 DVD5 64-bit
For upgrading a HiPath 8000 Assistant V3.0 32-bit to a 64-bit system you need
to upgrade to the OpenScape UC Application V3 R2 with OpenScape Voice V3.1
R3 DVD 8 first and then execute the instructions given in Section 15.18.3,
Upgrading from OS UC Appl. V3 R2 with OSV V3.1 R3 32-bit or OSV V4 R1 32bit to 64-bit, on page 940.
15.18.2.1 Backing up Data

Perform a data backup according to the instructions given in the V3.1 R3 DVD8
release notes.
15.18.2.2 Upgrade
1. Update the installed OpenScape UC Application to the last patch set and
hotfix of the OpenScape UC Application V3 R2 with OpenScape Voice
V3.1 R3 DVD8. Follow the instructions of the corresponding release notes for
this purpose.
2. Now execute the instructions given in Section 15.18.3, Upgrading from OS
UC Appl. V3 R2 with OSV V3.1 R3 32-bit or OSV V4 R1 32-bit to 64-bit, on
page 940.
15.18.2.3 Falling back to HiPath 8000 Assistant V3.0 32-bit

If you cannot correctly complete executing step 2 on page 938 in Section
15.18.2.2, Upgrade, on page 938, follow the instructions given in Section
15.18.3.3, Falling back to the original Version with 32-bit, on page 943.
If you cannot correctly complete executing step 1 on page 938 in Section
15.18.2.2, Upgrade, on page 938, execute the following steps:
1. Reinstall SLES 9 SP3 on the application computer.
2. Install the HiPath 8000 Assistant V3.0. Please obtain the required information
from the release notes on the HiPath 8000 Assistant V3.0 DVD.
4. Stop the Solid DB:
bash /etc/init.d/solid.sh stop
You can ignore the following message:
938
A31003-S5070-J100-12-7631, 02/2013
SOLID Communication Error 21308: Connection is broken (TCP/

IP)
5. Restore the Solid DB:
cp /software/backup/solid.db /enterprise/solid45/solid/RtpDb
6. Remove all *.log files from the following directory:
rm -f /enterprise/solid45/solid/RtpDb/*.log
7. Start the Solid DB.
bash /etc/init.d/solid.sh start
8. Open the backed up file ClmSettings.xml in an editor.
This file contains the configuration for the client's remote access to the CLM
(Customer License Manager).
9. Copy the IP addresses entered in this file to the following file:
/opt/siemens/clm/ApacheTomcat/ClmSettings.xml
10. Save the modified file.
12. Wait for two minutes before you log on to the CMP.
In you cannot log on to the CMP, execute command
, wait for another two minutes and then try to log on to the CMP once more.
A31003-S5070-J100-12-7631, 02/2013
939
15.18.3 Upgrading from OS UC Appl. V3 R2 with OSV

V3.1 R3 32-bit or OSV V4 R1 32-bit to 64-bit
15.18.3.1 Backing up Data
IMPORTANT: The software version (DVD, patch set/fix release and hotfix) of
data. Restoring data on a software version different from the one used for backing
up data is not supported.
1. Update the installed OpenScape UC Application to the last patch set/fix
release and hotfix, for example OpenScape UC Application V3 R2 with
OpenScape Voice V3.1 R3 DVD8 FR5 HF2 or OpenScape UC Application V3
R2 with OpenScape Voice V4 R1 DVD3 PS5 HF9.
2. Perform a data backup according to the administrator documentation
OpenScape UC Application V3 Configuration and Administration, section
Backup and Restoration Concept. Use the CMP for this purpose and heed
the following points:
Select the backup type DATA.
Verify that all available options except for HiPath8000:<PBX computer

name> (example: HiPath:ATHENSFT) are selected.
If you have questions, please contact the support.
3. If you have used the default archive you find the data backup in the /var/
siemens/backup/ directory.
Copy the data backup to a safe location.
The private welcome prompts in the directory
/opt/siemens/mediaserver/application_host/resources/waveRoot/voiceportalgreetings
are backed up automatically in the process.
4. Copy the response file of the initial installation to a safe location.
940
A31003-S5070-J100-12-7631, 02/2013
5. If the CLM (Customer License Manager) is installed, copy the file /opt/
licenses/clm/ApacheTomcat/ClmSettings.xml to a safe location.
This file contains the access configuration to the CLM.
6. Note down the IP address, the fully qualified domain name and the computer
name (host name) of the application computer.
15.18.3.2 Upgrade
1. Install the operating system SLES 11 SP1 or SP2 in the 64-bit version
considering the following points:
Use of the same hardware.
Information and instructions in Section 4.1, File System and Operating

System, on page 116.
In doing so use the IP address, the fully qualified domain name and the
computer name (host name) of the application computer you noted down
Depending on the hardware (IBM x3650T, FSC TX150 or FSC RX 330)

used you find information about setting up the operating system in the
corresponding sub-section of section Installing SLES OS with
appropriate service pack onto the External Applications Server in the
OpenScape Voice documentation.
2. IMPORTANT: Be sure to install exactly the same software version (DVD,

patch set/fix release and hotfix) (for example OpenScape UC Application V3
R2 with OpenScape Voice V3.1 R3 DVD8 FR5 HF2 or OpenScape UC
Application V3 R2 with OpenScape Voice V4 R1 DVD3 PS5 HF9) you
installed in step 1 on page 940 and in which you backed up data in step 3 on
page 940. Follow the instructions given in the corresponding setup an
upgrade guide, consider the information in the corresponding release notes
and use the response file backed up in step 4 on page 940.
3. Only if the software version mentioned in step 2 has been reached, proceed
with the following steps.
4. Copy the directories and files backed up in step 3 on page 940 to the directory
/var/siemens/backup/.
5. Restore the access configuration to the CLM and start OpenScape UC
Application by executing steps 5 on page 801 to 10 on page 802. Use the file
ClmSettings.xml backed up in step 5 on page 941 for this purpose.
A31003-S5070-J100-12-7631, 02/2013
941
6. Using the CMP, restore the data according to the administrator

section Backing up and restoring OpenScape System Components. In
doing so please heed the following points:

7. Execute the following command to restart OpenScape UC Application:
8. Check whether all previous configurations, data and features have been
restored.
9. Perform an update to OpenScape UC Application V3 R2 with OpenScape
Voice V4 R1 DVD5 HF1 or later by following the instructions given in section
"Updating to a new DVD" of the V3 R2 installation guide.
10. If you upgrade Large Deployment from 32-bit to 64-bit you need to execute
the following steps:
a) Replace all frontend computers by 64-bit computers and install the
frontend services, see the following chapters of the V3 R2 installation
guide:
Chapter "Virtualization" (only for virtual computers)
Chapter "Preparing the Server Applications"
Chapter Installing the OpenScape UC Application
a) Replace all media server computers by 64-bit computers and install the
media server services, see the following chapters of the V3 R2
installation guide:
942
Chapter "Virtualization" (only for virtual computers)
Chapter "Preparing the Server Applications"
A31003-S5070-J100-12-7631, 02/2013
Chapter Installing the OpenScape UC Application
NOTE: All frontend and media server computers can be installed in parallel.
They must be installed after the application computer, though.
15.18.3.3 Falling back to the original Version with 32-bit

1. Install the 32-bit operating system you used in step 1 on page 940.
2. Restore the OpenScape UC Application in exactly the same version (DVD,
patchset/fix release and hotfix, for example OpenScape UC Application
V3 R2 with OpenScape Voice V3.1 R3 DVD8 FR5 HF2 or OpenScape UC
Application V3 R2 with OpenScape Voice V4 R1 DVD3 PS5 HF9) that you
backed up in step 2 on page 940.
3. Perform a data backup according to the administrator documentation
OpenScape UC Application Configuration and Administration, section
Backup and Restoration Concept, in the CMP. In doing so please heed the
following points:

A31003-S5070-J100-12-7631, 02/2013
943
Changing the Hardware for V7 Small Deployment
15.19 Changing the Hardware for V7 Small Deployment

This section describes how to change the hardware of the application computer.
Other modifications will not be made.
The major hardware change steps are:
Backing up data of the OpenScape UC Application (no file system backup) on

the computer with the old hardware
Complete reinstallation of the OpenScape UC Application V7 including SLES

and LVM2 partitions on the target computer with the new hardware
IMPORTANT: The new hardware can also be a virtual computer. It is irrelevant whether the original computer with the old hardware is a real or virtual
computer.
Backing up Data
IMPORTANT: In the following you will be repeatedly prompted to back up
data (for example backing up data using the CMP, backing up of FQDNs, IP
addresses and personal greeting prompts). Be sure not to back up such
data on the application computer but on a separate computer as the application computer plus operating system will be completely reinstalled.
1. Execute the instructions given in Section 15.1, Determining the Source
Version, on page 662 as preparation. After the hardware has been changed,
the new installation will be performed for exactly the same version.
2. Be sure to use the setup medium with which you reached the current level of
Small Deployment for the new installation also.
944
A31003-S5070-J100-12-7631, 02/2013

Administration.
NOTE: Since the application computer is newly installed, using syncUC (see
Section 15.2.4.2, syncUC Commands, on page 707) instead of a data
backup is not advisable.
6. Note down the following application computer data:
IP address
Host name
FQDN
A31003-S5070-J100-12-7631, 02/2013
945
Community name
Community String.
example)
these computers:
computer.
Example:
267 on this.
If the command fails, the installation source is not provided in osc-setup. See
Section 5.3.1, Providing the Installation Sources in an Installation Repository
in osc-setup, on page 234 or Section 14.1, Installing additional RPM
Packages of the OpenScape UC Application, on page 637 for details.
8. Use the following command on the application computer to determine which
languages have been installed and note them down for use in step 13 on
page 952:
946
A31003-S5070-J100-12-7631, 02/2013
...
S | Name
| Summary
| Type
| package
| package
...
| package
| package
...
package
package
...
package
package
package
package
...
package
package
...
package
package
package
...
A31003-S5070-J100-12-7631, 02/2013
947
i | uc-asr
package
| uc-asr-de_de
package
| uc-asr-en_us
package
i | uc-asrcore
package
...
i | uc-tts
package
| uc-tts-de_de
package
| German tts voice.
| uc-tts-en_gb
package
| uc-asr-en_us
package
...
| uc-tts-zh_cn
package
i | uc-ttscore
package
...
9. The directory
on the application computer contains possibly available personal welcome

directory. It will be copied to the newly installed application computer in step
13 on page 952.
948
A31003-S5070-J100-12-7631, 02/2013

steps do not exist on the computer to be newly installed.
NOTE: In this sub-step and in the ensuing ones, we refer to the computer with
the new hardware when we speak of the application computer.
new installation of the OpenScape UC Application:
NOTE: Use during the preparations the IP address, the computer name and
the FQDN you noted down in step 6 on page 945.
System
A31003-S5070-J100-12-7631, 02/2013
949
Partition
Partition
type

Documentation
example1
Calculation Number
2
On the computer
Hard disk
N3
160
Planning Guide
/boot
Primary

boot Partition
Swap
Primary

swap Partition
LVM2 memory
Primary
N-4
156

LVM2 partition
Logical
volume
group
OpenScape
UC

OpenScape UC

Logical
operation of the
UC1
0.95*(N-4)/2 74,1

Logical Volume UC1

means of syncUC
Logical
UC2
0.95*(N-4)/2 74,1

Logical Volume UC2
Temporary snapshot
Logical
0.1*(N-4)/2
0.9*0.95*(N- 66,7
4)/2
7,8

Table 130

950
A31003-S5070-J100-12-7631, 02/2013

11. Configure the installation for the application computer according to Section
5.2.2.1, Example of Deployment Scenario Small Deployment, on page 198.
In doing so be sure to use the data you noted down in step 6 on page 945.
Step 8 on page 200
Step 9 on page 201
Step 10 on page 201
A31003-S5070-J100-12-7631, 02/2013
951
Installations
13. Execute the instructions given in Section 5.3.2, Installing the Small
In doing so heed the following:
a) Install the optional applications that were installed on the application
computer (see step 7 on page 946) before the OpenScape UC
Application V7 was set up, too.
b) In section Adding optional languages on page 270 be sure to install the
c) Copy the content of the directory backed up in step 9 on page 948
into the same path on the application computer. Personal welcome

prompts that probably existed before the installation will then still be
available.
Heed the information in section Section 5.5, Trouble Ticket, on page 358.
and Administration.
page 556 again.
952
A31003-S5070-J100-12-7631, 02/2013

18. Changing the hardware is now complete.
A31003-S5070-J100-12-7631, 02/2013
953
Changing the Hardware for V7 Large Deployment and Very Large Deployment
15.20 Changing the Hardware for V7 Large Deployment and Very Large
Deployment
This section describes how to change the hardware of the application computer.
Other modifications will not be made.
The major hardware change steps are:
Backing up data of the OpenScape UC Application (no file system backup) on

the computers with the old hardware
Complete reinstallation of the OpenScape UC Application V7 including SLES

and LVM2 partitions on the target computers with the new hardware
IMPORTANT: The new hardware can also be virtual computers. It is irrelevant whether the original computers with the old hardware are real or
virtual computers.
Backing up Data
IMPORTANT: In the following you will be repeatedly prompted to back up
data (for example backing up data using the CMP, backing up of FQDNs, IP
addresses and personal greeting prompts). Be sure to back up such data
on a separate computer and not on the application computer, on the
frontend computers or media server computers as such computers plus
operating system will be completely reinstalled.
1. Execute the instructions given in Section 15.1, Determining the Source
Version, on page 662 as preparation. After the hardware has been changed,
the new installation will be performed for exactly the same version.
2. Be sure to use the setup medium with which you reached the current level of
Large Deployment or Very Large Deployment for the new installation also.
which was used upon setting up Large Deployment (see step 7 on page 204).
954
A31003-S5070-J100-12-7631, 02/2013

Administration.
NOTE: Since the application computer, the frontend computers and media
server computers are newly installed, using syncUC (see Section 15.2.4.2,
syncUC Commands, on page 707) instead of a data backup is not
advisable.
A31003-S5070-J100-12-7631, 02/2013
955
IP addresses
Host names
FQDN
Community names
Community String.
Port
example)
these computers:
computer.
Example:
284 on this.
If the command fails, the installation source is not provided in osc-setup. See
Section 15.2.2, Providing the Update/Upgrade Sources in a Repository in
osc-setup, on page 671 for details.
8. Use the following command on the media server computer to determine
which languages have been installed and note them down for use in step 16
on page 963:
956
A31003-S5070-J100-12-7631, 02/2013

...
S | Name
| Summary
| Type
| package
| package
...
| package
| package
...
package
package
...
package
package
package
package
...
package
package
...
package
package
package
...
A31003-S5070-J100-12-7631, 02/2013
957
i | uc-asr
package
| uc-asr-de_de
package
| uc-asr-en_us
package
i | uc-asrcore
package
...
i | uc-tts
package
| uc-tts-de_de
package
| German tts voice.
| uc-tts-en_gb
package
| uc-asr-en_us
package
...
| uc-tts-zh_cn
package
i | uc-ttscore
package
...
958
A31003-S5070-J100-12-7631, 02/2013
9. The directory
on the media server computers contains possibly available personal welcome

directory. It will be copied to the newly installed media server computer in step
16 on page 963.
A31003-S5070-J100-12-7631, 02/2013
959

NOTE: In this sub-step and in the ensuing ones, we refer to the computers with
the new hardware when we speak of the application computer, frontend computer
and media server computer.
10. Prepare the application computer, the frontend computers and media server
computers according to the following sections for a new installation of the
System
960
A31003-S5070-J100-12-7631, 02/2013
Partition
Partition
type

Documentation
example1
Calculation Number
2
On the computer
Hard disk
N3
160
Planning Guide
/boot
Primary

boot Partition
Swap
Primary

swap Partition
LVM2 memory
Primary
N-4
156

LVM2 partition
Logical
volume
group
OpenScape
UC

OpenScape UC

Logical
operation of the
UC1
0.95*(N-4)/2 74,1

Logical Volume UC1

means of syncUC
Logical
UC2
0.95*(N-4)/2 74,1

Logical Volume UC2
Temporary snapshot
Logical
0.1*(N-4)/2
0.9*0.95*(N- 66,7
4)/2
7,8

Table 131


A31003-S5070-J100-12-7631, 02/2013
961

and all media server computers according to Section 5.2.2.2, Example of
Deployment Scenario Large Deployment, on page 203.
In doing so be sure to use the data you noted down in step 6 on page 956 in
the following sub-steps.
Step 8 on page 205
Step 10 on page 205
Step 11 on page 206
Step 24 on page 210
Step 25 on page 210
Step 26 on page 210
Step 27 on page 210
962
Step 39 on page 214
Step 40 on page 215
Step 41 on page 215
Step 42 on page 215
A31003-S5070-J100-12-7631, 02/2013
Installations
13. Execute the instructions given in Section 5.3.3.1, Installation on the
Application Computer, on page 281.
IMPORTANT: The installation on the application computer must be
performed before the installations on the frontend computer and media server
computer.
Install the optional applications that were installed on the application
computer before the migration (see step 7 on page 956) also.
14. Execute the instructions in Section 5.3.3.2, Requirements for Installing
15. Execute the instructions in Section 5.3.3.3, Installation on the Frontend
Computer, on page 293 for all frontend computers.
16. Execute the instructions in Section 5.3.3.4, Installation on the Media Server
Computer, on page 297 for all media server computers.
In doing so please heed the following sub-steps:
a) In section Adding optional languages on page 299 be sure to install the
b) Copy the content of the directory backed up in step 9 on page 959
into the same path on all media server computers. Personal welcome
prompts that probably existed before the migration will then still be
available.
Section 5.3.3.5, Starting and Rebooting Nodes, on page 311
A31003-S5070-J100-12-7631, 02/2013
963
and Administration.
page 556 again.
21. Changing the hardware is now complete.
22. If you wish to use more frontend or media server computers in Large
Deployment than were available before the upgrade, you need to follow the
page 647.
964
A31003-S5070-J100-12-7631, 02/2013
Migration from OpenScape ComAssistant to OpenScape UC Application
15.21 Migration from OpenScape ComAssistant to OpenScape UC

Application
15.21.1 General
This section describes the migration of user-related data from an OpenScape
ComAssistant V2.0 to an OpenScape UC Application.
NOTE: In this section, CA is the abbreviation for OpenScape ComAssistant, not
for Certificate Authority.
OpenScape ComAssistant
Migration OpenScape UC Application
CA user:
User data
- Login data
- Contact information
- Single sign-on
Personal address book
Call journal entries
Voicemail access via
OpenScape Xpressions
-->
UC user:
User data
- Login data
- Contact information
- Single sign-on
Private contact entries
Call journal entries
Voicemail access via OpenScape
Xpressions
CA teams
-->
Group entry in private contact list for

each team member
CA shared address books
-->
Address entries ready for import into

the OpenScape UC Application
OpenScape Web Client
Table 132
Migration from OpenScape ComAssistant to OpenScape UC

Application
The migration is done by executing the following main migration steps. A specific
migration tool is needed for each of these steps:
User Migration
The user migration tool creates a UC user including his contact data and, if
applicable, his SSO configuration for every CA user. The UC user has the
respective device assigned as ONS. The UC user entries are written into a
file that can be imported to the OpenScape UC Application by using the CMP.
The migrated CA users are written into a CA Management Portal importable
file to disconnect the CA user from the PBX.
The successful execution of this tool is a mandatory step before the other
tools can be executed.
A31003-S5070-J100-12-7631, 02/2013
965
Personal Address Book Migration

Entries in a personal address book of a CA user have among other things a
name, a phone number and a mail address. The name and the phone number
or the name and the mail address of an entry might match the name and the
phone number or the name and the mail address of a UC user.
If this is the case, the PABS (personal address books) migration tool migrates
these personal address book entries of these CA users to private contacts of
the corresponding UC users.
Shared Address Book Migration

Entries in a shared address book of a CA user have among other things a
name, a phone number and a mail address. The name and the phone number
or the name and the mail address of an entry might match the name and the
phone number or the name and the mail address of a UC user or a global
contact, e. g. connected to the OpenScape UC Application by an LDAP
directory.
If this is the case, the SABS (shared address books) migration tool migrates
these shared address books entries into an file that is importable to the
A filter depending on the number of CA users that access a shared address
book can be configured.
When the address book entries have been imported into the OpenScape UC
Application OpenScape Web Client, these entries are members of an
address group in the users private contact list. The prefix of the address
group name can be configured.
Team Migration
A CA user can own a team. This owner determines the team members and
their access rights. These team members might match UC users or global
contacts, e. g. connected to the OpenScape UC Application by an LDAP
directory. The match criteria are
first name and last name or
first name, last name and phone number.
If they match, the team migration tool migrates these members of a CA team
to entries in the personal contact list of a UC user corresponding to the CA
team owner user. These personal contact list entries are assigned to the
Teamview address group. The prefix of the address group name can be
configured.
The UC user corresponding to the CA team owner user has access to the
presence status of the UC users corresponding to the CA team member
users without asking them for permission.
966
A31003-S5070-J100-12-7631, 02/2013
Call Journal Migration

The journal migration tool migrates call journal entries of a CA user to call
journal entries of a UC user.
OpenScape Xpressions Access Migration

The Xpressions migration tool migrates CA users having access to an
OpenScape Xpressions server to the corresponding UC users having access
to t hat OpenScape Xpressions server.
15.21.2 General Restrictions

CA business groups are not migrated.
Due to some architectural differences of the team implementation in OpenScape
ComAssistant V2.0 and OpenScape UC Application V7 R1, the team migration
tool migrates OpenScape ComAssistant teams into a private contact list of a UC
user, but it does not migrates OpenScape ComAssistant teams to OpenScape
UC Application teams.
The Professional Services Center of Competence UC provides support for
analysis of OpenScape ComAssistant team data and OpenScape ComAssistant
team data migration.
A31003-S5070-J100-12-7631, 02/2013
967
15.21.3 Preparations
15.21.3.1 Software
1. One of the following operating systems must run on the CA migration
computer, i. e. the computer the migration tools should be executed on:
Windows XP Professional SP3 or higher, 32-bit, including all security

patches and update patches
Windows 7, all editions, with the latest SP, 32-bit, including all security
Windows 7, all editions, with the latest SP, 64-bit, including all security
2. Sun Java SE JRE 1.6.0_30 or higher must be installed.

3. Recommended tools:
Notepad++ for editing text files (http://notepad-plus-plus.org)
4. Using the CMP, back up the data and the file system according to the
Administration, section Backing up and restoring OpenScape System
Components.
NOTE: Please also note Section 15.2.4, Preparing to the syncUC Fallback,
on page 707.
5. Back up the OpenScape Voice according to the section Backup & Restore
in the service documentation OpenScape Voice Service Manual.
968
A31003-S5070-J100-12-7631, 02/2013
15.21.3.2 Documentation
You need the following documentations:
Administrator documentation OpenScape UC Application Configuration and

Administration, e. g section LDAP Connection (see step 6 on page 973)
Service manual HiPath CAP V3.0 Common Application Platform, section

Exporting data (see step 4 on page 987) and section Importing data (see
The following documentations might be needed for further details:
Administrator documentation OpenScape Xpresssions Server

Administration, section Database-Correl-Tool (DbTool) (see step 1 on page
1024 and step 11 on page 1026)
Administrator documentation OpenScape Common Management Platform

Administration, section How to Export Data for CMP (Common Management
Platform) (see step 1 on page 986)
A31003-S5070-J100-12-7631, 02/2013
969
15.21.3.3 Environment
1. You need a running OpenScape UC Application V7 R1 and a connected PBX.
2. The following computers are involved in the OpenScape ComAssistant
migration to OpenScape UC Application:
Computer
Description
Necessity
CA migration computer
The computer the CA migration tools are installed on (see Section

15.21.3.4, Installing the Migration Tools, on page 974).
Mandatory
CA MySQL computer
The CA MySQL database typically is installed on a different computer

Optional
than the CA migration tools. In this case, remote access to this database
must be granted (see step 7 on page 987).
PBX computer
The computer the PBX is installed on. CA users must be disconnected

from the PBX (see step 10b on page 998 and step 1 on page 1028)
Application computer of the

The UC users the CA user will be migrated to will be stored in a database Mandatory
on this computer.
OpenScape Xpressions
computer
Import and export of users to the OpenScape Xpressions must be done Mandatory or
(see step 1 on page 1024 and step 11 on page 1026). If the OpenScape optional1
Xpressions has satellite computers, these actions must be executed on
the kernel computer.
Computers with firewalls

between the computers above
If there are firewalls between the above computers in this table, certain
ports must be open. See the following steps for details.
Table 133
Mandatory
Optional
Computers involved in the CA Migration
1 Mandatory for Very Large Deployment, optional for Small Deployment and Large Deployment
970
A31003-S5070-J100-12-7631, 02/2013
Ports to be opened
3. Ensure that the following ports are open on the CA migration computer:
All Deployment Scenarios: CA Migration Computer
Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
Any
TCP
I/O
Application
computer
3306
Database connector to the MySQL Only needed for Very Large

database of the OpenScape UC
Deployment since only this deployment
Application
scenario uses a MySQL database
instead of a Solid database on the
Any
TCP
I/O
CA MySQL
database
computer
3306

MySQL database
Any
TCP
Application
computer
4709
SOAP/HTTPS access of the CA

migration computer to the
Any
TCP
I/O
CA MySQL
database
computer
8170

Only needed for exporting users to user

end devices (CA export).
Only needed if the MySQL database is
not on the CA migration computer.
This port is used for importing and
exporting purposes, see step 4 on page
Any
TCP
I/O
CA MySQL
database
computer
8470


This port is used for importing and
exporting purposes, see step 4 on page
Any
TCP
I/O
Application
computer
16760
Database connector to the Solid

Application
Only needed for Integrated

Deployment, Small Deployment and
Large Deployment since only these
deployment scenarios use a Solid
database instead of a MySQL database
Table 134
Comment

Ports to be opened on the CA Migration Computer
A31003-S5070-J100-12-7631, 02/2013
971
4. If the CA MySQL database is not installed on the CA migration computer,

ensure that the following ports are open on the CA MySQL database
computer:
All Deployment Scenarios: CA MySQL Database Computer
Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
3306
TCP
I/O
CA
migration
computer
Any

MySQL database
8170
TCP
I/O
CA
migration
computer
Any


8470
TCP
I/O
CA
migration
computer
Any


Table 135
Comment
5. Ensure that the following ports are open on the application computer of the
All Deployment Scenarios: Application Computer
Port
Trans
port
proto
col
I/O1 Partner
computer
Partner
port
Protocol / use
3306
TCP
I/O
CA
migration
computer
Any
Database connector to the MySQL Only needed for Very Large

Deployment since only this deployment
Application
scenario uses a MySQL database
instead of a Solid database.
4709
TCP
CA
migration
computer
Any
SOAP/HTTPS access of the CA

migration computer to the
16760
TCP
I/O
CA
migration
computer
Any
Database connector to the Solid

Application
Table 136
Comment
Only needed for Integrated

Deployment, Small Deployment and
Large Deployment since only these
deployment scenarios use a Solid
database instead of a MySQL
database.
972
A31003-S5070-J100-12-7631, 02/2013
LDAP
If a contact data evaluation via LDAP is required, the following conditions for the
access to a connected LDAP directory must be fulfilled:
6. An LDAP directory to be connected is installed and is in operation.
7. A connection to the LDAP directory is configured in the OpenScape UC
Application.
8. A field mapping (LDAP directory database field names to OpenScape UC
Application field names) is configured.
9. A connection test on OpenScape UC Application to the LDAP directory has
been successfully executed.
See the section LDAP Connection in the administrator documentation
OpenScape UC Application Configuration and Administration for a detailed
description about how to configure the connection to the LDAP directory.
A31003-S5070-J100-12-7631, 02/2013
973
15.21.3.4 Installing the Migration Tools

1. Execute the following sub-steps to download the installation file for the
migration tools from the Software Supply Server (SWS):
a) Login to the SWS.
the top of the web page when you are logged in to the SWS. You need
the EXPERT role. The ADVANCED role and the BASIC role are not sufficient.
b) Search for the product number P30152-P1576-A1.
c) Download the CA2UCMigration-<version>.zip installation file.
2. Extract this file into a free directory on the CA migration computer, i. e. the
installation directory <ca_install> of the migration tools, e. g.
C:\CA_Migration.
This creates the needed files and subdirectories:
974
common.properties
A31003-S5070-J100-12-7631, 02/2013
This is the common configuration file for all migration tools. This file defines
the used base path, used subdirectories and predefinitions for the input and
output files.
*.jar
The java archive files (ca_user.jar, ca_pabs.jar, ca_sabs.jar,
ca_team_partner.jar etc ) containing the executable migration tools.
run.bat
This is the MS-DOS shell script to execute the migration tools.
log4j.xml and log4.dtd

These are files for the logging configuration of the migration tools.
migration_common.jar
Library for all migration tools
You find the following subdirectories in the installation directory of the migration
tools:
lib
The Java libraries used by the migration tools
input
The default directory for the input files of a migration, e. g. location of the CA
export files and UC export files
output
The default directory for the generated output files
logs
The default directory for log files and error files
tools_config
The directory containing configuration files for additional helper tools for the
migration
common_config
This directory contains configuration information that is used by all migration
tools.
common_config\ucaccess.properties
This file contains the needed info to access the OpenScape UC
Application server.
common_config\LongLivedStatement.txt
A31003-S5070-J100-12-7631, 02/2013
975
This file contains the security statement for the communication with the
OpenScape UC Application backend.
common_config\datadef
This directory contains property files describing the columns of the table
based input and output of the migration tool chain. E. g. the
CAUserDefinition.properties file describes the column structure
from a user export via OpenScape ComAssistant Management Portal.
common_config\templates
This directory contains the Apache Velocity templates which are used if a
migration tool generates file based output. E. g. the
standard_csv_header_template.vm file describes the layout for a
single row as a CSV file.
<migration_tool_name>_config
These directories contain migration tool specific configuration files. E. g. the
ca_user_config subdirectory contains the configuration files for the
ca_user.jar migration tool.
These subdirectories contain at least one configuration file which is named
like the migration tool itself, e.g. ca_user.properties for the example
above. This is the main configuration file defining migration tool wide
properties.
976
A31003-S5070-J100-12-7631, 02/2013
15.21.3.5 Connecting to the OpenScape UC Application

The migration tools require access to the OpenScape UC Application for
migrating the CA data and for validating contact data. Therefore, a
LongLivedStatement must be generated in the OpenScape UC Application and
the access to the OpenScape UC Application must be configured.
Creating the LongLivedStatement
1. The required files and directories for creation the LongLivedStatement are in
the following directory on the CA migration computer:
<ca_install>\statement
2. Execute the following sub-steps on the application computer:
a) Copy all files from the <ca_install>\statement\backend directory on
the CA migration computer into the following directory on the application
computer:
/software/generate-statement
Using the WinSCP program is one option to do so.
b) Go into this directory:
cd /software/generate-statement
c) Execute the following command:
bash createLongLivedStatement_be.sh
This creates the SymphoniaStatement.cfg file. This file is needed for
creating the LongLivedStatement.
3. Execute the following sub-steps for Large Deployment and for Very Large
Deployment only:
a) Copy all files from the <ca_install>\statement\backend directory on
the CA migration computer into the following directory on one of the frontend computers. If there are several front-end computers, it does not
matter which one you choose:
Using the WinSCP program is one option to do so.
b) Copy the SymphoniaStatement.cfg file from application computer
into the following directory on the same front-end computer:
A31003-S5070-J100-12-7631, 02/2013
977
4. Execute the following sub-steps to create the LongLivedStatement. For Small

Deployment execute them on the application computer, for Large
Deployment and Very Large Deployment execute them on the frontend
computer:
a) Go into this directory:
cd /software/generate-statement
b) Create the LongLivedStatement:
bash createServiceStatement_fe.sh
This creates a LongLivedStatement.txt file containing the security
statement in the same directory.
5. Copy this file into the <ca_install>\common_config directory on the CA
migration computer that has been created in Section 15.21.3.4, Installing the
Migration Tools, on page 974.
Configuration
The configuration of the connection to the OpenScape UC Application is done by
using the file <ca_install>\common_config\ucaccess.properties.
The following properties can be set:
Property
Description
Necessity
UCServer
IP address of the application computer of the OpenScape UC Application

No host name or FQDN is permitted here.
Example: <entry key="UCServer">10.11.12.13</entry>
Mandatory
UCServerPort
Port on the application computer used for the communication the migration tools
Default value: 4709
Example: <entry key="UCServerPort">4709</entry>
Mandatory
UCServerProtocol
Communication protocol for the communication via UCServerPort

Default value: https
Example: <entry key="UCServerProtocol">https</entry>
Mandatory
UCDomain
Domain name of the OpenScape UC Application.

This is not the domain name of the application computer.
Default: system
Example: <entry key="UCDomain">system</entry>
Mandatory
UseLDAPDirectory
Indicator whether an LDAP directory is used

Default value: true
Example: <entry key="UseLDAPDirectory">false</entry>
Optional
Table 137
978
The common_config\ucaccess.properties File
A31003-S5070-J100-12-7631, 02/2013
Property
Description
Necessity
LDAPConnectors
ID(s) of the LDAP connector to be used in an LDAP request. These IDs can be found
for the LDAP Connector Service in the CMP in the ID column at Configuration >
Unified Communication > Accounts > Contact Settings > Global List.
Mandatory
Example: <entry key="LDAPConnectors">svc-ldapconnector</entry>

Multiple IDs are separated by a comma (,).
Example: <entry key="LDAPConnectors">svc-ldapconnector1,svcldapconnector2</entry>
WriteToUCServer
Table 137
If this property is set to true, the results will be deployed to the OpenScape UC
Mandatory
Application. If the property is set to false, the results will be logged. This property
applies for the private address book migration, the call journal migration and the team
migration.
Default value: true
Example: <entry key="UseLDAPDirectory">false</entry>
The common_config\ucaccess.properties File
6. An entry according to the following pattern must be added to the hosts file
on the CA migration computer:
<IP address of the application computer> <Host name/FQDN of the application computer>
Example:
10.11.12.13 MyOsuca
The hosts file typically is in the following directory:
A31003-S5070-J100-12-7631, 02/2013
979
C:\WINDOWS\system32\drivers\etc
NOTE: You retrieve the host name of the application computer by executing
the hostname command on the application computer. You retrieve the FQDN
by executing the hostname -f command.
NOTE: You must edit the hosts file in any case, even if the CA migration
computer uses a DNS server.
NOTE: If the host name or FQDN has been used in the /root/
repsonsefile.txt file for setting the parameters
SI_PRIMARY_NODE_HOST, SI_LOCAL_HOST and SI_DB_HOST (see
Section 5.2.2, Procedure, on page 198), the host name or the FQDN of the
application computer is shown in the CMP under Maintenance > Inventory >
Nodes & Applications > Nodes and Maintenance > Inventory > Nodes &
Applications > Applications in the IP address/Hostname column:
980
A31003-S5070-J100-12-7631, 02/2013
Verification
7. Check the access to the connected LDAP directory and the attribute mapping
using the contactfinder tool.
It is possible to use the following search criteria:
Given name, middle name and last name
Phone number
OpenScape UC Application user ID
You can define the values of these criteria in the

<ca_install>\tools_config\contactfinder.properties file.
If you search for a last name or a phone number you can use these criteria
as a parameter when calling the contactfinder tool instead of using the
contactfinder.properties file (see step 8 on page 982).
The <ca_install>\tools_config\contactfinder.properties file can
contain the following properties:
Property
Description
Necessity
givenNameToFind
Search an entry by the given name.

Example: <entry key=" givenNameToFind ">Carl</entry>
Optional
middleNameToFind
Search an entry by the middle name.

Example: <entry key="middleNameToFind">Mark</entry>
Optional
lastNameToFind
Search an entry by the last name.

Example: <entry key="lastNameToFind">North</entry>
Optional
numberToFind
Search an entry by the phone number.
Optional
The phone number may be a phone number in global number format (GNF,
e. g. +4989744123) or not (e. g. 4989744123 or extension number 123).
The phone number search value must match the phone number value that
had been entered in the LDAP directory.
Note: The search value 123 delivers a match, if the value in the LDAP
directory is e. g. +4989744123 or 4989744123 or 123.
Example: <entry key="numberToFind">+4989744123</entry>
symUserToFind
Table 138
Search an entry by the OpenScape UC Application user ID.

Example:
<entry key="symUserToFind">carl.north@system</entry>
Optional
The tools_config\contact.properties File
A31003-S5070-J100-12-7631, 02/2013
981
The following example explains how the search criteria are handled, if more
than one criterion is used. Assuming all example values in Table 138 on page
981 have been entered, the contactfinder tool delivers the following users:
All users that have the first name Carl, the middle name Mark and the
last name North
or have
the phone number +4989744123
or have
the OpenScape UC Application ID carl.north@system.
Execution
8. If you use the configuration file, enter one of the following commands in a
command prompt in the <ca_install> directory:
run contactfinder
or
run cf
If you do not use the configuration file but you use a call parameter instead,
enter a command according to the following patterns in a command prompt
in the <ca_install> directory:
run contactfinder -name <name>
run contactfinder -number <phone number>
Examples:
run contactfinder -name Inova
run contactfinder -number +4989744123
NOTE: Only the last name and phone numbers are allowed as call parameters.
NOTE: The information about phone numbers stated in Table 138 on page
981 are valid for phone numbers as call parameters as well.
Result
All found entries are displayed with their data.
982
A31003-S5070-J100-12-7631, 02/2013
15.21.3.6 Common Configuration

Migration Tools Configuration
The configuration of the migration tools is divided into a common configuration
and a migration tool specific configuration.
The common configuration is done by the
<ca_install>\common.properties file. There is no need to change these
common settings for the execution of the migration tools.
Property
Description
Necessity
Logpath
Path of the logging and error files that are generated during the migration
Default: The log files are available in the logs directory.
Mandatory
BasePath
Path relative to the installation

Default: ./
Mandatory
DataDefinitionDirName Name of the directory containing all definitions

Default: common_config/datadef/
Mandatory
TemplateDirName
Name of the directory containing all templates

Default: common_config/templates/
Mandatory
InputDirName
Name of the input directory

Default: input/
Mandatory
OutputDirName
Name of the output directory

Default: output/
Mandatory
ContactsDirName
Name of the contact directory

Default: contacts/
Mandatory
IMPORTANT: Do not change the above default settings!

UCExportFile
File name of the Openscape UC Application domain export

Default: domain_configuration.csv
Mandatory
CAUserFile
File name of the CA user and device export

Default: usr_dev_exported.csv
Mandatory
PabsAddressFile
File name of the OpenScape ComAssistant database export containing the

pabs_address table
Default: pabs_address.csv
Mandatory
PabsNoticeFile

pabs_notice table
Default: pabs_notice.csv
Mandatory
AddrCategoryFile

addr_categroy table
Default: addr_category.csv
Mandatory
SabsAddressFile

sabs_address table
Default: sabs_address.csv
Mandatory
Table 139
The common.properties File
A31003-S5070-J100-12-7631, 02/2013
983
Property
Description
Necessity
SabsBookFile

addr_sharedbooks table
Default: addr_sharedbooks.csv
Mandatory
SabsBookAclFile

addr_sharedbooks_acl table
Default: addr_sharedbooks_acl.csv
Mandatory
SabsNoticeFile

sabs_notice table
Default: sabs_notice.csv
Mandatory
JournalFile

journal_call table
Default: journal_call.csv
Mandatory
TwmPartnersFile

twm_partners table
Default: twm_partners.csv
Mandatory
TwmPartnerAclFile

twm_partneracl table
Default: twm_partneracl.csv
Mandatory
TwmWebclientFile

twm_webclient table
Default: twm_webclient.csv
Mandatory
UCUserFile
Name of the UC import file containing the new UC users

Default: uc_users.csv
Mandatory
UCExternalIdFile
Name of the UC import file containing the new external IDs

Default: uc_users_externalIds.csv
Mandatory
UCContactFile
Name of the UC import file containing the new contact data of the users
Default: uc_users_contact_data.csv
Mandatory
UserMapFile
Name of the file containing a summary (CA user ID, UC user ID etc.) of the users Mandatory
migrated by the user migration tool.
Default:user_map.csv
CAImportFile
The user migration tool migrates CA users to UC users. After this migration, the Mandatory
CA user that have been migrated must be disconnected from the PBX. The
CAImportFile property gives the name of the file containing these CA users.
Default: ca_import_delete_dev.csv
TeamListFile
Name of the file containing a list with all migrated CA team owners and their Mandatory
team members
Default: team_list.csv
Table 139
The common.properties File
The migration tools-specific configurations are described in the corresponding

subsections of Section 15.21.4, Migrations, on page 990.
984
A31003-S5070-J100-12-7631, 02/2013
Logging Configuration
The logging output of the migration tools in the command prompt is based on the
standard LOG4J and can be configured editing the <ca_install>\log4j.xml
file. The command prompt output is activated by the <appender> element in this
file that has a name attribute with the value CONSOLE.
<appender name="CONSOLE" class="org.apache.log4j.ConsoleAppender">
<param name="Threshold" value="WARN"/>
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d{ABSOLUTE} %-5p [%c{1}] %m%n" />
</layout>
</appender>
The <param> element with the name attribute Threshold indicates the logging
level by the value of its value attribute. Assign one of the following values:
Log level
Description
DEBUG
DEBUG indicates that debug messages and higher messages are put out in the command prompt, i e. the DEBUG
level includes the INFO, WARN, ERROR and FATAL levels.
INFO
INFO indicates that information messages and higher messages are put out in the command prompt, i e. the
INFO level includes WARN, ERROR and FATAL levels.
WARN
WARN indicates that warning messages and higher messages are put out in the command prompt, i e. the WARN
level includes ERROR and FATAL levels.
ERROR
ERROR indicates that error messages and higher messages are put out in the command prompt, i e. the ERROR
level includes FATAL level.
FATAL
FATAL indicates that only fatal error messages are put out in the command prompt.
Table 140
Log4j Levels
IMPORTANT: If you increase the number of the command prompt output statements, the execution time of the migration tools increases as well.
If mass data is migrated, it is recommended to change the log level for the
command prompt output due to performance issues.
A31003-S5070-J100-12-7631, 02/2013
985
15.21.3.7 Database Exports

The CA migration needs some export files generated by the OpenScape UC
Application and the OpenScape ComAssistant.
OpenScape UC Application domain management data export
The user migration tool needs an OpenScape UC Application domain
management data export file.
1. Execute the following sub-steps to generate an OpenScape UC Application
domain management data export file named
domain_configuration.csv.
a) Open the CMP of the OpenScape UC Application.
b) Click on the Recovery menu item on the Maintenance navigation tab of
the CMP.
c) Click on Import & Export > Export in the navigation tree. The dialog for
exporting configurations opens.
d) Select the check box of the Domain Management component under
Common Management Platform.
e) Click on Next.
f)
Click on Export. The selected data is loaded to the client PC as ZIP file.
g) Store the file locally on the computer system.

h) Open the downloaded ZIP file and open the following ZIP file contained
therein:
Package_domainmanagement_domainmanagement001.zip
i)
This ZIP file contains the domain_configuration.csv file.

NOTE: If you want to read or edit the domain_configuration.csv
file, use the text editor Notepad. If you use other text editors you need to
make sure that no Byte-Order-Mark BOM is used.
See the section How to Export Data for CMP (Common Management
Platform) in administrator documentation OpenScape Common
Management Platform Administration for details.
2. Check whether this file must be renamed according to Table 139 on page 983,
The common.properties File.
3. Copy the this file into the <ca_install>\input directory of the CA
migration computer.
986
A31003-S5070-J100-12-7631, 02/2013
CA user and device data export

The user migration tool needs a user and device data export file generated by the
OpenScape ComAssistant.
4. Use the OpenScape ComAssistant Management Portal to generate a user
and device data export file named usr_dev_exported.csv according to
the section Exporting data in the service manual HiPath CAP V3.0 Common
Application Platform.
5. Check whether this file name has to be renamed according to Table 139 on
page 983, The common.properties File.
6. Copy the this file into the <ca_install>\input directory of the CA
migration computer.
CA MySQL database export
The CA MySQL database export generates a CSV file needed by the CA
migration tools.The configuration of this export is done by the following file:
<ca_install>\ca_sql_export_config\ca_sql_export.properties
Property
Description
Necessity
db_user
The user who can access the database

Example:
<entry key="db_user">dbuser01</entry>
Mandatory
db_password
The users password

Example:
<entry key="db_password">password123</entry>
Mandatory
db_port
The database access port. Typically port 3306 is used.

Example:
<entry key="db_port">3306</entry>
Mandatory
db_host
The name of the computer hosting the database

Example:
<entry key="db_host">MySqlComputer</entry>
Mandatory
db_name
The name of the database

Example:
<entry key="db_namet">MySqlDb</entry>
Mandatory
Table 141
The ca_sql_export_config\ca_sql_export.properties File
7. The command to export the CA MySQL database always is executed on the

CA migration computer. If the CA MySQL database is not installed on the CA
migration computer, the following sub-steps must be executed on the CA
MySQL computer so that the export command has remote access to the CA
MySQL database:
a) Open a command prompt.
b) Go to the bin directory of MySQL database (e. g. C:\Program
Files\MySQL\MySQL Server 5.5\bin).
c) Enter the following command:
A31003-S5070-J100-12-7631, 02/2013
987
mysql -u root -p
d) Enter your root password when prompted. If you have logged in
successfully, you see the mysql prompt:
mysql>
e) Grant remote access to the CA MySQL database:
mysql> GRANT ALL PRIVILEGES ON *.* TO <user name>@<IP address> IDENTIFIED BY
<password>;
Example:
mysql> GRANT ALL PRIVILEGES ON *.* TO root@10.11.12.13 IDENTIFIED BY 123;
f)
Activate the new rights:

mysql> FLUSH PRIVILEGES;
g) Leave the MySQL command prompt:

mysql> quit;
8. Open a command prompt on the CA migration computer.
9. Navigate to the <ca_install> directory.
run sql_export
The following CSV files are available in the <ca_install>\input directory
after a successful export. Already existing files will be overwritten.
IMPORTANT: Any changes in the CA personal address books, the CA
shared address books, the CA teams and the CA call journal entries after the
execution of the run sql_export command will not be migrated to the
OpenScape UC Application and are lost.
988
Input files for the private address book migration
pabs_address.csv
pabs_notice.csv
pabs_phone.csv
addr_category.csv
Input files for the shared address book migration
addr_sharedbooks.csv
addr_sharedbooks_acl.csv
sabs_address.csv
A31003-S5070-J100-12-7631, 02/2013
sabs_notice.csv
sabs_phone.csv
Input files for the team migration
twm_partners.csv
twm_partneracl.csv
twm_webclient.csv
Input files for the call journal migration
journal_call.csv
11. Check whether all generated CSV files fulfil the following conditions:
a) Fields and columns are separated by the ; character (semicolon).
b) Records are terminated by a carriage return.
c) Empty fields or null values are shown as ;;(double semicolon).
Example:
Header:Name;Productiondate;additionalInfo
Record:BMW;2012;SUV
Record:VW;2010;;
A31003-S5070-J100-12-7631, 02/2013
989
15.21.4 Migrations
This section describes the supported migrations. Execute the instructions in the
subsections in the described order.
15.21.4.1 User Migration

The user migration tool migrates CA user entries of the CA export to UC user
entries in a CMP importable file. Each UC user entry is enhanced by its contact
data, ONS device and if required the SSO data.
An LDAP directory connected to the OpenScape UC Application can provide the
contact data information for the OpenScape UC Application user. The
configuration of the ONS device of the UC User is based on the OpenScape UC
Application domain export. Therefore, a connected and synchronized
OpenScape Voice or HiPath 4000 is required.
Preconditions
1. The user migration tool needs the following input files:
a) The domain management export file (default name:
domain_configuration.csv) generated in step 1 on page 986 by
the CMP of the OpenScape UC Application
b) CA user and device export data file (default name:
usr_dev_exported.csv) created in step 4 on page 987
2. If an LDAP directory is configured as a contact data source, a connection to
this LDAP directory must be established.
See the section LDAP Connection in the administrator documentation
OpenScape UC Application Configuration and Administration for a detailed
description about how to configure the connection to the LDAP directory.
3. Delete the <ca_install>\output\user_map.csv file, if available. Thus,
you avoid using an old input file for the migrations following the user
migration.
990
A31003-S5070-J100-12-7631, 02/2013
Configuration
4. The configuration is done by
<ca_install>\ca_user_config\ca_user.properties file and the
<ca_install>\ca_user_config\set.properties file.
Property
Description
Necessity
userIdKey
The generated UC user ID based on data of the usr_dev_exported.csv file.

Mandatory
Therefore, the name of the column/key which containing this information is required.
Example: <entry key="userIdKey">uid</entry>
If the data record in the CA export file usr_dev_exported.csv contains the value
john.doe in uid column, the ID of the UC user is john.doe.
If the user ID is empty or the user ID already exists (created during this execution),
an error is logged in the error file.
imDomain
It is possible to configure an instant-messaging address for a UC user. This instant- Optional

messaging address is made according to the following example:
Example: <entry key="imDomain">openfire</entry>
The user with the UC user id john.doe has following instant-messaging address:
john.doe@openfire
If there is no configured instant-messaging domain, no instant-messaging address
will be created.
<entry key="imDomain"></entry>
assignedPhoneKey The OpenScape Voice or the HiPath 4000 are supported as connected PBXs.
Mandatory
Depending on the connected PBX, the destination of the assigned phone number
value has to be decided.
Example for the configuration of a connected OpenScape Voice:
<entry key="assignedPhoneKey"> assignedPhone8kNumber</entry>
Example for the configuration of a connected Hipath 4000:
<entry key="assignedPhoneKey"> assignedPhone4kNumber</entry>
caNamePattern
The pattern of the CA user name.
Mandatory
Example 1: The first name is followed by a blank and the last name:
<entry key="caNamePattern"> Paul Smith</entry>
Example 2: The last name is followed by a semicolon and the first name:
<entry key="caNamePattern"> Smith;Paul</entry>
Table 142
The ca_user_config\ca_user.properties File
A31003-S5070-J100-12-7631, 02/2013
991
Property
Description
Necessity
domain
The domain of the OpenScape UC Application. Currently only the system domain
is supported.
Mandatory
Example: <entry key="domain">system</entry>

The UC user ID of the user with the ID john.doe is john.doe@system.
password
This property assigns a password to the UC user. It can be used for logging in to the Mandatory
OpenScape UC Application e. g. by using the OpenScape UC Application
OpenScape Web Client.
Example: <entry key="password">myPassword!09</entry>
The user must enter myPassword!09 as his password for the first logon and must
change it afterwards.
pin
This is the PIN of the UC user.

Example: <entry key="pin">12345678</entry>
Mandatory
defaultLocale
The locale for the UC user, if the CA user has no locale assigned.
Example: <entry key="defaultLocale">de_DE</entry>
Optional
Table 143
992
The ca_user_config\set.properties File
A31003-S5070-J100-12-7631, 02/2013
Property
Description
Necessity
defaultTimeZone
The time zone for the UC user, if the CA user has no time zone assigned.
Use Olson IDs as values (see Table 144 on page 994).
Optional
Example: <entry key="defaultTimeZone">Europe/Berlin</entry>
assignedProfile
This is the name of the assigned license profile for the UC user.
Mandatory
Use e. g. values that are shown in the CMP at Configuration > Unified
Communications > Account > List > <user name> > Profiles.
Use e. g. the values that are shown in the Profile name and Application columns
and separate them by a colon (:).
Examples:
Essential:OpenScape UC App
Professional:OpenScape UC App
Team:OpenScape UC App
Team Administrator:OpenScape UC App
Premium:E/A-Cockpit
Standard:E/A-Cockpit
Example: <entry key="assignedProfile">Essential:OpenScape UC
App/entry>
If the user has more than one assigned profile, use the following notation:
<entry key="assignedProfile">Essential:OpenScape UC
App\,Premium:E/A-Cockpit</entry>
Note: Ensure to use a backslash and a comma between the values. Do not use only
a comma.
Table 143
The ca_user_config\set.properties File
A31003-S5070-J100-12-7631, 02/2013
993
Use the Olson IDs in the following table for the defaultTimeZone property.
994
Time Zone
Olson ID
Offset to UTC
Honolulu
Pacific/Honolulu
UTC-10
Anchorage
America/Anchorage
UTC-9
US/Pacific
UTC-8
US/Mountain
UTC-7
US/Central
UTC-6
US/Eastern
UTC-5
Canada/Atlantic
UTC-4
Sao Paulo
America/Sao_Paulo
UTC-3
South Georgia
Azores
Atlantic/Azores
UTC-1
Reykjavik
Atlantic/Reykjavik
UTC
London
Europe/London
UTC
Lisbon
Europe/Lisbon
UTC
Berlin
Europe/Berlin
UTC+1
Madrid
Europe/Madrid
UTC+1
Paris
Europe/Paris
UTC+1
Rome
Europe/Rome
UTC+1
Cairo
Africa/Cairo
UTC+2
Johannesburg
Africa/Johannesburg
UTC+2
Moscow
Europe/Moscow
UTC+3
Tehran
Asia/Tehran
UTC+3:30
Yerevan (Armenia)
Asia/Yerevan
UTC+4
Calcutta
Asia/Calcutta
UTC+5:30
Dhaka
Asia/Dhaka
UTC+6
Ho Chi Minh
Asia/Saigon
UTC+7
Hong Kong
Asia/Hong_Kong
UTC+8
Shanghai
Asia/Shanghai
UTC+8
Taipei
Asia/Taipei
UTC+8
Tokyo
Asia/Tokyo
UTC+9
UTC+10
Salomon Islands
Pacific/Guadalcanal
UTC+11
Auckland
Pacific/Auckland
UTC+12
Table 144
A31003-S5070-J100-12-7631, 02/2013
5. The single sign-on (SSO) configuration is done by using the

<ca_install>\ca_user_config\uc_externalId.properties file.
Property
Description
Necessity
generateSSO
The generation of the SSO for the UC users can be activated or deactivated.
Optional
Example for the creation of SSO entries:

<entry key="generateSSO">true</entry>
Example for no creation of SSO entries:
<entry key="generateSSO">false</entry>
The generation of the SSO settings is deactivated if this property is not available, not
configured or faulty configured.
externalIdPostIn Example:
<entry key="generateSSO">true</entry>
fo
<entry key="externalIdPostInfo">@a.b.c</entry>
assignedExternal <entry key="assignedExternalSystemId">WinPassphrase</entry>

SystemId
<entry key="isContactMaster">false</entry>
isContactMaster <entry key="isProvisioningMaster">false</entry>
Optional
Optional
Optional
<entry key="additionalInfo"></entry>
Optional
isProvisioningMa
ster
These entries generate the following entry in the OpenScape UC Application import
file:
ExternalId;john.doe@a.b.c;john.doe@system;WinPassphrase;false
;false
Refer to the administrator documentation OpenScape UC Application Configuration
and Administration for a detailed description.
Table 145
The ca_user_config\uc_externalId.properties File
A31003-S5070-J100-12-7631, 02/2013
995
Skipping CA users
It is possible to skip CA users depending on the contents of the CA user data
records in the usr_dev_exported.csv file. The skipping is configurable via
properties in the
<ca_install>\ca_user_config\ca_user_skip.properties file.
Pattern:
<properties>
<entry key="<name of key or column>"><value/condition></
entry>
</properties>
6. Replace <name of key or column> by the name of the related key or
column in the CA user data record. Replace <value/condition> by the
value which must be equal to the value in the key or column in the CA user
data record.
Syntax:
Syntax example
Description
<entry key="k">v1</entry>
Skipping if the value of k is equal to v1.
<entry key="k">v1,v2</entry>
Skipping if the value of k is equal to v1 or equal to v2.
<entry key="k">!=v1</entry>
Skipping if the value of k is not equal to v1.
<entry key="k">!=v1,v2</entry>
Skipping if the value of k is not equal to v1 or not equal to v2.
<entry key="k">*v1</entry>
Skipping if the value of k ends with v1.
<entry key="k">*v1,v2</entry>
Skipping if the value of k ends with v1 or ends with v2.
<entry key="k">v1*</entry>
Skipping if the value of k starts with v1.
<entry key="k">v1,v2*</entry>
Skipping if the value of k starts with v1 or starts with v2.
Table 146
Syntax Examples for skipping CA Users
If the condition (value of the CA user record is equal to the configured value)
is fulfilled, the data record will be skipped, a log entry will be written and the
tool will proceed with the next CA user data record.
NOTE: Skipping is useful e. g. for migrating only CA users connected to a
certain PBX specified by the PBX ID.
Example 1 for ca_user_skip.properties:

<!DOCTYPE properties SYSTEM "http://java.sun.com/dtd/properties.dtd">
<properties>
<entry key="sccId">TEST</entry>
</properties>
996
A31003-S5070-J100-12-7631, 02/2013
The CA user is skipped, if he is connected to a PBX with the ID equal to

TEST or the CA user will be skipped, if the value of sccId (ID of the call
control service) in his data record is equal to TEST. You find the value of
sccId in the usr_dev_exported.csv file.
Example 2

<properties>
<entry key="sccId">!=TEST</entry>
</properties>
The CA user is skipped, if he is connected to a PBX with the ID not equal
to TEST, i. e. if the value of sccId is not equal to TEST.
Example 3

<properties>
<entry key="sccId">TEST,ZERT</entry>
</properties>
The CA user is skipped, if he is connected to a PBX with the ID equal to
TEST and the CA user will be skipped, if he is connected to a PBX with
the ID equal to ZERT.
Example 4

<properties>
<entry key="domainId">*Berlin</entry>
</properties>
The CA user is skipped, if his domainId ends with Berlin.
Example 5

<properties>
<entry key="domainId">UK*</entry>
</properties>
The CA user is skipped, if his domainId starts with UK.
A31003-S5070-J100-12-7631, 02/2013
997
Execution
7. Open a command prompt.
IMPORTANT: This command creates new output files overwriting potentially
existing output files. An overwrite warning is written to the error log file and
the trace file.
run user
The migration tool starts without user interaction. Log statements are
displayed during the execution.
Result
10. The following results of this migration tool are available in the
<ca_install>\output directory.
a) uc_users_import.csv
This is the file that contains UC user data, their contacts and, if applicable,
the SSO data.
Import this file to the OpenScape UC Application now by using the CMP.
(see the administrator documentation OpenScape UC Application
Configuration and Administration).
b) ca_import_delete_dev.csv
This is the import file for the OpenScape ComAssistant Management
portal to disconnect the CA users from the PBX.
IMPORTANT: Do NOT execute this import now. It will be done in step 1
on page 1028.
c) user_map.csv
This file contains a summary (CA user ID, UC user ID etc.) of the users
migrated by the user migration tool.
This file is e. g. used to select for which users the personal address book
should be migrated to the OpenScape UC Application. The enabled
value of the user records in the user_map.csv file specifies the users to
progress with.
Example in the user_map.csv file:
enabled;ca_user_id;
true;ca_user1111;
998
A31003-S5070-J100-12-7631, 02/2013
false;ca_user2222;
This example migrates the personal address book of user ca_user1111
and skips CA user ca_user2222.
The user_map.csv file is a necessary input for all subsequent migration
steps described in the next sections.
Copy the user_map.csv file into the <ca_install>\input directory.
Checking the results
11. Checking the log files
The log files of the user migration tool are in the
<ca_install>\logs\ca_user directory.
Each migration tool writes into the following log files:
error.log
This file contains only errors and warnings concerning the migration tool
execution, e. g. skipped users etc.
trace.log
This file contains all log entries of the migration tool execution including
errors and warnings.
ToDo.log
This file contains a list of problems that might be solved by a correction,
e.g. a correction of the database.
a) Check the entries of the error log file whether they are okay. If you need
further information, analyze the trace.log file.
NOTE: Checking the log files is recommended for each migration step.
b) Check the entries of the ToDo.log file. There might be hints to enhance
the quality of the migration step.
A31003-S5070-J100-12-7631, 02/2013
999
12. Checking via CMP

The migration of the CA users can be checked by using the CMP of the
a) Check whether the user is available in the User Management or
Configuration > Unified Communications > Accounts > List in the
CMP of the OpenScape UC Application.
b) Check whether the user has the expected call number and ONS.
1000
A31003-S5070-J100-12-7631, 02/2013
c) Check the users contact data.
13. Checking via OpenScape UC Application OpenScape Web Client

a) Enter http://<IP address of the application
computer>:8443 in a browser to open the OpenScape UC Application
b) Enter a UC user name of a migrated user and his password.

c) Click the OK button.
If the login is successful, the following screen is shown:
A31003-S5070-J100-12-7631, 02/2013
1001
15.21.4.2 Personal Address Book Migration

The PABS tool supports the migration of the personal address book of a CA user
to the private contact list of the corresponding UC user. CA address group names
are migrated to address group names in the private contact list of the
corresponding UC user.
The PABS migration tool checks whether the new entries in the private contact
list correspond to existing UC users.
Preconditions
1. The access to the OpenScape UC Application is configured in the
<ca_install>\common_config\ucaccess.properties file according
to Table 137 on page 978.
2. The CA MySQL database export in step 10 on page 988 has generated the
following import files:
pabs_address.csv
pabs_notice.csv
pabs_phone.csv
addr_category.csv
3. The user migration tool has been executed successfully in step 9 on page
998, i. e. the CA users have been migrated successfully to the OpenScape
UC Application and the <ca_install>\input\user_map.csv file is
available.
The user_map.csv file is used as a filter for the users to be processed. If
the user_map.csv file is not available, no address book is migrated.
4. Check whether the owners of the private address books to be migrated are
marked as enabled in the user_map.csv file (see step 10c on page 998).
Execution
7. Enter the following command
run pabs
Result
8. The personal address book entries are migrated into the private contact list
of the UC user.
1002
A31003-S5070-J100-12-7631, 02/2013

The log files of the PABS migration tool are in the
<ca_install>\logs\ca_pabs directory.
error.log
trace.log
ToDo.log
A31003-S5070-J100-12-7631, 02/2013
1003


d) Click the Contacts tab.
e) Check whether the personal address book entries of the CA user are
shown as entries in the private contact list of the corresponding UC user.
1004
A31003-S5070-J100-12-7631, 02/2013
f)
As stated above, a personal address book entry that is migrated to a

contact is assigned to an address group. Activate the check box of a
contact and click the Edit Contact icon.
The dialog shows the address group name of this contact in the Address
group field.
A31003-S5070-J100-12-7631, 02/2013
1005
15.21.4.3 Shared Address Book Migration

The SABS migration tool supports the migration of the shared address books of
an OpenScape ComAssistant. The result of this migration are import files
representing all shared address books. These files are importable into the
OpenScape UC Application OpenScape Web Client and shown as an address
group in the private contact lists.
The shared address books to be migrated can be filtered by the number of CA
users having access to a shared address book.
The user_map.csv file is used as a filter for the owner and the members of a
shared address book.
Preconditions
user_map.csv
sabs_address.csv
sabs_notice.csv
sabs_phone.csv
addr_sharedbooks.csv
addr_sharedbooks_acl.csv
available.
The user_map.csv file is used as a filter for the users to be processed.
IMPORTANT: The filtering effect of the user_map.csv only takes place, if
exactly one CA user accesses the shared address book.
If the user_map.csv file is not available, no address book is migrated.
3. Check whether the owners of the shared address books to be migrated are
marked as enabled in the user_map.csv file (see step 10c on page 998).
Configuration
4. The configuration of the SABS migration tool is done via the
<ca_install>\ca_sabs_config\ca_sabs.properties file.
The properties described in the following table can be set:
1006
A31003-S5070-J100-12-7631, 02/2013
Property
Description
Necessity
skipBooksWithAcces The property skipBooksWithAccessCount determines which address books are Optional
sCount
migrated.
Example 1: All shared address books are migrated.
<entry key="skipBooksWithAccessCount"></entry>
Example 2: Shared address books that are accessed by fewer than 4 CA users are
not migrated.
<entry key="skipBooksWithAccessCount">4</entry>
Example 3: Only shared address books that are accessed by exactly 4 CA users are
migrated.
<entry key="skipBooksWithAccessCount">!=4</entry>
Example 4: Shared address books that are accessed by exactly 4 CA users are not
migrated.
<entry key="skipBooksWithAccessCount">=4</entry>
Mandatory
outputFilePrefix The SABS migration tool migrates shared address book entries to a file
containing the contacts that will be imported into the OpenScape UC
Application. The outputFilePrefix property determines the prefix of this
file.
Example:
<entry key="outputFilePrefix">WebClientContacts_</entry>
outputFileExtens The SABS migration tool migrates shared address book entries to a file
ion
containing the contacts that should be imported into the OpenScape UC
Application. The outputFileExtension property determines the file
extension of this file.
Example: <entry key="outputFileExtension">txt</entry>
Mandatory
contactGroupPref The SABS migration tool migrates shared address book entries to a file
ix
containing the contacts that will be imported into the OpenScape UC
Application. These contacts are assigned to an address group. The
contactGroupPrefix property determines the prefix of this address
group name.
Example:
<entry key="contactGroupPrefix">CA-SABS </entry>
Mandatory
Table 147
The ca_sabs_config\ca_sabs.properties File
Execution
IMPORTANT: This command creates a new import file overwriting a potentially existing import file. An overwrite warning is written to the error log file
and the trace file.
A31003-S5070-J100-12-7631, 02/2013
1007
run sabs
Result
8. A file with a file name according to the following pattern has been created in
the <ca_install>\output directory for each shared address book that is
accessed by more than one user:
<outputFilePrefix>SharedAddressBook_<book name><outputFileExtension>.owner
Example:
WebClientContacts_SharedAddressBook_Book1.txt.owner
These files contain the CA user IDs of the users accessing the corresponding
address book. The files are not used as import files for further actions but they
enable you to check the users accessing the address books.
If the files already exist, they are extended by @ and a unique number:
<outputFilePrefix>SharedAddressBook_<book name>@<unique
number><outputFileExtension>.owner
Example:
WebClientContacts_SharedAddressBook_Book1@1.txt.owner
9. A file containing the shared address book has been created for each shared
address book in the <ca_install>\output directory.
If the shared address book is accessed by more than one user, a file with a
name according to the following pattern has been created:
<outputFilePrefix>SharedAddressBook_<book name><outputFileExtension>
If the files already exist, they are extended by @ and a unique number:
<outputFilePrefix>SharedAddressBook_<book name>@<unique number><outputFileExtension>
Example:
WebClientContacts_SharedAddressBook_Book1@1.txt
If the shared address book is accessed by more than one user, execute the
following sub-steps:
1008
A31003-S5070-J100-12-7631, 02/2013

b) Enter the UC user name corresponding to the first CA user ID in the file
created in step 8 on page 1008.
c) Enter his password.
d) Click the OK button.
A31003-S5070-J100-12-7631, 02/2013
1009
e) Click menu > General.
f)
1010
Click the Addresses tab.
A31003-S5070-J100-12-7631, 02/2013
g) Select the value ComAssistant 2.0 in the The address data was
exported from field.
Click the Browse... button and select the following file.

<outputFilePrefix>SharedAddressBook_<book name><outputFileExtension>
h) Click the Open button.
i)
Click the Import button.
j)
Execute step 9a on page 1009 to step 9i on page 1011 for all other CA
user IDs in the file created in step 8 on page 1008.
If the shared address book is accessed by one user, a file with a name
according to the following pattern has been created:
<outputFilePrefix><OpenScape UC Application user ID>_<book name><outputFileExtension>
If the file already exists, it is extended by @ and a unique number:
<outputFilePrefix><OpenScape UC Application user ID>_<book name>@<unique
number><outputFileExtension>
Example:
WebClientContacts_userD_Book1@1.txt
A31003-S5070-J100-12-7631, 02/2013
1011
If the shared address book is accessed by one user, execute step 9a on page
1009 to 9j on page 1011 only for this user.
Example
There is a shared address book named Book1 accessed by userA, userB and
userC. There is a shared address book named Book2 accessed by userD.
The SABS migration tool has the following configuration:
<entry
<entry
<entry
<entry
key="skipBooksWithAccessCount"></entry>
key="outputFilePrefix">WebClientContacts_</entry>
key="outputFileExtension">txt</entry>
key="contactGroupPrefix">CA-SABS: </entry>
The following files are available in the <ca_install>\output directory after a

successful execution of the SABS migration tool:
A file named WebClientContacts_SharedAddressBook_Book1.txt

containing the migrated shared address book Book1 that is ready for import.
When this file is imported into the OpenScape UC Application OpenScape
Web Client, a new address group named CA-SABS: Book1 is created and
all contacts of the shared address book Book1 will be added into this new
address group.
A file named
WebClientContacts_SharedAddressBook_Book1.txt.owner
containing the CA user IDs of the accessing users userA, userB and userC.
A file named WebClientContacts_userD@system_Book2.txt

When this file is imported into the OpenScape UC Application OpenScape
Web Client, a new address group named CA-SABS: Book2 is created and
all contacts of the shared address book Book2 will be added to this new
address group.
1012
A31003-S5070-J100-12-7631, 02/2013

The log files of the SABS migration tool are in the
<ca_install>\logs\ca_sabs directory.
error.log
trace.log
ToDo.log
A31003-S5070-J100-12-7631, 02/2013
1013


d) Click the Contacts tab.
e) Check whether the shared address book entries of the CA user are shown
as entries in the private contact list of the corresponding UC user.
1014
A31003-S5070-J100-12-7631, 02/2013
f)
As stated above, a shared address book entry that is migrated to a

contact is assigned to an address group. Activate the check box of a
contact and click the Edit Contact icon.
The dialog shows the address group name of this contact in the Address
group field.
A31003-S5070-J100-12-7631, 02/2013
1015
15.21.4.4 Team Migration

A CA user can own a team. This owner determines the team members and their
access rights. The team migration tool migrates all members of a CA team to
entries in the personal contact list of a UC user corresponding to the CA team
owner user. The access rights of the CA team members are not migrated.
Entries in a private contact list in the OpenScape UC Application can be assigned
to an address group. All personal contact lists entries that are migrated by the
team migration tool, are assigned to an address group named Teamview per
default. This address group name can be configured. The team members of all
CA teams are migrated to the same address group.
The UC user corresponding to the CA team owner user can see the presence
status of the UC users corresponding to his CA team member users without
having asked these UC users for permission.
IMPORTANT: Due to some architectural differences of the team implementation
in OpenScape ComAssistant V2.0 and OpenScape UC Application V7 R1, the
team migration tool migrates OpenScape ComAssistant teams into a private
contact list of a UC user, but it does not migrate OpenScape ComAssistant teams
into OpenScape UC Application teams.
The Professional Services Center of Competence UC provides support for
analysis of OpenScape ComAssistant team data and OpenScape ComAssistant
team data migration.
Preconditions
The access to the OpenScape UC Application is configured in the

The OpenScape UC Application LDAP connectivity is configured and is in

operation.
twm_partners.csv
twm_partneracl.csv
twm_webclient.csv
available.
The user_map.csv file is used as a filter for the users to be processed. If
the user_map.csv file is not available, no team is migrated.
1016
A31003-S5070-J100-12-7631, 02/2013
3. Check whether the owners of the teams to be migrated are marked as

enabled in the user_map.csv file (see step 10c on page 998).
Configuration
4. The configuration of the team migration tool is done by editing the
<ca_install>\ca_team_partner_config\ca_team_partner.prop
erties file.
The following property can be set:
Property
Description
groupNameTeamView
This property defines the address group name entries in the private contact list of a Optional
UC user can be assigned to by the team migration tool. This property affects all UC
users corresponding to CA team members, i. e. the property is not user-specific.
Example: <entry key="groupNameTeamView">Teamview</entry>
Table 148
Necessity
The ca_team_partner_config\ca_team_partner.properties File
Execution
IMPORTANT: This command creates a new report file overwriting a potentially existing report file. The default name of this report file is
team_list.csv. An overwrite warning is written to the error log file and the
trace file.
run team_partner
The migration tool executes without user interaction. Log statements are
A31003-S5070-J100-12-7631, 02/2013
1017
Result
8. The team migration tool migrates the CA team users to UC contact list entries
as described above. No CSV file is created that must be imported.
9. The UC user corresponding to the CA team owner user can see the presence
status of the UC users corresponding to his CA team member users without
having asked these UC users for permission. Each UC user can control and
edit the visibility of his presence status in the OpenScape UC Application
OpenScape Web Client at menu > General > Presence > Access Control
List.
10. The team_list.csv file has been generated for check purposes (see step
12 on page 1019).
11. The tool execution is recorded in log files and error files. They are available
in the <ca_install>\logs\ca_team_partner directory. You find a
dump of the used team data of the CA system in the trace.log file.
Example
There is a CA team owner 4711 with the CA team members 4760 and 4770.
The UC user 4711 has a new contact group with entries for his team members
4760 and 4770 after the migration. The team owner 4711 automatically has
access to the UC presence of 4760 and 4770 without the need of asking 4760
and 4770 for permission.
1018
A31003-S5070-J100-12-7631, 02/2013

12. The team migration has created a team_list.csv file in the output
directory. This file contains a list with all migrated CA team owners and their
team members.
Example:
enable;uc_user_id;partner_list
false;4711@system;<4760@system, 4770@system>
This file provides only information for checking the execution results of the
team migration tool. It is not needed as an input file for any import into the
The log files of the team migration tool are in the
<ca_install>\logs\ca_team_partner directory.
error.log
trace.log
ToDo.log
A31003-S5070-J100-12-7631, 02/2013
1019
15.21.4.5 Call Journal Migration

The journal migration tool migrates a call journal entries of CA users to call journal
entries of UC users.
Restrictions
The user migration tool has generated the journal_call.csv file in step
10 on page 988 and has determined the next free value of the primary key in
the database table of the OpenScape UC Applicaton. If there are active calls
in the OpenScape UC Application during the execution of the journal
migration tool, this tool might access the next free value of the primary key in
parallel to the OpenScape UC Application. This might result in errors.
IMPORTANT: This is why there must be no active calls in the OpenScape
UC Application during execution of the actual journal migration in step 11 on
page 1021. Therefore, the OpenScape UC Application must be stopped in
step 7 on page 1021 during the call journal migration.
Caller information (CallerInfo) in the OpenScape ComAssistant may contain

linked information to a connected directory service. This information is not
migrated.
The journal migration tool does not migrate CA shared journals, i. e. a UC

user can only see his own journal.
Preconditions
1. The access to the OpenScape UC Application is configured in the
2. The journal_call.csv file that has been created in step 10 on page 988
must be available. It contains the CA call journal entries to be migrated to UC
call journal entries.
IMPORTANT: Any CA call journal entry that has been created after the
creation of the journal_call.csv file, will not be migrated and is lost.
The journal_call.csv file name is a default name. It can be configured
according to Table 139 on page 983, The common.properties File.
3. The parameters for accessing the OpenScape UC Application database (see
Table 149 on page 1021) must be known.
4. The user migration in Section 15.21.4.1, User Migration, on page 990 has
been executed successfully.
1020
A31003-S5070-J100-12-7631, 02/2013
5. The <ca_install>\input\user_map.csv file that has been created in

step 10c on page 998 must be available. It is used for defining the CA users
whose call journal entries are migrated to call journal entries of UC users.
The user_map.csv file name is a default name. It can be configured
according to Table 139 on page 983, The common.properties File.
6. Check whether the owners of the teams to be migrated are marked as
enabled in the user_map.csv file (see step 10c on page 998).
7. Stop the OpenScape UC Application by executing the following command as
the root user in a command line on the application computer:
Configuration
8. The configuration is done by the
<ca_install>\ca_journal_config\ca_journal.properties file.
Property
Description
Necessity
db_user
The user ID to access the OpenScape UC Application database.
Mandatory
Example: <entry key="db_user">dba</entry>
db_password
The password of this user accessing the OpenScape UC Application database.
Mandatory
Example: <entry key="db_password">mypassword</entry>

IMPORTANT: This password must not be dba, the default value.
db_port
The port to access the OpenScape UC Application database.
Mandatory
Example: <entry key="db_port">16760</entry>

This port must be open in firewalls between the CA migration computer and the
application computer of the OpenScape UC Application, see Section 6.1, Lists of the
Ports to be opened, on page 359.
db_host
The IP address of application computer of the OpenScape UC Application.
Mandatory
Example: <entry key="db_host">10.11.12.13</entry>

Table 149
The ca_journal_config\ca_journal.properties File
Execution
9. Open a command prompt on the CA migration computer.
run journal
A31003-S5070-J100-12-7631, 02/2013
1021
12. Start the OpenScape UC Application by executing the following command as

the root user in a command line on the application computer:
This step is necessary to complete the call journal migration and to generate
a current view of the call journal entries in the OpenScape UC Application.
You can check the status of the OpenScape UC Application by executing the
following command in a command line on the application computer:
Result
13. The journal entries are migrated to the appropriate UC user.
The log files of the call journal migration tool are in the
<ca_install>\logs\ca_journal directory.
error.log
trace.log
ToDo.log
1022
A31003-S5070-J100-12-7631, 02/2013


d) Click the Journal tab.
The migrated call journal entries are shown.
A31003-S5070-J100-12-7631, 02/2013
1023
15.21.4.6 OpenScape Xpressions Access Migration

The Xpressions migration tools migrates CA users having access to an
OpenScape Xpressions server to the corresponding UC users having access to
the same OpenScape Xpressions server. E. g. before the migration, a CA user
4711~defaulft has access to an OpenScape Xpressions server. After the
migration, a UC user 4711@system has access to this OpenScape Xpressions
server instead.xxxWird der Zugang des Benutzers 4711~default automatisch
gelscht oder sind dafr manuelle Aktionen ntig?
The Xpressions migration tool uses an OpenScape Xpressions export file
containing the CA users as an input file and generates a TXT file containing the
corresponding UC users. This file is imported to the OpenScape Xpressions.
Preconditions
1. Execute the following sub-steps in order to export the OpenScape Xpressions
database:
a) Retrieve the following user accounts and passwords:
Access to the OpenScape Xpressions server computer
Access to the OpenScape Xpressions database by using the DbTool
b) Login to the OpenScape Xpressions server computer.

c) Double-click the <XPR_install>\SDKTools\DbTool.exe file in the
Windows Explorer. <XPR_install> is typically C:\Siemens\xpr\.
d) Enter the DbTool password and click the OK button.
NOTE: See the section Database-Correl-Tool (DbTool) in the administrator documentation OpenScape Xpresssions Server Administration for
details.
e) In the File menu select the Export... option.
1024
A31003-S5070-J100-12-7631, 02/2013
f)
A window appears in which you specify the file name and the target path
for the file to be exported. Name the file xpruserexport.txt.
g) Click the Open button.

h) Copy this file to the <ca_install>\input directory on the CA
migration computer.
UC Application and the <ca_install>\input\user_map.csv file (see
step 10c on page 998) is available.
The user_map.csv file is used as a filter for the users to be processed and
to deliver a mapping from a CA user ID to a UC user ID. If the user_map.csv
file is not available, the Xpressions migration is not executed.
3. Check whether the users to be migrated are marked as enabled in the
user_map.csv file (see step 10c on page 998).
Configuration
4. The configuration of the ca_xpressions migration tool is done by editing the
<ca_install>\ca_xpressions_config\ca_xpressions.properti
es file.
The following properties can be set:
Property
Description
DOMAIN
Mandatory
This property defines the value of the DOMAIN column in the file to be
imported to the OpenScape Xpressions server. It is identical to the name of
the OpenScape Xpressions server.
Example: <entry key="DOMAIN">XPR_WEB</entry>
KEYNAME
This property defines the value of the KEYNAME column in the file to be
imported to the OpenScape Xpressions server. Always use the value
CONUSER.
Example: <entry key="KEYNAME">CONUSER</entry>
Table 150
Necessity
Mandatory
The ca_xpressions_config\ca_xpressions.properties File
A31003-S5070-J100-12-7631, 02/2013
1025
Execution
7. Enter one of the following commands:
IMPORTANT: This command creates a new import file overwriting a potentially existing import file. An overwrite warning is written to the error log file
and the trace file.
run xpressions
or
run xpr
The migration tool executes without user interaction. Log statements are
Result
8. The Xpressions migration tool generates an
<ca_install>\output\xprconuserimport.txt file to be imported into
OpenScape Xpressions.
The file contains a tab separated table according to the following example:
DOMAIN
XPR_WEB
CLASSNAME
USER
CLASS
4989700733231
KEYNAME
CONUSER
KEY
33231@system
The values of the DOMAIN and KEYNAME properties in the

<ca_install>\ca_xpressions_config\ca_xpressions.properti
es file are copied into the DOMAIN and KEYNAME columns.
The value in the GROUP column in the xpruserexport.txt file created in
step 1 on page 1024 is copied into the CLASSNAME column.
The value of the user in the xpruserexport.txt file created in step 1 on
page 1024 is copied into the CLASS column.
The UC user ID for this user in the user_map.csv file that had been created
in step 10c on page 998 is copied into the KEY column.
9. The Xpressions migration tool execution is recorded in log files and error files.
They are available in the <ca_install>\logs\ca_xpressions
directory.
10. Copy the xprconuserimport.txt file to the OpenScape Xpressions
server computer.
11. The DbTool that had been started in step 1 on page 1024 is still running.
1026
A31003-S5070-J100-12-7631, 02/2013
a) In the File menu select the Import... option.

IMPORTANT: Please note that imported data records overwrite existing
data records with the same class name, class and key name when they
are saved in the database list.
b) Enter the DbTool password and click the OK button.

c) Select the xprconuserimport.txt file and confirm your selection with
Open.
d) A message informs you about the successful file import. All data records
that were imported appear with a blue-green background color.
e) A click on the Save changes icon adds the imported data records to the
database.
This action changes the CA user data records in the Xpressions database
to UC user data records. It does not create new data records.
NOTE: See the section Importing and Exporting Data in the administrator
documentation OpenScape Xpresssions Server Administration for details.

The log files of the Xpressions migration tool are in the
<ca_install>\logs\ca_xpressions directory.
error.log
trace.log
ToDo.log
A31003-S5070-J100-12-7631, 02/2013
1027
15.21.4.7 Disconnecting CA users from the PBX

1. You created the ca_import_delete_dev.csv file in step 10b on page 998
during the user migration. This is the import file for the CA Management portal
to disconnect the CA users from the PBX. Import it now according to the
section Importing data in the service manual HiPath CAP V3.0 Common
Application Platform.
IMPORTANT: You might do not execute all migration tools in one step for all
CA users you want to migrate but you execute these migration tools in a major
step 1 for CA user group 1, in a major step 2 for CA user group 2, etc. Ensure
that you import the ca_import_delete_dev.csv file after each of these
main steps since the subsequent major step contains a new user migration
that would create a new ca_import_delete_dev.csv file overwriting the
already existing ca_import_delete_dev.csv file.
15.21.4.8 Creating a Trouble Ticket

1. If you create a trouble ticket for the CA migration to OpenScape UC
Application, execute the following command in the <ca_install> directory
on the CA migration computer:
run diag
This creates a CAV20_UC_Migrationtools_DiagnosisData.zip file.
Attach this file and a detailed problem description to the trouble ticket.
2. If there are problems during the data import using the CMP, the /tmp/
backupWork/provImpo/provisioning.log file is created on the
application computer. Please attach this file and a detailed problem
description to the trouble ticket as well.
1028
A31003-S5070-J100-12-7631, 02/2013
IG_Deinstallation.fm
Uninstallation
16 Uninstallation
IMPORTANT: Uninstalling the OpenScape UC Application V7 has been
released for Integrated Deployment only (see the OpenScape Voice documentation).
A31003-S5070-J100-12-7631, 02/2013
1029
IG_Deinstallation.fm
Uninstallation
1030
A31003-S5070-J100-12-7631, 02/2013
IG_AppendixHardening.fm
Hardening the OpenScape UC Application Computers
A Hardening the OpenScape UC Application Computers

This section provides an overview of measures you can take to harden
OpenScape UC Application computers by setting the operating system and the
NOTE: Please also check the Release Notes for recent hardening instructions
as regards the Linux operating system.
A31003-S5070-J100-12-7631, 02/2013
1031
Hardening Settings in the Operating System
A.1 Hardening Settings in the Operating System

Configuring the operating system appropriately and removing unnecessary
applications minimizes the threats the computer is exposed to.
Operating system hardening is a necessity when you install an operating system
on the computer(s) in your network or use off-the-shelf computers with preinstalled operating system software.
NOTE: If a customer has specific hardening guidelines for the operating system,
they should be followed where applicable and compatible with the application.
A.1.1 Hardening Physical Interfaces

Deactivate and disconnect all network interfaces to the application computer
which are not used.
A.1.1.1 Using Boot/Setup Passwords

We do not recommend the use of boot/setup passwords as computers will
otherwise not automatically restart after a power failure.
A.1.1.2 Applying Security Fixes

We strongly recommend a managed update to current security fixes of an
operating system. Please read the Release Notes or contact the service
personnel to learn about the latest supported service pack level.
NOTE: See Section B.1, General Operation of YaST, on page 1044 for helpful
information about operating YaST.
Open in the YaST Software > Novell Customer Center Configuration and
configure your system to activate online updates.
Open in the YaST Software > Online Update and activate all Novell fixes (for
example security).
A.1.1.3 Security-related RPM Packages

Open in the YaST Software > Software Management , find the following RPM
packages and uninstall them:
1032
A31003-S5070-J100-12-7631, 02/2013
RPM Name
Description
xinetd
An inetd with expanded functionality
yp-tools
Network Information Service (YP) client utilities
ybpind
NIS client daemon
openslp-server The OpenSLP implementation of the Service Location Protocol V2

Table 151
RPM Packages to be installed in Software > Software Management
Install the following package:

RPM Name
Description
seccheck
Security-check scripts
Table 152
RPM Packages to be installed in Software > Software Management
Open in the YaST System > System Services (Runlevel), find the following
RPM packages and uninstall them:
RPM Name
Description
postfix
Start the PostFix MTA
nfs
Imports remote Network File Systems (NFS)
portmap
DARPA port to RPC program number mapper
xdm
X Display Manager
Table 153
RPM Packages to be uninstalled in System > System Services
A.1.1.4 Umask
OpenScape UC Application runs with the unmodified default SLES 11 umask
value (file creation mask) of 022.
A.1.1.5 Links in the temp Folder

OpenScape UC Application does not create any links in the folder /tmp.
A31003-S5070-J100-12-7631, 02/2013
1033
A.1.2 Network Security

A.1.2.1 Internet Daemon, "R"-Daemons and telnet Daemon
Verify that /etc/xinet.conf and /etc/xinet.d are owned by root and the
access rights are restricted.
Check that following services are deactivated in /etc/xinet.d:
fingerd (not configured by default)
rexd (not configured by default)
ruserd (not configured by default)
tftpd (not configured by default)
echo (deactivated by default)
discard (not configured by default)
daytime (deactivated by default)
chargen (deactivated by default)
time (deactivated by default)
comsat (deactivated by default)
systat (deactivated by default)
netstat (deactivated by default)
sprayd (not configured by default)
walld (not configured by default)
telnet (deactivated by default)
rlogin
rcmd
rexec
rwho
A.1.2.2 Trivial FTP (TFTP), FTP, redx, Samba, nfs, rsync etc.
The application computer should be used for features of the OpenScape UC
Application only. We do not recommend to provide network services such as FTP,
DNS, POP/IMAP on this computer.
1034
A31003-S5070-J100-12-7631, 02/2013
A.1.2.3 Hardening Shared Folders NFS

OpenScape UC Application does not require NFS to be used.
A.1.2.4 Sendmail Daemon

OpenScape UC Application does not require the installation of a local sendmail
entity. It is not activated during installation by default.
A.1.2.5 SNMP
Set the SNMP community string to a difficult to hack/guess phrase.
A.1.2.6 Deactivating X-Server, KDE and GNOME

Deactivate X-Server and graphic desktops such as KDE or Gnome in a
productive system (see also step 49 on page 140).
Siemens Enterprise Communications GmbH & Co. KG recommends to
deactivate X-Server for saving resources and preventing negative influences on
the OpenScape UC Application performance. It is also a good idea to deactivate
desktop environments such as KDE or GNOME for minimizing risks and saving
system resources.
You do this by deactivating the following check boxes during the SLES installation
in step Server Base System in the Graphical Environment section:
GNOME Desktop Environment for Server
KDE Desktop Environment for Server
X Window System
You can perform this deactivation also after an SLES setup by changing the
default runlevel to 3 using YaST (Yet another Setup Tool) or editing the /etc/
inittab file by opening it with the following command and the vi editor
vi /etc/inittab
Then look for the following line:
# The default runlevel is defined here
Change the ensuing line as follows:
id:3:initdefault:
A31003-S5070-J100-12-7631, 02/2013
1035
Save the file and close the editor vi by entering :wq. This sets the default runlevel
to Full multiuser with network.
NOTE: If you need to run X-Server for local or remote administration, do not use
xhost admission control.
NOTE: X-Server is not required for starting e.g. IBM Lotus Domino Setup. This
may also occur by using SSH with X11 forwarding or Xauthority / xauth to access
the computer remotely.
A.1.3 User Account Guidelines

A.1.3.1 Assigning and Setting Up User Accounts
End-user accounts shall not be created on the application computer. It is however
good practice to create user accounts for administrators so administrators have
a personal login with user rights from where they can switch to root when needed
by using SU.
NOTE: If you are performing procedures remotely and must use the root
account, log in as user account sysad and then switch to user root using the
switch user su - root command.
A.1.3.2 Built-In Accounts

OpenScape UC Application creates the ID for user sym and a group sym. This
user cannot log on, though.
A.1.3.3 Secured Linux Passwords

Please conform to the customer's password policies. If no password policies are
available, it is best to apply the following password criteria:
1036
Minimum password length 15 characters
At least one capital letter
At least one small letter
A31003-S5070-J100-12-7631, 02/2013
At least one digit
At least one special character
A.1.4 Access Privileges

Open in the YaST System > System > /etc/sysconfig Editor > System >
Security > Permissions > PERMISSION_SECURITY and set
PERMISSION_SECURITY from its default value easy local to value secure
local.
A.1.5 Monitoring and Auditing

It is recommended that syslog entries be inspected periodically using either tool
supported or manual audits.
A.1.6 Virus Scanner

OpenScape UC Application was tested with common Linux virus scanners.
Please note however that the common vectors to upload viruses like FTP servers,
file shares and E-mail systems are not part of an OpenScape UC Application
server and in addition no end-user accounts exist on the server. The virus
scanner policy settings may affect the computer's performance.
The OpenScape UC Application functionality was tested with the following virus
scanners in case a virus scanner is to be installed all the same:
F-Secure Linux Server
McAfee
Trend-Micro
A31003-S5070-J100-12-7631, 02/2013
1037
Hardening Settings in the OpenScape UC Application
A.2 Hardening Settings in the OpenScape UC Application

Execute the following setup and configuration instructions in the OpenScape UC
Application for hardening purposes:
A.2.1 No TTS or ASR

Do not install or configure TTS or ASR by excluding arguments such as uc-tts*
and uc-asr* from all osc-setup commands or other script executions.
A.2.2 Configuring the Media Server

1. Open the following address in a browser:
2. Log in.
3. Open Configuration > Unified Communications > Configuration > Media
Server.
1038
A31003-S5070-J100-12-7631, 02/2013
4. Click on the small triangle to the right of the connection entry and select Edit...
or click on the Media Server entry in the Name column.
5. Click on IP Telephony (SIP).
6. In the Listening points for SIP networking section, click on the radio
buttons UDPListeningPoint and TCPListeningPoint and then enable the
Remove button. This will deactivate UDP and TCP as signaling protocols for
the media server.
A31003-S5070-J100-12-7631, 02/2013
1039
8. Click on Streaming -IVR (TTS, ASR, SDP).

9. Click on the SDP tab.
10. Set the Security mode parameter to value Secure Only.
11. Save this configuration.
A.2.3 Deactivating User Accounts

NOTE: See Section B.1, General Operation of YaST, on page 1044 for helpful
information about operating YaST.
1. Open Security and Users > User Management.
2. If users hipatham, hipathcol or webad exist, edit each of them, activate the
Disable User Login check box and select the Accept button.
A.2.4 Configuring the Security Certificates

Use the official certificates on the Framework, the CMP and the WebClient as
described in section Configuring a Certificate Strategy of the administrator
1040
A31003-S5070-J100-12-7631, 02/2013
A.2.5 Backing up the Response File

Move the knut.responsefile.txt response file to a safe location (USB
stick, for example) and remove it from the computer. The file is typically found in
the /root directory.
IMPORTANT: The response file is not currently contained in the system backup
sets, but it is needed to rebuild the system during a crash recovery.
NOTE: In case of Large Deployment there is a response file on the application

computer, on all frontend computers and media server computers. All of them
must be backed up.
NOTE: The restore mechanism uses the database administrator password from
the original system, where the backup was taken, to access the Solid database.
If this password is not known, no recovery is possible. This password is defined
in the response file and that is why the response file must be backed up in a safe
location.
A31003-S5070-J100-12-7631, 02/2013
1041
1042
A31003-S5070-J100-12-7631, 02/2013
IG_AppendixYast.fm
Using YaST instead of zypper or rpm
B Using YaST instead of zypper or rpm

IMPORTANT: Using yast or zypper you may exclusively install SLES RPM
packages. You must not install any RPM packages of the OpenScape UC Application with yast or zypper. osc-setup must be used instead.
In this documentation, Zypper is used to perform the following actions:
Listing the available installation media

zypper lr
Providing an installation source

Example:
zypper ar cd://?devices=/dev/hdc,/dev/hdd osc
Removing an installation source

Example:
zypper rr 1
Search for all RPM installation packages with a specific name or partial name
having OpenScapeUC as name or containing OpenScapeUC in a part of their
name.
Examples:
rpm -q OpenScapeUC
This command searches all packages having OpenScapeUC as name or
containing OpenScapeUC in a part of their name.
rpm -q | grep uc-tts announc languagepack
This command searches all packages whose name or partial name is uctts, announc or languagepack.
YaST can be used instead of zypper or rpm to execute these actions. The
operation of YaST in general and for these purposes in particular is described in
the following subsections.
A31003-S5070-J100-12-7631, 02/2013
1043
IG_AppendixYast.fm
General Operation of YaST
B.1 General Operation of YaST

1. Enter yast in a console.
2. Use the , , and keys to navigate between the entries displayed.

3. Push the TAB key several times to jump from one GUI element (list entry,
button, check box, input field, menu item etc.) to another. Use the ALT + TAB
key combination to go backwards through these GUI elements.
The CTRL + F and CTRL + B key combinations have the same effect.
1044
A31003-S5070-J100-12-7631, 02/2013
IG_AppendixYast.fm
4. The elements whose labels contain a letter marked in yellow can be selected
by pushing the ALT key and the letter marked in yellow.
Example:
ALT + H opens the help.
A31003-S5070-J100-12-7631, 02/2013
1045
IG_AppendixYast.fm
5. A focused GUI element (displayed with a green background) will lose its focus
when the TAB key is pushed. If no GUI element is focused, you can use the
and keys to move a slider.
1046
A31003-S5070-J100-12-7631, 02/2013
IG_AppendixYast.fm
6. Push the ESC key to close selection dialogs.
A31003-S5070-J100-12-7631, 02/2013
1047
IG_AppendixYast.fm
yast instead of zypper Ir
B.2 yast instead of zypper Ir

Instead of the zypper lr command used e. g. in step 5 on page 238, you can
execute the steps described in this section using YaST to display the installation
media provided.
1048
A31003-S5070-J100-12-7631, 02/2013
IG_AppendixYast.fm
yast instead of zypper Ir
2. Select the Installation Source entry by pushing the and keys.
A31003-S5070-J100-12-7631, 02/2013
1049
IG_AppendixYast.fm
yast instead of zypper ar
B.3 yast instead of zypper ar

The provisioning of an installation source can be performed by using a command
with the pattern
zypper ar <URI> <Alias>
(see Section 5.3.1.2, Creating a Repository in osc-setup by using local
Installation Sources, on page 237). You can also execute the following steps in
YaST.
1050
A31003-S5070-J100-12-7631, 02/2013
IG_AppendixYast.fm
4. Enter the ALT + a key combination.

A31003-S5070-J100-12-7631, 02/2013
1051
IG_AppendixYast.fm
5. Enter the ALT + l key combination.
1052
A31003-S5070-J100-12-7631, 02/2013
IG_AppendixYast.fm
6. Enter the ALT + e key combination.
7. Enter the ALT + i key combination.
A31003-S5070-J100-12-7631, 02/2013
1053
IG_AppendixYast.fm
8. Enter the ALT + o key combination.
9. Use the key to navigate to the directory in which the ISO file of the
OpenScape UC Application is stored.
1054
A31003-S5070-J100-12-7631, 02/2013
IG_AppendixYast.fm
10. Use the TAB key to change to the right-hand section and select the ISO file.
A31003-S5070-J100-12-7631, 02/2013
1055
IG_AppendixYast.fm
11. Enter the ALT + o key combination.
12. Enter the ALT + n key combination.
1056
A31003-S5070-J100-12-7631, 02/2013
IG_AppendixYast.fm
yast instead of zypper rr
B.4 yast instead of zypper rr

If you wish to remove an installation source, execute the following steps instead
of using the zypper rr command:
A31003-S5070-J100-12-7631, 02/2013
1057
IG_AppendixYast.fm
4. Push the TAB key several times until the first medium provided is selected.
1058
A31003-S5070-J100-12-7631, 02/2013
IG_AppendixYast.fm
5. Push the key several times until the first medium to be removed is selected.
6. Enter the ALT + t key combination.
A31003-S5070-J100-12-7631, 02/2013
1059
IG_AppendixYast.fm
yast instead of zypper se or rpm -q
B.5 yast instead of zypper se or rpm -q

To search a specific RPM package, you can execute the following steps.
1060
A31003-S5070-J100-12-7631, 02/2013
IG_AppendixYast.fm
2. Select the Software Management entry by pushing the and keys.
A31003-S5070-J100-12-7631, 02/2013
1061
IG_AppendixYast.fm
4. If you want to display the installation packages sorted by categories, continue

with this and the following steps. If you want to display packages with a
specific name, continue with step 8 on page 1067.
Enter the ALT + f key combination.
1062
A31003-S5070-J100-12-7631, 02/2013
IG_AppendixYast.fm
5. Push the space bar.
A31003-S5070-J100-12-7631, 02/2013
1063
IG_AppendixYast.fm
6. Push the key five times, then push the space bar.
1064
A31003-S5070-J100-12-7631, 02/2013
IG_AppendixYast.fm
7. According to the packages you want to list, execute one of the following
substeps:
a) If you want to list the base packages,
push the key two times to select Base,
then push the return key.
One of these packages must be installed before you install other

OpenScape UC Application packages.
The packages displayed have the following meaning:
OpenScapeUC_Large_BE: For the deployment scenario Large

Deployment, this package contains the installation of the central
OpenScape UC Application component on the application computer
(backend) (see step 1 on page 282).
OpenScapeUC_Large_FE: For the deployment scenario Large

Deployment, this package contains the installation of OpenScape UC
Application components on all frontend computers (see step 4 on
page 293).
OpenScapeUC_Large_MS: For the deployment scenario Large

Deployment, this package contains the installation of OpenScape UC
Application components on all media server computers (see step 4 on
page 297).
A31003-S5070-J100-12-7631, 02/2013
1065
IG_AppendixYast.fm
OpenScapeUC_Small: This package contains the OpenScape UC

Application installation on the application computer for a connection
to a HiPath 4000 (see step 1 on page 263).
OpenScapeUC_StandardDuplexSmall: For the deployment

scenario Small Deployment, this package contains the OpenScape
UC Application installation on the application computer for a
connection to an OpenScape Voice (see step 1 on page 263). This
package contains the OpenScapeUC_Small package and the Voice
Assistant.
b) If you want to list additional packages,
push the key once to select AddOns,
The packages displayed have the following meaning:
1066
OpenScapeUC_4kaddons: If you want to connect the OpenScape

UC Application to a HiPath 4000, this package must be installed on
the application computer after the OpenScapeUC_Small package
scs_gwbeexch: This package installs the connection to Microsoft

Exchange as an alternative to connecting Lotus Domino (see Section
13.2, Connecting Microsoft Exchange, on page 624).
A31003-S5070-J100-12-7631, 02/2013
IG_AppendixYast.fm
scs_gwbenotes: This package installs the connection to Lotus Notes

as an alternative to connecting Microsoft Exchange (see step 3 on
page 635).
c) If you want to display the packages for an additional installation of

languages for announcements, for the Auto Attendant or the Voice Portal,
push the key three times to select Languages,
mediaserver_announcements_<language_code> is a package for the

installation of an announcement language,
mediaserver_autoattendant_languagepack_<language_code> is a
package for the installation of an Auto Attendant language, and
mediaserver_voiceportalspeech_languagepack_<language_code>
is a package for the installation of a Voice Portal language (see step 13
on page 271 to step 17 on page 276 or step 11 on page 301 to step 15 on
page 307).
8. If you want to display packages with a specific name, enter the ALT + s key
combination.
A31003-S5070-J100-12-7631, 02/2013
1067
IG_AppendixYast.fm
1068
A31003-S5070-J100-12-7631, 02/2013
IG_AppendixYast.fm
9. Enter e. g. openscape followed by the ALT + o key combination.
10. For each package selected, a long description is available. To activate it,
proceed as follows:
A31003-S5070-J100-12-7631, 02/2013
1069
IG_AppendixYast.fm
a) Enter the ALT + i key combination.
b) Enter the ALT + l key combination.
11. Enter ALT + i followed by ALT + f to display all installed files which have been
installed for the package selected.
1070
A31003-S5070-J100-12-7631, 02/2013
IG_AppendixYast.fm
A31003-S5070-J100-12-7631, 02/2013
1071
IG_AppendixYast.fm
12. Enter ALT + i followed by ALT + r to view on which packages the package
selected depends.
1072
A31003-S5070-J100-12-7631, 02/2013
IG_AppendixYast.fm
yast instead of zypper in
B.6 yast instead of zypper in

IMPORTANT: Using yast or zypper you may exclusively install SLES RPM
packages. You must not install any RPM packages of the OpenScape UC Application with yast or zypper. osc-setup must be used instead.
To install an RPM package by using YaST, proceed as follows:
1. To select the package to install, follow the instructions in Section B.5, yast
instead of zypper se or rpm -q, on page 1060.
The package status is displayed in the first column:
+: This package has been selected for installation manually.
+: This package has been selected for installation automatically.

This is the case e. g. if another package which depends on this package
has been selected for installation. The screenshot in step 2 on page 1073
shows an example.
>: This package has been selected for the update.
i: This package has been installed.
>: This package has been selected for the uninstallation.
---: Never install this package.
-i-: This package is protected and should not be updated or deleted

manually.
This is the case e. g. if this package has been installed as a package that
depends on the installation of another package. An update or deletion of
the other package would update or delete this package as well.
To display this package installation help, enter ALT + h followed by ALT + p.

2. To select a package for installation, push the + key.
Packages on which the package selected depends will be detected, marked
by a+ and installed during the later installation.
If applicable, dependency issues will be queried.
Select all packages to be installed.
If required, the + can be removed by pushing again the + key.
3. Start the installation of the selected packages by entering ALT + a.
A31003-S5070-J100-12-7631, 02/2013
1073
IG_AppendixYast.fm
yast instead of zypper in
1074
A31003-S5070-J100-12-7631, 02/2013
IG_AppendixWindows.fm
Installing Windows
Preparation
C Installing Windows
This section deals with the sample basic installation of Windows Server 2008 R2
that is widely used as operating system for many applications.
C.1 Preparation
Execute the following perparation steps:
1. Check the requirements defined by Microsoft:
http://technet.microsoft.com/en-us/windowsserver/bb310558
2. Check whether the Windows license code is available.
3. Retrieve the following data:
a) Name of the computer the Windows operating system should be installed
on
b) IP address of the computer the Windows operating system should be
installed on
c) If necessary, retrieve name of the domain the computer should be added
to. Retrieve an administrator user account and password for this domain.
d) Subnet mask
e) IP address of the default gateway
f)
IP address of the preferred DNS server
g) IP address or host name of the NTP server computer

4. Check whether the newest version including all updates of the Windows
operating system is suitable for the application you want to use. The needed
update is to be found in the version tracking info form of the acceptance test
manual.
5. Check whether a remote desktop connection is needed for the computer to
be installed
A31003-S5070-J100-12-7631, 02/2013
1075
Installing Windows
Installation
C.2 Installation
Execute the following steps to install the operating system:
1. Insert the installation DVD and reboot the computer.
1. Select the language, time and currency format and keyboard method.
2. Click the Next button.
1076
A31003-S5070-J100-12-7631, 02/2013
Installing Windows
Installation
3. Click Install now.
4. Select the installation version.

IMPORTANT: The installation version Server Core Installation does not
provide .NET framework, only offers a reduced GUI etc.
A31003-S5070-J100-12-7631, 02/2013
1077
Installing Windows
Installation
6. Click the I accept the license terms check box.
7. Click the Custom (advanced) button.
8. Select the partition you want to install Windows on.
1078
A31003-S5070-J100-12-7631, 02/2013
Installing Windows
Installation
The Windows installation starts.
A31003-S5070-J100-12-7631, 02/2013
1079
Installing Windows
Installation
10. Your computer is prepared for first use.
11. Click the OK button.
1080
A31003-S5070-J100-12-7631, 02/2013
Installing Windows
Installation
12. Enter a password for the administrator, confirm it and click the arrow button.
The desktop is prepared.

13. The Initial Configuration Tasks window opens automatically.
NOTE: You can open it manually by entering oobe into a Windows

command prompt.
A31003-S5070-J100-12-7631, 02/2013
1081
Installing Windows
Installation
14. Click Set time zone link.

15. Click the Change time zone... button.
16. Set the time zone.

18. Click the Internet Time tab.
1082
A31003-S5070-J100-12-7631, 02/2013
Installing Windows
Installation
19. Activate the Synchronize with an Internet time server check box.
20. Enter the name or IP address of the NTP server computer into the Server
field.
21. Click the Update now button.
NOTE: Check if the system time of all OpenScape UC Application-related
(NTP) is often used for synchronizing the system time (see Section 3.1.9.2,
Configuring the NTP Service, on page 66).
24. Click the Configure networking link.
25. Select the Local Area Connection entry with the right mouse button and
select Properties.
26. Select InternetProtocol Version 4 (TCP/IPv4).
A31003-S5070-J100-12-7631, 02/2013
1083
Installing Windows
Installation
27. Click the Properties button.
a) Activate the Use the following IP address check box.

b) Enter the IP address of the computer the Windows operating system
should be installed on.
c) Enter the subnet mask.
d) Enter the IP address of the default gateway.
e) Enter the IP address of the preferred DNS server.
f)
Click the OK button.

29. Close the Network Connections window.
30. Click the Provide computer name and domain link.
1084
A31003-S5070-J100-12-7631, 02/2013
Installing Windows
Installation
31. Click the Change... button.
32. Enter the name of the computer the Windows operating system should be
installed on into the Computer name field.
33. If necessary, activate the Domain check box, enter the domain name and
click the OK button.
NOTE: You are forced to reboot the computer, if you add the computer to a
domain.
A31003-S5070-J100-12-7631, 02/2013
1085
Installing Windows
Installation
35. If the newest version including all updates of the Windows operating system
is suitable for the application you want to use, click the Enable automatic
updating and feedback link.
a) Click Manually configure settings.
b) Click the Change Settings... button in the Windows automatic

updating section.
c) Select the Check for updates but let me choose whether to download
and install them option.
The computer now will periodically check for updates and will inform you.
1086
A31003-S5070-J100-12-7631, 02/2013
Installing Windows
Installation
d) Click the OK button.

e) Click the Close button.
f)
If you want to check for updates immediately, open the Internet Explorer
and select the Safety > Windows update menu option.
36. Check whether you can open an internet web site in the Internet Explorer. The
internet access is needed for the Windows license activation.
37. Click the Active Windows link.
38. Enter the product key into the Product key field. You find the product key on
the Windows installation DVD box.
39. Click the Next button and execute the remaining activation steps.
A31003-S5070-J100-12-7631, 02/2013
1087
Installing Windows
Installation
40. If you need remote access to the computer, click the Enable Remote
Desktop link, activate the Allow connections from computers running
any version of Remote Desktop (less secure) check box and click the OK
button.
41. Close the Initial Configuration Tasks window.

42. The basic Windows installation is complete now.
1088
A31003-S5070-J100-12-7631, 02/2013
IG_Abbreviations.fm
Acronyms
This list shows some important abbreviations.
Acronym
Definition
AD
Active Directory
BCOM
Basic Communication
CA
ComAssistant
CAP
Common Application Platform
CDC
Customer Data Collection
CLM
Customer License Manager
CMP
Common Management Platform
CSTA
Computer-Supported Telecommunications Applications
DLS
Deployment Service
DNS
Domain Name System
E/A
Executive/Assistant
FQDN
Fully Qualified Domain Name
GRUB
Grand Unified Bootloader
HISPA
HiPath Serviceability Platform for Application
HPUM
HiPath User Management
HTTP
Hypertext Transfer Protocol
HTTPS
Hypertext Transfer Protocol over Secure Socket Layer
IIS
Internet Information Services
IM
Instant Messaging
IP
Internet Protocol
IPSec
Internet Protocol Security
JAF
JavaBeans Activation Framework
LAG
Link Aggregration
LCS
Live Communications Server
LDAP
Lightweight Directory Access Protocol
LIN
Location Identification Number
LVM
Logical Volume Manager
MGCP
Media Gateway Control Protocol
MLHG
Multi-Line Hunt Group
MOP
Method Of Operation
MRCP
Media Resource Control Protocol
NCPE
Node Configuration Policy Editor
A31003-S5070-J100-12-7631, 02/2013
1089
IG_Abbreviations.fm
Acronym
Definition
NFS
Network File System
NIC
Network Interface Card
NTP
OND
One-Number Device
ONS
One-Number Service
OS UC Appl.
OSV
OpenScape Voice
OVA
Open Virtualization Archive
OVF
Open Virtualization Format
OWA
Outlook Web Access
PABS
Private Address Books
PKI
Public Key Infrastructure
PSM
Professional Services Center of Competence UC
RTP
Real-time Transport Protocol
RTCP
RTP Control Protocol
SABS
Shared Address Books
SAN
Storage Area Network
SIP
Session Initiation Protocol
SLES
SUSE Linux Enterprise Server
SMP
Symmetric Multiprocessing
SMS
Systems Management Server
SNMP
Simple Network Management Protocol
SOAP
Simple Object Access Protocol
SPML
Service Provisioning Markup Language
SRTP
Secure Real-Time Transport Protocol
SSDP
Smart Services Delivery Platform
SSE
Streaming SIMD Extension
SSL
Secure Socket Layer
SSO
Single Sign-On
SWS
Software Supply Server
TCP
Transmission Control Protocol
TLS
Transport Layer Security
TTS
Text-to-Speech
UC
Unified Communications
UCMA
Unified Communications Managed API
UEFI
Unified Extensible Firmware Interface
UDP
User Datagram Protocol
1090
A31003-S5070-J100-12-7631, 02/2013
IG_Abbreviations.fm
Acronym
Definition
UUID
Universally Unique Identifier
WebDAV
Web-based Distributed Authoring and Versioning
XMLPS
XML Phone Service
XMPP
Extensible Messaging and Presence Protocol
XPR
OpenScape Xpressions or HiPath Xpressions
X server
X Window System
X11
X Window System
YaST
Yet another Setup Tool
A31003-S5070-J100-12-7631, 02/2013
1091
IG_Abbreviations.fm
1092
A31003-S5070-J100-12-7631, 02/2013
Index
32-bit
falling back to 32-bit 943
falling back to HiPath 8000 Assistant V3.0
32-bit 938
upgrading to 64-bit 937
A
Additional computers, installing 290, 323
installing for large deployment 281, 314
installing for small deployment 263
migration on the computer 902
updating 718
upgrading 773
B
Bonding 165
C
Channel bonding 165
Check
migration 898
Checking
Facade server on SLES 559
installation 347
Rapidstat UC 349
Client installations
general information 487
Clients, configuration 616
CLM
backing up the access configuration 668, 941
installing 756
restoring the access configuration 801, 941
Common management platform
configuring 359
creating OpenScape UC Application users 485
Computer installation 115
Configuration
virtual computer 55
Configuring
common management platform 359
installation of large deployment 203
installation of small deployment 198
installation of the OpenScape UC Application 195
installation of very large deployment 218
OpenScape UC Application 359
Z
Connecting
IBM Lotus Domino 624
instant messaging 595
Microsoft Lync Server 579
Microsoft Office Communications Server 579
OCS 579
Connection
groupware 623
creating users 485
Customer license manager
backing up the access configuration 668, 941
installing 756
restoring the access configuration 801, 941
Customer, information provision 30
D
DAR file 292, 325
Deployment scenario 25
Integrated Duplex 27
large deployment 25
Mediaserver Standalone 26
Multiple Communication Server Admin 27
small deployment 25
Standard Duplex (medium) 26
Standard Duplex Voice 27
Documentation feedback 22
Domain system environment, preparation 32
Domino connection 624
E
Ethernet bonding 165
F
Facade server
checking on SLES 559
installing 549
installing on SLES 552
operating systems 551
Falling back
after upgrade abandoning 800
to 32-bit 943
to HiPath 8000 Assistant V3.0 32-bit 938
File system
installation 116
Frontend computer
installing on the computer 293, 326
A31003-S5070-J100-12-7631, 02/2013
1093
Index
updating 720
upgrading 782
G
Groupware
connecting IBM Lotus Domino 624
connecting Microsoft Exchange 624
connection 623
H
HiPath 4000
connection 745
connection via OpenScape Voice 484
HiPath UM 268, 285, 318, 924
HiPath user management 268, 285, 318, 924
HPUM 268, 285, 318, 924
I
IBM Lotus Domino
installing the connection 624
upgrading the connection 753, 774
IM connection 595
Information provision by the customer 30
Installation
checking 347
computer 115
file system 116
operating system 116
providing the installation source 234, 671
troubleshooting 312, 345
Installing
additional computers 290, 323
application computer for large deployment 314
application computer for Small Deployment 263
application computer for small deployment 281
CLM 756
Facade server 549
hotfix 727
IBM Lotus Domino 624
large deployment 281, 314
licenses 485
media server computer 297
Microsoft Lync Server 582
Microsoft Office Communications Server 582
Mobile Client Facade server 549
OCS 582
on the frontend computer 293, 326
on the media server computer 330
small deployment 263
UCMA proxy web service 582
virtual computer 41
1094
VMware tools 62
Web Collaboration 563
Installing a hotfix 727
Installing VMware tools 62
Instant messaging
connecting 595
uninstalling 617
updating 617
Integrated deployment
migration table 746
migration to small deployment 887
port list 363
updating 711
upgrade table 746
upgrading 749
Integrated Duplex 27
L
LAG 165
Large deployment 25
configuring the installation 203
installing 281, 314
migration from small deployment 899
port list 411, 444
response file 204
updating 716
upgrade table 745
upgrading 771
Licences, installing 485
Link aggregation 165
Link bundling 165
Lotus Domino connection 624
M
installing 297
installing on the computer 330
updating 723
upgrading 786
Mediaserver Standalone 26
Microsoft Lync Server
installing 582
Microsoft Lync Server connection 579
Microsoft Office Communications Server
installing 582
Microsoft Office Communications Server
connection 579
Migrating 659
Migration 916
check 898
from integrated deployment to small
A31003-S5070-J100-12-7631, 02/2013
Index
deployment 887
from small deployment to large deployment 899
on the application computer 902
on the frontend computer 905
on the media server computer 910
tables 745
Mobile client deployment
Mobile Client Facade server --> Facade server 549
Multicast 419, 424, 453, 458, 476
Multiple Communication Server Admin 27
N
NIC bonding 165
NTP 65, 66
O
OCS
connecting 579
installing 582
OpenScape Click-to-Dial Browser Plug-in
features 511
general considerations 511
installation, default installation 513
installation, general information 512
installing Firefox retrospectively 519
modifying the installation 518
performing an update installation 520
uninstalling Firefox 518
uninstalling via control panel 522
uninstalling via the setup.exe 521
uninstalling, general information 521
update installation (repair), general information 519
updating/uninstalling, general information 517
changing application parameters 544
features 537
installation requirements 538
performing the installation 540
repairing 545
setup adjustments 539
supported clients 538
uninstalling 546
updating 545
updating and uninstalling in general 543
OpenScape clients, configuration 616
OpenScape Conference Extension for Lotus Notes
installation, installation process 503
installation, requirements 503

performing the upgrade installation 507
uninstalling 508
updating/uninstalling, in general 506
OpenScape Conference Extension for Microsoft
Outlook
general description 487
initial configuration 490
initial configuration, OpenScape user account 491
initial configuration, Single Sign-On (SSO) 495
initial configuration, Windows user account 493
Installation
Mass Rollout 488
installation process 489
installation, requirements 489
installing the terminal server, general
information 497
performing an uninstallation 500
performing the upgrade installation 500
terminal server installation, creating user
configuration files 498
terminal server installation, installation process 497
terminal server installation, requirements 497
update/upgrade, msi-package 501
updating/uninstalling, in general 498
usage requirements 488
installation 509
OpenScape UC Application 485, 711
accounts 193
checking installation requirements 192
configuring 359
connection to HiPath 4000 745
connection to OpenScape Voice 745, 746
deployment scenarios 25
groupware connection 623
hotfix 727
installation check 347
installation overview 27
installation requirements 192
migrating 659
preparing 25, 32, 115
uninstalling the groupware packages 624
updating 659, 711
upgrading 659
Web Collaboration 563
OpenScape UC Application accounts 193
OpenScape Voice
A31003-S5070-J100-12-7631, 02/2013
1095
Index
connection 479
HiPath 4000 connection 484
OpenStage client
configuring the DSS keys 533
features 523
installing the call log application 531
Installing the main application 524
installing the phonebook application 529
Operating system
Facade server 551
hardening 1031, 1075
installation 116
installing on a virtual computer 58
Operating system hardening 1031, 1075
P
point-to-multipoint connection 476
point-to-point connection 476
Port list 359
integrated deployment 363
large deployment 411, 444
Preparation
upgrading from 32-bit to 64-bit 937
Preparing
OpenScape UC Application 25, 115
R
Rapidstat UC 349
Requirements
installation of the OpenScape UC Application 192
Response file
large deployment 204
very large deployment 219
Routing schema
Multicast 419, 424, 453, 458, 476
Unicast 419, 424, 453, 458, 476
S
Small deployment 25
installing 263
migrating from integrated deployment 887
migration table 745
migration to large deployment 899
port list 386
response file 199
updating 711
upgrade table 745
1096
upgrading 750
Standard Duplex (medium) 26
T
Time synchronization 32, 65
Trunking 165
U
UCMA 582
UCMA proxy web service
installing 582
uninstalling 590
UEFI 46, 83, 119, 162
Unicast 419, 424, 453, 458, 476
Unified Communications Managed API 582
Unified Extensible Firmware Interface 46, 83, 119, 162
Uninstalling
groupware packages of the OpenScape UC
Application 624
UCMA proxy web service 590
Updating 659, 711
application computer 718
frontend computer 720
Upgrade
abandoning 800
falling back 800
falling back to 32-bit 943
falling back to HiPath 8000 Assistant V3.0
32-bit 938
tables 745
Upgrading 659
application computer 773
frontend computer 782
Lotus Domino connection 753, 774
V
Very large deployment
response file 219
Virtualization 33
configuration 55
A31003-S5070-J100-12-7631, 02/2013
Index
configuration parameters 35
hardware requirements 35
installing a virtual computer 41
installing the operating system 58
VMware tools 62
W
Web Collaboration
installing 563
A31003-S5070-J100-12-7631, 02/2013
1097

OpenScape UC Application V7 Installation and Upgrade, Installation Guide, Issue 12

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OpenScape UC Application V7 Installation and Upgrade, Installation Guide, Issue 12

Uploaded by

Copyright:

Available Formats

Documentation

Siemens Enterprise Communications

Our Quality and Environmental Management

Copyright Siemens Enterprise

Siemens Enterprise Communications

OpenScape, OpenStage and HiPath are registered

3 Providing Virtual Computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

4.2.2.2 Creating the swap Partition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5 Installing the OpenScape UC Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

5.3.4.6 Resolving Installation Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6 Configuring the OpenScape UC Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7 Client Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487

10.1.3.3 Installing the Google Apps Presence Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

11 Connecting the Microsoft Office Communication Server/Microsoft Lync Server . . . . . . . . . . . . . . .

12 Connecting Instant Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13 Groupware Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623

15.5 Upgrading V3 R2 or V6 R0 Integrated Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 749

B Using YaST instead of zypper or rpm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C Installing Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1075

Section 15.14, Migration from V7 Integrated Deployment to V7 Small Deployment, on FRN4514

Installation of the OpenScape UC Application using the osc-setup script (see

The RPM OpenScapeUC_ssdpaddons is always automatically included in the setup

Information about fallback solutions (syncUC) and partitions updated:

Uninstalling the OpenScape UC Application is not supported (see Chapter 16,

The Web Collaboration servers do not offer mutual reliability.

OpenScape UC Application V7 R0 supports connections to OpenScape Voice V6 and FRN5144

Upgrading OpenScape UC Application V4 R0 to V7 R0 directly is not supported (see

Section 15.3.2, Installing a Hotfix, on page 727 updated.

Openfire server and MySQL server

Upgrading OpenScape UC Application V4 R0 to V7 R0 directly is not supported:

Several minor changes performed in Section 12.5, Initial Configuration of the

In case of a setup on an OpenStage telephone the IP address of the load balancer

Minor changes in Chapter 12, Connecting Instant Messaging

Mobile Client Facade server:

More information about the SI_DB_LOGON_PASSWORD parameter in configuration file

Migration from V7 Large Deployment to V7 Very Large Deployment added:

The following sections have been added:

Applications created with the Application Builder of the OpenScape UC Application

Data restore step added to Section 15.10, Upgrading V3 R2 or V6 R0 Small

Information about OpenScape Fusion for Google Apps added:

Section 15.12, Upgrading V3 R2 or V6 R0 Small Deployment in Case of only one

Openfire configuration steps changed, moved or deleted and screenshots updated

ethereal library replaced with wireshark (see step 52 on page 140)

If you cannot upgrade to V7 R0 Integrated Simplex for subsequently migrating to

Uninstalling the OpenScape UC Application V7 R0 has been released for Integrated

Section 15.12, Upgrading V3 R2 or V6 R0 Small Deployment in Case of only one

Links to steps replaced with the contents of such steps.

If you wish to upgrade to an OpenScape UC Application V7 R0 connected to a HiPath FRN6067

Changes concerning the Virtual Appliance:

If HiPathCA services on the application computer communicate with HiPathCA

If the OpenScape UC Application V7 shall be connected to an OpenScape Voice V7

If the OpenScape UC Application is connected to an OpenScape Fusion client, an

Section 15.7, Smooth Update/Upgrade of V3 R2, V6 R0 or V7 R0, on page 803

An OpenScape UC Application V3 R2 or earlier with an OpenScape Voice V4 R1 or CQ00220105

The Common Management Portal has been renamed as Common Management

The file /var/siemens/hp4kprovisioning/ConfigureBackup/

The instructions in section Configuring the Address Translation Context in the

The directory /opt/siemens/common/conf/diagnostic_configurations

Section 15.7, Smooth Update/Upgrade of V3 R2, V6 R0 or V7 R0, on page 803

Installation and configuration of OpenScape Fusion for Google Apps updated.

If you upgrade from OpenScape UC Application V3 R2 to V7, stop Loquendo before

A hint to the administrator documentation OpenScape UC Application Configuration

Only SP2 of SLES 11 is supported (see e. g. step 1 on page 116).

Mobile Client Facade Server: