OpenScape Voice V7

Product Name and Version

OpenScape Voice V7 & V7R1

Brief Product Overview

Objective and Scope

OpenScape Voice V7 is the software-based enterprise voice application running as part of
OpenScape UC Suite. It provides a rich set of enterprise voice features for medium to large size
enterprises. It can be deployed as a simplex (single server) solution, in “try and buy” scenarios,
or as a carrier grade voice solution for the enterprise (duplex server nodes with 100% failover
support). It is a SIP based voice application running on commercial servers supporting scaling
from 350 up to 5,000 users for a single server system and up to 100,000 users in a duplex
configuration It is built from the ground up as a data center application that can work in a
virtualized architecture. Virtualization is based on VMware hypervisor. OpenScape Voice can be
delivered as a vApp (virtualized application) – a pre-configured, ready to run application on a
Virtual Machine.
OpenScape Voice is designed to cover multiple customers and target market deployment
scenarios. The key deployment scenarios are:
1) OpenScape Exchange – OpenScape Exchange is deployed as an overlay solution for
multi-vendor networks, where there is TDM legacy, or converged IP systems. In the
overlay deployment, OpenScape Voice acts as a SIP based central routing and
administration solution for multi-site, multivendor networks, allowing customers a
“migrate at your own pace” solution.
2) Public Cloud / Hosted Edition – OpenScape Voice is the cornerstone application for
Public Cloud/Hosted Edition solutions. It supports multi-tenancy (up to 6,000 business
groups) allowing Service Providers to “build their own cloud”.
3) Private Cloud – for large enterprise customers (1,000 to 100,000 users) with multi-site
locations that span over a region or the globe, OpenScape Voice can deploy as a Private
cloud solution. The key characteristic of a Private Cloud is centralized deployment of
voice (and UC) service from the customer’s data center. .
It is the successor of OpenScape Voice V6.
* Note: Please see OpenScape UC Server Hosted Edition documentation for more details on the hosted
services offering.

Product Matrix
All components included in the OpenScape Solution Set V7/V7R1 are listed in the Product
Compatibility Matrix.

Brief Overview Page 1 November 2012

 OpenScape Voice V7

What’s New in OpenScape Voice V7 & V7R1

End-User Features

OpenScape Voice V7R1 features:

Notification of Connecting to a Lower Security Zone - RQ00032342/FRN4344

The “Notification of a lower security zone” feature shall enable a user to be informed when an
incoming call originated from a lower security zone, or when an outgoing call terminates in a
lower security zone.
In addition, a user in a multiparty call such as conference shall be informed, if any of the
participants in the conference has a lower security zone.
The notification of the user in such an event shall be via a short message display on the
OpenStage device along with an audible indication, e.g. a ‘beep’, or a special ring back tone. As
a call evolves over time due to feature usage, e.g. call diversion, call transfer, call pickup etc, the
parties involved in the call shall be constantly informed if a change in the security level of the
other party(ies) has occurred.

Support ONS-Enabled OpenScape Contact Center Mobile Agents independent of

OpenScape UC - RQ00034540/FRN5440
(Note: This function will be released after the OpenScape GA date. Check with PM for status)
Contact Center agents will be able to set a preferred device from inside their OSCC Agent
Desktop even if OpenScape UC is not deployed so that they can perform their tasks for example
via their home phone or cell phone.
This feature provides an OpenScape Contact Center (OS CC) and OpenScape Voice solution
where contact center agents are:
• provisioned for One Number Service (ONS)
• require no deployment with OpenScape UC application licenses
The solution must permit contact center agent to select and set a preferred device via the OS CC
desktop application. Once this feature is active all inbound calls shall to be routed to the agent’s
last selected preferred device by OSV even when OS CC server is down.
The solution shall also support the OS CC callback service via the ONS Make Call service.

Silent Monitor Whisper (Coaching) - RQ00030029/FRN4209

(Note: This function will be released after the OpenScape GA date after completion of an eeQA/eeQS. Check with PM for status)
During a call, the contact center supervisor has the possibility to talk only with the agent and
coach him. In this case, only the agent will receive the supervisor’s voice. This feature is very
useful in contact center environments, because the supervisor will coordinate and coach his new
agent.

