OpenScape Business V1, Last Changes, Description, Issue 2

Siemens Enterprise Communicationswww.siemens-enterprise.com

DocumentationOpenScape Business V1, Last Changes

P31003P3010T101017618 09/2013Siemens Enterprise Communications GmbH & Co. KG.2013

OpenScape Business V1Last ChangesDescription

A31003-P3010-T101-2-7618

Siemens Enterprise Communicationswww.siemens-enterprise.com

Our Quality and Environmental Management Systems are implemented according to the requirements of the ISO9001 and ISO14001 standard certified by an external certification company.

Copyright Siemens Enterprise Communications GmbH & Co. KG 2013Hofmannstr. 51, D-80200 Mnchen

Siemens Enterprise Communications GmbH & Co. KG is a Trademark Licensee of Siemens AG

Reference No.: A31003-P3010-T101-2-7618

The information provided in this document contains merely general descriptions or characteristics of performance which in case of actual use do not always apply as described or which may change as a result of further development of the products. An obligation to provide the respective characteristics shall only exist if expressly agreed in the terms of contract. Availability and technical specifications are subject to change without notice.

OpenScape, OpenStage and HiPath are registered trademarks of Siemens Enterprise Communications GmbH & Co. KG. All other company, brand, product and service names are trademarks or registered trademarks of their respective holders.

A31003-P3010-T101-2-7618, 09/2013OpenScape Business V1, Last Changes, Description 3

1 About this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 I30848: Web Security for UC Smart / UC Suite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52.1 Chapter 19.5.1 Web Access Filter (UC Suite) Connections to Web Server. . . . . . . . . . . . . . . . . . . . . . . . . . 52.2 Chapter 19.5.1.1 How to configure Web Access the connections to the Web Server (UC Suite) . . . . . . . . . 52.3 Chapter 19.5.1.2 How to configure the connections to the Web Server (UC Smart) . . . . . . . . . . . . . . . . . . . 6

3 I30948: Valid Values for Node ID from 1 to 100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73.1 Chapter 4.7.2.3 How to Activate or Deactivate Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73.2 Chapter 5.8.2.3 How to Activate or Deactivate Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73.3 Chapter 27.3.1.11 Basic Settings > Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

4 I31066: Boards TS2/TS2R and TST1/TST1R not suppoerted in OpenScape Business X3W/R . . . . . . . 104.1 Chapter 9.1 Hardware Expansion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

5 I31112: Incorrect Virtual Disk Format Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155.1 Chapter 2.2 Installation in a virtual environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

6 I31334: Microsoft Exchange Server 2003 not supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176.1 Chapter 12.4.1 Presence Status (UC Suite) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176.2 Chapter 12.4.1.1 How to Configure the Exchange Calendar Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . 186.3 Chapter 12.5.1.2 How to Enable or Disable the Integrated Public Exchange Folder . . . . . . . . . . . . . . . . . 196.4 Chapter 27.4.3.7 OpenScape Business UC Suite > External Providers Config . . . . . . . . . . . . . . . . . . . . . 20

7 I31436: No UC Features with Open Numbering Scheme. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227.1 Chapter 20 Networking OpenScape Business . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227.2 Chapter 20.4.2 Dial Plan in the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237.3 Chapter 20.6.3 / 20.6.6 / 20.6.9 / 20.6.12 Szenario 1/2/3/4: Network-wide Features . . . . . . . . . . . . . . . . . 247.4 Chapter 2.6.14 Scenario 5: Network-wide Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267.5 Chapter 20.6.16 Scenario 7: Open Numbering in OpenScape Business X3/X5/X8 Networks . . . . . . . . . . 28

Contents

About this Document

A31003-P3010-T101-2-7618, 09/20134 OpenScape Business V1, Last Changes, Description

1 About this Document This document provides you with information on the latest changes and additions to the administrator and user documentation for OpenScape Office V3.

Examples: Changes due to ICTS (International Case Tracking System) tickets Additions due to new features

This information, which was received after the cut-off date, was not available at press time and could therefore not be considered in the current issues of the administrator and user documentation. It will automatically be taken into account in subsequent editions.

Display Conventions

This document uses the following display conventions to indicate changes and additions.

Related Topics

Purpose Presentation Example

Changes / Deletions red and crossed out Only IP phones (system clients) are supported for this.

Additions / Corrections green Only internal extensions for which the first and last names of the subscriber are entered in the internal directory are supported here.

I30848: Web Security for UC Smart / UC SuiteChapter 19.5.1 Web Access Filter (UC Suite) Connections to Web Server2 I30848: Web Security for UC Smart / UC Suite

2.1 Chapter 19.5.1 Web Access Filter (UC Suite) Connections to Web Server

The access of clients to the communication system can be restricted by web access filters. The web access filter controls the permissions of clients such as myPortal for Mobile/Tablet and for OpenStage XML. It defines how these clients access the web via http or https. The connections from the clients (e. g. myPortal for Mobile/Tablet) to the internal Web Server of the communication system can be either encrypted (HTTPS) or unencrypted (HTTP).

NOTICE: By setting or changing the parameters of this filter, the functionality of the communication system can be restricted considerably (e.g., administration via LAN becomes impossible) or otherwise unauthorized persons can be granted access to sensitive information. With unencrypted connections to the Web Server unauthorized persons could have access to sensitive infor-mation! For security reasons, it is strongly recommended that only an encrypted connection (HTTPS) be used when working with myPortal for Mobile/Tablet over the Internet. For myPortal for OpenStage (XML) an unencrypted connection (HTTP) is required.

2.2 Chapter 19.5.1.1 How to configure Web Access the connections to the Web Server (UC Suite)

