OpenScape V2.0 Media Server Installation Guide

HiPath OpenScape Media Server
V2.0
Installation Guide
*1PA31003-S5020-S200-1-7620*
1P A31003-S5020-S200-1-7620
The information provided in this document contains merely general descriptions or

characteristics of performance which in case of actual use do not always apply as described or which may change as a result of further development of the products.
An obligation to provide the respective characteristics shall only exist if expressly
agreed in the terms of contract.
Siemens AG 2004
Information and Communication Networks,
Hofmannstrae 51, D-81359 Mnchen, Germany
Reference No.: A31003-S5020-S200-1-7620 Printed in the Federal Republic of Germany.
Subject to availability. Right of modification reserved.
5458TOC.fm
Nur fr den internen Gebrauch
Content
Content
1 About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.1 Who Should Use This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Related Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3 Documentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-1
1-1
1-1
1-1
2 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1 Telecommunication Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2 Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3 Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4 Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-1
2-1
2-1
2-2
2-3
3 Installing Windows Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.1 Windows 2000 Advanced Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2 Windows 2000 Server Service Pack 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3 Internet Explorer 6.0 with Service Pack 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4 Windows Script Host 5.6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5 Removing Terminal Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.6 Installing Virus Scan Software (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.7 Server Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.8 Step for Exchange 2003 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.9 Front-End and Back-End Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.10 Disabling Restrict CD-ROM Access to Locally Logged-on User Only Parameter . .
3.11 Requesting a Certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-1
3-1
3-1
3-2
3-2
3-2
3-2
3-3
3-3
3-3
3-3
3-4
4 Pre-Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

4.1 HiPath OpenScape/Live Communications Installed . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4.2 Using HiPath OpenScape RTC Config Tool to check and create a new static route trusted
if needed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4.3 Verifying Media Server System Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4.4 Validating the Creation of Media Server Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4.5 Creating Mailboxes for the Media Server Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
4.6 Validating and Configuring Media Server Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
4.7 Validating the <systemID>SiemensIC Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
4.8 Validating the Creation of the Destination Target . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
4.9 Verifying the HiPath OpenScape License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
4.10 Verifying IPSec settings on Media Server & HiPath OpenScape Servers . . . . . . . . . 4-4
5 Installing Third-Party Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2 Installing Package 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-1
5-1
5-1
5-1
5-2
A31003-S5020-S200-1-7620, July 2004

HiPath OpenScape Media Server V2.0, Installation Guide
0-3
5458TOC.fm
Content
5.5 Validating the Locale in the Registry. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

5.6 Validating OSR is installed and Configured Correctly. . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
5.7 Siemens Voice Browser Software Upgrade Instructions. . . . . . . . . . . . . . . . . . . . . . . . 5-4
6 Installing and Validating Media Server Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
6.1 Installing Media Server Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
6.2 Validating Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
7 Configuring the Media Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
7.1 Setting Content Expiration Dates in IIS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
7.2 Entering HiPath OpenScape System Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
7.3 Importing Subscribers into Media Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
7.3.1 Importing HiPath OpenScape Subscribers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
7.3.2 Importing Non-HiPath OpenScape Subscribers . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
7.4 Preparing Media Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
7.4.1 Entering the Interaction Center Super User Credentials . . . . . . . . . . . . . . . . . . . . 7-5
7.4.2 Configuring the Front-End Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7
7.4.3 Interaction Center Folders for Individual Subscribers. . . . . . . . . . . . . . . . . . . . . . . 7-7
7.4.4 Subscriber Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11
7.5 Managing Default Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13
7.6 Saving a Recovery Image (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13
8 Creating Applications in Media Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
8.1 CRDirectApp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
8.2 CRForwardApp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
9 Testing Media Server with HiPath OpenScape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1 Interoperability Tests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.2 Diagnostic Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.3 Testing Direct Call to the Media Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.4 Routing Through HiPath OpenScape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.5 HiPath OpenScape Voice Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10 Maintenance Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.1 Uninstalling Media Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.1.1 Uninstalling the Media Server Application Only . . . . . . . . . . . . . . . . . . . . . . . . .
10.1.2 Uninstalling the VocalOS Browser and Media Server Application . . . . . . . . . . .
10.2 Reinstalling Media Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.3 Backing Up and Restoring Media Server User Data. . . . . . . . . . . . . . . . . . . . . . . . .
10.3.1 Backing Up and Restoring Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.3.2 Backing up and Restoring Customer-Created Applications . . . . . . . . . . . . . . . .
10.3.3 Backing Up and Restoring Report Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.4 Media Server Dependability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.5 Restoring Media Server Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.5.1 Recovery if You Have Recovery Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.5.2 Recovery Without Recovery Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9-1
9-1
9-2
9-4
9-5
9-5
10-1
10-1
10-1
10-1
10-2
10-2
10-2
10-2
10-4
10-5
10-5
10-5
10-6
11 Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1
0-4
A31003-S5020-S200-1-7620, July 2004

5458TOC.fm
Content
11.1 Siemens TAPI Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1

11.1.1 Other Features of the TAPI Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2
11.2 System Verification Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3
A Miscellaneous. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
A.1 Updating the Number of Lines When the License Changes . . . . . . . . . . . . . . . . . . . . A-1
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Z-1
A31003-S5020-S200-1-7620, July 2004

0-5
5458TOC.fm
Content
0-6
A31003-S5020-S200-1-7620, July 2004

5458pref.fm
About This Guide
Who Should Use This Guide
About This Guide
This guide provides an overview of HiPath OpenScape Media Server V2.0 and instructions for
installing, maintaining, and troubleshooting the product. The HiPath OpenScape Media Server
application runs on the Media Server machine.
Check the KMOSS website at https://kmoss.icn.siemens.de for the latest version of this guide.
1.1
Who Should Use This Guide
This guide is provided for use by qualified personnel including Siemens TST, VARs and SIs who
will install the HiPath OpenScape Media Server.
1.2
Related Information
For task-related information on using the Media Server System Administrator, refer to the online
Help.
The following also contain related information:
1.3
HiPath OpenScape Media Server Administration Guide A31003-S5020-A600
Installation Guide A31003-S5020-S100
Administration Guide A31003-S5020-A900
User Guide A31003-S5020-A100
Project Planning Guide A31003-S5020-A300
Documentation Feedback
To report a problem with this document, call your next level of support.
When you call, be sure to include the following information. This will help identify which document you are having problems with.
Title: HiPath OpenScape Media Server V2.0, Installation Guide
Order Number: A31003-S5020-S200-1-7620
A31003-S5020-S200-1-7620, July 2004

1-1
5458pref.fm
About This Guide

Documentation Feedback
1-2
A31003-S5020-S200-1-7620, July 2004

5458intro.fm
Overview
Telecommunication Platforms
Overview
This chapter provides a high-level overview of HiPath OpenScape Media Server application
running on the Media Server. It also provides an overview of the installation process.
>
Note that the Media Server installation is part of the overall HiPath OpenScape installation as described in the HiPath OpenScape Installation Guide. This Guide also
includes instructions on how to upgrade the HiPath OpenScape Media Server from
V1.0 SPCR to V2.0 as part of the overall upgrade.
The installation consists of
Pre-installation checklist
Installation
Windows components
Third party software
HiPath OpenScape Media Server application
Post-installation steps
For uninstallation and re-installation, refer to Section 10.1 and Section 10.2, respectively.
2.1
Telecommunication Platforms
HiPath OpenScape Media Server can be used with the following platforms:
SIP-based platform - HiPath OpenScape
2.2
Hardware Requirements
The following are the minimum hardware requirements for the HiPath OpenScape Media Server:
One CPU
2.0 GHz Pentium III or higher
Memory: 1024 MB
Drives:
At least 10 GB of free space
One 3.5" floppy disk drive (optional)
One CD-ROM, 4x minimum
A31003-S5020-S200-1-7620, July 2004

2-1
5458intro.fm
Overview
Software Requirements
NIC: 10/100 MB Ethernet
NOTE: If you have more than one NIC card in your server, a special configuration is required - see step 6 on page 6-2 in Section 6.2, Validating Installation.
Peripherals:
Monitor and SVGA video controller (800x600 minimum resolution if using System Administration console on the server)
Keyboard - 101
Mouse or other compatible pointing device
2.3
Software Requirements
The three basic components are:
Several Windows components including Windows 2000 Advanced Server as described in Chapter 3, Installing Windows Components.
Third-party software as described in Chapter 5
HiPath OpenScape Media Server software as described in Chapter 6
2-2
Do not install HiPath OpenScape Media Server on any machine that is:
a Domain Controller or DNS server
running any database program like MS SQL Server, Informix, etc.
running any significant software program like Microsoft Exchange program
A31003-S5020-S200-1-7620, July 2004

5458intro.fm
2.4
1.
Overview
Installation Overview
HiPath OpenScape Media Server installation consists of the following components:
Core software for the HiPath OpenScape Media Server;
Third Party Software CD contains 3rd Party Software required for the HiPath OpenScape applications (there are different versions of this CD for the various languages
supported including US English, UK English and German);
OpenScape XX 3rd Party Software CD contains 3rd party software to be installed

on German and UK English Media Server systems;
Service Pack CD contains HiPath OpenScape Service Packs and documentation.
2.
Be sure to verify the hardware/software requirements mentioned in Section 2.2 and

Section 2.3.
3.
Install Windows components
4.
It is imperative that all steps in the Pre-installation checklist (Chapter 4) be performed before starting the installation.
5.
6.
7.
Ensure that HiPath OpenScape and Live Communications have been installed
Check if RTC tool has been run to ensure that the HiPath OpenScape Media Server
has trusted static routing and endpoints
Validate that the Environment Preparation Tool has been run or manual preparation
has been performed so that the required HiPath OpenScape Media Server accounts
have been created and configured
Install Virus scan software (optional)
Obtain server info and accounts (done as part of Pre-Installation Checklist in HiPath
OpenScape Installation Guide)
Request certificate
Install
Third-party software components
HiPath OpenScape Media Server software and validate
Post-install
Configure Media Server for HiPath OpenScape
Install patches
Configure the HiPath OpenScape Media Server:
A31003-S5020-S200-1-7620, July 2004

2-3
5458intro.fm
Overview
Import subscribers into Media Server
Prepare Media Server
Enable SiemensIC super user credentials
Create Interaction Center folders for Individual Subscribers
Verify subscriber profiles
8.
Create HiPath OpenScape Media Server applications
9.
Test Media Server with HiPath OpenScape:
2-4
Interoperability tests
Diagnostic test
Make direct call
Route through HiPath OpenScape
A31003-S5020-S200-1-7620, July 2004

5458windowcomp.fm
Installing Windows Components
Windows 2000 Advanced Server
Perform the following on the HiPath OpenScape Media Server machine using the <osinstaller>
account - verify that this account has local admin rights.
>
3.1
Note: Be sure to install all critical and current Windows updates which may not be
specifically listed here.
Windows 2000 Advanced Server
This should be done as part of the installation.

1.
Install Windows 2000 Advanced Server, following the instructions provided by Microsoft.
>
Note: For any country or language (German, UK English, etc.), install the US
English version of Win2k Advanced Server and set locale to US English. This
is the only configuration currently supported by the Speech Recognizer. If the
operating system is installed and ONLY the locale is not set to US English, there is
a patch to set the locale in the registry to US English - see Section 5.5, Validating
the Locale in the Registry.
2.
Install Simple Network Management Protocol (SNMP), which is a subcomponent under the
optional component Management and Monitoring Tools. This is required for the CAP
Fault Management system which is installed with the third party software installation.
3.
Install the optional component Internet Information Services (IIS), version 5.0 with the following subcomponents of IIS:
3.2
Common Files
Front Page Server Extensions
IIS Snap-in
SMTP Service
World Wide Web Server (Do not install the documentation)
Windows 2000 Server Service Pack 4
1.
From the Start menu, select Windows Update to open the Windows Update website.
2.
Follow the instructions on the website to install Windows 2000 Service Pack 4.
A31003-S5020-S200-1-7620, July 2004

3-1
5458windowcomp.fm

Internet Explorer 6.0 with Service Pack 1
3.3
Internet Explorer 6.0 with Service Pack 1
1.
From the Start menu, select Windows Update to open the Windows Update website.
2.
Follow the instructions on the website to install Internet Explorer 6, SP1.
3.4
Windows Script Host 5.6
Be sure you are at Windows Script Host 5.6. You can upgrade to this version at http://msdn.microsoft.com/scripting/.
To see which version you are at:
1.
Click Start->Run.
2.
Enter cmd, then click OK.
3.
Then at the command prompt window, type cscript, then hit Enter.This will show the version and how to use cscript.
3.5
Removing Terminal Services
If Terminal Services is installed on the HiPath OpenScape Media Server machine, then disable
it as follows:
1.
Go to the Windows Service Control Manager.
2.
Check if Terminal Services is in the list. If not, continue to the next section.
3.
If so, right click Terminal Services, then click Properties.
4.
Change the Startup type to Disabled. Click Apply.
5.
Reboot the PC.
3.6
Installing Virus Scan Software (optional)
There is no installation of virus-scan software with HiPath OpenScape Media Server.

Install virus scanning software at your own discretion.
HiPath OpenScape Media Server has been tested with McAfee VirusScan v4.5 w/Service Pack
1 and VirusScan Enterprise 7.0.0.
3-2
A31003-S5020-S200-1-7620, July 2004

5458windowcomp.fm

Server Information
3.7
Server Information
Complete the following (refer to the section on Server Information in the HiPath OpenScape Installation Guide - this should have been done already):
HiPath
OpenScape
Media Server
HiPath
OpenScape
Live Communications
Exchange
2000/2003
N/A
N/A
N/A
Host Name
Domain Name
Fully Qualified Domain Name (FQDN)
IP Address
Voice Portal extension
Table 3-1
3.8
Server Information
Step for Exchange 2003
If you are using Exchange 2003 in your domain, IIS WebDAV of the Exchange Server must be
set to Allowed. Refer to Appendix B.1 of the HiPath OpenScape Installation Guide for instructions.
3.9
Front-End and Back-End Servers
This applies to configurations with Front-End Servers for Exchange.

The FQDN of the Exchange Front-End Server(s) is required. The name of the associated Exchange back-end server is also needed for Section 7.4.2, Configuring the Front-End Server.
3.10
Disabling Restrict CD-ROM Access to Locally Logged-on User

Only Parameter
This applies to Windows 2K Advanced Server only.

If this parameter is enabled, then it will prevent the user from installing MSDE from the CD;
therefore, disable this parameter as follows:
1.
Go to Local Security Policy.
2.
In the Local Security Settings window, expand Local Policies->Security Options.
3.
Right click Restrict CD-ROM access to locally logged-on user only. Click Security...
4.
Change the Local Policy Setting to Disabled. Click Ok.
A31003-S5020-S200-1-7620, July 2004

3-3
5458windowcomp.fm

Requesting a Certificate
3.11
Requesting a Certificate
Logon to the HiPath OpenScape Media Server with an account that can request machine certificates from the Certificate Authority. Then perform the following steps.
1.
Click Start->Run.
2.
Enter mmc and click OK.
3.
Select Console, then Add/Remove Snap-in.
4.
In the Add/Remove Snap-in window, click Add.
5.
In the Add Standalone Snap-in window, select Certificates, then click Add.
6.
In the Certificate Snap-in window, select Computer account, then click Next.
7.
In the Select Computer window, select Local computer, then click Finish.
8.
Click Close in the Add Standalone Snap-in window.
9.
Click OK in the Add/Remove Snap-in window.
10. Expand Certificates (local computer).

11. Right-click Personal, then click All Tasks->Request New Certificate.
12. In the Certificate Request Wizard window, click Next.
13. Click Next.
14. In the Friendly name field, enter Media Server Certificate, then click Next.
15. Click Finish.
16. Click OK.
17. Expand Personal->Certificates, then double-click the FQDN of Media Server.
18. Click the Certification Path tab.
19. Locate the Certificate Status box in the lower part of the window and verify there is a message This certificate is OK., then click OK.
20. Close Console without saving.
3-4
A31003-S5020-S200-1-7620, July 2004

5458checklist.fm
Pre-Installation Checklist
HiPath OpenScape/Live Communications Installed
This chapter provides a checklist of tasks that must be performed and completed before starting installation of HiPath OpenScape Media Server.
4.1
HiPath OpenScape/Live Communications Installed
Verify that HiPath OpenScape and Live Communications have been installed properly.
Go to the HiPath OpenScape server and log in as <osinstaller>.
4.2
Using HiPath OpenScape RTC Config Tool to check and create a

new static route trusted if needed
This is performed on the server where the Routing Dispatcher is installed.

1.
Open the Explorer window and go to c:\Program Files\Siemens\Hipath Routing Dispatcher\tools.
2.
Double-click OpenScapeRTCtool.exe.
3.
Check if the static route trusted has been created by clicking Display Current LCS Configuration. If yes, continue to next section.
4.
If not, select Create New Static Route, and enter for each field as follows:
Match Uri sip:*@FQDN of the Media Server e.g. sip:*@Aple.Bluechip.uk.com.
Next Hop sip:*@FQDN of the Media Server e.g. sip:*@Aple.Bluechip.uk.com.
Port 5060 (by default)
Route Type Trusted
4.3
Verifying Media Server System Preparation
Make sure that System Preparation has been performed for the Media Server using the Environment Preparation Tool. Refer to section 8.15, Media Server System Preparation and Verification, in the HiPath OpenScape Installation Guide.
4.4
Validating the Creation of Media Server Accounts
Validate these account creations by the Environment Preparation Tool as follows:

1.
Click Start->Run and enter mmc.
2.
Click Add Active Directory Users and Computers.
A31003-S5020-S200-1-7620, July 2004

4-1
5458checklist.fm
Creating Mailboxes for the Media Server Accounts
3.
Expand Active Directory Users and Computers-><domain>->Users.
4.
Verify that these Media Server accounts have been created:
<systemID>SiemensCR
<systemID>SiemensIC
<systemID>CRDirect
<systemID>CRForward
where <systemID> is the HiPath OpenScape system name e.g. PeachCRForward if the HiPath OpenScape system name is Peach.
5.
If accounts are missing, it means that Environment Preparation was not run properly and
it needs to be re-run. Please refer to the HiPath OpenScape Installation Guide for details.
4.5
Creating Mailboxes for the Media Server Accounts
These four Media Server accounts each need to have a mailbox created on the Exchange
Server.
1.
On the Exchange Server or on a computer with an Exchange Server snap-in, click Start>Run and enter mmc.
2.
Click Add Active Directory Users and Computers.
3.
Expand Active Directory Users and Computers-><domain>->Users.
4.
For each Media Server account, do the following:

a) Right click on the user.
b) Select Exchange Tasks.
c)
Select Create mailbox.
d) Click Next twice and then Finish.
4.6
Validating and Configuring Media Server Accounts
Validate that all the Media Server accounts have been added to the LCS.
Validate and configure CRDirect and CRForward accounts by following instructions in Appendix C in the HiPath OpenScape Installation Guide.
Configure SiemensCR and SiemensIC as HiPath OpenScape users. Please refer to the Appendix B of the HiPath OpenScape Installation Guide.
4-2
A31003-S5020-S200-1-7620, July 2004

