OpenScape V2.0 Project Planning Guide

7/23/2019 OpenScape V2.0 Project Planning Guide

http://slidepdf.com/reader/full/openscape-v20-project-planning-guide 1/50

HiPath OpenScape V2.0

Project Planning Guide



*1PA31003-S5020-A300-1-7619*

1P A31003-S5020-A300-1-7619

The information provided in this document contains merely general descriptions orcharacteristics of performance which in case of actual use do not always apply as de-scribed or which may change as a result of further development of the products.An obligation to provide the respective characteristics shall only exist if expresslyagreed in the terms of contract.

Siemens AG 2004 ● Information and Communication Networks,

Hofmannstraße 51, D-81359 München, GermanyReference No.: A31003-S5020-A300-1-7619 Printed in the Federal Republic of Germany.Subject to availability. Right of modification reserved.



5453TOC.fm

A31003-S5020-A300-1-7619, July 2004

HiPath OpenScape V2.0, Project Planning Guide 0-3

Nur für den internen Gebrauch Content

Content 0

1 Preface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11.1 About this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

1.1.1 Prerequisite Knowledge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11.1.2 Purpose of This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11.1.3 How to Use This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11.1.4 Related Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

1.2 Documentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

2 Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12.1 Executive Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12.2 Technical Requirements Questions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22.3 Key Customer Contact Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-32.4 Project Phases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

2.4.1 Project Definition Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-52.4.2 Analysis Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-52.4.3 Design Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-52.4.4 Integration Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-62.4.5 Validation Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

2.5 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-62.5.1 Hardware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-72.5.2 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8

2.5.3 Data Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-82.5.4 Voice Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-102.5.5 SIP Phone. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-102.5.6 Gateway Port Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12

2.6 OpenScape Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-142.6.1 Infrastructure Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-142.6.2 OpenScape Application Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-152.6.3 Additional Devices and Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-152.6.4 Deployment Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-162.6.5 Deployment Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-182.6.6 Typical Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20

2.7 OpenScape Security Tips for the Administrator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-202.7.1 Kerberos . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21

A Deploying Multiple Gateways for Scalability and in Geographically Distributed Sys-tems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-1

A.1 Customer Deployments with Multiple Gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1A.2 Topologies with Multiple Gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

A.2.1 Gateways to PSTN and Corporate Network Topology . . . . . . . . . . . . . . . . . . . . A-2A.2.2 Branch Office with Local PSTN and Voice Access . . . . . . . . . . . . . . . . . . . . . . . A-4



Content Nur für den internen Gebrauch

A31003-S5020-A300-1-7619, July 2004

0-4 HiPath OpenScape V2.0, Project Planning Guide

5453TOC.fm

A.2.3 Branch Office with PBX for local PSTN and Voice Access . . . . . . . . . . . . . . . . . . A-6A.3 Routing – Dial Plan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7

A.3.1 Dial Plan – Secondary AOR Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7A.3.2 Incoming Call Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8

A.3.3 Gateway Selection by Access/Barrier Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-10A.4 Routing Needs for OpenScape Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-12

A.4.1 Multipoint Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-12A.4.2 HiPath OpenScape Media Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-12A.4.3 SIP Gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-12

B Required Licenses and Software Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1B.1 Infrastructure Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1B.2 OpenScape Application Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1B.3 OpenScape Administration Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2B.4 MCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2

B.5 Routing Dispatcher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3B.6 Trace File Accumulator (TFA). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3B.7 Early Deployment Mode (EDM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3B.8 HiPath OpenScape Media Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3B.9 End Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4B.10 OpenScape Order Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-5

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Z-1



5453intro.fm

A31003-S5020-A300-1-7619, July 2004


Nur für den internen Gebrauch Preface

About this Guide

1 Preface

1.1 About this Guide

This user guide describes the project planning guide for HiPath OpenScape V2.0.

1.1.1 Prerequisite Knowledge

This guide is intended for Siemens service personnel and Siemens partners to help with theproject planning of HiPath OpenScape.

1.1.2 Purpose of This Guide

The purpose of this guide is to provide:

● an executive summary to the CIO - what is required and the impact to his IT networkinfrastructure

● a guideline for sales consultants during the pre-sales phase and an outline of the spec-ification and implementation phase

1.1.3 How to Use This Guide

This book contains the following:

● Chapter 2, “Planning” which describes the various project planning aspects of OpenScape

● Appendix A, “Deploying Multiple Gateways for Scalability and in Geographically DistributedSystems”

● Appendix B, “Required Licenses and Software Prerequisites”

1.1.4 Related Information

The following information sources are available for HiPath OpenScape V2.0:

● Online helpThe online help provides explanations covering all areas of the user interface.

● HiPath OpenScape V2.0 System Description (A31003-S5020-A400) - provides the userwith a system description of OpenScape.

● HiPath OpenScape V2.0 Installation Guide (A31003-S5020-S100) - provides the user withdetailed information on how to install HiPath OpenScape V2.0 as well as how to upgradefrom V1.0 SPCR to V2.0.



Preface Nur für den internen Gebrauch

A31003-S5020-A300-1-7619, July 2004


5453intro.fm

Documentation Feedback

● HiPath OpenScape V2.0 Administration Guide (A31003-S5020-A200) - provides the userwith detailed information on how to administer OpenScape.

● HiPath OpenScape V2.0 Media Server Installation Guide (A31003-S5020-S200) - provides

the user with detailed information on how to install the Media Server.

● User Guide (A31003-S5020-A100)

● Project Initiation Document (PID)

The documents above can be found at:

● Direct Channels: Professional Services description at https://netinfo.icn.siemens.de/ es/products/prod_hipath_openscape_professional_services_v1_0/product.

● Indirect channels: a separate password and profile is allocated in the Siemens Enter-prise Business Area (SEBA) website for each partner company. This profile deter-

mines what the partner company can see or do. As only the local company and/or ICNCS IC can determine whether a contractual relationship exists with the partner com-pany, the LC must register the partner company.

● KMOSS - https://kmoss.icn.siemens.de.

1.2 Documentation Feedback

To report a problem with this document, call your next level of support:

When you call, be sure to include the following information. This will help identify which docu-

ment you are having problems with.

● Title: HiPath OpenScape V2.0, Project Planning Guide

● Order Number: A31003-S5020-A300-1-7619



5453planning.fm

A31003-S5020-A300-1-7619, July 2004


Nur für den internen Gebrauch Planning

Executive Summary

2 Planning

2.1 Executive Summary

This planning guide describes the basics needed for the customer especially the CIO in deter-mining how HiPath OpenScape fits into the customer’s environment. The areas covered include

● technical requirements questions

● key customer contact profiles

● project phases

● hardware/software requirements

● data/voice network requirements

● SIP phone requirements

● typical OpenScape configurations

● OpenScape security tips for the administrator



Planning Nur für den internen Gebrauch

A31003-S5020-A300-1-7619, July 2004


5453planning.fm

Technical Requirements Questions

2.2 Technical Requirements Questions

Ask the following questions. If the answer is no to any, then stop and do not proceed fur-ther.

1. Is there an Active Directory (AD) deployed in production (or planned)?

2. Does the customer have or plan to have an Exchange 2000/2003 Server?

3. Does the customer have a PKI infrastructure? If not, are they willing to install or purchasecertificates from a third party?

4. If no LC Server is deployed, then is the customer willing to allow schema changes in theirActive Directory for Windows LC Server deployment?

5. Will OpenScape users be in a single forest? If not, can these users be moved to one forest?

6. Is the customer willing to allow schema changes in their Active Directory for OpenScapedeployment? If not, is the customer willing to have ADAM (Active Directory in ApplicationMode) deployed in their environment?

a) Assuming a process for AD schema updates exist, how long does this take?