Prerequisites You are logged on the WBM with the Expert profile.

Step by Step 1. In the navigation bar, click Expert Mode.

2. In the navigation tree, click Telephony > Security.

3. Navigate in the menu tree to Web Access.

4. Select the following check boxes in the Web Access window: Configure the connections to the Web Server:

Access via HTTPS, if you want to restrict access to the secure HTTPS protocol.

If you want to enable encrypted connections, select the check box HTTPS.

Affected Documentation Administrator Documentation

Issue 21

Reference No. A31003-P3010-M100-21-76A9A31003-P3010-T101-2-7618, 09/2013OpenScape Business V1, Last Changes, Description 5

I30848: Web Security for UC Smart / UC SuiteChapter 19.5.1.2 How to configure the connections to the Web Server (UC Smart) Access via HTTP, if you want to allow access via the HTTP protocol.

If you want to enable unencrypted connections, select the check box HTTP.

5. If necessary, enable Save login data to device, if you want to store the login data in the device. With it the login data are stored in the Web Browser of the mobile phone via so-called cookies.

6. Click Save.

2.3 Chapter 19.5.1.2 How to configure the connections to the Web Server (UC Smart)



2. Click in the navigation tree on Applications > UC Smart > Basic Settings.

3. Make sure that UC Smart is Active.4. Configure the connections to the Web Server:

If you want to enable encrypted connections, select the check box HTTPS.

If you want to enable unencrypted connections, select the check box HTTP.

5. Click Apply, followed by OK. A31003-P3010-T101-2-7618, 09/20136 OpenScape Business V1, Last Changes, Description

I30948: Valid Values for Node ID from 1 to 100Chapter 4.7.2.3 How to Activate or Deactivate Networking3 I30948: Valid Values for Node ID from 1 to 100

3.1 Chapter 4.7.2.3 How to Activate or Deactivate Networking

Prerequisites You are in the Summary window.

Step by Step 1. If the communication system is to be networked with other communication systems:

a) Select the Network Integration check box.

b) In the Node ID field for the communication system, enter a node ID that is unique in the internetwork (digits from 0 through 999 1 through 100 are possible).

2. If the communication system is not to be networked with other communication systems, leave the Network Integration check box disabled.

3. Click OK & Next.

Next steps Configure the station data.

3.2 Chapter 5.8.2.3 How to Activate or Deactivate Networking

Prerequisites You are in the Summary window.


Issue 21


I30948: Valid Values for Node ID from 1 to 100Chapter 27.3.1.11 Basic Settings > GatewayStep by Step 1. If the communication system is to be networked with other communication systems:

a) Select the Network Integration check box.

b) In the Node ID field for the communication system, enter a node ID that is unique in the internetwork (digits from 0 through 999 1 through 100 are possible).

2. If the communication system is not to be networked with other communication systems, leave the Network Integration check box disabled.

3. Click OK & Next.

Next steps Configure the station data.

3.3 Chapter 27.3.1.11 Basic Settings > Gateway

Parameter Description of Tabs: Edit Gateway Properties

Parameters Description

General

Customer name Freely definable name for the customer; only for informational purposes (optional)

Value range: max. 15 characters

Contract number Freely definable string for informational purposes only (optional)

Value range: unlimited

System name Freely definable name for the communication system. This string appears on the display of all system telephones.

Value range: max. 24 characters

Gateway Location Freely definable string to specify the physical location of the communication system. This information helps a service technician to find the communication system when physical access to the communication system is required. (optional)

Value range: unlimited A31003-P3010-T101-2-7618, 09/20138 OpenScape Business V1, Last Changes, Description

I30948: Valid Values for Node ID from 1 to 100Chapter 27.3.1.11 Basic Settings > GatewayContact Address Freely definable string to specify the person to be contacted if problems arise with the communication system. (optional)

Value range: unlimited

System Country Code Selection of the country in which the communication system is operated; changing the system country code requires a reboot, which is carried out automatically.

Gateway IP address Displays the IP address of the communication system, e.g., 192.168.1.2.

Gateway Subnet Mask Displays the subnet mask of the communication system, e.g., 255.255.255.0.

International Prefix Entry of the prefix for international calls, e.g., 00 in Germany or 011 in the U.S.

National Prefix Entry of the prefix for national calls, e.g., 0.

Brand Selection of the purchased product (OpenScape Business or Octopus or FX)

Gateway Location

Country code Enter the country code prefix, e.g., 49 for Germany or 1 for the U.S.

Local area code Enter the local area code (e.g., 89 for Munich)

PABX number Specifies the PABX number (central number without station DID), e.g., 7007

Network Parameters

Node ID Each node in a networked system must be assigned a unique node ID. This enables the individual nodes in a networked system to be uniquely identified.

Value range: 0 to 100 1 to 100

Parameters DescriptionA31003-P3010-T101-2-7618, 09/2013OpenScape Business V1, Last Changes, Description 9

I31066: Boards TS2/TS2R and TST1/TST1R not suppoerted in OpenScape Business X3W/RChapter 9.1 Hardware Expansion4 I31066: Boards TS2/TS2R and TST1/TST1R not suppoerted in OpenScape Business X3W/R

4.1 Chapter 9.1 Hardware Expansion

The hardware expansion details refer to the OpenScape Business X3R/X3W, OpenScape Business X5R/X5W and OpenScape Business X8 communication systems.

Hardware Expansion for OpenScape Business

The following table lists the maximum number of time-division multiplex channels that the different boards require. A distinction is made here between: Static assignment

Time-division multiplex channels are assigned statically for trunk and tie-traffic boards. This ensures that all calls can be processed.

