OpenScape V2.0 System Description

HiPath OpenScape V2.0

System Description

*1PA31003-S5020-A400-1-7618*

1P A31003-S5020-A400-1-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 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 expressly agreed in the terms of contract.

Siemens AG 2003, 2004 ● Information and Communication Networks, Hofmannstraße 51, D-81359 München, GermanyReference No.: A31003-S5020-A400-1-7618 Printed in the Federal Republic of Germany. Subject to availability. Right of modification reserved.

5350SystemTOC.fm

Nur für den internen Gebrauch Contents

Contents 0

1 An Overview of OpenScape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11.1 OpenScape Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

1.1.1 OpenScape Server on Office LCS 2003 Platform. . . . . . . . . . . . . . . . . . . . . . . . . 1-31.1.2 Exchange Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-31.1.3 Active Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-41.1.4 Communications Broker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-41.1.5 Media Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-41.1.6 Multipoint Conferencing Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-41.1.7 SIP Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-41.1.8 SIP Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

1.2 Accessibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-51.3 OpenScape Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

1.3.1 OpenScape Dependencies on LCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-61.3.2 Virtual Assistant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-61.3.3 Workgroup Assistant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-71.3.4 Interaction Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-71.3.5 User Notification Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-71.3.6 Media Server and Speech SDK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-81.3.7 Portals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-101.3.8 MCU and MCU Resource Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-101.3.9 WebEx Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-111.3.10 Live Meeting Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-111.3.11 Routing Dispatcher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-111.3.12 Presence Age Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-111.3.13 Groupware Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-121.3.14 B2BUA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-121.3.15 Assistant Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-121.3.16 Knowledge Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-121.3.17 Context Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-131.3.18 Database Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-141.3.19 Serviceability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-141.3.20 Data Synch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-151.3.21 License Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15

1.4 Tool Suite Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-171.4.1 Deliverables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-171.4.2 Web Services-based SDK Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18

1.5 Call Flow Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-191.5.1 Basic Call Using Click-to-Dial from Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-191.5.2 Basic Call Between OpenScape Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-211.5.3 Basic Conference Call. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-23

A31003-S5020-A400-1-7618, June 2004OpenScape, System Description 0-3

Contents Nur für den internen Gebrauch

5350SystemTOC.fm

1.6 System Capacities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-251.7 No Special Handling for Emergency Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-25

2 Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12.1 Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12.2 Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22.3 Licensing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-32.4 OpenScape Management Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-32.5 Server Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-42.6 User Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-52.7 Device Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

2.7.1 General Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-52.7.2 Phone-specific Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-62.7.3 Parameters for a Single SIP Phone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-72.7.4 Administration of Unassigned SIP Phones. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-72.7.5 Management of RTP Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

2.8 Application Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-82.8.1 Application Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-82.8.2 Trace Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9

2.9 System Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-102.9.1 System Data Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-102.9.2 Storage Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-102.9.3 Storage Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-112.9.4 Knowledge Management Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-122.9.5 Resource Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-122.9.6 Systems Destination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-122.9.7 Portals Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-122.9.8 SDK Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-132.9.9 Web Conferencing SPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-132.9.10 Licensing Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13

2.10 OMC Snap-Ins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-132.11 Administration of Other Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-132.12 Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-142.13 Installation of OpenScape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14

3 Personal Portal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13.1 Personal Portal in a Browser Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13.2 Personal Portal as Outlook or Messenger Plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23.3 My Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23.4 My Preferred Phone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33.5 My Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33.6 My Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

3.6.1 Contacts in Outlook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43.6.2 Contacts in Windows Messenger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

3.7 My Workgroups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

A31003-S5020-A400-1-7618, June 20040-4 OpenScape, System Description

5350SystemTOC.fm


3.8 Other OpenScape Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-53.9 Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-63.10 Interaction with Windows Messenger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-63.11 OpenScape Presence and Availability Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

3.11.1 Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-73.11.2 Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-83.11.3 Enhancements to Microsoft Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-93.11.4 Interaction with the OpenScape Presence Model . . . . . . . . . . . . . . . . . . . . . . . 3-10

4 Rules Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14.1 Rules for My Presence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

4.1.1 Actions for My Presence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34.2 Rules for Incoming Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

4.2.1 Actions for Incoming Calls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-54.2.2 Exceptions for Incoming Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6

4.3 Rules for Outgoing Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-64.3.1 Actions for Outgoing Calls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-64.3.2 Exceptions for Outgoing Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7

4.4 Rules for Incoming Instant Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-74.4.1 Actions for Incoming Instant Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-84.4.2 Exceptions for Incoming Instant Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9

4.5 Rules for Outgoing Instant Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-104.5.1 Actions for Outgoing Instant Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-104.5.2 Exceptions for Outgoing Instant Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10

4.6 Rules for Incoming Emails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-114.6.1 Actions for Incoming Emails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-114.6.2 Exceptions for an Incoming Email . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12

4.7 Default Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12

5 Workgroup Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15.1 Viewing Conference Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25.2 Sharing Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25.3 Creating Workgroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25.4 Launching a Workgroup Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

5.4.1 Multimedia Conferencing—Launching a Web Conference . . . . . . . . . . . . . . . . . . 5-4

6 Voice Portal and Self-Service Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16.1 Voice Portal Access for OpenScape Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

6.1.1 Listen to Voice and Email Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16.1.2 Create and Delete Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26.1.3 Manage Calendar Appointments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26.1.4 Review and Manage Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-36.1.5 Manage User Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-36.1.6 Manage Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-36.1.7 Speech Input to the Voice Portal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3

6.2 Self-Service Portal for Guests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4



5350SystemTOC.fm

6.2.1 Guest Access to Self-Service Portal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-46.2.2 How Contacts are Authenticated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-56.2.3 Leave Voice Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-56.2.4 Schedule Appointments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-66.2.5 Access Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7

6.3 The Interaction Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-86.3.1 HiPath Media Server Administration Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-86.3.2 Scenario 1—Media Server Provides Greetings . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-86.3.3 Scenario 2—User Customizes Greeting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-106.3.4 Scenario 3—Contact Guest Accesses Self-Service Portal. . . . . . . . . . . . . . . . . . 6-11

6.4 OpenScape Interaction with Outlook and Exchange Server . . . . . . . . . . . . . . . . . . . . 6-126.4.1 Configuration of Outlook Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-126.4.2 Pre-defined Outlook Folders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-126.4.3 Interaction Center Folder and Sub-folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-136.4.4 Outlook Journal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14

7 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17.1 Password Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17.2 Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-27.3 Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-27.4 Authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-37.5 Siemens SIP Phone Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-37.6 Certificate Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3

7.6.1 Server Certificates and Root CAs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-47.6.2 Workstation Certificates and Root CAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-47.6.3 SIP Phone Certificates and Root CAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-47.6.4 Non-Siemens Gateway Certificates and Root CAs . . . . . . . . . . . . . . . . . . . . . . . . 7-4

7.7 Remote Access to Portals via the Internet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-57.7.1 Scenarios for Remote Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5

8 Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-18.1 Basic Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

8.1.1 Forests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-18.1.2 Trees . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-18.1.3 Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

8.2 Network Infrastructure Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-28.2.1 OpenScape Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-28.2.2 OpenScape Application Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-28.2.3 OpenScape Administration Clients. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-38.2.4 MCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-38.2.5 Media Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-38.2.6 End Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4

8.3 Deployment Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-58.3.1 Minimum Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-68.3.2 Expanded Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7


5350SystemTOC.fm


8.3.3 Deployment Scenario Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-88.3.4 Single Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-108.3.5 Multiple Domains. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-128.3.6 Multiple OpenScape Systems - Separate Domains . . . . . . . . . . . . . . . . . . . . . . 8-138.3.7 Multiple OpenScape Systems - Same Domain . . . . . . . . . . . . . . . . . . . . . . . . . . 8-158.3.8 Multiple LCS Servers behind Front-End LCS Server . . . . . . . . . . . . . . . . . . . . . 8-18

8.4 Mix of OpenScape and non-OpenScape LCS Users. . . . . . . . . . . . . . . . . . . . . . . . . 8-19

9 SIP Phones and Gateways. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-19.1 optiPoint 400 standard SIP V3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-19.2 Third-party SIP Phones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-19.3 Third-party Gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . X-1

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



5350SystemTOC.fm


5350over.fm

Nur für den internen Gebrauch An Overview of OpenScapeOpenScape Platform

1 An Overview of OpenScape

OpenScape is an open, real-time communications suite of software applications. It fits into an enterprise’s existing voice and data infrastructure and ties together phones, voice mail, email, text-messaging, calendaring, instant messaging, and conferencing services. It provides an interface to manage online presence and communication and collaboration services.

OpenScape makes it easier for users—regardless of whether they are in the office, at home, or on the road—to access the people and the information they need.

A few examples:

● A user can set her preferences for various communications media, specify which people she will take calls from and how they can reach her. For example, if she’s out of the office for the afternoon, she can have all incoming calls between noon and 5:00 p.m. routed to her assistant. But when a special customer calls her office phone, that customer can be routed to a self-service center where the customer can retrieve a document and request an appointment with the OpenScape user.

● With a glance at the contact list, a user can see how a particular contact has set his status (for example, in the office, in a meeting) and determine the best way to reach him (voice, instant messaging, email).

● With a single click, a user can initiate a voice conference with his team members and share documents. He can also launch a web conference using Live Meeting or WebEx.

1.1 OpenScape Platform

The typical solution requires three OpenScape servers:

● The OpenScape server running on Microsoft Office Live Communications Server (LCS) 2003

● The Media Server running on Windows 2000

● The Multipoint Conferencing Unit (MCU) Server running on Windows 2003

Other configurations are possible. Users in one OpenScape system can be distributed on mul-tiple LC servers. Conversely, one LC server can host multiple OpenScape systems. Refer to the Installation Guide for more information.

Figure 1-1 on page 1-2 shows the components of a typical OpenScape system.


An Overview of OpenScape Nur für den internen Gebrauch

5350over.fm

OpenScape Platform
. F
igur

e 1-

1P

hysi

cal C

ompo

nent

s of

Ope

nSca

pe

Med

ia S

erve

rM

CU

PC

for

Web

-ba

sed

Por

tal

SIP

Ter

min

als

WM

DN

S/D

HC

PD

omai

n C

ontr

olle

r

SIP

pho

nes

3rd

Par

tyS

iem

ens

Act

ive

Dire

ctor

y

Exc

hang

eS

erve

r

SQ

L D

B

Cel

l ph

one

SIP

Gat

eway

PS

TN

PC

TN

PS

TN

ph

one

SIP

Gat

eway P

BX

PB

X

phon

eS

iem

ens

com

pone

nts

=

MP

s

3rd

part

y

Em

ail

Ser

ver

Ope

nSca

pe

Ser

ver

LC S

erve

rP

roxy

Reg

istr

arR

outin

g D

ispa

tche

r

UA

C/U

AS

Virt

ual A

ssis

tant

Com

mun

ity A

ssis

tant

Con

text

Age

ntK

now

ledg

e A

gent

Lice

nse

Ser

ver


5350over.fm

Nur für den internen Gebrauch An Overview of OpenScapeOpenScape Platform

1.1.1 OpenScape Server on Office LCS 2003 Platform

The Live Communications Server Is a SIP proxy server that provides a SIP registrar and Pres-ence and Availability Service (PAS). The proxy and registrar allow SIP endpoints to register and communicate using voice, video and instant messaging. The PAS provides SIP endpoints with the presence and availability status of other SIP endpoints.

Figure 1-2 shows the shows the OpenScape features that run on this server.

1.1.2 Exchange Server

The Exchange server provides the ability to send and receive email and centralized storage for email calendars journals and email folders. Users are able to access the contents of the Ex-change server using the Outlook client or Outlook Web Access.

Figure 1-2 OpenScape Features

Voi

ce P

orta

l

Ope

nSca

pe S

uite

Personal Productivity Application Workgroup Collaboration Application

Inte

llige

nt R

each

Wor

d W

eb

Rul

es W

izar

d

Sel

f-se

rvic

e P

orta

l

Personal Portal

Aud

io C

onfe

renc

ing

Mul

ti-re

sour

ceC

onfe

renc

ing

Con

fere

nce

Vie

w

Inst

ant C

onfe

renc

e

Med

ia A

dvan

ce

Workgroup Portal

Operating System

Communication Broker

Interworking Services

Context Manager Configuration andManagement

Telephony Features Reports and Data Storage

Options SIP Clients 3rd Party Gateways SDK Toolkits



5350over.fm

OpenScape Platform

1.1.3 Active Directory

Active directory provides a centralized directory server that stores personal information about network users including their passwords. It provides applications with access to directory infor-mation and services that can be used to authenticate network users.

1.1.4 Communications Broker

The Communications Broker encompasses the OpenScape architecture components de-scribed in Section 1.3 on page 1-5. It provides an open, modular, standards-based middleware architecture with common access to various multi-media services across various underlying communications platforms. It enables the OpenScape portals, as well as OpenScape applica-tions and third party applications.

The Communications Broker contains both basic services and OpenScape assistant services that expose Software Development Kit (SDK) interfaces that portals and applications can use.

1.1.5 Media Server

The Media Server running on Windows 2000 (Windows 2003 in upcoming feature pack) is a system resource based on a telephony browser that supports voth VXML and SALT standards. It provides multimodal user interfaces to the applications. Refer to Section 1.3.6 on page 1-8 for more information on the Media Server architecture and features.

1.1.6 Multipoint Conferencing Unit

The Multipoint Conferencing Unit (MCU) running on Windows 2003 provides media mixing (that is, combining the audio channels from multiple parties) for conference calls that OpenScape users may be involved in. Refer to Section 1.3.8 on page 1-10 for more information on the MCU architecture and features.

1.1.7 SIP Gateway

The Session Initiation Protocol (SIP) gateway provides a signaling and media path into circuit-switched networks. It has to convert SIP into the appropriate protocol of the circuit-switched network and convert the media stream considering the appropriate media codec. As shown in Figure 1-1 on page 1-2, the gateway can be used to connect to either the public network or a PBX network.

1.1.8 SIP Endpoints

OpenScape is designed to interact with any standard SIP endpoint, including Windows Mes-senger and the Siemens optiPoint 400 SIP phone.


5350over.fm

Nur für den internen Gebrauch An Overview of OpenScapeAccessibility

As new LCS-compliant phones enter the market, check KMOSS for the latest compatibility test-ing information that may be available.

Refer to Chapter 9 for more information on the SIP phones.

1.2 Accessibility

Although it is not a PBX or IVR Messaging system as covered by Federal Communications Commission (FCC) rules 6/7 (section 255), OpenScape adheres to the guidelines specifying that communications systems must be usable by persons with disabilities. This impacts all as-pects of the OpenScape system and includes provision for the deaf, blind, limited mobility, color blind, susceptibility to flashing lights, and so on.

1.3 OpenScape Architecture

OpenScape is designed as an IT application for advanced enterprise communication. As such, the OpenScape architecture:

● Follows a horizontal approach that fully utilizes the communication features of the enter-prise server operating system and desktop PC environment (e.g. Windows Server 2003, Microsoft Office Live Communications Server, Windows Messenger)

● Integrates with the IT infrastructure in areas of:

– Management, for example Windows Management Instrumentation (WMI) and Mi-crosoft Management Console (MMC)

– Security, for example Kerberos, Transport Layer Security (TLS), IPSec

– Directory services, for example Active Directory

● Integrates with the enterprise groupware environment for message store, calendar, con-tact, and shared folders, for example Exchange 2000

● Follows industry standards that promote inter operability with third party devices and appli-cations, for example SIP, SIMPLE, XML, Integrated Services Digital Network (ISDN), QSIG.

● Offers open Application Programming Interfaces (APIs), again based on standards, for ex-tensibility and customization (for example, based on web services architecture)

OpenScape application features are designed to be media and device independent. The appli-cation features are accessible through a wide range of devices, including Microsoft Outlook, Windows Messenger, Internet Explorer web browser, SIP phones, regular phones, and mobile phones.



5350over.fm

OpenScape Architecture

in Version 2, the open interfaces of OpenScape make it a powerful platform for communica-tions-enabling a wide range of business applications, such as Enterprise Resource Planning (ERP), Customer Relationship Management (CRM), and eCommerce applications.

OpenScape is delivered as a closely integrated set of components. The major components are described in this section.

1.3.1 OpenScape Dependencies on LCS

OpenScape is intended to support SIP users who are registered on an Office Live Communi-cations Server 2003.

As part of the OpenScape system, an OpenScape Routing Dispatcher application is installed on the Office Live Communications server. The Routing Dispatcher uses the LCS application interface to monitor all SIP calls handled by the server.

Calls identified as being of interest to the OpenScape application (involving an OpenScape us-er) are routed to the OpenScape Back-to-Back User Agent (B2BUA). This is done using the LCS application interface to specify a different destination for the call.

The only call-related interface to the LCS is by the Routing Dispatcher. The other OpenScape applications deal with SIP calls that are routed to them by the LCS with the help of the Routing Dispatcher. In addition, the Microsoft PAS service that is part of the LCS is accessed to view and set the presence of LCS users by the OpenScape application.

The LCS requires that all SIP users that wish to register with it be defined in Active Directory. Active Directory provides authentication and routing information for the LCS.

The OpenScape application requires that all SIP users be defined in Active Directory. While OpenScape stores most of the user information it needs in its local storage, it does depend on some information from Active Directory and does store a portion of the user information it needs in Active Directory.

1.3.2 Virtual Assistant

The Virtual Assistant is the OpenScape component that allows the user to control the process-ing of a communication session. A communication session may be a single phone call, an email or an instant message session.

The core functionality is the set of rules that are called into play when any session (incoming or outgoing) that is recognized by OpenScape occurs for an OpenScape user.

The Assistant is aware of the devices associated with the user. These can include registered devices (SIP phones and clients registered to the user) and associated devices (mobile phones or home phones). The Virtual Assistant provides the only interface to the OpenScape user por-tals so that applications can view or update the rules and status information associated with the user, the user’s workgroups, and user’s devices.


5350over.fm

Nur für den internen Gebrauch An Overview of OpenScapeOpenScape Architecture

Refer to Section 3.9 on page 3-6 for more information on device types.

1.3.3 Workgroup Assistant

The Workgroup Assistant enhances an OpenScape user’s capability to create and manage col-laborative sessions through a variety of portals such as an Outlook portal, a Windows Messen-ger portal, a telephony portal and a web portal. Workgroups can be set up once and remain persistent over multiple voice or multimedia conferencing sessions.

Each workgroup consists of a set of members, storage for documents associated with the work-group and the ability to establish collaborations between the members of the workgroup. The data storage area for the workgroup contains those documents and files workgroup members may wish to access during collaboration. A set of document types may be included in the data storage area and then accessed from a portal.

1.3.4 Interaction Center

The Interaction Center (shown in Figure 1-3 on page 1-9) implements the Telephony User In-terface (TUI) and the Speech User Interface (SUI) which provides speech and DTMF (telepho-ny) access for OpenScape users and their callers. OpenScape users can use the Voice Portal to access their messages including email, other groupware (calendar, tasks) and functions re-lated to personal and workgroup features.

Callers to an OpenScape user go through the Self Service Portal, which allows them to either leave messages, or upon authentication, to get information greetings specific to the caller.

Refer to Chapter 6, “Voice Portal and Self-Service Portal” for more information on the Interac-tion Center capabilities.

1.3.5 User Notification Service

The User Notification service is designed to provide a mechanism for applications and users to send a notification message to a number of different destinations. Applications such as the Knowledge Manager are able to send notifications of significant system events to system ad-ministrators or other interested personnel.

