Mod02 GL OS4TSEPSDT CD2673EN00CD

6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
Unify and the Unify Academy are pleased to present the Unify Certified Technical Sales Expert for
C
OpenScape 4000 Course.

00
E N
73
26
D
C
DD3683FN10DD_BACZZZJHDI
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
The course comprises the following content:

C
00
• Unify Technical Sales Specialist Review,

E N
• OpenScape Cordless Enterprise,

73
• System Networking,
26
• OpenScape 4000 Redundancy and

D
C
• Special Features and security.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
• We will also look at OpenScape UC Redundancy,

C
• OpenScape UC Communications Enabled Business Processes and

00
• Virtualization
NE
73
26
D
C
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
We will start with a review of the Certified OpenScape 4000 Technical Sales Specialist course.
C
00
E N
73
26
D
C
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
Unify Technical Sales Specialist Review (1)

C
00
In the Unify Technical Sales Specialist course you have become acquainted with the OpenScape
E N
4000 system architecture and gained a deep insight into the world of boards.
73
26
D
C
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
Unify Technical Sales Specialist Review (2): Here is a summary of the OpenScape 4000 system
C
architecture:
00
E N
OpenScape 4000 is the PBX of the next generation. It offers three different provisioning options and,
73
together with OpenScape UC, forms an Enterprise Unified Communications server.

26
D
OpenScape 4000 Communication Server option (EcoServer) supports convergent IP requirements,

C
including applications with a high analog share, DECT applications or special industry applications,
and has been designed for centralized provisioning.
The provision of OpenScape 4000 on standard servers equipped with Linux is ideal for the
requirements of convergent IP telephony and for distributed environments.
In this provisioning version, SoftGate (simplex only) can also be added on the same server.
The provision of OpenScape 4000 SW on a VMware® infrastructure is ideal for use in data centers.
This is also possible together with virtualized OpenScape UC and Unified Messaging. The virtual
solution provides the same high scalability as on cPCI hardware or the EcoServer.
The OpenScape 4000 Real Time IP communication solution consists of a central Call Control
installed on the OpenScape 4000 Communication Server (EcoServer) or a VMware®, and various
access points, OpenScape 4000 SoftGate server or OpenScape Access components for the flexible
connection of all end devices, network accesses and special solutions.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D

C
00
Furthermore you have been introduced to the system and subscriber features and been acquainted
E N
with the different components of the OpenScape 4000 IPDA infrastructure.

73
26
D
C
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
Unify Technical Sales Specialist Review 4: OpenScape 4000 – IP Distributed Architecture, abbreviated as
C
(IPDA):
00
• The IP Distributed Architecture, also known as IPDA, with IP access points, OpenScape Access Modules
N
and OpenScape SoftGate allows the connection of branches via a cost-effective IP infrastructure and ,at
E
the same time, provides benefits from central applications such as OpenScape UC, OpenScape Contact
73
Center and centralized management.

26
• The subscribers at the access points behave like subscribers that are directly connected to
D
OpenScape 4000.
C
• Thus, switching of payload channels (B-channels) is no longer limited to the central switching matrix
(host) since
– Calls within an IP access point can be switched without a delay in the local switching matrix of the IPDA
or OSA500 and SoftGate.
– Calls can be routed between IP access points in the IP network, and
– Calls that are not restricted to IP access points are routed in the IP network as well as in
OpenScape 4000.
• Up to 83 IP access points can be deployed in a single OpenScape 4000 simplex system.
• OpenScape 4000 supports many external applications such as OpenScape Contact Center, OpenScape
Xpressions etc. Over open interfaces such as CSTA, OpenScape 4000 supports attendant console
connectivity, third party CTI products and much more.
• In this course you will become familiar with additional special features and be introduced to the
redundancy options.
• OpenScape 4000 networking will be then covered as the final point.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D

C
00
In the OpenScape UC section you became acquainted with the software architecture and the
E N
deployment scenarios.
73
26
They are the Integrated Deployment for 1250 UC users, the Small Deployment for up to 2500 users,
D
the Large Deployment for up to 15000 users and the Very Large Deployment with the expansion
C
states for up to 200000 subscribers in networked scenarios.
A wide choice of modern clients is available for users.
The open SOA architecture enables specific integration of the OpenScape UC system at the
customer’s premises.
In this course you will become familiar with the redundancy options of OpenScape UC and gain
insight into the Communication Enabled Business Process virtualization capabilities of OpenScape
UC.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
The next Chapter comprises OpenScape Cordless Enterprise.

C
00
E N
73
26
D
C
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
OpenScape Cordless Enterprise is the integrated radio switching module for OpenScape 4000.
C
00
The radio technology in OpenScape Cordless Enterprise is in accordance with the DECT standard
E N
(Digital Enhanced Cordless Telecommunications).

73
26
DECT always operates in a connection- oriented manner and is primarily designed for what is known
D
as pico-cellular telephony within buildings with a range or cell radius of 30 to 50 meters and in the
C
open, transmission distances of up to 300 meters are possible.

The base stations implement the transition from the cable-linked network to the radio net-work. The
maximum permissible output power from a base station is 250 milliwatt.
Using special antennas, the radio coverage can be adjusted to meet the needs of large open areas or
difficult radio environments within metal structures.
Outdoor housings for base stations allow their use outdoors.
The base stations are connected to between 1 and 3 UP0/E ports on the SLC24 board.
A maximum of 48 SLC24 boards in each shelf are possible.
OpenScape Cordless E V7 supports SLC24 boards exclusively and a maximum 16 base stations can
be connected to each SLC24 board are connectable.
Furthermore up to 3 Up0E, there is a maximum of 12 calls per base station using the protocol
CorNet-T Radio.
The system does Roaming and Handover, which are being discussed later in this course.
Different types of Unify DECT telephones for industry and office environments can be used known as
OpenStage DECT handsets based on the GAP standard.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
Gigaset S4 professional
C
The Gigaset S4 professional is an elegant DECT cordless telephone with outstanding features. It
00
impresses through its high-quality equipment with silver-colored keypad and a large 1.8" FT color
N
display and optimal user prompting. The scope of service is comparable to corded system terminals.
E
73
OpenStage SL4 professional

26
OpenStage SL4 professional is the smallest and lightest DECT mobile phone in the portfolio. With its
D
high end functions and design, it meets the most stringent requirements and is the perfect device for
C
many workstations.
The scope of service is comparable to corded system terminals as well.
OpenStage M3
The OpenStage M3 DECT handsets are a family of devices designed to perform in harsh
environments.
This family comes with variants covering different alarm options and also use in potentially explosive
environments where moisture, dirt, shocks, dust, or high ambient noises degrade communication
quality. With its device protection class of IP65 they are ideally suited for these environments.
The OpenStage M3 is ideal for industrial environments or vertical industries, including:
• Docks/airports
• Hospitals
• Shipping and logistics companies
• The OpenStage M3 Ex variants are ideal for potentially harsh and explosive environments, such as
oil, gas, and chemical production, as well as other gas and dust-filled environments.
• The advanced alarm options connect personnel in security-critical areas where heightened
supervision is needed, i. e. law enforcement, forensic institutions,
power plants and industrial scenarios.
OpenScape DECT Phone S5