Dynamic assignment Time-division multiplex channels are subject to dynamic assignment in subscriber line modules. The channels are seized with every call and released at the end of each call. The current number of time-division multiplex channels required is determined by the number of active stations.

Static/dynamic assignment. For boards with S0 interfaces, the way in which the time-division multiplex channels are assigned depends on the actual use of the individual S0 interfaces. The channels are assigned statically if the S0 interface is used for the ISDN trunk connection (ISDN trunk). The channels are assigned dynamically if the S0 interface is used for the ISDN station connection.

OpenScape Business X8 provides PCM highway trunk groups with 2 x 4 PCM highways for each peripheral board slot. There are 32 time-division multiplex channels available for each PCM highway. If all of these channels are busy, no further call requests can be accepted. To guarantee that the communication system operates without blocking, make sure when performing configuration that the boards on a PCM segment do not require more than the number of time-division multiplex channels available. For detailed information on the distribution of the PCM highways and the boards installed in OpenScape Business X8, see OpenScape Business V1, Service Documentation, Installing OpenScape Business X8.

Affected Documentation Installing the Hardware, Service Documentation

Issue 20

Reference No. A31003-P3010-S100-20-7620

System Box Maximum configuration

OpenScape Business X8 system box 2 A31003-P3010-T101-2-7618, 09/201310 OpenScape Business V1, Last Changes, Description

I31066: Boards TS2/TS2R and TST1/TST1R not suppoerted in OpenScape Business X3W/RChapter 9.1 Hardware ExpansionRegardless of which boards are installed in OpenScape Business X3R/X3W, OpenScape Business X5R/X5W, blocking-free operation is ensured at all times.

Peripheral board

Part Number Maximum number of

time-division multiplex channels required

Time-division

multiplex channel

assignment

Use in OpenScape Business

X3R X3W X5R X5W X8

4SLA1 S30810-Q2925-X100

S30810-Q2923-X200

4 Dynamic X X

8SLA1 S30810-Q2925-X

S30810-Q2923-X100

8 Dynamic X X

8SLAR1 S30810-K2925-Z 8 Dynamic X X

16SLA1 S30810-Q2923-X 16 Dynamic X X

DIU2U1 S30810-Q2216-X (For U.S. only)

48 Static X

DIUN21 S30810-Q2196-X 60 Static X

DIUT2 S30810-Q2226-X100

60 Static X

IVMN81 S30122-H7688-X200

8 Dynamic X

IVMNL S30122-H7688-X 24 Dynamic X

IVMP4 S30122-Q7721-X 4 Dynamic X X

IVMP4R S30122-K7721-F 4 Dynamic X X

IVMS8N S30122-Q7379-X200

8 Dynamic X X

IVMS8NR S30122-K7379-Z200

8 Dynamic X X

SLA16N1 S30810-Q2929-X100

16 Dynamic X

SLA24N1 S30810-Q2929-X 24 Dynamic X

SLAD4 S30810-Q2956-X100

4 Dynamic X X

SLAD8 S30810-Q2956-X200

8 Dynamic X X

SLAD8R S30810-K2956-X300

8 Dynamic X X

SLAD16 S30810-Q2957-X 16 Dynamic X X

SLC16N S30810-Q2193-X100

642 Dynamic XA31003-P3010-T101-2-7618, 09/2013OpenScape Business V1, Last Changes, Description 11

I31066: Boards TS2/TS2R and TST1/TST1R not suppoerted in OpenScape Business X3W/RChapter 9.1 Hardware ExpansionSLCN S30810-Q2193-X300

1282 Dynamic X

SLMA21 S30810-Q2246-X 24 Dynamic X

SLMA81 S30810-Q2191-C100

8 Dynamic X

SLMA241 S30810-Q2191-C300

24 Dynamic X

SLMAE81 S30810-Q2225-X100

8 Dynamic X

SLMAE241 S30810-Q2225-X200

24 Dynamic X

SLMAV8N S30810-Q2227-X300

8 Dynamic X

SLMAV24N S30810-Q2227-X400

24 Dynamic X

SLMO8N S30810-Q2168-X300

163 Dynamic X

SLMO24N S30810-Q2168-X400

483 Dynamic X

SLMO81 S30810-Q2901-X100

163 Dynamic X

SLMO241 S30810-Q2901-X 483 Dynamic X

SLU8N S30817-Q922-A401

16 Dynamic X X

SLU8NR S30817-K922-Z401

16 Dynamic X X

STLS21 S30817-Q924-B313

4 dynamic/static

X X

STLS41 S30817-Q924-A313

8 dynamic/static

X X

STLS4R1 S30817-Q924-Z313

8 dynamic/static

X X

STLSX2 S30810-H2944-X100

4 dynamic/static

X X

STLSX4 S30810-H2944-X 8 dynamic/static

X X

STLSX4R S30810-K2944-Z 8 dynamic/static

X X

Peripheral board



Time-division

multiplex channel

assignment


X3R X3W X5R X5W X8 A31003-P3010-T101-2-7618, 09/201312 OpenScape Business V1, Last Changes, Description

I31066: Boards TS2/TS2R and TST1/TST1R not suppoerted in OpenScape Business X3W/RChapter 9.1 Hardware ExpansionSTMD3 S30810-Q2217-X10

16 dynamic/static

X

TCAS-2 S30810-Q2945-X (for selected countries only)

60 Static X

TCASR-2 S30810-K2945-X (for selected countries only)

60 Static X

TLANI2 S30810-Q2953-X100

S30810-K2953-X182 (For Brazil only)

2 Static X X