OpenScape users can specify rules that will send notifications of events related to their person-al communications sessions. Notifications can be sent using instant messages (IMs), SMS, pagers or email. When instant messages are sent the user notification service uses the Client API provided by the LC server.

The target of the notification is intended to be a live person who wants to be notified of some significant event. The purpose of the notification is to let that person know of the event. Because the notification may be through a different means than the event that triggered it, it is not intend-



5350over.fm


ed that all of the information from the triggering event be communicated via the notification. In-stead it is intended to allow the user to know that they should check for the event that triggered the notification.

For example, if a user’s Virtual Assistant has been told to look for an email from an important customer, the Virtual Assistant can send a notification that such an email has arrived to the us-er’s pager with a limited portion of the email text (limited by pager capabilities). If the email is truncated, the user would be expected to log on and retrieve this email.

1.3.6 Media Server and Speech SDK

The Media Server platform, shown in Figure 1-3 on page 1-9, consists of the voice browser, text-to-speech, automatic speech recognition, SIP connectivity and system administrator web services. Together, they provide the client side for rendering the OpenScape application on a telephony channel. This includes voice output, as well as processing DTMF and speech input.

There is also a Speech SDK tool suite, which, along with VXML and SALT standard scripting capabilities, includes an application builder, Word Web proxy, the Dialog engine and tuning tools for speech input. This provides the ability to build or customize speech applications.


5350over.fm


Fig

ure

1-3

Med

ia S

erve

r A

rchi

tect

ure

Customer Applications

Applications Connectors

Customer ConnectorsCustomer Web

WebsiteTUI/SUI Clients

WA

VA

Exc

hang

eS

TS

IMA

P 4

Act

ive

Dire

ctor

yLD

AP

Dire

ctor

y

HPPC

Adm

inis

trat

ion

HPPC API

Lice

nse

Aut

hent

icat

ion Installation

Configuration

Application Builder

Con

nect

ivity

Dia

gnos

tics

Opt

ions

Rep

orts

Sch

edul

e

Wor

d W

eb

Sub

scrib

er

Lice

nse

XM

LIn

tera

ctio

n C

ente

r Fr

amew

ork

with

EI

Journal

Contact

Calendar

Messenger

Folders

DB

Syn

c

MS

DE

Dat

abas

e

Inte

ract

ion

Cen

ter

(IC

)

Dire

ct

Acc

ess

Spe

ech

ICV

A/W

AD

ialo

gP

erso

nal

Adm

inG

uest

Acc

ess

Spe

ech

Dia

log

SD

K

Music on Hold

DTMF AA

TUI IA

IA

HPPC IVR

Web

Ser

ver

IIS

Wor

d W

eb P

roxy

Channel Web Service

Admin Web Service

VX

ML

& S

ALT

Bro

wse

r

Med

ia A

bstr

actio

n

TT

S

Cha

nnel

Abs

trac

tion

TD

M S

PS

IP S

PA

SR



5350over.fm


1.3.7 Portals

Refer to Chapter 3, “Personal Portal”, Chapter 5, “Workgroup Portal” and Chapter 6, “Voice Por-tal and Self-Service Portal” for a description of the various portals.

1.3.8 MCU and MCU Resource Controller

The MCU provides the mixing capability (combining the audio channels from multiple parties) for voice conferences.

The MCU resource controller is accessed by OpenScape applications to allocate an MCU for a conference. The access occurs at the point that the application wishes to connect parties to the conference. The controller is responsible for checking the availability and capacities of the possibly multiple MCU components that are part of the OpenScape system.

The MCU is built using a decomposed model. Media processing is distributed over multiple servers using the Megaco protocol. (Figure 1-4 on page 1-10).

Figure 1-4 MCU Architecture

The MCU contains internally one central MC (Multipoint Controller) which deals with the SIP signaling and controls the mixing of the voice and up to four Media Processors that perform the actual mixing of the voice samples.

The MCU supports the following:

● Ad-hoc and dynamic conference creation from the contact list following the SIP conferenc-ing model for ad-hoc conferences

● Codec support G.711, G.723.1, advanced audio processing

MC

SIPMegaco(H.248)

IP

MP

RTPMegaco(H.248)

IP

MCU

Megaco (using TCP and IPSec)

SIP (using TCPor IPSec)

RTP (using UDP

and QoS)LCS

server Client


5350over.fm


● A single Media Processor running on a 2.4 GHz Pentium 4 can support 72 channels G.711 or 24 channels of G723.1 or a mix thereof.

A total of four Media Processors and 288 G.711 channels is currently supported.

1.3.9 WebEx Connector

The WebEx Connector uses the WebEx API to connect to the WebEx Services. The WebEx connector also implements a Siemens Web Conferencing Service Provider Interface (WCSPI) to integrate with OpenScape. The Workgroup Assistant uses the WCSPI to integrate with the WebEx Service.

1.3.10 Live Meeting Connector

The Live Meeting Connector acts as a client to a Live Meeting Service (also known as PlaceWare) and make API requests by submitting HTTP request to the Live Meeting Server. The Live Meeting connector also implements the Siemens WCSPI to integrate with Open-Scape. The Workgroup Assistant uses the WCSPI to integrate with a Live Meeting Service.

1.3.11 Routing Dispatcher

The Routing Dispatcher (RD) is an application that sits on top of a Microsoft LC server and be-haves like a proxy. The RD has an RD-Active Directory Connector (RD-ADC) sub-component that provides information on all OpenScape users that are configured in Active Directory (AD). This RD-ADC component interfaces directly with AD; it does not interwork with Microsoft’s Ac-tive Directory Connector (ADC) component. The RD-ADC will also monitor for changes in OpenScape user information that are made to AD. The RD will thus use the RD-ADC to check to see if users indicated in a SIP message (in a From or To header) are OpenScape users or not. If so, the home OpenScape server for the user will be indicated by the RD-ADC to the RD.

1.3.12 Presence Age Script

The Presence Age Script resides on a Microsoft LC server and monitors all NOTIFY messages. When the application finds a NOTIFY that is doing a presence update of an OpenScape user, it adds AgeOfPresence information for each of an OpenScape user’s endpoints to the NOTIFY message. Since the Context Agent subscribes to the presence of all OpenScape users, it re-ceives such a NOTIFY every time an OpenScape user’s presence changes. The Context Agent then uses the AgeOfPresence information to determine the most current device entry for any device that has multiple entries. This function needs to be performed because an LC server does not automatically insert this information in the NOTIFY message



5350over.fm


1.3.13 Groupware Connector

The Groupware Connector component provides a general abstraction for an application that needs to access a user’s groupware. This layer shields an application from the actual group-ware / store used by the user. It provides access to the following objects:

● Calendar

● Journal

● Inbox

● Other message folders

It is the responsibility of this component to know and access the groupware store for an appro-priate object and attributes. However, the insulation to the store is not total in that the applica-tion should know that there are differences in the store, and should be able to handle conditions where certain object types and attributes are not provided by the groupware connector.

1.3.14 B2BUA

All SIP messages related to an OpenScape user are routed to this Back-to-Back User Agent (B2BUA). The B2BUA presents SIP messages received from an LC server to the Assistant En-gine and Context Agent. Those components interact with the B2BUA to generate new SIP re-quests and responses.

The B2BUA recognizes only incoming messages from known LC servers and not from any un-specified source in order to avoid attacks from a malicious source. The B2BUA uses a Siemens developed stack for SIP signal processing.

1.3.15 Assistant Engine

The Assistant Engine component provides a SIP-to-CSTA III XML mapping. It performs this function by acting on received SIP messages, which are provided by the SIP stack of a Sie-mens-developed B2BUA process, and translating the SIP messages to CSTA III XML events when appropriate. It also accepts CSTA III XML requests and, as needed, alters or generates new SIP messages to act on such requests. This functionality allows OpenScape CSTA III XML applications such as the Virtual Assistant and Workgroup Assistant to influence the handling of a call involving SIP devices (such as SIP clients, phones and gateways). It also logs session interaction data to the Context Agent for inclusion in the Context Data Record (XDR).

1.3.16 Knowledge Agent

There are three distinct processes involved in knowledge enabling in the OpenScape system.


5350over.fm


1. Gather useful information—requires knowledge instrumenting of the OpenScape compo-nents to generate the information.

2. Analyze the gathered information