These are reliable, high-quality DECT cordless devices for telephoning professionally.
They are large and robust enough to deal with tough conditions.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
Networked systems have network-wide roaming and handover within a node Up to 64 OpenScape
C
4000 nodes with HiPath Cordless E V3.0 elements and OpenScape 4000 with OpenScape Cordless
00
E V7 elements can be networked to form a joint DECT system.

E N
73
This DECT system supports a maximum of 511 SLC24 boards and 48641 mobile subscribers. Of
these, up to 383 SLC 24 boards can be operated as home boards. Up to 127 subscribers can be
26
administered on one SLC24 board.

D
C
This results in a total of 12264 UP0/E ports.
With respect to one-channel base stations, a total of 8176 can be connected.

Automatic roaming between the base stations of different nodes is possible within this system.
It can be enabled by networking the systems via CorNet-NQ. Handover between the base stations of
a node (including transitional nodes) is possible too.
With the Inter Systemr Synchronisation (ISS) feature, connection handover is also possible between
nodes in a DECT system.
Inter System Synchronization (ISS) is used to synchronize different OpenScape nodes. The
foundation for this is the Global Positioning System (GPS) which provides a single time base within
an OpenScape network and consists of a GPS receiver (GPS170MP) and an antenna.
Project planning for OpenScape Cordless Enterprise must include an assessment of the radio
coverage with the "OpenScape Cordless HCS DECT Service Tool”.
This is the only way to ensure optimum technical positioning of the base stations as well as cost-
effective coverage of the customer-specific radio range.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
Due to the full integration into the highly scalable OpenScape 4000 System, the OpenScape Cordless
C
profits from the flexible branch solutions of that system and can be aligned to the customer´s needs.
00
AP3700IP (IPDA) and OpenScape Access are well known. Up until Cordless V7 it is possible to use
N
the OpenScape 4000 SoftGate, where a virtual SLC (vSLC) can be installed and offers the customer
E
some new options.

73
26
As of OpenScape 4000 V7, the OpenScape 4000 SoftGate supports the Cordless Multicell Integration
D
(CMI) DECT functionality. This means that in addition to HFA and SIP subscribers, cordless DECT
C
subscribers can also be configured in an OpenScape 4000 SoftGate.
Project planning for OpenScape Cordless Enterprise must include an assessment of the radio
coverage with the "OpenScape Cordless HCS DECT Service Tool”.
This is the only way to ensure optimum technical positioning of the base stations as well as cost-
effective coverage of the customer-specific radio range.
Administration is done via CATool.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
The following Main Features are supported by OpenScape Cordless Enterprise:

C
00
• Voice encryption
E N
• Blocking/unblocking DECT frequencies

73
• Automatic compensation of signal delay to base stations

26
• Improved user interface with dual-mode softkeys

D
C
• Support for the OpenScape Display Telephone Book (DTB)

• Message Waiting Indication (MWI) for the mailbox and display of missed calls
• in the missed calls list or in the DTB call journal
• Network-wide roaming without full intermeshing
• Network-wide handover by means of ISS "Inter System Synchronization”
• Support of Easy Services such as easy Unified Communications
• Support for the Cyrillic character set
• OpenScape UC ONS Functionality
• Enhanced Security due to Re-keying
• Availability of the Virtual SLC and
• Eco DECT Functionality.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
Now we want to explain OpenScape 4000 – OpenScape Cordless- the solution concept.
C
00
Realization of the Cordless E system in OpenScape 4000 consists of the SLC24 / SLC
E N
(OSA500&Softgate) / vSLC (OSA500&Softgate) module, base stations (BS3/3, BS4) and mobile
73
phones.
26
D
The SLC is a module that can be plugged in at an LTU position as a Subscriber Line Module (SLM),
C
or connected in OpenScape Access 500 / Softgate over X link. Base stations are connected to the
SLC24 UP0 E outputs, currently except for vSLC.
A basestation has one, two or three interfaces. The interfaces are ADPCM-coded, which means that
calls are transmitted with 32 kbit/s.
The advantage of the ADPCM now lies in 4 voice channels per UP0 E.
It is the task of the SLC to transliterate the time slots of 32 kbit/s to 64 kbit/s, and vice versa. The
base stations create an area of radio coverage in which the subscriber may move freely with his or
her mobile phone.
Signaling between the SLC and the base stations is carried out according to the Cornet T Radio
protocol as mentioned before.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
Now we will explain roaming:

C
00
Moving in a cellular radio area is called roaming. Roaming means that the mobile user is reachable
E N
throughout the entire radio network area. Consequently, it is irrelevant to which SLC the base station
73
that is being used belongs. Incoming and outgoing calls are possible at any time. Roaming caters for
two different cases:
26
D
C
Roaming 1: The subscriber moves within the radio net of a Cordless E and changes cells. He may be
reached under the same extension number in each cell.
Roaming 2: The subscriber changes from Cordless E to another DECT system, e.g. to a Gigaset
base station. The advantage is that he uses only one mobile telephone for different DECT systems.
With the Cordless E mobile telephone, the subscriber may roam between four different systems. If the
mobile telephone is adjusted correctly, it automatically changes the DECT system.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
How does handover work?

C
00
Handover is the change of the radio channel during a call. At the same time, all the tasks required are
E N
automatically completed by the mobile telephone, the basestation and the SLC.
73
The user is not aware that a handover has taken place (Seamless Handover). In the DECT standard,
26
a handover is always initiated by the mobile telephone.

D
The mobile telephone measures the power of the base station and the quality of transmission during
C
a call.
Should the parameters change and thereby endanger secure transmission, the change is initiated. In
all handover cases, a second connection up to the new radio channel is added, in addition to the
existing connection.
Once this second connection is established, the mobile telephone needs only to switch over.
Thereafter, the old connection is discontinued.
Essentially, there are 3 types of handover:

1: Intracell Handover
2: Intercell Handover to the same SLC
3: Intercell Handover to another SLC
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
Here are some tips for OpenScape 4000 – OpenScape Cordless Enterprise- distribution of base
C
stations
00
E N
When distributing the basestations at the SLC24, attention should be paid that they cover the largest
73
possible related areas that belong to the same SLC.

26
D
If the cells are poorly distributed on the SLC, then Location Updates are needed more often and
C
extended connections are required more frequently.

The system dynamics worsen.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
Now we speak about OpenScape Cordless Description of virtual Subscriber Line Cordless:
C
00
In order to use the “OpenScape Cordless Enterprise Integration" feature, a software-based "virtual
E N
Subscriber Line Cordless" (vSLC) connector unit must be configured in the OpenScape 4000
73
SoftGate.
26
D
This means that besides HFA and SIP subscribers DECT cordless subscribers can also be
C
configured in an OpenScape 4000 SoftGate.
As with the SLC24 line cards, the vSLC provides the option of generating up to 127 cordless
handsets.
The vSLC operates as a virtual home SLC for all subscribers administered.
The visit SLCs together with the DECT base stations form the location areas at the site.
At the moment it is not possible to connect base stations to the vSLC.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
The number of CMI subscribers in the OpenScape 4000 SoftGate can be increased by adding on
C
other vSLC applications.