5458checklist.fm
4.7
Validating the <systemID>SiemensIC Account
Validating the <systemID>SiemensIC Account
On the Exchange Server, validate that the SiemensIC account has permissions set properly.
Please refer to the Appendix B of the HiPath OpenScape Installation guide for instructions.
4.8
Validating the Creation of the Destination Target
This information is same as Appendix C.3 of HiPath OpenScape V2 Installation Guide:

1.
Expand the HiPath OpenScape snap-in and the server where <systemID>CRForward is a
member.
2.
Expand System Management.
3.
Double-click System Destination.
4.
Right-click on the System Destination Administration window, then select Add Destination.
5.
For the Destination Name field, enter VoiceMail.
6.
For the Contact Address field, enter sip:<systemID>CRForward@<domain_name>

where <domain_name> is your domain.
7.
For the Destination Type field, select Media Server from the dropdown menu.
8.
Click OK.
9.
Click Close on the System Destination Administration window.
Verify that the SIP URI of the <systemID>CRForward account is the same as the <systemID>CRForwards e-mail address. Check if the domain-name part (i.e. after the @ symbol)
specifies the root domain.
4.9
Verifying the HiPath OpenScape License
Using the Windows Service Control Manager, make sure that the SIemens License Management service is running.
1.
Using MMC, load the OpenScape snap-in.
2.
Double-click HiPath OpenScape [2.0].
3.
Double-click the OpenScape server name.
4.
Click System Management.
5.
Double-click Licensing in the right-hand window.
6.
Click the Licenses tab.
A31003-S5020-S200-1-7620, July 2004