b) If too long, then a 2nd forest is required for trials which will eventually involve migratingthe trial users back to the 1st forest. If not acceptable, then will users want to have a2nd account?

7. Will the customer allow full access rights to E2000/2003 mailbox stores?

8. Is the customer willing to allow the addition of groups and account at the root domain andchild domain levels in the default ou=users?

9. Will the customer allow AD groups and accounts to be created with fixed names, chosenby OpenScape, that cannot be modified?

10. For the HiPath OpenScape Media Server, will the customer allow the installation of Win-dows 2000 Advanced Server, US English version and locale setting?

11. Will the customer accept the connection between the HiPath OpenScape Media Serverand Exchange as not encrypted? If not, will they deploy an Exchange front end server forsecurity?

12. If the customer deploys optiPoint 400 SIP Phones, will the Active Directory user accountsfor the phone users be configured in the same domain as the Active Directory user accountfor the LCS services?

For more information, refer to the HiPath OpenScape Professional Services (HOSc PS) SalesKit at the SEBA website or https://netinfo.icn.siemens.de/es/products/ prod_hipath_openscape_professional_services_v1_0/product/sk.



5453planning.fm

A31003-S5020-A300-1-7619, July 2004



Key Customer Contact Profiles

2.3 Key Customer Contact Profiles

These are just the key customer contacts.

Here is an overview of the people involved.

2.4 Project PhasesThe project methodology provides a project guideline including a structured project approach(i.e. project phases, well defined milestones and project tasks) and well defined project organi-zation (i.e. project roles, responsibilities, tasks and required skills).

This methodology makes the project approach visible to all stakeholders, simplifies the initialproject planning and project control, ensures and increases project quality.

Key project parameters include timeline/milestones, content, quality and budget.

Contact Name E-mail Phone # CommentProject Manager Main contact person

Data NetworkTechnical Lead

Refer to Section2.5.3 on page 2-8

Voice NetworkTechnical Lead

Refer toSection2.5.4 on page 2-10




A31003-S5020-A300-1-7619, July 2004


5453planning.fm

Project Phases

See process diagram below. For more details, refer to the HiPath OpenScape Professional Ser-vices documentation at https://netinfo.icn.siemens.de/es/products/ prod_hipath_openscape_professional_services_v1_0/product.

HOSc PS offers the following services:



5453planning.fm

A31003-S5020-A300-1-7619, July 2004



Project Phases

2.4.1 Project Definition Phase

Define and agree to the project goals, scope, approach and organization.

2.4.2 Analysis Phase

Analyze the customer’s environment (i.e. data and voice network infrastructure assessment,business processes, data security analyses, and Microsoft infrastructure analyses).

2.4.3 Design Phase

Provide solution and describe in detail within the OpenScape Solution Design Document. Fur-thermore, the test plan and training concept are also defined.




A31003-S5020-A300-1-7619, July 2004


5453planning.fm

Requirements

2.4.4 Integration Phase

2.4.4.1 Environment Preparation Phase

Prepare the customer’s environment either in Production Mode or Early Deployment Mode (seeSection 2.6.1.1 on page 2-14.

2.4.4.2 Installation Phase

Subsequently, the OpenScape System will be installed and configured accordingly. During thedeployment phase, the entire technology deployment takes place. Meanwhile, all OpenScapeend users are trained.

2.4.5 Validation Phase

This phase starts with the tests as outlined in the test plan. After that the OpenScape systemwill be used by the designated pilot users. This phase ends with the OpenScape pilot sign-off.

After successful deployment testing follows the final project sign-off.

The OpenScape project ends with a project review and customer feedback meeting called theProject Conclusion Workshop.

2.5 Requirements

Here is a general network diagram of OpenScape V2.0.

Figure 2-1 OpenScape Network Diagram



5453planning.fm

A31003-S5020-A300-1-7619, July 2004



Requirements

2.5.1 Hardware

2.5.1.1 Normal Traffic Call Model

Assumptions - (3 events per user per hour) where events include phone calls, portal calls, in-stant messages and status changes)

Note: * The number of MP servers is dependent on the amount of conference resources used(also multiprocessors units can be used).

2.5.1.2 Minimal Configuration

The OpenScape, MCU, LCS and MS SQL can be installed on the same server (P4 Xeon/2 GB).

The HiPath OpenScape Media Server needs to be on a separate 2nd server (P4/2 GB).

2.5.1.3 High Traffic Call Model

Assumptions - (6 events per user per hour) where events include phone calls, portal calls, in-stant messages and status changes)

Note: * The number of MP servers is dependent on the amount of conference resources used(also multiprocessors units can be used).

Server 100/250 UsersProcessor/Memory/HD

500/750 UsersProcessor/Memory/HD

OpenScape Server P4/2 GB/ P4 Xeon/2 GB

MCU Server P4/1 GB/>10GB HD P4/1 GB (1 - 2 servers*)

Media Server P4/2GB/>18 GB HD two P4 Xeon/2 GB

LC Server/MS SQL (optional

on OS server)/Routing Dis-patcher

Yes on Xeon Yes, if dual processor

Table 2-1 Recommended hardware requirements - Normal Traffic Call Model

Server 100/250 UsersProcessor/Memory/HD

500/750 UsersProcessor/Memory/HD

OpenScape Server P4/2 GB/ two P4 Xeon/2 GB

MCU server P4/1 GB/>10GB HD P4/1 GB (1 - 2 servers*)Media Server P4/2GB/>18 GB HD four P4 Xeon/2 GB

LC Server/MS SQL (optionalon OS server)/RD

Yes on Xeon Yes, if dual processor

Table 2-2 Recommended hardware requirements - High Traffic Call Model




A31003-S5020-A300-1-7619, July 2004


5453planning.fm

Requirements

2.5.2 Software

● Operating System Licenses for:

● HiPath OpenScape Main System Server: Windows Server 2003● MCU Server: Windows Server 2003

● HiPath OpenScape Media Server: Windows Server 2000 Advanced

● Trace File Accumulator: Windows 2003 or Windows XP (or located on OpenScapeServer)

● Early Deployment Mode (EDM): Windows 2003 or located on OpenScape Server

● MS SQL 2000: Windows 2000/2003 or located on the OpenScape System server

●

Live Communications (LC) Server 2003Refer to Appendix B, “Required Licenses and Software Prerequisites” for further details.

2.5.3 Data Network

The HiPath OpenScape connects to and is part of the customer’s existing messaging infra-structure. Like any other server/application, it is the customer’s responsibility to ensure theproper evaluation, planning and design of the network, capacity, and bandwidth which are es-sential to a successful installation and deployment.