a) Analyze and derive OpenScape system characteristics for the administrators (e.g. trouble shooting, resource utilization

3. Distribute / use / report the analysis

The third step completes the knowledge loop by delivering the analysis to the system adminis-trators and other components for appropriate action. The scope of Knowledge Agent is to de-liver part of the analysis to the system administrator through user notification service. Value-added resellers (VARs) and independent software vendors (ISVs) have the opportunity to pro-vide rich reports using powerful third party reporting tools like Crystal Reports.

1.3.17 Context Agent

The Context Agent performs the following functions:

● Implements the OpenScape Presence and Availability Model and provides access to this model.

– Receives presence status information on registered SIP devices for OpenScape users from the Microsoft Presence and Availability Service (PAS) component of a Microsoft LC Server.

– Aggregates presence status by media type.

– Maps between the Microsoft and Siemens Presence and Availability models.

● Provides the OpenScape portals with access to the contact (buddy) lists of OpenScape us-ers.

– Receives contact list and Access Control List (ACL) information on OpenScape users from the Microsoft PAS.

– Filters the contact lists to limit membership to OpenScape users.

– Provides updates to the portals when the OpenScape presence and availability of watched contacts change.

● Logs Session Interaction Data from other components to Intermediate Persistent Storage for the XDR Service.

1.3.17.1 XDR Real-time Data Recorder

The data provider components In the OpenScape system generate session (transaction)-relat-ed data on the activities of OpenScape users. The XDR-Real-time Data Recorder stores the data rapidly into Intermediate Persistent Storage (IPS).



5350over.fm


1.3.17.2 Context Data Record (XDR) Service

The XDR Service periodically reads the IPS produced by the various instances of the XDR-Real-time Data Recorder. Based on the data category (session or session interaction), the XDR Service processes the data and stores it in a database. After the data has been success-fully stored, IPS files are deleted. The XDR Service stores the data into XDR database (SQL Server). Only completed records will be stored in the database. All incomplete records will be stored in a flat file

The XDR service performs a similar function to Call Detail Recording (CDR) because it allows administrators to retrieve the data and use it for analysis, bill-back, etc.

Refer to the Administration Guide for information on the data stored by XDR.

1.3.18 Database Layer

The Database layer is responsible for communications between OpenScape applications and the OpenScape Data Repositories, which include Active Directory, CIM and a Relational Data-base.

The DB layer is implemented as a component integrated into each application in the format of a plug-in (DLL or assembly) that provides the interfaces for the application to access the data repositories and some required functions.

The DB layer provides a set of Helper classes to assist the application developer by encapsu-lating security, performance and connection management.

1.3.19 Serviceability

Serviceability is a group of components responsible for dependability, fault management, diag-nosis, inventory, and discovery services.

1.3.19.1 Serviceability Broker (SB)

The SB controls the startup and shut down of OpenScape components, monitors OpenScape and third party services, restarts OpenScape services when they fail, maintains an inventory of OpenScape components via registration, and provides location/auto-discovery services. Components interface with the SB using their Serviceability Agent (SA)

Additionally the SB provides an SNMP trap receiver that allows third party applications and HW components such as SIP phones to log errors to the OpenScape DB.


5350over.fm


1.3.19.2 Serviceability Agent (SA)

The SA provides interfaces for registration (inventory) and auto-discovery to OpenScape com-ponents. There would be a serviceability agent that is part of each component that uses the services of the serviceability component.

1.3.19.3 Platform Resource Monitor (PRM)

The PRM monitors resource usage and raises warnings when certain thresholds are exceed-ed. Memory, CPU, and disk resources are monitored.

1.3.19.4 Trace Library

The trace library provides an interface to components to log errors, warnings and to generate trace files. Errors are written to the windows event log on the local host and to the SQL DB. Traces are sent to the Trace-Queue Service.

1.3.19.5 Trace-Queue Service

The Trace-Queue Service reads the trace messages from components and writes them to trace files per component. The Trace-Queue service manages the size and the number of trace files based on configuration data.

1.3.19.6 Trace File Accumulator (TFA)

The Trace File Accumulator collects trace files from multiple OpenScape Systems and/or Rout-ing Dispatchers and stores them on a single host.

1.3.20 Data Synch

The Data Synch component is an Active Directory Connector that synchronizes user data from AD to the OpenScape SQL DB. Data is synchronized to allow applications to cache it in mem-ory for real time access.

1.3.21 License Server

The License Server component interfaces to other components that check out licenses, check for the existence of licenses or monitor license usage in the system. The License Server com-ponent also contains a License Monitor (LM) that checks for the imminent expiration of tempo-rary licenses and for the use of licenses in excess of those installed (purchased).

This is achieved by having a scheduled task (the License Monitor) run daily, which uses the Li-cense Agent to read the installed licenses and check their validity periods. Warnings are logged when temporary licenses will expire. Warnings are also logged by the License Agent when the



5350over.fm


usage of a “counted” license type exceeds the installed unexpired count, and when an unin-stalled “uncounted” license type is reported “present”. These warnings will be reported at the time that the License Agent methods are used by the client applications.

1.3.21.1 License Snap-in and WMI Provider

This is the configuration interface to the licensing product. It provides an API to show all licens-es and where they are being used. It also tracks who is using what licenses as well.

1.3.21.2 License Key Generator

The License Key Generator is an off-line factory tool that will generate license files for customer systems. The file is encrypted with a public / private key pair, such that even if an individual de-termines the public key that enables the file to be decrypted, that individual will not be able to modify the file without invalidating it.

1.3.21.3 Installation

The Installation component is responsible for providing a program that installs all code and data needed.

Installation interfaces with every other component in the system that has software installed in the system. Each component has responsibility for a piece of code that installs itself called the ‘Component Install’. If a component has some data to be stored in the Database, or Active Di-rectory or Exchange Server, this ‘Component Install’ would write the data into the data store.

For upgrades, there is some functionality that resides in the Data Storage component that helps with the translation of data during the installation of the new software. This function is called during installation, and must be available at the time of installation; it cannot depend on the en-tire data storage component to be running.


5350over.fm

Nur für den internen Gebrauch An Overview of OpenScapeTool Suite Overview

1.4 Tool Suite Overview

The Tool Suite is available only with an OpenScape installation.

1.4.1 Deliverables

The Hipath OpenScape Tool Suite contains the following:

● Web Service-based SDKs:

– Front End Application support:

● CSTA III SDK (CSTA)

● Presence and Availability SDK (PA)

● User Notification Service SDK (UNS)

● Virtual Assistant SDK (VA) (released at a later time)

● Workgroup Assistant SDK (WA) (released at a later time)

– Back End Application support:

● Web Conference SPI (WC SPI)

● Application SDKs:

– Speech SDK (released at a later time)

– Third-party Phone Management SPI

– Management Interface (WMI)

In HiPath OpenScape V2.0, the SDK deliveries include:

● Installed CSTAIII, PA and UNS Request Web Services

● Installed CSTAIII and PA sample Event Web Services

● WSDL definitions for CSTAIII, PA and UNS Request Web Services

● WSDL definitions for the CSTAIII, PA and UNS Event Web Services

● Installed and working client samples of CSTAIII, PA and UNS applications

● Source for the CSTAIII, PA and UNS client samples and Event Web Services.



5350over.fm

Tool Suite Overview

1.4.2 Web Services-based SDK Architecture

Figure 1-5 shows the generic architecture of the SDK services.

Communications between the applications and the Siemens SDK is via Web Services. These web services communicate via SOAP/XML over HTTP.

Figure 1-5 SDK Architecture

As the figure shows, a customer developing an application using the HiPath OpenScape SDK will need to code both the application as well as the Event Web Service to receive the HiPath OpenScape Service events.

Each Web Service is described via Web Services Description Languages (WSDL). In general, each SDK component has two web services (request and event) and thereby two WSDL files. The WSDLs for the Request Web Services may not be changed since they provide the descrip-tions of specific HiPath OpenScape Request Web Services. However, since the Event Web Services will be developed by the customer, the WSDLs for the Event Web Services may be changed to provide additional methods if necessary for the customer’s application.

Customer Environment OpenScape Components

SOAP/XML requests to Event Web service

SOAP/XML requests to Event Web service

Events

Requests

ASP.Net EventWeb Service

Applications

Applications

Applications

ASP.Net RequestWeb Service

CSTAPA

VA

WA

OpenScapeServices

Customer ComponentFunction

CSTA

PA

UNSWA

Requests

OpenScape ComponentFunction

Event information

Request flow


5350over.fm

Nur für den internen Gebrauch An Overview of OpenScapeCall Flow Examples

1.5 Call Flow Examples

This section provides examples of basic call flows.

1.5.1 Basic Call Using Click-to-Dial from Portal

Scenario: (Figure 1-6) User A initiates a call from their portal to User B (non OpenScape user)

1. In this scenario the request for the call is transferred from the Portal to the OpenScape ap-plication (1).

2. The request causes the OpenScape application to initiate a call to the preferred voice de-vice of user A. User A answers the call and is placed in a hold state until the call is com-pleted to Party B. The steps to establish this call are shown in (2).

3. Once User A is connected, a call is placed to Party B. The steps to establish this call are shown in (3). Party B sends an answer by selecting the media that it can support from A’s media offer that was offered to it.

4. Once OpenScape has this information, it repeats the call setup to User A with the media capabilities of Party B. This is shown in (4).

5. The response to the Re-Invite contains the media answer from User A indicating the se-lected media for the call. This is sent to Party B in an ACK. This allows the two terminals to establish the media stream.



5350over.fm

Call Flow Examples

Fig

ure

1-6

Bas

ic C

all U

sing

Clic

k-to

-Dia

l fro

m P

orta

l


5350over.fm


1.5.2 Basic Call Between OpenScape Users

Scenario: User A initiates a call to User B. In this scenario, User A Initiates the call using their SIP terminal.

1. This generates an Invite (1) addressed to User B. As part of the processing for the invite in the OpenScape application, any outgoing rules that User A may have for operations such as logging the call take place.

2. In addition the OpenScape application will evaluate User Be’s current identity context, rules, and device presence to determine the correct device to process this call. This is the device that is selected to receive the invite (2). When the selected device of User B re-ceives the Invite it responds with an indication that the device is ringing.

3. This is passed to the OpenScape application and on to the terminal of user A (3).

4. When User A answers the call, an indication that the device is call is answered is sent (4). This is passed to the OpenScape application and on to the terminal of user A.

5. When the answer is received by User A’s terminal it responds with an ACK that is sent to the OpenScape application and on to User B’s terminal (5).

At this point in time the two terminals are able to establish the media stream for the call.



5350over.fm

Call Flow Examples

Fig

ure

1-7

Bas

ic C

all B

etw

een

Ope

nSca

pe U

sers


5350over.fm


1.5.3 Basic Conference Call

Scenario: User A selects a list of parties (user B and C) to be part of the conference from their portal.

1. Once the list is selected the conference operation is selected. The request for the confer-ence is transferred from the portal to the OpenScape application (1).

2. The request causes OpenScape to allocate resources for the conference from the MCU resource controller (2)

3. OpenScape then initiates a call to the MCU. The MCU answers the call and is placed in a hold state until the call is completed to User A. The steps to establish this call are shown in (3).

4. Once the MCU is connected, a call is placed to the preferred voice device of User A. The steps to establish this call are shown in (4). As part of answering the call, User A sends it’s media answer to the media offer from the MCU.

5. Once OpenScape has this information, it repeats the call setup re-Invite to the MCU with the media answer from user A. This is shown in (5).

6. The MCU selects the media to be used for the call and this is sent to user A in the ACK message.

This allows the terminal and the MCU to establish the media stream. The sequence 3-6 are repeated for each participant in the conference (B and C).



5350over.fm

Call Flow Examples

Fig

ure

1-8

Bas

ic C

onfe

renc

e C

all


5350over.fm

Nur für den internen Gebrauch An Overview of OpenScapeSystem Capacities

1.6 System Capacities

1.7 No Special Handling for Emergency Calls

Note the following:

● OpenScape does not provide any special emergency call processing.

● Depending on where the SIP gateway is located, the emergency call may be routed to a fire or police department that is in a different location from the caller.

● Emergency calls do not have a higher priority higher than other off-net calls. Emergency calls are completed only if there is a free trunk available at the time an emergency call is initiated.

Maximum number of OpenScape users 2000

Maximum number of MCU connections One MP with the minimal hardware re-quirements can support:● 72 channels G.711 ● 24 channels of G723.1

Can have up to 4 MPs

Maximum number of parties in conference 288

Maximum number of Media Server ports One Media Server with 30 ports

Maximum parties in a single conference 72



5350over.fm

No Special Handling for Emergency Calls


5350man.fm

Nur für den internen Gebrauch ManagementArchitecture

2 Management

This chapter describes the various components of OpenScape management, including the ad-ministration interface (the OpenScape Management Console, or OMC).

2.1 Architecture

OpenScape configuration management is built on a three tier architecture as illustrated in Fig-ure 2-1.

Figure 2-1 Architecture of OpenScape Management Console

The Presentation Tier is an application tier that has access to the OpenScape management objects. The management objects are defined with DMTF – MOF classes (Distributed Manage-ment Task Force - Managed Object Format). These classes are accessible via the Microsoft provided WMI services (Windows Management Instrumentation). In particular MOF classes can be accessed via APIs (managed/unmanaged) or with the Windows Script Host (WSH) us-ing VBScripts or JScripts.

The Configuration Logic Tier is the implementation of the exposed managed objects. MOF objects are implemented as WMI providers that are hosted in the WMI Managed Provider Ser-vice. This tier contains the configuration rules that ensure data consistency.

The Data Repository / Managed Component Tier is where persistent data is stored or where dynamic data is retrieved.

.

OMC 3rd party applications

JScript VBScript

WSH

Presentation Application Tier

WMI Services (Microsoft)

Provider Provider Provider Provider

Configuration Logic Tier

Data RepositoryManaged Component Tier

DIR DBFS

ManagedComponent

ManagedComponent


Management Nur für den internen Gebrauch

5350man.fm

Interface

2.2 Interface

The OpenScape Management user interface, provided as a snap-in, provides the following functions:

● Using the WMI interface and the database layer API, examines and modifies OpenScape configuration information that is stored in the Windows Active Directory / SQL database, primarily in the form of user profiles and device profiles.

● Through an interface with the Serviceability Broker, monitors and updates serviceability and dependability data in other OpenScape applications (as exposed using the Service-ability API in the application).

● Using the Microsoft .NET System.Management API and the OpenScape Management Schema, monitors and updates configuration data within OpenScape applications.

The OpenScape snap-in may be loaded into the MMC together with other snap-ins provided by Microsoft or third parties. This allows for a seamless transition between Windows and Open-Scape administrative tasks. Dedicated OpenScape administration group facilitates manage-ment.

Management access to the data repository is done through a WMI interface on the OpenScape server. The OpenScape snap-in can connect to one or more OpenScape servers locally or re-motely using this WMI interface. Security for remote access is provided by the Microsoft WMI framework. The WMI interface can also be accessed by the Windows Script Host (WSH). JScript or VBScript applications can be written to automate management functions or to exe-cute operations in batch mode. The functionality available through WSH is the same as the one provided by the OpenScape snap-in.

The management snap-in provides multi-language support. English and German are currently provided. The language is automatically set based on the Windows user locale.

There are three server components in OpenScape: the Communication Broker, MCU, and Me-dia Server. In the current version of OpenScape, only the Communication Broker is fully inte-grated into the Windows management architecture as shown in Figure 2-1. The MCU provides a native Win32 user interface and the Media Server provides native web-based management interfaces.

Microsoft SQL Server 2000 is used for the data repository. Database management tasks are described in Section 2.9.2 on page 2-10.


5350man.fm

Nur für den internen Gebrauch ManagementLicensing

2.3 Licensing

In OpenScape V2.0, customers purchase licenses for the feature packages described below. User licenses are purchased separately for each package.

● The HiPath OpenScape Version 2.0 Core Package (required):

– Personal Portal, including rules engine, presence, contact list, etc. Refer to Chapter 3 for a complete description of the Personal Portal.

● The HiPath OpenScape Version 2.0 Collaboration Package (optional). Refer to Chapter 5 for a complete description of the Workgroup Portal.

– 288 conferencing sessions

– Ability to initiate WebEx or LiveMeeting with a single click (if the customer subscribes to one of these services)

● The HiPath OpenScape Version 2.0 Voice Portal Package (optional). Refer to Chapter 6 for a complete description of the Voice and Self-Service Portals.

– Voice Portal and Self Service Portal features.

– Additional Media Server sessios licenses must be purchased to support the number of users and the traffic patterns.

In addition to the feature packages described above, developers can buy the OpenScape Tool-Suite or the OpenScape Speech Toolkit. Customers who purchase applications developed with the Tool Suite must also purchase application deployment licenses.

2.4 OpenScape Management Console

The administration interface for OpenScape, the OpenScape Management Console (OMC), is available in two languages, English and German.

The Siemens-developed OpenScape snap-in, which is a DLL that runs under an instance of the Microsoft-provided mmc.exe process, has multiple functions, where each function is repre-sented as a tree node. Within the OpenScape snap-in, there is one primary node and multiple child nodes for each installed OpenScape server. These OpenScape servers are automatically discovered by the OMC.

For each OpenScape system node the following functions are available:

● User Management—administers OpenScape user data, based on existing Windows LCS user accounts.

● Device Management—administers Siemens SIP phones.

● Application Management—administers database configuration, trace management, and other functions on a per-application basis.



5350man.fm

Server Management

● System Management—administers other options and settings.

Configuration operations that modify the data repository are logged in an audit trail. The audit trail information indicates for each operation the time and date, the data being changed, and the administrator’s account.

2.5 Server Management

The administrator can start or stop the OpenScape software and verify the current state of the OpenScape server, including the following conditions:

● An error has occurred while trying to determine the state of the OpenScape software

● The OMC is currently trying to determine the state of the OpenScape software.

● OpenScape software is up and running.

● OpenScape software is stopped.


5350man.fm

Nur für den internen Gebrauch ManagementUser Management

2.6 User Management

The administrator can access user information for all OpenScape users from a central location, regardless of the user’s associated OpenScape server.

To add an OpenScape user, the administrator must first enable a new or existing Windows user account for LCS. This can be accomplished using either the Microsoft LCS Server MMC Snap-in or the Microsoft AD (Active Directory) MMC Snap-in. The administrator then uses the Add New User Wizard to create a new OpenScape user from a LCS user.

The system administrator manages following parameters associated with each user:

● The OpenScape user ID number

● Password—The administrator can reset a user’s password

● Phone Numbers —an OpenScape user can have a public (DID) number as well as an ex-tension number.

● Whether the user is also a Media Server user

● User Group—whether the user will be added to the User group or the OpenScape Admin-istrator group.

2.7 Device Management

The Device Management function allows administrators to manage optiPoint 400 SIP V3.0 phones. It provides Phone Management and Real-time Transport Protocol (RTP) Statistics.

2.7.1 General Parameters

Administrators can manage the following general parameters for the SIP phones:

● The start date and time and recurrence for data synchronization

● Common data parameters for all SIP phones, including

– SIP session timer and timer value and registration timer

> Although the system administrator can configure an optiPoint 400 SIP phone using the phone’s menus or the phone’s Web Management Interface (each phone has a built-in web server), it is recommended that the system administrator uses only OMC to configure optiPoint 400 SIP V3.0 phones for OpenScape users.

> The OMC provides management of Siemens SIP phones only; third-party SIP phones have their own management interfaces.



5350man.fm

Device Management

– SNMP parameters

– QoS parameters

● Phone-specific data profiles used when configuring new phones. The administrator can add new profiles, for example for executives, for lobby phones, etc.

● The default phone administration password and the default wildcard server certificate that are used to configure new OpenScape phones.

● The parameters to be used to discover the phones for a particular OpenScape system

2.7.2 Phone-specific Parameters

The administrator can view and configure the phones associated with the OpenScape users in that system. Only phones that have been configured via the OMC are displayed. For an indi-vidual phone or group of phones, the administrator can modify the following settings:

● Which LCS server the phone is associated with

● Network settings

● Authentication settings such as Kerberos Key Distribution Center (KDC) server address and port

● System settings such as voice mail destination and number for message waiting

● Timers for presence and availability

● File Transfer settings such as FTP server address and account name

● Time & Date settings such as whether daylight savings is off or on.

● Speech settings for jitter buffer, compression codec, audio mode, and silence suppression

● Regional settings for country and language

● Settings (on or off) for components such as instant messaging and contacts

● Key layout

● Menus

● Dial plan

In addition, the administrator can:

● Disassociate a phone from an OpenScape user. This causes the phone’s data to be reset in the phone and removed from the OpenScape database.

● Initiate software updates for the phones. The administrator can also download a new file for Music-on-Hold.


5350man.fm

Nur für den internen Gebrauch ManagementDevice Management

● Initiate a consistency check between the data stored in the phones and the data stored in the OpenScape database.

2.7.3 Parameters for a Single SIP Phone

The administrator can manage the following parameters for a single SIP phone:

● General data about the phone and associated user

● Security settings, including:

– The local administrator password stored in the phone

– The user password stored in the phone

– The Windows password that the phone uses to authenticate itself with the LCS server

– The Server Certificate and Private Key stored in the phone that is used to enable a secure connection on the phone’s external interfaces

2.7.4 Administration of Unassigned SIP Phones

The administrator can manage the Siemens IP phones detected via the auto-discovery protocol that have not been configured for OpenScape. The administrator can:

● Configure the phones (assign the phones to OpenScape users)

● Reset the data stored in the phones

● Initiate software updates for the phones

2.7.5 Management of RTP Statistics

The administrator can manage RTP statistics as follows:

● Turn on and off the collection of RTP statistics

● Enable and disable the collection of RTP statistics for a specific phone.

● Retrieve the statistics files on the local machine

● View the statistics files

● Set the maximum number of statistics files and the maximum size per file



5350man.fm

Application Management

2.8 Application Management

The administrator uses Application Management to administer data, options settings, and trace operations for the various applications (services) in the OpenScape system. The Application Management screen lists every OpenScape Service, with its current software version informa-tion and execution state.

2.8.1 Application Properties

This section describes the properties that can be administered for the various services in the OpenScape system.

2.8.1.1 Community Assistant

The following properties can be administered for the Community Assistant (Workgroup) appli-cation:

● Access to Collaboration Web Page—used to enter the URLs of the internal and external Collaboration web site.

● Collaborations—the maximum number of collaborations, the maximum number of mem-bers per collaboration, the maximum number of parties in a conference, and an indication of whether or not the call should be dropped when only non-OpenScape users are left in it.

● Email—the default email text that is sent in various situations with the Workgroup Portal.

2.8.1.2 Data Synchronizer

The OpenScape Data Synchronizer application synchronizes LCS user data stored in the Win-dows Active Directory with corresponding user data in the OpenScape database.

This application contains one configurable property, the synchronization interval, which speci-fies the interval for the one-way synchronization from the Active Directory user information to the OpenScape user information. This synchronizes users from all Active Directory domains that house a user for this LCS Server.

2.8.1.3 Platform Resource Monitor

The Platform Resource Monitor application monitors administrator-defined system and pro-cess resources by polling them in regular intervals. The administrator can specify how often the resources should be polled.


5350man.fm

Nur für den internen Gebrauch ManagementApplication Management

2.8.1.4 Context Data Recorder

The Context Data Recorder (XDR) application provides per-session logging. The administrator can configure:

● The data category:

– Session Data: information regarding calls and messaging between various endpoints for OpenScape users

– Session Interaction Data: information associated with call sessions such as account codes, subject, etc.

– Presence information for OpenScape users.

● Periodicity—Context data is eventually stored in the database for persistent storage from intermediate locations at periodic intervals. The Periodicity defines the interval in the range of 1 to 3600 minutes.

● Disk Quota—the maximum hard disk space used by context data intermediate locations. The quota defines the space in megabytes with a minimum value of 10MB.

● Generate Switch -If not selected, the context data for this data category would not be stored.

● Intermediate Persistent Storage (IPS) location for the data category.

● Incomplete Record Location - Context data location to store the incomplete records for the data category. This data will be moved to database once the records are completed.

2.8.2 Trace Control

The following trace control settings can be administered:

● Trace Settings

– The maximum number of trace files that can be generated by the application, and the maximum size each file can attain before another trace file is created.

– The trace level value and trace status (enabled or disabled) for each sub -component in the selected application.

● File Retrieval —retrieves the generated trace files for selected application from the server on which the application is running, and stores those files on the system on which the OMC is running.



5350man.fm

System Management

2.9 System Management

System Management is used to administer system options settings (those that do not relate to a specific application), and to invoke various system-related tasks.

2.9.1 System Data Function

The System Data function is used to configure system-wide data such as:

● Security certificate used by OpenScape

● Interface ports used by the various OpenScape software interfaces

● Default phone number type and number rules—defines whether the Phone Number field in Active Directory is used to create the Phone Number (Secondary URI) of a OpenScape user or the administrator enters the Phone Number individually for each user.

● Dynamic Port Range for the range of communications ports used by the various Open-Scape services.

OpenScape internally uses dynamic ports for communication. The administrator has the option to define the range of consecutive ports that can be used at runtime by the Open-Scape services. The low port number has to be greater than 1024 and lower than the high port number. The range has to be at least 30 in order for the system to operate properly. It is recommended that the dynamic ports start at higher numbers to make sure that they don't interfere with reserved ports (1025~10000).

2.9.2 Storage Administration

This function allows the administrator to invoke on-demand backup, restore, and purge opera-tions for the OpenScape database and to schedule operations for later (and repeated) execu-tion.

2.9.2.1 Database Backup

The administrator can back up the OpenScape database to a location accessible from the local servers file system. Three types of backup are available:

● Full— backup all OpenScape database files

● Incremental—back up only files modified since the last backup of the transaction log.

The backup can be scheduled or on-demand.

There is no system-wide backup, so it is the responsibility of the administrator to perform the following backups:


5350man.fm

Nur für den internen Gebrauch ManagementSystem Management

● Back up OpenScape via the OMC on a regular basis. The system prompts the administra-tor to perform a backup before a software upgrade.

● Back up Active Directory

● The Media Server and the MCU must be backed up manually.

2.9.2.2 Database Restore

The administrator can restore the OpenScape database from a location accessible from the local servers file system.

2.9.2.3 Database Export and Purge

The Purge function can be used to delete historical voluminous data that is no longer needed by the system, but which is occupying a lot of database space. The following types of Purge are available:

● XDR Session data in the SQL database XDR data can be exported to a file and optionally be purged after the export operation completes.

● Event Logs in the SQL Database

● Aged Orphaned users in the SQL database.

The Purge should be run from the OMC Storage Management screens during idle conditions when there is minimal load on the system. It can be run on-demand or scheduled to run at re-curring intervals.

2.9.3 Storage Monitor

The administrator can monitor the OpenScape database and view the log file generated by that task. The log file can also be saved as a Word or text document.

> NOTE: A backup should be taken at a time when the system is idle or under very low load. This ensures that the performance of other system components is not affected during backup and also that the backed up data is in a consistent state.

For a restore, the system has to be in an idle state and may also require that some of the services/components be stopped completely. For backup purposes a separate device is required at the customer site. Currently only disk devices will be supported.



5350man.fm

System Management

2.9.4 Knowledge Management Reports

This function allows the administrator to:

● Specify where email notifications for the Fault Diagnostic Report or System Statistics Re-port should be sent

● Schedule the System Statistics Reports

● View the Fault Diagnostics and System Statistics Reports

Refer to the Administration Guide for detailed descriptions of these reports.

2.9.5 Resource Monitor

Resource Monitor monitors resource usages of OpenScape system. The monitored resources can be grouped in two categories: system resources and application resources. The system resources that are monitored for the host machines running the OpenScape system are CPU, hard disk and memory. The application resources that are monitored for each OpenScape ap-plication are CPU and memory.

The following resources can be monitored by the Platform Resource Monitor service:

● The remote host machines running on the OpenScape server. A new host machine can be added

● All services that are running on the OpenScape server. The administrator can manually enter a host machine name or IP address, or select a machine name from the pull-down list. The administrator can set the upper and lower thresh-old values, expressed in percentages (from 1-100 for upper threshold, 0-99 for lower thresh-old) as well as the monitored disk drive.

2.9.6 Systems Destination

The Systems Destination function maps Media Server rules to Addresses-of-Record.

2.9.7 Portals Management

The system administrator can use the Portals Management function to add a new portlet, de-lete an existing portlet, or modify the properties of a portlet such as URL, minimum width and height, and whether the portlet is sizable.


5350man.fm

Nur für den internen Gebrauch ManagementOMC Snap-Ins

2.9.8 SDK Management

The administrator can use the SDK Management function to add a new SDK application, delete an existing SDK application, or change the properties configured for an application such as ap-plication type, certificate information, and password.

2.9.9 Web Conferencing SPI

From OMC, the administrator can launch the relevant web page for configuring the Web Con-ferencing Connectors / SPI and can enable or disable any connector that has been configured.

2.9.10 Licensing Management

The Licensing Management function allows the administrator to:

● Configure the administration and client ports of the license server

● View the installed and checked-out licenses

● Install a license key file

● Schedule the license monitor task

2.10 OMC Snap-Ins

There are two new snap-ins for OMC in V2.0 of OpenScape:

● The Trace File Accumulator Snap-in (TFASI) is used o configure Trace File Accumulator data settings.

● The Routing Dispatcher Snap-in is used to configure routing dispatcher server data and trace settings.

2.11 Administration of Other Components

The following components use their own administration interfaces:

● SIP Gateways

● MCU

● Media Server



5350man.fm

Fault Management

2.12 Fault Management

Fault management provides four distinct functions:

● Error collection: Archives errors and warnings generated by OpenScape components. This includes Siemens SIP phones, MCU, Media Server, and the OpenScape core applications. Errors are posted into the Windows event logs. Third-party components or applications such as gateways can also send errors to the OpenScape management via SNMP.

● Error analysis: Performed on the collected data. If it is determined during error analysis that actions need to be taken by the administrator, a report detailing these steps is generated. Also if error analysis determines that the system is in a critical state and requires immedi-ate intervention, a notification is sent to the administrator.

● User notification: Notification targets can be configured for e-mail, page, SMS, and Instant Messaging.

● Trace utility: An extensive trace utility is provided as described in Section 2.8.2 on page 2-9.

2.13 Installation of OpenScape

All OpenSpace client applications and server components are provided as Microsoft Installer (MSI) packages. The server packages are: Communication Broker, MCU, and Media Server. The client packages are the Management snap-in, Windows Management Add-In, and Outlook Add-In. Installation wizards are provided. Automation of client distribution can be achieved by using the IntelliMirror feature in Active Director.


5350Pport.fm

Nur für den internen Gebrauch Personal PortalPersonal Portal in a Browser Window

3 Personal Portal

The Personal Portal provides a unified way to manage all communication tasks, handling voice calls, emails, and instant messages. It can be:

● Accessed via Internet Explorer (Figure 3-1)

● Accessed as a Microsoft Outlook folder web page (Figure 3-2 on page 3-3)

● Accessed as a tab in Windows Messenger (Figure 3-3 on page 3-4)

3.1 Personal Portal in a Browser Window

Figure 3-1 shows the Personal Portal in an Internet Explorer (IE) browser window.

Figure 3-1 Personal Portal in Internet Explorer

> Note that OpenScape uses the Exchange 2000 or Exchange 2003 server. For the desktop client, users can have Outlook 2000 or higher.


Personal Portal Nur für den internen Gebrauch

5350Pport.fm

Personal Portal as Outlook or Messenger Plug-in

3.2 Personal Portal as Outlook or Messenger Plug-in

The Personal Portal can also be accessed as a plug-in in Outlook or Windows Messenger.

3.3 My Status

My Status is the primary variable that OpenScape checks to determine how to route commu-nications. It provides a basis for the rules that give users control over how their communications work.

In addition, any OpenScape user can view the status of another user who has been configured as a contact.

The predefined statuses that users can select from are:

● Working remotely

● In Office

● Be Right Back

● In Meeting

● No Interruptions

● Out of Office

● On Business Trip

● On Vacation

Refer to Section 3.11 on page 3-7 for more information on how My Status is used.

> Windows XP is required in order to have the Personal Portal appear as a Windows Messenger tab.

> There is no correlation between status in OpenScape and status in Windows Mes-senger. An OpenScape user’s status must be set manually; there is no option to change status automatically.


5350Pport.fm

Nur für den internen Gebrauch Personal PortalMy Preferred Phone

3.4 My Preferred Phone

Users set their preferred voice device from the Personal Portal. Other preferred phones and de-vices are available and configured with Options...Devices. (Refer to Section 3.9 on page 3-6 for more information about devices.)

For maximum flexibility, users can configure a number of associated devices and then set their rules (described in Chapter 4) to route incoming calls to the preferred device. An outgoing call that a user places through My Calls is routed through the preferred device.

3.5 My Calls

My Calls allows users to:

● Place a call on the device that has been designated as the preferred device.

● Start a conference call.

● View the status of current calls.

● Take actions on current calls: put on hold, release the hold, hang up, add a caller, or show the parties in the call.

Note that My Calls knows only about the calls that are routed through OpenScape. For exam-ple, if someone calls a user’s OpenScape number and is routed to his cell phone, then Open-Scape continues to monitor the progress of the call and can act on it. However, if a caller dials a user’s cell phone directly, then OpenScape has no knowledge of the call and cannot act on it.

The Number field is provided for users to enter the phone numbers of parties who are not in their contact list or their Outlook Address book.

3.6 My Contacts

My Contacts allows users to manage their contacts and take the following actions:

● Add a new contact or remove a contact

● Start a voice conference or a multimedia conference (using web conferencing tools such as WebEx and Live Meeting) with contacts

● Place a phone call, send an IM or an email to a contact

● View a contact’s status

● View the contact’s availability for a phone call, IM, and email. (However the contact can use Windows Messenger to block someone from viewing his status and media availability.)

● Use the Tell Me When feature to set a reminder so that you can be notified when a contact becomes available.



5350Pport.fm

My Contacts

The icon next to the contact's name indicates whether that person is reachable by phone, in-stant messaging, or email.

3.6.1 Contacts in Outlook

OpenScape contacts are separate and distinct from Outlook contacts. There is no facility to im-port contacts from Outlook to OpenScape or vice-versa.

In OpenScape, the term contacts is used in the same sense that Microsoft uses the term for Windows Messenger. It essentially means a buddy in the buddy list. In OpenScape V.1, these contacts are limited to other OpenScape users. When users use the Address Book as an input source to select parties for a conference, they can access only the Global Address Book (not the Contacts Address Book).

In Outlook, contacts describes names and addresses that a user saves in the Outlook address book. These people tend to be external to the enterprise. The Contacts directory in Outlook is unique for each person and can be accessed in the same way that the Global Address Book is accessed through the Address Book function.

OpenScape users can configure special properties for their Outlook contacts (that is, for people external to the enterprise) that allow them to have guest access to OpenScape and the features of the Self-Service Portal. (Refer to Section 6.2 on page 6-4 for information about the Self-Ser-vice Portal.)

3.6.2 Contacts in Windows Messenger

OpenScape users configure their contacts using Windows Messenger and must use Windows Messenger to delete a contact. However, a user’s list of contacts in Windows Messenger can contain non-OpenScape as well as OpenScape users.

From Windows Messenger, a user has access to all of the users known to the LC server. These include the following:

● LC users that are not OpenScape users

● LC users that are OpenScape users on the same OpenScape system as the user config-uring their contacts

● LC users that are OpenScape users on other OpenScape system that the customer may have in their network.

Any of these can be added to the user’s contact list in Windows Messenger. But only other OpenScape users that are part of the user’s OpenScape system can be added to the Open-Scape My Contacts list.


5350Pport.fm

Nur für den internen Gebrauch Personal PortalMy Workgroups

3.7 My Workgroups

From My Workgroups a user can:

● Add a new work group, delete a workgroup, or copy an existing one

● See the status of the existing workgroups (idle, voice conference in progress, web confer-ence in progress)

● Take action:

– Start a voice conference

– Start a multimedia conference

– View or edit the properties of a collaboration group

Only the person who set up the work group can modify it or delete members from it. When a work group is deleted, all information including membership, options, and documents are de-leted. A backup owner can take over when the owner is deleted (for example, when the owner leaves the company.)

Chapter 5 has more information on workgroups.

3.8 Other OpenScape Options

Users can also set their preferences for:

● The language of the Personal Portal

● Preferred device for instant messaging

● Preferred device for email

● Ring-no-answer timeout: the time interval that voice devices continue to ring before moving to the next step in the call process

● Password for web conferencing tool (such as WebEx, Live Meeting)

● Layout of the Personal Portal. Users have the ability to design a custom layout for the Per-sonal Portal by selecting the portlets, including web applications and web pages, that ap-pear in the Personal Portal.

Another option, the Rules Wizard, is described in Chapter 4.



5350Pport.fm

Devices

3.9 Devices

In OpenScape, device refers to any entity that can act as a communications endpoint: phones, instant messaging, or email. There are two categories of devices, registered devices and as-sociated devices.

● Registered devices are automatically configured for a user. SIP phones and Windows Messenger are considered registered devices because they register with a part of the LCS server called the SIP Registrar. They are automatically recognized by the system.

Each registered device has a name and an ID key. For phones, the ID key is the physical address of the phone. For Windows Messenger, it is the name of the machine that it is run-ning on. Users can edit the name of the registered devices but cannot change the ID key. They can also edit the supported modes of the device (voice, IM, email) unless supplied by the device itself (as is the case with the Siemens SIP phones.)

● Associated devices must be configured by the user.

A user can create an associated device by entering the name and contact information (phone number, IM address, or email address) and its initial status (offline, online, or busy). To subsequently change the status for that device, the user must set it manually.

3.10 Interaction with Windows Messenger

Windows Messenger provides an OpenScape tab as an alternative way of accessing the Per-sonal Portal. In addition, Windows Messenger:

● Can be one of a users’ registered devices. Windows Messenger can be configured to be enabled or disabled from specific communications modes such as voice, email, and instant messaging.

● Provides the ability to add and delete contacts and manage the allow / block list.

● Provides the instant messaging window for sending and receiving instant messages.

Users can take advantage of the Windows Messenger capabilities such as application sharing, file transfer, and point-to-point video when cameras are installed.

Because Windows Messenger availability is taken into account by OpenScape when it consid-ers to which device a particular voice call, email, or instant message should be delivered, it is recommended that OpenScape users should mark themselves Online when they want their Windows Messenger to be included and mark it Away when they do not want it included.


5350Pport.fm

Nur für den internen Gebrauch Personal PortalOpenScape Presence and Availability Model

3.11 OpenScape Presence and Availability Model

The OpenScape presence and availability model is based on the Microsoft presence model and enhances it with value-added Siemens propositions. It consists of two separate elements:

● A user-level presence (status) set with My Status in the Personal Portal

OpenScape users manually set their status to show whether they are in the office, in a meeting, on vacation, working remotely, etc.

● An overall availability for each media type (voice, email, instant message) that is support-ed by any of the devices owned by a user. The overall availability for each media type takes into account the state (busy, online, unknown, offline) of each device that supports that me-dia type. Then those states are combined (or aggregated) to determine overall availability.

There is no direct link between a user’s status and the overall availability for each media type. While the media states are aggregated from actual device settings, the status is not.

3.11.1 Status

Every OpenScape user has a status at all times. Status can be set from the Personal Portal or the Voice Portal and can be one of the following:

● Working remotely

● In Office

● Be Right Back

● In Meeting

● No Interruptions

● Out of Office

● On Business Trip

● On Vacation

There is an additional status value of “Unknown” that is used by the OpenScape system in sit-uations where the status is not currently available or where the user is prohibited from seeing the status value. Note that only the OpenScape system can set this value; users cannot.

Status is one of the key means by which an OpenScape user personalizes the behavior of the OpenScape system. In particular:

● Status determines which rule set will be applied for the user.

● Status is displayed as part of the contact list for each of the contacts who are OpenScape users.



5350Pport.fm

OpenScape Presence and Availability Model

3.11.2 Availability

Availability applies to the following media types:

● Voice

● Instant messages

● Email

As Figure 3-2 shows, it is arrived at by taking into account whether each device that is capable of that media type is busy, online, offline, or whether its availability is unknown. Those individual states are summed up to arrive at the combined availability.

Figure 3-2 Overall Availability by Media Type

Based on the availability information about each media type (for example, available via phone, not available via instant messaging, available via email), OpenScape can make the appropriate routing decision.

IM Voice IM Voice IMEmail Voice Voice

Combinedavailability for IM

Availability for voice

Availability for IM

Availability for email


5350Pport.fm

Nur für den internen Gebrauch Personal PortalOpenScape Presence and Availability Model

Besides enabling OpenScape to make routing decisions, the overall availability by media type also appears for each contact on the Contact List in the Personal Portal.

3.11.3 Enhancements to Microsoft Model

The Siemens Presence and Availability Model provides the following enhancements to the na-tive Microsoft presence model:

● Support for other, non-SIP registered devices (associated devices)—This extends the reach of the communications solution to legacy devices (connected to private networks, the PSTN, the CSPN, etc.)

● Aggregation by media type—This provides users with a better idea of what kind of commu-nications their contacts are willing to accept.

● A single, user-level presence attribute (status)—This provides centralized control and avoids the confusion that a number of competing devices can cause.

● User-visible presence attributes that are more appropriate to an enterprise environment than consumer-oriented values used by Windows Messenger.

● Communications rules based on the user’s status—These provide more appropriate be-havior than that provided by default in the Microsoft solution.

● Ability to manage basic presence (user status) from any telephone in the world and from any web browser that can access the OpenScape site.

> If a user is accessible by any phone device such as an office phone, a home phone, or a mobile phone, OpenScape simply makes the assumption that the user is available via phone. If a user is currently in an active voice call on any of her monitored devices, then she is considered busy. If she is not busy in a voice call, then if she is accessible by any of her phone devices she is considered available for voice.



5350Pport.fm

OpenScape Presence and Availability Model

3.11.4 Interaction with the OpenScape Presence Model

The following are recommended guidelines for OpenScape users:

● Use OpenScape’s My Status (and the associated rule set) to indicate their own personal status and control which OpenScape rules are in effect.

● Use Windows Messenger Status only to indicate the availability of their Windows Messen-ger device.

> It is important to note the difference between status of a user and information that OpenScape retrieves about the dynamic state of a device.

The user always sets My Status (In Office, In Meeting, On Vacation, etc.).

For SIP phones, OpenScape can detect if it is available (Offline or Online) as well as its current state (Offline, Do-Not-Disturb, Unknown, Busy, Forwarded, Online). This includes dynamic call states (in call, etc.).

For Windows Messenger, OpenScape can detect if it is available as well as the user-set device status (online, busy, be right back, away, on the phone, out to lunch). OpenScape does NOT get dynamic call status for Windows Messenger devices.

For an associated device, OpenScape cannot detect its dynamic state so the user must set this directly in the Options – Devices – Associated Devices screen to values of Online, Offline, or Busy.


5350rules.fm

Nur für den internen Gebrauch Rules Wizard

4 Rules Wizard

With the Rules Wizard users set up rules to determine how, when, and where they can be reached. For example:

For an incoming call received after Wednesday November 12th, 2003 and before Wednesday November 19th, 2003 and received after 16:00 PST and before 04:00 PST, redirect to cell phone and where redirect fails, redirect to voice mail and where redirect fails, notify by SMS to cell phone with 'missed call'.

A user creates a rule with the Rule Wizard and puts it into effect by assigning it to one or more statuses (Working Remotely, In Office, etc.). When a user sets My Status, only those rules that are assigned to this status are executed when a primary condition is triggered.

Each rule consists of:

● Conditions—the user selects one of the following primary conditions:

– For a change in my presence (referring to the user’s own status or availability)

– For an incoming call

– For an outgoing call

– For an incoming instant message

– For an outgoing instant message

– For an incoming email

This selection determines the set of supported conditions, actions, and exceptions that are unique for each primary condition.

● Additional conditions with parameters

After selecting the primary condition, the user can optionally select one or more associated conditions with parameters (such as dates or people) that make the rule more specific. No condition can appear in a rule more than once.

● Actions

A valid rule contains at least one action. The user can specify multiple actions (for example, redirect to cell phone AND where that redirect fails, redirect to voice mail). No action can appear in a rule more than once. Actions can be cumulative or conflicting:

– Cumulative actions: all actions are executed.

> The “My Presence” condition does not support additional parameters or excep-tions.


Rules Wizard Nur für den internen Gebrauch

5350rules.fm

– Conflicting actions: only the action belonging to the higher priority rule is executed. Pri-ority is determined by placement in the rule set, with the topmost rule set having high-est priority. (The rules can be reordered to reflect the desired priority.)

● Exceptions

After selecting actions, the user can optionally include one or more exceptions. The excep-tions are identical to the conditions but with “except if” or “except” added at the beginning. No exception can appear in a rule more than once. Multiple exceptions are separated by an OR. Therefore, if any exception is TRUE, the rule will be evaluated as FALSE and no action associated with that rule will be used.

For example: Assume that the rule states, For an incoming call from Bill Gates, redirect to my preferred device OR to My Assistant except if after 19:00 and before 08:00. If a call from Bill Gates arrived at 7:30 p.m., the call would not be redirected.

When there is no action that takes precedence, the default rules are used. The final default rule is “route to voice mail” so if no other condition or exception applied, the call would be directed to the user’s voice mail.


5350rules.fm

Nur für den internen Gebrauch Rules WizardRules for My Presence

4.1 Rules for My Presence

A user can create rules for incoming calls using any of the conditions in Table 4-2.

4.1.1 Actions for My Presence

A rule based on My Presence must have one of the following actions:

● Set Out-of-Office message (user defines the text message displayed)

● Set Interaction Center greeting

● Notify (by pop-up, email, IM, SMS, or page) destinations with specific message

● Log or don’t log to journal

Condition Parameter Values Multiple Entries?

Context type ● User status● Voice availability● IM availability

N

User status ● In Office● Working Remotely● Be Right Back● In Meeting● Out of Office● On Vacation● No Interruptions

N

Voice availability ● Online● Unknown● Offline● Busy

N

IM availability ● Online● Unknown● Offline

N

Becomes or changes from

● Becomes● Changes from

Y

Table 4-1 Conditions for My Presence



5350rules.fm

Rules for Incoming Calls

4.2 Rules for Incoming Calls


> When a term is underlined, (for example, people) it indicates that the user has to specify parameters. In the Rules Wizard, the underline signifies a link that displays the available values or a place to enter data.


From people Names from Outlook directory, contact list, typed in, or a pre-saved user defined list.Typed SIP URIs or phone numbers (including wildcards at the beginning or end)

Y

Where call is call type ● internal (call from other OpenScape user)● external (call from non-OpenScape user)

N

Where my device... Name of the device from the list of the user’s registered and associated devices or:● Preferred Voice Device● Preferred IM Device● Aggregated Voice● Aggregated IM

N

Where my device is con-text 1

1 When the device specified is an associated device, the context used will be as it was set in the Options – Devices – Asso-ciated Devices screen

● Available● Unavailable● Online● Offline● Busy● Do not disturb● Unknown

N

Received on certain dates

Calendar dates in local format Y

Received in a specific date range

An after date and a before date as calendar dates in the local format.

N

Received in a specific time range

A start time and end time in 24-hour format N

Received on certain days of the week

Sunday, Monday, Tuesday, Wednesday, Thursday, Fri-day, Saturday

Y

Table 4-2 Conditions for Incoming Calls


5350rules.fm

Nur für den internen Gebrauch Rules WizardRules for Incoming Calls

4.2.1 Actions for Incoming Calls

A rule for incoming calls must include one or more of either class of the following actions.

● Cumulative Actions

– Notify destinations with specific message

– Where redirect fails, notify destinations with specific message

– Write text string to journal

● Conflicting Actions

– Redirect to my device or person list

– Where redirect fails, redirect to my device or person

– Log or don’t log call to journal

– Assign account code to call

Table 4-3 describes the action parameters.

Parameter Values Multiple Entries?

destinations Notification methods (email, IM, pager, SMS) and target ad-dress, for example By email to Preferred Email Device and by IM to Lynn Nottbohm

Y

specific mes-sage

The message text. Standard information such as the calling par-ty information and time and date of the call are always sent when possible by the notification method.

N

text string Text string typed in by user N

my device or person list

A list of routing destinations to which OpenScape will try to di-rect the call (in the order of the list) that can include:● Preferred Voice Device● Registered or associated devices● Typed SIP URIs or phone numbers● System destinations such as VoiceMail, HotList, etc.● The name of another OpenScape user to forward the call to

(only one forwarding target is allowed and it always termi-nates the list when present)

Y

my device or person

Same as above but only single selection can be made N

log or don’t log Indicates whether call should be logged in journal N

Table 4-3 Action Parameters for Incoming Calls (Sheet 1 of 2)



5350rules.fm

Rules for Outgoing Calls

4.2.2 Exceptions for Incoming Calls

For an incoming call, any of the following exceptions can be included:

● Except if from people

● Except where call is call type

● Except where my device is context

● Except if received on certain dates

● Except if received in a specific date range

● Except if received in a specific time range

● Except if received on certain days of the week

The parameter values are described in Table 4-2 on page 4-4.

4.3 Rules for Outgoing Calls

A user can configured rules for outgoing calls using any of the following conditions:

● To people

● Where call is call type

● Placed on certain dates

● Placed in a specific date range

● Placed in a specific time range

● Placed on certain days of the week


4.3.1 Actions for Outgoing Calls

One of the following actions must be included:



account code user-defined account code N


Table 4-3 Action Parameters for Incoming Calls (Sheet 2 of 2)


5350rules.fm

Nur für den internen Gebrauch Rules WizardRules for Incoming Instant Messages




The action parameters are described in Table 4-3 on page 4-5.

4.3.2 Exceptions for Outgoing Calls

Any of the following exceptions can be included. No exception can be used more than once.

● Except if to people

● Except where call is call type

● Except if placed on certain dates

● Except if placed in a specific date range

● Except if placed in a specific time range

● Except if placed on certain days of the week


4.4 Rules for Incoming Instant Messages



From people Names from contact list, typed in, or a pre-saved user defined list.Typed SIP URIs (including wildcards at the beginning or end)

Y

Where my device... Name of the device from the list of the user’s registered and associated devices or:● Preferred Voice Device● Preferred IM Device● Aggregated Voice● Aggregated IM

N

Table 4-4 Conditions for Incoming Instant Messages(Sheet 1 of 2)



5350rules.fm

Rules for Incoming Instant Messages

4.4.1 Actions for Incoming Instant Messages

A rule for incoming calls must include one or more of either class of the following actions:


– Notify destinations with specific message

– Where redirect fails, notify destinations with specific message



– Redirect to my device or person

– Where redirect fails, redirect to my device or person



Table 4-5 describes the action parameters for incoming instant messages.

Where my device is con-text 1

● available● unavailable● online● offline● busy● DND● unknown

N


Calendar dates in local format Y



N


A start time and end time in 24-hour format (Both entries required)

Received on certain days of the week


Y

1 When the device specified is an associated device, the context used will be as it was set in the Options – Devices – As-sociated Devices screen.


Table 4-4 Conditions for Incoming Instant Messages(Sheet 2 of 2)


5350rules.fm

Nur für den internen Gebrauch Rules WizardRules for Incoming Instant Messages

4.4.2 Exceptions for Incoming Instant Messages

For an incoming instant message, any of the following exceptions can be included:


● Except where my device is context






destinations Notification methods (email, IM, pager, SMS) and target ad-dress, for example By email to Preferred Email Device and by IM to Lynn Nottbohm

Y

specific mes-sage

The message text. Standard information such as the calling par-ty information and time and date of the call are always sent when possible by the notification method.

N

text string Text string typed in by user N

my device or person list

A list of routing destinations to which OpenScape will try to di-rect the call (in the order of the list) that can include:● Preferred IM Device● Registered or associated devices● Typed SIP URIs or phone numbers● System destinations such as VoiceMail, HotList, etc.● The name of another OpenScape user to forward the call to

(only one forwarding target is allowed and it always termi-nates the list when present)

Y

my device or person

Same as above N

log or don’t log Indicates whether call should be logged in journal N

account code user-defined account code N

Table 4-5 Action Parameters for Incoming Instant Messages



5350rules.fm

Rules for Outgoing Instant Messages

4.5 Rules for Outgoing Instant Messages

For outgoing instant messages, any of the following conditions can be included:

● To people

● Sent on certain dates

● Sent in a specific date range

● Sent in a specific time range

● Sent on certain days of the week


4.5.1 Actions for Outgoing Instant Messages

A rule for incoming calls must include one or more of either class of the following actions:




– Log or don’t log message to journal


The parameters for the actions are described in Table 4-5 on page 4-9.

4.5.2 Exceptions for Outgoing Instant Messages

For an outgoing instant message, any of the following exceptions can be included:

● Except if to people

● Except if sent on certain dates

● Except if sent in a specific date range

● Except if sent in a specific time range

● Except if sent on certain days of the week



5350rules.fm

Nur für den internen Gebrauch Rules WizardRules for Incoming Emails

4.6 Rules for Incoming Emails


4.6.1 Actions for Incoming Emails

For a given rule with the Primary Condition of “For an incoming email”, one or more of either class of the following actions must be included. No action can be used more than once is a sin-gle rule.


– notify destinations with specific message

– write text string to journal



From people Names from contact list, typed in, or a pre-saved user defined list.Typed SIP URIs (including wildcards at the beginning or end)

Y

Sent only to me

Where my name is in the To box

Where my name is in the CC box

With specific words in the subject

Text strings, including wildcards (* ) at the beginning or end

Marked as urgent High importance, normal importance, or low importance


Calendar dates in local format N




A start time and end time in 24-hour format (Both entries required)

Received in certain days of the week


Y

Table 4-6 Conditions for Incoming Emails



5350rules.fm

Default Rules

– log or don’t log email to journal

The action parameters for an incoming email are the same as those for an incoming call, de-scribed in Table 4-2 on page 4-5.

4.6.2 Exceptions for an Incoming Email

For a given rule with the primary condition of “For an incoming instant message”, any of the following exceptions can be optionally included. No exception can be used more than once.


● Except if sent only to me

● Except where my name is in the To box

● Except where my name is in the Cc box

● Except with specific words in the subject

● Except if marked as urgent

● Except if received on certain dates




The parameters for exceptions are the same as those for conditions, described in Table 4-6 on page 4-11.

4.7 Default Rules

Default rules are available from the system, based on the status that the user sets. A user who is configured in OMC as an administrator can modify the default rules. Any user can override the default rules by using the Rules Wizard to set up custom rules. Custom user rules are al-ways prioritized above default rules when conflicting actions are evaluated.

If the user sets his status to: In Office, Working Remotely, Be Right Back, In Meeting, the default rules are:

● For an incoming call—Redirect to preferred voice device and where redirect fails, redirect to voice mail and log call to journal

● For an outgoing call—Log call to journal

● For an incoming instant message—Redirect to preferred IM device and don’t log message to journal


5350rules.fm

Nur für den internen Gebrauch Rules WizardDefault Rules

● For an outgoing instant message—Don’t log message to journal

● For an incoming email—Don’t log email to journal

If the user sets his status to On Business Trip, Out of Office, On Vacation, Unavailable, or if it is unknown:

● For an incoming call—Redirect to voice mail and log call to journal

● For an outgoing call—Log call to journal

● For an incoming instant message—Redirect to preferred IM device and don’t log message to journal

● For an outgoing instant message—Don’t log message to journal

● For an incoming email—Don’t log email to journal



5350rules.fm

Default Rules


5350work.fm

Nur für den internen Gebrauch Workgroup Portal

5 Workgroup Portal

The Workgroup Collaboration application, accessible from the Workgroup Portal, facilitates document sharing, instant set-up of voice conferences and the automatic launch of web-based application sharing with tools like WebEx and Live Meeting.

Figure 5-1 shows the Workgroup Portal with a document open in the Document Viewer.

Figure 5-1 Workgroup Portal

Workgroup members can use this portal to manage a voice conference or a web conference, including the following tasks:

● Adding or removing participants

● Viewing details of conference

● Sharing documents

● Converting a voice conference into a web conference


Workgroup Portal Nur für den internen Gebrauch

5350work.fm

Viewing Conference Details

5.1 Viewing Conference Details

While participating in a workgroup conference, whether a voice conference or a web confer-ence, the members of the workgroup can see:

● The time the conference started and the number of callers in the conference. This display remains active for the duration of the media conference and is updated in real time with any changes, for example when a participant drops out.

● The names of the participants who are in the voice conference or web conference and the names of workgroup members or requested conference participants who are not in the voice or web conference.

● The documents that are available for this work group.Note that members of a workgroup are those who have access to the workgroup data. This may or may not match the actual participants in the conference.

5.2 Sharing Documents

Members of a workgroup have access to a common storage area of documents. The storage area, an Exchange folder, holds whatever documents and files that members may wish to access. Any type of document or file may be included in the storage area and then accessed from a portal as long as the document type is already associated with Internet Explorer and the correct Internet Explorer plug-in for this type of document is installed on the user’s PC.

5.3 Creating Workgroups

Users can create workgroups from My Workgroups in the Personal Portal.

A user can also create a workgroup by copying and modifying an existing workgroup. This cop-ies the members and the options, but not the documents.

A user can also set up an ad-hoc conference, selecting members “on the fly”. An ad-hoc con-ference consists of creating a workgroup and invoking a media conference simultaneously. For example, user A wishes to discuss something with users B and C, sees from the contact list that they are both available, selects them and in a single step creates a media conference and one-time workgroup. This ad-hoc session can be converted into a permanent workgroup by ed-iting the workgroup properties prior to the end of the media conference.

To set up a workgroup, users configure:

● Name and description of the workgroup

> OpenScape users must have an email address in Active Directory in order to partic-ipate in a workgroup conference.


5350work.fm

Nur für den internen Gebrauch Workgroup PortalCreating Workgroups

● Type of collaboration: one-time only or recurrent.

● Whether workgroup members are added automatically to a conference as soon as they an-swer the call or are given the option to accept or reject the conference.

● Whether a custom email is sent to the members when a workgroup is created

● The documents to be shared.

These documents can be in any format but are viewable only if the user has the appropriate browser plug-in to view that document type.

● The parties who are members.

Workgroup members can be selected from the contact list, the Outlook Address Book, or by typing in a name, phone number, and email address. For each workgroup member, a flag is set indicating whether or not this member will participate in media conferences whenever a conference is initiated by another workgroup member.

● The group’s backup owner. This person becomes the owner in the case where the owner is deleted as an OpenScape user.

To finish up the creation of the workgroup, the workgroup can be saved or an immediate voice or web conference can be launched.


Workgroup Portal Nur für den internen Gebrauch

5350work.fm

Launching a Workgroup Session

5.4 Launching a Workgroup Session

Once a workgroup is set up, a user can invoke a session with one click from either the Personal Portal or Workgroup Portal. OpenScape automatically calls all workgroup members who have been specified to be in the conference and if they are available, puts them in a voice confer-ence.

Participants in the conference hear a beep when people join or leave the conference.

After the session begins, any participant can add parties to a conference. Any participant that is a member of the workgroup can drop other parties.

In an ad-hoc conference, no special warning messages (besides standard beeps) are played if parties are being dropped by other participants. In the case when the system parameter is set to drop the conference if it contains only non-OpenScape users, there is also no warning mes-sage.

5.4.1 Multimedia Conferencing—Launching a Web Conference

The following options are available:

● Start voice and web conference together. When the first party is connected via voice, the web conference is launched.

● Start a web conference in an ongoing voice conference (unless the conference was launched from Voice Portal, in which case the user is assumed to be on the phone and has a voice-only connection to OpenScape)

● Add participants to both voice and web conferences together

● Send emails to participants with URL to join the conference

An ad-hoc web conference can be launched from My Calls and My Contacts in the same man-ner as conference calls. If the user selects one contact and starts a web conference, a two-par-ty web session can be created but it will be treated as a conference by the system.


5350Vport.fm

Nur für den internen Gebrauch Voice Portal and Self-Service PortalVoice Portal Access for OpenScape Users

6 Voice Portal and Self-Service Portal

This chapter describes the Voice Portal and the Self-Service Portal.

6.1 Voice Portal Access for OpenScape Users

By phone, OpenScape users can set their status, initiate conferences, and access the Ex-change server for both voice and email messages, contact lists, calendars and tasks.

Users who call in to the Voice Portal are authenticated by entering their OpenScape ID and password. The caller is allowed three tries before authentication fails and the call is disconnect-ed. Users can also log on using Dial by Name (last name followed by first name)

This section describes the full capabilities of the Voice Portal.

6.1.1 Listen to Voice and Email Messages

Users can use the Voice Portal to listen to messages in their Inbox as well as in other folders at the same level as their Inbox, such as their Deleted, Sent, and Drafts folders.

The user hears the date and time the message was received and the type of the message (voice or email). Voice messages are in 8khz, 16-bit mono PCM format.

The user can replay the message, forward it, and mark it unread.

For an email message, the body of the message is rendered by text-to-speech. The system ad-vises the user if there is an attachment but mail attachments are not rendered.The following message controls are in effect during and after the message playback of the message:

● Skip to next message

● Go to previous message

● Repeat from beginning

● Delete

● Mark unread

> The Voice Portal accepts voice input as well as DTMF tones. (The functionality that provides voice input will be delivered in a feature pack.)

> Some of the voice portal capabilities described in this section will be delivered in a feature pack.


Voice Portal and Self-Service Portal Nur für den internen Gebrauch

5350Vport.fm

Voice Portal Access for OpenScape Users

● Forward (via email) a message to other users (OpenScape or non-OpenScape) or to con-tacts.

● Reply to message. A user can reply to any message as long as the message sender has a defined email address. The delivery mechanism is via email.

Users address messages using Dial-By-Name or by entering an extension number.

Users can filter the messages by voice or email, by urgency, newness (i.e. unread messages), or simply listen to all messages in the order received.

6.1.2 Create and Delete Messages

An OpenScape user can create a voice message, forward a message with a comment, or reply to a voice or email message. The message is sent immediately (not held until the end of the session.) Messages cannot be marked private, so any message can be forwarded.

Messages are deleted on request (not at the end of a session) and moved to the Deleted Items folder. The next time the user accessing his emails via Outlook closes the Outlook session, (de-pending on his Outlook settings) the message may be permanently deleted. (This depends on his Outlook settings). Once the message is deleted, the user cannot reply to it or forward it.

There is no Saved folder for messages.

6.1.3 Manage Calendar Appointments

OpenScape users can access their calendars from the Voice Portal to do the following:

● Accept, decline, and delete declined appointments

● Play back the next appointment

For example: “Your next appointment is at <time><date> with <person name>”.

● Play all appointments for a specific date and time range. The user must enter the desired date and the desired time range. Time range will be determined by asking for the start time and end time.

● Block a specific date and time range in the calendar. No invitees are specified. Note that the appointment will be blocked even if there is already an appointment in that time range.

● Review upcoming appointments. All appointments with a tentative meeting status within the specified time frame are played, one after the other, and the user can accept or reject each one. When a meeting is rejected, the busy status is changed from tentative to free and the user can still see the meeting in his or her calendar. The user can then delete the rejected appointment and it is moved to the Deleted Items folder.


5350Vport.fm

Nur für den internen Gebrauch Voice Portal and Self-Service PortalVoice Portal Access for OpenScape Users

● If the user is the originator of the appointment or if a contact guest made the appointment, the user can delete the appointment. (Refer to Section 6.2.1 on page 6-4 for a description of guest access.)

● Play meeting notices in the mailbox. Create a new meeting or update an existing one by adding attendees, setting or changing the time and date, and including an audio file.

6.1.4 Review and Manage Contact Information

The user can review and manage contact information from the Voice Portal. The user dials the contact by name and hears all the matches for that name. Once a selection is made, the user hears: “Contact: <first name> <last name> <home phone number> <business phone number> <fax number> <e-mail address>”.

Users can modify and delete contacts from the Voice Portal.

6.1.5 Manage User Profiles

An OpenScape user can change his personal status and select his preferred voice device, change the device context of an associated device, and review his Rules for a specific status.

6.1.6 Manage Tasks

Users can create a new task with a due date and a voice attachment, and can also review and update existing tasks.

6.1.7 Speech Input to the Voice Portal

OpenScape users who call the Voice Portal can make their selections by speaking, for example by saying “List appointments for today” or “I want to hear my urgent messages”. Ample Help for this feature is available for users who need examples of phrases they can use or who are con-fused about where they are in the menu. (This functionality will be delivered in a feature pack.)

The Phone Favorites feature provides user-defined short cuts that allow users to call the Voice Portal and easily access their most-used functions, for example, by saying “Urgent messages” or “Check Calendar”.



5350Vport.fm

Self-Service Portal for Guests

6.2 Self-Service Portal for Guests

The Self-Service Portal allows guests calling into the system to leave a message for an Open-Scape user or to help themselves to information that the user has made available. Each user controls access to his or her own Self-Service Portal.

A guest accesses the user’s Self-Service Portal by first dialing the user’s extension number and then making the appropriate selection from the list of choices.

The guest can use:

● Voice mail functions—leave a message, transfer from voicemail

● Calendar functions—with a user-provided password, the guest can schedule, cancel, or modify appointments with the user and receive email confirmation of an appointment.

● Document access functions—read, or retrieve by email or fax a document stored in Ex-change folders

This feature provides productivity improvement for the user because information he has to share can easily be accessed by the appropriate party.

6.2.1 Guest Access to Self-Service Portal

There are two kinds of guest users for the Self-Service Portal:

● Anonymous guest— a person who is not listed in the user’s Contact folder in Outlook. This type of guest has limited access.

● Contacts—a person who is listed in the user’s Contact folder in Outlook. A contact guest has full access to the Self-Service Portal.

The user must assign a numeric password for the contact guest. It is the responsibility of the user to:

● Create this new field via Outlook and communicate it to the contact.

● Ensure that the combination of contact name and password is unique.

● Enter and manage this person in Contacts via Outlook or Outlook Web Access. Note that this person must be an Outlook contact; whether or not he or she is an OpenScape contact is irrelevant for this feature.

> The OpenScape user specifies these choices in the web greeting that he sets up. If the user has not set up his web greeting, the caller can only leave a message.Sec-tion 6.4.3.1 on page 6-13 has more information on the web greeting.


5350Vport.fm

Nur für den internen Gebrauch Voice Portal and Self-Service PortalSelf-Service Portal for Guests

The numeric password is human readable when entered by the user. If the contact guest changes the password the resulting password is stored in a hashed format that cannot be read by the OpenScape user. The OpenScape user can reset the password by entering a new nu-meric password and communicating this password to the contact guest.

6.2.2 How Contacts are Authenticated

Contact guests who call in to the Self-Service Portal are authenticated as follows:

a) The caller is asked to enter (via DTMF name dialing) their last name and first name until there is a match and then the numeric password.