00
E N
Up to six vSLC applications with a maximum of 400 handsets (0.15 ERL per handset) can be
73
configured in a OpenScape 4000 SoftGate.

26
D
Base stations cannot be connected to the vSLC.

C
If subscribers are not in the location area of their home SLC (this always applies with vSLC), a data
exchange must be performed between the home and visit SLC in order to fulfill the mobility concept.
A prolonging connection is set up for this purpose.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
Let us now explain OpenScape 4000 Cordless Enterprise Redundancy:

C
00
If an OpenScape 4000 SoftGate V7 is operated in a VMware environment, then the customer has the
E N
opportunity of operating the entire Cordless E V7 in redundant mode.

73
26
D
C
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
OpenScape Cordless Enterprise V7 together with OpenScape 4000 SoftGate V7 offers the customer
C
a redundancy option for the whole OpenScape Cordless Enterprise solution.

00
E N
All cordless subscribers have to be configured on virtual SLCs in the OpenScape 4000 SoftGate for
73
this purpose.
26
D
An additional base station is also installed at every base station location within a radius of approx. 1 -
C
2m.
The radio range will be supported from two base station of different SLC24 boards.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
This additional base station is connected to a different SLC, which in turn must be connected to a
C
different shelf (or also an OpenScape 4000 system).

00
E N
The second base station is operated with reduced transmission power in order to avoid excessive
73
alternation between base stations. (10% of transmission- power).

26
D
If now for some reason the operating SLC board fails the nearby base station using the parallel SLC
C
board takes over the call.
Note: A project-specific release is absolutely mandatory for the redundancy scenario described.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
Moving on, System Networking is next.

C
00
E N
73
26
D
C
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
The term networking covers the functionality of the main system connections.
C
00
In this case, networking means interconnecting systems with different network structures, such as:
E N
• several OpenScape 4000/HiPath 4000 systems with another or with old systems via S0/S2 lines or
73
• virtual networking of several OpenScape 4000/HiPath 4000 systems with one another or with old
26
systems via carrier.

D
• IP networking with SIP Trunking (SIPQ and native SIP)

C
Networking can use either closed or open numbering in E.164 Standard.
Heterogeneous networking, which is networking with systems from other manufacturers, is also
possible.
Many features that operate throughout the network can be set up or barred individually for each
line/trunk group.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
Next we will explain the different types of network within the OpenScape 4000 environment.
C
00
Meshed network, fully meshed:

E N
In this type of network, each system has a direct connection to every other system. Because of the
73
large number of lines, this type of network is not useful in large networks.
26
Meshed network, partially meshed:

D
In this type of network, only some systems have a direct connection to every other system.
C
Star-type network:
IP networking is typically acheived in star form, this is what the customer are actually doing
Routing with LCR allows the specification of several alternative routes within a network to the
destination station.
All User Features are available Throughout the Network. The Configuration is done via OpenScape
4000 Manager.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
The following tips for Networking should be considered:

C
00
• Carry out a network analysis,

E N
• Discuss network components,

73
• QoS mechanisms / bandwidth,

26
• Firewall configuration,
D
C
• Question the use of resource management and define network bottlenecks with the customer,
• For SIP trunking boards, the upgrade/check of the SIP trunking configuration should be performed in
accordance with the software release information.
• Create a Network Plan,
• Create a Node Numbering Concept,
• Incorporate Network-wide Features and consider Connection between OpenScape 4000 V7 and
Applications and External Products.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
The given figure shows an overview of possible networking with OpenScape 4000 using CorNet NQ
C
V 2.3 protocol and older Hicom 300 using CorNet-NQ V2.1.

00
E N
73
26
D
C
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
OpenScape 4000 does networking with OpenScape Voice as well using SIP-Q V2.
C
00
Networking with older HiPath 3000 V8 or 9 and OpenScape Business CorNet –NQ or SIP Q V2 will
E N
be used.
73
26
D
C
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
Moving on, OpenScape 4000 Redundancy is next.

C
00
E N
73
26
D
C
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
OpenScape methods of providing business continuity are:

C
00
Redundancy – this means a complete duplication of a critical component by the following methods:
EN
• Active-Active
73
• Hot Standby
26
• Warm Standby and

D
C
• Cold Standby
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
Initially we introduce you to OpenScape 4000 Redundancy and high availability:

C
00
OpenScape 4000 offers a wide range of feature sets to establish a highly available communication
E N
platform.
73
26
In addition to the previous software versions with features like Signaling and Payload Survivability,
D
alternate route on error mechanism, HFA- Standby Board and Access Point emergency,
C
OpenScape 4000 also supports duplex configuration and geo separation of the DSCXL2 server
hardware.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
OpenScape 4000 and the Replication of ADP, SWU and OpenScape 4000 Assistant Hard Disk
C
00
To enable complete recovery of the RMX-based software and the OpenScape 4000 Assistant in case
E N
of failover, the relevant virtual hard disk partitions and files on the primary machine are replicated on
73
the hard disk of the secondary machine. This is achieved by the DRBD (Distributed Replicated Block
Device) software, which replicates the relevant files over the LAN.
26
D
C
The whole virtual RMX HD (including ADP and SWU) is represented as a single file on the physical
HD. DRBD will replicate the configured partitions containing this RMX file and the specified
OpenScape 4000 Assistant files over the LAN.
If both hardware machines are connected via the local network, synchronous replication is used (in
DRBD terminology: protocol C). This implies that all data blocks are written on the hard disk of the
active machine and, at the same time, on the hard disk of the standby machine. The file system of the
active machine is notified when the writing process has been successful on both machines.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
OpenScape 4000 Duplex with DSCXL2 processor board

C
00
Based on OpenScape 4000 hardware (DSCXL2) the duplex configuration of OpenScape 4000 is
E N
realized in one cPCI shelf. Within a duplex system, one "Active" and one "Stand-by" DSCXL2 server
73
blade are available.

26
D
The OpenScape 4000 Basic shelf contains a switch fabric (SF2X8) in slot 6, two DSCXL2 cards, one
C
in the system slot (slot 1), one in slot 5 and two RTM cards.
This solution supports:

• redundant LAN port
• break down of SWU
• break down of ADP
• break down of OpenScape Assistant and
• break down of OpenScape 4000 CSTA.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
OpenScape 4000 Normal operation

C
00
The active ADP is connected to CCA-SWU and CCB-SWU via the virtual Atlantic LAN using the
E N
same Atlantic LAN IP and MAC addresses by the virtual machines for the ADP and for the CCs.
73
Moreover, all ADP services are available in OpenScape 4000.

26
D
In normal operation, the virtual machines of the ADP and the OpenScape 4000 Assistant on the
C
primary hardware machine are active, while the corresponding virtual machines on the secondary
hardware machine are offline. The ADP and the OpenScape 4000 Assistant, which reside on the
same hardware machine, can only change their active/offline states together. Thus, an OpenScape
4000 Assistant can be active only on that hardware machine on which the virtual machine for the
ADP is active.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
OpenScape 4000 and the Redundant LAN-Ports

C
00
The LAN-Ports on DSCXL2 server blade can be configured in hot redundant mode and connected to
E N
two redundant Ethernet switches. L1 failure of one Ethernet switch results in hot switch-over to the
73
redundant Ethernet switch without loosing calls or application connectivity.