2.5.3.1 Active Directory

OpenScape system installation and configuration will require the following roles and tasks (one

person may have two or more of these roles):

1. Schema Administrator

● Make Active Directory schema modifications required for the LC Server (note: this inonly required for the first LC Server installation in the forest; this is not required if cus-tomer already has an LC Server in any domain in the same forest)

● Make Active Directory schema extensions required for OpenScape (note: a prepara-tion step as well as domain preparation steps)

2. Root Domain Administrator

● Add the OpenScape Services Group to the root domain

● Add the OpenScape Services Groups of the child domains to this root group as mem-bers

3. Domain Administrator



5453planning.fm

A31003-S5020-A300-1-7619, July 2004



Requirements

● Create OpenScape service accounts and groups

● Join OpenScape servers to the Domain

● Install the LC Server for OpenScape

4. OpenScape LCS Administrator

● Configure the OpenScape LC Server

● Assign the OpenScape LC Server as the home server for OpenScape users

5. Domain User with Local Administrator Rights on OpenScape Server

● Perform OpenScape installation and configuration tasks. This activity will be done bySiemens personnel, SI or VAR.

6. DNS Administrator

● Assign IP address and network name to the SIP gateway

● Create an A record entry for the SIP gateway

● Create and configure DNS SRV records for SIP phones

7. Enterprise Root Certificate Authority (Security) Administrator

● Issue server certificates for HiPath OpenScape as follows:

● One for OpenScape main server

●

One for the Media Server● One for the optiPoint 400 SIP phones if they are deployed

● One for the MS SQL Server if it is deployed on a different machine than the Open-Scape main server

8. Exchange Administrator

● Create mailboxes for OpenScape service account

● Provide access rights to OpenScape service account on the Exchange mailbox andpublic folder stores for Exchange servers where OpenScape users have mailboxes

2.5.3.2 Firewall Requirements

The firewall must be configured to publish the web site to direct web requests to the OpenScapeserver. Also, for access from the outside, the proper ports for http and https must be opened(80 and 443, respectively).

● Portal Access




A31003-S5020-A300-1-7619, July 2004


5453planning.fm

Requirements

In a customer environment, there may be a need for a user to access their portal through theinternet. This requires going through a firewall.

To enable this capability, the firewall needs to be able to configure server certificates. A certifi-

cate is required for a proxy, that is, if the HTTPS is bridged ending up with one HTTPS connec-tion from the browser to the proxy and one HTTPS connection from the proxy to the portals Webapplication.

If there is no proxy, HTTPS is tunneled directly from the browser to the portals Web application.This is not secure and is not recommended.

● OpenScape Management Console

HiPath OpenScape is managed through WMI which uses RPC (Remote Procedure Calls) toaccess the OpenScape Server. Therefore, OpenScape could be managed through a firewall byconfiguring RPC Dynamic Port Allocation. Refer to Microsoft Knowledge Base Article 154596

for more information. It is recommended to use an application like Remote Desktop to connectto a server within the firewall instead of allowing RPC calls through the firewall for security rea-sons.

2.5.4 Voice Network

PBX administrator:

● Identify and configure available trunk circuits (i.e. T1, E1, analog as required by the SIPgateway) to be used by the OpenScape SIP gateway for inbound and outbound calls.

● Create DID phone numbers for all OpenScape users. These DID numbers will serve as theone-number service for these users. Each OpenScape user needs a DID phone numberthat will be used by callers to reach OpenScape users via the PSTN.

● Create a DID number to be used as the Voice Portal access number.

● There are a number of cases where a given customer may wish to deploy multiple SIPgateways, e.g., multiple sites or more trunk capacity needed. For a detailed description ofsuch scenarios and the configuration tips, refer to Appendix A, “Deploying Multiple Gate-ways for Scalability and in Geographically Distributed Systems”.

2.5.5 SIP PhoneThe Siemens optiPoint 400 standard phone offers a SIP variant which is full interoperable withOpenScape. Several features of this phone may have planning implications and should be tak-en into account during the project planning phase. They are as follows:



5453planning.fm

A31003-S5020-A300-1-7619, July 2004



Requirements

1. Power-over-LAN

This SIP phone is equipped with a power-over-LAN interface on the LAN port and complieswith the IEEE802.3af standard. Eight-wire Ethernet cables are required for this phone. If

this interface is used to supply power to the phone, the power source must be a limitedpower source PowerHub compliant with IEC 60950. Another power option for the phone isan external AC adaptor which is not included with the phone and must be ordered sepa-rately.

2. Integrated Mini Switch

This SIP phone is supplied a built-in mini-switch that provides an additional 10/100 Mbps,auto-negotiating, Ethernet port which can be used to connect to a PC/workstation. ThisSIP phone feature eliminates the need for an additional LAN connection which would oth-erwise be required.

The default operation for the mini switch will be to auto negotiate transfer rate (10/100 Mb/ s) and duplex method (full or half duplex) with whatever equipment is connected to the miniswitch.

The software provides options to prevent auto negotiation and to specify the required trans-fer rate and duplex mode for the LAN and PC ports. In the default configuration, the LANport supports automatic detection of cable configuration (pass through or crossover cable)and will reconfigure itself as needed to connect to the network. However if the phone is setup to manfully configure the switch port settings, then the cable detection mechanism isdisabled. In this case, care must be taken to use the correct cable type.

Depending on what has been implemented in the software, IEEE802.1x (Port based net-work access control) packets generated by equipment connected to the PC port will bepassed through the mini switch and out of the LAN port. Removing the power from thephone, or a phone reset/reboot will result in the temporary loss of the network connectionto the PC port. Typically this is about 5 seconds. The Line Monitor diagnostic routine pro-vides information on the configuration of the mini switch.

3. Dynamic Host Configuration Protocol (DHCP) Server

This SIP phone contains a dynamic host configuration protocol (DHCP) client that supportsautomatic configuration of various parameters. If this SIP phone is factory pre-configuredto enable DHCP, then when the device starts it will automatically attempt to obtain from a

DHCP server, the following options that are essential for the configuration of its Ethernetinterface:

● Terminal IP address

● Terminal Mask (Network Mask)




A31003-S5020-A300-1-7619, July 2004


5453planning.fm

Requirements

4. Audio Mode

CODEC: Determine the optimal audio transfer codec for the customer's environment.G711 preferred is used for uncompressed audio transmission suitable for broadband inter-

net connections. G729 preferred is used for compressed audio transmission suitable forconnections with different bandwidths, G729 always is used for compressed audio trans-mission suitable for connections with low bandwidths.

COMPRESSION: IF the compressed audio mode is selected, then use this function to se-lect one of the two compression encodings. The default value is G729.

5. File Transfer Protocol (FTP) Server

This SIP phone is capable of transferring files using the FTP protocol. The feature can beused to update the phone software and upload/download the phone's configuration file.The phone acts as an FTP client and requires a FTP server in the IP network where the

files are located or can be placed.

6. Simple Network Time Protocol (SNTP) Time Server

