OpenScape Enterprise Express V9, Staging Guide, Installation Guide, Issue 20.

OpenScape Enterprise Express V9
Staging Guide
Installation Guide
A31003-S5190-J100-20-7631
Our Quality and Environmental Management Systems are
implemented according to the requirements of the ISO9001 and
ISO14001 standards and are certified by an external certification
company.
Copyright © Unify Software and Solutions GmbH & Co. KG. 07/2017
Mies-van-der-Rohe-Str. 6, 80807 Munich/Germany
All rights reserved.
Reference No.: A31003-S5190-J100-20-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.
Unify, OpenScape, OpenStage and HiPath are registered trademarks of Unify Software and
Solutions GmbH & Co. KG.. All other company, brand, product and service names are
trademarks or registered trademarks of their respective holders.
unify.com
Contents
Contents
1 OpenScape Enterprise Express V9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

1.1 OpenScape Enterprise Express V9 Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2 Installing the Hardware Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.1 Inventory & Installation Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.1.1 Dell PowerEdge R630 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.2 Printed Installation Guides and Digital Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.3 Cable Connections to Dell PowerEdge R630 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.4 RAID Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.5 Modifying the Server UEFI Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.6 iDRAC Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.7 iDRAC and Remote Console Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.8 Boot of ESXi Hypervisor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3 VM Environment and Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.1 OSEE VM Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.2 OSEE-AI VM requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4 VMware ESXi Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
4.1 Configuring VMware ESXi . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
4.2 Downloading vSphere Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
4.3 Starting vSphere Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
4.4 VMware ESXi network configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
4.5 Enable Remote SSH and ESXi Shell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
4.6 Execution of the OSEEreconfig.sh script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
4.7 Configuring VMware ESXi (Deployment E) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
5 OVA deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
5.1 Preparation steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
5.2 Deploy the OSEE-AI OVA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
5.3 Deploy the OSEE V9 OVAs with AI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
5.4 Configure the SBC-THIG VMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
5.4.1 Apply SBC-THIG license . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
5.5 Configure the OSV VMs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
5.6 Power on the UC VM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
5.7 Setup and Configuration of the Windows VMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
5.7.1 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
5.7.2 Configure the Windows VMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
5.7.3 Windows Server 2012 R2 Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
5.7.3.1 Windows Server Administrator Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
5.7.3.2 Install .NET Framework 3.5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
5.7.3.3 Install VMWare Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
5.7.3.4 Update Windows Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
5.7.3.5 Configuration of Windows pt.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
5.7.4 Silent Installation Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
5.8 OpenScape Contact Center Licensing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
6 OVA deployment on a Resource Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
6.1 Preparation steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
A31003-S5190-J100-20-7631, 07/2017
OpenScape Enterprise Express V9, Staging Guide, Installation Guide 3
Contents
6.1.1 OSEE Designated networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

6.2 Deploy the OSEE-AI OVA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
6.3 Deploy the SBC-THIG OVA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
6.3.1 Apply SBC-THIG license . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
6.4 Deploy the OSV OVA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
6.5 Deploy the UC OVA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
6.6 Setup and Configuration of the Windows VMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
6.6.1 Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
6.6.2 Deploy the Windows OVA template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
6.6.3 Windows Server 2012 R2 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
6.6.3.1 Windows Server Administrator Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
6.6.3.2 Install .NET Framework 3.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
6.6.3.3 Install VMWare Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
6.6.3.4 Update Windows Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
6.6.4 Silent Installation Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
6.7 OpenScape Contact Center Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
7 OSEE Automated Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
7.1 Copy Additional Language Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
7.2 Preparation Steps for OSEE Deploy script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
7.3 Import and Run OSEE Deploy script. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
8 OpenScape Branch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
8.1 OpenScape Branch Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
8.2 Configuration of OpenScape Branch or Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
8.3 Adding and updating Media Server announcement files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
8.4 Upload licenses to Common Management Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
8.5 Apply licenses to the OpenScape Branch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
9 OpenScape Deployment Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
9.1 DLS Account Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
9.2 Enable DLS SSO functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
9.3 Enable Plug&Play via DHCP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
10 OpenScape Xpressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
10.1 Special Server Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
10.2 Customizing the AutoAttendant. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
10.2.1 Example with predefined AutoAttendant script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
10.2.2 Steps to modify the AutoAttendant Destination Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
10.2.3 Steps to modify the Announcements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
10.3 Number Conversion (NCO) rules modification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
11 OpenScape Contact Center. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
11.1 OpenScape Contact Center Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
11.2 OpenScape Contact Center Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
11.2.1 System requirements for a client machine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
11.2.2 Software installation on a client machine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
12 OpenScape Contact Center Extensions, Concierge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
12.1 OpenScape Contact Center Extensions Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
12.2 Concierge Client Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
13 OpenScape Trace Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
13.1 OpenScape Voice Tracing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
A31003-S5190-J100-20-7631, 07/2017
4 OpenScape Enterprise Express V9, Staging Guide, Installation Guide
Contents
13.2 Configure OpenScape Trace Manager to Collect Phone QoS data (Optional) . . . . . . . . . . . . . . . . . . . . . 88
13.3 Configure Phone Devices to Send QoS Data to OSV-TM Listener (Optional). . . . . . . . . . . . . . . . . . . . . . 90
13.4 Configure UC Remote Logging to OpenScape Trace Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
14 OpenScape UC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
14.1 Configuration of Trusted Transfer Mode (TTM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
15 User Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
15.1 Create Subscriber Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
15.2 Create Standard Locality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
15.3 Create User Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
15.4 Example of Creating a UM User with the created default Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
16 OSEE Hardening . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
16.1 Apply Group Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
16.2 Running the common security hardening script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
16.2.1 Execution of the OSEEsecurity.sh hardening script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
A Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
A.1 Passwords for OSV Server login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
A.2 Passwords for OSV Apps Server login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
A.3 Password for Windows Server Login. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
A.4 Passwords for OpenScape Deployment Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
A.5 Passwords for OpenScape Xpressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
A.6 Passwords for OpenScape Contact Center. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
A.7 Passwords for Concierge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
A.8 Passwords for OpenScape Trace Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
A.9 Passwords for SBC-THIG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
B Survival Authority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
C OSEE Windows vApp. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
D Optional redundancy to cover total failure of the OSEE server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
D.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
D.2 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
D.3 Configuring Server Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
D.3.1 vCenter Server OVF Template Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
D.3.2 vSphere Replication Virtual Appliance Deployment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
D.3.3 vSphere Replication Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
D.3.4 Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
E Optional configuration for OSCCE, Concierge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
E.1 Associate multiple office codes to a tenant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
F Optional XPR Database Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
G C-SBC Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
H Optional Direct Access to OSEE VMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
I Softcom InsideEdge (OSCC Analytics) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
J Call Director SIP Service Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
K Optional DNS info update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
L OpenScape Accounting V2 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
M Optional installation of an external OSCC-E server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
M.1 SBC THIG configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
A31003-S5190-J100-20-7631, 07/2017
Contents
M.2 OpenScape Voice configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

N Emergency Calling capability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
O Collocated OSEE deployments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
P Optional configuration to enable XPR Resource Type for User Templates in CMP User Management . .
148
Q Optional Steps to add an external third party CSTA Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
A31003-S5190-J100-20-7631, 07/2017
HOC.fm
History of Changes
Issue Date Description
Issue 1 10/2016 First issue of the OSEE V9 Staging Guide.
The following chapters/sections were updated:
• Section 4.7, “Configuring VMware ESXi (Deployment E)”
Issue 2 10/2016 • Section 11.1, “OpenScape Contact Center Configuration”
The following chapters/sections were added:
• Appendix B, “Survival Authority”
The following changes were made:
Issue 3 10/2016 • Section 2.3, “Cable Connections to Dell PowerEdge R630” updated.
• Section 3.2, “OSEE-AI VM requirements” added.
Issue 4 10/2016 Section 5.6, “Power on the UC VM” updated: Network configuration steps removed.
• Section 11.1, “OpenScape Contact Center Configuration” updated.
Issue 5 11/2016 • Section 12.1, “OpenScape Contact Center Extensions Configuration” updated.
• Appendix H, “Optional Direct Access to OSEE VMs” added.
• Section 5.8, “OpenScape Contact Center Licensing” updated.
Issue 6 12/2016
• Section 12.1, “OpenScape Contact Center Extensions Configuration” updated.
Issue 7 12/2016 Section 10.3, “Number Conversion (NCO) rules modification” added.
• Appendix I, “Softcom InsideEdge (OSCC Analytics)” added.
Issue 8 01/2017 • Appendix J, “Call Director SIP Service Installation” added.
• Appendix K, “Optional DNS info update” added.
Issue 9 02/2017 Appendix L, “OpenScape Accounting V2 Configuration” added.
• Section 4.1, “Configuring VMware ESXi” updated.
Issue 10 02/2017
• Appendix M, “Optional installation of an external OSCC-E server” added.
• Section 4.7, “Configuring VMware ESXi (Deployment E)” updated.
• Section 5.5, “Configure the OSV VMs” updated.
Issue 11 03/2017
• Section 6.4, “Deploy the OSV OVA” updated.
• Section 6.6.3, “Windows Server 2012 R2 Installation” updated.
Issue 12 03/2017
• Appendix N, “Emergency Calling capability” added.
• Appendix O, “Collocated OSEE deployments” added.
Issue 13 04/2017 Section 2.3, “Cable Connections to Dell PowerEdge R630” graph updated.
Issue 14 04/2017 Appendix K, “Optional DNS info update” updated.
Appendix P, “Optional configuration to enable XPR Resource Type for User Templates in
Issue 15 05/2017
CMP User Management” added.
Issue 16 05/2017 Transfer of some sections from OSEE V9 Staging Guide to OSEE V9 Planning Guide.
Issue 17 05/2017 Appendix Q, “Optional Steps to add an external third party CSTA Application” added
A31003-S5190-J100-20-7631, 07/2017
HOC.fm
Issue Date Description

Issue 18 06/2017 Section 14.1, “Configuration of Trusted Transfer Mode (TTM)” added
Section 2.4, “RAID Configuration” updated the steps
Section 4.1, “Configuring VMware ESXi”, update some steps

Section 4.5, “Enable Remote SSH and ESXi Shell” update some steps
Section 4.7, “Configuring VMware ESXi (Deployment E)” update some steps
Section 5.2, “Deploy the OSEE-AI OVA” update some steps
Issue 19 07/2017
Section 5.5, “Configure the OSV VMs” update some steps
Section 5.7.3.5, “Configuration of Windows pt.1” update steps
Section 5.7.4, “Silent Installation Steps” update steps
Section 6.6.2, “Deploy the Windows OVA template” update steps
Section 6.6.3.5, “Configuration of Windows pt.1” update steps
Section 6.6.4, “Silent Installation Steps” update steps
At beginning of the document add a note about the deployments and where they can be
found
Issue 20 07/2017
Section 3.2, “OSEE-AI VM requirements” add a note
Section 7.3, “Import and Run OSEE Deploy script” add a note
A31003-S5190-J100-20-7631, 07/2017
HOC.fm
A31003-S5190-J100-20-7631, 07/2017
OSEE.fm
OpenScape Enterprise Express V9 Installation Checklist
1 OpenScape Enterprise Express V9

IMPORTANT: Always check on Partner Portal or E-Doku for the latest release of
the Staging Guide before proceeding with the installation of OpenScape
Enterprise Express V9.
Note: Info concerning the available OSEE deployments (A, B, C, D, E) that will
be used as a reference throughout the current document can be retrieved from
the OpenScape Enterprise Express V9, Design and Planning Manual, Planning
Guide.
1.1 OpenScape Enterprise Express V9 Installation Checklist
Pre-Installation activities
Item Description Initials
1. Use WebCDC to generate the OSEE configuration files.
2. Download the OpenScape Enterprise Express V9 zipped software package from SWS.
3. Obtain licenses for OpenScape Enterprise Express V9.
4. Configure the Layer 3 routable switches, per customer configured layout.
Installation activities
5. Install the Hardware platform:
• Chapter 2, “Installing the Hardware Platform”.
6. Configure VMware ESXi:
• Chapter 3, “VM Environment and Requirements”
• Chapter 4, “VMware ESXi Configuration”.
7. Locate and add the Licenses.
8. Deploy and configure the OSEE V9 OVAs:
• Chapter 5, “OVA deployment”
• Chapter 6, “OVA deployment on a Resource Pool”
9. Initiate OSEE Automated Installation (OSEE-AI):
• Chapter 7, “OSEE Automated Installation”.
Configuration activities
10. Install and configure OpenScape Branch:
• Chapter 8, “OpenScape Branch”
11. Configure OpenScape Deployment Service:
• Chapter 9, “OpenScape Deployment Service”
12. Configure OpenScape Xpressions:
• Chapter 10, “OpenScape Xpressions”
A31003-S5190-J100-20-7631, 07/2017
OSEE.fm
Configuration activities
13. Configure OpenScape Contact Center and its Client:
• Chapter 11, “OpenScape Contact Center”
14. Install and configure Concierge Client:
• Chapter 12, “OpenScape Contact Center Extensions, Concierge”
15. Configure OpenScape Voice Trace Manager:
• Chapter 13, “OpenScape Trace Manager”
16. Configure OpenScape UC:
• Chapter 14, “OpenScape UC”
17. Create default User Templates:
• Chapter 15, “User Template”
Security activities
18. Enhance OpenScape Enterprise Express V9 Server Security:
• Chapter 16, “OSEE Hardening”
A31003-S5190-J100-20-7631, 07/2017
OSEE.fm
A31003-S5190-J100-20-7631, 07/2017
HW.fm
Installing the Hardware Platform
Inventory & Installation Materials
2 Installing the Hardware Platform
2.1 Inventory & Installation Materials
2.1.1 Dell PowerEdge R630

1. Check inventory and inspect the materials.
2. Check for shipping damage or any shortages and discrepancies of materials.
3. Return and reorder damaged or missing material according to local

procedures.
2.2 Printed Installation Guides and Digital Media

Collect and store in a secure location at the job site all the printed documentation
and digital media for any equipment that you will be installing. This includes, but
is not necessarily limited to the following:
• Dell PowerEdge R630 server printed guides and digital media
• Ethernet switch documentation
• KVM (if so equipped) documentation
• Power distribution unit (PDU) or uninterruptible power supply (UPS)

documentation (if so equipped)
You might need to reference these documents/media for installation procedures,

physical characteristics of the server and other hardware components, and for
troubleshooting procedures.
A31003-S5190-J100-20-7631, 07/2017
HW.fm
Cable Connections to Dell PowerEdge R630
2.3 Cable Connections to Dell PowerEdge R630
The image above shows the connector locations at the back of the Dell
PowerEdge R630.
Item Indicator, button, Description

or connector
1 System The identification buttons on the front and back panels
identification button can be used to locate a particular system within a rack.
When one of these buttons is pressed, the LCD panel on
the front, and the system status indicator on the back,
flash until one of the buttons is pressed again.
2 LP PCIe Allows you to connect a LP PCIe expansion card.
expansion card slot
3 System Allows you to connect the optional system status
identification connector indicator assembly through the optional cable
management arm.
4 iDRAC8 Enterprise port Dedicated management port.
5 Serial connector Allows you to connect a serial device to the system.
6 Video connector Allows you to connect a VGA display to the system.
7 USB connectors Allows you to connect USB devices to the system. The
ports are USB 3.0-compliant.
8 Ethernet connectors Eight integrated connectors
9 Power supply 1 and 2 750 W
1. Connect the following items to the server:
• Keyboard
• Mouse
• Monitor
Note: The server requires a USB keyboard and mouse.
A31003-S5190-J100-20-7631, 07/2017
HW.fm
2. Attach the Ethernet cables:
• to the iDRAC8 port for the management platform to remotely monitor,

troubleshoot, and repair the Dell system even when the system is down.
• to Ethernet port 1 (VMNIC0) for ESXi Management Network.
• to Ethernet port 2 (VMNIC1) and port 3 (VMNIC2) for OSEEWAN.
• to Ethernet port 4 (VMNIC3) and port 5 (VMNIC4) for OSEELAN.

You can find below the OSEELAN network diagram for each deployment of
OpenScape Enterprise Express V9:
Deployment A:
The Network switch is only required if direct access to the OSEELAN is
needed (e.g. SESAP).
Deployments B and C:
The cabling displayed below offers redundancy for hardware failure scenarios
at multiple levels (network ports, cabling, L2 switch).
A31003-S5190-J100-20-7631, 07/2017
HW.fm
Deployment D:
Same logic as for Deployments B and C.
3. Finally, connect the power cord to the server and to the socket-outlet.
A31003-S5190-J100-20-7631, 07/2017
HW.fm
RAID Configuration
2.4 RAID Configuration

1. During the boot process, when prompted hit the F10 key to enter Lifecycle
Controller.
2. Go to System Setup -> Advanced hardware configuration
3. Select Device Settings -> Integrated RAID controller 1
4. Under Configuration Management select Clear configuration
5. Confirm checkbox and select Yes and then OK
6. Select Back and then Configuration Management
7. Select Create Virtual Disk
8. For RAID level select RAID1
9. Then select Physical Disks
10. Select the first 2 available disks and click Next.
11. Select Apply Changes and then OK
12. Set virtual disk name OSEELINUX
13. Select Create Virtual Disks
15. Select Physical Disks
16. Select the last 2 available disks and Apply Changes
17. Select OK
18. .Set virtual disk name OSEEWIN
19. Select Create Virtual Disks
21. When message for absence of configurable physical disks appears select
Back
22. Select Finish -> Finish -> Finish (3 times) to complete RAID configuration
23. Proceed to Section 2.5, “Modifying the Server UEFI Settings”.
2.5 Modifying the Server UEFI Settings

24. In the System Setup Main Menu click on System BIOS.
A31003-S5190-J100-20-7631, 07/2017
HW.fm
iDRAC Configuration
25. The system should come with the default UEFI settings; however to make
sure that this is the case it is highly recommended that the defaults are
loaded.
In the System Configuration and Boot Management screen, click on the
Default button and then on the pop-up window click Yes. The system default
settings should now be set.
26. From the System BIOS Settings list select Miscellaneous Settings.
27. Set the System Time and System Date.
28. Click Back.
29. From the System BIOS Settings list select Boot Settings.
30. Click on BIOS Boot Settings and then on Boot Sequence.

Verify that the first item in the list is the Hard drive C:
31. Click OK and then select the Hard-Disk Drive Sequence.

Verify that the first item in the list is Internal SD:IDSDM.
32. Click OK.
33. Click Finish and then Yes.
34. Proceed to Section 2.6, “iDRAC Configuration”.
2.6 iDRAC Configuration

35. From the System Setup Main Menu select iDRAC Settings.
36. Click on Network.
37. Verify that the Enable NIC option is Enabled.
38. Scroll down to the IPV4 SETTINGS category.

Verify that the Enable IPV4 option is Enabled and set the following:
• Static IP Address
• Static Gateway
• Static Subnet Mask
39. Click Back and scroll down to User Configuration.
40. Verify that Enable User is Enabled and set the following:
• Username: USERID
• LAN User Privilege: Administrator
A31003-S5190-J100-20-7631, 07/2017
HW.fm
iDRAC and Remote Console Access
• Serial Port User Privilege: Administrator
• Password: PASSW0RD
Note: PASSW0RD uses the number zero and not the letter O.
41. Click Back and then Finish.
42. Click Yes on the pop-up window.
43. On the upper right corner click Exit and then confirm by clicking Yes.
2.7 iDRAC and Remote Console Access

Requirement
Java 8 installed
Procedure
1. Open a web browser window and in the URL field type in 10.5.33.70
2. Log in using the following credentials:

Username: USERID
Password: PASSW0RD
Note: PASSW0RD uses the number zero and not the letter O.
3. On the Virtual Console Preview area click Launch.
4. The browser will display a window asking to open viewer.jnlp
5. Select Java(TM) Web Start Launcher to open it and click OK.
6. The console should bring up the screen that is active on the server:
2.8 Boot of ESXi Hypervisor

After the UEFI initializes and the relevant devices are started, as part of the
normal boot sequence, the system shall start to boot the Hypervisor. It shall load
the Hypervisor software and boot to the Main Login window.
The system is ready for the OpenScape Enterprise Express V9 Solution to be

installed and deployed.
A31003-S5190-J100-20-7631, 07/2017
vm_env_req.fm
VM Environment and Requirements
OSEE VM Requirements
3 VM Environment and Requirements
3.1 OSEE VM Requirements

For information regarding the Virtual Machine requirements, and Template for
Virtualization Overhead requirements, please refer to OpenScape Solution Set
V9, Virtual Machine Resourcing and Configuration Guide.
For additional information regarding the Virtual Machine requirements of

deployments for 500, 1000, 2000, 3000, 4000 and 5000 users, please refer to
OpenScape Enterprise Express V9, Design and Planning Manual, Planning
Guide.
3.2 OSEE-AI VM requirements
Note: There is no need to allocate additional resources for the OSEE-AI during
the hardware planning phase.
OSEE-AI
vCPU 1
vCPU Freq. 2.4 GHz
vRAM 2 GB
vDisk (no req’d) 1

vDisk Size 80 GB
vDisk Format THIN
A31003-S5190-J100-20-7631, 07/2017
vm_env_req.fm
OSEE-AI VM requirements
During staging, the server is operating at low load and ESXi is able to share the
resources needed for the OSEE-AI VM. vCPU and vRAM overcommitment is
acceptable at this state.
IMPORTANT: After the staging is over, the OSEE-AI VM should be removed from
the ESXi!
Note: Note: OSEE-AI does not support backwards compatibility for OSEE
products. For each OSEE release, the latest released OSEE-AI in the same
production line (i.e. V9R2) should be used.
A31003-S5190-J100-20-7631, 07/2017
vm_env_req.fm
OSEE-AI VM requirements
A31003-S5190-J100-20-7631, 07/2017
VM.fm
VMware ESXi Configuration
Configuring VMware ESXi
4 VMware ESXi Configuration

For Software Only installations proceed to Section 4.7, “Configuring VMware
ESXi (Deployment E)”
4.1 Configuring VMware ESXi
Note: In case where multiple hosts are deployed, follow the steps below for each
host.
1. Once VMWare ESXi boots up press F2 to “Customize System”.
2. When prompted type in the following credentials:

– Login Name: root
– Password: <Password set by the user during installation>
and press Enter to log in.
3. On the “System Customization” screen select Configure Password and

press ENTER.
Type in the old password and the new password (according to local company
policies) twice for confirmation, and press ENTER.
4. On the “System Customization” screen select Configure Management

Network and press ENTER.
a) Select Network Adapters and press ENTER.
b) Verify that vmnic0 is the selected adapter and is marked with an X.
c) Press ENTER.
5. On the “Configure Management Network” screen select IPv4 Configuration