TLANI4 S30810-Q2953-X


4 Static X X

TLANI4R S30810-K2953-X200


4 Static X X

TLANI8 S30810-Q2954-X100

S30810-Q2954-X101 (For inter-national markets only)


8 Static X X

TM2LP1 S30810-Q2159-Xxxx

8 Static X

TMANI S30810-Q2327-X

S30810-Q2327-X1 (For interna-tional markets only)


8 Static X

Peripheral board



Time-division

multiplex channel

assignment


X3R X3W X5R X5W X8A31003-P3010-T101-2-7618, 09/2013OpenScape Business V1, Last Changes, Description 13

I31066: Boards TS2/TS2R and TST1/TST1R not suppoerted in OpenScape Business X3W/RChapter 9.1 Hardware ExpansionRelated Topics

TMC161 S30810-Q2485-X 16 Static X

TMCAS1 S30810-Q2938-X 30 Static X

TMCAS2 S30810-Q2946-X (for selected countries only)

60 Static X

TMDID4 S30810-Q2197-T (for selected countries only)

8 Static X

TMEW2 S30810-Q2292-X100

4 Static X

TS2 S30810-Q2913-X100

30 Static X X

TS2R S30810-K2913-Z100

30 Static X X

TST1 S30810-Q2919-X 24 Static X X

TST1R S30810-K2919-Z 24 Static X X1 This board is being discontinued and can no longer be ordered. However, it can still

be used in the communication systems of the OpenScape Business communication platform.

2 A time-division multiplex channel is required if a call is conducted via the "home cordless board" of a mobile telephone. If a call is conducted via a "current-location Cordless board", additional time-division multiplex channels are necessary.

3 The maximum possible number of masters and slaves is taken into account. 4 The TMDID board only uses the first half of a PCM segment, which means that up to

64 channels are available per PCM segment for TMDID static time-division multiplex channels. To guarantee that the communication system operates without blocking when using the TMDID, the boards on a PCM segment must not occupy more than 64 static time-division multiplex channels. Examples for a PCM segment: 2 x TMDID + 1 x DIU2U = 64 static time-division multiplex channels = approved equipment. 1 x TMDID + 1 x TMANI + 1 x DIUT2 = 76 static time-division multiplex channels = unapproved equipment. 1 x TMDID + 2 x SLMO2 = 8 static and 96 dynamic time-division multiplex channels = approved equipment.

Peripheral board



Time-division

multiplex channel

assignment


X3R X3W X5R X5W X8 A31003-P3010-T101-2-7618, 09/201314 OpenScape Business V1, Last Changes, Description

I31112: Incorrect Virtual Disk Format TypeChapter 2.2 Installation in a virtual environment5 I31112: Incorrect Virtual Disk Format Type

5.1 Chapter 2.2 Installation in a virtual environment

The communication software can run in a virtual environment.

To set up a virtual environment, the virtualization software (host operating system) must be first installed and configured on the server PC. Linux is then installed as a guest operating system. Within the Linux operating system, the communication software is installed last.

For licensing in a virtual environment, an Advanced Locking ID is generated and used for the softswitch instead of the MAC address.

The following virtualization software has been released: VMware vSphere Version 4 or 5 including the latest patches

For details on the hardware requirements of the physical server PC, refer to the "VMware Compatibility Guide and the "VMware Management Resource Guide" at www.vmware.com.

To determine the hardware requirements at the physical server PC, VMware offers an online search function for certified and tested hardware under "Compat-ibility Guides" on their Internet homepage at:

http://www.vmware.com/resources/guides.html The description of the installation and configuration of the virtualization software is not part of this documentation. The installation process for Linux and the communication software in a virtual environment is exactly the same as for a direct installation on the server PC.

The following minimum requirements must be configured for Linux and the communication software in the virtual environment:

Affected Documentation Linux Server, Installation Guide

Issue 3

Reference No. A31003-P3010-J103-3-7631

Parameters VM Settings

Guest Operating System SLES 11 SP2 64-bit

VM HD Capacity 200 GB

Virtual Disk Mode Default

Virtual Disk Format Type Thin Provisioning (fixed dynamic HD Capacity) or

Thick Provisioning (dynamic fixed HD Capacity)

vCPUs 2A31003-P3010-T101-2-7618, 09/2013OpenScape Business V1, Last Changes, Description 15

I31112: Incorrect Virtual Disk Format TypeChapter 2.2 Installation in a virtual environmentThe VM (Virtual Machine) may utilize the CPU up to 70%; values above that can result in erratic behavior.

The following VMware vSphere features are supported: Thin Provisioning High Availability (HA) VMotion Data Recovery (VDR) DRS (Automatic VMotion) Storage VMotion

The following VMware vSphere features are not supported: Fault tolerance

The screen saver for the virtual environment must be disabled.

vCPUs Shares (High/Normal) High

vCPU Reservation 2 GHz

vCPU Limit Unlimited

VM Memory 2 GB

VM Memory Shares (High/Normal) Normal

VM Memory Reservation 2 GB

VM Memory Limit Unlimited

Number of vNICs 1

VMware Manual MAC Used NO

Virtual Network Adapter Support YES, vmxnet3 driver

VMware Tools Installation YES

Parameters VM Settings A31003-P3010-T101-2-7618, 09/201316 OpenScape Business V1, Last Changes, Description

I31334: Microsoft Exchange Server 2003 not supportedChapter 12.4.1 Presence Status (UC Suite)6 I31334: Microsoft Exchange Server 2003 not supported

6.1 Chapter 12.4.1 Presence Status (UC Suite)