4-3
5458checklist.fm
Verifying IPSec settings on Media Server & HiPath OpenScape Servers
7.
Verify that non-zero values exist for the Communications Broker and
SIP_Interaction_Sessions license types in the Installed Unexpired column. Also, a valid
MAC address should appear in the MAC Address column. If not, a valid OpenScape license needs to be installed (refer to the OpenScape V2.0 Installation Guide).
4.10
Verifying IPSec settings on Media Server & HiPath OpenScape

Servers
Make sure that the IPSecurity settings on the HiPath OpenScape and Media Server PCs match
(either both ON or both OFF). On both servers, do the following:
1.
Click Start->Run and enter mmc.
2.
Click Console->Add/Remove Snap-in.
3.
Click Add.
4.
Select IP Security Policy Management.
5.
Click Add.
6.
Make sure Local computer is selected.
7.
Click Finish, then Close and OK.
8.
Click IP Security Policy on Local Machine.
9.
Verify that Policy Assign is either ON or OFF.
4-4
A31003-S5020-S200-1-7620, July 2004

5458third.fm
Installing Third-Party Software
Introduction
5.1
Introduction
The Third Party Software CD contains three Packagex.bat files which need to be run in order.
The HiPath OpenScape Media Server machine will need to be restarted as indicated in the following instructions. Once all the third party software is installed and configured the HiPath
OpenScape Media Server software itself can be installed.
From this point please log in as <osinstaller> for installation of HiPath OpenScape Media Server components.
5.2
Installing Package 1
1.
Insert the Third Party Software CD into the CD-ROM drive.
2.
Execute the file <CD-ROM drive>:\Package1.bat. This installs the .Net Framework and the
ASP.NET Roll Up, a .Net Hotfix, MSDE 2000 database and SP 3, Microsoft IE Web controls, Siemens CAP Fault Management, and Speechify TTS Core. This will require a few
minutes to install. NOTE: No progress bars are shown.
3.
When the command window (DOS Prompt) shows Package1 is complete, your machine
should reboot. If error messages are displayed, contact technical support before continuing with the next section.
4.
After the restart completes, continue with the next section.
5.3
1.
Execute the file <CD-ROM drive>:\Package2.bat. This installs Speechify TTS Mara and
Speechify OSR Core. This will require a few minutes to install.
2.
If error messages are displayed, contact technical support before continuing with the next
section.
3.
When Package 2 is completed, it will automatically reboot your machine. After the restart
completes, continue with the next section.
A31003-S5020-S200-1-7620, July 2004

5-1
5458third.fm

5.4
1.
Execute the file <CD-ROM drive>:\Package3.bat. This installs the all Speechify OSR Language Pack and the Siemens Voice Browser. After the software is installed the configuration file for ScanSoft and some Service startup values are automatically configured. This
will require a few minutes to install.
2.
When the command window (DOS Prompt) shows Package 3 is complete, check carefully
that no error messages are displayed. If error messages are displayed, contact technical
support before continuing with the next section.
3.
Windows should then restart.
4.
For non-US installations only:

Locate and run the ADDUSOSR batch file from the OpenScape XX 3rd Party Software CD.
5.5
Validating the Locale in the Registry
The registry setting for the Locale needs to be set to US English; otherwise, the speech recognition engine will not work properly. Please do the following to check whether the Locale is US
English for your system:
1.
Click Start->Run. Enter regedit, then click OK.
2.
In the Registry Editor, expand HKEY_USERS -> .Default -> Control Panel -> International.
3.
In International, check if Locale is set to 00000409 and sCountry is set to United States.
If so, then proceed to Section 5.6, Validating OSR is installed and Configured Correctly.
4.
If either Locale or sCountry is not set to those values, the following instructions need to be
done in order to set the Locale to US English:
5.6
Go to the Patch folder on the OpenScape Third party software CD.
Copy DefaultUserLocaleSettings.reg to your computer and double-click the file to run