Hunt group parallel ringing in normal mode - RQ00033303/FRN4614

This feature provides an additional choice in the MLHG distribution possibility. When the main
site number is called, all phones should ring so that the incoming caller can have the fastest
response possible, but – unlike how the Hunt group works now – each user must be callable
directly as well. Only the main site number should ring all phones. They will also need queuing
for incoming calls when all phones are busy/ringing (e.g. when the main site number is called).

Brief Overview Page 2 November 2012

 OpenScape Voice V7

A subscriber cannot be a member of a ‘regular’ Call Pickup Group and a member of a Parallel
Hunt Group at the same time. A subscriber also cannot be a member of more than one Parallel
Hunt Group.
Hunt group Name Display - Multiple RQs/FRN4614
Today, a hunt group member cannot distinguish if an incoming call is related to the hunt group
or to his station number. The display only shows the calling party and no hunt group info.
A new “Send Pilot’s Display Information to Members” parameter shall control whether the
OpenScape Voice sends the Pilot’s display information to the Hunt Group members for hunted
calls. If this parameter is set, the Pilot’s Name and Number will display on the member’s phone,
like the OpenStage phones.
For instance, consider a call from 815615551234 to a Hunt Group Pilot with Name = “Sales” and
Number = 51000. In this case, the display on the Hunt Group member’s OpenStage phone would
be as follows
“Send Pilot’s Display Information to Members” is unchecked (Default)

815615551234

“Send Pilot’s Display Information to Members” is checked

815615551234
-> 51000 Sales

Group Call Pick Up Group Display and Naming Enhancements - Multiple RQs/FRN4615
This feature addresses the following enhancements to the OpenScape Voice’s Call Pickup Group
feature:
1. Allow the administrator to block the calling party’s identity (Name and Number) in the
notifications sent to the CPU members. This is required by several customers that want
the calling party’s identity to be presented only to the called party and the party that picks
up the call. (RQ00030223, RQ00030517, RQ00033146, RQ00033909)
2. Allow the administrator to configure a Name for the Call Pickup Groups. (RQ00033250)
3. Include an indication that the call has been picked-up. This is needed so the phone can
decide whether the picked-up call should be logged as a missed call or not.
(RQ00032410, RQ00034315)

Group Call Pick Up Group Display and Naming Enhancements - Multiple RQs/FRN4615
This feature addresses the following enhancements to the OpenScape Voice’s Call Pickup Group
feature:
1. Allows the administrator to block the calling party’s identity (Name and Number) in the
notifications sent to the CPU members.
2. Allows the administrator to configure a Name for the Call Pickup Groups.
3. Includes an indication that the call has been picked-up

However, this enhancement also requires an enhancement in the OpenStage phone. This is
being addressed as part of an enhancement which is targeted for OpenStage V3R2. As part of
this enhancement, the OpenStage phone will allow the users to decide (via configuration)
whether to log calls that are completed elsewhere or not. If logging ‘calls completed
elsewhere’ is enabled, the missed calls will be marked with a new indication. Contact
OpenStage phone Product Management for availability.
Brief Overview Page 3 November 2012
 OpenScape Voice V7

OS Voice Group Call Pickup interworking with HiPath DX - RQ00032316/FRN5344

(Note: This function will be released after the OpenScape GA date. Check with PM for status)
Currently Group Pickup interworking is supported between HiPath DX systems and between
HiPath 4000 and HiPath DX systems.
The successful introduction of OSV into the UK PSN network is going to require interworking
with the base of approximately 2000 DX systems. The migration of this base will take several
years.
Additionally there is a base (under service contract) of approximately 4000 DX systems (350K
users) that are potential migration customers. Some of these, such as the West Berkshire
Council, will have a mixed network of DX and Voice for some time in the future.
If there is no party to pick up locally, OSV should request Group Call Pick up from a remote
endpoint despite the absence of a Group member ringing indication. Also, a request from a
remote endpoint should be serviced regardless. The HiPath 4000 has already made the
modifications to accommodate the DX operation. The changes in the DX to comply with the
current OS Voice operation are estimated to be in the Large Development effort range and do not
make sense to implement in this phase of the DX sales life.
OSV network-wide group pickup is requested to interwork with legacy DX users over SIPQ.
Currently network-wide group pickup supports HiPath 4K group members. The main difference
between HiPath DX and HiPath 4K regarding the group pickup feature is HiPath DX does not
support Group Indication On/Off.