b) If there is a conflict on the name, the caller is asked for their business phone number.

If there is no unique match found for either case (a) or (b), the caller is directed to leave a mes-sage.

The caller is allowed three attempts to authenticate. If the authentication fails, the caller is di-rected to leave a voice message.

6.2.3 Leave Voice Messages

Contacts and anonymous guests can leave voice messages for one or more OpenScape users:

● By directly calling the Guest Access Number created by the system administrator.

When a guest calls this number, he can record a message. Before recording, the guest is asked to enter the destination of the message, via DTMF name dialing or by entering the extension number.

● If the caller reaches the user’s web greeting and chooses to leave a voice message or if the user’s rules redirect the caller to his web greeting.

There are two message delivery options: normal and urgent. The default delivery option is nor-mal. A caller must explicitly mark a message urgent.

The maximum recording length is five minutes. The message is recorded in 8kHz 16-bit mono pulse code modulation (PCM) format.

The recording controls are Stop-Record, Replay, and Erase-And-Record Again.

The message is delivered when the caller explicitly chooses the option to deliver the message or when the caller records a message and immediately hangs up.

The guest can also enter multiple destinations for the message to be delivered to. When the extension has been identified, the system plays the user’s name or repeats the extension num-ber entered and asks the guest for confirmation.



5350Vport.fm