it.
Validating OSR is installed and Configured Correctly
1.
START Speechworks OSR Service or RESTART the Speechworks OSR Service (if already started).
2.
Go to DOS (CMD) window and type following:

>cd c:\Program Files\Speechworks\OpenSpeech Recognizer\bin
>SWIrectest
5-2
A31003-S5020-S200-1-7620, July 2004

5458third.fm
3.

Validating OSR is installed and Configured Correctly
You should see the following:

Make sure that the RecoCount was successful and there are zero failures.
Reboot the server.

A31003-S5020-S200-1-7620, July 2004
5-3
5458third.fm

Siemens Voice Browser Software Upgrade Instructions
Now that you are done, continue with Chapter 6, Installing and Validating Media Server
Software.
5.7
Siemens Voice Browser Software Upgrade Instructions
This section covers upgrading Siemens Voice Browser (Vocalocity) software. Vocalocity also
installs the Firebird DB software. It is assumed that the previous version of VocalOS has been
uninstalled using instructions from Chapter 10, Maintenance Procedures.
1.
Insert the Third Party Software CD into the CD-ROM drive.
2.
Execute the file <CD-ROM drive>:\SiVBinst.bat. This installs the Siemens Voice Browser.
3.
When the command window (DOS Prompt) shows SiVBinst.bat is complete, check carefully that no error messages are displayed. If error messages are displayed, contact technical support before continuing with the next section.
4.
Your windows system should restart now. If it does not automatically restart, manually restart the PC. At this point continue with the upgrade of the actual HiPath OpenScape Media
Server software.
5-4
A31003-S5020-S200-1-7620, July 2004

5458install.fm
Installing and Validating Media Server Software
Installing Media Server Software
This chapter provides information on installing Media Server and validating the installation.
6.1
Installing Media Server Software
1.
Logon as <osinstaller>.
2.
From the HiPath OpenScape Installation Programs CD, open the HiPath OpenScape Media Server folder, then double-click OpenScapeMediaServer.exe.
3.
Select the appropriate language, then click OK.
4.
On the Welcome dialog box, click Next.
5.
On the Customer Information dialog box, enter user name and company name, then click
Next.
6.
On the Custom Setup dialog box, select HiPath OpenScape Media Server, then click
Next.
7.
On the HiPath OpenScape Media Server System Information dialog box, enter the HiPath OpenScape system name (e.g. CROopenscape) and the HiPath OpenScape Service
password, then click Next.
8.
Enter the DB server and DB instance info, then click Next.
9.
On the Ready to Install the Program dialog box, click Install.
10. Click Finish when done.

11. When prompted to reboot the PC, click No.
6.2
Validating Installation
1.
Go to the Service Control Manager. Change the Startup type of Siemens HPCR Startup
Windows Service from Automatic to MANUAL.
2.
Then restart Windows (Reboot).
3.
Logon to Windows with the <osinstaller> account name and password.
4.
Install Patches from the Service Pack CD - the patches are delivered on the Service Pack
CD of the product set.
5.
Validate if SieSiP has been installed correctly.

Go to Control Panel->Phone and Modem Options->Advanced tab.
A31003-S5020-S200-1-7620, July 2004

6-1
5458install.fm

Check if Siemens TAPI Service Provider is installed. If Siemens TAPI service IS installed,
continue to step 6.
If Siemens TAPI Service Provider IS NOT INSTALLED, do the following:
Reboot the system
Check if following six files are in the C:\Program Files\Siemens\iwr\bin directory:

a) SieSip.tsp
b) SieWav.dll
c)
WaveRTP.dll
d) OpenH323.dll
e) PTLib.dll
f)
Libg723.dll
If NOT, please COPY them from the WINDOWS\system32 directory to C:\Program

Files\Siemens\iwr\bin directory, then delete them from the system32 directory.
Perform the following:

a) Start -> Run -> cmd
b) cd C:\Program Files\Siemens\iwr\bin
c)
SieSipInstall /d /f
d) There should be NO error messages
6.
Check Phone and Modem options again. If TAPI Service Provider is still not installed
call technical support.
If the Media Server PC does not have more than one NIC device, then proceed to step 7.
If the Media Server PC has more than one NIC device, the IP address of the selected NIC
card must be assigned in the Vocalocity configuration files.
a) In the file, C:\Program Files\Siemens\Media Server Voice Browser\Server\server\nodeserver\deploy\jboss-mx-remoting-service.xml, replace localhost with the IP
address of the selected NIC card in the lines:
<attribute name="InvokerLocator">socket://localhost:51090</attribute>
<mbean code=org.jboss.remoting.detection.multicast.MulticastDetector
name=jboss.remoting:service=Detector,transport=multicast>

<attribute name=BindAddress>localhost</attribute>
<attribute name=Port>51055</attribute>
</mbean>
b) In the file, C:\Program Files\Siemens\Media Server Voice Browser\Server\server\node\deploy\jboss-mx-remoting-service.xml, replace localhost with the IP address
of the selected NIC card in the following lines:
<attribute name="InvokerLocator">socket://localhost:51091</attribute>
<mbean code="org.jboss.remoting.detection.multicast.MulticastDetector"
name="jboss.remoting:service=Detector,transport=multicast">

<attribute name="BindAddress">localhost</attribute>
attribute name="Port">51055</attribute>
</mbean>
7.
Manually START the Siemens HPCR Startup Windows Service from Service Control
Manager.
8.
Invoke TaskManager, add column Thread Count, and observe the thread count reaches
at least 230 for vocalos_native_ for about 30 seconds. Then proceed to next step.
A31003-S5020-S200-1-7620, July 2004

6-3
5458install.fm

9.
Start Media Server System Administration via Start > Programs > HiPath OpenScape >
HiPath OpenScape Media Server > Media Server Administration.
10. If asked, login as <osinstaller> with password and local domain.

11. Click System Administration and Connectivity (left side). Siemens SIP Lines 1 to 30
should be displayed. If yes, you can proceed. If not, contact customer support.
12. Change the Startup type of the Siemens HPCR Startup Windows Service from Manual
to Automatic.
13. Make sure all Siemens HPCR services are started.
6-4
A31003-S5020-S200-1-7620, July 2004

5458ICenter.fm
Configuring the Media Server
Setting Content Expiration Dates in IIS
Use the procedures in this chapter to integrate Media Server with HiPath OpenScape:
Set content expiration dates in IIS (Section 7.1)
Enter HiPath OpenScape System Information (Section 7.2)
Import subscribers from HiPath OpenScape into Media Server (Section 7.3).
In Media Server, configure the subscribers that have been imported (Section 7.4).
7.1
Setting Content Expiration Dates in IIS
Two folders, SystemURLs and Applications, under the IIS directory need to have their content
expiration dates set so that the .wav files are cached in the Vocalocity browser.
1.
From the desktop, right-click My Computer, then select Manage.
2.
Double-click Services and Applications, then expand IIS->Default Web Site->Siemens>IWR.
3.
From the right pane, locate and right-click SystemURLs, then select Properties.
4.
Select the HTTP Headers tab.
5.
Click the Enable Content Expiration checkbox.
A31003-S5020-S200-1-7620, July 2004

7-1
5458ICenter.fm

Entering HiPath OpenScape System Information
6.
Select Expire on, then set the Expire on date to July 15, 2020.
7.
Click Apply, then OK.
8.
From the right pane, locate and right-click Applications, then select Properties.
9.
Select the HTTP Headers tab.
10. Click the Enable Content Expiration checkbox.

11. Select Expire on, then set the Expire on date to July 15, 2020.
12. Click Apply, then OK.
13. Close this window.
7.2
Entering HiPath OpenScape System Information
1.
Click Start->Programs->HiPath OpenScape->Hipath OpenScape Media Server->Media Server Administration.
2.
If prompted, logon with the <osinstaller> name and password and enter the FQDN of the
child domain.
3.
Configure the HiPath OpenScape user logon accounts for Media Server as follows:
7-2
A31003-S5020-S200-1-7620, July 2004