26
D
The following redundant LAN ports are available on the DSCXL2 server blade:
C
• two LAN ports in hot-redundant mode for call control

• two LAN Ports for OpenScape 4000 Assistant/OpenScape 4000 CSTA and
• two LAN Ports for OpenScape 4000 Duplex
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
OpenScape 4000 and SWU failover

C
00
As mentioned before the active ADP is connected to CCA-SWU and CCB-SWU via the virtual Atlantic
N
LAN. Both CCs running in a hot standby mode. This means that one CC is in active mode and the
E
other one in standby mode. In case of break down or restart of the active CC the standby one is able
73
to take over the active role each time.

26
D
C
In case of SWU failover, there is:

• no loss of established calls
• no data loss (e.g. billing, configuration data)
• other virtual machines (ADP, OpenScape 4000 Assistant, OpenScape 4000 CSTA) are not affected
• the ADP and SWU switch overs are independent from each other
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
OpenScape 4000 and the Redundant LAN-Ports

C
00
The LAN-Ports on DSCXL2 server blade can be configured in hot redundant mode and connected to
E N
two redundant Ethernet switches. L1 failure of one Ethernet switch results in hot switch-over to the
73
redundant Ethernet switch without loosing calls or application connectivity.

26
D
The following redundant LAN ports are available on DSCXL2 server blade:
C
• two LAN ports in hot-redundant mode for call control

• two LAN Ports for OpenScape 4000 Assistant/OpenScape 4000 CSTA and
• two LAN Ports for OpenScape 4000 Duplex
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
OpenScape 4000 and ADP failover continued

C
00
In case of ADP failover there are:

E N
• no loss of established calls

73
• restart of ADP/ OpenScape 4000 Assistant VMs (offline time < 5 - 10 minutes)
26
• restart of OpenScape 4000 CSTA - VM (offline time < 5 minutes)

D
C
• unavailability during the switchover no new call can be established

• Dynamic data in RAM and active connections will get lost during the switchover, and
• ADP and SWU switch over are independent from each other
To the external applications, an ADP failover appears as a connection loss and a loss of dynamic
data. Thus, the external applications need to reconnect to the ADP.
The redundant ADP functionality is possible with the following restrictions: The alarm relays ALUM,
not urgent alarm (NAL) and urgent alarm (UAL), all located on the system management board MCM,
are hard wired to the processor board in slot 1.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
OpenScape 4000 and Assistant and CSTA failover

C
00
OpenScape 4000 Assistant failover:

E N
OpenScape 4000 Assistant will shut down all of its components internally. The OpenScape 4000
73
Assistant plays a passive role in the ADP failover. The process monitor does not consider its state in
26
the failover decision. However, the OpenScape 4000 Assistant on the secondary hardware machine
can only be started if the previously active one has been turned down completely. For this purpose,
D
C
the process monitor will send a shutdown request to the OpenScape 4000 Assistant. Hereupon, the
OpenScape 4000 Assistant will shut down all of its components internally.
OpenScape 4000 CSTA – failover:

In case of OpenScape 4000 CSTA failover the application has to be initiated via a new connection to
the active DSCXL2 server. During the cut-over no OpenScape 4000 CSTA services are available.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
OpenScape 4000 Separated Duplex

C
00
OpenScape 4000 Separated Duplex offers hot stand-by call control/SWU resilience functionality with
E N
separated communication servers. The following separated deployments will be possible:

73
26
OpenScape 4000 software installed on two standard / EcoServer / Vmware running as Separated
D
Duplex and
C
OpenScape 4000 installed on two OpenScape 4000 communication server with each one DSCXL2
server blade in a cPCI housing.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
OpenScape 4000 Separated Duplex has the following conditions:

C
00
• The Servers need to be installed in the same L2 broadcast domain

E N
• There must be at least 1 GB of bandwidth,

73
• The RTT (Round Trip Time) between the 2 servers must be lower than 10 msec
26
• Only IP Access Points (AP 3700IP/AP3300IP and/or OpenScape 4000 SoftGate can be connected)
D
and
C
• Quorum Node software needs to be installed on a 3rd independent server.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
and
C
00
• Quorum node software can also run in a VMware environment.

E N
73
• OpenScape 4000 Data Center Edition also supports the feature "separated duplex", installed on
26
virtual machines using VMware. The separated duplex architecture and mechanism will also be used
D
in case of Duplex operating mode in a VMware environment. In this case the software is mapped to
C
three virtual machines.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
The Quorum Node

C
00
• controls the decision process for the changeover,

E N
• monitors that both communication servers are not activated at the same time,
73
• a standard server for the Quorum node must be ordered separately (see the Server White List) and
26
• it can also be installed in a VMware virtual machine.

D
C
• it is part of the OpenScape 4000 DVD or the software image and does not need additional licenses.
• cluster servers must be installed in the same L2 broadcast domains.
• 1 Gbit/s link between the 2 cluster servers must be given.
• the RTT (turnaround time) between the two servers must be less than 10 ms and
• all cluster servers must be synchronized with an NTP server.
Only IP Access Points, OpenScape Access 500 and SoftGate servers can be connected to a
Separated Duplex System.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
OpenScape 4000 Failover and Redundancy of HG 3500 Gateways

C
00
It works as a Redundant LAN Interface as follows:

E N
• HG 3500 and HG 3575 modules can be connected to two different switches via two LAN cables
73
• LAN port 1 active and

26
• LAN port 2 remains in standby mode and only Layer 1 is active at which higher protocol layers
D
remain inactive.
C
When changing the ports through the module, the payload is lost for a period of at least 2 sec. Active
connections are saved and NOT disconnected.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
The standby module (with no IP address of its own) takes over the function of the failed HG3500
C
module.
00
E N
Either of the following can be done:

73
• A manual switchover or an
26
• Automatic changeover
D
C
After a changeover, the network management is informed by an alarm.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
Moving on, security is last chapter about OpenScape 4000.

C
00
E N
73
26
D
C
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
Next, the special feature Restricted Call Duration for Transit Calls is described:
C
00
With the feature Restricted Call Duration for Transit Calls it is possible to limit the duration of a transit
E N
call.
73
26
The parties in the call will be warned by an Override tone shortly before the maximum call duration is
D
reached.
C
The call will be automatically released after the warning period.
The call duration timer range is from 1 to 60 minutes in minute intervals and is available for ISDN as
well as IP trunking connections.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
Single Point of Access is next point.

C
00
The SPoA concept offers, in accordance with the customer the remote access to the customer
E N
netpoints (OpenScape 4000, applications).

73
26
The access is realized via an ISDN respectively a DSL connection between the RCC and the SPoA
D
Router (Huawei and Cisco) on customer side.

C
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
The next special feature is virtual Numbering:

C
00
The Virtual Numbering – VNR feature in OpenScape 4000 supports:

E N
• the multiple assignment of station numbers and

73
• the configuration of overlapping station numbers with different lengths (dependent on DPLN
26
groups).
D
C
Furthermore multiple virtual nodes must be created for this in the OpenScape 4000 (the physical
node).
These are defined with node number and node code.
The station ports configured are each assigned to one of the virtual nodes and the station number of
a station port is now only unique within the virtual node.
The unique identification of a station within the physical node is only possible with the combination of
the node code and station number.
And Shared Use of a OpenScape 4000 by Different Companies is possible.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
Call detail recording (INCDR = internal and network-wide call detail recording) is responsible for
C
recording, outputting, and processing charge and call data for the purpose of determining costs and
00
billing them for certain communication services.