Self-Service Portal for Guests

Once the caller has finished recording the message, contact guests who are logged on can use other guest features of the system like transferring to another extension.

6.2.4 Schedule Appointments

A contact guest who is logged on can schedule an appointment with the user. The guest can request the following for a particular user:

● Tell me next available appointment today (one hour slot only). Once the system prompts the availability, the guest has the option to accept the appointment or request the next avail-able appointment or exit the system.

● Tell me the first available appointment on a particular day. The guest enters the month and date on the phone keypad. Once the system prompts the availability, the guest has the op-tion to accept the appointment, request the next available appointment, or exit the system.

● The guest can enter a date and time and the system will respond with the availability.

When a guest accepts an appointment, an email notification is sent to the user and the calendar appointment appears as a tentative appointment on the user’s Outlook calendar. When the user accepts or rejects the appointment, the guest will be sent an e-mail confirmation.

Once the guest accepts the appointment, he cannot modify it but can remove it from the calen-dar and start the request process again. A guest can only remove an appointment that he or she made.

A guest can make one appointment per day (of one hour duration) per user but cannot make recurring appointments.

The subject field of the appointment is pre-defined by the system. For example: “Appointment with <first name> <last name>”. The caller can also record a message up to three minutes in length and attach this message to the appointment.

> Note that this feature is available to contact guests, but not to anonymous guests.