5458ICenter.fm
4.

Importing Subscribers into Media Server
Click System Administration, then HiPath OpenScape (on the left side), then click
the Certificate tab.You will see a certificate.
Click Modify (on right side).
Check the Selected box, then click Update.
Under the Selected column, verify that you see True.
Enter information about HiPath OpenScape system
Click the System tab.
Fill in the following three fields:
SystemID for HiPath OpenScape Integration HiPath OpenScape system

name.
Media Server Service Account Name SiemensCR account name created by

EPT e.g. PeachSiemensCR
Media Server Service Accounts Domain FQDN for the HiPath OpenScape
system.
Click Submit.
5.
Reboot Media Server system.
6.
Restart Serviceability Broker on HiPath OpenScape Core.
7.3
There are three types of subscribers in Media Server.

HiPath OpenScape Users - These users can use all HiPath OpenScape features. These subscribers must be imported from a HiPath OpenScape system.
Interaction Center Subscribers - These subscribers can use the Interaction Center features,
log on to Media Server and check their Inbox messages and appointments. You can import
these subscribers or create them in Media Server.
Normal Subscriber - This is the basic subscriber, who cannot log on to Media Server but can
call in. Callers can transfer to these subscribers by DTMF name dialing or by entering their extensions. These subscribers are used by the Auto-Attendant applet, which allows callers to
transfer to a subscribers extension by entering the subscribers name.
A31003-S5020-S200-1-7620, July 2004

7-3
5458ICenter.fm

7.3.1
Importing HiPath OpenScape Subscribers
HiPath OpenScape subscribers are imported automatically, assuming the following pre-condition:
The Siemens HPCR Startup Windows Service must be successfully registered with the HiPath OpenScape Serviceability Service.
7.3.2
Importing Non-HiPath OpenScape Subscribers
Non-HiPath OpenScape subscribers can be imported from Active Directory or from the Exchange 2000/2003 server.
7.3.2.1
Importing from the Active Directory
1.
If you want to include the Exchange Super User in the Media Server database.
2.
If you want to include Windows users that are not HiPath OpenScape subscribers for the
sole purpose of being able to reach these users via the DTMF AA application.
3.
Note that users from the Active Directory must have an entry in the Telephone Number field
in order to be imported to Media Server
7.3.2.2
Importing from Exchange
Import from the Exchange 2000/2003 server if the HiPath OpenScape Administrator gave full
Exchange 2000/2003 mailbox and public store privileges to an HiPath OpenScape subscriber:
1.
Select System Administration and click Import.
2.
Select the server that you want to import subscribers from or configure a new server as
follows:
7-4
Click Create New Server.
Enter name of Exchange server.
From dropdown menu, select Exchange 2000/2003 for Exchange Server type.
Click Create.
Click the General tab. In the address field, enter the domain name where the SiemensIC user belongs. Select Logon Required. For user name, enter <domain
Name>\<osinstaller>. Enter the password for <osinstaller>.
Click the Mapping tab, then select Mail from right side. Click the < icon for the Extension field. Mail will now appear in this field.
A31003-S5020-S200-1-7620, July 2004

5458ICenter.fm

Preparing Media Server
Click the Filter tab, use filters to select which users should be imported to the Media
Server database.
Click the Extension tab, then enter the conversion information for extensions or click
No conversion on extension field. The Extension field must map to a correct LDAP
property when imported. For example, you could start with the number 8-492-2525,
add8 as a prefix, take 4 digits from the right, and append 0 as a suffix. The result
would be 8-25250.
Click the Schedule tab, configure the frequency with which the databases will be synchronized and the time at which the synchronization will start.
Click Submit to complete the configuration of the import server.
3.
Click Import (on left side).
4.
Click <servername>.
5.
Click Import (on right side).
6.
Select an import option:
Add only the new subscribers
Re-import subscribers
Delete previously imported subscribers
Synchronize the Media Server and Exchange databases
7.
Click Import (on right side).
8.
This may take several minutes. Click View Log to see if successful.
7.4
The steps described in this section are just to make sure Media Server works with Exchange
2000/2003. Before starting these steps, logon to Windows with the <osinstaller> account
name and password.
7.4.1
Entering the Interaction Center Super User Credentials
The Super User is required so that Media Server can access individual subscriber mailbox information without knowing the subscribers account credentials. The password is stored in the
Media Server database and is encrypted.
The Super User in this case is that Windows Domain User that was created and was given full
mailbox and public store privileges.
A31003-S5020-S200-1-7620, July 2004

7-5
5458ICenter.fm

Click the Interaction Center tab at the top of the screen. Click Exchange Super User in the
left column.
For these fields:
Exchange Server Name - Enter the server name + FQDN of the Exchange 2000/2003
Server you want Media Server to integrate with. For example, the exchange server named
padres is in the domain "big.foot.com". Therefore, the entry in this field is padres.big.foot.com.
User Name - Enter SiemensIC.
User Password - Enter the password for SiemensIC.
User Domain Name - Enter FQDN where SiemensIC user belongs.
After you click Submit, Media Server will perform a Read-Property operation on a subscribers mailbox whose server name and domain matches the Super Users. This ensures that the
Super User credentials and privileges are correct.
You can enter as many Super Users as needed for every Exchange 2000/2003 Server that you
will integrate with.
>
It is mandatory that you import the Super User from the Active Directory.
To change the domain name, user name or user password for any of the Super Users, select
the Edit Super User tab. Click the Finished tab once done.
.
7-6
A31003-S5020-S200-1-7620, July 2004

5458ICenter.fm
7.4.2

Configuring the Front-End Server
For security and ease-of-use, Microsoft recommends a front-end/back-end server topology for
organizations with multiple Exchange servers and users who access e-mail via Outlook Web
Access. There can be more than one front-end server.
1.
From the Interaction Center, click Front-End Servers on the left.
2.
Enter the FQDN of the Front-End Server. Also select one or more Back-End Servers serviced by this Front-End Server, then click Submit. Refer to Section 3.9, Front-End and
Back-End Servers.
7.4.3
Interaction Center Folders for Individual Subscribers
There are three menus for this function:
Create Folders
Status
Errors
7.4.3.1
Creating Folders
To enable the Interaction Center features for a subscriber, Media Server must create the Interaction Center folders in its Exchange 2000/2003 mailbox.
1.
Click Subscriber Folder, then select an Exchange 2000/2003 server from the dropdown
list, then click Get Subscribers.
2.
Select one or more subscribers to create Interaction Folders. Once you have done that,
click Create Folders. The selected subscribers will then be removed from this list.
A31003-S5020-S200-1-7620, July 2004

7-7
5458ICenter.fm

>
3.
A prerequisite to this operation is a Windows Service named SubsrrCreateFolder.exe. This Service automatically gets started by Media Server and runs in the
background.
Check status of operation by clicking Status. Then select an Exchange 2000/2003 Server
from the dropdown list, then click Get Status/Refresh. You will see two status list boxes.
The upper box contains the list of subscribers whose folder-creation operation has been
completed. The lower box contains subscribers whose folder-creation is in progress.
To refresh the list boxes, click Get Status/Refresh.
7-8
A31003-S5020-S200-1-7620, July 2004

5458ICenter.fm
4.

When Media Server finishes creating Interaction Center folders for a subscriber, this subscriber will appear in the upper list box. You may need to click Get Status/Refresh to update these list boxes.
A31003-S5020-S200-1-7620, July 2004

7-9
5458ICenter.fm

7.4.3.2
Checking for Errors
Click Errors to show any errors in the create-folder operation for each subscriber. In the example here, there was no superuser defined for this subscriber.
Once the error is corrected, you can retry to complete the create-folder operation for the subscriber by clicking Retry.
7-10
A31003-S5020-S200-1-7620, July 2004

5458ICenter.fm
7.4.4

Subscriber Profile
Click Subscriber Profile to view the profile of each imported subscriber.