E N
73
This refers to outgoing (trunk, tie) and incoming external connections as well as to internal
connections.
26
D
C
CDR (Call Data Recording) performs charge calculation for external connections without charging
information from the line or for internal connections.
The following features are supported:

• Individual display on a terminal device,
• Charge display for each connection on attendant console with AC WIN IP,
• Call charge display at the night answering position,
• Immediate output of call charges to an external data medium,
• Call charge output by call-up on auxiliary devices,
• Call charge output to FT file,
• Call detail recording and calculation for internal traffic,
• Call detail recording and charge calculation for incoming trunk calls and inter- PBX traffic,
• Call detail recording and charge calculation for outgoing inter-PBX traffic (networking),
• Call detail recording and charge calculation for Euro-ISDN trunk,
• Charge calculation of the call charges on Digite display and
• LCR expensive warning.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
The last special feature is Route Optimization:

C
00
The purpose of this function is to prevent the unnecessary use of alternative routes and the
E N
unnecessary seizure of lines.

73
26
To this end, a "more favorable“ alternative path is searched for as a replacement for the standard
D
route which has been selected for a particular call processing situation; the system performs
C
changeover to this new route.
This feature applies to the voice service for both open and closed numbering schemes in
homogeneous OpenScape 4000/HiPath 4000 networks.
CornetNQ or SIPQ must be used as the networking protocol on both the standard and the alternative
routes.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
Moving on, Security is the last chapter.

C
00
E N
73
26
D
C
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
The distributed and open system architecture of the IP network itself enables attacks against integrity
C
and confidentiality of data communicated over it.

00
E N
OpenScape 4000 provides security for many signaling and payload streams passed through an IP
73
network by means of encryption.

26
D
In detail:
C
• For payload protection in general SRTP / SDES is used.

• For signaling PEP is used to protect the signaling connections between Host System and IP access
points.
• For all other signaling connections TLS is used.
• For security parameter handling related to the payload connections in general MIKEY is used.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
This table shows the available encryption in use by HFA subscribers, SIP Q V2 Trunking, Native SIP
C
Trunking and IPDA signaling.

00
For native SIP subscribers encryption is not supported at the moment.

E N
73
There are two authentication models, when establishing a TLS connection:

26
1. Server-provided TLS certificates model (TLS): In this model the TLS server provides its certificates
D
as part of the TLS establishment phase to the TLS client.

C
2. Mutual TLS certificates model (MTLS):In this model, both partners provide their respective
certificate as part of the establishment phase.
3.SDES is only for OpenScape Softgate and OpenScape Access.
MIKEY is the key management solution to be used for crypto context negotiation in case of SIP and
HFA calls.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
OpenScape UC Redundancy is next.

C
00
E N
73
26
D
C
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
There are several components to an OpenScape UC system as we covered in the Technical Sales
C
Class including OpenScape Voice or OpenScape 4000, which each have unique redundancy options,
00
so that is covered elsewhere.

E N
73
Optional components include the Facade Server, OpenFire and OpenScape Web Collaboration.
These optional components also have their own methods of implementing redundancy, so they will
26
not be covered in this section either.

D
C
What will be covered in this section?

This will be the OpenScape UC Backend Server, which always resides on the OpenScape UC
Application Server, the OpenScape UC Frontend Server and OpenScape UC Media Server
redundancy options.
In reference to the Media Server and Frontend server, there can be from one to four of them, and
each one can support approximately 5000 users, based on the specifications of the server and the
load generated by the users.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
The OpenScape UC Media Server and OpenScape Frontend Server support N+1 redundancy. If one
C
Media Server is required, then a second Media Server is provided for redundancy.
00
E N
There is no special provisioning required, the two media servers are treated as a resource and by
73
providing two, if one fails, the other one has capacity to handle the Media Server requests. The
Frontend Server redundancy is similar, but there will be an appliance required to provide either
26
redundancy or capacity above 5000. This device is the load balancer that was described in the
D
Technical Sales Specialist course.

C
Load balancers are commonly used when multiple servers are used to provide high capacity web
services.
If one Frontend Server is required for capacity, then a second one is provided for redundancy to
achieve the N+1 redundancy and a load balancer is added to distribute the web requests between the
two Frontend Servers.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
In this example, three Media Servers and three Frontend Servers are required for capacity, so a
C
fourth Media Server and a fourth Frontend Server is provided for redundancy.
00
E N
In this example, N+1 becomes 3+1, and this cluster can support up to 15,000 users, even if one
73
Media Server and one Frontend Server fails.

26
D
C
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
The OpenScape UC Backend Server/Application Server has different requirements for redundancy.
C
The OpenScape UC logic, which is controlled by the Backend Server, resides on a single computer
00
so the N+1 type redundancy is not an option.

N
OpenScape UC Backend Server survivability is the more standard environment of a backup computer
E
running the same software as the primary computer.

73
Unfortunately, there is no Active/Active mode for OpenScape UC, so the first option is Active – cold
26
standby. In this case, the primary Backend Server is used until there is some type of failure.
D
C
The cold standby computer runs the same software, but isn’t available to the clients until an
administrator makes changes to the database and disables the primary server, if that server is still
running.
The database must reside on an external Storage Area Network accessible to both machines, and
manual intervention is required for this redundancy option.
Both the active and cold Backend Servers use same the Media Servers and Frontend Servers.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
Here is a listing of the manual tasks required for activation of the cold standby Application Server.
C
00
E N
73
26
D
C
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
There are additional options available for redundancy for the OpenScape UC Application Server.
C
When the customer has a virtualized datacenter, or is exploring virtualization for OpenScape, then
00
VMware survivability options are available and this will be covered in a later section.
E N
73
There may be additional options available from the Unify Professional Services organization for your
particular country.
26
D
C
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
Moving on, OpenScape UC Communications Enabled Business Processes is next.

C
00
E N
73
26
D
C
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
CEBP, or Communications Enabled Business Processes is achieved by integrating OpenScape UC

C
functions into the business applications that your customers use every day. The primary objective of
00
CEBP is to reduce the human latency that exists within a process flow.
E N
73
For example, a mortgage approval process may be experiencing human latency because the person
assigned to provide approval is on vacation or busy working on something else. To reduce this
26
latency, CEBP leverages unified communications capabilities by embedding them into the business
D
process flow so that the loan officer can see who else is available that can provide this approval with
C
a quick glance at the screen, and can then initiate contact with that person with a single mouse click.
The result is a more efficient, more automated closed-loop process; translating into significant ROI.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
To understand how a business application, like SAP, can interact with OpenScape UC, it is important
C
to know how the OpenScape clients interact with the Frontend and Backend servers.
00
E N
In this diagram, you can see the OpenScape UC Web Client on the left. It pulls the information it
73
needs from the Frontend which is responsible for “painting the screen” of the web client.
26
The Frontend Server creates the portlets used within OpenScape UC. The Frontend communicates
with the Backend to determine what information should be sent to the client, for example, is Michael’s
D
C
phone on hook or off hook and is Michael’s personal status available or busy?
You can also see arrows pointing off the screen to the right from the Backend Server. These are links
to the various systems which can interact with OpenScape UC. These include LDAP directory, Web
Conferencing, Groupware like Microsoft Exchange, XMPP chat servers and unified messaging
systems like Unify’s Xpressions.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
The OpenScape Desktop Client Web Embedded and the Fusion clients; Fusion for Outlook, Fusion
C
for Notes and Fusion for Lync (or Skype for Business), act much like the OpenScape Web Client, but
00
add functions including a SIP soft client for VoIP.