General Availability of Virtual OpenScape Voice Integrated Simplex – FRN6406

(Note: This function will be released after the OpenScape Voice GA date after completion of an eeQA.
Check with Product Management for status)

This deployment model is designed to replace the previously discontinued OpenScape Entry model.
The customer will use the OpenScape Integrated Simplex ISO Installable image from SWS which
includes the following products
OpenScape Voice
CMP
UC Server
Media Server

System/Architectural Features
Pass Call Access Control response codes transparently between networked OpenScape
Voice systems – RQ34148/5226
In pre-V7 OpenScape Voice systems, if Call Admission Control (CAC) blocking occurs beyond
an OpenScape Voice transit node, the treatment is different than if the CAC blocking occurs at
the same OpenScape Voice node as the caller.
As of OpenScape Voice V7R1, a new CorNet-NQ operation is created to carry the SIP response
Status-code, which provides consistent CAC treatment, independent of where caller is located
with respect to where the CAC blocking occurs.

Support DLS server assignment at branch office level in Assistant - RQ00033162/ FRN4847

Brief Overview Page 4 November 2012

 OpenScape Voice V7

This Assistant enhancement shall allow the administrator to use multiple deployment servers
(one deployment server per branch office) for the subscribers that belong to the same business
group. It is not possible to associate more than one DLS for the same business group.

Management and Administration

Provide a GUI for OpenScape Voice Firewall /Packet filter rules - RQ00030705/FRN3655
The administrator navigates to the Administration section of the OpenScape Voice Assistant and
is able to:
• List the already created packet filter rules
• Add packet filter rule(s)
• Edit and modify an existing one
• Clone an existing one
• Delete packet filter rule(s)
The Security Administrator will be able to access the Packet Filter Rules management user
interface.

Implement existing Toolkit for upgrade and migration support in Assistant -

RQ00030389/FRN5020
Fr FRDB: The scope of this FRN is to provide UI for the Outage Free Upgrade
The main functionalities will be:
** The trigger of the Upgrade will be done from within OpenScape Voice Assistant/CMP.
** The usage of the DVDs and USB sticks will be eliminated, so as the service technician can
execute the Upgrade remotely.
** After the trigger of the Upgrade the user can monitor the status of the procedure from
OpenScape Voice Assistant in case of cluster. In case of simplex the status can be monitored via
the RSA of the server.
Fr Joe’s: Allow the administrator to use the Assistant GUI to support:
• Upgrades
• HW Migrations (Server upgrades)
• Network Changes (L2 to L3 Geo Separation)

Release of OpenScape Voice Trace Manager for Internal and External use.
The OpenScape Voice Trace Manager (OSV-TM) tool provides for:
• an off-line store of trace files reported by a range of OpenScape solution elements that is
the basis for saving the event traces over long periods of time on a 24x7 continuous view
• the tool runs parsing and indexing routines against the traces to normalize the data
between the applications and write to a relational database
• as a result, the OSV-TM client provides a focused and manageable way to execute data
retrieval that isolates the relevant traces for event debugging

Other Changes

• The OpenScape Voice Entry deployment model has been discontinued and has been
removed from the Sales tools.

Brief Overview Page 5 November 2012

 OpenScape Voice V7

OpenScape Voice V7R0 features:

Continuous Silent Monitoring - RQ00032372/4208