and press ENTER.
a) Mark the option Set static IP address and network configuration by

pressing Space and set the following based on customer network
configuration:
– IPv4 Address
– Subnet Mask
– Default Gateway
b) Press ENTER.
A31003-S5190-J100-20-7631, 07/2017
VM.fm
Downloading vSphere Client
6. Back on the “Configure Management Network” screen select DNS

Configuration and press ENTER.
a) In the Hostname field set a distinctive hostname for the ESXi host.
The hostname should be in Fully Qualified Domain Name (FQDN)
(e.g. host1.esxi.net)
b) Press ENTER.
7. On the “Configure Management Network” screen press Esc to exit.
8. Press Y to apply changes and restart management network.
9. On the “System Customization” screen press Esc to exit.
4.2 Downloading vSphere Client

1. Open Internet Explorer and navigate to the IP address of the ESXi console.
2. Ignore the message regarding the security certificate and click Continue to
this website.
3. On the next window click Download vSphere Client.

Click Save
The file download should commence.
4. After the download is complete click Run and wait for the package to be
extracted.
Wait for the vSphere Installation wizard to start. Select your language and
click OK.
5. On the next screen click Next.
6. Select “I accept the terms in the license agreement” and click Next.
7. Click Next.
8. Click Install and wait for the installation to complete.
9. On the next window click Finish.
4.3 Starting vSphere Client

1. Find the VMware vSphere Client icon on your desktop and double click it.
2. Enter the following:
A31003-S5190-J100-20-7631, 07/2017
VM.fm
VMware ESXi network configuration
– IP address of the ESXi server you want to manage

(the IP address shown on the console in the login page of the ESXi
server)
– Username: root
– Password: <set during ESXi installation>
Click Login.
3. On the security warning select the checkbox “Install this certificate and…”
and click Ignore.
Wait until the connection is established.
4. You have successfully logged onto the ESXi host via vSphere Client.
5. Proceed to the next section without logging out.
4.4 VMware ESXi network configuration
Note: In case where multiple hosts are deployed, follow steps 1 - 7 for each host.
Make sure that the following are set:
1. Select the ESXi server and click on the Configuration tab. Under the
“Hardware” list select Networking and then click on Properties... next to
Standard Switch: vSwitch0
2. On the vSwitch0 Properties window under the Ports tab select vSwitch and
click on Edit...
3. On the new window that pops up on the General tab and set:
– Number of Ports: 120
– MTU:1500
4. Navigate to the Security tab and set:
– Promiscuous Mode: Reject
– MAC Address Changes: Accept
– Forged Transmits: Accept
5. Navigate to the Traffic Shaping tab and set:

Status: Disabled
6. Navigate to the NIC Teaming tab and set:
– Load Balancing: Route based on the originating virtual port ID
A31003-S5190-J100-20-7631, 07/2017
VM.fm
Enable Remote SSH and ESXi Shell
– Network Failover Detection: Link status only
– Notify Switches: Yes
– Fallback: Yes
7. Click OK and on the next window Close.
4.5 Enable Remote SSH and ESXi Shell

1. Select the ESXi server from the column located on the left side of the screen.
2. Click on the Configuration tab.
3. From the “Software” list select Security Profile.
4. In the Services section click Properties.
5. Select SSH and then click on the Options... button.
6. Make sure that the option Start and stop manually is selected, click on the
Start button and then click OK.
7. Repeat steps 5 and 6 for ESXi shell.
8. Make sure that ESXi shell and SSH are running and then click OK.
4.6 Execution of the OSEEreconfig.sh script
Note: In case where multiple hosts are deployed, follow steps 1 - 7 for each
host.
1. From a Windows machine use WinSCP to login as root to the ESXi host
using the IP address configured in Section 4.1, “Configuring VMware ESXi”
for the management interface. Transfer OSEEreconfig.sh that is generated
by WebCDC (vApp folder of the downloaded zip) to the /tmp directory.
Note: In WinSCP change the File Transfer Protocol to SCP.
2. After OSEEreconfig.sh is transferred to the ESXi host /tmp directory use

SSH or Putty to login as root to the ESXi service console and execute the
OSEEreconfig.sh script with the following command:
/tmp # sh OSEEreconfig.sh
A31003-S5190-J100-20-7631, 07/2017
VM.fm
Configuring VMware ESXi (Deployment E)
This step will configure DNS and NTP servers, create the OSEE datastores
on the RAID arrays, and configure the OSEE-specific vSwitch network
settings.
Note: If a drive contains existing partitions and does not already contain an
OSEE datastore, the user will be prompted to overwrite the contents of the
drive.
3. After the execution of the script the host is going to reboot automatically.
Please wait approximately 5 minutes.
4. Open vSphere Client and logon to the IP address of the VMware ESXi
server.
5. On the main window under the Configuration tab on the “Hardware” list
select Storage.
6. Make sure that the datastores are named OSEEOSV and OSEEWIN, and
they are of VMFS5 type.
Note: The names for the vSwitch0 and vSwitch1 should remain constant
and should always be called OSEEWAN and OSEELAN respectively. This
will be needed when the OVA is deployed onto the system to have a one to
one match between the OVA network adapter and the server’s vSwitch.
4.7 Configuring VMware ESXi (Deployment E)

1. Download and install vSphere Client.
https://www.vmware.com/go/download-vsphere
2. Log in to the ESXi host via vSphere Client.
Note: In case where multiple hosts are deployed, follow the steps below for
each host.
3. Switch to the Configuration tab.
4. Under the Hardware section click on Storage.
A31003-S5190-J100-20-7631, 07/2017
VM.fm
a) Set up the Windows datastore. Name it OSEEWIN or give it a name of

your choice.
b) Set up the OSV datastore. Name it OSEEOSV or give it a name of your

choice.
Note: Make sure that the datastores’ type is VMFS5.
5. Under the Hardware section click on Networking and set up the following
vSwitches:
OSEEWAN
• Select 2 of the available vmnic.
• Set the Network Label to OSEEWAN.

OSEELAN
• Select 1 of the available vmnic.
• Change the Network Label to OSEELAN.
A31003-S5190-J100-20-7631, 07/2017
VM.fm
A31003-S5190-J100-20-7631, 07/2017
OVA2.fm
OVA deployment
Preparation steps
5 OVA deployment
The procedure described in this chapter applies to Deployments A, B, C and D.
In case you are working on Deployment E, refer to Chapter 6, “OVA deployment
on a Resource Pool”.
5.1 Preparation steps

WebCDC generated configuration files can be downloaded directly from the user
interface of the tool and saved to the user’s preferred location.
Unzip CDC_<project_name>.zip and copy:
Deployment A and B
File From (zip) To
Root directory of the OSEEOSV datastore
vApp.iso vApp folder of the ESXi host where OSV will be
installed.
CDC_SbcThig1_conf.iso OS_SBC folder Root directory of the OSEEOSV datastore
of the ESXi where SBC THIG will be
installed.
Deployments C and D
File From (zip) To
of the ESXi host where OSV node 1 will be
installed.
vApp.iso vApp folder
of the ESXi host where OSV node 2 will be
installed.
of the ESXi where SBC THIG 1 will be
installed.
of the ESXi where SBC THIG 2 will be
installed.
A31003-S5190-J100-20-7631, 07/2017
OVA2.fm
OVA deployment
Deploy the OSEE-AI OVA
5.2 Deploy the OSEE-AI OVA

1. On the upper left corner of the vSphere Client click on File and select
Deploy OVF Template...
2. Click Browse and select the OSEE-AI OVA from the locally or network
attached hard disk drive on the computer running vSphere Client and click
Open.
3. Click Next on "OVF Template Details" step.
4. Click Next on "Verify OVF Template Details" step.
5. Set a name of your choice and click Next.
6. Choose the OSEEOSV datastore and click Next.
7. Select Thin Provision and click Next.
8. Map the source networks to your destination networks:
Source Network Destination Network

OSEELAN OSEELAN
OSEEWAN OSEEWAN
Click Next when done.
9. Click Finish and wait until the OVA deployment status completes and then
click Close.
Note: Wait time can be a few minutes.
10. Right click on the OSEE-AI VM and select Open console.
11. Click on the Power on button.
12. When prompted to log in, use the following credentials:

Username: root
Pasword: vagrant
13. Follow the instructions displayed on your screen to configure the OSEE-AI
WAN IP address.
Note: After setting up for the first time, every time you open the console and
log in, you will be given the option to check the WAN IP and change it if
needed.
A31003-S5190-J100-20-7631, 07/2017
OVA2.fm
OVA deployment
Deploy the OSEE V9 OVAs with AI
14. Copy the following files to the oseeai-shared directory using the WAN IP
address configured in step 13 (e.g. \\10.5.32.21\oseeai-shared):
Use the following credentials:
Username: vagrant
Password: vagrant
• OSEE_SI_Staging_WIN1.zip
• CDC_<project_name>.zip generated by WebCDC
• Phone Software (*.img files) in the oseeai-shared\SW_OpenStage

folder
• License files in the oseeai-shared\licenses folder
15. Open CDC_<project_name>.zip and go to the CDC_Information folder.
16. Extract osee-parameters.xml to the oseeai-shared directory.
17. Edit osee-parameters.xml and fill in the missing values of the parameters.
Note: Parameters vmHost, vmUser and vmPwd are required in order to

successfully deploy the OVAs using OSEE-AI. If left empty the process will
fail.
18. Return to the open console window and execute the prepare_osee.sh script:
#cd ~vagrant/osee-ai
#./prepare_osee.sh
5.3 Deploy the OSEE V9 OVAs with AI

1. Copy all OVA files to \oseeai-shared\ovf directory using the OSEE-AI WAN
IP address.
Note: Use the following credentials:

Username: vagrant and password: vagrant
3. Execute the deploy_osee.sh script:

#./deploy_osee.sh
4. Select option 1 (Deploy OVA to ESXi).
A31003-S5190-J100-20-7631, 07/2017
OVA2.fm
OVA deployment
Configure the SBC-THIG VMs
5. Answer Y when asked to deploy the OVAs.
5.4 Configure the SBC-THIG VMs

1. Right click on the SBC-THIG VM and select Edit settings...
2. Click on CD/DVD drive 1, select Datastore ISO file and then click on the
Browse button. Navigate to the root directory of the OSEEOSV datastore
and select the CDC_SbcThig1_conf.iso
Note: If a second SBC is deployed for redundancy, select the

CDC_SbcThig2_conf.iso for the second node.
3. Check the Connect at power on option and set Virtual Device Node to IDE
(0:0) CD/DVD drive 1 and select OK.
4. Click OK.
5. Right click on the SBC THIG VM and select Open console.
6. Click on the Power on button and wait for OpenSUSE to boot.
7. The OSEE deployment script is executed automatically and the server

restarts. Wait for the server to restart and then close the console.
8. In case you are deploying a second SBC-THIG then follow the procedure for
the second node.
Note: Depending on the configuration, the second SBC-THIG will reboot one
additional time. To setup the redundancy with the first SBC-THIG no
additional steps are needed.
5.4.1 Apply SBC-THIG license

1. Log in to OpenScape SBC THIG Management Portal.
2. Navigate to Network/Net Services > DNS and mark the checkbox to enable
the DNS server.
3. Click OK and then Apply Changes.
4. Then navigate to System > License and under General select Refresh to
calculate ALI.
5. Using the calculated ALI generate the needed license file.
A31003-S5190-J100-20-7631, 07/2017
OVA2.fm
OVA deployment
Configure the OSV VMs
6. Back in the OpenScape SBC THIG Management Portal go to

System > License.
7. Under License Information, click on Browse and select the generated

license file. Click Upload and then OK on the pop-up windows.
8. Wait until the upload process is over and make sure that the following
message is displayed:
The file was processed with no errors. Refresh the window
to see the new values.
9. Refresh the window and then click OK.
10. Navigate to Network/Net Services > DNS and disable the DNS server by
removing the check from the checkbox.
11. Click on OK and then Apply Changes.
5.5 Configure the OSV VMs

1. Right click on osee_v9_osv_n1 VM (osee_v9_osv VM in case of OSV type
Simplex) and select Edit settings...
2. Select Video card from the Hardware list and make sure Auto-detect
settings is enabled.
Browse button. Select the configuration ISO file vApp.iso from the OSV
datastore and click OK.
Note: The vApp.iso is the same for both nodes in case a cluster is deployed.
5. Click OK.
6. At the bottom of the screen, in the “Recent Tasks” area of the vSphere Client,
there will be an entry for “Reconfigure virtual machine.”
Wait for the Status to change to Completed before proceeding.
7. Power on osee_v9_osv_n1 (osee_v9_osv in case of OSV type Simplex).
8. Repeat the procedure for osee_v9_osv_n2 (in case of OSV type Duplex).
9. The procedure will end when the following message is displayed:

Press Alt+F1 for the first login terminal.
A31003-S5190-J100-20-7631, 07/2017
OVA2.fm
OVA deployment
Power on the UC VM
5.6 Power on the UC VM

1. Right click on the osee_v9_uc VM > Power > Power On.
5.7 Setup and Configuration of the Windows VMs
Important: Repeat the procedure described in Section 5.7, “Setup and

Configuration of the Windows VMs” and its subsections for each Windows VM.
5.7.1 Requirements
• Windows Server 2012 R2 x64 English Standard + Hotfixes
• Windows Server 2012 R2 installation media (needed for the installation of

.NET Framework 3.5)
5.7.2 Configure the Windows VMs

1. Right click on the Windows VM and select Edit settings...
2. Select Video card from the Hardware list and make sure Auto-detect
settings is enabled.
3. Click OK.
5.7.3 Windows Server 2012 R2 Installation

1. Right click on the VM and select Edit virtual machine settings.
Browse button. Select the Windows installation media ISO file and click OK.
4. Power on the VM.
5. Start the installation of the operating system, and when prompted select the
Server with a GUI option.
A31003-S5190-J100-20-7631, 07/2017
OVA2.fm
OVA deployment
Setup and Configuration of the Windows VMs
5.7.3.1 Windows Server Administrator Password
Once the installation of Windows is over, set up Asd123!. as the Administrator

password. This step is important for the operation of the automation script.
Note: You may change the password to one that complies with the customer’s
policies AFTER the staging of OpenScape Enterprise Express is over.
Important: If the local Administrator password is changed, all OpenScape

Xpressions Windows services which are using this account to run, must be
updated with the new password.
5.7.3.2 Install .NET Framework 3.5
1. In Server Manager, click Manage and then select Add Roles and Features
to start the Add Roles and Features Wizard.
2. On the Select installation type screen, select Role-based or feature-

based installation.
3. Select the target server.
4. On the Select features screen, check the box next to .Net Framework 3.5
Features.
5. On the Confirm installation selections screen, a warning will be displayed

asking:
Do you need to specify an alternate source path?
Click the Specify an alternate source path link to specify the path to the
\Sources\Sxs folder on the installation media and then click OK.
6. After you have specified the alternate source, click the X next to the warning,
and then click Install.
5.7.3.3 Install VMWare Tools
Install VMWare Tools before proceeding to the next section. This step is
important in order to have available a driver for the network adapter.
A31003-S5190-J100-20-7631, 07/2017
OVA2.fm
OVA deployment
5.7.3.4 Update Windows Server
1. Open the Control Panel and on the upper right corner search for “Update”.
2. Click on Windows Update and then Change settings.
3. Select the option Check for updates only but let me choose whether to
download and install them.
4. Download and install all available updates.
Note: Remember to execute Windows Update several times as not all

updates are downloaded and applied at once.
5.7.3.5 Configuration of Windows pt.1
Windows Server Default input language and System locale:

1. Open the Control Panel and click on Clock, Language and Region.
2. Open the Language section and click on Change input methods.
3. In the next screen click Options and change the input language to US and
click Save.
4. Go back to Clock, Language and Region and click on Region.
5. Change to the Administrative tab and click on Change system locale...
6. Select English (United States) and click OK.
Set your Time Zone:

7. Click on Set the time and date.
8. Under the “Date and Time” tab click on Change time zone...
Select the time zone you have set in WebCDC for the main site and click OK.
9. Under the “Internet Time” tab click on Change settings...

Enter the NTP source IP address that was set in WebCDC.
Click OK.
10. Click OK to exit the “Date and Time” window.
A31003-S5190-J100-20-7631, 07/2017
OVA2.fm
OVA deployment
Configure Network Connections:

1. Open the Control Panel and click on Network and Internet. Then click on
Network and Sharing Center and finally Change adapter settings.
2. Right click on the Ethernet Adapter and select Rename. Rename the adapter
to:
VM Network Connection
Windows VM 1 XPR_VM
Windows VM 2 VM2
3. Configure XPR_VM / VM2:

Right click on the XPR_VM / VM2 adapter and select Properties
a) Uncheck Internet Protocol Version 6 (TCP/IPv6)
b) Select TCP/IPv4 and click Properties:

Select the Use the following IP address option and set the following:
Windows VM 1 Windows VM 2
IP address 10.82.53.241 10.82.53.249
Subnet mask 255.255.255.0 255.255.255.0
Default gateway 10.82.53.227 10.82.53.227
Select the Use the following DNS server addresses option and set the
following:
Preferred DNS Server 10.82.53.231 10.82.53.231
Click Advanced… and under the DNS tab select Append these DNS
suffixes (in order) and add the following DNS suffixes:
xpr.<domain from WebCDC> <domain from WebCDC>
<domain from WebCDC>
Only for Windows VM1, enter xpr.<domain from WebCDC> in the DNS
suffix for this connection field.
c) Click OK to close the opened windows. After closing the XPR_VM

Properties / VM2 Properties window wait for a few seconds and when
asked if you want to automatically connect to devices like printers and
TVs select No.
A31003-S5190-J100-20-7631, 07/2017
OVA2.fm
OVA deployment
Note: In case Windows need to join a domain, the DNS IP of the aforementioned
domain needs to be added to the Network adapter card settings.
1. Open the built in File Explorer.
2. In the address bar type \\10.82.53.250
3. Open the oseeai-shared folder and when prompted enter the following
network credentials:
• Username: vagrant
• Password: vagrant
Important: Do NOT mark the “Remember my credentials” checkbox.
Click OK.
4. Copy the following files:
OSEE_SI_Staging_WIN1.zip OSEE_SI_Staging_WIN2.zip
OSEEWinCnf.ps1 OSEEWinCnf.ps1
to the C: drive of the virtual machine.
5. Run Windows Powershell (not x86) as Administrator and type in the

following:
cd C:\
.\OSEEWinCnf.ps1
6. After the script is executed, press Y when prompted to restart the computer.
A31003-S5190-J100-20-7631, 07/2017
OVA2.fm
OVA deployment
5.7.4 Silent Installation Steps

1. Using the console of each Windows VM extract the contents of:
zip file VM
OSEE_SI_Staging_WIN1 Windows VM 1
to the C:\ drive.
2. IMPORTANT: Take a snapshot of each VM.
3. On Windows VM 1 run Command Prompt as Administrator.
a) Type the following commands:

cd C:\OSEE_SI_Staging
SI_MASTER_WIN1.bat
Note: If you do NOT want OpenScape Contact Center to be installed use

the -noOSCC flag (e.g. SI_MASTER_WIN1.bat -noOSCC).
IMPORTANT: Do NOT proceed with the installation on Windows VM 2
before Windows VM 1 installation is over.
b) Windows VM 1 will reboot several times and log back in automatically.

IMPORTANT: Do NOT perform any actions in the meantime.
After the last reboot, a command prompt window will be opened and
OscceMainService will start automatically.
c) A countdown timer will start. Please wait for 5 minutes until

OscceMainService has started successfully. The command prompt
window will close automatically after the countdown is over.
d) Proceed to the next step.
4. On Windows VM 2 run Command Prompt as Administrator and type the

following commands:
SI_MASTER_WIN2.bat
Note: Press Enter when prompted to “Press any key to continue...”
5. Make sure all hotfixes are installed:
A31003-S5190-J100-20-7631, 07/2017
OVA2.fm
OVA deployment
Under the OSEE_SI_STAGING/HOTFIXES/ directory follow the release

notes of each hotfix for further information and steps to be taken.
Note: In case a hotfix / patch is accompanied by a README file (i.e.

README.txt), please consult it for specific installation instructions.
Note: Before proceeding with Xpressions hotfixes' installation, all

Xpressions services should be stopped.
In Windows VM 1 open Server Manager and click on Tools > Services.
To stop the Xpressions services :
- Select XPR Administrator (mrs) and right click > Stop. Wait until all
services (except XPR License Server) are stopped.
- Select XPR License Server(licsvc) and right click > Stop
After those hotfixes are installed, a reboot of Windows VM 1 should be
also performed.
A31003-S5190-J100-20-7631, 07/2017
OVA2.fm
OVA deployment
OpenScape Contact Center Licensing
5.8 OpenScape Contact Center Licensing

1. If the MAC address was not pre-defined so that the license files could be
generated earlier then use the following to obtain the MAC address of the
virtual machine for OpenScape Contact Center license.
Note: This can only be done if the Windows Server virtual machine is
powered off.
• Right Click on the OSEE_Windows Virtual Machine you would like to

obtain the MAC address, and select “Edit Settings…”
• Select the Network adapter – the MAC address is listed on the right.
Note: If the Virtual Machine was turned off, the user has the ability to
manually change the MAC address of the VM by selecting the Manual
radiobox and entering a MAC address in the textbox.
2. Information needed to obtain an ALID (Advanced Locking ID) License for

OpenScape Voice, OpenScape UC Application, DLS, CMP, and OpenScape
Xpressions. This information will need to be gathered from the WebCDC
configuration information.
Note: This information can also be found after the installation of the OSV
Integrated Simplex by going to the CMP and viewing the License details on
the Maintenance tab under Licensing and Locking ID. Exception is the XPR
that does not provide an ALI on the Windows box.
A31003-S5190-J100-20-7631, 07/2017
OVA2.fm
OVA deployment
You will need the following information from the VM to request an ALID
license:
– Host Name
Note: WebCDC assigns "mgmt" as default host name for the SLES VM
and uses it as it is for license key generation.
– Host IP Address
– Gateway Address
– Primary DNS IP Address
Note: This is the OSV IP Address that will be used by all the OSEE
applications and not the DNS Server information in the WebCDC, as that
is the DNS forwarder address.
– Time Zone
A31003-S5190-J100-20-7631, 07/2017
OVA.fm
OVA deployment on a Resource Pool
Preparation steps
6 OVA deployment on a Resource Pool

The procedure described in this chapter applies only to Deployment E. In case
you are working on Deployments A, B, C or D, refer to Chapter 5, “OVA
deployment”.
6.1 Preparation steps

WebCDC generated configuration files can be downloaded directly from the user
interface of the tool and saved to the user’s preferred location.
Unzip CDC_<project_name>.zip and copy:
Deployment E
File From (zip) To
Root directory of the OSEEOSV datastore of
the ESXi host where OSV node 1 will be
installed.
vApp.iso vApp folder
Root directory of the OSEEOSV datastore of
the ESXi host where OSV node 2 will be
installed.
CDC_SbcThig1_conf.iso OS_SBC folder Root directory of the OSEEOSV datastore of
the ESXi where SBC THIG 1 will be
installed.
CDC_SbcThig2_conf.iso OS_SBC folder Root directory of the OSEEOSV datastore of
the ESXi where SBC THIG 2 will be
installed.
6.1.1 OSEE Designated networks

You may use your own naming scheme for the OSEE designated networks but
for the purposes of this chapter the following names will be used:
• OSEELAN
• OSEEWAN
A31003-S5190-J100-20-7631, 07/2017
OVA.fm
Deploy the OSEE-AI OVA
6.2 Deploy the OSEE-AI OVA

2. Click Browse and select the OSEE-AI OVA from the locally or network
Open.
5. Set a name of your choice and click Next.
6. Choose the datastore that was created for OSV and click Next.
7. Select Thin Provisioning and click Next.

OSEELAN OSEELAN
OSEEWAN OSEEWAN
click Close.
11. Click on the Power on button.
12. When prompted to log in, use the following credentials:

Username: root
Pasword: vagrant
13. Follow the instructions displayed on your screen to configure the OSEE-AI
WAN IP address.
Note: After setting up for the first time, every time you open the console and
log in, you will be given the option to check the WAN IP and change it if
needed.
14. Copy the following files to the oseeai-shared directory using the WAN IP
address configured in step 13 (e.g. \\10.5.32.21\oseeai-shared):
A31003-S5190-J100-20-7631, 07/2017
OVA.fm
Deploy the SBC-THIG OVA

Username: vagrant
password: vagrant
• CDC_<project_name>.zip generated by WebCDC
• OpenStage *.img files in the oseeai-shared\SW_OpenStage folder
• License files in the oseeai-shared\licenses folder
15. Open CDC_<project_name>.zip and go to the CDC_Information folder.
16. Extract osee-parameters.xml to the OSEE-AI directory.
17. Edit osee-parameters.xml and fill in the missing values of the parameters.
Note: Parameters vmHost, vmUser and vmPwd are optional. They are only
required if the “backup and revert virtual machines” functionality of OSEE-AI
is used.
18. Return to the open console window (step 10) and execute the
prepare_osee.sh script:
#./prepare_osee.sh
6.3 Deploy the SBC-THIG OVA

2. Click Browse and select the SBC THIG OVA from the locally or network
Open.
5. Set the name to osee_v9_sbc_thig and click Next.
Note: If a second SBC is deployed for redundancy set the name of the
second node to osee_v9_sbc_thig_n2.
A31003-S5190-J100-20-7631, 07/2017
OVA.fm
Deploy the SBC-THIG OVA
7. Select Thick Provisioning Lazy Zeroed.
Note: Do NOT select Thin Provisioning.
Click Next.

OSEELAN OSEELAN
OSEEWAN OSEEWAN
click Close.
10. Right click on the SBC THIG VM and select Edit settings...
Browse button. Navigate to the root directory of the OSEEOSV datastore
and select the CDC_SbcThig1_conf.iso
Note: If a second SBC is deployed for redundancy, select the

CDC_SbcThig2_conf.iso for the second node.
13. Click OK.
14. Right click on the SBC THIG VM and select Open console.
15. Click on the Power on button and wait for OpenSUSE to boot.
16. The OSEE deployment script is executed automatically and the server
restarts. Do not login after the restart procedure is over. You may close the
console.
17. In case you are deploying a second SBC-THIG then follow the procedure for
the second node.
Note: Depending on the configuration, the second SBC-THIG will reboot one
additional time. To setup the redundancy with the first SBC-THIG no
additional steps are needed.
A31003-S5190-J100-20-7631, 07/2017
OVA.fm
Deploy the OSV OVA
6.3.1 Apply SBC-THIG license

2. Navigate to Network/Net Services > DNS and mark the checkbox to enable
the DNS server.
3. Click OK and then Apply Changes.
4. Then navigate to System > License and under General select Refresh to
calculate ALI.
5. Using the calculated ALI generate the needed license file.
6. Back in the OpenScape SBC THIG Management Portal go to

System > License.
7. Under License Information, click on Browse and select the generated

license file. Click Upload and then OK on the pop-up windows.
8. Wait until the upload process is over and make sure that the following
message is displayed:
The file was processed with no errors. Refresh the window
to see the new values.
9. Refresh the window and then click OK.
10. Navigate to Network/Net Services > DNS and disable the DNS server by
removing the check from the checkbox.
Click on OK and then Apply Changes.
6.4 Deploy the OSV OVA
Important: In case a cluster is deployed the steps on this section should be

repeated for each node.
1. On the upper left corner of vSphere Client, click File and select Deploy OVF
Template…
2. Click Browse.
Select the OSV OVA file (osee_v9_osv.ova) and click Open.
Note: In case a cluster is deployed the following OVA files should be used:
- osee_v9_osv_n1.ova for Node 1
- osee_v9_osv_n2.ova for Node 2
A31003-S5190-J100-20-7631, 07/2017
OVA.fm
Deploy the OSV OVA
5. Set the name to "osee_v9_osv" and click Next.
Note: In case a cluster is deployed the following names should be used:

- osee_v9_osv_n1 for Node 1
- osee_v9_osv_n2 for Node 2
Important: It is important to set the name(s) mentioned above or the

execution of OSEE-AI will fail.
6. Choose the datastore that was created for the OSV (e.g. OSEEOSV).
Click Next.
7. Select Thick Provisioning Lazy Zeroed.
Note: DO NOT choose Thin Provisioning.
Click Next.
8. Map the source network to your destination network (the name of the switch
allocated to OSEE usage). Click on Destination Network and select the
destination network OSEELAN (Ethernet Interface) that was created in
Section 4.7, “Configuring VMware ESXi (Deployment E)”.
9. Click Next on "Network Mapping" step.
10. Click Finish on "Ready to Complete" step.
11. Wait until all processes complete.

Once completed click Close.
12. Click on the VM just created and select Edit settings...
13. Click on Video card, in the “Displays and video memory” section and make
sure Auto-detect settings is enabled.
Browse button. Select the configuration ISO file vApp.iso from the OSV
datastore and click OK.
Note: The vApp.iso is the same for both nodes in case a cluster is deployed.
16. At the bottom of the screen, in the in the “Recent Tasks” area of the vSphere
Client, there will be an entry for “Reconfigure virtual machine.”
A31003-S5190-J100-20-7631, 07/2017
OVA.fm
Deploy the UC OVA
Wait for the Status to change to Completed before proceeding.
17. Power on the virtual machine (osee_v9_osv).
Note: In case a cluster is deployed, power on both VMs (osee_v9_osv_n1

and osee_v9_osv_n2).
18. The procedure will end when the following message is displayed:
Press Alt+F1 for the first login terminal.
6.5 Deploy the UC OVA

2. Click Browse and select the UC OVA from the locally or network attached
hard disk drive on the computer running vSphere Client and click Open.
5. Set the name to osee_v9_uc and click Next.
7. Select Thick Provisioning Zeroed.
Note: DO NOT choose Thin Provisioning.
Click Next.
allocated to OSEE usage). Click on Destination Network and select the
9. Click Next on "Network Mapping" step.
10. Click Finish on "Ready to Complete" step.
11. Wait until all processes complete.

Once completed click Close.
12. Click on the osee_v9_uc virtual machine and select Edit virtual machine
settings.
13. Click on Video card, in the “Displays and video memory” section and make
sure Auto-detect settings is enabled.
A31003-S5190-J100-20-7631, 07/2017
OVA.fm
14. Right click on the osee_v9_uc VM and select Power > Power on.
6.6 Setup and Configuration of the Windows VMs
Important: Repeat the procedure described in Section 6.6, “Setup and

Configuration of the Windows VMs” and its subsections for each Windows VM.
6.6.1 Requirements
• Windows OVA template
Note: Can be found under

\\osee-ai_wan_ip_address\oseeai-shared\vApp\OVA
• Windows Server 2012 R2 x64 English Standard + Hotfixes
• Windows Server 2012 R2 installation media (needed for the installation of

.NET Framework 3.5)
6.6.2 Deploy the Windows OVA template

1. On the upper left corner of the vSphere Client click on File and select Deploy
OVF Template…
2. Click Browse and select the Windows OVA:
VM OVA file Components

Windows VM 1 osee_v9_win_1.ova Concierge, OSCC, XPR
Windows VM 2 osee_v9_win_2.ova DLS, OSTM
from the locally or network attached hard disk drive on the computer running
vSphere Client and click Open.
5. Verify that the name is:
VM Name
Windows VM 1 osee_v9_win_1
Windows VM 2 osee_v9_win_2
and click Next.
A31003-S5190-J100-20-7631, 07/2017
OVA.fm
6. Choose the datastore that was created for the Windows VM (e.g. OSEEWIN).
Click Next.
7. Select Thick Provision Lazy Zeroed.
Note: DO NOT choose Thin Provision.
Click Next.
allocated to OSEE usage). Click on the Destination Network and select the
9. Click Finish when done on "Ready to Complete" step.
10. Wait until the OVA deployment status completes and then click Close.
Note: Wait time can be a few seconds.
6.6.3 Windows Server 2012 R2 Installation

1. Right click on the VM and select Edit virtual machine settings.
Browse button. Select the Windows installation media ISO file and click OK.
4. Power on the VM.
5. Start the installation of the operating system, and when prompted select the
Server with a GUI option.
6.6.3.1 Windows Server Administrator Password
Once the installation of Windows is over, set up Asd123!. as the Administrator

password. This step is important for the operation of the automation script.
Note: You may change the password to one that complies with the customer’s
policies AFTER the staging of OpenScape Enterprise Express is over.
A31003-S5190-J100-20-7631, 07/2017
OVA.fm
6.6.3.2 Install .NET Framework 3.5
1. In Server Manager, click Manage and then select Add Roles and Features
to start the Add Roles and Features Wizard.
2. On the Select installation type screen, select Role-based or feature-

based installation.
3. Select the target server.
4. On the Select features screen, check the box next to .Net Framework 3.5
Features.
5. On the Confirm installation selections screen, a warning will be displayed

asking:
Do you need to specify an alternate source path?
Click the Specify an alternate source path link to specify the path to the
\Sources\Sxs folder on the installation media and then click OK.
6. After you have specified the alternate source, click the X next to the warning,
and then click Install.
6.6.3.3 Install VMWare Tools
Install VMWare Tools before proceeding to the next section. This step is
important in order to have available a driver for the network adapter.
6.6.3.4 Update Windows Server
1. Open the Control Panel and on the upper right corner search for “Update”.
2. Click on Windows Update and then Change settings.
3. Select the option Check for updates only but let me choose whether to
download and install them.
4. Download and install all available updates.
Note: Remember to execute Windows Update several times as not all

updates are downloaded and applied at once.
A31003-S5190-J100-20-7631, 07/2017
OVA.fm
Windows Server Default input language and System locale:

1. Open the Control Panel and click on Clock, Language and Region.
2. Open the Language section and click on Change input methods.
3. In the next screen click Options and change the input language to US and
click Save.
4. Go back to Clock, Language and Region and click on Region.
5. Change to the Administrative tab and click on Change system locale...
6. Select English (United States) and click OK.
Set your Time Zone:

7. Click on Set the time and date.
8. Under the “Date and Time” tab click on Change time zone...
Select the time zone you have set in WebCDC for the main site and click OK..
9. Under the “Internet Time” tab click on Change settings...

Enter the NTP source IP address that was set in WebCDC.
Click OK.
10. Click OK to exit the “Date and Time” window.
Configure Network Connections:

1. Open the Control Panel and click on Network and Internet. Then click on
Network and Sharing Center and finally Change adapter settings.
2. Right click on the Ethernet Adapter and select Rename. Rename the adapter
to:
VM Network Connection
Windows VM 1 XPR_VM
Windows VM 2 VM2
3. Configure XPR_VM / VM2:

Right click on the XPR_VM / VM2 adapter and select Properties
a) Uncheck Internet Protocol Version 6 (TCP/IPv6)
b) Select TCP/IPv4 and click Properties:

Select the Use the following IP address option and set the following:
A31003-S5190-J100-20-7631, 07/2017
OVA.fm
IP address 10.82.53.241 10.82.53.249
Subnet mask 255.255.255.0 255.255.255.0
Default gateway 10.82.53.227 10.82.53.227
Select the Use the following DNS server addresses option and set the
following:
Preferred DNS Server 10.82.53.231 10.82.53.231
Click Advanced… and under the DNS tab select Append these DNS
suffixes (in order) and add the following DNS suffixes:
xpr.<domain from WebCDC> <domain from WebCDC>
<domain from WebCDC>
Only for Windows VM1, enter xpr.<domain from WebCDC> in the DNS
suffix for this connection field.
c) Click OK to close the opened windows. After closing the XPR_VM

Properties / VM2 Properties window wait for a few seconds and when
asked if you want to automatically connect to devices like printers and
TVs select No.
Note: In case Windows need to join a domain, the DNS IP of the aforementioned
domain needs to be added to the Network adapter card settings.
1. Open the built in File Explorer.
2. In the address bar type \\10.82.53.250
3. Open the oseeai-shared folder and when prompted enter the following
network credentials:
• Username: vagrant
• Password: vagrant
IMPORTANT: Do NOT mark the “Remember my credentials” checkbox.
A31003-S5190-J100-20-7631, 07/2017
OVA.fm
Click OK.
4. Copy the following files:
OSEE_SI_Staging_WIN1.zip OSEE_SI_Staging_WIN2.zip
OSEEWinCnf.ps1 OSEEWinCnf.ps1
to the C: drive of the virtual machine.
5. Run Windows Powershell (not x86) as Administrator and type in the

following:
cd C:\
.\OSEEWinCnf.ps1
6. After the script is executed, press Y when prompted to restart the computer.
6.6.4 Silent Installation Steps

1. Using the console of each Windows VM extract the contents of:
zip file VM
to the C:\ drive.
2. Take a snapshot of each VM.
3. On Windows VM 1 run Command Prompt as Administrator.
a) Type the following commands:

SI_MASTER_WIN1.bat
Note: If you do NOT want OpenScape Contact Center to be installed use

the -noOSCC flag (e.g. SI_MASTER_WIN1.bat -noOSCC).
IMPORTANT: Do NOT proceed with the installation on Windows VM 2
before Windows VM 1 installation is over.
b) Windows VM 1 will reboot several times and log back in automatically.

IMPORTANT: Do NOT perform any actions in the meantime.
After the last reboot, a command prompt window will be opened and
OscceMainService will start automatically.
c) A countdown timer will start. Please wait for 5 minutes until

OscceMainService has started successfully. The command prompt
window will close automatically after the countdown is over.
A31003-S5190-J100-20-7631, 07/2017
OVA.fm
d) Proceed to the next step.
4. On Windows VM 2 run Command Prompt as Administrator and type the

following commands:
SI_MASTER_WIN2.bat
Note: Press Enter when prompted to “Press any key to continue...”
5. Make sure all hotfixes are installed:

Under the OSEE_SI_STAGING/HOTFIXES/ directory follow the release
notes of each hotfix for further information and steps to be taken.
Note: In case a hotfix / patch is accompanied by a README file (i.e.

README.txt), please consult it for specific installation instructions.
Note: Before proceeding with Xpressions hotfixes' installation, all

Xpressions services should be stopped.
In Windows VM 1 open Server Manager and click on Tools > Services.
To stop the Xpressions services :
- Select XPR Administrator (mrs) and right click > Stop. Wait until all
services (except XPR License Server) are stopped.
- Select XPR License Server(licsvc) and right click > Stop
After those hotfixes are installed, a reboot of Windows VM 1 should be
also performed.
A31003-S5190-J100-20-7631, 07/2017
OVA.fm
6.7 OpenScape Contact Center Licensing

If the MAC address was not pre-defined so that the license files could be
generated earlier then use the following to obtain the MAC address of the virtual
machine for OpenScape Contact Center license.
Note: This can only be done if the Windows Server virtual machine is powered
off.
• Right Click on the OSEE_Windows Virtual Machine you would like to obtain
the MAC address, and select “Edit Settings…”
• Select the Network adapter – the MAC address is listed on the right.
Note: If the Virtual Machine was turned off, the user has the ability to
manually change the MAC address of the VM by selecting the Manual
radiobox and entering a MAC address in the textbox.
Note: If the MAC address gets changed after the installation of Windows the
setup of the XPR_VM NIC will be gone.
A31003-S5190-J100-20-7631, 07/2017
OVA.fm
A31003-S5190-J100-20-7631, 07/2017
osee_auto.fm
OSEE Automated Installation
Copy Additional Language Files
7 OSEE Automated Installation
7.1 Copy Additional Language Files

Prerequisites
• The languages that are going to be installed need to be determined in
WebCDC under the field "Default prompt language for the Subscribers" in the
Site tab and under the "Prompt language" field in the Subscriber tab.
• OpenScape Applications software, languages and hotfixes ISO files
Note: The OpenScape Applications software and languages ISO files are in
split zip files and require a file archiver such as WinZip to be extracted.
– Application.* files
Gather all Application.* files that you downloaded from SWS in the same
directory.
Then open Application.zip using the file archiver and extract the ISO
files.
– Application_Languages.* files
Gather all Application_Languages.* files that you downloaded from
SWS in the same directory.
Then open Application_Languages.zip using the file archiver and
extract the ISO files.
Procedure
Transfer the OpenScape Applications software, languages and hotfixes ISO files
to the oscISOs directory under the oseeai-shared directory (oseeai-
shared\oscISOs).
Important: Make sure that all needed files are transfered to the oseeai-shared
directory and its sub-directories.
A31003-S5190-J100-20-7631, 07/2017
osee_auto.fm
Preparation Steps for OSEE Deploy script
7.2 Preparation Steps for OSEE Deploy script

1. Download TWIN server 1.0 (twin-1.0.zip) and transfer it to the oseeai-shared
directory using the WAN IP address configured earlier (e.g.
\\10.5.32.21\oseeai-shared):
username: vagrant
password: vagrant
2. Log in to OSV via console and check that OSV is up and running (state 4)
using the following command:
srxqry
3. Login to CMP
https://<ipaddress>:446/management/
and navigate to:
Configuration > OpenScape Voice > General > Switches
4. Click on the Add... button.
5. Set the IP Address to 10.82.53.229
6. Enter the srx password: 2GwN!gb4
7. Check the connection by clicking on the Test Connection button.
8. Click Save and wait until the procedure is over.
Note: Wait time can be up to 10 minutes.
9. Log in to Windows VM 1 through console on the vSphere Client.
10. Right click on the desktop and select Screen resolution.
11. Make sure that the resolution is set to 1024 x 768.
12. Copy the twin-1.0.zip file from the oseeai-shared directory to

Windows VM 1. Then proceed to open the folder inside the zip file and
extract the folder’s contents to:
C:\Program Files (x86)\OpenScape Xpressions Application Builder
13. Open CDC_<project_name>.zip generated by WebCDC.

Navigate to the CDC_Information directory and copy sharpclaws.xml.
14. Navigate to C:\Program Files (x86)\OpenScape Xpressions Application

Builder and replace sharpclaws.xml with the one copied in the previous
step.
A31003-S5190-J100-20-7631, 07/2017
osee_auto.fm
Import and Run OSEE Deploy script
15. Run SharpClaws.exe.

A window will open that is required for the tool to successfully continue the
installation.
Note: DO NOT close the window that opens.

If there is no pop up window or the window closes by itself please check
sharpclaws.xml for errors.
16. Minimize all open windows and proceed to the next section without logging
out.
7.3 Import and Run OSEE Deploy script

1. Open the OSEE-AI console.
2. Execute the following command:

./deploy_osee.sh
3. The OSEE Deploy script starts.
4. It is recommended that before you proceed to the next step, if there is

enough space available in the datastore, backup the Virtual Machines using
option 11 (this will not include the SBC-THIG VMs).
Note: You are able to take multiple backups using option 11 but the
Automation Tool will revert to the last one when you select option 12.
You can make use of any other backup you took, through vSphere Client.
Note: Options 11 and 12 are only functional if the VM credentials are added
in the osee-parameters.xml file. See step 17 in Section 6.2.
Note: Take a snapshot of the Windows VMs before proceeding to the next
step.
5. Select options 2-6 sequentially to configure OpenScape Voice, OpenScape

Deployment Service, OpenScape UC, OpenScape Xpressions and
OpenScape Contact Center.
Note: Logs and reports can be found under oseeai-shared/reports and

oseeai-shared/logs respectively.
6. Exit OSEE Deploy script by selecting option 99.
A31003-S5190-J100-20-7631, 07/2017
osee_auto.fm
Import and Run OSEE Deploy script
7. Open the minimized window of Windows VM 1 and right click on the

sharpclaws.exe icon on the taskbar and select Close window.
Note: After successful configuration of all OSEE components, latest released

patches should be also applied per component (i.e. OSV, UC etc.) in case they
are in a higher version than the one delivered with the OSEE release.
A31003-S5190-J100-20-7631, 07/2017
OSB.fm
OpenScape Branch
OpenScape Branch Installation
8 OpenScape Branch
8.1 OpenScape Branch Installation

For instructions on how to install the OpenScape Branch servers refer to Chapter
4 "Installation and Upgrades - Overview" of OpenScape Branch V9, Installation
Guide in e-doku.
8.2 Configuration of OpenScape Branch or Gateway

1. Connect/Insert the USB stick into server.
2. Power up or restart the server.
3. Open an Internet browser and connect to the OpenScape Branch/Gateway.
• https://<IP Address of OpenScape Branch/Gateway>
4. Log on to the OpenScape Branch/Gateway.
• User Id = administrator
• Password = Asd123!. (Please note period [dot] at end of password)
5. Click on OK on the pop-up “You are booting from USB stick/CDROM”.
6. Click on Backup/Restore.
7. Click on Install button under Installation.
8. Click OK button on pop-up “Are you sure you want to perform a full
installation?”.
9. Click OK button on pop-up “System installed. Press OK to reboot the system

now”.
10. Remove the USB stick from the server.
11. Click OK button on pop-up “Please remove the USB stick before continue”.
12. OpenScape Branch/Gateway has been configured.
13. Log in to CMP.
14. Navigate to Configuration > OpenScape Voice > Administration > Media
Servers > List
15. For each OSB Media Server repeat steps 16 - 17.
16. Select an OSB Media Server named as follows:
A31003-S5190-J100-20-7631, 07/2017
OSB.fm
OpenScape Branch
Adding and updating Media Server announcement files
MS_<site name from WebCDC>
Note: Do NOT select the Media Server of the Headquarters/Site 1.
Note: On WebCDC, check the Site and Endpoints tabs for related
information.
17. Click Block.
18. Proceed to Section 8.3, “Adding and updating Media Server announcement
files”.
8.3 Adding and updating Media Server announcement files

By default the OpenScape Branch media server supports US English
announcements. If applicable, add the new default or additional announcements.
1. Download the appropriate language files (example:

OpenScapeUcSuiteApps-German-V7R2.0-150000.iso) from SWS. As sysad
user transfer the file to OpenScape Voice Linux VM.
a) Mount the ISO file to the Linux VM with the following command:
# mount -o loop /home/sysad/OpenScapeUcSuiteApps-German-
V7R2.#.#-######.iso /mnt
b) Copy the media server file (example: mediaserver_announcements_de-

7.1_0.2.0-7.noarch.rpm) from the /mnt/noarch dir on the Linux VM to the
local PC.
c) Unmount the ISO file with the following command:

# umount /mnt
d) Delete the media server ISO file from Linux VM:

# rm /home/sysad/OpenScapeUcSuiteApps-German-V7R2.#.#-
######.iso
2. Select the OpenScape Branch tab within the Common Management

Platform.
– The system presents the OpenScape Branch Overview form with a

current list of all known branch offices of all systems.
3. Select a particular branch office in the Branch Office selection list in the
navigation area.
4. Navigate to Configuration > Media Server.
A31003-S5190-J100-20-7631, 07/2017
OSB.fm
OpenScape Branch
Upload licenses to Common Management Platform
– The Media Server dialog appears.
5. Click the Configure... button in the General field area.
– The Media Server Advanced Features window appears.
6. Click the Browse... button in the Language file field area.
– The Explore dialog appears. Change to the local PC directory where you
copied the media server file in Step 1.b.
7. Select the media server file and click Open.
8. Click the ADD button.
– The value selected appears in the Language file field.
9. Click the OK button.
– The Media Server Advanced Features dialog disappears.
10. In the Media Server window, select the language in the Language drop-
down list.
11. Click the OK button to store the changes temporarily in the administrator’s
login session.
– The Media Server dialog disappears.
12. Click the Apply changes button in the main window to save the changes.
13. In the pop-up Confirmation window click OK to save the changes

permanently.
14. Proceed to Section 8.4, “Upload licenses to Common Management Platform”
8.4 Upload licenses to Common Management Platform
Note: After installing the OpenScape Branch a 30 day grace period is allowed
until licenses are applied. During this grace period, the product is functional. If
licenses are not installed after the grace period, the product becomes severely
restricted or stops working entirely.
The Central License Server (CLS) generates and manages the license files. A
license file is generated when the License Authorization Code (LAC) is sent to the
CLS by the Common Management Platform. The transfer of the license file to the
Common Management Platform occurs automatically via the internet.
A31003-S5190-J100-20-7631, 07/2017
OSB.fm
OpenScape Branch
Apply licenses to the OpenScape Branch
OpenScape Branch Base licenses are configured and activated via the Common
Management Platform (Using ALI of CMP in CLS). The licenses and their related
information are displayed in the Common Management Platform.
1. On the Maintenance navigation tab click on the Licenses navigation menu.
2. Select Information in the navigation tree.
3. Click the Offline Activation... button in the work area.

The License Activation dialog appears.
4. Click on Browse next to the "License file:" field and navigate and select the
license file you have received with the product.
5. Click on Activate
The license information for OpenScape Branch is displayed in the work area.
6. Proceed to Section 8.5, “Apply licenses to the OpenScape Branch”.
8.5 Apply licenses to the OpenScape Branch
Note: Applying licenses require the SIP server to restart in OpenScape Branch.
Therefore, the following steps should be done during a maintenance window.
1. Edit the MAC Address for the OpenScape Branch:
a) Navigate to:
– Configuration > OpenScape Branch > Branch Office List
b) Select the Check Box for the Branch Office and click Edit...
c) Remove the check mark from "Communicating over Secured channel:"
d) Click on Configure Installation button
e) Select the "Hardware Type:" from the drop down lists.
f) Enter the MAC Address of the OpenScape Branch
Note: MAC Address for Node 2 is only required for a redundant

OpenScape Branch.
g) Click OK
h) Click OK
2. Configure and Apply Licenses:
A31003-S5190-J100-20-7631, 07/2017
OSB.fm
OpenScape Branch
a) Navigate to: Configuration > OpenScape Branch
b) Select the Branch from the "Select Branch Office:" drop down list.
c) Under the "Licensing Information" section, click the Configure button.
d) Configure required licenses for the Branch office and click Save
e) Click on Device license update button

The OpenScape Branch licenses are applied.
A31003-S5190-J100-20-7631, 07/2017
OSB.fm
OpenScape Branch
A31003-S5190-J100-20-7631, 07/2017
DLS.fm
OpenScape Deployment Service
DLS Account Management
9 OpenScape Deployment Service
9.1 DLS Account Management

1. Log in to Common Management Platform (CMP) as administrator.
2. Go to:
Configuration > OpenScape Voice > General > Deployment Servers
3. Click on Add...
4. Type a Name of your choice for the Deployment Server.
5. Type the FQDN of DLS on the IP Address or FQDN field.
Note: In case name resolution is not guaranteed by DNS within the network,
name resolution must be made by entries in the local machine's hosts file.
6. Switch to the Advanced Settings tab.
7. Under the User Interface Access section set the username to admin and
the password to dls.
8. Under the Application Interface section set the username to api and the
password to Asd123!.
Note: In case you change the passwords of DLS after the staging of OSEE is
over, make sure that you update the passwords above too.
9. Click on the Save button.
10. Proceed to the next section without logging out of CMP.
9.2 Enable DLS SSO functionality

1. In CMP go to:
Maintenance > Inventory > Applications
2. From the displayed list, click on the arrow next to the Device Management
row and select Create connection...
A31003-S5190-J100-20-7631, 07/2017
DLS.fm
Enable DLS SSO functionality
3. Enter the following:
• IP Address/Hostname: dls.<corp domain name>
Note: This FQDN can be found in the fqdn.cfg file in the OSV server
under the /etc/hiq8000/ directory and should be resolvable.
• Port: 10443
4. Click on Retrieve Certificate.
5. Under the Device Management section enter the username and password
for the DLS server.
• Username: admin
• Password: dls
6. Click Save.
A31003-S5190-J100-20-7631, 07/2017
DLS.fm
Enable Plug&Play via DHCP
9.3 Enable Plug&Play via DHCP
Note: To enable auto-configuration (Plug&Play), the DLS IP address must be

entered in the device manually or configured via the DHCP server.
Parameters required to enable Plug&Play functionality for the IP phones:

1. The IP phones must be supplied with the customer‘s IP configuration
• IP address
• Subnet mask
• Default gateway
• DNS (NOTE: This is the SBC-THIG IP address).

2. The DLS server must be specified as "Vendor Specific Information" in the
DHCP:
• Tag "001": Vendor name Siemens (required)
• Tag "002": Assigned VLAN-ID (only when necessary)
• Tag "003": IP address of SBC-THIG

The DHCP server supplies the OpenStage with the IP, DNS and default
gateway addresses and other optional information, as the result of an
address query. In addition, the DHCP server can distribute the IP address and
port number of the DLS. This added information is provided in the form of
Vendor Specific Information Elements by the DHCP server. The allocation is
carried out on the basis of Vendor Classes.
DHCP server settings

1. DHCP Option Class 043
To transfer the vendor-specific information, Option 043 specified data in the
DHCP server may be used. This data must be entered in Hex format.
A31003-S5190-J100-20-7631, 07/2017
DLS.fm
– Option 043 Hex format for OpenScape Enterprise Express V9, with no
VLAN ID defined
010A5369656D656E73000000031873646C703A2F2F3137322E32302
E36322E363A3138343433000000000000FF
Note: When Option 043 is used, all IP devices that place DHCP requests in
the IP range obtain its defined information. There may be IP devices that
interpret the information incorrectly, and consequently fail to work properly. To
avoid this situation, the use of Defined Vendor Classes may be preferred.
Configuration information of Defined Vendor Classes can be found in the
OpenScape Deployment Administration Documentation.
2. DHCP with Linux (File: dhcpd.conf)

The configuration is performed in the /etc/dhcpd.conf file. This file can easily
be edited with any text editor. This file shows a configuration example which
can be adapted to the customer’s needs.
Warning: Before every change of the configuration file, a back up of the

original file must be done.
A31003-S5190-J100-20-7631, 07/2017
DLS.fm
This option can be defined as a class for all network ranges at the start of the
configuration file or inserted within individual subnet configurations.
To obtain a result that is equivalent to that of Option 43, only use the string
option vendor-encapsulated-options... in the network range.
Note: The DHCP service must be restarted to save the changes.
A31003-S5190-J100-20-7631, 07/2017
DLS.fm
A31003-S5190-J100-20-7631, 07/2017
XPR.fm
OpenScape Xpressions
Special Server Settings
10 OpenScape Xpressions
10.1 Special Server Settings