E N
73
26
D
C
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
By altering the code of the business application, information from OpenScape UC can be displayed in
C
the pages of the customers’ business application in much the same way as the OpenScape UC
00
Clients.
E N
73
This is very easily done in a web page.

26
D
For example, the “portlets” of OpenScape UC can be displayed in the customers’ Intranet home page
C
with Single System Sign-on for easy access to the UC features.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
Here is a blowup of the customers Intranet page showing the Contacts portlet and the Journal portlet.
C
00
They look the same as with the OpenScape UC Web Client, but they are imbedded the Intranet so
E N
the employees can see all the pertinent information from one browser page as opposed to one page
73
for Intranet and a different page (or tab) for the OpenScape UC functions.
26
D
Any of the OpenScape UC Portlets can be accessed this way with a minimum of effort by Unify’s
C
professional services, the partners professional services, or even the customers IT department.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
The customer may opt for a richer integration where the application accesses the OpenScape UC
C
Backend Server without going through the Frontend Server.

00
E N
In this way, the display is no longer limited to the “portlet” view, but can be truly customized.
73
26
D
C
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
Here is an example using SharePoint.

C
00
In the standard contacts portlet, all of your contacts are displayed. In this customized version, only the
E N
contacts related to this task are displayed. The user doesn’t have to hunt through all their contacts to
73
find the 4 or 5 that are related to this task.

26
These don’t even have to be the user’s contacts. They can be anybody; OpenScape UC users, other
enterprise employees and even customer or partner contacts.
D
C
This CEBP customization will find the right people to display and if they are OpenScape UC users,
will automatically display their status. It will even build a conference or two with a single click –
including out dialing of all parties. Now that is convenient and time saving.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
You have just seen two of the many ways to do custom integration with CEBP. This page shows you the general
C
categories with a simple description of each one.

00
E N
We will start with Rebranding. Does the customer want their brand and logo showing on the OpenScape clients?
73
If so, most of the OpenScape clients can be modified to display whatever the customer wants. This is the
26
simplest form of CEBP.

D
C
Next is Embed. Each of the OpenScape UC functions; call control, contacts, journal, conferences, team,
directory, personal status, preferred device, rules, Softphone controls and chat are displayed in a “portlet”. Each
function has its own portlet. These portlets are portable and can be embedded into the customer’s web site, or
business application. They can choose one portlet or all portlets effectively creating their own UC client.
Next is customize. If the customer likes the OpenScape Desktop Client Web Embedded but would like to
change the functionality, then they can. Perhaps they want to remove the conference function for half the
enterprise. The customer can customize the OpenScape client and offer two versions to their users - one with
conference, and one without.
The deepest level of customization is to Integrate. This is the SharePoint example I used earlier to demonstrate
UC functionality added to the business application.
Additional integrations are available to connect to web conferencing services that haven’t been previously
developed, groupware systems for email and calendaring other than Exchange and Domino and other services
the customer may be using.
And the final customization is for management. If the customer is using a management system for their other
applications and wants to use the same one for OpenScape UC, then the APIs and SOA interfaces are
available.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
Here is a better look at that Intranet web page with a users Contact list and Journal Portlets.
C
00
Note that all the functions are available; seeing user and phone status, single click to call, ad-hoc
E N
conference, add contact and more. The customer must have some type of SSO authentication in their
73
network, or the user would need to log in when opening this page.
26
D
The other portlets are also available for this type of integration.
C
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
On this page, the customer has integrated OpenScape UC into their Google Mail with OpenScape
C
Fusion for Google.

00
E N
Notice the OpenScape standard icons for status and preferred device and how they match the
73
Google Mail look and feel.

26
Note that Fusion for Google is included in the User license for OpenScape UC, but customization
would need to be done for full integration. This would be considered a PSR, or project specific
D
C
release.
Contact Professional Services for more information and availability in your country.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
OpenScape UC integrates very nicely into the corporate directory. Here you can see the Unify
C
corporate directory with the entry for Michael and you can see the OpenScape UC enhancements on
00
the right side of the screen. The user can simply click on the green phone handset icon to initiate a
N
call to Michael, even if they are not an OpenScape UC user.

E
73
That makes finding and calling people even easier. Presence and personal status could be added if
26
required.
D
C
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
Unify has created some marketing brochures to demonstrate the capabilities and benefits of CEBP.
C
This screen shot was taken from one of those brochures and shows an integration that was done for
00
a customer using SharePoint.

N
On this site, the Sales Team Home page is displayed with a list of contacts within the sales
E
organization.
73
Their presence and their phone status is displayed for all to see. Documents have been loaded in the
26
bottom section and the owner of each document is identified.

D
C
You can see their status and they can be reached with click to call for any question regarding the
document.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
After clicking to call, the call control window pops up. If the user has one of the OpenScape Desktop
C
clients, the call can be placed through the PC Softphone as in this example.
00
E N
Clicking on the video camera icon would instantly elevate this phone call to a video call.
73
26
D
C
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
Here is an example of CEBP integration of OpenScape UC with SAP. Once again, you can see the
C
contacts associated with this order, their status, their phone status and the chat bubble for each one.
00
E N
By seeing their status, initiating contact to one of these members is done in a more intelligent
73
manner. Reinhard is obviously not available as you can see by the yellow handset, so it would make
more sense to reach out to Adam for a quick answer.
26
D
C
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
For our last example of CEBP, the LIFERAY Portal is shown. There is also a brochure available
C
which can be distributed to prospects to demonstrate the power of CEBP. You can see not only the
00
OpenScape UC functions imbedded into the portal; you can also see the OpenScape Web
N
Collaboration controls.
E
73
26
OpenScape UC CEBP provides great benefits to our customers but it does require customization.
D
OpenScape UC is designed around the open principals of SOA, and customers with creative and
C
capable IT departments can use this to customize their own environment. Unify Professional
Services, partner Professional Services and companies like LIFERAY can also help customers
extend the benefits of OpenScape UC into their everyday business applications.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
Unify continues to enhance OpenScape products and add new capabilities. Since the creation of the
C
Technical Sales Specialist course, additional functions have been added that can impact the
00
deployment of OpenScape UC. One of those enhancements is the ability to record conferences. This
N
is accomplished by a deeper integration between the OpenScape UC Media Server and OpenScape
E
73
Web Collaboration.
26
D
Audio conferences, video conferences and web collaboration sessions with audio can now be
C
recorded. A click of the mouse while in a web collaboration or taps on your phone dial will start,
pause, resume and stop the recording. The recordings are created on the OpenScape Media Server
and then transferred to the OpenScape UC Back End server for storage and distribution.
The recording will then be available to the end-users in standard AV format which can be edited.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
Here is a closer look at the recording controls.