The protocol is used between timeservers and terminal devices on a network to synchro-nize the time, date, daylight saving and time zone information. The SNTP address can beconfigured on this SIP phone either by DHCP or manually. If the SNTP server address isconfigured the server will be queried for the time. If the server address is not configuredthe phone will look for SNTP broadcasts and set the time and date accordingly.

7. Programmable Keys

This SIP phone is equipped with 12 function keys of which 11 are user programmable intwo levels the function key "Stop/Escape" is not programmable. Five of these keys comealready preassigned in the first level.

8. Simple Network Management Protocol Server

This SIP phone supports SNMP which allows network related information to be browsed(MIB II support). Standard SNMP browsers are sufficient for this purpose.

2.5.6 Gateway Port Requirements

Gateway ports are required for calls where an OpenScape user is connected with a port viathe gateway. These are, for example, connections to CO lines or to phones connected to a

PBX. When OpenScape users use an Associated Device as their Preferred Phone, at least

one gateway port is used for every call since the caller itself needs to be reached via a gate-

way port. In the case of Associated Devices, if the called party also happens to be CO or PBX

line, two gateways ports will be required, one to connect to the caller’s Preferred Phone and

one to connected to the called party.



5453planning.fm

A31003-S5020-A300-1-7619, July 2004



Requirements

The following requirements were taken into account in the calculation: each OpenScape userhas 0.1 Erlang for the external traffic via a gateway channel. Loss of accessibility is estimatedat 1 to 1.2%. A 0.1 Erlang means that the station is busy for 10% of working hours (3.6CCS/ Line). This should not be estimated for call centers or similar organizations.

Here are the gateway port requirements under three traffic scenarios:

A - 0% of OpenScape users on Associated devices; no additional conferencing traffic.

B - 50% of OpenScape users on Associated devices; no additional conferencing traffic (Asso-ciated devices require a gateway connection for all calls).

C - 50% of OpenScape users on Associated devices; default assumptions about additional ad-hoc conferencing:

1. One conference call/OpenScape user/day; 0.05 erlangs/user in the busy hour

2. Average number of conference participants is 5

3. 50% of conference participants on average are external

With those assumptions, the following table can be used for planning the size of your system:The number of ports will vary based on application traffic requirements that are not covered inthe assumptions used by this table.

Table 2-3 Number of Gateway Ports

Please note that the actual number of gateways required in order to provide the required num-ber of ports in Table 2-3 is a function of:

1. Gateway port capacity: higher capacity gateways may be available from gateway vendors

that provide all the required ports on a single gateway with a single IP address2. Multiple gateways configurations: multiple gateways may be deployed to satisfy the higher

port requirements. However, such configurations may have some limitations and will there-fore need to be planned carefully. Please refer to Appendix A, “Deploying Multiple Gate-ways for Scalability and in Geographically Distributed Systems” for details.

# Users Scenario A(0% Associated Devices)

Scenario B(50% Associated Devices)

Scenario C(50% AD + conferencing)

100 18 30 51

250 36 63 98

500 64 116 172

750 91 168 242




A31003-S5020-A300-1-7619, July 2004


5453planning.fm

OpenScape Configurations

2.6 OpenScape Configurations

Version 2 of HiPath OpenScape supports a broad variety of deployment options, which are de-pendent on customer environments and functional requirements.

An OpenScape Application deployment requires various components:

● Infrastructure components in the IT environment, which are software and networkcomponents

● OpenScape Application components, which are software components installed onWindows servers

● Additional devices or clients, which are used by the user or the system to connect tothe current communication infrastructure and to the OpenScape application

Multiple OpenScape systems can be deployed in the network as well. However, the featuresare not completely transparent in such an environment. Mainly, the users of a other OpenScapeare handled like ‘external’ users and information (like presence information) is not shared be-tween different OpenScape systems.

2.6.1 Infrastructure Components

OpenScape is an application based on the Live Communication Service (LCS) product of Mi-crosoft and requires

● An TCP/IP network installation with Active Directory on Windows 2000 or 2003

● One or many LCS installations (on Windows 2003)

● One or many Microsoft Front End server (FES) (optional installation)

● One or many Microsoft Exchange 2000 or 2003

● Microsoft SQL Server 2000 (MS-SQL)

OpenScape installation requires Active Directory schema extensions. If the customer does notallow Active Directory changes the system needs to be deployed in “Early Deployment Mode”,which does require additional software components, but does not require a schema change inActive Directory.

LCS deployments require Active Directory schema changes as well and are still required.

2.6.1.1 Production Mode vs. Early Deployment Mode

Production Mode: This is the recommended mode. OpenScape schema extensions to the Ac-tive Directory are configured.



5453planning.fm

A31003-S5020-A300-1-7619, July 2004




Early Deployment Mode: This mode can be used as alternative when the customer does notallow the Active Directory to be extended for HiPath OpenScape. Note that LCS schema exten-sions are still required.

There can only be one mode for the whole Active Directory forest at a given time. It is possibleto migrate from EDM to Production Mode once the Active Directory schema can be extended.

The advantage of running HiPath OpenScape in Production Mode is better performance espe-cially in a larger deployment in terms of number of users and multiple locations.

Using the Early Deployment Mode requires the following additional components

● Microsoft Active Directory for Early Deployment (ADAM) on Windows 2003

● OpenScape Early Deployment Active Directory Connector (EDM) on Windows 2003

2.6.2 OpenScape Application Components

The following components comprise the OpenScape Application

● Management Console (OMC) on Windows 2000 or 2003 or XP Pro

● OpenScape Application (OS-Core) on Windows 2003

● Routing Dispatcher (RD) on Windows 2003

● Multi Conferencing Unit - Controller (MC) on Windows 2003

● Multi Conferencing Unit – Processor (MP) on Windows 2003

● Media Server Application (MS) on Windows 2000

● Trace File Accumulator on Windows 2003 or XP pro

The distribution of the various components is completely flexible, but is dependent on

● operating system requirements

● performance of the hardware

● required performance of the application (number of users and traffic model)

2.6.3 Additional Devices and Components

In addition the following components can be deployed

● SIP Gateways

● SIP phones

● Windows Messenger 5.0




A31003-S5020-A300-1-7619, July 2004


5453planning.fm


● OpenScape Client

The portal interface does not require any client installation. However, for Outlook orMessenger integration OpenScape client installation is necessary.

2.6.4 Deployment Rules

There is a set of rules which need to be adhered to for the system to work successful. The nextsection depicts then more concrete implementation scenarios.

1. All components need to be installed in the same (Active Directory) forest.

● That includes the server components

● LCS,FES, OS-Core, MS-SQL, MS, MCU (MC, MP)

● And users (with clients or SIP phones), OMC, Gateways

2. All server components of one OpenScape system need to be installed in the same domainwith the exception of RD (see rules 5 and 6 below).

3. An OpenScape installation requires one or more LCS installation in the same forest

● The Microsoft deployment guide for LCS / FES applies

4. Multiple OpenScape systems can be deployed in the same or different domains.

5. The Routing Dispatcher (RD) needs to be installed on each LCS in the forest.