Click the first letter of the last name or * for all names.
The envelope icon indicates that the Interaction feature is enabled for this subscriber. The X
icon indicates that the Interaction Center is not enabled.
If you wish to enable the Interaction Center for a subscriber, go to Section 7.4.3.1 on page 7-7.
To view the properties for a subscriber, click the subscribers name, then click View.
The profile is displayed. These fields are read-only because these subscribers were imported
into the Media Server database from the HiPath OpenScape database. It is only in the HiPath
OpenScape database one should add, change, or delete. Any of these database actions will
be propagated from HiPath OpenScape to Media Server. You cannot delete Subscribers that
were imported from HiPath OpenScape.
A31003-S5020-S200-1-7620, July 2004
7-11
5458ICenter.fm

7-12
A31003-S5020-S200-1-7620, July 2004

5458ICenter.fm
7.5

Managing Default Documents
Managing Default Documents
Interaction Center subscribers are supplied with a set of default HTML documents that provide
greetings for their callers. Subscribers can customize these greetings by modifying the documents. When a subscriber wishes to revert to the default version of a greeting, you can use this
page to restore the default document.
1.
From the Interaction Center, click Default Documents.
2.
Depending on the language, select the default document you wish to recover, then click
Download. You can then e-mail the document to users who need it or place it on the network where users can access it.
7.6
Saving a Recovery Image (Optional)
To assist in recovery from a catastrophic failure, you may want to create a recovery image of
your completed installation at this time. To do this, you need to use a tool such as Norton Ghost
or PowerQuest Drive Image. Save the recovery image to CD-ROMs or other secure media. If
needed, you can restore your system from the recovery image. Refer to Section 10.5, Restoring Media Server Software for more details.
A31003-S5020-S200-1-7620, July 2004

7-13
5458ICenter.fm

Saving a Recovery Image (Optional)
7-14
A31003-S5020-S200-1-7620, July 2004

5458crinos.fm
Creating Applications in Media Server
CRDirectApp
Create two applications in Media Server. They are configured for testing purposes only to make
sure that HiPath OpenScape and Media Server are working properly.
>
8.1
Refer to the Administration Guide for details on system administration and creating
custom applications.
CRDirectApp
Go to Media Server Administration.

1.
Click Application Builder.
2.
Click Interaction Center (on left side).
3.
Click Create New Application.
4.
In the Select an application category field, select Subscriber Access from the drop
down menu.
5.
In the Name field, change to CRDirectApp.
6.
Select the appropriate language from the drop-down list, then click Submit.
8.2
CRForwardApp
1.
From Media Server Administration, click Application Builder.
2.
Click Interaction Center (on left side).
3.
Click Create New Application.
4.
In the Select an application category field, select Forward Access from the drop down
menu.
5.
In the Name field, change to CRForwardApp.
6.
Select the appropriate language from the drop-down list, then click Submit.
A31003-S5020-S200-1-7620, July 2004

8-1
5458crinos.fm

CRForwardApp
8-2
A31003-S5020-S200-1-7620, July 2004

5458testing.fm
Testing Media Server with HiPath OpenScape
Interoperability Tests
This chapter describes simple tests to verify that Media Server works with HiPath OpenScape.
9.1
Interoperability Tests
1.
To run these tests, logon to Media Server as <osinstaller>.
2.
In Media Server Administration, click HiPath OpenScape on left side.
3.
Click Interoperability tab.
4.
Click Run Test for each test.
5.
If status is Pass, continue with next test until you have completed all tests.
6.
If status is Fail, click Detail for detailed error message or click Help for troubleshooting
hints.
A31003-S5020-S200-1-7620, July 2004

9-1
5458testing.fm

Diagnostic Tests
9.2
Diagnostic Tests
1.
Click Interaction Center from Media Server.
2.
Click Diagnostics.
3.
Select the appropriate Exchange Server, then click Get Subscribers.
4.
Select all the subscribers, then click Run Test.
5.
To see the results, click Show Report.
9-2
A31003-S5020-S200-1-7620, July 2004

5458testing.fm

Diagnostic Tests
6.
Select appropriate Exchange Server and Show only subscribers with test status = fail.
Then click Get Status/Report.
7.
Select a failed subscriber, if any, then click Get Details.
A31003-S5020-S200-1-7620, July 2004

9-3
5458testing.fm

Testing Direct Call to the Media Server
8.
9.3
Read the information in the bottom window to resolve problem. If applicable, click Additional Help to get more information.
Testing Direct Call to the Media Server
1.
Open a Windows Messenger instance on a client.
2.
Click Start a voice conversation.
3.
Click the Other tab.
4.
Enter sip:abc@FQDN_of_the_Media_Server. For example, if the FQDN is yankees.big.boss.com, then enter sip:abc@yankees.big.boss.com.
5.
Media Server should accept the call. This call is routed directly to Media Server through
LC via the LC Static Routing parameter.
6.
If the call does not work, make sure that the Siemens TSP is installed (Control Panel>Phones&Modem->Advanced).
7.
Continue to next section when successful.
9-4
A31003-S5020-S200-1-7620, July 2004

5458testing.fm
9.4

Routing Through HiPath OpenScape
Routing Through HiPath OpenScape
1.
Sign on to a client with Windows Messenger.
2.
From the clients Windows Messenger portal, click Start a voice conversation.
3.
Click the Other tab.
4.
On the e-mail address field, enter sip:CRDirect@<domain_name_of_Media_Server>.

For example, if the domain name is big.boss.com, then enter sip:CRDirect@big.boss.com.
5.
Media Server should accept the call. This call is routed through LC and HiPath OpenScape.
6.
If the call does not work,

a) Make sure that the Siemens TSP is installed (Control Panel->Phones&Modem->Advanced).
b) Make sure an application exists for CRDirectApp in the Media Server.
c)
Check that the CRDirectApp user is in the Active Directory, is an LC user and a HiPath
OpenScape user
d) Check that the domain name is spelled correctly throughout the route (i.e. in the AD,
LC and HiPath OpenScape configurations).
e) Check that the phone numbers are also correct and conform to the numbering plan for
the site.
9.5
HiPath OpenScape Voice Portal
If all tests passed, then you have successfully installed the Media Server application on the Media Server.
Now, configure the HiPath OpenScape and Media Server systems per the customers actual
requirements - refer to the online Admin Help and the Administration Guide.
A31003-S5020-S200-1-7620, July 2004

9-5
5458testing.fm

HiPath OpenScape Voice Portal
9-6
A31003-S5020-S200-1-7620, July 2004

10
5458imaint.fm
Maintenance Procedures
Uninstalling Media Server
This chapter contains procedures that you may need once Media Server has been installed.
10.1
Uninstalling Media Server
10.1.1
Uninstalling the Media Server Application Only
Open the Service Control Manager.
Change the startup type of the Siemens HPCR Startup Windows Service from AUTOMATIC to MANUAL.
Restart the Media Server.
From Add/Remove programs, remove HiPath OpenScape Media Server. If you wish to
preserve your database, please select Save Database option.
To install a new version of Media Server, please go to Chapter 6, Installing and Validating
Media Server Software.
10.1.2
Uninstalling the VocalOS Browser and Media Server Application
Steps to uninstall VocalOS
Open the Service Control Manager.
Change the startup type of the Siemens HPCR Startup Windows Service from AUTOMATIC to MANUAL.
From the Add/remove programs, remove VocalOS.
In C:\Program Files\Siemens, check if the Media Server Voice Browser folder is removed.
If still there, delete it manually.
Steps to install Media Server
From Add/Remove programs, remove HiPath OpenScape Media Server. If you wish to
preserve your database, please select Save Database option.
Go to Section 5.7, Siemens Voice Browser Software Upgrade Instructions to install the
VocalOS, then to Chapter 6, Installing and Validating Media Server Software.
A31003-S5020-S200-1-7620, July 2004

10-1
5458imaint.fm
Reinstalling Media Server
10.2
Reinstalling Media Server
Note the following cases:
To reinstall Media Server Application only (without VocalOS) please go to Chapter 6, Installing and Validating Media Server Software.
To reinstall both Media Server Application and VocalOS, go to Section 5.7, Siemens Voice
Browser Software Upgrade Instructions to install the VocalOS, then to Chapter 6, Installing and Validating Media Server Software.
For the complete reinstall (Media Server Application, VocalOS and third party SW) please
start with Chapter 5, Installing Third-Party Software.
10.3
Backing Up and Restoring Media Server User Data
User data is located in several places on the Media Server. This section describes how to backup and restore each of those areas.
10.3.1
Backing Up and Restoring Databases
You can use the Database Backup Utility described in this section to back up and restore database files. Two conditions are necessary:
MS SQL Server must be running.
Traffic on your system should be low. (Run this utility after-hours.)
To use the Backup and Restore utility (DBUtil.exe):