(Note: This function will be released after the OpenScape GA date. Check with PM for status)
The current Silent Monitoring feature monitors only the current call of the monitored
party (provided that the monitored party is in a call during the invocation). If the
monitored party leaves the current call then the Silent Monitoring Session is terminated.
In V7, when silent monitoring is invoked, the session remains active whether the
monitored agent is in a call or not. That is: the monitoring session is not released when
the agent leaves the call, but since the agent becomes idle, the supervisor goes to the state
in which he/she hears either an announcement or silence waiting for the next call in
which that agent will be involved. The session will terminate when the supervisor or
monitoring device hangs up. If a supervisor has selected to monitor a particular agent,
they should be hearing either an announcement or silence if the agent is idle or if the
agent is not in a stable call otherwise a live call if the agent is active in one.
The party being monitored will not be aware of the monitoring of the conversation during
the life of the call.
When a Silent Monitoring Session is initiated via CSTA, two different modes shall be
supported:
• Continuous Silent Monitoring
• Per-Call Silent Monitoring
With Continuous Silent Monitoring the amount of conf ports required for a basic Silent
Monitoring Session (one monitoring party), will be increased from 3 to 5. One extra
conference port will be needed for each new monitoring party added to an existing
monitoring session. This needs to be factored into the sales and deployment plans. See
the technical documentation for details.

Continuous Silent Monitoring tone/ alert - RQ00031012/4208

(Note: This function will be released after the OpenScape GA date. Check with PM for status)
It shall be possible to configure that an initial and periodic tones are applied to all parties
(monitored party and partner) in the call during a silent monitoring session. This shall be
provision able on a subscriber basis (via OSV Assistant). The time interval between the
periodic tones shall be configurable on a per subscriber basis (via OSV Assistant). The
tones or announcements that are provided can be provisioned system wide.

Authorization Code Toll Restriction Override - RQ00031417/4017

This feature uses an authorization code to override the toll restrictions that would
normally apply to a call. It is similar to the Mobile PIN feature in the HiPath 4000.
This feature allows a user to use another phone (as in a conference room, a factory floor
or a building lobby) and with their authorization code override the call restrictions that
normally apply to the phone with their own level of calling capabilities.
This feature also allows an administrator to create groups of authorization codes. For
each group a class of restriction can be defined that contains the toll restricted traffic
types that are overridden.

Brief Overview Page 6 November 2012

 OpenScape Voice V7

Feature Access Code Support for the Directed Call Pickup Station Feature -
RQ00031910/3050

The Directed Call Pickup feature is enhanced to support the Directed Call Pickup feature
via Feature Access Code. The new feature supports pickup of alerting calls, camped-on
calls, and held calls (Keyset Manual Hold) in the same manner as the DIR-PICKUP key
in the OpenStage phones.
Closed padlock icon for secure large conferences - RQ00032718/4353
Currently while in a Large Conference, all phones (internal and/or external participants)
indicate the call as non-secure.With this feature the same rules that apply for basic calls
shall also apply to large conference calls. If all participants of the conference have secure
connections (end-to-end) with the Media Server, then their displays shall indicate the call
as secure.
Name resolution for incoming & outgoing calls - RQ00031788/4242
This feature allows OpenScape Voice to provide the capability for Computer Supported
Telephony Applications (CSTA)-enabled applications to associate a name string for
inbound or outbound calls from/to the PSTN.
This feature enhances OpenScape Voice’s CSTA interface to expose a Name Provider
capability for external devices. The Name Provider option is realized by presenting a
limited set of CSTA services and events for incoming and outgoing calls on a trunk
gateway (SIP and SIP-Q) provisioned for the CSTA Network Interface Access service. A
Name Provider application is then able to monitor calls on the Network Interface Device
(NID) and associate a calling or called party name for external (PSTN) calls.
A Name Provider application for each customer’s environment will need to be developed
and maintained by Siemens professional services.
Receiving the CSTA incoming call event, this application will perform a reverse lookup
query based on the originating address of the incoming call in a customer’s DB.