The Presence status indicates the availability of internal subscribers (including mobile stations) in the Favorites list, the internal directory, the virtual conference room and via voicemail announcements. In addition, the Presence status controls the availability of internal subscribers with status-based call forwarding, rule-based call forwarding and the personal AutoAttendant.

As a subscriber, you can change your Presence status in myPortal for Desktop and myPortal for Outlook or via the menu controls of the voicemail box. Deacti-vating call forwarding at the telephone returns you to the Office presence status. For every change in the Presence status (except for Office and CallMe), you also define the scheduled time of your return to the Office or CallMe status.

As a subscriber, you can select the following statuses: Office Meeting Sick Break Gone Out Vacation Lunch Gone Home Do Not Disturb

(not available for Mobility Entry or MULAP)

...

Automatic Update of Presence Status via Outlook / iCal Appointments

As a subscriber, you can automatically control your Presence status via appoint-ments (but not for those that have been proposed or declined) by using the specific keywords in the Subject line. You can choose between the following calendars:


Issue 21


I31334: Microsoft Exchange Server 2003 not supportedChapter 12.4.1.1 How to Configure the Exchange Calendar Integration Exchange calendar (on the Exchange Server)The automatic update of the presence status via Outlook appointments occurs independently, regardless of whether or not your PC is running. The administrator must configure the Exchange Calendar Integration for this function.

INFO: Appointments from a Microsoft Exchange Server 2003 that were created with Outlook Web Access are not visible for the system.

Outlook calendarThe automatic update of the presence status via Outlook appointments requires myPortal for Desktop or myPortal for Outlook to have been started on your PC.

iCal calendar (myPortal for Desktop)

You can use the following keywords: Meeting Sick Break Gone Out Vacation Lunch Gone Home

The keywords depend on the language set for the user interface. The keywords may be located anywhere in the Subject line. If the Subject line contains more than one such keyword, only the fist takes effect. When this function is enabled, your Presence status changes automatically at the start and end time of the relevant appointment. The check for calendar appointments occurs at 30-second intervals.

NOTICE: When enabling this function, please bear in mind that any appointments with corresponding keywords in the Subject line could lead to undesirable changes in your Presence status. Consequently, you may nee to change the Subject line if needed.

...

6.2 Chapter 12.4.1.1 How to Configure the Exchange Calendar Integration



2. In the navigation tree, click on Applications > UC Suite.

3. Click Servers in the menu tree. A31003-P3010-T101-2-7618, 09/201318 OpenScape Business V1, Last Changes, Description

I31334: Microsoft Exchange Server 2003 not supportedChapter 12.5.1.2 How to Enable or Disable the Integrated Public Exchange Folder4. Click on the Exchange tab.

5. Enable the Exchange Calendar Integration check box.

6. Select one of the following options in the "Exchange Calendar Integration" area, depending on the version of Microsoft Exchange Server being used:

For Microsoft Exchange Server 2010: Enter the Server URL (e.g., https:///ews/exchange.asmx).

For Microsoft Exchange Server 2007or Microsoft Exchange Server 2003: Enter the Server URL (e.g., https:///exchange), User Name and Password of the Exchange calendar.

INFO: If the integration with the specified in the Server URL does not work, enter the ... instead.

7. Enter the User Name of the Exchange Calendar in the Exchange Calendar Integration area.

8. Enter the Password of the Exchange Calendar in the Exchange Calendar Integration area.

9. Click Save.

INFO: Information on the usage of Microsoft Exchange Server can be found under: http://wiki.siemens-enter-prise.com.

6.3 Chapter 12.5.1.2 How to Enable or Disable the Integrated Public Exchange Folder



2. In the navigation tree, click on Applications > UC Suite.

3. Click Servers in the menu tree.

4. Click on the Exchange tab.

5. Select one of the following options:

If you want to activate the integration of the public Exchange folder, select the Enable search in public Exchange folder check box.

If you want to deactivate the integration of the public Exchange folder, clear the Enable search in public Exchange folder check box. A31003-P3010-T101-2-7618, 09/2013OpenScape Business V1, Last Changes, Description 19

I31334: Microsoft Exchange Server 2003 not supportedChapter 27.4.3.7 OpenScape Business UC Suite > External Providers Config6. If you want to activate the integration of the public Exchange folder, select one of the following options in the "Enable search for Exchange public folder" area, depending on the version of Microsoft Exchange Server being used:

For Microsoft Exchange Server 2010: Enter its Server URL (e.g., https:///ews/exchange.asmx).

For Microsoft Exchange Server 2007 or Microsoft Exchange Server 2003: Enter its Server URL (e.g., https:///public).

INFO: If the integration with the specified in the Server URL does not work, enter the ...... instead.

7. If you want to activate the integration of the public Exchange folder, enter the User Name for accessing the public Exchange folder in the "Enable Exchange calendar integration" area.

8. If you want to deactivate the integration of the public Exchange folder, enter the Password for accessing the public Exchange folder in the "Enable Exchange calendar integration" area.

9. Click Save.

INFO: Information on the usage of Microsoft Exchange Server can be found at http://wiki.siemens-enterprise.com.

6.4 Chapter 27.4.3.7 OpenScape Business UC Suite > External Providers Config

Parameter Description of Tabs: Contact Provider > Exchange

Parameter Description of Tabs: Contact Provider > LDAP


Add/Edit Input of access data for the Exchange Server. In a Microsoft environment, the Active Directory Server (ADS) or the Exchange Server also serves as the LDAP server.

Name Name of this external offline directory.

Server address DNS name or IP address of the Exchange server.

User Name / Password User name and password for accessing the remote Exchange server. A31003-P3010-T101-2-7618, 09/201320 OpenScape Business V1, Last Changes, Description

I31334: Microsoft Exchange Server 2003 not supportedChapter 27.4.3.7 OpenScape Business UC Suite > External Providers ConfigParameter Description of Tabs: Contact Provider > MSSQL

Parameter Description of Tabs: Calendar Provider > Exchange


Add/Edit Access data of the LDAP server.

Name Name for this external offline directory

Server address DNS name or IP address of the LDAP server.

Port Port number of the external LDAP server

User Name / Password User name and password for accessing the remote LDAP server.

LDAP Base Distinguished Name LDAP base distinguished name, e.g., dc=example-for-a-domain, dc=net.

Title, First Name, Last Name, Business Ph. 1, Business Ph. 2, Private, Mobile/Cell, Company, Company Ph., Postal Address, State or Region, Country, Post Code, E-mail, Pager, Facsimile Phone Number, XMPP ID and City

During the configuration of an external offline directory, the administrator can adapt the mapping of fields to the names of the used LDAP server. Deleted fields are ignored when searching for names via phone numbers. The search always occurs with the last 4 positions of the phone number preceded by a wildcard. You can deactivate the search for names via phone numbers for incoming calls. Enter the corresponding field name of the LDAP server in each case.


Add/Edit Access data of the Microsoft SQL Server

Name Name for this external offline directory

Server address DNS name or IP address of the Microsoft SQL Server

User Name / Password User name and password for accessing the Microsoft SQL server

DB Name Name of the database.


Exchange Calendar Integration The calendar integration is used for the automatic creation of Outlook appointments under Windows when the user is absent. If the Outlook appointments are not to be stored in the local PST file of the user, but on the Exchange server instead, the requisite access data must be entered here.

Enable Exchange calendar integration

Enable the Exchange calendar integration

Server URL Microsoft Exchange the Server 2010: e.g., https:///ews/exchange.asmx.

Microsoft Exchange Server 2007, Microsoft Exchange Server 2003: e.g., https:///exchange, User Name and Pof the Exchange calendar. If the integration with does not work, enter the < IP address>. A31003-P3010-T101-2-7618, 09/2013OpenScape Business V1, Last Changes, Description 21

I31436: No UC Features with Open Numbering SchemeChapter 20 Networking OpenScape Business7 I31436: No UC Features with Open Numbering Scheme

7.1 Chapter 20 Networking OpenScape Business

The communication system enables the networking of OpenScape Business X3/X5/X8, OpenScape Business S, HiPath 4000 and OpenScape Voice. In a homogeneous network, subscribers can now use features such as the presence status, voicemail, conferencing and much more in exactly the same way as was originally possible with only a single OpenScape Business communication system.

Possible Networks:

Pure voice network of OpenScape Business X3/X5/X8 OpenScape Business X3/X5/X8 network (optionally with UC Suite or UC

Smart) and OpenScape Business S (always with UC). OpenScape Business X3/X5/X8 with HiPath 4000 (UC functionality in

OpenScape Business only under certain conditions) OpenScape Business X3/X5/X8 with OpenScape Voice (without UC function-

ality in OpenScape Business) Networking with certified third-party applications and external systems via SIP

trunks.

Supplemented with a comprehensive set of features in the area of voice networking, medium-size companies now have access to a solution that offers a rich portfolio of features.

Configuring an IP network is a complex task and should only be performed by experienced service technicians.

INFO: For all UC Suite-based networking scenarios described here, closed numbering is assumed. This means that the dial plan of the internal station numbers must be unique.In a UC Suite-based internetwork without unified communica-tions, both closed and open numbering can be used. Consequently, closed numbering should always be selected for any newly created network (with UC functionality) to allow for future expansion requests by the customer.

For all networking scenarios with Unified Communications features (e. g. UC Smart or UC Suite, Application Launcher, Gate View, Open Directory Service), closed numbering is assumed. Networking scenarios without Unified


Issue 21

Reference No. A31003-P3010-M100-21-76A9 A31003-P3010-T101-2-7618, 09/201322 OpenScape Business V1, Last Changes, Description

I31436: No UC Features with Open Numbering SchemeChapter 20.4.2 Dial Plan in the NetworkCommunications features both closed and open numbering can be used. Conse-quently, closed numbering should always be selected for any newly created network (with UC functionality) to allow for future expansion requests by the customer.

INFO: Configuring an IP network is a complex task and should only be performed by experienced service technicians.

A network of OpenScape Business with the following systems is not supported: HiPath 3000 HiPath 5000 RSM OpenScape Office MX OpenScape Office LX

The migration from HiPath 3000 to OpenScape Business is described in the "Migration" chapter.

7.2 Chapter 20.4.2 Dial Plan in the Network

The dial plan is an important prerequisite for networking. The complexity of the internetwork configuration depends on the dial plan. OpenScape Business generally supports open and closed numbering in an internetwork. It should be noted, however, that the full scope of UC features can only be used only with closed numbering.

Closed numbering

In the case of closed numbering, a station in the internetwork is uniquely identified by the station number. Each station in the internetwork can reach another station by directly dialing its station number.

The advantage of closed numbering is that you do not have to dial a node number to reach another station in another networked communication system.

Table: Examples of closed numbering

Open numbering

In open numbering, a station is uniquely identified by the node number and the station number. Users of different communication systems (nodes) in the inter-network can thus have the same station number.

Node 1 Node 2 Node 3 Node 4

Phone Numbers 100

101

102

103

104

200

201

202

203

204

300

301

302

303

304

400

401

402

403

404A31003-P3010-T101-2-7618, 09/2013OpenScape Business V1, Last Changes, Description 23

I31436: No UC Features with Open Numbering SchemeChapter 20.6.3 / 20.6.6 / 20.6.9 / 20.6.12 Szenario 1/2/3/4: Network-wide FeaturesWith open numbering, the station's node number must always be dialed in addition to the phone number. Phone number ranges can be used more than once for this, and multiple phone numbers can be used.

The following UC features are not supported with open numbering: myPortal Smart UC Solution UC Suite Application Launcher Web Services (Gate View, Web Collaboration) Open Directory Services

The following UC features are supported locally with open numbering: Smart VoiceMail Company AutoAttendant (UC Smart)

Table: Examples of Open Numbering

INFO: In general, closed numbering should be used (because it supports all UC features). Existing customer networks should be adapted.

7.3 Chapter 20.6.3 / 20.6.6 / 20.6.9 / 20.6.12 Szenario 1/2/3/4: Network-wide Features

...

Node 1 Node 2 Node 3 Node 4

Node number (PABX number) 95 96 97 98

Phone Numbers 100

101

102

103

104

100

101

102

103

104

100

101

102

103

104

100

101

102

103

104

myPortal for Desktop / myPortal for Outlook (UC Suite)

Closed numbering Open numbering

Netwide with UC functionality via UC Booster Server, UC Booster Card or OpenScape Business S.

Not supported

Instant Messaging Netwide Not supported

Voicemail Subscribers use their local voicemail system; there is no central voicemail for the entire internetwork.

Not supported A31003-P3010-T101-2-7618, 09/201324 OpenScape Business V1, Last Changes, Description

I31436: No UC Features with Open Numbering SchemeChapter 20.6.3 / 20.6.6 / 20.6.9 / 20.6.12 Szenario 1/2/3/4: Network-wide FeaturesPresence Status Netwide Not supported

Busy indication Netwide Not supported

Internal Directory / Favorites Netwide Not supported

External directory Local, via import of CSV files Not supported

Search in external directories of other nodes Not possible Not supported

External Offline Directory (LDAP) via LDAP Not supported

myPortal for Desktop / myPortal for Outlook (UC Suite)

Closed numbering Open numbering

myPortal Smart (UC Smart) Closed numbering Open numbering

Netwide with UC functionality via UC Booster Server, UC Booster Card or OpenScape Business S.

Not supported

Voicemail Subscribers use their local voicemail system; there is no central voicemail for the entire internetwork.

Not supported

Presence Status Local Not supported

Busy indication Local Not supported

Internal Directory / Favorites Local Not supported

Company AutoAttendant (UC Suite) Closed numbering Open numbering

Company AutoAttendant: after the AutoAttendant answers a call, the caller must dial the number of the station to which he or she wants to be connected.

CCV scripts allow you to dial station numbers from the internal directory within the internetwork.

Not supported

Personal AutoAttendant: after the Auto Attendant answers a call, the caller must dial a single digit to be connected to his or her call destination.

Any station number preconfigured by a UC subscriber is possible

Not supported

Company AutoAttendant (UC Smart) Closed numbering Open numbering

Company AutoAttendant (UC Smart) Local, not for communication systems with UC Suite

Local

External applications Closed numbering Open numbering

OpenScape Business TAPI Applications See Administrator Documentation, Application Connectivity

External CSTA applications

Application Launcher

OpenScape Contact Center See Administrator Documentation, Multimedia Contact Center.A31003-P3010-T101-2-7618, 09/2013OpenScape Business V1, Last Changes, Description 25

I31436: No UC Features with Open Numbering SchemeChapter 2.6.14 Scenario 5: Network-wide Features7.4 Chapter 2.6.14 Scenario 5: Network-wide Features

Mobility Closed numbering Open numbering

Desk Sharing Within a node; network-wide with DLS Not supported

Mobility with DTMF control of the system Local (not supported for OpenScape Business S)

myPortal for Mobile (UC Suite) Network-wide presence status and directories (requires a UC Booster Card, UC Booster Server or OpenScape Business S for each node)

Not supported

myPortal for Mobile (UC Smart) Local, not for UC Booster Card, UC Booster Server and OpenScape Business S

Local Not supported

Other functionalities Closed numbering Open numbering

Signaling and Payload Encryption (SPE) Not supported for UC connections and conferences

Not supported for conferences

DSS server Network-wide (requires a UC Booster Card, UC Booster Server or OpenScape Business S for at least one of the nodes)

Not supported

Maximum configuration

Maximum number of nodes depends on OpenScape Voice

Maximum number of stations in a single communication system depends on OpenScape Business X3/X5/X8

Maximum number of stations in the network depends on OpenScape Voice

Administration

WBM The Networking wizard cannot be used. OpenScape Voice is administered per node via the OpenScape Business expert mode.

Manager E Not recommended

UC Suite Administration via UC Booster Server or UC Booster Card

UC is not relevant in connection with OpenScape Voice

Mass data import via CSV files (call numbers, DID numbers, names)

Separately for each of the nodes in the OpenScape Business internetwork A31003-P3010-T101-2-7618, 09/201326 OpenScape Business V1, Last Changes, Description

I31436: No UC Features with Open Numbering SchemeChapter 2.6.14 Scenario 5: Network-wide FeaturesLicensing

Licensing Each node individually; a network license is required for each OpenScape Business node

New licensing structure A network license is required for each OpenScape Business node

Clients

myPortal Smart Not relevant, because UC is not supported in this networking scenario

myPortal for Desktop Not relevant, because UC is not supported in this networking scenario

myPortal for Outlook Not relevant, because UC is not supported in this networking scenario

myAttendant Not relevant, because UC is not supported in this networking scenario

myAgent Not relevant, because UC is not supported in this networking scenario

Company AutoAttendant (UC Suite) Not relevant, because UC is not supported in this networking scenario

OpenScape Business Attendant

Support Is supported within the OpenScape Business internetwork. Otherwise, internal call numbers are limited to 8 characters (by the interface).

Instant Messaging Local for each node

Voicemail Local for each node

Presence status Not possible

Busy indication Local for each node

External directory via LDAP

Central Attendant Console Not supported

Company AutoAttendant (UC Smart)

Company AutoAttendant (UC Smart) Local Not relevant, because UC is not supported in this networking scenario

External applications

OpenScape Business TAPI Applications See Administrator Documentation, Application Connectivity

External CSTA applications

Application Launcher

OpenScape Contact Center Not relevant, since UC is not supported in this networking scenario. A31003-P3010-T101-2-7618, 09/2013OpenScape Business V1, Last Changes, Description 27

I31436: No UC Features with Open Numbering SchemeChapter 20.6.16 Scenario 7: Open Numbering in OpenScape Business X3/X5/X8 Networks7.5 Chapter 20.6.16 Scenario 7: Open Numbering in OpenScape Business X3/X5/X8 Networks

A internetwork with open numbering can be set up by networking two (or more) communication systems whose numbering schemes overlap one another (i.e., they are not unique throughout the internetwork).

Telephony

SIP Provider (ITSP) Not supported when connected to OpenScape Business; Internet phone calls are conducted exclusively via OpenScape Voice

PSTN Provider Local, or with OpenScape Business as a gateway for OpenScape Voice

Survivability (redundancy in the event of an internetwork or OpenScape Business S breakdown)

Not supported (since there is no OpenScape Business S in the network)

Dial a public number in the own node Supported

Dial a public number in a networked node Depends on the Configuration of OpenScape Voice

Mobility

Desk Sharing Locally, within an OpenScape Business node

Mobility with DTMF control of the system Local

myPortal for Mobile (UC Smart) Not supported (because UC Suite is not available) Not relevant, because UC is not supported in this networking scenario

myPortal for Mobile (UC Suite) Local

Other functionalities

Signaling and Payload Encryption (SPE) Supported A31003-P3010-T101-2-7618, 09/201328 OpenScape Business V1, Last Changes, Description

I31436: No UC Features with Open Numbering SchemeChapter 20.6.16 Scenario 7: Open Numbering in OpenScape Business X3/X5/X8 NetworksNetwork Data

Network-wide voice networking via OpenScape Business UC Suite (via UC Booster Server or UC Booster Card) is not supported. UC

features are not supported. Smart VoiceMail and Company AutoAttendant (UC Smart) can be used locally.

Every call within a node with an internal call number Every call to another node (without a node number, with an internal call

number) Each node must be configured in Expert mode. The Networking wizard is

disabled once a node number for open numbering has been configured. Local access to PSTN and ITSP from each node No OpenScape Business S is permitted, since the integrated UC Suite of the

softswitch does not work together with open numbering

OpenScape Business X3/X5/X8 (without

UC Suite)

STN

s8t e)

STSTSTSTNTNTNTNNNNSTS NSSPSTN ITSP

Internal No. 100

DID not relevant

100 Dials 88 100

100 Dials 87 100

SIP-Q

PSTN ITSP

Internal No. 100

DID not relevant

OpenScape Business X3/X5/X8 (without

UC Suite)

Node Number 87

Node Number 88 A31003-P3010-T101-2-7618, 09/2013OpenScape Business V1, Last Changes, Description 29

1 About this Document2 I30848: Web Security for UC Smart / UC Suite2.1 Chapter 19.5.1 Web Access Filter (UC Suite) Connections to Web Server2.2 Chapter 19.5.1.1 How to configure Web Access the connections to the Web Server (UC Suite)2.3 Chapter 19.5.1.2 How to configure the connections to the Web Server (UC Smart)

3 I30948: Valid Values for Node ID from 1 to 1003.1 Chapter 4.7.2.3 How to Activate or Deactivate Networking3.2 Chapter 5.8.2.3 How to Activate or Deactivate Networking3.3 Chapter 27.3.1.11 Basic Settings > Gateway

4 I31066: Boards TS2/TS2R and TST1/TST1R not suppoerted in OpenScape Business X3W/R4.1 Chapter 9.1 Hardware Expansion

5 I31112: Incorrect Virtual Disk Format Type5.1 Chapter 2.2 Installation in a virtual environment

6 I31334: Microsoft Exchange Server 2003 not supported6.1 Chapter 12.4.1 Presence Status (UC Suite)6.2 Chapter 12.4.1.1 How to Configure the Exchange Calendar Integration6.3 Chapter 12.5.1.2 How to Enable or Disable the Integrated Public Exchange Folder6.4 Chapter 27.4.3.7 OpenScape Business UC Suite > External Providers Config

7 I31436: No UC Features with Open Numbering Scheme7.1 Chapter 20 Networking OpenScape Business7.2 Chapter 20.4.2 Dial Plan in the Network7.3 Chapter 20.6.3 / 20.6.6 / 20.6.9 / 20.6.12 Szenario 1/2/3/4: Network-wide Features7.4 Chapter 2.6.14 Scenario 5: Network-wide Features7.5 Chapter 20.6.16 Scenario 7: Open Numbering in OpenScape Business X3/X5/X8 Networks

OpenScape Business V1, Last Changes, Description, Issue 2

Documents

Transcript of OpenScape Business V1, Last Changes, Description, Issue 2