An RD installation is not required if● all users of this particular LCS are not users of OpenScape;

● these users are not involved in calls with OpenScape users.

For that reason it is recommended to install RD on all LCS of this forest.

6. The RD should be installed on an FES.

7. The LCS can be installed in a different domain (implies also to RD in rule 5.).

8. Users on multiple LCS in different domains can be supported with one OpenScape instal-lation and as well with multiple OpenScape installations.

9. OMC can be installed in different domains (there is always an OMC installed on the OS-Core system) of the same forest.

10. All Windows 2003 components can be installed on the same server or separate servers.This includes:

● LCS with RD

● MS-SQL



5453planning.fm

A31003-S5020-A300-1-7619, July 2004




● OS-Core

● MCU-MC

● MCU-MP

● TFA

● EDM

● OMC

11. An existing MS-SQL 2000 installation can be extended to be used for an OpenScape in-stallation.

12. An MCU-MC does not require a separate server and should reside with one MCU-MP.

13. MCU-MP residing on a separate machine guarantees voice quality in a higher traffic model

scenario. Up to 4 MPs can be deployed, but a single MP is only bound by the CPU perfor-mance and will not limit itself to 72 channels. E.g. a dual processor machine can support144 channels.

14. There is only one MS per OpenScape system installation.

15. MS requires Windows 2000. It is not recommended to install additional software compo-nents on this server.

16. Multiple Exchange servers are supported, but

● All need to have the same version (2000 or 2003)

● Each Exchange server can be configured with a different language




A31003-S5020-A300-1-7619, July 2004


5453planning.fm


2.6.5 Deployment Models

The deployment rules allow a wide variety of configurations.

The figure shows complete configurations with minimum and maximum number of servers.

Figure 2-2 Minimum Complete Server Configuration



5453planning.fm

A31003-S5020-A300-1-7619, July 2004




Figure 2-3 Maximum Complete Server Configuration




A31003-S5020-A300-1-7619, July 2004


5453planning.fm

OpenScape Security Tips for the Administrator

2.6.6 Typical Configurations

The following table allows to identify typical configurations based on the number of users andthe traffic model. The “normal” traffic model assumes a call volume of 3 calls per user per hour

and the “high” traffic model assumes a call volume of 6 calls per user per hour.

Table 2-4 Typical Configurations

2.7 OpenScape Security Tips for the Administrator

There is a document on the SEBA and KMOSS website that provides security tips to help asystem administrator secure the OpenScape environment and enhance a company’s own se-

curity policy.

These tips are not intended to replace or substitute for a company’s own security policy.

On the KMOSS website, this document can be found at https://kmoss.icn.siemens.de/livelink/ livelink.exe?func=ll&objId=2322890&objAction=View&nexturl=%2Flivelink%2Flivelink%2Eexe%3Ffunc%3Dll%26objId%3D1242024%26objAction%3DBrowse.

Traffic Scenario 100/250 Users 500/750 Users

Normal

Machine 1● OS-Core● LCS + RD● MS-SQL● MCU (MC+MP)● TFA● EDM (optional)

Machine 2 ● Media Server

Machine 1● OS-Core● LCS + RD● MS-SQL


Machine 3

● MCU (MC+MP)Machines 4, 5, 6 (if required) ● for additional MPs

High

Machine 1● OS-Core● LCS + RD● MS-SQL


Machine 3 ●

MCU (MC+MP)

Machine 1● LCS + RD

Machine 2 ● OS-Core● MS-SQL


Machine 4 ● MCU (MC+MP)Machines 5, 6, 7(if required) ● for additional MPs



5453planning.fm

A31003-S5020-A300-1-7619, July 2004




2.7.1 Kerberos

OpenScape supports a cross-realm scenario where the SIP phone user and the LCS arehomed in different domains/realms. More than one domain controller (DC) and corresponding

Kerberos Distribution Center (KDC) are involved when the Kerberos client on the phone triesto get a ticket to access the LCS service. The different domains need to be in the same forestand a trust relationship needs to be set up between the domains. Cross forest Kerberos au-thentication is not supported.




A31003-S5020-A300-1-7619, July 2004


5453planning.fm




mutiplegateways.fm

A31003-S5020-A300-1-7619, July 2004

HiPath OpenScape V2.0, Project Planning Guide A-1

Nur für den internen Gebrauch Deploying Multiple Gateways for Scalability and in Geo-

Customer Deployments with Multiple Gateways

A Deploying Multiple Gateways for Scalability and inGeographically Distributed Systems

A.1 Customer Deployments with Multiple Gateways

OpenScape V2 is an application that runs on top of the Microsoft Live Communications Server2003 (here referred to as LCS). As such it leverages the infrastructure and topologies the LCSsupports. This is true too for the support of multiple Gateways and in regards to dial plans androuting.

A.2 Topologies with Multiple Gateways

The LCS supports many different topologies. The ones shown here are typical examples.

Microsoft recommends to set up an LCS as Front End Server (FES) which interfaces to all theGateways in the system (see Appendix A — Setting Up IP-PSTN Connectivity, Microsoft OfficeLive Communications Server 2003 Reference Guide Published: August, 2003). This has theadvantage to limit the impact of potentially complex routing rules as well as IPSec setup to thisServer and not to have to replicate these through the system.

In this chapter we do not address complex dial plans. The examples given assume access codebased Gateway selection. Please see Section A.3 on page A-7 on more advanced dial plans.

Most of the scenarios are shown with separate inbound and outbound gateways. You can useseparate gateways or a single gateway to handle incoming and outgoing calls.

Furthermore we show most of the scenarios using an LC Server as FES to connect the LCSnetwork to the Gateways. This is not a requirement to connect Gateways to the LCS network.You can connect the Gateways directly to e.g. your OpenScape LC Server as well. You will haveto modify the example routes accordingly.



Deploying Multiple Gateways for Scalability and in Geographically Distributed Systems

A31003-S5020-A300-1-7619, July 2004

A-2 HiPath OpenScape V2.0, Project Planning Guide

mutiplegateways.fm

Topologies with Multiple Gateways

A.2.1 Gateways to PSTN and Corporate Network Topology

A.2.1.1 Direct Gateway Connection to OpenScape LC Server

The OpenScape LC Server connects via Gateways to the PSTN and Corporate Voice Network.



mutiplegateways.fm

A31003-S5020-A300-1-7619, July 2004


Nur für den internen Gebrauch Deploying Multiple Gateways for Scalability and in Geographi-


A.2.1.2 Gateway Connection to OpenScape LC Server via FES

Here, the FES connects the SIP world to the PSTN and the Corporate Voice//TDM Network.




A31003-S5020-A300-1-7619, July 2004


mutiplegateways.fm


A.2.2 Branch Office with Local PSTN and Voice Access


This example expands the scenario above with a Branch Office Deployment that allows usersin a remote location (Location B) to allow these Branch Office users to use local Gateways to

the PSTN and Corporate Voice Network.

Such a configuration is especially desirable for the PSTN aspect as users otherwise would haveto have a telephone number with the country and area code of the main office (Location A). Soa Branch office that has only PSTN access but uses the main office for access to the CorporateVoice Network is possible as well.