1. Log into Xpressions Web Assistant using the following credentials:
• User: ADMINISTRATOR
• Password: Asd123!.
2. Select Special server settings > Mask editor and from the dropdown list
select USER and click Edit.
3. Add the following line below FAXG3-ID:
4. Scroll to the bottom of the page and click Save.
10.2 Customizing the AutoAttendant
10.2.1 Example with predefined AutoAttendant script

DID number xxx is routed from OpenScape Voice to OpenScape Xpressions.
The following announcements are heard:
• Custom Greeting announcement “Thank you for calling XYZ Corporation”
• Custom Menu announcement listing the User OPTIONS:
1. "If you know your parties extension please press 1”
– Announcement “Enter the extension number then push #”

2. “To search by name, please press 2”
– Announcement “Please enter a name, Last name then first name. To

restart your search push #, to cancel push *”
Note: The call flow for the name search is set for LastName, FirstName.
If WebCDC was built with the Display Name set for FirstName LastName
then the search order will have to be manually changed in the Application
Builder script on Xpressions.
A31003-S5190-J100-20-7631, 07/2017
XPR.fm
Customizing the AutoAttendant
3. “To be transferred to the Sales group, please press 3”
– Call is routed to a profile only DN with RCF to MLHG Pilot (1)

controlled by OpenScape Contact Center
4. “To be transferred to someone in Customer Service, please press 4”
– Call is routed to a profile only DN with RCF to MLHG Pilot (2)

controlled by OpenScape Contact Center
5. “To be transferred to an Operator, please press 0”
– Call is routed to an Extension number or MLHG pilot

If a caller selects option 3 or 4 and no Agents are logged in, then the call is
immediately routed to a DN which results in a custom ‘closed’ announcement.
– Announcement: "Thank you for calling XYZ Corporation, currently

there is no one available to take your call, please call back during
normal business hours".
10.2.2 Steps to modify the AutoAttendant Destination

Routes
The following steps allow the user to configure the destination routes from the
AutoAttendant (i.e. where the calls get routed via AutoAttendant)
1. Log on to the Windows VM machine as Administrator.
2. On desktop, right click Application Builder icon and select Run as

Administrator.
3. If the Xpressions Server Login is showing "Current Status = Not Logged In",
select Administrator from the drop-down list and then click on the Login
button. If it is showing "Current Status = Logged In (user 'ADMINISTRATOR'
on server 'XPRESSIONS')", then continue onto next step.
4. Under the Workspace window on the left hand side expand the
AutoAttendantWTime application. Double click on Time to open the callflow.
5. Under the Callflow (Time) window right click on Definition Configurations

and select Properties.
6. Select the Commands tab. In this window you can define the extensions
where the calls will be routed.
• $PREDEFEXT1 – Destination Extension if the user selects option 3 from

AutoAttendant menu, this should be the extension part of what you
defined as Call in Public directory number for OSCC Call Center Group
1, i.e. -1200.
A31003-S5190-J100-20-7631, 07/2017
XPR.fm
Customizing the AutoAttendant
• $PREDEFEXT2 – Destination Extension if the user selects option 4 from

defined as Call in Public directory number for OSCC Call Center Group
2, i.e. -1204
• $OPERATOR – Destination Extension if the user selects option 0 from

defined as Operator Extension, i.e. -1999
7. Click OK.
8. Redeploy the AutoAttendantWTime and OSCC closed message applications.
• Right-click on AutoAttendantWTime and select Deploy Application...
– Protocol Name: Vogue (extension range defined during

Xpressions configuration)
– Phone Number: extension defined as Auto Attendant Number

(Public) i.e. - 1000
– Click Finish
• Right-click on OSCC closed message and select Deploy Application...
– Protocol Name: Vogue (extension range defined during

Xpressions configuration)
– Phone Number: extension defined as Closed Announcement

(Private) Extension for OSCC Call Center Group 1, i.e. - 1001
– Click Finish
Note: Repeat this step for all required numbers.
9. Stop and restart OpenScape Xpressions before proceeding to the next step.
10.2.3 Steps to modify the Announcements

1. There are three announcements that will have to be customized as part of the
base package.
• Greeting Announcement (Greeting.wav)
• Menu Announcement (Menu.wav)
• Closed Announcement (Closed.wav)
2. The recommended format properties for announcements recorded in the pcm

or wav file format read:
• 8 kHZ sample rate
A31003-S5190-J100-20-7631, 07/2017
XPR.fm
Number Conversion (NCO) rules modification
• 16-bit resolution
• channel mono
• linear coding.
3. Custom announcements can be recorded using a 3rd party SW or by using

the OpenScape Xpressions to leave a Voice Mail, then copy/ rename the file
as an announcement. Once the "Custom” Announcements are recorded, they
can be renamed identical to the file names above and copied into the
following directories:
• Place the "Greeting.wav" and the "Menu.wav" in the following directory:

C:\AppBuilder_Workspace\items\AutoAttendantWTime\prompts\america
n
• Place the "Closed.wav" in the following directory:

C:\AppBuilder_Workspace\items\OSCC closed
message\prompts\american
Note: Changing these files require the "AutoAttendantWTime" and "OSCC

closed message" to be Redeployed. Section 10.2.2, “Steps to modify the
AutoAttendant Destination Routes” step 8 will perform this task.
10.3 Number Conversion (NCO) rules modification

1. Log in to vSphere Client.
2. Right click on WIN_VM1 and select Open console.
3. Log in as administrator.
4. Open the built-in file explorer and navigate to C:\openscape\xpr\res\NCO.
5. Run the NCOAdminDownload.exe file.
6. Navigate to the newly created folder

C:\openscape\xpr\res\NCO\NCOAdminDownload
7. Run NumberConversionAdmin.exe
The Number Conversion administration application is launched.
8. Switch to the Localization tab and when prompted enter the following
password
xyzzy
9. Double-click on the Telematic localization entry.
A31003-S5190-J100-20-7631, 07/2017
XPR.fm
Number Conversion (NCO) rules modification
10. On the displayed Localization rules - Telematic localization window,

double-click on the entry with Rule description use international number
type in the Conversion rules section.
11. On the displayed Conversion batch rule for localization window, switch to
the Result tab.
12. Add a leading '+' symbol to the variable $1 in the Resulting normalized
number section.
13. Click Save and accept all subsequent prompts.
A31003-S5190-J100-20-7631, 07/2017
OSCC.fm
OpenScape Contact Center
OpenScape Contact Center Configuration
11 OpenScape Contact Center

Before proceeding with the configuration of OpenScape Contact Center, make
sure that all hotfixes have been applied.
11.1 OpenScape Contact Center Configuration

1. In Windows VM 1 open Server Manager and click on Tools > Services.
2. Start the OpenScape Contact Center service:

Right click > Start
3. Wait for all OSCC servers to start:
4. Launch OpenScape Contact Center Manager and login using the following
credentials:
• User name: master
• Password: password
Click on the Options >> button and fill in the following:
• Connect to: Production Database
• Administration Server: 6000@vm
• Business Unit: DEFAULT
5. Click on File, select Save Database As...:
a) Select From a design database to this production database, and

choose the updated design database OSCCCDCImportTemplate-
enterprise-V8R2GP8.mdb.
Note: The updated design database can be found under:

C:\OSEE_SI_Staging\WORKING\OSCC_DB_template\OSCC CDC
Import Tool version #.#.#.##
b) Press OK.
A31003-S5190-J100-20-7631, 07/2017
OSCC.fm
OpenScape Contact Center Configuration
c) Click Yes on the OpenScape Contact Center Manager window.
Note: Wait a few minutes.
d) Click OK in the pop-up window.
6. Restart OpenScape Contact Center:
a) Open Server Manager and click on Tools > Services and stop the
OpenScape Contact Center service:
Right click > Stop
b) Wait a few minutes for the service to stop:

Make sure that all servers have stopped in the OpenScape Contact
Center Server status window.
c) In the Services window start the OpenScape Contact Center service:

Right click > Start
Note: The startup process takes a few minutes. Wait until all servers
except for the Statistics Server, T-Server and Presence Server are
running.
7. Back on the main screen of OpenScape Contact Center Manager, navigate

to Tools > Options
8. Under the System Settings area select Voice
9. Select the Communication Platform tab and fill in the following:
• Type: OpenScape Voice V9
• IP address: 10.82.53.231
10. Click Apply.

Acknowledge the restart warnings and exit the OpenScape Contact Center
Manager application.
11. Restart OpenScape Contact Center following the instructions in step 6 but
make sure that ALL servers are running this time.
12. Log in again to OpenScape Contact Center Manager as in step 4.
13. Click on Administration Center and then click on Locations under the
General area
14. Double click on the entry Default in the Locations list and set the Time zone
to the location of OpenScape Contact Center. Click OK.
15. Click on File > Exit to exit OpenScape Contact Center Manager
16. Restart OpenScape Contact Center following the instructions in step 6 but
make sure that ALL servers are running this time.
A31003-S5190-J100-20-7631, 07/2017
OSCC.fm
OpenScape Contact Center Client
11.2 OpenScape Contact Center Client
11.2.1 System requirements for a client machine

The minimum system requirements for installing the OpenScape Contact Center
software on a client machine are listed in the table below.
Note: These are the minimum system requirements. For improved performance,
use hardware that exceeds these minimum requirements.
Note: If you intend to run two instances of the Manager application on a client
machine simultaneously, the hardware should exceed the minimum system
requirements to ensure a reasonable level of performance.
Requirement Client Desktop Manager or System Monitor

Processor* Intel Pentium 4 at 1.6 GHz Intel Pentium 4 at 1.6 GHz (Intel
(Intel Pentium Dual-core Pentium Dual-core E2180 at 2.0
E2180 at 2.0 GHz GHz recommended)
recommended)
Memory 512 MB (1 GB recommended) 1 GB (2 GB recommended)
Hard Drive 100 MB available disk space 500 MB available disk space
Display Settings 1024 x 768 pixels with 16-bit color
Operating System • Windows 10 Professional or Enterprise Edition
• Windows 8 or 8.1 Professional or Enterprise Edition or later
• Windows 7 Professional or Enterprise Edition or later
• Windows Vista Business or Enterprise Edition with Service Pack
2 or later
Other • 100 Mbps Ethernet • 100 Mbps** Ethernet network
network infrastructure for infrastructure for the customer
the customer LAN LAN
• DVD-ROM drive (optional) • DVD-ROM drive (optional)
• Sound playback device for
listening to .wav files or audible
thresholds from reports
(optional)
* The OpenScape Contact Center software has been tested on machines running Intel dual-core,
Intel quad-core, and AMD dual-core processors. In general, hardware that meets or exceeds the
minimum requirements can be used, provided that it delivers comparable or better performance.
** 10 Mbps Ethernet network infrastructure is only supported if there are no Client Desktop
applications and no more than five concurrent Manager applications installed on the system
A31003-S5190-J100-20-7631, 07/2017
OSCC.fm
11.2.2 Software installation on a client machine

This section describes how to install the OpenScape Contact Center client
software on a client machine.
Note: If the client machine is running Windows Vista, Windows 7, Windows 8, or

Windows 8.1 and you want to test the server connection during installation (see
step 15), you must disable the Windows Firewall or configure it to allow all traffic
between the client and server machine before you begin.
To install the software on a client machine:

1. From the client machine initiate a Remote Desktop Connection to the
Windows Server that hosts OpenScape Contact Center.
Set the following options for the Remote Desktop Connection:
• Click on Show Options on the Remote Desktop Connection window.
• Click on the Local Resources tab.
• In the Local devices and resources section click on the More… button.
• On the next window expand Drives and select the local drive that you
would like to save the software to. You will need a location that has space
of at least 1GB to copy the folder.
• Click the OK button.
• Click on the Connect button.
• Click on the Connect button on the “Do you trust this remote
connection?”.
• Enter the Administrator’s User name and Password. Click OK.
2. On the Remote Desktop Connection to the Windows Server go to:

Start > Computer
3. In the Computer window you will see under the are Other a System Folder.
This is your local PC connection drive.
4. Open the folder and navigate to the location you would like to save the
software.
5. On the Remote Desktop Connection to the Windows Server navigate to:

C:\Program Files (x86)\OpenScape\Contact Center\NetSetup
6. Copy the folder OpenScape Contact Center Client from the Remote
Desktop location to the window that has the local drive location from step 4.
A31003-S5190-J100-20-7631, 07/2017
OSCC.fm
7. Close the two windows that were opened on the Remote Desktop connection
and close the Remote Desktop Connection.
8. The software can now be installed on the Client machine or transferred to the
PCs that the “OpenScape Contact Center Client Software” is required on.
9. To install the OpenScape Contact Center Client Software, open the

OpenScape Contact Center Client folder, and then double-click setup.exe
10. Select a language for the installation, and then click OK.
11. In the Welcome dialog box, click Next.
Note: The installation wizard performs a system check to ensure that the
client machine meets the minimum requirements for installing the
OpenScape Contact Center client software. If the client machine fails to meet
one of these requirements, you will be unable to install the client software.
12. In the License Agreement dialog box, read the license agreement, mark the
I accept the terms in the license agreement checkbox, and then click Next.
13. In the Customer Information dialog box, type your name and the name of
your organization, and then click Next
14. In the Setup Type dialog box, select Typical, and then click Next.
15. In the OpenScape Contact Center Server Configuration dialog box, enter
the following information:
• Machine Name: <IP Address of OSCC>
• Port Number: 6000

Click the Test button and then click on Next.
16. In the Ready to Install dialog box, click Install.
17. When the installation process is complete, click Finish.
18. The Client can be launched from:

Start > All Programs > OSCC Enterprise > Client Desktop
19. The folder containing the software for installation can now be deleted off of
the client’s PC, as it is no longer needed.
Note: For default OpenScape Contact Center client login credentials, refer to
step 2 in Appendix A.6, “Passwords for OpenScape Contact Center”.
A31003-S5190-J100-20-7631, 07/2017
Concierge.fm
OpenScape Contact Center Extensions, Concierge
OpenScape Contact Center Extensions Configuration
12 OpenScape Contact Center Extensions, Concierge
12.1 OpenScape Contact Center Extensions Configuration

1. Log in to OSCC-E System Management using the following credentials:
• Username: manager
• Password: manager
2. On the side menu navigate to Basics > Basic Services.
3. Under Log Transfer Settings select the checkbox Transfer Enabled and
type in the following:
• Hostname: 10.82.53.249
• Username: tracedata
• Password: Asd123!.
• Destination Path: /tracemanager/OSCCE
4. Under Client Settings set the following:
• HTTP Port: 449
5. Navigate to Action > Publish Installation Data and select Yes > Yes.
12.2 Concierge Client Installation
Note: Only Server Host Names must be entered during installation and
configuration - DO NOT enter IP addresses. In case name resolution is not
guaranteed by DNS within the network, name resolution must be made by entries
in the local machine's hosts file.
Note: You have to use a local user account with administration rights.
1. Copy the following files from the Windows VM to the local PC:
– C:\Program Files(x86)\OpenScape Contact Center

Extensions\ClientSetups\Concierge-Setup.exe
– C:\Program Files (x86)\OpenScape Contact Center

Extensions\ClientSetups\Concierge.msi
A31003-S5190-J100-20-7631, 07/2017
Concierge.fm
OpenScape Contact Center Extensions, Concierge
Concierge Client Installation
2. Double Click on Concierge-Setup.exe
3. The "Welcome to the OpenScape Contact Center Extensions Concierge

Setup Wizard" window opens. Click Next.
4. Read the End User License Agreement (EULA) and then click Accept.
5. The setup offers the creation of application shortcuts. Select the desired
locations and click Next.
6. The setup requires the Main Server Host Name and the port number to
connect to.
Note: Enter the Server Host Name of the OSCC-E server and NOT the IP
address. In case name resolution is not guaranteed by DNS within the
network, name resolution must be made by entries in the hosts file
After entering the required parameters click Next.
7. Configure the Product Features / Applications you want to install on your PC

by setting the corresponding checkmarks for the Concierge Client GUI and
the Concierge Management Applications.
8. Change to the tab Installation Folder to view or modify the folder where the
application will be installed. The required and available disk space is
displayed. Click on Next.
9. Click on INSTALL.
10. After the installation is complete click Finish to close the installation wizard.
A31003-S5190-J100-20-7631, 07/2017
TM.fm
OpenScape Trace Manager
OpenScape Voice Tracing
13 OpenScape Trace Manager

13.1 OpenScape Voice Tracing
OpenScape Trace Manager (OS-TM) is an application that offers the capability to
collect OpenScape Voice trace data, OpenScape Branch data and Phone Quality
of Service (QoS) data. It also aids on the identification of specific trace files that
can be used for analysis and troubleshooting of OpenScape Voice, OpenScape
Branch and Phone QoS problems.
Note: 24/7 continuous tracing is turned on by default for OpenScape Enterprise

Express V9.
The FADE tool can be used when attempting to locate and analyze trace data for
a specific issue, problem or error condition. Follow the steps below to log in to
FADE:
1. Double-click on the FADE shortcut to launch the Trace Management Portal.
2. Use the following credentials when you log in for the first time:
• Username: Admin
• Password: Admin
After logging in, you will be prompted to set a new password. It is suggested
to use Asd123!. as the new password.
All trace files are stored under the following directory:

D:\Tracedata\tracemanager
13.2 Configure OpenScape Trace Manager to Collect Phone QoS data

(Optional)
The Quality of Service (QoS) data generated from the phones is collected in the
OpenScape Trace Manager server by the Phone Listener or Phone Trap. The
ports used by the phone and by OpenScape Trace Manager must agree to have
successful connectivity. Only one phone listener is configured per OpenScape
Voice system and correspondingly per OpenScape Trace Manager system.
Note: When configuring Phone Listeners for multiple systems on the OSV-TM
server, the Trace and Trap port numbers must be unique for each OSV-TM
system. Do not use the same port number.
A31003-S5190-J100-20-7631, 07/2017
TM.fm
Configure OpenScape Trace Manager to Collect Phone QoS data (Optional)
1. Login to Trace Manager Portal (FADE) web interface
2. Click view Administration > Manage Phones
3. There are three possible options in the Manage Phones tab: add, delete or
modify phones depending on the existing phone configuration.
• Add Phone
If there is no phone configured for the current system, then the Add
Phone button is displayed.
Continue with step 4.
• Delete Phone
• Modify Phone
4. Enter the required information for the Phone:
a) Phone Trap Port 17001.
b) Phone Trace Port 501.
c) Max CAP File Size (MB): 2MB (default)

If the file exceeds this size then a new CAP file is created.
d) Max Trace File Size (MB): 2MB (default)

If the file exceeds this size then a new Trace file is created.
e) Continue with step 10.
5. Go to the Phone entry to delete.
6. Click Delete right to the Phone entry.

Note: The existing Phone trace files and data are not deleted from the system
but are aged by the DIPAZ monitor.
7. Go to the Phone entry to modify.
8. Click Modify right to the Phone.
9. Change, if necessary, its ports or the file sizes (allowed values: see step 4).
10. Click Save

A message indicates that the changes will take effect in 2 minutes.
A31003-S5190-J100-20-7631, 07/2017
TM.fm
Configure Phone Devices to Send QoS Data to OSV-TM Listener (Optional)
13.3 Configure Phone Devices to Send QoS Data to OSV-TM Listener