Multi Line Hunt Group Enhancement - Local ring back option (No Intercept
Announcement Treatment) – RQ34299 and RQ32193 /3501
(Note: This function will be released after the OpenScape GA date. Check with PM for status)
This enhancement addresses a new German legal requirement (Delayed Connect) which
requires that the OpenScape Voice connects an incoming call to the media server for
providing Music on Hold, tones or announcements but does not return a “200 OK” or a
CONNECT message. However, if DTMF input is needed then OSV can send 200 OK /
CONNECT - the call is then considered as being processed and not in a free-of-charge
waiting cycle any more.
In addition, there are several application scenarios where calls are queued to a Hunt
Group for ring back treatment. In certain cases the application does not want the inbound
call answered and would prefer that ring back be provided to the calling party from the
local SIP or Gateway device. The OpenScape Voice hunt group provides a configurable
option to enable the local ring back option. If the local ring back option is configured then
the MLHG Service shall not seize media server circuits but instead ringing will be
returned to the calling device. All other hunt group processes are maintained for the
queued call.
OpenScape Contact Center handles very high inbound call traffic. Currently all inbound
calls go to an initial hunt group which provides ring back until a Call Director port is
available. OSCC requires OpenScape Voice to provide the local ring back capability for

Brief Overview Page 7 November 2012

 OpenScape Voice V7

the initial hunt group to improve inbound call performance by eliminating the internal
media server messages.
Send e-mail notification upon receiving an E911 SNMP trap - 5052
This enhancement introduces the capability in CMP/Assistant to send an e-mail
notification upon receiving an E911 SNMP trap (that is.: when an E911 call is dialed
within the OpenScape Voice).

System/Architectural Features
Handle Calling Party Name delivered after SIP INVITE request – RQ33731/5130, 4917
The OpenScape Voice is enhanced to support receiving the caller identity from a Cisco
Media GW that delivers the Calling Name for the incoming call in a delayed SIP:INFO
message within the Remote-Party-ID (RPID) header field, which includes a display-name
and optionally a number.
Similarly, an incoming call may be received from a SIP-Q endpoint and the Calling Party
Name is being received in a SIP:INFO message containing a QSIG FACILITY with a
Calling Name Information Element.
For these scenarios, the OpenScape Voice shall return to the called party a message
containing BOTH the Name and Number.

Support Sending different display and authentication number in From and PAI headers –
5398, 5238

The OpenScape Voice is enhanced to allow both a display number and authenticated
number (different) be sent in an SIP INVITE to an external destination. Two new
endpoint attributes "Use SIP Endpoint Default Home DN as Authentication Number" and
"Use Subscriber Home DN as Authentication Number" are used to control which
parameter shall be used as the authentication number. The above attributes are mutually
exclusive. The existing (V5 onwards) "Send Authentication Number in ..." attributes are
used to determine which SIP header field(s) shall be used to signal the authentication
number.

Support New Operating System SLES 11 - RQ00030000/3682

This Feature introduces:
• SuSe Linux - SLES11
• OpenScape Voice Cluster software instead of HA-Linux
• RTP V2.4
IMPORTANT NOTE: IBM has advised that the IBM x3650T server will not support the
updated SUSE Linux operating system, SLES 11. As a result this server will not support
OpenScape Voice V7 or OpenScape UC Application V7 and onward. OpenScape Voice
systems using the IBM x3650T will therefore need to be migrated to a currently supported
platform during the upgrade to OpenScape Voice V7. OpenScape UC Application
deployments which are currently installed on the IBM 3650T and wish to upgrade to V7
with SLES11, must also migrate to a supported platform. Please consider the implications
of the server migration when planning the upgrade of the OpenScape Voice or OpenScape
UC Application to V7 and onwards. OpenScape Voice V7 is planned to have General
availability by the 3rd quarter 2012 (Calendar Year).
The currently available migration deployment options are:

Brief Overview Page 8 November 2012

 OpenScape Voice V7

- IBM x3550 M3 server

- Fujitsu RX200 S6
- Virtualized environment on VMware ESXi V4.0 / V4.1 /V5