mutiplegateways.fm

A31003-S5020-A300-1-7619, July 2004




A.2.2.2 Gateway Connection to OpenScape LC Server via FES

This example expands the scenario above with a Branch Office Deployment that allows usersin a remote location (Location B) to allow these Branch Office users to use local Gateways viaFES to access the PSTN and Corporate Voice Network.

Such a configuration is especially desirable for the PSTN aspect as users otherwise would haveto have a telephone number with the country and area code of the main office (Location A). Soa Branch office that has only PSTN access but uses the main office for access to the CorporateVoice Network is possible as well.




A31003-S5020-A300-1-7619, July 2004


mutiplegateways.fm


A.2.3 Branch Office with PBX for local PSTN and Voice Access


Many customers have existing corporate voice networks and manage a large number of PBXs.Many of the existing PBX installation have Least Cost Routing set up.

This example can take advantage of the Least Cost Routing feature in the PBX.

As in the Branch office example above users in Location B can access PSTN and CorporateVoice Network locally. Again this allows us to provide users in Location B with telephone num-bers that have country and area codes appropriate to their geographic location.



mutiplegateways.fm

A31003-S5020-A300-1-7619, July 2004



Routing – Dial Plan

A.2.3.2 Direct Gateway Connection to OpenScape LC Server via FES

Many customers have existing corporate voice networks and manage a large number of PBXs.Many of the existing PBX installation have Least Cost Routing set up.

This example can take advantage of the Least Cost Routing feature in the PBX.

As in the Branch office example above users in Location B can access PSTN and CorporateVoice Network locally. Again this allows us to provide users in Location B with telephone num-bers that have country and area codes appropriate to their geographic location.

A.3 Routing – Dial Plan

A.3.1 Dial Plan – Secondary AOR Introduction

Each Live Communication Server (LCS) user is assigned a Primary AOR (Address of Record- SIP address as published in AD) which is also used as Primary AOR for HiPath OpenScape.

In addition each HiPath OpenScape user can be assigned up to two Secondary AORs whichrepresent the internal extension number and the public E.164 DID number. These SecondaryAORs are also stored in Active Directory (or ADAM), but are unknown to LCS.

All Secondary AORs consist of a numeric user part and the domain part of its Primary AOR,e.g. a user with Primary AOR [email protected] may have the Secondary AORs [email protected] and [email protected].




A31003-S5020-A300-1-7619, July 2004


mutiplegateways.fm


The extension and DID Secondary AORs can be configured manually for each user or systemwide number conversion rules can be set up to derive the numeric part of these SecondaryAORs from one of the following Active Directory user attributes: Telephone Number, HomePhone, Pager, Mobile, or IP Phone.

An example for user Tim is:

Primary AOR in Active Directory: [email protected]

Telephone Number in Active Directory: (561)555-1234

OpenScape Server’s number conversion rules for

Extension: retain trailing 4 digits of Telephone Number field and prefix with digit 2

DID: retain all digits of Telephone Number field and prefix with digit 1

Tim’s Secondary AORs would then be:Extension Secondary AOR: [email protected]

DID Secondary AOR: [email protected]

As these Secondary AORs are not known to LCS itself special attention will need to be givento the routing of these Secondary AORs. This is because LCS is not aware of “Telephone Num-bers”, but only of Active Directory Users, which do not normally follow a telephone number rout-ing hierarchy, but follow a domain based model.

A.3.2 Incoming Call Routing

HiPath OpenScape version 1 supports only a single Secondary AOR and therefore the PSTNtrunks had to be provisioned to present the called party number as an extension. In HiPathOpenScape version 2 this is not necessary anymore since both a public E.164 DID number andan extension are supported.

A.3.2.1 Short Number Dialing

PSTNs usually provide the extension number as called party number to the gateway. CO trunksmay also be provisioned to provide only partial digits, called Dialed Number Identification Ser-vice (DNIS). In these cases the gateway shall append the domain part of the users PrimaryAOR to the received digits.

An example for a call from the PSTN to Tim:

Called Party Number provided by PSTN to GW: 21234





mutiplegateways.fm

A31003-S5020-A300-1-7619, July 2004




Number conversion rules for Extension: retain trailing 4 digits of Telephone Number fieldand prefix with digit 2

Tim’s Extension Secondary AORs would then be: [email protected]

Extension Secondary AOR provided by GW to LC Server: sip:[email protected]

The HiPath OpenScape Routing Dispatcher deployed on the LC Server will intercept this “call”to sip:[email protected] and route it to that users assigned OpenScape Server for furtherprocessing.

A.3.2.2 Fully Qualified E.164 Number Dialing

It is also possible to get the CO trunk provisioned to provide called party numbers as fully qual-ified E.164 numbers. The E.164 number should have the format “Country Code” + “NationalDestination Code” + “Subscriber Number”. This number should not contain any access or bar-rier codes.

In these cases, as in the short number dialing, the gateway shall append the domain part of theusers Primary AOR to the received digits.

If such a configuration is requested from a service provider, then the DID Secondary AORsmust be configured using E.164 numbers. If Active Directory already contains the users E.164numbers, then the DID number conversion rules should be set up to have the DID SecondaryAORs configured for the users match the DID Secondary AORs received from the gateway.

An example for a call from the CO to Tim:



Number conversion rules for DID: use Telephone Number field and prefix with digit 1

Tim’s DID Secondary AORs would then be: [email protected]

Called Party Number provided by CO trunk to GW: 15615551234

DID Secondary AOR provided by GW to LC Server: sip:[email protected]

A.3.2.3 Single Domain for Primary and Secondary AORsNormally, gateways, SIP phones, and terminal adapters will append a single configurable do-main to the target telephone number e.g. they see 1234 as the incoming number and add sie-mens.com as the domain, thus making this [email protected].

This will pose a problem if you have a Primary or Secondary AOR scheme that has multipledifferent domains used as the base of the AORs. [email protected] will never [email protected] unless you have some special static routes that handle this.




A31003-S5020-A300-1-7619, July 2004


mutiplegateways.fm


Therefore we limit ourselves to addressing scenarios that use a single domain as the domainused for AORs and secondary AOR. OpenScape provides no special support for AORs in mul-tiple domains and therefore we recommend a single domain for the Primary or SecondaryAORs.

A.3.3 Gateway Selection by Access/Barrier Code

To support multiple gateways, PBX-style barrier codes can be used. For example we can de-sign a system where a user would dial 9+PSTN number to dial into the public network and 8 +internal number to dial into the corporate voice network.

In an environment with multiple sites it is often desirable to connect locally to the public or cor-porate network instead of routing all calls through a central GW.

In this chapter we develop routing tables for the topology described in Section A.2.3 on page

A-6.

Location A has the following number spaces and access codes:

● Enterprise Number Space: 2xxxx

● OpenScape Number Space: +1 408 492 2xxx, internally dialed as 22xxx

● Access code: 9 to dial PSTN

Location B has the following number spaces and access codes:

● Enterprise Number Space +49 89 277xxxxx, internally dialed xxxxx