(Optional)
Note: Configuration of the telephones should be preformed after business hours

as the device requires a reset on the phones causing a service interruption. This
procedure can only be run after the phones have been deployed and configured.
1. Login to Common Management Platform as administrator.
2. Go to:
– Configuration > OpenScape Voice > General > Deployment Servers
3. Select the icon under DLS Management Panel.
4. Go to:
– DeploymentService > IP Devices > IP Phone Configuration > QoS

Data Collection
5. Search for phone to configure.
6. Change to Table view by checking the Table option on Views.
7. Configuration of Traps for phones.
a) Check box “Send Traps QCU”.
b) Set “QCU Home Address” to OSV-TM IP address.
c) Set “QCU Host Port Number” to 17001.
d) Set “Report Mode” to EOS (End of Session)
8. If configuration is only for one phone click Save button. If configuring multiple
phones highlight the additional phones that require configuration and then
click on Save button.
9. Go to:
– DeploymentService > IP Devices > IP Phone Configuration >

Diagnosis
10. Search for phone to configure.
11. Change to Table view by checking the Table option on Views.
A31003-S5190-J100-20-7631, 07/2017
TM.fm
Configure Phone Devices to Send QoS Data to OSV-TM Listener (Optional)
12. Configuration of Traces for phones.
a) Set “Call View phonelet” to debug.
b) Set “Communication service” to debug.
c) Set “CSTA service” to Debug.
d) Set “SIP Signaling” to Debug.
e) Set “SIP Call Control” to Debug.
f) Set “SIP Messages” to Debug.
g) Set “Trace file size (bytes)” to 1048576.
h) Set “Trace timeout (min)” to 999.
i) Check box for “Core dump enabled”.
j) Check box for “Remote Trace”.
k) Set “Remote Trace Destination” to OSV-TM IP address.
l) Set “Remote Trace Port” to 501.
m) Check box “Store Security Log File to DLS”.
13. If configuration is only for one phone click Save button. If configuring multiple
phones highlight the additional phones that require configuration and then
click on Save button.
14. The phones will need to be reset.
Note: This will reset the phones and this should be done during a
maintenance window, as this will cause a service disruption.
a) Go to:
– DeploymentService > IP Devices > IP Device Interaction > Reset

IP Devices
b) Search for the phone that was configured.
c) Change to Table view by checking the Table option on Views.
d) If reset is only for one phone click on “Reset IP Device” button. If resetting
multiple phones highlight the additional phones that require reset and
then click on “Reset IP Device” button.
A31003-S5190-J100-20-7631, 07/2017
TM.fm
Configure UC Remote Logging to OpenScape Trace Manager
13.4 Configure UC Remote Logging to OpenScape Trace Manager

1. After logging into CMP navigate to Maintenance > Monitoring
2. In the navigation tree, click Logs > Remote Logging for OSV-TM
The Remote Logging for OSV-TM window opens.
3. Check the box Enable Remote Logging
4. Select the sequence in which a trace file will be sent to OSV TM.
The Send every field can be:
from 5 to 60 Minutes with a step of 5 minutes
or
from 1 to 24 Hours with a step of 1 hour
Note: The default value of Send every field is 5 minutes
Note: So if the Send every field is set to 5 minutes:

CMP will send every hour 12 trace files (one every 5 minutes with each one
containing symphonia information for the chosen period).
If the Send every field is set to 30 minutes:
CMP will send every hour 2 trace files (one every 30 minutes with each one
containing symphonia information for the chosen period).
In any case the trace files sent from CMP will contain all the trace information
of the chosen period.
5. Configure the Save the last field so all trace files of this time period during a
transmission failure are saved in CMP and transmitted when possible.
The Save the last field can be:
from 5 to 60 Minutes with a step of 5 minutes
or
from 1 to 24 Hours with a step of 1 hour
Note: The default value of Save the last field is1 hour
Note: If there is a transmission failure towards OSV-TM and you have set the:
Save the last field to 3 hours
Send every field to 30 minutes
and the transmission to OSV-TM is re-established after 5 hours
A31003-S5190-J100-20-7631, 07/2017
TM.fm
Configure UC Remote Logging to OpenScape Trace Manager
Then:
the trace files of the first 2 hours of the failure period are deleted and the last
3 hours of the period have generated 6 trace files that are sent to OSV-TM.
6. Enter the path "/tracemanager" to OpenScape Trace Manager directory in

the Directory field.
7. In the field IP/Hostname, enter the IP or Hostname of the OSV-TM SFTP

server.
8. Enter the Port Number of the OSV-TM SFTP server, default value is 22
9. Add Default Username = tracedata
10. Add Default Password = Asd123!.
11. Click Save.
12. Activate UC Tracing.
a) Navigate the CMP to Maintenance > Monitoring
b) Select the Configuration Files under Tools & Utilities
c) Click on the Node name
d) Select the left of the File Name “log4j-sip-csta.xml”
e) Select Activate button on the upper right side of the Menu
f) Enter a Name and Reason (example: “OSVTM” for both)
g) Select “Activate”
A31003-S5190-J100-20-7631, 07/2017
UC.fm
OpenScape UC
Configuration of Trusted Transfer Mode (TTM)
14 OpenScape UC
If the Media Server Conference Number field has been modified in WebCDC
under the Site tab, the following configuration steps are required:
1. Log in to CMP.
2. Navigate to Configuration > Unified Communications.
3. Under the Configuration section click on Conferences.
4. Switch to the Configuration tab and click on Bridge Numbers.
5. The following message will be displayed:

Bridge number has been converted to the new format. Please
review and save.
Click on Close.
6. Click Save and then Close.
14.1 Configuration of Trusted Transfer Mode (TTM)

Check Chapter E.8 Operation Mode Settings of Application Profiles of
OpenScape UC Application V9, Configuration and Administration, Administration
Guide.
A31003-S5190-J100-20-7631, 07/2017
UC.fm
OpenScape UC
Configuration of Trusted Transfer Mode (TTM)
A31003-S5190-J100-20-7631, 07/2017
UserTemplate.fm
User Template
Create Subscriber Template
15 User Template
15.1 Create Subscriber Template

OpenScape Contact Center requires five Subscriber templates. The steps below
should be repeated using the names and feature profiles provided in the table
below.
Name Feature Profile

Standard FP_UC_Nat
OSCC_Agent FP_OSCC_Agent_Nat
OSCC_Supervisor FP_OSCC_Supervisor_Nat
MLHG_Standard FP_OSCC_Initial_MLHG_Nat
MLHG_with_MoH FP_OSCC_MoH_MLHG_Nat
1. Log on to the CMP and navigate to Configuration > OpenScape Voice tab.
2. Click on the Business Group icon.
3. Select a BG from the Business Group List drop-down list.
4. Navigate to General > Subscriber Templates.
5. Click Add... on the upper right corner
6. On the window that pops up navigate to the General tab.
7. Type in Standard in the field Name for the Subscriber Template.
8. Click on the button ... next to the field of Time Zone
9. Select the time zone and click OK.
10. Navigate to the Security tab
11. Select the SRTP support “Automatic” from the drop-down list
12. Navigate to the Features tab
13. Select the Feature Profile “FP_UC_Nat” from the list
14. Click Save
– The Subscriber Template is saved and displayed in the Subscriber

Template list.
15. Repeat the steps above for each of the names and feature profiles listed in
the table above.
A31003-S5190-J100-20-7631, 07/2017
UserTemplate.fm
User Template
Create Standard Locality
15.2 Create Standard Locality

A Standard Locality needs to be manually created with the default values. The
new standard locality will contain specifications for all three types (OSV
Subscriber, UC account, Xpressions account). Each resource type needs to be
configured with the appropriate values for the customer.
1. Log on to the CMP and navigate to the User Management
2. Click on the Localities under Administration.
3. Click on Add
4. Enter a Locality site name
5. Configure Rules for resource configuration Click on Configure... for

OpenScape Voice
6. Select form Operation Mode “Enabled”
7. Select the appropriate Customer specific Attributes from each drop-down list.
8. Click OK
9. Configure Rules for resource configuration Click on Configure... for

10. Select from Operation Mode “Enabled”
11. Enter the Preferred Address name “MAILBOX”
12. Enter the Voice Mail System name “PHONEMAIL”
13. Enter the Internal mailbox name “default”
14. Check the CTI Journal box.
15. Set the Home Time Zone and Language as required by the customer
16. Click on OK
17. Configure Rules for resource configuration Click on Configure... for Unified
Communications
18. Select from Operation Mode “Enabled”
19. Click on the Translator Context list box. Select the radio button for the
appropriate Translator Context in the list.
20. Click on the Voice Mail Number list box. Select the radio button for the
appropriate Voice Mail Number in the list.
21. Click OK and then click Save on the Add Locality Window.
A31003-S5190-J100-20-7631, 07/2017
UserTemplate.fm
User Template
Create User Template
15.3 Create User Template

A default User Template needs to refer to the default resource template
previously created (OSV Subscriber “Standard”). The following two profiles were
automatically created and also need to be referred: UC Profile “Team with
Xpressions” and Xpressions Template “USER”
1. Navigate to User Management > Administration > User Templates
– A list of the existing User Templates is displayed.
2. Click Add to create a new User Template
– A pop-up window Add User Template is displayed.
3. Fill in the name field with the name “Default”
4. Click on Add... to the right of OpenScape Voice on the Add User Template
screen
5. In the Operation Mode drop-down list, select “Create new resources”
6. Select from Resource Template (i.e “Standard@Domain”)
7. All remaining entries can remain as default
8. Click OK
9. Click on Add... to the right of OpenScape Xpressions on the Add User

Template screen
11. Set the Xpressions User ID to “UM User ID”
12. In the Resource Template drop-down list, select “USER”
13. In the Voice Mail drop-down list, select “Use Business Phone 1”
14. In the Business Phone drop-down list, select “Use Business Phone 1”
15. Fill in a user defined Password and PIN
16. Leave remaining fields as default.
17. Click OK
18. Click on Configure... to the right of Unified Communications on the Add User
Template screen
20. Select from the UC Profile drop-down list, the UC Profile that contains Team
with Vmail via Xpressions (e.g. “Team with Xpressions”)
A31003-S5190-J100-20-7631, 07/2017
UserTemplate.fm
User Template
Example of Creating a UM User with the created default Template
21. In the ONS Number drop-down list, select “Use the OSV resource assigned
to this User Template”
22. Select a default Login password and Telephony PIN, and check the User has
to change boxes.
23. In the IM Address drop-down list, select “User IM Address”
24. Click OK
25. Click on Configure... to the right of Xpressions/UC Integration on the Add

User Template screen
26. Change the Operation Mode to “Enabled” using the drop-down list
27. Click OK
28. Click Save
15.4 Example of Creating a UM User with the created default Template

OpenScape Conference Xpress can now utilize the newly defined template to
create additional UM Users.
Note: Default template can also be used as a guide to create additional templates
based on the customer unique configuration.
The following example provides the steps to create a UM User and resource
assignments using the created default template.
1. Log on to the CMP and navigate to the User Management
2. Click on Users & Resources under Administration
3. Click on Add
4. Fill in the “User ID” (i.e. 15619232052), and “Business phone 1” (Enter in GNF
format i.e +15619232052)
5. Enter user’s Display name and Last name
6. Enter the Newly created Locality (e.g. Boca)
7. On the Advanced tab enter the IM address (i.e. 15619232052@im.server)
8. Click Save
9. Select the newly created UM User by placing a check mark to the left
10. Select the “More” button (upper right side of the screen) and select the “Add
Resource from Template…”
A31003-S5190-J100-20-7631, 07/2017
UserTemplate.fm
User Template
11. Select the Default from the drop-down list and click Start
12. Verify the pop-up “Operation completed successfully”
13. Click Close
14. Click Close
The newly created UM User will now have the following resource created: OSV
Subscriber, OpenScape UC App, and OpenScape Xpressions.
A31003-S5190-J100-20-7631, 07/2017
UserTemplate.fm
User Template
A31003-S5190-J100-20-7631, 07/2017
osee_hardening.fm
OSEE Hardening
Apply Group Policy
16 OSEE Hardening
IMPORTANT: After the staging of OpenScape Enterprise Express is over, the
OSEE-AI virtual machine is no more needed. It also poses a security threat to
your systems and as a result it must be deleted:
1. Copy the log files from the oseeai-shared\logs directory to a safe location.
2. Backup any files stored in the datastore of OSEE-AI.
3. Delete OSEE-AI VM from the disk.
a) In vSphere right click on the OSEE-AI VM.
b) Select Delete from Disk.
The following sections are approved for deployments with hardware provided by
Unify and should be used for Software-only solutions only if the customer agrees.
16.1 Apply Group Policy

1. Install the LocalGPO.msi package.
Note: The package is located under C:\OSEE_SI_Staging\GPO
2. Start the LocalGPO Command line tool:

Start > All Programs > LocalGPO > LocalGPO Command-Line
3. Import the Group Policies into the Local Group Policies by running the
LocalGPO.wsf command.
Example:
C:\Program Files (x86)\LocalGPO>LocalGPO.wsf /
Path:C:\OSEE_SI_Staging\GPO\{51080B1C-F8E2-466F-8326-
F70465AFA8FA}
Microsoft (R) Windows Script Host Version 5.8

Copyright (C) Microsoft Corporation. All rights reserved.
Modifying Local Policy... this process can take a few

moments.
"Applied valid INF from C:\OSEE_SI_Staging\{51080B1C-F8E2-

466F-8326-F70465AFA8FA}
"Applied valid Machine POL from C:\OSEE_SI_Staging\{51080B1C-
F8E2-466F-8326-F70465AFA8FA}
A31003-S5190-J100-20-7631, 07/2017
osee_hardening.fm
OSEE Hardening
Running the common security hardening script
"No valid User POL to apply in C:\OSEE_SI_Staging\{51080B1C-

F8E2-466F-8326-F70465AFA8FA}
"Applied valid Audit Policy CSV from
C:\OSEE_SI_Staging\{51080B1C-F8E2-466F-8326-F70465AFA8FA}
Local Policy Modified!

4. Close all open windows.
5. Shut down OSCC:
a) Navigate to Start > OpenScape Contact Center Enterprise > System

Monitor
b) Select the central node (vm) and then click on Stop Machine.
c) Click Yes and wait for the servers to shut down except for:
• Watchdog server
• Administration server
d) Exit System Monitor.
6. Restart the server.
The Microsoft LocalGPO package may be removed from the Server as it is no

longer required or it can be left on the system for future use.
16.2 Running the common security hardening script

The following subsection describes how to execute the script to perform the
Security Hardening of the ESXi host, network settings, and Virtual Machines.
Note: Upon execution of the OSEEsecurity.sh script in the last step, SSH access
will be automatically disabled again.
A31003-S5190-J100-20-7631, 07/2017
osee_hardening.fm
OSEE Hardening
16.2.1 Execution of the OSEEsecurity.sh hardening

script
This step will perform the security hardening of the ESXi host, network settings,
and all Virtual Machines that exist on the host. This step is executed after all of
the VMs have been deployed.
Note: The PC connecting via Remote Desktop must support NLA (Network Level
Authentication). Please see OS manufacture for details on requirements for this.
Note: Repeat the procedure described below for all Virtual Machines.
1. From a PC initiate a Remote Desktop connection to the Windows Server

2012 R2 Virtual Machine and enter the Windows Virtual machine IP address
and user Administrator then set the following options for the Remote Desktop
connection:
a) Click on Show Options on the Remote Desktop Connection window.
b) Select the “Local Resources” tab.
c) Under Local devices and resources click More…
d) Expand Drives and select a drive that you want to save the software to.
Note: You will need a location that has enough space to copy a 624MB
sized folder.
e) Click OK.
f) Click Connect.
g) Enter the Administrators user ID and password. Click OK.
2. On the Remote Desktop connection of the Windows Server 2012 R2 go to:

Start > Computer
3. In the Computer window you will see a System Folder in the area Other. This
is your local PC connection drive.
4. Open the folder and navigate to the location you would like to save the
software.
5. Download the file OSEE security.sh from SWS.
6. Copy the file OSEEsecurity.sh to the window that has the local drive location
from step 4.
A31003-S5190-J100-20-7631, 07/2017
osee_hardening.fm
OSEE Hardening
7. Close the windows that were opened on the Remote Desktop connection.
8. Power down the Windows Virtual Machine. Go to:

Start > Log Off > Shutdown
9. Close the Remote Desktop Connection.
10. Log on to OpenScape Voice, and shutdown the applications:

su - root
/etc/init.d/symphoniad stop
/unisphere/srx3000/srx/startup/srxctrl 2 0
Exit out of the connection.
11. On the vSphere client right click on OSV VM and select Power Off.
12. Make sure the ESXi host has SSH enabled.

Refer to Section 4.5, “Enable Remote SSH and ESXi Shell”.
13. On the workstation that you copied the OSEEsecurity.sh file onto, open an
SFTP connection to the ESXi host machine.
14. Copy the OSEEsecurity.sh file to the /tmp directory.
15. Close the SFTP connection.
16. Connect to the ESXi host machine via SSH and log on using the ESXi user
and password.
17. Change directory and modify permissions on script:

cd /tmp
chmod 744 OSEEsecurity.sh
18. Execute the OSEEsecurity.sh script to harden the ESXi and set the NTP
server information.
sh OSEEsecurity.sh –n "IP Address of Customer NTP server"
Example:
sh OSEEsecurity.sh –n 10.231.1.4
19. On the vSphere Client you will see that the connection is lost. Do NOT close
the window. In a few minutes you will get a Connection Failure warning pop-
up. Click Yes to login again.
Note: Make sure that you repeat the procedure described above for all VMs.
20. Log on to the ESXi host using the vSphere Client.
21. Power on the virtual machines in the following order:
A31003-S5190-J100-20-7631, 07/2017
osee_hardening.fm
OSEE Hardening
a) SBC VM
b) OSV VM
c) UC VM
d) WIN1 VM
e) WIN2 VM
A31003-S5190-J100-20-7631, 07/2017
osee_hardening.fm
OSEE Hardening
A31003-S5190-J100-20-7631, 07/2017
passwords.fm
Passwords
Passwords for OSV Server login
A Passwords
A.1 Passwords for OSV Server login

OpenScape Voice V9 default users and passwords are listed in the table below.
Type User Password

Console root T@R63dis
Console srx 2GwN!gb4
SSH sysad 1clENtk=
SSH superad BF0bpt@x
SFTP cdr MNY9$dta”
The "sysad" and "superad" users can be used to access the system via console
as well as via SSH.
Note: Please switch between users using su - <user>, i.e. su - srx, so that you
use the user profile.
OpenScape Voice subscribers for Digest Authentication:
• REALM= “WebCDC General & IP sheet next to Company Name”
• Username= “Directory Number Assigned”
• Password= “WebCDC General & IP sheet next to User Digest Password”
A.2 Passwords for OSV Apps Server login

CMP Access:
https://<IPaddress>:446/management/
– Username: administrator@system
– Password: Asd123!.
CMP-Next Access:
https://<IPaddress>:8085
– Username: operator
A31003-S5190-J100-20-7631, 07/2017
passwords.fm
Passwords
Password for Windows Server Login
UC Access:
– Username: root
– Password: T@R63dis
OpenScape Web Client Login:

https://<IPaddress>:8443/
<ipaddress> = OSV (refer to the WebCDC generated file “fqdn.cfg”
host.osv.OSEE.com)
– Username = “UC Login ID” (located on the WebCDC UC Data Sheet)
– Default password = Password1!
A.3 Password for Windows Server Login

All user account passwords (except for SvcCOPSSH) and applications installed
on the Windows Servers have the following default password:
Asd123!.
Note: Some applications may have components with different default passwords
assigned during install; in such cases, these default passwords are disclosed in
the document under their corresponding section.
The Administrator Password is set during bootup of the Windows VMs.
A.4 Passwords for OpenScape Deployment Service

https://<IPaddress>:10443/DeploymentService
– Username: admin
– Password: dls
A.5 Passwords for OpenScape Xpressions

OpenScape Xpressions Manager Login:
Click Start > All Programs > Xpressions > Monitor – System Logging
– User Name: ADMINISTRATOR
A31003-S5190-J100-20-7631, 07/2017
passwords.fm
Passwords
Passwords for OpenScape Contact Center
OpenScape Xpressions Web User Administrator Login:

https://<IPaddress>:28084/cgi_bin/webassistant/start
– User Name (or mailbox/ID number) = administrator
– Default password (or PIN) = Asd123!.
Note: Due to time passing from the time the Windows OVA is created to the
time it is deployed you may be prompted to change password at initial log on.
OpenScape Xpressions Web User Client Login:

https://<IPaddress>:28084/cgi_bin/webassistant/start
– User Name(or mailbox/ID number) = 11 digit phone number
– Default password (or PIN) = 000000
A.6 Passwords for OpenScape Contact Center

OpenScape Contact Center Manager Login:
Click Start > All Programs > OpenScape Contact Center Enterprise >
Manager
– User Name: master
– Password: password
OpenScape Contact Center Client Login:

– User ID: ‘First Name + Last Name’
Note: (refer to CDC_OSCC_Config.txt for all user IDs).
– Default password = password1
A.7 Passwords for Concierge

Concierge Manager Login:
– User Name: manager
– Password: manager
Concierge Login:
– User Name: user
– Password: user
A31003-S5190-J100-20-7631, 07/2017
passwords.fm
Passwords
Passwords for OpenScape Trace Manager
A.8 Passwords for OpenScape Trace Manager

• Username: Admin
• Password: Admin
Note: The first time you access Trace Manager, you will be prompted to set
up a new password.
A.9 Passwords for SBC-THIG

Signaling-Management Separated
https://<WAN interface Management IP address>/login.html
Signaling-Management Shared
https://<WAN interface Signaling IP address 1>/login.html
Credentials
• Username: service
• Password: BF0bpt@x
A31003-S5190-J100-20-7631, 07/2017
OSV-SA.fm
Survival Authority
B Survival Authority
For OSEE duplex solutions the default location for the Survival Authority (SA)
is the UC server. However in order to support hardware redundancy, the SA
should NOT be installed on the same hypervisor as the two OSV nodes.
Therefore it is strongly advised, especially for OSEE deployments with hardware

provided by Unify, that the SA is installed on a server with direct connection to the
OSEE internal LAN.
Survival Authority installation

Refer to Section 6.5.3 “Installing the Standalone Survival Authority” of
OpenScape Voice V9, Service Manual: Installation and Upgrades, Installation
Guide in e-doku.
Survival Authority configuration

1. Log in to CMP.
2. Navigate to Configuration > OpenScape Voice > Administration >
General Settings > EZIP
3. Type in the IP address of the Survival Authority server in the Survival
Authority IP field.
4. Click Save.
A31003-S5190-J100-20-7631, 07/2017
OSV-SA.fm
Survival Authority
A31003-S5190-J100-20-7631, 07/2017
win_vApp.fm
OSEE Windows vApp
C OSEE Windows vApp
Note: Make sure you have updated Windows.
1. Log in as Admin and execute the System Preparation Tool:
• Navigate to C:\Windows\System32\sysprep
• Double click on sysprep.exe
2. In the System Preparation Tool set the following:
• System Cleanup Action: Enter System Out-of-Box Experience (OOBE)
• Generalize: Checked
• Shutdown Options: Shutdown

and click OK.
Note: Wait time for Sysprep is approximately 5 minutes.
3. When Sysprep process finishes, Windows and the VM will shut down
automatically.
4. Using the vSphere Client select the VM.
5. Navigate to File > Export > Export OVF Template...
6. In the pop-up window set the following:
• Name: enter your desired name
• Directory: select the directory you want the OVA to be saved to
• Format: Single file (OVA)

and click OK.
Note: Wait time is approximately 2 hours.
7. Deploy the Windows OVA following the steps in Section 6.6.2, “Deploy the
Windows OVA template”.
8. Power on the Windows VM.
• Windows setup will be initiated
• When the setup is over the computer will restart.
9. After restarting you will be prompted to change password.
A31003-S5190-J100-20-7631, 07/2017
win_vApp.fm
OSEE Windows vApp
10. Once you log in as Admin the License Sticker key can be used to activate
the product.
11. Proceed to Section 6.6.3.4, “Update Windows Server” and install any
Windows updates available.
A31003-S5190-J100-20-7631, 07/2017
opt_redundancy.fm
Optional redundancy to cover total failure of the OSEE server
Overview
D Optional redundancy to cover total failure of the OSEE

server
D.1 Overview
In OpenScape Enterprise Express V9 a new redundancy option is introduced to
cover for VMs that are no longer able to run due to an OSEE server failure.
VMware's vSphere Replication will be used to provide the solution including the
configuration and management of the replication to a stand-by server (with ESXi)
and the creation of the protection copies of the VMs available for restoration
through the VMware vSphere Web Client.
VMware's vSphere Replication is provided as a no-charge component of all

eligible vSphere licenses, ranging from VMware vSphere Essentials Plus Kit to
VMware vSphere Enterprise Plus Edition. The customer bears all additional costs
including the VMware Licenses required and is responsible for obtaining and
installing the additional VMware vSphere components required (e.g. vSphere
Web Client, vCenter, vSphere Replication Server virtual appliances).
VMware's vSphere Replication is available as a virtual appliance that consists of:
• a vSphere Replication Management Server that provides replication

management
• a vSphere Replication Server that is in charge of performing actual data

transfer between source and destination
• an embedded database to store data and replication schedules
• and a plug-in for vSphere Web Client that provides management

capabilities for vSphere Replication within Web Client.
VMware's vSphere6.0 Replication can be managed only from vSphere 5.5 Web
Client that is connected to the 5.5 vCenter.
The additional server serves as a warm stand-by only (in the same L2 network).
The customer bears all additional costs including the additional server(s).
D.2 Preparation
Once the VMs are initially replicated by placing a "seed" copy of the VMs on the
additional server, vSphere Replication copies only those blocks that have
experienced unique writes during a Recovery Point Objective (RPO) to the target
location's vSphere Replication appliance (running on the additional server).
A31003-S5190-J100-20-7631, 07/2017
opt_redundancy.fm
Configuring Server Redundancy
The average Data change rate is estimated to be ~10% of 595 GB (59.5 GB) with
in the 18 hour RPO. The 18 hour RPO is expected to generate 0.007 Gbit/sec
traffic across the L2 NW between the servers (59.5*8/18/3600)
Note: The datastores must be named differently than the existing datastores
Note: Use the vSphere Web Client to add the additional server to the same
Datacenter as the server normally used for the production OSEE server.
D.3 Configuring Server Redundancy
D.3.1 vCenter Server OVF Template Deployment

Using the vSphere Web Client deploy the vCenter Server OVF Template on the
datastore on the additional server following the VMware documentation:
• Deploying the vCenter Server Appliance
Note: Deploy thin provisioned. The resulting vCenter Server disk size will be at
least 7 GB and can grow up to 80 GB according to the VMware documentation.
D.3.2 vSphere Replication Virtual Appliance

Deployment
Using the vSphere Web Client deploy the vSphere Replication virtual appliance
on the datastore on the additional server following the VMware documentation:
Note: Deploy thick provisioned. The resulting vSphere Replication Server has a
dual core CPU, a 10GB and a 2GB hard disk, and 4GB of RAM. You must deploy
the virtual appliance in a vCenter Server environment by using the OVF
deployment wizard on an ESXi host.
A31003-S5190-J100-20-7631, 07/2017
opt_redundancy.fm
D.3.3 vSphere Replication Configuration

VMware vSphere Replication shall be configured according to the VMware
documentation:
• VMware vSphere Replication
• Introduction to vSphere Replication
The OSV VMs shall be configured to be replicated to the datastore on the target
(additional) server.
The Windows VMs shall be configured to be replicated to the datastore on the

target (additional) server.
D.3.4 Testing
Test placing a "seed" copy of the VMs on the target server according to the
VMware vSphere Replication documentation:
• VMware vSphere Replication
• Introduction to vSphere Replication
Test Protecting all VMs, Recovering all VMs, & Checking Replication Status
following the VMware documentation.
A31003-S5190-J100-20-7631, 07/2017
opt_redundancy.fm
A31003-S5190-J100-20-7631, 07/2017
opt_config_concierge.fm
Optional configuration for OSCCE, Concierge
Associate multiple office codes to a tenant
E Optional configuration for OSCCE, Concierge
E.1 Associate multiple office codes to a tenant

A user is always assigned to a tenant and each tenant has an office code
(outbound access) associated. With WebCDC the office code of the headquarter
is assigned to the default tenant.
To use multiple office codes/sites you have to create user groups below the
tenant, associate an office code to the group and set the user group for each user.
You can find below the steps to be taken in order to associate multiple office
codes to a tenant:
1. Add additional trunks to the configuration:
a) Log in to System Management with the following credentials:

Username: systemmanager
Password: manager
b) On the left sidebar select PABX Connections under Resources and

then click on Modify.
c) On the new window "PABX Connection" that opens add Additional Local
Trunks using the button Add.
d) On the "Local Trunk" window that pops up fill in the Country Code, Area
Code and Trunk Code and click OK.
Note: Repeat this step for any additional office codes.
e) Close the "PABX Connection" window.
f) Navigate to Action > Publish Installation Data via the menu or by

clicking F5 in order to publish the installation data.
g) Exit System Management.
2. Add user group:
a) Log in to OSCDataCenter with the following credentials:

Username: manager
Password: manager
b) On the left sidebar navigate to User administration > Supergroup +

groups.
c) Click on the "plus" button on the bottom of the screen under the Edit
groups window.
A31003-S5190-J100-20-7631, 07/2017
opt_config_concierge.fm
Optional configuration for OSCCE, Concierge
Associate multiple office codes to a tenant
d) Enter a name for the group, check the "Has own configuration settings"
and then click on the "green check" button.
Note: Repeat this step for each site.
3. Assign office code to user group:
a) On the left sidebar navigate to System data > Client configuration.
b) On the top of the "Client configuration" screen select User Group and
select the group you want to modify from the drop down list. On the upper
right corner change the Display level to Advanced.
c) On the "Sections" list select Trunk Numbers and click on the Change
button. Select the code for this site/group and save the setting.
Note: Repeat this step for each user group.
4. Assign User Account to user group:
a) On the left sidebar navigate to User administration > Accounts, select

the user you want to change and click on the Change button.
b) Select the users group you want to assign to the user and click on Save.
Note: Repeat this step for each user account.
c) Close OpenScape Concierge DataCenter.
Now OpenScape Concierge is able to associate different office codes depending

on the user logged on.
A31003-S5190-J100-20-7631, 07/2017
XPR_db_back-up.fm
Optional XPR Database Backup
F Optional XPR Database Backup

1. Create a new folder on the Xpressions server and name it as you want.
Note: The folder can also be on a USB drive attached to the Xpressions
server.
2. Log on to Xpressions Web Assistant as administrator and access Server

settings > Smart Backup and Restore.
3. Schedule your backup as desired.
Note: For lifetime put the quantity of days that the backup will exist before it
is overwritten by another backup.
4. Check all items, if you do not have one on the Xpressions server it will just
provide a warning in the Xpressions monitor.
4. Click Save. You can back up now if you want to.
A31003-S5190-J100-20-7631, 07/2017
XPR_db_back-up.fm
Optional XPR Database Backup
A31003-S5190-J100-20-7631, 07/2017
CSBC.fm
C-SBC Installation
G C-SBC Installation
C-SBC enables OpenScape SIP-based communication and applications to be
securely extended beyond the boundaries of an enterprise network when
deployed in a centralized location (e.g. the customer’s Data Center).
C-SBC offers the option to be installed either in hardware provided by Unify or in

a virtual environment.
Depending on your configuration follow the procedure described in:
• Section 4.1 “Installation and Upgrades” for Hardware deployments or
• Section 4.2 “Virtualization - Overview” for Virtualized deployments
of OpenScape SBC V9, Installation Guide with the following important deviation:
In the USB Stick Setup screen select Already existing database file as
Installation Method and use the SBC_<hostname>_CDC.xml file which can be
found in the zip file generated by WebCDC.
Note: After you have extracted the contents of the zip file generated by WebCDC,
navigate to the following path in order to find the xml file:
OS_SBC/ob_config/<OSB Cluster Name>#@<BG Name>#@<Central SBC
hostname>/Configuration_data/
A31003-S5190-J100-20-7631, 07/2017
CSBC.fm
C-SBC Installation
A31003-S5190-J100-20-7631, 07/2017
DirectAccess.fm
Optional Direct Access to OSEE VMs
H Optional Direct Access to OSEE VMs
Warning: The procedure described in this section is not recommended by Unify.
In case direct access is needed to each VM of the OpenScape Enterprise

Express deployment, follow the steps below to redirect all traffic and assign a
separate IP address from the signaling network to each one of the VMs:
1. Log in to SBC-THIG.
2. Navigate to Network/Net Services > Settings.
3. Scroll down to the Access and Admin realm configuration area.
4. Click Add and set the following:
Type Network ID IP address Subnet mask Signaling Media
Non-VLAN IP osv-Access-IPv4 IP of your choice Same as the main IPv4 NOT selected
Non-VLAN IP uc-Access-IPv4 IP of your choice Same as the main IPv4 NOT selected
Non-VLAN IP win1-Access-IPv4 IP of your choice Same as the main IPv4 NOT selected
Non-VLAN IP win2-Access-IPv4 IP of your choice Same as the main IPv4 NOT selected
For duplex OSV deployments only:
Non-VLAN IP osv2-Access-IPv4 IP of your choice Same as the main IPv4 NOT selected
Note: Each VM should be assigned a different IP address.
5. Click OK.
6. Navigate to Security > Firewall.
7. Click Add.
8. Repeat the following steps for each Network ID you added in step 4:
a) Select a Network ID.
b) Deselect the Enable IP masquerading checkbox.
c) Select the Allow all network connections checkbox.
d) Change the SNMP and SSH options to Allow.
e) Click OK.
9. Highlight the row of osv-Access-IPv4 and click Edit.
a) Click on Configure next to the Enable port forwarding checkbox.
b) Click Add to add a new row.
A31003-S5190-J100-20-7631, 07/2017
DirectAccess.fm
c) Set the following:
Name Source IP Incoming port Destination IP Destination port Transport

OSV 0.0.0.0 0 10.82.53.229 0 All
d) Click OK > OK
10. Highlight the row of uc-Access-IPv4 and click Edit.

UC 0.0.0.0 0 10.82.53.233 0 All
d) Click OK > OK
11. Highlight the row of Win1-Access-IPv4 and click Edit.

Win1 0.0.0.0 0 10.82.53.241 0 All
d) Click OK > OK
12. Highlight the row of Win2-Access-IPv4 and click Edit.

Win2 0.0.0.0 0 10.82.53.249 0 All
d) Click OK > OK
A31003-S5190-J100-20-7631, 07/2017
DirectAccess.fm
13. For duplex OSV deployments only:

Highlight the row of osv2-Access-IPv4 and click Edit.

OSV2 0.0.0.0 0 10.82.53.230 0 All
a) Click OK > OK
14. Click OK to return to the main screen of SBC THIG Management Portal.
15. Click Apply Changes.
A31003-S5190-J100-20-7631, 07/2017
DirectAccess.fm
A31003-S5190-J100-20-7631, 07/2017
InsideEdge.fm
Softcom InsideEdge (OSCC Analytics)
I Softcom InsideEdge (OSCC Analytics)

This appendix will cover the installation and connection of Softcom InsideEdge
Life of Call as an external server that will reside outside of the OSEE LAN
network.
Make sure that OSCC is up and is listening to the correct port

1. Log in to Windows VM 1 and launch the Command Prompt.
2. Type the following:

netstat -an | findstr :9088
This command will check whether Contact Center is listening to port 9088 and
also list all active connections to this port.
• If the following output is displayed:

TCP 169.2.3.4:9088 0.0.0.0:0 LISTENING
then Contact Center is running on the XPR_Loopback network interface.

Proceed to step 3.
• If the displayed output is different, skip steps 3-10 and proceed with the
configuration of SBC-THIG.
3. Open the Control Panel and then navigate to Network Connections.
4. Right click on XPR_Loopback and select Disable.
5. Click Start, click in the Start Search box, type services.msc, and then press
ENTER.
6. Find the Informix IDS service, right click on it, and then select Restart.
Wait until the service has successfully restarted.
7. Go back to the Control Panel and open Network Connections.
8. Right click on XPR_Loopback and select Enable.
9. Launch the Command Prompt and type the following:

netstat -an | findstr :9088
The following output should be displayed:
TCP 10.82.53.241:9088 0.0.0.0:0 LISTENING
10. Proceed with the configuration of SBC-THIG.
Configure SBC-THIG
2. Navigate to Security > Firewall.
A31003-S5190-J100-20-7631, 07/2017
InsideEdge.fm
Softcom InsideEdge (OSCC Analytics)
3. Highlight the row with Network ID: Main by clicking on it and click Edit.
4. Click on Configure next to Enable port forwarding.
5. Click Add.
A new entry is created on the list.
6. Fill in the following:
• Name: LIFECYCLE
• Source IP/Logical-Endpoint-ID: <IP of InsideEdge Server>
• Incoming port: 0
• Destination IP/Logical-Endpoint-ID: 10.82.53.241
• Destination port: 9088
• Transport: All
Install InsideEdge Life of Call

During the installation of InsideEdge LoC, you will be prompted to enter the
Informix connection information for the Primary Server:
• OSCC Informix Server’s Network Name or IP Address: <SBC-THIG IP>
• Informix Server’s Port Number: 9088
• Informix Server’s Instance Name: ol_vm
• Informix User Name: informix
• Informix Server’s Password: Asd123!.
Note: The Server’s Instance Name, User Name and Password provided above,
are the default values. If changed, make sure that you use the new values.
A31003-S5190-J100-20-7631, 07/2017
CDSS.fm
Call Director SIP Service Installation
J Call Director SIP Service Installation

This appendix will cover the installation, configuration, and connection of OSCC
Call Director SIP Service as an external server to OSEE V9.
CDSS Installation
Follow the instructions in Section 2.2 “Installing the Call Director SIP Service
software” of OpenScape Contact Center Enterprise V9 Call Director SIP Service,
Installation Guide to install Call Director SIP Service as an external server.
CMP Configuration
1. Log in to CMP.
2. Navigate to Configuration > OpenScape Voice > Business Group >

Members > Subscribers.
3. Click Add... to create a new SIP Subscriber.