5350Vport.fm

Nur für den internen Gebrauch Voice Portal and Self-Service PortalSelf-Service Portal for Guests

6.2.5 Access Documents

A user can store documents of any kind in predefined Exchange folders to make them available to guests who access the Self-Service Portal.

The user can make a specific association between a resource and an authenticated contact guest by specifying the URL of the greeting set up for that contact guest in the “Web page ad-dress” field of the Contact properties for that guest.

The documents can be accessed as follows:

● A text document or wav file can be read to contacts or anonymous guests.

● A document can be emailed as attachment to a contact guest if the email address is avail-able.

● When applicable, a document can be faxed back to a contact guest.

– The fax server must be accessible (configured in the Media Server)

– The contact must have a fax number listed as a Contact Property in Outlook or must enter one via the phone keypad.

Users can also make documents available to be faxed to anonymous guests but the guest must enter the fax number.

> The documents reside in folders for the user in the Exchange 2000/2003 Server. The management of these folders is the responsibility of the user.



5350Vport.fm

The Interaction Center

6.3 The Interaction Center

The Interaction Center provides a set of generic greetings for OpenScape users and their call-ers. These greetings are interactive dialogs such as Welcome to my personal web page. Press 1 to leave a voice message.... The greetings are HTML pages created with the Word Web fea-ture (typed into Word and saved as HTML).

The Interaction Center also provides the text-to-speech and routing capabilities that allow call-ers to hear and interact with the greetings.

6.3.1 HiPath Media Server Administration Tool

The HiPath Media Server administration tool allows the system administrator to do the follow-ing:

● Create the interactive dialogs that provide appropriate greetings to callers.

Note that the Media Server comes with a default set of interactive dialogs. The system ad-ministrator can modify these and / or create new ones.

● Set up the routing table in Media Server to route incoming calls.

The default greetings (and any new greetings created by the user) are stored in predefined Outlook folders belonging to each OpenScape user.

Each user can customize his or her own greetings using the Word Web feature.

6.3.2 Scenario 1—Media Server Provides Greetings

In this scenario (Figure 6-1 on page 6-9):

1. An outside caller dials the number for OpenScape user Maria.

2. Incoming calls for OpenScape users that are not answered or routed elsewhere by their Rules are routed to their web greetings, stored in their Forward Access folders.

3. Maria is on vacation and the default rules route her incoming calls to her web greeting.

4. Maria’s greeting is rendered (text-to-speech) to the caller.


5350Vport.fm

Nur für den internen Gebrauch Voice Portal and Self-Service PortalThe Interaction Center

Fig

ure

6-1

Med

ia S

erve

r P

rovi

des

Gre

etin

gs to

Out

side

Cal

ler

(4)

(1)

(2)

....

.....

....C

alle

d pa

rty

num

ber

rout

es to

For

war

d A

c-ce

ss a

pplic

atio

n...

....

.....

For

war

d A

cces

s A

pplic

atio

n po

ints

to

Web

Gre

etin

g H

TM

L pa

ge

Med

ia S

erve

r

Cal

ler

hea

rs “

Wel

com

e to

my

pers

onal

w

eb p

age.

..”

(3)

Out

side

cal

ler



5350Vport.fm

The Interaction Center

6.3.3 Scenario 2—User Customizes Greeting

In this scenario (Figure 6-2 on page 6-10), Maria is going to be out of the office on vacation but wants to let callers know whom they can contact in her absence.

1. She uses Word Web to customize her personal greeting.

She does this by creating a Word document with some simple text that will be rendered to her callers: Welcome to my personal web page... Then she creates hyperlinks in the doc-ument that offer choices to her callers: Leave message for me, transfer to Mr. Schmidt, Log in, Disconnect.

2. She saves the document as HTML and drags and drops it in the appropriate Outlook folder, making sure that it is correctly named.

3. When her web greeting is read to the callers, the Media Server inserts the instructions “Press 1 for... Press 2 for...”

Figure 6-2 User Customizes Greeting

OpenScape & Exchange

(1)

(3) “Welcome to Maria’s web page.

(2)

Welcome to Maria’s web page

Media Server


5350Vport.fm

Nur für den internen Gebrauch Voice Portal and Self-Service PortalThe Interaction Center

6.3.4 Scenario 3—Contact Guest Accesses Self-Service Portal

Before she leaves for her ski vacation in Switzerland, Maria has been trying to reach Sandra, a special customer in Zurich. She would like to call on Sandra while she is Switzerland but is having trouble setting up the meeting. So she gives Sandra access to the Self-Service Portal:

1. Maria creates a simple Word Web greeting that is customized for Sandra and she stores it in a dedicated folder.

Hello Sandra, I am looking forward to meeting with you between February 1 and February 8. Please choose a time that is convenient for you.

Maria configures the Contact information in Outlook for Sandra with the location of the spe-cial greeting and a password. She sends Sandra an email communicating the password and the request to schedule a meeting.

2. Sandra calls and hears Maria’s greeting to all callers. She presses 3 to log in and hears the special greeting. Once she has accessed the Self-Service Portal, she follows the voice prompts to schedule an appointment.

3. Maria (now on vacation in Switzerland), calls in to the Voice Portal and hears the details of the appointment that Sandra has scheduled.

Figure 6-3 Contact Guest Accesses Self-Service Portal

OpenScape & Exchange

(2)

(1)

Media Server



5350Vport.fm

OpenScape Interaction with Outlook and Exchange Server

6.4 OpenScape Interaction with Outlook and Exchange Server

Besides the functions of the Voice Portal that give OpenScape users access to messages re-ceived in their Inbox and Calendar appointments, there are other important functions provided by Outlook and the Exchange Server.

6.4.1 Configuration of Outlook Contacts

For each Contact Guest who will be able to access the Self-Service Portal, the user must con-figure a password, a business phone number, and an email address. If the user wants to pro-vide custom content (such as a personalized greeting for that guest), he can configure the URL where the content is stored. A fax number can also be configured to use when faxing docu-ments to contacts.

6.4.2 Pre-defined Outlook Folders

Folders specifically for use with OpenScape are set up in each user’s Folder List. A user can create a sub-folder such as the one called Sandra in Figure 6-4 to provide content destined for a particular guest.

Figure 6-4 Outlook Folders for OpenScape

> The names of folders and default files are fixed and may not be changed.The user who wants to customize a default greeting can change the content but not the name of the file.


5350Vport.fm

Nur für den internen Gebrauch Voice Portal and Self-Service PortalOpenScape Interaction with Outlook and Exchange Server

6.4.3 Interaction Center Folder and Sub-folders

The Interaction Center folder contains the resources for OpenScape that are described in this section.

6.4.3.1 ForwardAccess Folder

Language-dependent subfolders under this folder contain the menu of selections that users provide to callers (“Press 1 to leave a message”, etc.). The source is an HTML document (cre-ated with Word Web) called WebGreeting. The Word Web document to use must be located in the ToUse sub-folder. Users can modify the content but should not change the name of this greeting.

6.4.3.2 PersonalizedGreetings Folder

This folder and its subfolders contains the initial wav file that will be played to all callers. A user can change the greeting by recording a new wav file on a PC or recording a voice message for himself via the phone and dropping the wav file into the Outlook folder. The greeting to be used must be in the ToUse folder.

6.4.3.3 SelfService Folder

The folder contains documents that the user wishes to make available to callers. Guests ac-cessing this folder may have text or voice documents read to them and may have any document emailed or faxed, depending on the Outlook Contact properties for that guest.

The user may configure subfolders in the SelfService folder. File and folder names are defined by the user and must be compatible with URL conventions.

> The folders described in this section contain subfolders with English (en-US) and German (de-DE) files. Users should be sure to access the appropriate language files.

> The wav greeting must be in 8Khz 16-bit mono PCM format. If this greeting is not in the folder (or if more than one greeting is in the folder), nothing will be played.

> Callers can browse subfolders. A user should keep this in mind when setting up the structure for folders and not include restricted-access subfolders under a folder that everyone can access.



5350Vport.fm


6.4.3.4 GuestContent Folder

This folder contains the HTML document for greeting a contact guest, along with any associat-ed wav files. The folder is accessed when a call from a contact, for example Bill Gates, is routed to the SelfService Portal, and Bill Gates logs in with the password provided to him earlier.

It is recommended that users manage their guest greetings by creating subfolders, for example, a folder called BillGates. When the user configures Bill Gates as a contact in Outlook, he adds the location of his folder to the Contact Property sheet in Outlook.

6.4.4 Outlook Journal

Using the Rules Wizard, users can specify that certain activities should be logged in the Out-look Journal. Depending on how a user has set up his or her rules, OpenScape logs the follow-ing activities when “log in journal” is specified:

● For an incoming voice call:

– Subject: Call from <caller>

– Body: Call at <time and date>, connected to <device name and address>, elapsed time <time>

● For an outgoing voice call:

– Subject: Call to <called>

– Body: Call at <time and date>, called from <device name and address>, elapsed time <time>

● For an incoming instant message

– Subject: instant message from <caller>

– Body: instant message at <time and date>, send to <device name and address>

● For an outgoing instant message

– Subject: instant message to <called>

– Body: instant message at <time/date>

● For an incoming email

– Subject: e-mail from <caller>

– Body: email received at <time/date>

> Note that the documents to be supplied to the guest should be in the SelfService folder.


5350Vport.fm

Nur für den internen Gebrauch Voice Portal and Self-Service PortalOpenScape Interaction with Outlook and Exchange Server

When the user specifies “write text string to journal”, the text provided is appended to the ap-propriate Journal item.

Journal entries created by OpenScape can be viewed only in Outlook. The entry in the Journal appears as a push-pinned yellow post-it icon that contains the information described above.



5350Vport.fm



5350sec.fm

Nur für den internen Gebrauch SecurityPassword Access

7 Security

OpenScape fulfills stringent security requirements. It is the mission of Siemens to provide se-curity that:

● Integrates Siemens products into customers’ solutions with outstanding security features

● Provides uniform and interoperable security solutions

● Provides scalable security features

● Implements user-friendly access to security features

● Implements security solutions based on standards.

7.1 Password Access

To protect access to the OpenScape system, logon is restricted with user IDs and passwords. The following types of password access exist:

● The user’s Windows domain user-name and password are used for portals that support al-phanumeric input, such as the user’s Personal Portal. This is the same user-name / pass-word that is used to log on to the network domain in Windows.

● A fully numeric OpenScape user ID and password are supported for easy access from de-vices that do not easily support alphabetic input such as a telephone keypad. A user ac-cesses the Voice Portal by dialing his name or dialing his user ID and password.

● The Siemens SIP Phone has the following three passwords configured on it:

a) Windows domain password to register with the SIP registrar

b) Administrator password to allow administrators to configure administrative data on the phone

c) User password to allow the phone’s user the following types of access to the phone:

– local configuration

– user Web pages

– CTI interface.


Security Nur für den internen Gebrauch

5350sec.fm

Authentication

7.2 Authentication

OpenScape uses the Kerberos Version 5 IETF standard protocol to provide a highly secure method of user authentication. OpenScape components authenticate with, and get tickets from, a Key Distribution Center (KDC). The KDC authenticates users via Microsoft Active Directory and provides a Ticket Granting Ticket (TGT) if authentication is successful. OpenScape com-ponents get service tickets from the KDC that are subsequently used to securely access ser-vices in the system.

OpenScape uses the Transport Layer Security (TLS) Version 1.0 IETF standard protocol to per-form machine authentication using certificates and encryption. The OpenScape components running on the Office Live Communications Server may use the same certificate installed for that server. The certificate to be used for a particular server is configurable. The customer can configure it so that OpenScape uses the same certificate as that used for the LCS.

7.3 Encryption

OpenScape uses two standard protocols to perform encryption of network signaling messages:

● Transport Layer Security (TLS) IETF standard protocol – Note again that TLS requires cer-tificates either purchased from a certificate authority vendor or created by the customer. TLS is used for the following interfaces:

– Between OpenScape components

– Interfaces to and from the Siemens SIP Phone

– For Personal Portal access

● Internet Protocol Security (IPSec) IETF standard protocol. IPSec is used for the following interfaces:

– Between the Media Server and the LCS

– Between the Media Server and the License Server

– Between MCU and the LCS

– Between MCU and the License Server

– On the SIP interface between the OpenScape Server and the LCS

– Between the MC and MP of the MCU.

> Note that the TLS option of Windows Messenger must be turned on.


5350sec.fm

Nur für den internen Gebrauch SecurityAuthorization

7.4 Authorization

After performing user authentication to prevent user impersonation, OpenScape determines whether the user is authorized to access the system. The following three types of authorization checks are performed:

● Administrator authorization to determine whether a user is an OpenScape administrator. Administrators can do configuration and use all OpenScape features.

● User authorization to determine whether the user is an OpenScape user. A user cannot do OpenScape system configuration.

● Service authorization to determine whether a service is authorized to communicate with an OpenScape service.

Authorization is implemented using Windows user groups.

7.5 Siemens SIP Phone Security

The Siemens optiPoint 400 SIP phone supports outstanding security features that use Ker-beros for user authentication and TLS for encryption. The user’s Windows domain user-name and password are stored on the phone to provide secure access to the LCS using Kerberos tickets. TLS requires a certificate purchased from a certificate authority vendor or created by the customer. A wildcard certificate from a certificate authority vendor is supported to reduce the certificate cost per phone.

7.6 Certificate Strategy

OpenScape certificate strategy is based on either third-party certificates issued by a globally known trusted certificate authority (such as Verisign) of the customer’s choice, or the custom-er’s own PKI using customer-specific certificates. The LCS platform also requires the installa-tion of a certificate of the customer’s choice as a prerequisite for TLS. The certificate installed as a prerequisite for the LCS and TLS may be used by OpenScape on that machine.

It is the customer’s responsibility to choose a certificate with a high degree of security. For ex-ample, test certificates, expired certificates, and class-0 (email/demo) certificates should not be chosen.

Microsoft Internet Explorer 6 comes with approximately 60 root certificate authorities (CAs). The certificate chosen by the customer should either be one issued by one of those 60 CAs, or a customer-specific certificate that has an associated root CA stored on the machines with Win-dows Messenger.



5350sec.fm

Certificate Strategy

7.6.1 Server Certificates and Root CAs

The LCS, OpenScape server, and the Media Server should have either a third-party server cer-tificate of the customer’s choice installed and configured by the customer, or a customer-spe-cific certificate installed and configured by the customer. The MCU does not require a certificate because it is not the server in any TLS interface.

Each of the OpenScape servers will have the common 60 root CAs as part of Internet Explorer that comes with Windows. If customer-specific certificates are used, customer-specific root CAs should be installed on the servers.

OpenScape Management Console can run on multiple servers in the system to perform remote management. However a certificate is not necessary for the servers from which remote man-agement is performed.

Mutual TLS (MTLS) is used to communicate from one LCS to another. If this configuration is deployed, Microsoft documentation should be consulted for instructions on certificate installa-tion and configuration.

7.6.2 Workstation Certificates and Root CAs

OpenScape users’ PCs do not require the installation of a certificate because they have the common 60 root CAs as part of Internet Explorer. If the customer is using customer-specific certificates on the servers, the workstation machines should be installed and configured with customer-specific root CA’s by the customer.

If the customer deploys a workstation that is not running a Windows operating system, it is the responsibility of the customer to install a root CA that matches the certificates that were chosen for the servers and the phones.

7.6.3 SIP Phone Certificates and Root CAs

The SIP Phones support the installation of either a server certificate (and key) issued by one of the common 60 CAs, or a customer-specific certificate (and key). The phones also support running with the embedded certificate that comes on the phone.

7.6.4 Non-Siemens Gateway Certificates and Root CAs

Non-Siemens gateway may or may not require the installation of a certificate. This depends on the following factors:

● The third-party gateways supported by OpenScape

● The interfaces that are supported on those gateways

Customers should follow the instructions in the gateway’s documentation for certificate support (if existing).


5350sec.fm

Nur für den internen Gebrauch SecurityRemote Access to Portals via the Internet

7.7 Remote Access to Portals via the Internet

Users can remotely access OpenScape Personal Portals and Workgroup Portals via the inter-net using Internet Explorer (IE). Users cannot remotely access those portals from Outlook or Windows Messenger.

7.7.1 Scenarios for Remote Access

The following scenarios are examples of remote features that are supported:

An OpenScape user is sitting in an Internet café or is visiting another company. The user wants to change her preferred device to her cell phone number and to perform other preference se-lections via her OpenScape portal. She opens an IE browser and inputs the URL to obtain ac-cess to her company. After authenticating with RSA SecurID and then with the portal (and op-tionally Outlook Web Access —OWA), she gains access and makes the desired changes.

For example:

● She can select any callable device as a preferred device

● She can send email from the Contact list in the Personal Portal using the email client (Out-look or Outlook Express) configured in the local IE browser. Note that the sender ID of the email (the “from” field) may or may not identify the user, depending on IE configuration.

● She can view and manage her Inbox and Calendar (obtained via OWA)

● She can retrieve a document from Exchange via the Workgroup Portal. Hypertext Transfer Protocol over Secure Socket Layer (HTTPS) should be used for this.

● She can initiate a WebEx collaboration session from the Workgroup Portal

The user logged on remotely cannot:

● Send an instant message

● Initiate a call from the local Windows Messenger via the portal

● Use the Windows Messenger portal

● Use the Outlook Client portal



5350sec.fm

Remote Access to Portals via the Internet


5350conndw.fm

Nur für den internen Gebrauch ConnectivityBasic Definitions

8 Connectivity

This chapter provides information on OpenScape connectivity.

8.1 Basic Definitions

Active Directory, which provides authentication and routing information for the LCS Server, is typically viewed from a logical perspective without regard for the physical location of a compa-ny’s offices, server or people. The primary logical objects related to AD are: Forests, Trees, and Domains.

8.1.1 Forests

A forest is a collection of trees and is the highest level in Active Directory. There can be multiple forests in your Active Directory (for example, to accommodate subsidiaries, outside business entities or merger partners).

Graphically, a forest is sometimes represented by a large box that contains everything else. For-ests are most common in large enterprises.

8.1.2 Trees

Trees are a collection of domains, typically arranged in a hierarchical view. One defining char-acteristic is that trees share a common root domain name, such as siemens.com.

A Windows 2003 Active Directory domain tree is a set of Windows 2003 domains connected via a two-way transitive trust, sharing a common schema (database), configuration (topology) and Global Catalog (quick search engine).

Larger organizations such as enterprises would actually speak of trees.

A tree appears as lines connecting multiple domains but does not implicitly have a shape itself.

8.1.3 Domains

Microsoft defines domains that contain:

● Security requirements

● Replication processes

● Administration

Domains are the core of Active Directory and take on the name of the registered Internet do-main name.The top-level domain is called the parent domain and the lower-level domains (typ-ically placed beneath parent domain in a figure) are considered a child domain.