C
00
The Moderator can start the recording with or without participant video. Once started the moderator
E N
can pause and resume the recording.

73
26
Emails with download-link are send to all moderators when the session is over, however the email
D
address must be in UC system and web collaboration user identified with Single System Sign-on -
C
SSO.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
For existing customers whose system was installed before mid 2015, a redesign of their Media
C
Server and Web Collaboration environment will be required to use this new recording feature for
00
recording Web Collaborations. The established landscape of the OpenScape UC Server in the
N
intranet and the OpenScape Web Collaboration server in the DMZ can be still used, but there is no
E
73
recording of joint audio and video available. However, recording of Audio and Video Conferences can
26
be done if upgrading this landscape to OpenScape UC V7R3. As a matter of fact, you don’t even
D
need the Web Collaboration Server to record the audio or video conferences.
C
These recordings are created on the Media Server and send to the Backend server for storage and
distribution.
A separate video composer is required in the Media Server, which does require more CPU
processing power.
The pre mid 2015 landscape has the OpenScape UC components including Backend, Frontend and
Media Server, all installed in the Intranet. The OpenScape Web Collaboration Server is installed in
the DMZ allowing access from the Intranet and the Internet. A connection between the OpenScape
UC Backend and Web Collaboration Servers is used to schedule and initiate Web Collaboration
Sessions.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
Here is the new landscape. You will notice that the Web Collaboration Server is now integrated into
C
the Media Server and is now installed in the Intranet. A Reverse Proxy is installed in the DMZ to
00
provide connection between the trusted and untrusted networks. This allows recording of voice
N
conference and Web Collaboration Session simultaneously. These recordings are also made on the
E
OpenScape UC Media Server and sent to the Backend server for storage and distribution.
73
26
For security, encryption is provided from the OpenScape Media Server to the user.
D
C
This concludes the OpenScape UC section of this course.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
OpenScape in the Virtualized environment is our next topic.

C
00
E N
73
26
D
C
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
There are two basic reasons for OpenScape data centers to go virtual, functionality and cost savings.
C
00
N
From the functionality perspective, virtualization offers hardware independence. When Unify provides
E
the hardware, it will be a specific manufacture like Lenovo or Fujitsu. If the customer uses Dell
73
hardware in their data center, they may not want Lenovo. Virtualization allows them to use any
26
hardware that is approved by VMware, as long as it meets the minimum specifications for
D
OpenScape.
C
Implementation is faster and less prone to errors using vApps and Appliances.
There are additional options for redundancy and survivability with VMware, and they match the other
applications installed in the data center.
Most servers run at 30-40% of capacity. Virtualization can increase that percentage dramatically
which results in fewer servers.
And management becomes more consistent across systems if all the hardware is the same type and
VMware is managing the virtual machines.
From a cost savings perspective, less hardware means less initial cost, lower maintenance costs and
most certainly lower environmental costs for physical space in the data center and power and cooling.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
Here is what we have found with OpenScape Virtualization.

C
00
N
Hardware utilization increases by 50 to 70%, cost reductions amounting to 60% and energy savings
E
up to 30%. Administration productivity gains of 2 to 3 times are also seen.

73
26
D
C
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
Unify has chosen to focus its development efforts on VMware ESX/ESXi as the market leader in
C
hypervisor technology with over 80% market share. Alternative hypervisor technologies may be
00
supported on a customer specific basis via PSR and Unify Professional Services.
E N
73
OpenScape Voice, OpenScape UC Application, Common Management Portal (CMP), OpenScape

26
Media Server, Deployment Services (DLS) and other OpenScape Enterprise components will work in
D
a virtual environment using VMware and support many of the VMware features.
C
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
Let’s compare OpenScape in a physical deployment to OpenScape in a virtual deployment.

C
00
N
In a virtual deployment, an OpenScape Voice “node” can be considered the OpenScape Voice
E
software application as a “virtual node” running in a SuSe Linux environment, but on a VMware
73
virtualization layer and running on one or more hardware machines also referred to as hosts.
26
D
C
The OpenScape Voice virtual nodes can be running on the same host, physically co-located hosts or
geographically separated hosts.
With virtual nodes, all the requirements for inter-node communication, database synchronization and
switch-over concepts still apply, even though the OpenScape Voice application itself is not aware as
to whether it is running in a physical deployment or a virtual deployment.
As with physical deployments, care also must be taken with virtual deployments to ensure the
necessary performance, capacity and redundancy performance criteria are met to satisfy the
customer’s reliability and availability demands, such as is provided carrier class availability.
Thus, as we go forward in the discussion of virtual deployments, you should think of software
application virtual nodes which are independent of the server platform whenever there is a reference
to nodes with respect to performance, operations or requirements.
Let us now look further at the OpenScape Voice virtual deployment environment.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
A hypervisor, also called a virtual machine manager (VMM), is a program that allows multiple
C
operating systems to share a single hardware host. Each operating system appears to have the
00
host’s processor, memory and other resources all to itself. However, the hypervisor is actually
N
controlling those resources, allocating what is needed to each virtual machine, or vm, making sure
E
73
that the guest operating systems cannot disrupt each other.

26
D
Vmware vSphere Hypervisor is a “bare-metal” hypervisor that partitions physical servers into multiple
C
virtual machines.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
A typical VMware Infrastructure datacenter consists of basic building blocks such as x86 computing
C
servers, storage networks and arrays, IP networks, a management server and desktop clients.
00
E N
73
26
D
C
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
OpenScape Voice virtual deployment is supported for duplex deployment environments, where there
C
are two virtual nodes that are either co-located or geographically separated.
00
N
OpenScape Voice virtual deployments are compatible with VMware ESX(i) v4.x or ESXi v5.x
E
software. ESXi v5.5 is the latest version supported at the time of this course creation, but later
73
versions will be approved as appropriate. As mentioned previously, other VMware products or other
26
hypervisor technologies can be considered on a project specific basis.

D
C
OpenScape Voice is independent of the underlying hardware servers or hosts, as long as the
hardware is on the VMware compatibility list for ESX(i) v4.x or ESXi v5.x and the OpenScape Voice
performance and capacity requirements are satisfied. The hard disk storage can be either internal to
the servers or hosts running the OpenScape Voice application, or hard disk storage can be part of a
Storage Area Network (or SAN) infrastructure. In a virtual deployment, the OpenScape Voice system
assumes it has one hard disk drive and four Ethernet ports available for its use.
For high availability, the OpenScape Voice specifications require redundancy of these and other key
hardware resources.
In a virtual deployment, the Billing, Signaling, OAMP and Cluster Interconnect Ethernet ports do not
need redundancy because Vmware provides recovery of the virtual Ethernet ports. Also, the machine
management port is no longer used and the STONITH command is typically sent over the OAMP
port.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
In an OpenScape Voice virtual deployment, the hardware platform is typically installed, supervised
C
and maintained by the customer, assuming no other special considerations have been made by Unify
00
or the partner channel with the customer.

E N
73
This obviously differs from a physical deployment when the OpenScape Voice system operation is
26
tightly coupled with the Lenovo or Fujitsu servers.