This subscriber has to be configured for dynamic registration. It will become
registered once the configuration of CDSS is complete.
• Under the Connection tab set the following:
– Type: Dynamic
– Transport Protocol: UDP
• Under the Features tab:
a) Click on the Click to select Features button.
b) From the dropdown list select Call Forwarding No Reply, Call
Transfer, CSTA Access, and Malicious Call Trace and then click
Add.
c) In the list below click on Call Forwarding No Reply.
d) Select the Activate checkbox and click OK.
e) Back in the list set the following:
Name Assignment
Call Forwarding No Reply Assigned
Call Transfer Assigned
CSTA Access Assigned
Malicious Call Trace Switch-wide
f) Click on Save.
4. Additionally for OSB CAC support and in general to avoid divert failures, the
Call Director extensions should be configured as members of a Hunt Group
of manual type. The Hunt Group must be dedicated to this purpose and
separate from the pair of Initial and Music On Hold Hunt Groups to which the
user subscriber numbers belong.
To create a new Hunt Group, navigate to Configuration > OpenScape Voice
> Teams > Hunt Groups and click on Add...
A31003-S5190-J100-20-7631, 07/2017
CDSS.fm
CDSS Configuration
Follow the instructions in Chapter 3 “Configuring the Call Director SIP Service” of
OpenScape Contact Center Enterprise V9 Call Director SIP Service, Installation
Guide to configure Call Director SIP Service. The following exceptions apply:
• In Section 3.3.4 “Configuring the communication platform settings” use the

following values:
– SIP Server: <IP of SBC-THIG>
– Registrar Host: <IP of SBC-THIG>
– RTP Start Port: 38000
– Transport Type: UDP
• Ignore the instructions in Section 3.3.5 “Configuring the SIP timers” and
proceed to Section 3.3.6 “Configuring the ports”.
• Follow the instructions up to and including Section 3.3.6.1 “Configuring the

extensions”.
OSCC Configuration
1. Log in to OpenScape Contact Center Manager.
2. Navigate to Tools > Options.
3. Under the System Settings area select Voice.
4. Switch to the Features tab and enable the Call Director checkbox.
5. Click Apply.
6. Follow the instructions in Section 12.3 “Configuring the Call Director

resources” of OpenScape Contact Center Enterprise V9, Manager
Administration Guide.
7. In OpenScape Contact Center Manager switch to Telephony Center.
8. Navigate to Resources > Subscriber Numbers > Call Directory.
9. Right click on the main area and select New.
10. In the pop-up window, give a name of your choice and fill in the From and To
fields with the range of the extension numbers you want to add.
11. Click OK.
12. Exit OpenScape Contact Center Manager.
13. Restart OpenScape Contact Center:
A31003-S5190-J100-20-7631, 07/2017
CDSS.fm
a) Open Server Manager and click on Tools > Services and stop the
OpenScape Contact Center service:
Right click > Stop
b) Wait a few minutes for the service to stop:

Make sure that all servers have stopped in the OpenScape Contact
Center Server status window.
c) In the Services window start the OpenScape Contact Center service:

Right click > Start
Note: The startup process may take a few minutes.
d) Make sure that Call Director Server is listed under the OpenScape
Contact Center Server status window.
A31003-S5190-J100-20-7631, 07/2017
CDSS.fm
A31003-S5190-J100-20-7631, 07/2017
DNS.fm
Optional DNS info update
K Optional DNS info update

All DNS related information are listed in the fqdn.cfg file that is located under the
/etc/hiq8000/ directory of OSV. The steps below will guide you through the
process of editing this file.
Attention: fqdn.cfg is a proprietary file and all changes must be made with
caution.
Note: In case a cluster is deployed, it is strongly advised to perform the update

procedure on the 2nd node (the slave DNS) as well. The updated FQDNs will be
copied from node1 (master) via zone transferring; but problems may arise if
node2 has an outdated fqdn.cfg file.
WebCDC Delta generation - configuration files

• In case a new site has been added to your project, you can use WebCDC
Delta generated configuration files to replace the existing fqdn.cfg.
1. Log in to OSV as root.

2. Copy the deltaFqdn_setup.sh file to OSV using an FTP client.
3. Change the access permissions of the file:
chmod +x deltaFqdn_setup.sh
4. Execute the script:
./deltaFqdn_setup.sh
• In case one or multiple new endpoints are introduced when using the Delta
generation mode, WebCDC produces the SBC THIG xml file with all solution
remote endpoint entries (i.e. Staged + Delta).
If no additional manual edits have been performed to SBC THIG, the
aforementioned xml file can be used. Otherwise, please refer to OpenScape
SBC V9, Configuration Guide, Administrator Documentation and proceed
with the manual steps in order to add all new Remote Endpoints along with
their Media Server configuration to SBC THIG.
Manual edit of fqdn.cfg
Warning: The procedure described in this section is not recommended by Unify.
In case manual editing of fqdn.cfg is required, the vi editor can be used to add
the new A and/or SRV records in the corresponding sections.
A31003-S5190-J100-20-7631, 07/2017
DNS.fm
Optional DNS info update
1. Log in to OSV as root.
2. Execute the following commands:

cd /etc/hiq8000
vi fqdn.cfg
Edit the file using the following formats:
• For new FQDN entries:

A <hostname>.<solution domain name> externalIPAddr internalIPAddr
or
B <hostname>.<solution domain name> externalIPAddr internalIPAddr
where:
– you set:
> B in case there is an addition of a slave DNS server (e.g. OSB)
> A for all other cases (FQDN records)
– externalIPAddr is the IP that is used by nodes outside the OSEE LAN.

Usually it would be the external IP of the THIG Virtual Machine (it can be
found in WebCDC under IP Tab).
– internalIPAddr it is the IP of an internal virtual machine. It is required only for

VM that resides inside the OSEE LAN
• For new SRV records(proprietary):

<SRVhostname>.<solution domain name> <first FQDN> <priority>
<weight> <port> <second FQDN> <priority> <weight> <port>
where:
– SRVhostname has the following options:

_sip._tcp
_sips._tcp
_sips._tcp.mtls
– priority is he relative Priority of this service
– weight defines the relative frequency of the Target use when two or more
services have the same priority.
3. Execute the following command in OSV:

/unisphere/srx3000/callp/bin/buildDNSconfig
A31003-S5190-J100-20-7631, 07/2017
Accounting.fm
OpenScape Accounting V2 Configuration
L OpenScape Accounting V2 Configuration

Requirements
• OpenScape Accounting V2 should be installed outside the OSEE LAN
• OpenScape Accounting V2 should be connected to CMP using ports 443,

4709 and OSV over SFTP using port 22
Note: In case a cluster is deployed, OpenScape Accounting V2 should

connect to both OSV nodes using port 22.
Step by step
1. Create an SSL certificate on OpenScape Accounting V2 Server.
Note: This certificate must not be based on localhost, but on OpenScape

Accounting V2 Server’s IP address.
This requires a connection to OpenScape Accounting V2 Server through

RDP. For instructions, refer to Section 3.14.2 “Generation of SSL Certificates”
of OpenScape Accounting V2, Installation and Configuration, Installation
Guide.
2. Since the OpenScape Accounting V2 Server requires ports 443 and 4709 to
be forwarded to CMP, a new virtual IP address needs to be created on the
SBC WAN Interface.
The additional IP address can be created using WebCDC by selecting the
option Signaling-Management Separated in the Wan Subnet Sharing field
under the IP tab.
Alternatively, you may follow the steps below:
a) Log in to SBC-THIG.
b) Navigate to Network/Net Services > Settings.
c) Scroll down to the Access and Admin realm configuration area.
d) Click Add and set the following:
Non-VLAN IP uc-Access-IPv4 IP of your choice Same as the main IPv4 NOT selected
e) Click OK.
f) Navigate to Security > Firewall and click Add.
1. Select the UC Network ID.
2. Deselect the Enable IP masquerading checkbox.
A31003-S5190-J100-20-7631, 07/2017
Accounting.fm
3. Select the Allow all network connections checkbox.
4. Change the SNMP and SSH options to Allow.
5. Click OK.
g) Highlight the row of uc-Access-IPv4 and click Edit.
1. Click on Configure next to the Enable port forwarding checkbox.
2. Click Add to add a new row.
3. Set the following:
Acc_1 0.0.0.0 443 10.82.53.233 443 All
Acc_2 0.0.0.0 4709 10.82.53.233 4709 All
4. Click OK
5. Set the HTTPS field to Allow and click OK.
h) Click OK to return to the main screen of SBC THIG Management Portal.
i) Click Apply Changes.
3. Configure the OpenScape Accounting Scheduler Service as described in

Chapter 8 “OpenScape Accounting Scheduler Service” of OpenScape
Accounting V2, Installation and Configuration, Installation Guide
Attention: Use the WAN IP address of SBC THIG and the port 451 as the
address of the Target Host and Port respectively.
In case of a cluster, a secondary entry is necessary, which also uses the WAN
IP of SBC THIG, but the port is 452 this time.
4. Log in to CMP and perform the following actions:
a) Navigate to Maintenance > Inventory > Applications.
b) Find the OpenScape Accounting entry and click on the arrow displayed
in the far right of the entry. Then select Create Connection.
c) In the displayed window set the following:
Configure Connection - OpenScape Accounting
Connection
IP Address/Hostname <IP address of OpenScape Acounting Server>
Port 443
CMP
IP Address/Hostname <Secondary WAN IP of SBC THIG>
Port 4709
OpenScape Accounting
A31003-S5190-J100-20-7631, 07/2017
Accounting.fm
Configure Connection - OpenScape Accounting
Username
<Username and password for OpenScape Accounting>
Password
d) Click Save.
A31003-S5190-J100-20-7631, 07/2017
Accounting.fm
A31003-S5190-J100-20-7631, 07/2017
opt_ext_concierge.fm
Optional installation of an external OSCC-E server
SBC THIG configuration
M Optional installation of an external OSCC-E server

Follow the instructions provided in OpenScape Contact Center Extensions V3,
Server, Installation Guide to deploy OSCC-E outside OSEE LAN. After
successfully installing the server, proceed with the following sections, in order to
connect the external OSCC-E server with OSEE:
• SBC THIG configuration
• OpenScape Voice configuration
M.1 SBC THIG configuration

In order for the external OSCC-E server to successfully connect with OSEE, a
new firewall rule should be created in SBC THIG.
1. Log in to SBC-THIG.
2. Navigate to Network/Net Services > Settings.
3. Scroll down to the Access and Admin realm configuration area.
4. Click Add and set the following:
Non-VLAN IP oscce-Access-IPv4 IP of your choice Same as the main IPv4 NOT selected
5. Click OK.
6. Navigate to Security > Firewall and click Add.
a) Select the Accounting Network ID.
b) Deselect the Enable IP masquerading checkbox.
c) Select the Allow all network connections checkbox.
d) Change the SNMP and SSH options to Allow.
e) Click OK.
7. Highlight the row of oscce-Access-IPv4 and click Edit.
ext_oscce 0.0.0.0 1040 10.82.53.231 1040 TCP
d) Click OK
A31003-S5190-J100-20-7631, 07/2017
opt_ext_concierge.fm
Optional installation of an external OSCC-E server
OpenScape Voice configuration
8. Click OK to return to the main screen of SBC THIG Management Portal.
9. Click Apply Changes.
M.2 OpenScape Voice configuration

1. Log in to CMP.
2. Navigate to Configuration > OpenScape Voice.
3. On the side menu, click on Administration > Signaling Management >

CSTA.
4. In the pop-up window switch to the Applications tab, and click on Add...
5. In the next pop-up window set the following:
• Application Name (e.g. Concierge_External)
• Application IP Address (e.g. 10.5.33.70)
6. Click on Save and again Save.

You have now successfully added a CSTA firewall rule in OpenScape Voice
for your external OSCC-E Server.
A31003-S5190-J100-20-7631, 07/2017
emergency_calling.fm
Emergency Calling capability
N Emergency Calling capability

To enable the built-in Emergency Call capability, each BG (Business Group) is
equiped with an Emergency Calling table that is provisioned using OpenScape
Voice Assistant.
The maximum number of entries in the Emergency Calling table is 6000 per BG.
For more information, refer to Section 3.9.4 "Emergency Calling Table" of

OpenScape Voice V9, Administrator Documentation.
Every Emergency Calling table entry in an OSEE deployment can be defined by:
• Department or
• a valid Location Domain or
• a combination of the above or
• IPV4/6 Address/Subnet bound with a Location Domain

This last option requires the IP Address to be configured in SBC-THIG
Management Portal under the Remote subscriber configuration area with a
Location Domain Name assinged to it. For more information, refer to Section
5.5.1.1 "Remote Subscriber Configuration" of OpenScape SBC V9,
Administrator Documentation.
Additionally this same Location Domain Name needs to be configured in
CMP. For details refer to Section 3.9.4 "Emergency Calling Table" of
OpenScape Voice V9, Administrator Documentation.
A31003-S5190-J100-20-7631, 07/2017
emergency_calling.fm
Emergency Calling capability
A31003-S5190-J100-20-7631, 07/2017
collocated_osee.fm
Collocated OSEE deployments
O Collocated OSEE deployments

In case multiple OSEE deployments reside in the same virualized environment,
the following limitations apply:
• Each OSEE deployment must have its own set of datastores.
• Datastore names must be unique.
• VM names must be unique.
• Each OSEE deployment:
– must either use a unique vSwitch.
– or share the same vSwitch with other OSEE deployments, but have a
unique VLAN ID set.
Note: This VLAN ID is only used inside the vCenter network.
In the following example we have 2 collocated OSEE deployments called OSEE

Athens and OSEE Berlin respectively:
OSEE Athens OSEE Berlin

VMs osee_v9_osv_Athens osee_v9_osv_Berlin
osee_v9_sbc_thig_Athens osee_v9_sbc_thig_Berlin
osee_v9_uc_Athens osee_v9_uc_Berlin
osee_v9_win_1_Athens osee_v9_win_1_Berlin
osee_v9_win_2_Athens osee_v9_win_2_Berlin
Datastores OSEEOSV_Athens OSEEOSV_Berlin

OSEEWIN_Athens OSEEWIN_Berlin
vSwitch OSEELAN_Athens OSEELAN_Berlin
Note: The OSEEWAN network can be the same for all collocated deployments.
A31003-S5190-J100-20-7631, 07/2017
collocated_osee.fm
Collocated OSEE deployments
A31003-S5190-J100-20-7631, 07/2017
XPR_resources.fm
Optional configuration to enable XPR Resource Type for User Templates in CMP User Management
P Optional configuration to enable XPR Resource Type for

User Templates in CMP User Management
The primary goal of User Templates is to minimize administrator’s efforts related
to the creation and assignment of UM Users and Resources. However, XPR
Resource Type is not enabled by default. Follow the steps below to enable XPR
Resource Type in CMP:
1. Login to CMP.
2. Navigate to Maintenance > Inventory > Nodes.
3. Click Add OSC Xpressions.
4. Fill in the following values:
• Name: Set the name of your choice
• Node IP: xpr.<domain from WebCDC>
• SNMP Com. String : public
• Port : 161
• EM SDK Port : 4444
5. Click Save and close any open windows in CMP.
A31003-S5190-J100-20-7631, 07/2017
XPR_resources.fm
Optional configuration to enable XPR Resource Type for User Templates in CMP User Management
A31003-S5190-J100-20-7631, 07/2017
CSTA_third_partyy.fm
Optional Steps to add an external third party CSTA Application
Q Optional Steps to add an external third party CSTA

Application
Follow the steps below to add an external third party CSTA Application to OSEE:
1. Login to CMP
2. Navigate to Configuration > OSV Administration > Signalling

Management > CSTA
3. A pop up window "CSTA settings" should be displayed
4. Select the Application tab
5. Click on the Add button
6. In the field "Application Name" enter the name of the CSTA application
7. For the field "Application Type" select "3rd party" in the drop down menu
8. In the field "Application IP Address" enter the ip address of the CSTA

application
9. Click on the save button.
A31003-S5190-J100-20-7631, 07/2017
CSTA_third_partyy.fm
Optional Steps to add an external third party CSTA Application
A31003-S5190-J100-20-7631, 07/2017

OpenScape Enterprise Express V9, Staging Guide, Installation Guide, Issue 20.

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

OpenScape Enterprise Express V9, Staging Guide, Installation Guide, Issue 20.

Hochgeladen von

Copyright:

Verfügbare Formate

OpenScape Enterprise Express V9

1 OpenScape Enterprise Express V9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

6.1.1 OSEE Designated networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

M.2 OpenScape Voice configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Issue Date Description

Section 4.1, “Configuring VMware ESXi”, update some steps

1 OpenScape Enterprise Express V9

1.1 OpenScape Enterprise Express V9 Installation Checklist

2 Installing the Hardware Platform

2.1 Inventory & Installation Materials

2.1.1 Dell PowerEdge R630

2. Check for shipping damage or any shortages and discrepancies of materials.

3. Return and reorder damaged or missing material according to local

2.2 Printed Installation Guides and Digital Media

• Dell PowerEdge R630 server printed guides and digital media

• Ethernet switch documentation

• KVM (if so equipped) documentation

• Power distribution unit (PDU) or uninterruptible power supply (UPS)

You might need to reference these documents/media for installation procedures,

2.3 Cable Connections to Dell PowerEdge R630

Item Indicator, button, Description

1. Connect the following items to the server:

Note: The server requires a USB keyboard and mouse.

2. Attach the Ethernet cables:

• to the iDRAC8 port for the management platform to remotely monitor,

• to Ethernet port 1 (VMNIC0) for ESXi Management Network.

• to Ethernet port 2 (VMNIC1) and port 3 (VMNIC2) for OSEEWAN.

• to Ethernet port 4 (VMNIC3) and port 5 (VMNIC4) for OSEELAN.

2.4 RAID Configuration

2. Go to System Setup -> Advanced hardware configuration

3. Select Device Settings -> Integrated RAID controller 1

4. Under Configuration Management select Clear configuration

5. Confirm checkbox and select Yes and then OK

6. Select Back and then Configuration Management

7. Select Create Virtual Disk

8. For RAID level select RAID1

9. Then select Physical Disks

10. Select the first 2 available disks and click Next.

11. Select Apply Changes and then OK

12. Set virtual disk name OSEELINUX

13. Select Create Virtual Disks

14. Confirm checkbox and select Yes and then OK

15. Select Physical Disks

16. Select the last 2 available disks and Apply Changes

18. .Set virtual disk name OSEEWIN

19. Select Create Virtual Disks

20. Confirm checkbox and select Yes and then OK

23. Proceed to Section 2.5, “Modifying the Server UEFI Settings”.

2.5 Modifying the Server UEFI Settings

27. Set the System Time and System Date.

28. Click Back.

30. Click on BIOS Boot Settings and then on Boot Sequence.

31. Click OK and then select the Hard-Disk Drive Sequence.

32. Click OK.

33. Click Finish and then Yes.

34. Proceed to Section 2.6, “iDRAC Configuration”.

2.6 iDRAC Configuration

36. Click on Network.

37. Verify that the Enable NIC option is Enabled.

38. Scroll down to the IPV4 SETTINGS category.

• Static Subnet Mask

39. Click Back and scroll down to User Configuration.

• LAN User Privilege: Administrator

• Serial Port User Privilege: Administrator