Connectivity Nur für den internen Gebrauch

5350conndw.fm

Network Infrastructure Requirements

A domain is an administrator-defined logical grouping of computer systems, servers and other hardware which share a common directory database. The first domain installed in a tree is con-sidered the root domain of that tree.

8.2 Network Infrastructure Requirements

8.2.1 OpenScape Application Server

8.2.2 OpenScape Application Clients

The English and German versions are supported.

> Please verify the latest versions, service packs and hotfixes at http://kmoss.icn.sie-mens.com.

Component Type/Edition/Company

Base Server

OpenScape Base Server Siemens

OpenScape Management Console Siemens

Microsoft Windows Office Live Commu-nications Server 2003

Standard or Enterprise Edition

.Net Framework Microsoft

Java 2 Runtime Environment Sun

MS SQL Server 2000* Standard Edition or Enterprise Edition

MSMQ – MS Message Queue Service Microsoft

Table 8-1 Requirements for OpenScape Application Server

> *Please note that the MS SQL Server 2000 can be located anywhere within the do-main where OpenScape resides.

Component Tested Edition

Windows XP or Windows XP SP1 Professional edition

Windows 2000 and latest service pack Professional edition

Table 8-2 Requirements for OpenScape Client Application


5350conndw.fm

Nur für den internen Gebrauch ConnectivityNetwork Infrastructure Requirements

8.2.3 OpenScape Administration Clients

* - The OMC client is supported on Windows 2000 and XP clients.

8.2.4 MCU

8.2.5 Media Server

Refer to the Media Server for OpenScape V1.0 Installation Guide for the correct versions.


OpenScape Management Console (OMC)* Siemens


MS Windows 2000 or MS XP Professional Microsoft


Table 8-3 Requirements for OpenScape Administration Clients


OpenScape MCU

Microsoft Windows Server 2003 Standard Edition orEnterprise Edition

MS .Net Framework Microsoft


Table 8-4 Requirements for MCU


Media Server application

Windows 2000 Server(Windows 2003 in upcoming feature pack)

Standard Edition

Internet Explorer Microsoft

HiPath CAP Fault Management Siemens

MS .Net Framework Microsoft

Java 2 Runtime Environment Sun

Speechify (TTS engine) ScanSoft

Table 8-5 Requirements for Media Server (Sheet 1 of 2)



5350conndw.fm

Network Infrastructure Requirements

8.2.6 End Points

OSR (engine for automatic speech rec-ognition)

ScanSoft

IE Web Controls Microsoft

MDAC Microsoft

MSDE 2000 + SP2 Microsoft



optiPoint 400 SIP phone

Windows Messenger Microsoft

Windows 2000 or Windows XP Profes-sional

Table 8-6 Requirements for End Points

Table 8-5 Requirements for Media Server (Sheet 2 of 2)


5350conndw.fm

Nur für den internen Gebrauch ConnectivityDeployment Scenarios

8.3 Deployment Scenarios

The network topology at a customer site is the responsibility of the customer’s IT organization. This section outlines the supported scenarios for the system and identifies some key factors for the main components.

This section describes four scenarios supported by OpenScape:

● Single domain - all components and users are in a single child domain

● Multiple domains - components and users are distributed across multiple domains

● Multiple OpenScape Systems - separate domains

● Multiple OpenScape Systems - same domain

● Multiple LCS servers behind front end server

There are two key principles that need to be satisfied by any topology for OpenScape to be functional. These are:

● Access to contact information of system users

● Registration of users with an appropriate LCS Server.

The root domain contains a master Active Directory. A domain controller of each domain in the domain hierarchy contains a partial copy of Active Directory. This copy contains the configura-tion and schema partitions containing information about the entire forest. The copy also con-tains a domain partition with information on all objects and attributes within that domain. A do-main controller in each domain must also contain the Global Catalog which contains a full replica of its own domain objects as well as a partial replica of all other domain objects in the forest. Thus, some contact information (i.e. username and address) about all users in the forest is available to the system.

Microsoft allows for multiple LCS Servers to be installed in multiple domains in the forest; how-ever, OpenScape restricts this topology by requiring a single LCS Server per OpenScape sys-tem. So for users to be considered as members of a particular OpenScape system, they need to be registered with an appropriate LCS Server.

In the sections that follow, the four scenarios (topologies) are discussed. For all these, the Ex-change Server is denoted as being in its own separate domain because its actual physical lo-cation need not be co-located with the OpenScape system.

All the figures show an organization siteA.com and its forest forest1.siteA.com. The root do-main of the forest root.forest1.siteA.com contains the master Active Directory, domain con-trollers and a Global Catalog.

The figures show the locations of the OpenScape Systems (OS1, OS2) and the LCS Home Servers (LCS HS1, LCS HS2). Other LCS Servers may exist in the same domain whose users are not OpenScape (OS) users.



5350conndw.fm

Deployment Scenarios

8.3.1 Minimum Configuration

Figure 8-1 shows the minimum configuration of an OpenScape System.

Figure 8-1 Minimum Configuration

The minimum configuration has three servers: the OpenScape Server, MCU Server and Media Server.

The MCU Server contains the MC and up to four MPs. The minimum configuration is one server containing one MC and one MP. An additional 3 servers each containing one MP is possible.

The 3rd Party SIP Gateway is connected to the OpenScape System.

> Exchange 2000/2003 can be anywhere in the domain where OpenScape resides.

Windows Messenger 5.0 / IE 5.1 / Outlook 2000

OS

OpenSca

pe

OpenScape System

Windows 2000 or XP Pro

OMC Administration

Client OpenScape Management

Console

OpenScape Base SIP Gateway

Required Infrastructure

OpenScape Application

3rd Party Software TTS,ASR,Dialogic

JAVA Runtime

Windows Server 2003

LCS MS-SQL Server 2000

Windows 2000 Server + SP3

MSDE, MDAC

Windows Server 2003 or Windows

2000 Server

Active Directory

Windows 2000 Server

Exchange 2000

Main Server Media Server(ComResponse)

Domain Controller

Exchange Server

OpenScape Base

Windows Server 2003

MCU Server

MCU MP Application

MCU MC Application

OpenScape Base

OpenScape Management Console

MS IIS

MS IIS

OpenScape Base

ComResponse Application

OpenScape Client

JAVA Runtime


5350conndw.fm


8.3.2 Expanded Configuration

Figure 8-2 shows an expanded configuration.

Figure 8-2 Expanded Configuration

OpenScape Application

3rd Party Software TTS,ASR,Dialogic

JAVA Runtime

Required Infrastructure

Windows Server 2003

Windows 2000 Server + SP3

MSDE, MDAC

Active Directory

Windows 2000 Server

Exchange 2000

OS

Open

Sca

pe

Main Server Media Server(ComResponse)

OpenScape SystemDomain

Controller Exchange

Server

OpenScape Base

Windows Server 2003

MCU Server

MCU MP Application

MCU MC Application

OpenScape Base


OMC Administration

Client

SIP Gateway

MS IIS MS IIS

Windows Server 2003

LCS MS-SQL Server 2000

LCS Server

OpenScape Base

MS SQL Server

OpenScape Base

Infra- structure

OS

Open

Sca

pe

OpenScape Base

ComResponse Application



OpenScape Base

OpenScape UsersOpenScape User Clients


Windows Messenger 5.0 / IE 5.1 / Outlook 2000

OpenScape Client SIP Phones

JAVA Runtime


2000 Server


2000 Server



5350conndw.fm


8.3.3 Deployment Scenario Prerequisites

All deployment scenarios must be configured with the following prerequisites:

● LCS/OpenScape may only be installed in child domains, Microsoft specifically recom-mends against installing LCS Server in a root or grandchild domain.

● All OpenScape systems/users must reside in one forest.

● OpenScape requires association with a a single LCS Server (1 to 1 relationship). This means that all users that are a part of a single OpenScape system must be registered to only one LCS Server regardless of how many LCS Servers are available. An LCS server can only support the registration of OpenScape users from a single OpenScape system. If a user has 2 OpenScape systems in their network, they will need at least 2 LCS Servers.

● All users registered to a single OpenScape system must be members of domains within a single forest.

● The OpenScape components can be located across several servers.

● Users registered to a single OpenScape may be in multiple domains as long as they on are on the same Active Directory and share the same Exchange and can register with the LCS server.

● LCS has to be deployed in the same domain where OpenScape is installed.

● Firewall Support—Connectivity with firewalls between network components is not support-ed. However, the remote access feature RSA-SecurID is supported. Refer to Chapter 7, “Security” for more details.

● Active Directory—All users must be members of a Microsoft Windows 2000 or Windows Server 2003 Active Directory forest (Windows NT4 domain configurations are not support-ed).

● Exchange 2000/2003 – All users must use Microsoft Exchange 2000 or Exchange 2003 as their primary mail and calendaring server.

● Client Operating System – All users must have Microsoft Windows XP or Windows 2000 installed as their client operating system.

However, there are limitations with Windows 2000. Windows Messenger has reduced fea-tures: no echo cancellation, no white boarding, application sharing, or video. In addition, versions of Windows earlier than Windows XP do not support Universal Plug and Play (UP-nP)-aware Network Address Translation (NAT) or firewall transversal.

● Outlook– All users must use Microsoft Outlook 2000, Outlook 2003, or Outlook XP as their primary mail client.

● IE 5.0 or later – All users must have Microsoft Internet Explorer 5.0 or later installed.


5350conndw.fm


● Windows Messenger 5.5 – All users must have Microsoft Windows Messenger 5.5 or later installed.

● Separate SQL Server 2000 instance - OpenScape will use the customer’s existing MS SQL Server if the prerequisites for version and storage space are met. OpenScape requires one dedicated instance of SQL running on the MS SQL Server.

> This instance cannot be shared with other applications. OpenScape installation will prompt the user for this named instance of SQL. If it does not exist, then create a dedicated instance before continuing the OpenScape installation. The installation of MS SQL Server remains the responsibility of the customer.



5350conndw.fm


8.3.4 Single Domain

The simplest scenario (Figure 8-3) has the entire OpenScape System and associated users in one domain..

Figure 8-3 Single Domain

Here four users are shown belonging to the child domain domain1. There is one OpenScape system (OS1) with one LCS Server (LCS HS1) installed on the OpenScape Home Server. In-side OS1 is the OS Home Server (which contains MS SQL and LCS HS1), MCU Server and Media Server.

Users user1, user2, user3 and user4 are:

● Configured in Active Directory as belonging to domain1.root.forest1.siteA.com via do-main administration.

siteA.com

root.forest1.siteA.com

DC GC

domain1.root.forest1.siteA.com

DC GC

OpenScape System OS1

user1, user2, user3, user4 with SIP phone

DC - Domain Controller

GC - Global Catalog

domain2.root.forest1.siteA.co

DC GC Exchange 2000/2003

forest1.siteA.com


5350conndw.fm


● Configured with LCS HS1 as their home server by LCS administration.

● Configured as OS1 users by OpenScape administration.

> It is also possible in this scenario to have several parallel and independent Open-Scape installations each with one LCS server.



5350conndw.fm


8.3.5 Multiple Domains

Here (Figure 8-4) users exist across domains although still associated with a particular Open-Scape system.

Figure 8-4 Multiple Domain

Here four users are shown belonging to the child domain domain1, with an additional three us-ers belonging to domain3. There is one OpenScape system (OS1) with one LCS Server (LCS HS1) installed on the OpenScape Home Server in domain1.


DC GC

domain1.root.forest1.siteA.co

OpenScape System


DC - Domain ControllerGC - Global Catalog



forest1.siteA.com

DC



DC GC

siteA.com

user5, user6, user7

2-way trust

VPNRemote ac-cess for user5


5350conndw.fm


There is an implicit trust between the peer domains domain1 and domain3. Microsoft recom-mends the explicit creation of a 2-way trust between the peer domains for performance rea-sons. This may be done via domain administration.

● Users user1 through user4 are configured in Active Directory as belonging to domain1.root.forest1.siteA.com via domain administration.

● Users user5, user6 and user7 are configured in Active Directory as belonging to domain3.root.forest1.siteA.com via domain administration.

● Users user1 through user7are:

– configured with LCS HS1 as their home server by LCS administration.

– configured as OS1 users by OpenScape administration.

8.3.6 Multiple OpenScape Systems - Separate Domains

Here (Figure 8-5) multiple OpenScape systems co-exist in one site. In this scenario, as long as the OpenScape and LCS requirements are met, many OpenScape systems may exist within one forest. OpenScape systems in separate forests would follow the Single or Multiple Domain scenarios.

> For each OpenScape system, the contact list can only contain buddies within the same OpenScape system.

> Users may access the system from a remote location via VPN. In this situation, the user is effectively logging into the local domain. This type of access is possible in any of the supported scenarios



5350conndw.fm


Figure 8-5 Multiple OpenScape Systems in Separate Domains


DC GC

siteA.com

root.forest1.siteA.co

DC GC


GC - Global Catalogforest1.siteA.com




DC GC


Exchange 2000/2003

DC


user5, user6, user7



user8, user9, user10, user11

DC GC

2-way trust

2-way trust


5350conndw.fm


Here four users are shown belonging to child domain domain1, three users to domain3 and an additional four users to domain4. There are two OpenScape systems (OS1 and OS2) each with one LCS Server (LCS HS1, LCS HS2) installed on their OpenScape Home Server. The two OpenScape systems are in two separate domains.

If the OpenScape systems are installed in a multiple server configuration, it is possible to locate the MS SQL Server on a separate machine. However, each OpenScape system must refer to one and only one instance of the database server. There may be multiple instances of SQL Server on the same machine.

There is an implicit trust between the peer domains domain1 and domain3 and between peer domains domain3 and domain4. Microsoft recommends the explicit creation of a 2-way trust between the peer domains for performance reasons. This may be done via domain administra-tion.

● Users user1 through user4 are configured in Active Directory as belonging to domain1.root.forest1.siteA.com via domain administration.

● Users user5, user6 and user7 are configured in AD as belonging to domain3.root.forest1.siteA.com via domain administration.

● Users user8 through user11 are configured in AD as belonging to domain4.root.forest1.siteA.com via domain administration.

● Users user1 through user4 are configured with LCS HS1 as their home server by LCS ad-ministration.

● Users user8 through user11 are configured with LCS HS2 as their home server by LCS administration.

● Users user5, user 6 and user7 can be assigned to either LCS HS1 or LCS HS2 as their home server by LCS administration but not to both. For example, user5 to LCS HS1 and user6 and user7 to LCS HS2.

● Users user1 through user5 are configured as OS1 users and users user6 through user11 are configured as OS2 users by OpenScape administration.

8.3.7 Multiple OpenScape Systems - Same Domain

Here (Figure 8-6) multiple OpenScape systems co-exist in one site and in one domain. Simi-larly, in this scenario, as long as the OpenScape and LCS requirements are met, there may be multiple OpenScape systems within one domain.



5350conndw.fm


Figure 8-6 Multiple OpenScape Systems - One Domain


DC GC



user1, user2, user3,user4


GC - Global Catalog



forest1.siteA.com

DC

domain3.root.forest1.siteA.com domain2.root.forest1.siteA.com

DC GC

siteA.com

user5, user6, user7

user8, user9, user10,user11


2-way trust


5350conndw.fm


Here eight users are shown belonging to child domain domain1 and three users to domain3. There are two OpenScape systems (OS1 and OS2) each with one LCS Server (LCS HS1, LCS HS2) installed on their OpenScape Home Server. The two OpenScape systems are in the same domain.

If the OpenScape systems are installed in a multiple server configuration, it is possible to locate the MS SQL Server on a separate machine. However, each OpenScape system must refer to one and only one instance of the database server. There may be multiple instances of SQL Server on the same machine.

There is an implicit trust between the peer domains domain1 and domain3. Microsoft recom-mends the explicit creation of a 2-way trust between the peer domains for performance rea-sons. This may be done via domain administration.

● Users user1 through user4 and user8 through user11 are configured in Active Directory as belonging to domain1.root.forest1.siteA.com via domain administration.

● Users user5, user6 and user7 are configured in AD as belonging to domain3.root.forest1.siteA.com via domain administration.

● Users user1 through user4 are configured with LCS HS1 as their home server by LCS ad-ministration.

● Users user8 through user11 are configured with LCS HS2 as their home server by LCS administration.

● Users user5, user 6 and user7 can be assigned to either LCS HS1 or LCS HS2 as their home server by LCS administration but not to both. For example, user5 to LCS HS1 and user6 and user7 to LCS HS2.

● Users user1 through user5 are configured as OS1 users and users user6 through user11 are configured as OS2 users by OpenScape administration.



5350conndw.fm


8.3.8 Multiple LCS Servers behind Front-End LCS Server

In this scenario (Figure 8-7) OpenScape V1.0 supports a “redirecting” front-end LCS server. Microsoft does not support a “proxying” front-end LCS server.

This front-end LCS server is located in the same domain where OpenScape resides. Essen-tially, this server overlays onto any of the 4 supported scenarios.This server acts as a load bal-ancer to redirect traffic. Also, this server does not home anyone.

The home servers only service the users that are homed to it. These servers do not provide any redirect services, as the front-end server does that. Once a user discovers the address of their home server from the front-end server, it no longer needs to communicate with the front-end server until the user’s DNS cache expires..

Figure 8-7 Front-End Server with Single Domain

siteA.com


DC GC


DC GC


user1, user2, user3, user4 w/SIP phone

DC - Domain ControllerGC - Global Catalog


DC GC Exchange 20002003

forest1.siteA.com

Front-End Server


5350conndw.fm

Nur für den internen Gebrauch ConnectivityMix of OpenScape and non-OpenScape LCS Users

8.4 Mix of OpenScape and non-OpenScape LCS Users

The mixed OpenScape scenarios are typical of the environment seen when the LCS server is used for Presence and Instant Messaging (IM) and possibly voice communications and Open-Scape is added for individual groups within the enterprise.

In this environment:

● OpenScape users—can put other OpenScape users within their own OpenScape system on their OpenScape contact list and have full access to all OpenScape features for all com-munications they receive or initiate. They can place OpenScape and non-OpenScape us-ers on the contact list of Windows Messenger or an IP phone and can communicate with them using voice, video and IM.

● Non-OpenScape LCS users—can have OpenScape users on their contact lists and com-municate with them using voice, video, and IM.



5350conndw.fm

Mix of OpenScape and non-OpenScape LCS Users


5350phone.fm

Nur für den internen Gebrauch SIP Phones and GatewaysoptiPoint 400 standard SIP V3.0

9 SIP Phones and Gateways

This chapter describes the SIP phones and gateways that are supported by OpenScape V1.0.

9.1 optiPoint 400 standard SIP V3.0

This Siemens IP telephone uses SIP for connections to Voice-over-IP communications systems and it is interoperable with Microsoft LCS, supporting presence and instant messaging.

The hardware dependent features include:

● Full-duplex hands free

● Integrated mini-switch

● Power over LAN

Interoperability with SIP and LCS provides the following features:

● Access to contact lists and associated presence information)

● Sending, receiving instant messages

● Web-based management interface

● Device configuration through OpenScape management interface

● Authentication with LCS server

The only limitation is that there is no automatic or preconfigured association of a telephone with a specific PC or office location. Therefore in the hot-desking scenario, the user will have to log onto both devices. The user will not be able to logon to his SIP device.

For more information on the optiPoint 400 standard V3.0, refer to:

http://www.siemensenterprise.com/prod_sol_serv/products/workpoint_clients/optipoint/service_user_guide.shtml

9.2 Third-party SIP Phones

OpenScape is based on the SIP protocol standard and the Microsoft LCS platform. As such, any SIP phone that is interoperable with Microsoft LCS should also interoperate with Open-Scape. However, the exact level of interoperability will not be established until detailed tests have been carried out. Once LCS-compliant versions of some of the other leading SIP Phones (e.g., Cisco 7960, Pingtel Xpress, Polycom IP 500) are available, they will be tested with Open-Scape and an interoperability statement will be made available


SIP Phones and Gateways Nur für den internen Gebrauch

5350phone.fm

Third-party Gateways

9.3 Third-party Gateways

OpenScape V1 requires a SIP media gateway in order to connect to the time-division-multiplex-ing (TDM) world such as the PSTN and PBX systems. Such gateways must meet the following criteria:

● Be able to operate with Microsoft LCS

● Be able to operate in a standalone mode, that is, not require the gateway vendor’s soft-switch, proxy server, etc.

● Meet the minimal feature requirements of OpenScape V1.

The third party SIP gateways listed in Table 9-1 have been tested and recommended to be de-ployed with OpenScape V1:

Vendor Product Name Analog/Digital Num Ports

Region

VegaStream1

1 IPSec not supported. External or router-based IPSec solutions may be used. IPSec can provide security for the gateway by encrypting the signaling channel.

To be able to use the one-button redial feature of the Siemens SIP phones for external calls, The gateway must generate incoming SIP calls that contain a call back address that is valid for the LC server dialing plan. This may require configuration of the gateway or the TDM in-frastructure to ensure that the callback address in the SIP call is valid for the LC server to which the SIP phone is connected.

Vega50 BRI 4 spans IM

VegaStream* Vega100 T1/E1 1-60 spans

U.S./IM

Table 9-1 Third Party SIP Gateways


5350glossary.fm

Nur für den internen Gebrauch Glossary

Glossary X

A

Active DirectorySee Microsoft Active Directory.

American Standard Code for Information Interchange (ASCII)The most common format for text files in computers and on the Internet. In an ASCII file, each alphabetic, numeric, or special character is represented with a 7-bit binary number (a string of seven 0s or 1s). 128 possible characters are defined.

APISee Application Programming Interface

Application Programming Interface (API)The specific method prescribed by a computer operating system or by an application pro-gram by which a programmer writing an application program can make requests of the op-erating system or another application.

ASCIISee American Standard Code for Information Interchange.

AvailabilityThe willingness and ability of a user to engage in a communications session.

B

B2BUASee Back-to-Back User Agent

Back-to-Back User Agent (B2BUA)A SIP-based logical entity that can receive and process INVITE messages as a SIP User Agent Server (UAS). It also acts as a SIP User Agent Client (UAC) that determines how the request should be answered and how to initiate outbound calls. Unlike a SIP proxy server, the B2BUA maintains complete call state and participates in all call requests.

C

Collaboration GroupThe people who belong to or have access to the collaboration session and its data form a collaboration group.

Communications BrokerAn umbrella term for a collection of interfaces and adapting layers enabling communications in

A31003-S5020-A400-1-7618, June 2004OpenScape, System Description X-1

Glossary Nur für den internen Gebrauch

5350glossary.fm

an open environment.

Computer Supported Telephony Applications (CSTA)A protocol standard for advanced call control, used by a wide range of applications.

contact list A group of people who work closely together who have mutually agreed to share personal presence-state information with each other, for the purpose of expediting communication amongst themselves. Contact lists are joined, defined and maintained by the individuals. Individuals can be members of multiple contact lists. The Presence status of the members of each contact list is displayed on the preferred communication clients of each member.

Context ManagerThe OpenScape service that provides information about the presence and availability of users, the state of users (e.g. in a voice call), each user’s collaboration session associa-tions, etc. The result is a detailed view of what the user and their devices are doing at any point in time, which is used by other system components to make decisions about the best means to contact the user.

CRMSee Customer Relationship Management.

CSTASee Computer Supported Telephony Applications.

Customer Relationship ManagementAn information industry term for methodologies, software, and usually Internet capabilities that help an enterprise manage customer relationships in an organized way.

D

DHCPSee Dynamic Host Configuration Protocol.

DNSSee Domain Name System.

Domain Name System (DNS)The way that Internet domain names are located and translated into Internet Protocol ad-dresses. A domain name is a meaningful and easy-to-remember “handle” for an Internet address.

DTMFSee Dual-tone Multifrequency.

Dual-Tone Multifrequency (DTMF)The signal to the phone company that you generate when you press an ordinary tele-phone's touch keys.

A31003-S5020-A400-1-7618, June 2004X-2 OpenScape, System Description

5350glossary.fm


Dynamic Host Configuration Protocol (DHCP)A communications protocol that lets network administrators manage centrally and auto-mate the assignment of Internet Protocol (IP) addresses in an organization's network. Us-ing the Internet Protocol, each machine that can connect to the Internet needs a unique IP address.

E

Enterprise Resource Planning (ERP)An industry term for the broad set of activities supported by multi-module application soft-ware that helps a manufacturer or other business manage the important parts of its busi-ness, including product planning, parts purchasing, maintaining inventories, interacting with suppliers, providing customer service, and tracking orders.

ERPSee Enterprise Resource Planning.

H

H.323One of the first and most popular protocols for handling multimedia communications over IP networks. In recent times H.323 has fallen out of favor with many vendors and customer due to its complexity in implementation.

I

IISSee Internet Information Server.

Instant Messaging (IM) The ability to send messages in near real-time to other IM users, especially members with-in a personal contact list. IM is generally used to ask quick questions or send quick updates and confirmations.

Internet Information Server (IIS)A group of internet servers (including a Web or Hypertext Transfer Protocol server and a File Transfer Protocol server) with additional capabilities for Microsoft's Windows NT and Windows 2000 Server operating systems.

Integrated Services Digital Network (ISDN)A system of digital phone connections that allows data to be transmitted simultaneously across the world using end-to-end digital connectivity.

Intelligent ReachThe OpenScape feature that provides presence status of members of a user’s contact list.



5350glossary.fm

Internet Protocol (IP)The method or protocol by which data is sent from one computer to another on the Internet.

Internet Security and Acceleration (ISA)The successor to Microsoft's Proxy Server 2.0 and part of Microsoft's .NET support. ISA Server provides the two basic services of an enterprise firewall and a Web proxy/cache server.

IPSee Internet Protocol.

IpSecA protocol for negotiating encryption and authentication at the IP (host-to-host) level.

ISASee Internet Security and Acceleration

ISDNSee Integrated Services Digital Network.

J

J2EESee JAVA 2 Enterprise Edition.

JAVA 2 Enterprise Edition (J2EE)A web services programming language. J2EE is the standard used by IBM to support their WebSphere e-business applications.

K

KDCSee Key Distribution Center.

KerberosA secure method for authenticating a request for service in a computer network; the user’s password does not have to pass through the network.

Key Distribution CenterA domain service that runs on each Windows 2000 domain and provides Authentication Service and Ticket Granting Service.

Knowledge ManagerAn OpenScape architecture component that


5350glossary.fm


M

MCUSee Multipoint Conferencing Unit.

MegacoMedia Gateway Control Protocol (MGCP), also known as H.248 and Megaco, is a standard protocol for handling the signaling and session management needed during a multimedia conference. The protocol defines a means of communication between a media gateway, which converts data from the format required for a circuit-switched network to that required for a packet-switched network and the media gateway controller.

MGCP/Megaco/H.248A protocol designed for the carrier side of VoIP, to handle the integration of circuit-switched carrier SS7 systems with new carrier-class VoIP systems.

Microsoft Active DirectoryA component of Windows 2000 architecture, Active Directory presents organizations with a directory service designed for distributed computing environments. Active Directory al-lows organizations to centrally manage and share information on network resources and users while acting as the central authority for network security. In addition to providing com-prehensive directory services to a Windows environment, Active Directory is designed to be a consolidation point for isolating, migrating, centrally managing, and reducing the num-ber of directories that companies require.

Microsoft Management Console (MMC)An application that provides a graphical-user interface (GUI) and a programming frame-work in which consoles (collections of administrative tools) can be created, saved, and opened.

MMCSee Microsoft Management Console

Multipoint Conferencing Unit (MCU)Provides users the ability to set up ad hoc voice, data, or multimedia conferencing ses-sions.

O

OMCSee OpenScape Management Console.

OpenScape Management Console (OMC)The administration interface for OpenScape.



5350glossary.fm

P

PBXSee Private Branch Exchange.

PCTNSee Public Cellular Telephone Network.

Private Branch Exchange (PBX)A telephone system within an enterprise that switches calls between enterprise users on local lines while allowing all users to share a certain number of external phone lines.

PSTNSee Public Switched Telephone Network.

Public Cellular Telephone Network (PCTN)The network of cellular equipment and terminals.

Public Switched Telephone Network (PSTN)The world's collection of interconnected voice-oriented public telephone networks, both commercial and government-owned. It's also referred to as the Plain Old Telephone Ser-vice (POTS). It's the aggregation of circuit-switching telephone networks that has evolved from the days of Alexander Graham Bell (“Doctor Watson, come here!”). Today, it is almost entirely digital in technology except for the final link from the central (local) telephone office to the user.

Q

QSIGA global signalling system for corporate networks.

QoSSee Quality of Service.

Quality of Service (QoS)The idea that transmission rates, error rates, and other characteristics can be measured, improved, and, to some extent, guaranteed in advance. QoS is of particular concern for the continuous transmission of high-bandwidth video and multimedia information.

S

SALTSee Speech Application Language Tags.

SDKSee Software Development Kit.


5350glossary.fm


Self-Service PortalProvides access to OpenScape features for callers.

Session Initiation Protocol (SIP)Signaling protocol defined by the IETF for handling multimedia communications over IP networks.

Short Messaging Service (SMS)Globally accepted wireless service that enables the transmission of alphanumeric messag-es between mobile users and external systems such as electronic mail, paging, and voice-mail systems.

SIPSee Session Initiation Protocol.

SIP gatewaySupports exchange of packet-switched communications between a SIP-based communi-cations system and the PSTN or a corporate PBX.

SIP phoneIP telephone connected to any system that supports delivery of telephony functionality us-ing the SIP protocol.

SIMPLESIP for Instant Messaging and Presence Leveraging Extensions (IETF). Based on SIP, SIMPLE is an IETF standard and has emerged as the leading method of standardizing in-stant messaging and presence among various service providers.

Simple Object Access Protocol (SOAP)The variation of XML that Microsoft uses to develop web services through their .NET plat-form.

SIPSee Session Initiation Protocol.

SMSSee Short Messaging Service.

SOAPSee Simple Object Access Protocol. (XML protocol).

Speech Application Language Tags (SALT)A lightweight set of extensions to existing markup languages, in particular HTML and XHT-ML that enable multimodal and telephony access to information, applications and Web ser-vices from PCs, telephones, tablet PCs and wireless personal digital assistants (PDAs).

SQLSee Structured Query Language.



5350glossary.fm

Structured Query Language (SQL)A standard interactive and programming language for getting information from and updat-ing a database.

T

TCPSee Transmission Control Protocol.

TDMSee Time-Division Multiplexing

TGTSee Ticket Granting Ticket.

Ticket Granting Ticket (TGT)Part of the Kerberos Version 5 IETF standard protocol that provides user authentication.

Time-division multiplexing (TDM)A method of putting multiple data streams in a single signal by separating the signal into many segments, each having a very short duration. Each individual data stream is reas-sembled at the receiving end based on the timing.

TLSSee Transport Layer Security.

Transmission Control Protocol (TCP)A set of rules (protocol) used along with the Internet Protocol (IP) to send data in the form of message units between computers over the Internet. While IP takes care of handling the actual delivery of the data, TCP takes care of keeping track of the individual units of data (called packets) that a message is divided into for efficient routing

Transport Layer SecurityA protocol that ensures privacy between communicating applications and their users on the Internet. When a server and client communicate, TLS ensures that no third party may eavesdrop or tamper with any message. TLS is the successor to the Secure Sockets Layer (SSL).

U

User Notification ServiceThe architecture component that provides a mechanism for sending a notification message to users.


5350glossary.fm


V

Voice PortalProvides voice (telephone) access to OpenScape features.

W

Web Services Description Language (WSDL)An XML-based language used to describe the services a business offers and to provide a way for individuals and other businesses to access those services electronically.

Web Telephony Engine (WTE)A run-time engine in Windows 2000 that uses HTML to enable the use of standard web authoring tools to create a variety of telephony solutions, such as Interactive Voice Re-sponse (IVR), voice mail, automatic call distribution, and call centers.

Word WebThe OpenScape feature that allows users to create a document using Microsoft Word 2000 that can be saved as HTML and used as a voice application.

Windows Management Instrumentation (WMI)Microsoft's implementation of Web-Based Enterprise Management (WBEM) technology. WBEM is a standard that the Distributed Management Task Force (DMTF—an industry consortium) defines. The WBEM standard encompasses the design of an extensible en-terprise data-collection and management facility that has the flexibility and extensibility re-quired to manage local and remote systems that comprise arbitrary components.

Windows Scripting Host (WSH)A Windows administration tool that creates an environment for hosting scripts. That is, when a script arrives at your computer, WSH plays the part of the host — it makes objects and services available for the script and provides a set of guidelines within which the script is executed. Among other things, Windows Script Host manages security and invokes the appropriate script engine

Workgroup Collaboration PortalThe part of the OpenScape user interface that allows users to manage collaboration ses-sions.

WMISee Windows Management Instrumentation.

WSHWindows Script Host

WTESee Web Telephony Engine



5350glossary.fm

X

XML eXtensible Markup Language, a standard for the exchange of structured and networked data on the Web. XML documents can define their own tags, providing outstanding flexibil-ity. XML makes it easy to define, author and manage SGML-defined documents and makes easy to share and transmit these documents.


5350SystemIX.fm

Nur für den internen Gebrauch Index

Index Z

Aactions for incoming emails 4-11actions for incoming instant messages 4-8actions for outgoing instant messages 4-10Active Directory, role of 1-6administration interface 2-3anonymous guest, definition 6-4appointments, scheduling from Self-Service Portal 6-6

Assistant Engine 1-12associated devices 3-6

BBack-to-Back User Agent (B2BUA) 1-6browser view of Personal Portal 3-1

Ccalendar appointments, user checking by phone 6-2

capacities 1-25contact access through Self-Service Portal 6-4

contact guests for Self-Service Portal 6-5contact information, reviewing through Voice Portal 6-3

contact, password for using Self-Service Por-tal 6-4

contacts in Windows Messenger 3-4contacts, communicating with 3-3Context Data Record (XDR) Service 1-14Context Manager 1-13

Ddata storage for workgroups 1-7default rules 4-12deployment, typical 1-1device management in OMC 2-5devices, configuring 3-6devices, registered and associated 1-6document access from Self-Service Portal 6-

A31003-S5020-A400-1-7618, June 2004OpenScape, System Description

7

Eexceptions for incoming emails 4-12exceptions for incoming instant messages 4-9

exceptions for outgoing instant messages 4-10

Ffault management 2-14

Gguest access to Self Service Portal 6-4guests, contacts and anonymous 6-4

Iincoming calls, exceptions 4-6incoming calls, possible actions 4-5incoming calls, rules for 4-4incoming emails, actions 4-11incoming emails, exceptions 4-12incoming emails, rules for 4-11incoming instant messages, actions 4-8incoming instant messages, exceptions 4-9installation of OpenScape 2-14instant messages, rules for 4-7Interaction Center, described 6-8interactive dialogs provided by Media Server 6-8

Kknowledge management reports 2-12Knowledge Manager 1-12

Llanguage support 2-2languages for OMC 2-3Licensing Management function in OMC 2-13

Live Communications Server (LCS) 1-1

Z-1

Index Nur für den internen Gebrauch

5350SystemIX.fm

Mmanagement architecture 2-1management console for OpenScape 2-3MCU description 1-4MCU ports, numbers 1-25MCU Server 1-1media gateway 1-4Media Server 1-1, 1-4Media Server administration tool 6-8Media Server ports 1-25Media Server, examples of interaction with OpenScape 6-8

Microsoft Office Live Communications Server (LCS) 1-1

multi-language support 2-2Multipoint Control Unit (MCU) 1-1My Calls 3-3My Contacts

Personal PortalMy Contacts 3-3

My Preferred Phone 3-3My Status 3-2My Work Groups 3-5

Nnumber of users supported 1-25

OOMC 2-1OpenScape dependencies on LCS 1-6OpenScape interaction with Media Server 6-8

OpenScape management 2-1OpenScape Management Console 2-3optiPoint 400 standard SIP V3.0 9-1outgoing calls, exceptions 4-7outgoing calls, possible actions 4-6outgoing calls, rules for 4-6outgoing instant messages, actions 4-10outgoing instant messages, exceptions 4-10outgoing instant messages, rules for 4-10Outlook and Exchange Server, interaction with OpenScape 6-12

Outlook Contacts, configuration of 6-12

overview of OpenScape 1-1

Ppassword for Self-Service Portal 6-4Personal Portal 3-1

My Calls 3-3My Preferred Phone 3-3My Status 3-2My Work Groups 3-5

phone access for OpenScape users 6-1Phone Favorites feature 6-3Pre-defined Outlook folders 6-12predefined statuses for users 3-2preferred phone 3-3

Rregistered devices 3-6reports on knowledge management 2-12Resource Monitor in OMC 2-12Routing Dispatcher 1-6rules for incoming calls 4-4rules for incoming emails 4-11rules for incoming instant messages 4-7rules for outgoing calls 4-6rules for outgoing instant messages 4-10Rules Wizard, 4-1rules, default 4-12

SSelf-Service Portal 6-4servers that comprise OpenScape 1-1Session Initiation Protocol (SIP) gateway 1-4shortcuts for Voice Portal 6-3SIP endpoints 1-4status for users 3-2status in Windows Messenger 3-2storage function 2-10support for English and German 2-2system capacities 1-25Systems Destination function in OMC 2-12

Tthird-party gateways 9-2typical deployment 1-1

A31003-S5020-A400-1-7618, June 2004Z-2 OpenScape, System Description

5350SystemIX.fm

Nur für den internen Gebrauch Index

UUser Notification Service 1-7user status 3-2users, number supported 1-25

VVirtual Assistant 1-6voice and email messages, listening 6-1voice messages, creating and deleting 6-2Voice Portal 6-1

WWindows Messenger, contacts in 3-4Windows Messenger, status in 3-2Workgroup Assistant 1-7Workgroup Portal 5-1workgroups 1-7

A31003-S5020-A400-1-7618, June 2004OpenScape, System Description Z-3

Index Nur für den internen Gebrauch

5350SystemIX.fm

A31003-S5020-A400-1-7618, June 2004Z-4 OpenScape, System Description

www.siemens.com/hipath

Siemens AG 2003, 2004 • Information and Communication Networks • Hofmannstraße 51 • D-81359 München, GermanyReference No.: A31003-S5020-A400-1-7618 Printed in the Federal Republic of Germany. Subject to availability. Right of modification reserved.

The information provided in this document contains merely general de-

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

*1PA31003-S5020-A400-1-7618*

OpenScape V2.0 System Description

Documents

server management

system management

openscape server

openscape management

sdk management

user management

fault management

device management