In addition to the introduction of the new SLES 11 operating system, new ordering
positions have been added to the ordering tools for the SUSE SLES Upgrade Protection
License.
Novell’s operating system “SUSE Linux Enterprise Server (SLES)” is an open source
operating system (OS) and as such freeware. Nevertheless, it is required to pay a yearly
fee to Novell, if any of the Novell services shall be used (e.g. error corrections, updates
etc.). This license allows SEN to obtain Operating System software upgrades and
corrections from Novell which are then verified by SEN and included in the OpenScape
Voice product releases and updates, including off-board Media Server and OpenScape
Voice Assistant.
Starting with OpenScape Voice V7, the Operating System is delivered with a three year
Upgrade Protection license. This three year upgrade license is delivered with every
major release of OpenScape Voice. To enforce the license, The SLES Upgrade
Protection License Key will be included in the product key that is delivered by SEN’s
Central License Server (CLS).
Although it is in the customers’ interest to upgrade to the latest software versions in order
to take advantage of the new functionalities offered by the solution, some customers may
chose to remain on an older version of software, at their own risk. In these cases,
customers should take advantage of the extension of the SUSE Linux Upgrade Protection
to ensure that they can obtain updates/corrections.

Secure Authentication (for OS Mobile) - 4433

TLS connections will be allowed to be created from the OpenScape Mobile Application
towards the OpenScape Voice.

OpenScape Mobile (OSMO) Seamless Handover (RQ28039/3658)

(Note: This function will only be released after the OpenScape GA date. Check with PM for status)
The OpenScape Mobile Application uses the One Number Service Handover feature,
which is based on the CSTA Single Step Transfer Call request, to move the call between
the Desk Phone, the WiFi client, and the Cellular.
Currently, with Silent Handover, the conversation between the transferred party and the
transferring ONS subscriber is placed on hold as soon as the handover is initiated and it is
only resumed after the call is answered at the new destination. During the handover, the
transferred party does not hear hold or ringback tones. However, for calls to the PSTN
(e.g. in case of handover to cellular) the transferred party may remain several seconds
listening to silence.
With OpenScape Voice V7, the ONS handover feature is enhanced to provide a real
Seamless Handover option where the conversation between the transferred party and the
transferring ONS subscriber is maintained without interruption.
This feature also covers the enhancements to support the new Seamless Handover option
for scenarios where the ONS subscriber is either held or is holding the call.
There is no Handover feature which must be assigned to the subscriber. However,
Handover is only allowed for subscribers provisioned with the following features:
- Call Transfer
- CSTA Access

Brief Overview Page 9 November 2012

 OpenScape Voice V7

- One Number Service – The One Number Service status MUST be set to “Inbound
And Outbound”.
In order for the Silent Handover to be completely silent, the ONS subscriber MUST be
provisioned with the Music on Hold (MOH) feature. If the ONS subscriber does not have
MOH feature assigned, the transferred party may hear local music on hold (or a beep)
until the call starts alerting (or is answered at) the target device.

Serviceability, Management and Administration

Alarm Logging Enhancements – 2540
This feature implements the most important missing Application level logging changes
that were deferred from the original logging standardization requirement. To this end, the
functionality of the existing OSV logs will be maintained, expanded and improved.
Logging calls of OSV SW are modified to:
• Remove obsolete Log Categories
• Only call the OpLogReport API, (this includes obsolete RTP events)
• In-source-code documentation is added to each logging call, which will be used to
generate a logging-documentation Wiki page

X-Channel Compression and MTU Size to be Configurable Options – 4955/4802

1) X-Channel Compression
The current OSV implementation enables compression on the x-channels independent of
the configuration of co-located or geo-separated, it has been found that this compression
affects the call per second performance. Compression is needed in geo-separated
configurations where delays are encountered however in co-located clusters delay is
generally not a concern and compression therefore is a negative impact.
• A checkbox is added to the NCPE to enable or disable compression
• The default for all configurations is compression enabled.
• EZ-IP is updated to modify this new parameter
• Rapidstat is updated to report the status of compression (enabled/disabled)
2)MTU Size
The current configuration sets the MTU size for all bonds/network interfaces to 1500; this
value depending on the customer network may not be supportable. Therefore the
configuration of this parameter will be supported by NCPE at installation time and EZ-IP
for modification.
• Add a configurable option to NCPE for the MTU size for all Bonds/Network
interfaces
• The default MTU size is 1500
• Update EZ-IP to modify this new configuration parameter
• Update Rapidstat to report the MTU size for all Bonds/Network Interfaces
• Max allowable MTU size = 1500, Min allowable MTU size = 1000