● OpenScape Number Space: 74xxx

● Access code 0 to dial PSTN

Location A and B have a number overlap. As long as none of the OpenScape secondary AORoverlap with the other numbers in the overall system, OpenScape will not have an issue, but itwill be impossible to dial PBX users in Location A and B that have the same number. To solvethis we will have to make some tough choices:

1. Use a special code to dial internal PBX users in Location B. So we define that all PBXusers in Location B will have to be dialed as 8xxxxx when dialed from within the LCS

network.2. Alternatively we could allow the users to use an access code to allow calling Location

B PBX users. E.g. Access code 8 to call PBX users in Location B.

3. Have users in location B always dial a number that allows us to differentiate calls e.g.they dial internal numbers as 277xxxxx and their OpenScape Number space is27774xxx. Unfortunately LCS only support suffix matching so 277* may match Loca-tion A PBX users as well as Location B PBX users. Therefore we would have to makethe users in Location A dial 492xxxx to contact the Location A PBX users.



mutiplegateways.fm

A31003-S5020-A300-1-7619, July 2004




In this case we choose option 1 as this solved the PBX number overlap as well as potentialoverlaps when we move PBX users to OpenScape in the future.

For option 1 with gateway directly connected to the OpenScape LC Server, the routing table

would be1

:

For option 1 with gateway connected to OpenScape LC Server via FES, the routing table in theFES would be:

The routing table in the LCS Home Server for OpenScape would be:

The routing table in the other LCS Servers would be:2

Notes:

0*@* -> PBX GW Location B2

8*@* -> PBX GW Location B2

9*@* -> PBX Outbound GW Location A2

2*@* -> PBX Outbound GW Location A

0*@fes.foo.com3 -> PBX GW Location B2

8*@fes.foo.com3 -> PBX GW Location B2

9*@fes.foo.com3 -> PBX Outbound GW Location A2

2*@fes.foo.com3 -> PBX Outbound GW Location A

*@foo.com4 -> fes.foo.com; Replace Host in Request URI

*@FQDN5 -> fes.foo.com; Replace Host in Request URI

2*@* -> OpenScape LCS Home Server, RequestHost in Request URI

0*@* -> fes.foo.com; Replace Host in Request URI



1 - The routing tables in this example are not complete. You will have to add addi-tional routes as described in Section A.4 on page A-12.

2 - This requires the Gateway to strip off the first digit before dialing out3 - Fes.foo.com means the Fully Qualified Domain Name of the FES

4 - foo.com means the user SIP URI domain name (i.e. SIP:[email protected])

5 - FQDN is the Fully Qualified Domain Name of the LCS Home Server for Open-Scape




A31003-S5020-A300-1-7619, July 2004


mutiplegateways.fm

Routing Needs for OpenScape Components

A.4 Routing Needs for OpenScape Components

A.4.1 Multipoint Controller

A route for the MCU has to be set on the OpenScape home server only. Please refer to theOpenScape Installation Guide; specifically, the chapter on Installing MCU and the section in theappendix on the OpenScape RTC Tool.

A.4.2 HiPath OpenScape Media Server

A route for the Media Server has to be set on the OpenScape home server only. Please referto the Media Server documentation and the section in the appendix on the OpenScape RTCTool in the OpenScape Installation Guide.

A.4.3 SIP Gateways

In addition to routing the numbers to gateways, gateways also need trusted static routes toroute requests that are part of a session of an incoming call to the gateway. Otherwise the LCSwould not trust the responses of these requests.

So if you have a gateway vega100.iris.boreas.net, you would need a route entry on the Open-Scape LC Home Server to route *@vega100.iris.boreas.net to the gateway.

Also of course a gateway will need a trusted static port for incoming calls as described in theadditional gateway documentation and the section in the appendix on the OpenScape RTC

Tool in the OpenScape Installation Guide.



licenses.fm

A31003-S5020-A300-1-7619, July 2004

HiPath OpenScape V2.0, Project Planning Guide B-1

Nur für den internen Gebrauch Required Licenses and Software Prerequisites

Infrastructure Components

B Required Licenses and Software Prerequisites

This appendix provides information about OpenScape licenses.

B.1 Infrastructure Components

CAL = Client Access License

Note 1: If the customer is licensed for Microsoft Exchange under Software Assurance or an

Enterprise Agreement before October 1, 2003, the customer is likely already licensed for Live

Communications Server 2000. Refer to Microsoft for details as licensing provisions are subject to change at Microsoft’s discretion. Some helpful links are: http://www.microsoft.com/edu-

cation/?id=livecommservertransition and http://www.microsoft.com/office/livecomm/howtobuy/

default.mspx.

Note 2: Active Directory Application Mode (ADAM) is a part of Microsoft’s fully integrated

directory services available with Windows Server 2003. ADAM can be downloaded at http://

www.microsoft.com/downloads/details.aspx?FamilyId=9688F8B9-1034-4EF6-A3E5-

2A2A57B5C8E4&displaylang=en.

B.2 OpenScape Application Server

Component Server Licenserequired?

CALsrequired?

CAL LicenseType

Quantity

MS Exchange Server2000/2003

Yes but none spe-cific to Open-

Scape

Yes but nonespecific to

OpenScape

MS LCSVersion 1.0.4949

Yes YesNote 1

User Mode 1 Server li-cense + 1CAL/userNote 1

Active Directory Applica-tion Mode (ADAM)

Note 2

No No


CALsrequired?

License Type Quantity

OpenScape BasePackage

Yes n/a User 1 Server license + user li-cense in package of 25



Required Licenses and Software Prerequisites Nur für den internen Gebrauch

A31003-S5020-A300-1-7619, July 2004

B-2 HiPath OpenScape V2.0, Project Planning Guide

licenses.fm

OpenScape Administration Clients

Note 1: Refer to www.microsoft.com/licensing.

B.3 OpenScape Administration Clients

The only license needed per client is MS Windows 2000, MS Windows 2003, or MS XP Pro-fessional.

B.4 MCU

OpenScape User

Package

n/a Yes User Additional 25 user license

packageOpenScape Man-agement Console

No No

OpenScapeRouting Dis-

patcher

No. Included inOpenScape

Base Package

No n/a n/a

MS WindowsServer 2003

Standard or En-terprise Edition

Yes Yes User ModeCAL, and

Server Modeserver

1 CAL per user; Servercomes with initial 25

CALs; No CALs requiredfor Gateway

MS SQL Server2000 and SP 3Standard or En-terprise Edition

Yes No Processor-basedNote 1

1 Server license only

OpenScape EDM No, included inOpenScape

Base Package

No n/a n/a

Microsoft ADAM(refer to Note 2 in

Section B.1)

No No n/a n/a


CALs required? LicenseType

Quantity

OpenScape MCU No. Covered in the BaseOpenScape license for up tofull 288 ports on 4 servers

No n/a n/a


CALsrequired?

License Type Quantity



licenses.fm

A31003-S5020-A300-1-7619, July 2004



Routing Dispatcher

B.5 Routing Dispatcher

Nothing needed since it is installed on the LC Server.