D
C
Therefore, in a virtual deployment, the following are outside the scope of OpenScape Voice control
and are provided and managed by the customer:
• the hard disk location, which can be local or on a storage area network (or SAN),
• the type of disk redundancy that is deployed (such as RAID),
• the server, or host, core processor and memory redundancy infrastructure,
• the network redundancy, such as Ethernet bonding drivers for signaling, and
• the method of remote access for service and hardware alarming.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
It is highly recommended that each Technical Sales person download and review the latest copy of
C
the OpenScape Virtual Machine Resourcing and Configuration Guide to familiarize themselves with
00
the specific requirements and the guidelines on sizing the virtual machines.
E N
73
26
D
C
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
Within that guide, and in the Sales Information Document for each OpenScape application, the
C
support for that particular application will be defined.

00
E N
For example, some applications support vMotion, and others do not.

73
26
D
C
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
A chart is provided which lists the OpenScape components and the VMware features that each one
C
supports. On this chart you can see the OpenScape Voice supports vMotion and HA, but not Fault
00
Tolerance.
E N
73
Many of the features on this chart provide alternatives to the hardware oriented redundancy of
26
OpenScape products. For example, High Availability and vMotion provide an alternative to
D
OpenScape UC cold standby.

C
Please check the latest documentation because the support is changing for these features as Unify
modifies the OpenScape software and completes testing.
Refer to the VMware website or other training materials for more information on each of these
features.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
For each OpenScape application, the OpenScape Virtual Machine Resourcing and Configuration
C
Guide provides details of the virtual deployment.

00
E N
Here is an example of the details provided for OpenScape Branch V8 showing the operating system,
73
native redundancy support and strategy, types of traffic handles and VMware feature compatibility.
26
D
C
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
The guide also lists the virtual machine requirements for each OpenScape application. Here are the
C
details for OpenScape Branch V8. The details include CPU, RAM, NIC and Hard Drive space
00
required in the virtual machine.

E N
73
26
D
C
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
In the initial installations of OpenScape on VMware, there were issues with the method of license
C
enforcement. The licenses were tied to the MAC address of the physical machine. In a VMware
00
environment, the virtual NICs no longer have unique MAC addresses, so a new method was devised
N
for licensing. the Advanced Locking ID (ALI).

E
The Advanced Locking ID is a character string comprised of the locking parameters:

73
• Host Name
26
• Host IP Address
D
C
• Gateway (default) IP Address

• Primary DNIS IP Address
• Time Zone (GMT Offset)
• Either IPv4 or IPv6 IP addresses are supported.
Advanced Locking ID tolerance levels for locking parameters are established in the event one or
more changes, versus the much more rigid MAC-based licensing.
OpenScape Enterprise V7 products that support Advanced Locking ID include OpenScape Voice,
OpenScape Session Border Controller, OpenScape Concierge, Common Management Platform
(CMP) and OpenScape Branch.
For a full list of OpenScape Enterprise V7 and other Unify products that support Advanced Locking
ID, refer to the Central License Server (CLS) documentation and user interface to see if a particular
product requires use of Advanced Locking ID for virtual deployments.
Also refer to the License Management technical resource documents for further details.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
In support of virtualized deployments, Unify has delivered pre-installed, pre-configured, ready-to-run

C
applications that can be deployed onto virtual infrastructure, which simplifies solution deployment.
00
E N
These applications are called virtual appliance (vApp) applications.

73
26
vApp application functions include creation of the customer environment, distribution of software
D
images and deployment of configuration data, installation files and licensing, as well as the capability
C
for mass provisioning.
vApp can be directly loaded onto open hardware, which avoids the installation, configuration and
maintenance associated with running multiple complex software stacks, operating systems and
applications.
This makes deployment via partner channels substantially easier and there is a serviceability
enhancement. Initially Unify, our partners or our customers had to configure and install virtual
machines for OpenScape Enterprise deployments. The vApp allows Unify to deliver a single, ready to
run disk/image of a virtual machine, avoiding the additional effort of building a virtual machine.
This concludes the section on Virtualization.
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
This completes the Unify Certified Technical Sales Expert for OpenScape 4000 course.
C
00
E N
73
26
D
C
6
-1
08
1-
_0
H
C
AR
_H
EL
._
_A
D
Thank you for attending.

C
00
E N
73
26
D
C

Mod02 GL OS4TSEPSDT CD2673EN00CD

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Mod02 GL OS4TSEPSDT CD2673EN00CD

Uploaded by

Copyright:

Available Formats

6

OpenScape 4000 Course.

The course comprises the following content:

• Unify Technical Sales Specialist Review,

• OpenScape Cordless Enterprise,

• OpenScape 4000 Redundancy and

• Special Features and security.

• We will also look at OpenScape UC Redundancy,

• OpenScape UC Communications Enabled Business Processes and

Unify Technical Sales Specialist Review (1)

together with OpenScape UC, forms an Enterprise Unified Communications server.

OpenScape 4000 Communication Server option (EcoServer) supports convergent IP requirements,

Unify Technical Sales Specialist Review (3)

with the different components of the OpenScape 4000 IPDA infrastructure.

Center and centralized management.

Unify Technical Sales Specialist Review (5)

states for up to 200000 subscribers in networked scenarios.

A wide choice of modern clients is available for users.

The next Chapter comprises OpenScape Cordless Enterprise.

(Digital Enhanced Cordless Telecommunications).

open, transmission distances of up to 300 meters are possible.

OpenStage SL4 professional

OpenScape DECT Phone S5

E V7 elements can be networked to form a joint DECT system.

administered on one SLC24 board.

This results in a total of 12264 UP0/E ports.

With respect to one-channel base stations, a total of 8176 can be connected.

some new options.

subscribers can also be configured in an OpenScape 4000 SoftGate.

Administration is done via CATool.

The following Main Features are supported by OpenScape Cordless Enterprise:

• Blocking/unblocking DECT frequencies

• Automatic compensation of signal delay to base stations

• Improved user interface with dual-mode softkeys

• Support for the OpenScape Display Telephone Book (DTB)

Now we will explain roaming:

How does handover work?

a handover is always initiated by the mobile telephone.

Essentially, there are 3 types of handover:

possible related areas that belong to the same SLC.

extended connections are required more frequently.

configured in an OpenScape 4000 SoftGate.

At the moment it is not possible to connect base stations to the vSLC.

other vSLC applications.

configured in a OpenScape 4000 SoftGate.

Base stations cannot be connected to the vSLC.

A prolonging connection is set up for this purpose.

Let us now explain OpenScape 4000 Cordless Enterprise Redundancy:

opportunity of operating the entire Cordless E V7 in redundant mode.

a redundancy option for the whole OpenScape Cordless Enterprise solution.

different shelf (or also an OpenScape 4000 system).

alternation between base stations. (10% of transmission- power).

board takes over the call.

Moving on, System Networking is next.

systems via carrier.

• IP networking with SIP Trunking (SIPQ and native SIP)

Networking can use either closed or open numbering in E.164 Standard.

Meshed network, fully meshed:

Meshed network, partially meshed:

The following tips for Networking should be considered:

• Carry out a network analysis,

• Discuss network components,

• QoS mechanisms / bandwidth,