Application administration and service status monitoring via Assistant - 4526

(Note: This function will only be released after the OpenScape GA date. Check with PM for status)
This feature addresses the following customer request:
1. Enables management of CSTA application identification and operational data by type
using SOAP and Assistant / CMP. Application types include OpenScape, 3rd Party
and Telefonica.
2. Display of CSTA and Application status via Assistant / CMP
Brief Overview Page 10 November 2012
 OpenScape Voice V7

3. Display of Licensing and CSTA Feature Usage data by application type via SNMP
and Assistant / CMP
4. CSTA SOAP Manager to support multiple applications. Previously support was
limited to only one SOAP application.
5. Real-time updating of Packet Filter Rules for CSTA Applications administratively
added or removed via Assistant / CMP

Configuration Profiles for SIP Providers - 4355

The OpenScape Voice profiles define a specific set of SIP Service Provider Profiles that a
craftsperson can use to establish their own specific SSP interface with a SSP.

The following SSPs are supported:

1. AT&T IP Toll-Free
2. AT&T Flex Reach
3. Verizon US IP Trunking
4. Verizon IPCC Trunking
5. Verizon EMEA IP Trunking
6. BT
7. Global Crossing
8. DTAG / T-Systems (Sonus)
9. Telefonica
10. COLT Telecom
11. Vodafone / Arcor
12. Qwest
13. Orange
14. Skype

Protection against registration peaks – 4616

In some cases the registration messages come with different Call Ids for the same
Directory Number, IP and port number, which causes the OSV to treat each message as a
new registration. With this enhancement, the OSV recognizes the flood, identifies the
sender (IP address, DN and User Agent header), alarms the event, and discards all
registration messages from the identified sender for a limited period of time.

OpenScape Voice Assistant: Usability Enhancements in Subscriber List & Features – 4472,
4716
Enhancements include the following:
• Subscriber Features Enhancements: allowing the user to directly specify the desired
Feature status.
• Additional sorting options for the Subscribers List
• Switch-Wide Settings account codes enhancements
• E164/Destination Codes clone functionality
• Multiple Feature selection
• Executive/Assistant Wizard Enhancements

Brief Overview Page 11 November 2012

 OpenScape Voice V7

• Provide Device Profile selection in the ‘Quick Add Subscriber’ screen

Synchronization of data of OpenScape Branch from OpenScape Voice – 3641/4787

Currently data such as Multi Line Hunt Groups and Emergency list have to be
provisioned separately on OSB and OSV to support these features in the standalone
mode. Although the provisioning of the MLHG, MLHG member and Emergency List
data provisioning is still supported on OSB, the user does not have to provision these
features on OSB. Instead provisioning on OSV via OSV Assistant will synchronize the
data on the OSB(s) as needed. The data provisioned via Mass Provisioning gets
synchronized periodically by the OSV Assistant. This ensures that all the plausibility
checks are done ensuring the data on OSV and OSB is same for these features.

Miscellaneous OpenScape Voice Assistant enhancements – 4857, 5124

• This feature introduces the RapidStat initiation via SOAP interface in the OpenScape
Voice dashboard. Using this approach the RapidStat in dashboard will behave like the
“Check Node Health” in the Software Activation screen.
• The interface with HiPath User Management will include the MAC Address of the phone.
This will provide the capability to activate the phone without entering the Directory
Number on the phone.
• Group the options that are offered as buttons in the OSV Subscriber list in the Assistant
to improve usability.

Other changes

Subscription Licensing (SSL) support