B.6 Trace File Accumulator (TFA)

TFA requires a Windows 2003 Server or XP license but no CALs required.

B.7 Early Deployment Mode (EDM)

ADAM requires Windows 2003 but no CALs.

B.8 HiPath OpenScape Media Server

MS Windows

Server 2003Standard or En-terprise Edition

Yes. One for each server. Up

to 4 servers may be requiredto support all 288 ports

No. Only one set of

CALs is sufficient toaccess all Win200x

servers

Server 1

Component Server License

required?

CALs required? CAL

LicenseType

Quantity

Media Server No. Included inBase OpenScape

system

No CALs.Thirty Media Server

ports included but ad-ditional ASR/TTSsessions licensesmay be required

n/a 1 ASR/TTS sessionis provided in BaseOpenScape pack-

age. Up to 29 moremay be purchased.

MS Windows2000 Advanced

Server + SP4 min-imum

Standard Edition

Yes No. Only one set ofCALs is sufficient to

access all Win200xservers. Note 3

User n/a

Speechify TTSScansoft V2.0

Yes. Already inOpenScape

product structure

No No n/a


CALs required? LicenseType

Quantity




A31003-S5020-A300-1-7619, July 2004


licenses.fm

End Points

Note 3: According to Microsoft, the fact that no additional CALs are required for the MediaServer is based on the assumption that all access to the Media Server is directed through

OpenScape and LCS. If in the future, we decided to add features to the Media Server that mayenable direct access to it (without going through OpenScape), additional Windows CALs maybe required.

B.9 End Points

OSR Scansoft Yes. Already inOpenScape

product structure

No n/a n/a

MSDE 2000 +SP3

No with purchaseof Win2K Server

No n/a n/a

VocalOS(Vocalocity)

No with purchaseof Win2K Server

No n/a n/a

End Point Server Licenserequired?

CALsrequired?

CALLicense Type

Quantity

OptiPoint 400 n/a Already covered

by OpenScapeuser license

n/a n/a

Windows MessengerVersion 5.0

n/a n/a n/a n/a

MS Windows 2000 orMS Windows XP Pro-

fessional

n/a n/a. Part of clientmachine

n/a n/a


CALs required? CALLicense

Type

Quantity



licenses.fm

A31003-S5020-A300-1-7619, July 2004



OpenScape Order Examples

B.10 OpenScape Order Examples

This section shows three examples of OpenScape V2.0 orders and lists all the required com-ponents. The examples include some variations in Microsoft licensing agreements.

Item A B C

Customer Configuration

Number of OpenScape users; accessible from various end-points like multiple PCs, SIP phone, voice/self-service portals

150 90 400

Number of conferencing ports 72 30 150

Additional ASR/TTS ports 10 5 25

Number of ports in SIP Gateway that connects OpenScape to

the customer’s PBX

48 24 4 x 48

Number of Siemens SIP phones 70 10 100

Software Assurance (SA) for Exchange Agreement) No Yes Yes

Enterprise Agreement No No Yes

OpenScape Components

OpenScape Basic Package(25 users, including service) 1 1 1

25 user packages 5 3 15

Additional ASR ports 10 5 25

Additional TTS ports 10 5 25HiPath OpenScape Professional Services Packages*

HiPath OpenScape DesignFor the customer specific consulting and creation of the solu-tion design including deployment, test and training concept.Based on results of analysis phase, the customer’s require-ments will be transformed into a specific solution design.

Hourly Hourly Hourly

HiPath OpenScape IntegrationFor the integration in the customer-specific environment


HiPath OpenScape TrainingFor the customer specific creation and implementation of cus-tomer training which reflects the customer’s specific solutionimplementation


Microsoft Components

Win2003 Server license for the OpenScape server 1 1 1

LC Server license for the OpenScape server 1 1 1




A31003-S5020-A300-1-7619, July 2004


licenses.fm

OpenScape Order Examples

*Note: For the successful implementation of the HiPath OpenScape project, HiPath Open-Scape Professional Services are required (refer to HOSc PS description).

Win2003 Server license for the MCU Server 1 1 3

Win2000 Advanced Server license for the Media Server, 30ports included 1 1 1

Processor-based SQL Server 2000 license 1 1 0

Windows server user-mode CALs. With a single CAL, eachuser will be able to access any of the Win2000/Win2003 serv-ers from any device

150 90 0

LCS user-mode CALs (LCS license includes 5 CALs) 145 0 0

Exchange 2000/2003, AD and the client licenses for the XP/ Win2K client machines are considered as pre-requisite with noadditional licenses required by OpenScape

Additional Equipment

Vega100 48-channel gateway (service extra) 1 1 4

Item A B C



5453IX.fm

A31003-S5020-A300-1-7619, July 2004

HiPath OpenScape V2.0, Project Planning Guide Z-1

Nur für den internen Gebrauch Index

Index Z

AAdditional Devices and Components 2-15Audio Mode 2-12

BBranch Office with Local PSTN and Voice Ac-cess A-4

Cconfiguration

minimum complete server 2-15

DData Network 2-8Deployment Models 2-18Deployment Rules 2-16Domain Administrator 2-8Domain User with Local Administrator Rightson OpenScape Server 2-9

Dynamic Host Configuration Protocol (DHCP)Server 2-11

EEarly Deployment Mode 2-15Early Deployment Mode (EDM) B-3Enterprise Root Certificate Authority (Securi-ty) Administrator 2-9

Environment Preparation Phase 2-6Exchange Administrator 2-9

Ffeedback, documentation 1-2

File Transfer Protocol (FTP) Server 2-12Firewall Requirements 2-9Fully Qualified E.164 Number Dialing A-9

GGateway Port Requirements 2-12Gateways to PSTN and Corporate NetworkTopology A-2

HHardware 2-7High Traffic Call Model 2-7

IInfrastructure Components 2-14Installation Phase 2-6Integrated Mini Switch 2-11Integration Phase 2-6

KKerberos 2-21Key Customer Contact Profiles 2-3

Mminimum complete server

configuration 2-15Multipoint Controller A-12

NNormal Traffic Call Model 2-7

OOpenScape LCS Administrator 2-9OpenScape Management Console 2-10

PPortal Access 2-9Power-over-LAN 2-11Production Mode 2-14Project Phases 2-3

Rrequirements 2-7, 2-8Root Domain Administrator 2-8

SSchema Administrator 2-8Short Number Dialing A-8Simple Network Management Protocol Serv-er 2-12



Index Nur für den internen Gebrauch

A31003-S5020-A300-1-7619, July 2004

Z-2 HiPath OpenScape V2.0, Project Planning Guide

5453IX.fm

Simple Network Time Protocol (SNTP) TimeServer 2-12

Single Domain for Primary and SecondaryAORs A-9

SIP Phone 2-10Programmable Keys 2-12

Software 2-8

TTechnical Requirements 2-2Topologies with Multiple Gateways A-1Trace File Accumulator (TFA) B-3

VValidation Phase 2-6





The information provided in this document contains merely general de-

criptions 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.

www.siemens.com/hipath

Documents

OpenScape V2.0 Project Planning Guide