1.
From the Start Menu, select Programs->Siemens HiPath OpenScape->HiPath OpenScape Media Server, then Database Backup Utility.
You can choose to backup or restore the Main Database or the Report Database.
2.
To back up a database, browse to the location where you want to store the backed-up file
and enter a file name, for example c:\temp\mybackup.bak then click Backup.
To restore the database, browse to the location where the file is stored. Select it, and then
click Restore.
10.3.2
Backing up and Restoring Customer-Created Applications
Each application created in the Media Server has a corresponding folder on the Server. The
following process backs up the folders for the customer-created applications.
Identify the names of all customer-created applications by doing the following:
10-2
Open the Services Management from the Control Panel.

A31003-S5020-S200-1-7620, July 2004
5458imaint.fm
Start the MSSQL$IWR service (if not already started).
Open the Media Server System Administrator via the Start->Programs->Siemens HiPath OpenScape->HiPath OpenScape Media Server->Media Server Administration.
Go to the Application Builder and click Custom.
Write down all the application names of the applications listed under Application
Name.
Click Word Web.
Write down all the application names of the applications listed under Application
Name.
To save the application folder of the user created application, do the following:
Using Windows Explorer, go to the folder C:\Program Files\Siemens\IWR\www\IWR\Applications.
For each of the application names that were written down, copy each of the folders with
that same name. Make sure all the files and folders beneath it are copied too.
Save the folders to a safe location such as a network server that is not on the Media
Server machine.
Save any additional files (.wav, .xml, .vxml, etc.) not stored in the application folder that are
used by the application. To know if an application uses additional files, do the following:
Under Custom or Word Web, click on the application name.
Click View.
Click a step.
Click Step Settings (the magnify glass icon).
Scroll to the bottom of the webpage.
Click the Options tab.
See if there is a file listed in URL. If so, locate the file. Save the path to the file and then
save file to a safe location. If the file is already located in a safe location, then there is
no need to save it again. But, save the path to the safe location so that later that connection to the location can be restored and verified.
Do this for each step of the application.
Following process is used to restore backed up applications
Go to the safe location where the customer-created application folders are stored.
A31003-S5020-S200-1-7620, July 2004

10-3
5458imaint.fm
Copy each of the customer-created application folders (and all files and folders beneath it)
into the Applications folder located at C:\Program Files\Siemens\IWR\www\IWR\Applications.
Note: Do NOT overwrite anything in the Application folder on the new machine. This copy
operation restores all customer-created application folders without disturbing the folders
that were installed as a part of Media Server. If the copy operation advises you that a folder
already exists on the target, or asks for permission to overwrite an existing folder or file,
answer No.
Restore any additional files to their original location (with the exact path that they had originally). For the files that were already saved to a safe location, make sure the connection
to that location is restored.
To verify that the applications were copied properly, open the System Administrator Application (Start->Programs->Siemens HiPath OpenScape->HiPath OpenScape Media
Server->Media Server Administration). Click Application Builder. Click either Custom
or Word Web. The applications should be there. View the steps and all the properties of
each application, including any media files (.HTML, .WAV, .TXT, etc.) associated with each
application.
10.3.3
Backing Up and Restoring Report Files
The Media Server contains reports that the user generates. The following process backs up the
report files.
Open the Windows Explorer.
Go to <IWR home directory>\www\IWR\SA\Report\ReportFiles.
Copy the report files that you want to save to a safe location such as a network server.
The following process restores the backed up report files.
Go to the safe location where you stored the report files.
Copy all the files back to <IWR home directory>\www\IWR\SA\Report\ReportFiles.
To verify that the report files were copied properly, open the System Administrator Application:
Click Start->Programs->Siemens HiPath OpenScape->HiPath OpenScape Media

Server->Media Server Administration).
Click System Administrator->Reports.
Click Report Jobs. The report files should be there.
For each report, click View to open the report file.
10-4
A31003-S5020-S200-1-7620, July 2004

5458imaint.fm
10.4
Media Server Dependability
Media Server Dependability
The Media Server includes a Dependability module (Siemens HPCR Startup Windows Service) whose purpose is to monitor system health and take corrective action when necessary
to keep the system in stable running condition. Customers should be aware that this module is
configured to automatically restart system services under severe conditions such as the excessive use of memory or CPU over extended periods of time.
10.5
Restoring Media Server Software
This chapter describes how to restore your complete Media Server system after a serious failure (a disk crash, for example) that renders the system unusable. To accomplish a full recovery,
you will need a recent backup of your user data as described in Section 10.3, Backing Up and
Restoring Media Server User Data.
10.5.1
Recovery if You Have Recovery Image
If you created a recovery image of your newly installed system perform the following steps:
1.
Restore your system from the recovery image per the instructions provided by your imaging software.
2.
If the password for the HiPath OpenScape core account changed, then
a) Click Start->Programs->Siemens HiPath OpenScape->HiPath OpenScape Media
Server->Password Configuration (to start the Password Configuration tool).
b) Enter the HiPath OpenScape core account name in the Account name field.
c)
Enter the password in both the New Password and Confirm Password fields
d) Click Submit. When the tool has finished configuring the account, a popup message
box will appear indicating success or failure.
e) Configure this account with local admin rights.
f)
3.
Restart Windows.
Restore your backed-up user data as described in Section 10.3.1 and Section 10.3.2.
A31003-S5020-S200-1-7620, July 2004

10-5
5458imaint.fm
Restoring Media Server Software
10.5.2
Recovery Without Recovery Image
If you do not have a recovery image, perform the following steps.

1.
Begin with a clean formatted hard disk. The Windows 2000 Advanced Server installation
program can do this for you.
2.
Re-install the Windows 2000 operating system, Service Pack 4, other Windows updates as
described in Chapter 3 and all third-party software as described in Chapter 5. The thirdparty software is found in the Third Party Software CD.
3.
Perform all the steps in Chapter 6 of this document to install and validate the Media Server
software.
4.
Restore your backed-up user data as described in Section 10.3.1 and Section 10.3.2.
10-6
A31003-S5020-S200-1-7620, July 2004

11
5458trbl.fm
Troubleshooting
Siemens TAPI Monitor
Troubleshooting
This chapter describes the tools to troubleshoot problems with Media Server.
11.1
The Siemens Telephone Application Programming Interface (TAPI) Monitor monitors activity on
the telephony lines at the TAPI level. Use this tool to monitor all TAPI lines on the Media Server
server. This can tell you the current state of the lines (idle, offering, ringing, connected, etc.)
and any digits received on the line.
The TAPI Monitor is installed in <Media Server installation directory>\Bin.
The Tapi Lines window shows all installed TAPI lines. For each line, you see the line number
(TAPI line numbers start at zero), the current line status, and the current call status.
UN
Unopen or unable to open
OU
Open but status yet unknown
OS
Open but out of service
IS
Open and in service
Table 11-1
Line Status Values in TAPI Monitor
Idle
No call present
Offering
Incoming call present, not yet accepted
Accept
Incoming call accepted, not yet connected
Dial Tone
Outgoing call off hook and receiving dial tone
Dialing
Outgoing call dialing
Ringback
Outgoing call receiving ringback signal
Busy
Outgoing call receiving busy signal
Special
Vendor-specific
Connect
Call (incoming or outgoing) is connected
Proceed
Outgoing call proceeding through network
Hold
Call is on hold
Conf
Call is in a conference
HoldConf
Call is on hold pending a conference
HoldXfer
Call is on hold pending a transfer
Table 11-2
Call Status values in TAPI Monitor
A31003-S5020-S200-1-7620, July 2004