OpenScape Voice V7 supports the SSL V2 licensing mechanism for high watermark and
automated reporting of license usage data to CMP. It is important to note that in order to
enable the characteristics and enhancements of SSL V2, all deployed components that
support SSL must be at the levels indicated in the solution product matrix for OpenScape
Solution Set V7. There is no backward compatibility for automated usage reporting.
Transmission of the automated usage reports requires that the customer’s network be
connected to Service’s secure SSDP system (Smart Services Delivery Platform); SSDP
needs a simple IP connection via the Internet. See the SSL Sales Information document
for details on SSL V2.

SuSe Linux (SLES) Upgrade Protection License activation

Starting with OpenScape Voice V7, the Operating System is delivered with a three year
Upgrade Protection license. This three year upgrade license is delivered with every
major release of OpenScape Voice. To enforce the license, the SLES Upgrade
Protection License Key will be included in the product key that is delivered by SEN’s
Central License Server (CLS).
Brief Overview Page 12 November 2012
 OpenScape Voice V7

As of OpenScape Voice V7, to ensure compliance with reporting of license usage, when
activating a license file which includes a base license or an upgrade from one major
release to V7, the Common Licensing System (CLS) will verify that the SuSe license has
also been activated. If you have not done so, the CLS will prompt you to activate the
Upgrade Protection license(s) before the license key can be generated.
See the “Licensing” section for additional details.

Brief Overview Page 13 November 2012

 OpenScape Voice V7

Configuration Overview

Brief Overview Page 14 November 2012

 OpenScape Voice V7

Customer Benefits

Elevator Pitch
OpenScape Voice is a SIP-based, software application running on commercial servers. It
provides industry leading scalability and carrier grade reliability, meaning a rock solid
architecture with no single point of failure, and in the event of a single node failure, 100% of the
call load traffic can be carried over to the surviving node. It is the only carrier grade reliable
next generation enterprise voice solution on the market today. It can be deployed in any mid to
large size enterprise network scenario, from a single site on-premise solution, to the world’s
largest private cloud solution i using geographically redundant servers that provide service to
hundreds of geographically remotes sites.
As a next generation enterprise voice solution it offers up to a 43% cost savings over traditional
PBX system. The solution is security hardened, tested and verified by an independent testing
company that specialized in internet security.
OpenScape Voice is a next generation SIP-based voice application, with carrier grade reliability,
industry leading scalability, and security hardened. All this adds up to a lower overall total cost
of ownership (TCO) and a clear and easy to understand return on investment (ROI).
OpenScape Voice customer benefits are summarized in the following table:
Attributes Benefits
SIP-based software foundation • Combines all enterprise communications into a single
for enterprise Voice and Unified manageable interface
Communications and • Unified architecture with shared services for ease of
Collaboration (OpenScape UC integration
Suite) applications
• Built as a true Next Gen SIP-based software application -
not “bolted-on” or wrapped around a legacy product
• Hardware independent – allowing customers to rid the
technology curve
Open Communications • Standards Based Approach
Architecture foundation for • Multivendor integrations w/o “rip and replace”
OpenPath solutions
• Multivendor Services (OpenScape Fusion)
• No vendor lock-in for services

Designed for data center / IT • Virtualization of applications

environment • Flexible deployment models – private / public cloud,
premise based and hybrid models
• Green IT

OpenSOA Framework • Pre-built in integrations for Outlook and Lotus Notes

• Integrations for social media and groupware
rd
• SDKs / API and developer portal for 3 party application
innovations

Brief Overview Page 15 November 2012

 OpenScape Voice V7

Attributes Benefits
SIP Session Multi-media Engine • Real-time multi-media control, session detail recording,
and coordination for UCC services
Carrier Grade Reliability • Massively scalable allowing for flexible deployment
options
• Five 9’s reliability – maintain high level of business
continuity
• Geographical node separation for simplified Disaster
Recovery planning
For a complete overview of all marketing collateral relating to OpenScape Voice please visit the
Marketing Home page on the Intranet.
For OpenScape solutions and related OpenScape Solution Set V7 Marketing material, please
visit the marketing page for Unified Communications. Here you will find customer facing
presentations, messaging grids with key value propositions, and links to OpenScape Voice Sales
Playbook.
i
Federal Republic of Germany Employment Agency

Brief Overview Page 16 November 2012