11-1
5458trbl.fm
Troubleshooting
Disconn
Call has disconnected awaiting idle indication
Unknown
None of the above
Table 11-2
Call Status values in TAPI Monitor
If the line is busy (i.e. the call status is not Idle), information about the call appears next to the
call status. The following information is displayed if available:
Call direction
Call origin
Call reason
Consultation flag
Called/redirecting number
Calling/connected number.
Line
Call Status
Status
Description
IS
Connect <dir-61058:x77022
Incoming call from internal extension 77022 by directly dialing 61058
IS
Connect <bsy-65510:t
Incoming call from an external trunk (with no caller

ID) by busy forwarding through extension 65510
IS
Connect <rna65510:t4084922000
Incoming call from an external trunk (caller ID 408492-2000) by ring-no-answer forwarding through
extension 65510.
IS
Connect <unc-65510:x77192c
Incoming consultation call from internal extension

77192 by unconditionally forwarding through extension 65510. If 77192 hangs up, the party held
by 77192 will connect and the display will change
accordingly.
IS
Ringback -dir>
Outgoing call (always direct), is ringing an unidentified party.
Table 11-3
11.1.1
Examples of TAPI Monitor Display
Other Features of the TAPI Monitor
The Screen Log window, when active, displays a detailed TAPI trace of a single selected line.
11-2
A31003-S5020-S200-1-7620, July 2004

5458trbl.fm
Troubleshooting
System Verification Application
Logging Options controls how information appears in the Screen Log. To select a line to trace,
double click that line in the Tapi Lines window, or select the line and select Log to Screen. If
you select Auto Track, the line is automatically tracked if it is the only non-idle line. The line
being tracked appears in red.
The Show Digit Values button allows display of DTMF/Keypad digit values in the screen log.
It is password protected.
11.2
Media Server is shipped with sample applications that perform system verification:
SystemVerificationTest
TestTextToSpeech
TestSpeechRecognition
You can assign these applications to the routing table and call them to verify your Media Server
installation.
A31003-S5020-S200-1-7620, July 2004

11-3
5458trbl.fm
Troubleshooting
11-4
A31003-S5020-S200-1-7620, July 2004

5458AppC.fm
Miscellaneous
Updating the Number of Lines When the License Changes
Miscellaneous
A.1
The number of lines that are created in the telephony subsystem need to be equal to the
SIP_INTERACTION_SESSIONS count in the license. If there is a change in the license anytime after the installation of the HiPath OpenScape Media Server, do the following to update
the number of lines:
1.
In the Media Server Administration, click System AdministrationHiPath OpenScapeLicense.
2.
Click Update.
3.
Reboot the PC.
A31003-S5020-S200-1-7620, July 2004

A-1
5458AppC.fm
Miscellaneous
A-2
A31003-S5020-S200-1-7620, July 2004

5458IX.fm
Index
Index
B
Backing Up and Restoring Report Files 10-4
C
Certificate
Requesting 3-4
Checking for Errors 7-10
Configuring
Front-End Server 7-7
Content Expiration Dates 7-1
CRDirectApp 8-1
Creating Folders 7-7
CRForwardApp 8-1
D
Default Documents 7-13
dependability 10-5
Destination Target 4-3
Diagnostic Tests 9-2
diagnostics 11-1
Disabling Restrict CD-ROM Access to Locally Logged-on User Only Parameter 3-3
F
Front-End and Back-End Servers 3-3
Front-End Server 7-7
H
Hardware Requirements 2-1
HiPath OpenScape License 4-3
HiPath OpenScape RTC Config Tool 4-1
I
IIS WebDAV 3-3
Importing HiPath OpenScape Subscribers 74
Importing Non-HiPath OpenScape Subscribers 7-4
Installation Overview 2-3
Installing
Package 1 5-1
Package 2 5-1
Package 3 5-2
installing HiPath OpenScape Media Server
software 6-1
Interaction Center Folders 7-7
Checking for Errors 7-10
Creating 7-7
Managing Default Documents 7-13
Subscriber Profile 7-11
Interaction Center Super User Credentials 75
Internet Explorer 6.0, installing 3-2
Internet Information Services 3-1
Interoperability Tests 9-1
IPSec settings 4-4
M
maintenance procedures 10-1
Media Server Dependability 10-5
R
Removing Terminal Services 3-2
Requesting a Certificate 3-4
Requirements
Hardware 2-1
Software 2-2
restart of system services 10-5
S
Server Information 3-3
Siemens TAPI Monitor 11-1
Siemens Voice Browser (Vocalocity) 5-4
SMTP service 3-1
Software Requirements 2-2
Speechworks OSR Service 5-2
Subscriber Profile 7-11
System Verification Application 11-3
T
TAPI monitor 11-1
A31003-S5020-S200-1-7620, July 2004

Z-1
5458IX.fm
Index
troubleshooting 11-1
U
Uninstalling the Media Server Application
Only 10-1
Uninstalling the VocalOS Browser and Media
Server Application 10-1
V
virus scan software, installing 3-2
W
weekly restart of system services 10-5
Windows 2000 Server, installing 3-1
Windows 2000 service pack 4, installing 3-1
Windows Script Host 5.6 3-2
WTE Service restart 10-5
Z-2
A31003-S5020-S200-1-7620, July 2004

www.siemens.com/hipath
The information provided in this document contains merely general descriptions or characteristics of performance which in case of actual use do
not always apply as described or which may change as a result of further
development of the products.
An obligation to provide the respective characteristics shall only exist if
expressly agreed in the terms of contract.
*1PA31003-S5020-S200-1-7620*
Siemens AG 2004 Information and Communication

Networks Hofmannstrae 51 D-81359 Mnchen, Germany
Reference No.: A31003-S5020-S200-1-7620
Printed in the Federal Republic of Germany.
Subject to availability. Right of modification reserved.

OpenScape V2.0 Media Server Installation Guide

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

OpenScape V2.0 Media Server Installation Guide

Încărcat de

Drepturi de autor:

Formate disponibile

HiPath OpenScape Media Server

The information provided in this document contains merely general descriptions or

1 About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3 Installing Windows Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4 Pre-Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

A31003-S5020-S200-1-7620, July 2004

Nur fr den internen Gebrauch

5.5 Validating the Locale in the Registry. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

A31003-S5020-S200-1-7620, July 2004

11.1 Siemens TAPI Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1

A31003-S5020-S200-1-7620, July 2004

Nur fr den internen Gebrauch

A31003-S5020-S200-1-7620, July 2004

Nur fr den internen Gebrauch

About This Guide

Who Should Use This Guide

HiPath OpenScape Media Server Administration Guide A31003-S5020-A600

Installation Guide A31003-S5020-S100

Administration Guide A31003-S5020-A900

User Guide A31003-S5020-A100

Project Planning Guide A31003-S5020-A300

Title: HiPath OpenScape Media Server V2.0, Installation Guide

Order Number: A31003-S5020-S200-1-7620

A31003-S5020-S200-1-7620, July 2004

About This Guide

Nur fr den internen Gebrauch

A31003-S5020-S200-1-7620, July 2004

Nur fr den internen Gebrauch

The installation consists of

Third party software

HiPath OpenScape Media Server application

SIP-based platform - HiPath OpenScape

2.0 GHz Pentium III or higher

At least 10 GB of free space

One 3.5" floppy disk drive (optional)

One CD-ROM, 4x minimum

A31003-S5020-S200-1-7620, July 2004

Nur fr den internen Gebrauch

NIC: 10/100 MB Ethernet

Mouse or other compatible pointing device

The three basic components are:

Third-party software as described in Chapter 5

HiPath OpenScape Media Server software as described in Chapter 6

a Domain Controller or DNS server

running any database program like MS SQL Server, Informix, etc.

running any significant software program like Microsoft Exchange program

A31003-S5020-S200-1-7620, July 2004

Core software for the HiPath OpenScape Media Server;

OpenScape XX 3rd Party Software CD contains 3rd party software to be installed

Service Pack CD contains HiPath OpenScape Service Packs and documentation.

Be sure to verify the hardware/software requirements mentioned in Section 2.2 and

Install Windows components

Install Virus scan software (optional)

Third-party software components

HiPath OpenScape Media Server software and validate

Configure Media Server for HiPath OpenScape

Configure the HiPath OpenScape Media Server:

A31003-S5020-S200-1-7620, July 2004

Nur fr den internen Gebrauch

Import subscribers into Media Server

Prepare Media Server

Enable SiemensIC super user credentials

Create Interaction Center folders for Individual Subscribers

Verify subscriber profiles