um4730 installation guide

Liability Disclaimer

NEC Unified Solutions, Inc. reserves the right to change the specifications, functions, orfeatures at any time without notice.

NEC Infrontia Inc. has prepared this document for the exclusive use of its employeesand customers. The information contained herein is the property of NEC Infrontia Inc.and shall not be reproduced without prior written approval from NEC Infrontia Inc.

NEC Unified Solutions, Inc. has prepared this document for use by its employees andcustomers. The information contained herein is the property of NEC Unified Solutions,Inc. and shall not be reproduced without prior written approval of NEC UnifiedSolutions, Inc. Dterm, NEAX and UNIVERGE are registered trademarks of NECCorporation and Electra Elite is a registered trademark of NEC America, Inc. Windows isa registered trademark of Microsoft Corporation. AT&T is a registered trademark ofAT&T Wireless Services, Inc. Pentium is a trademark or registered trademark of IntelCorporation or its subsidiaries in the United States and other countries. AutoTalk is atrademark of Uniden America Corporation. ViewCall and ViewMail are registeredtrademarks of Active Voice, LLC.

© 2009 NEC Infrontia Inc.

MS-DOS, Microsoft, and Windows are trademarks of Microsoft Corporation.All other brand or product names are or may be trademarks or registered trademarks

of, and are used to identify products or services of, their respective owners. NEC Infrontia, Inc.

6535 N. State Highway 161Irving, TX 75039-2402

Technology Development

ii UNIVERGE UM4730 INSTALLATION GUIDE

■ CONTENTS

CHAPTER 1 Introduction 1About the Messaging System............................................................ 1

About this Guide ......................................................................... 1Third-party Documentation........................................................... 1Web Browser Support .................................................................. 1Document Conventions ................................................................ 1Administration Console Icons........................................................ 3Using the Command Line Interface ................................................ 3Related Documentation................................................................ 4Supported Phone Systems............................................................ 4Site Requirements....................................................................... 4

Web Registration ............................................................................ 5Registering the Product................................................................ 5

To register and validate the messaging system .......................... 5Preparing to Install the Messaging System.......................................... 7

CHAPTER 2 Pre-Installation 9Messaging System Overview............................................................. 9Pre-Installation Checklist................................................................ 10

New System Installation Steps.................................................... 10System Upgrades...................................................................... 10

Configuring the BIOS..................................................................... 11Enabling USB Ports on Dell Computers ......................................... 11

To enable USB ports on Dell Computers ................................... 11Configuring a Dell Mini-Tower Computer BIOS............................... 12

To configure the Dell mini-tower computer BIOS ....................... 12Configuring a Rack-Mounted Dell PowerEdge 2900 Computer .......... 13

Use the following procedure to configure the BIOS on a Rack-Mounted Dell PowerEdge 2900. ................................ 13

To configure the rack-mounted Dell PowerEdge 2900 BIOS......... 13Configuring the Rack-Mounted NEC Express 5800 BIOS.................. 14

To configure the rack-mounted NEC Express 5800 BIOS............. 14

CHAPTER 3 WinSCP and PuTTY 15Overview ..................................................................................... 15

Installing WinSCP...................................................................... 15To install the WinSCP client .................................................... 15

Using WinSCP to Access the Messaging System............................. 16To run WinSCP...................................................................... 16

Installing PuTTY ........................................................................ 17To install the PuTTY application ............................................... 17

Configuring PuTTY..................................................................... 17To configure PuTTY................................................................ 17

Using PuTTY to Access the Maintenance Menu ............................... 18To run PuTTY........................................................................ 18

CONTENTS iii

CHAPTER 4 Building the Messaging System Server 19Overview ..................................................................................... 19

System Components.................................................................. 19System Requirements.................................................................... 20

Minimum System Requirements for 40 or Fewer Ports .................... 20Minimum System Requirements for More than 40 Ports .................. 20System Configuration Steps........................................................ 21

CHAPTER 5 Installing the Messaging System 23Introduction ................................................................................. 23

To install the messaging system.............................................. 23Introducing the Linux Desktop ........................................................ 25

System Status Icon ................................................................... 25

CHAPTER 6 Configuring the Messaging System 27Overview ..................................................................................... 27

Configuring the Network ............................................................ 27To configure the network settings ........................................... 27

Configuring the Messaging System .................................................. 29To configure the messaging system date and time .................... 29To create a new system manager ........................................... 30

Resetting Third-Party Licensing Agreements.................................. 31To reset the third-party licensing agreements .......................... 31

Configuring System Security........................................................... 32Additional Recommended Security Practices.................................. 32

To change the default system manager personal ID .................. 33To set a security code for a system manager ........................... 33To configure a default password ............................................. 33To set maximum times a caller can enter an invalid ID .............. 34

Configuring the E-mail Integration................................................... 35To configure the e-mail integration ......................................... 35

Configuring Subscriber Mailboxes for the E-mail Integration................ 36To set up the default subscriber template for e-mail access ........ 36

Setting Subscriber E-mail Access Options ..................................... 36To set the e-mail access options ............................................. 36To set up an individual subscriber for e-mail access .................. 36

Configuring PMS............................................................................ 38To configure the Property Management System package ............ 38

CHAPTER 7 Configuring the Phone System Integration 41About the Phone System Integration ............................................... 41

Integration Steps ...................................................................... 41Using the Messaging System Software Tools ................................. 41

Configuring the Phone System ........................................................ 42Phone System Configuration Steps .............................................. 42Configuring Pooled Ringing ......................................................... 42

To configure pooled ringing .................................................... 42Connecting the Phone System to the Messaging System..................... 43

Selecting the Phone System Integration ....................................... 43To select the phone system .................................................... 43To assign extensions to the ports ............................................ 43

Using GTDetect............................................................................. 45To run GTDetect ................................................................... 45

UNIVERGE UM4730 INSTALLATION GUIDEiv

Testing the Integration .................................................................. 47Test Requirements .................................................................... 47Test Steps................................................................................ 47

Selecting a Call Transfer Type......................................................... 48Selecting Call Transfer Types ...................................................... 48Configuring Transfer Types......................................................... 48

To configure subscriber call transfer settings ............................ 48To change existing subscriber call transfer settings ................... 49

Changing the Keypad Map.............................................................. 50To change the keypad map .................................................... 50

CHAPTER 8 E-mail Integrations 51Overview ..................................................................................... 51

E-mail Protocols........................................................................ 51System E-mail Authentication Protocols........................................ 52E-mail Integration Configuration ................................................. 52

Configuring the E-mail Server ......................................................... 53Converting Existing Domino E-mail Files for Users ......................... 53

To convert existing e-mail files ............................................... 53Configuring the Messaging System .................................................. 55

To configure the messaging system for e-mail notification ......... 55To configure the e-mail notification template ............................ 56

Configuring Subscriber Mailboxes .................................................... 57Configuring the Default Subscriber Template................................. 57

To set up the default subscriber template ................................ 57Setting Individual Subscriber E-mail Options................................. 57

To set subscriber e-mail access options ................................... 57Setting Individual Subscriber E-mail Notifications .......................... 58

To set subscriber e-mail access options ................................... 58Configuring Individual Subscriber E-mail Reader Settings ............... 58

To set subscriber e-mail access options ................................... 59

CHAPTER 9 Remote Maintenance 61Remote Maintenance Overview ....................................................... 61

Dial-up Access Configuration Steps.............................................. 61Network Access Configuration Steps ............................................ 61

Configuring Dial-up Access ............................................................. 62To configure dial-up networking on a remote computer .............. 62

Configuring TCP/IP on a Remote Computer................................... 63To configure TCP/IP for the remote computer............................ 63

Installing WinSCP and PuTTY .......................................................... 64Installing the Clients.................................................................. 64

To install the WinSCP client on a remote computer .................... 64To install the PuTTY client on a remote computer....................... 64

Connecting to the Messaging System........................................... 64To connect to the messaging system using WinSCP ................... 64

Transferring Files ...................................................................... 65To transfer files using WinSCP................................................. 65

Opening a Terminal Window ....................................................... 65Changing the UNIVERGE UM4730 Admin Password ........................ 65

To change the admin password .............................................. 65Logging Out of the Maintenance Menu and PuTTY .......................... 66

To log off using PuTTY ........................................................... 66

CONTENTS v

CHAPTER 10 Backing Up and Restoring Data 67Backing Up the Messaging System................................................... 67

Types of Backups ...................................................................... 67To immediately backup the messaging system ......................... 67To schedule daily backups ..................................................... 68

Restoring Back Up Files.................................................................. 69To restore back up data ........................................................ 69

APPENDIX A Using the Messaging System 71Sign In and Signing Out of the Desktop............................................ 71

To sign in to the operating system........................................... 71To log off the Linux desktop.................................................... 71

The Administration Console Main Menu ............................................ 72The Administration Console Icons ................................................ 72The Administration Console Main Menu......................................... 73Signing in to the Administration Console....................................... 73

To sign in to the Administration Console ................................... 73Signing Out of the Administration Console .................................... 74

To sign out of the Administration Console ................................. 74Using the Maintenance Menu .......................................................... 75

Accessing the Maintenance Menu................................................. 75To log on to the Maintenance Menu.......................................... 75To remotely log on to the Maintenance Menu ............................ 76To log out of the Maintenance Menu......................................... 76

Using the Administration Console .................................................... 77Using the Administration Console the First Time ............................ 77

To sign in the first time ......................................................... 77Signing In to the Administration Console ...................................... 80

To sign in to the Administration Console .................................. 80To log off the Administration Console ...................................... 80

Stopping the Messaging System Software......................................... 81To stop the messaging system software .................................. 81To stop the messaging system software .................................. 81

Restarting the Messaging System Software....................................... 82To start the messaging system software .................................. 82To start the messaging system software .................................. 82

Using the System Status Icon ......................................................... 83To stop the messaging system on the server............................. 83To start the messaging system at the server............................. 83

Shutdown and Restart the Linux Operating System............................ 84To shut down the Linux operating system ................................ 84To restart the Linux operating system ..................................... 84To shut down Linux from the system tray ................................. 84

APPENDIX B Updating the Messaging System 85Overview ..................................................................................... 85

Migrating Existing Messaging Systems to a New Server .................. 85Updating an Existing Messaging System ....................................... 85

Verifying and Changing Licensing Information ................................... 86Verifying Licensing Information ................................................... 86

To verify license information .................................................. 86Changing Licensing Information .................................................. 86

To change license information ................................................ 86

UNIVERGE UM4730 INSTALLATION GUIDEvi

Adding and Removing Language Packs............................................. 87To install new language packs ................................................ 87

Removing Language Packs ......................................................... 88To remove language packs .................................................... 88

Updating the Messaging System...................................................... 89Downloading and Installing the Update File................................... 89

To download and install updates ............................................. 89Restoring the Database and Voice Messages ..................................... 92

To restore files from disks to the messaging system .................. 92Importing and Exporting Data..................................................... 92

To import or export data ....................................................... 92

APPENDIX C Migrating from AD-40 Messaging Systems 95Migrating Data.............................................................................. 95

Reviewing Migration Methods...................................................... 95Selecting a Migration Method ...................................................... 95Migrating from NEAXMail® AD-64 ............................................... 96

Backing Up OS/2 Data to Disks ....................................................... 97To back up the OS/2 database messages only........................... 97To back up database files to disks ........................................... 97

Backing up OS/2 Database Using a Network Connection ................. 98To back up the OS/2 database messages and log files ................ 98

Backing up OS/2 Data with a Direct Connection............................. 98To back up the OS/2 database with the Online Backup Utility ...... 98To configure the OS/2 FTP server ............................................ 99

Installing Network Protocols .......................................................... 100Network Backup Requirements................................................... 100Direct Connection Backup Requirements...................................... 100

To install network protocols for a network or a direct connection backup ........................................................... 100

To set up Multi-Protocol Transport Service (MPTS) .................... 101To test the network protocols installation ................................ 102

Configuring NEAXMail AD-40 to Log On to a Network ........................ 103Windows Connection with NetBIOS ............................................. 103

To log on to Windows NT with NetBIOS ................................... 103To map a Windows NT network drive ...................................... 103

Automatic Windows Log On ....................................................... 103To automatically log on to Windows NT with NetBIOS................ 103

Configuring a Remote Windows Computer for a Backup..................... 105To configure a Windows 98 or ME Workgroup computer............. 105To set up share-level access for 98 or ME ................................ 105

Windows NT or 2000 Setup ....................................................... 105To configure a NT or 2000 workgroup computer ....................... 105To configure a NT or 2000 user ID and password...................... 106To set up share-level access for NT or 2000............................. 106

Upgrading to New Hardware .......................................................... 107Prerequisites ........................................................................... 107

Upgrading Existing Hardware......................................................... 108Prerequisites ........................................................................... 108

To use an external USB DVD drive.......................................... 108Network Method....................................................................... 108

To use the network to restore data ......................................... 108

CONTENTS vii

APPENDIX D Migrating from AD-64 Messaging Systems 111Overview .................................................................................... 111

The AvBackup Utility................................................................. 111Levels of Backup ...................................................................... 111Types of Backups ..................................................................... 112Backup File Names ................................................................... 112Overriding the File Naming Convention........................................ 112

Backing Up the NEAXMail® AD-64 Messaging System ...................... 113To create a manual backup.................................................... 113

Verifying the AD-64 Back Up File Integrity ....................................... 114To verify the backup file integrity ........................................... 114

Migrating the AD-64 Database and Voice Messages........................... 115To restore the AD-64 back up file to the UM4730 messaging system

115

APPENDIX E Migrating from OS/2 Messaging Systems 117Overview .................................................................................... 117

Requirements .......................................................................... 117Migration Steps........................................................................ 117

Backing Up the OS/2 Database ...................................................... 118To back up the OS/2 database ............................................... 118

Compressing the OS/2 Backup Data ........................................... 119To compress the OS/2 backup data ........................................ 119

Transferring the backup data ..................................................... 119Migrating the Backup Files............................................................. 120

To restore backup data ........................................................ 120

APPENDIX F Migrating from OS/2 Messaging Systems 121Overview .................................................................................... 121

Requirements .......................................................................... 121Migration Configuration Steps .................................................... 121

Configuring a Remote Windows Computer for a Backup ..................... 122Windows NT, 2000, or XP Configuration ...................................... 122

To set up an NT, 2000, or XP workgroup ................................. 122To set up an NT or 2000 user ID and password ........................ 122To set up share-level access for Windows NT, 2000 or XP .......... 122

Configuring the OS/2 NetBIOS to Transfer Files................................ 123Configuring NetBIOS over TCP/IP ............................................... 123

To install network protocols for a NetBIOS backup .................... 123Connecting an OS/2 system to a network .................................... 124

To log on to a Windows network............................................. 124To add a user with network access rights................................. 125To specify the network Primary Domain Controller IP address..... 125To log on to the Windows domain or workgroup using NetBIOS .. 126To map a Windows network drive ........................................... 126

Logging on to Windows Automatically ......................................... 126To automatically log on to Windows using NetBIOS................... 126

Backing Up OS/2 Data .................................................................. 127To backup the OS/2 database ................................................ 127

Compressing the OS/2 Backup Data ........................................... 127To compress the OS/2 backup data ........................................ 127

Transferring the Backup Files......................................................... 128Using FTP to Transfer Files ........................................................ 128

To transfer the backup file using FTP....................................... 128

UNIVERGE UM4730 INSTALLATION GUIDEviii

Using CoSession to transfer files ................................................ 128To set up the OS/2 FTP server ............................................... 128

Migrating to UNIVERGE UM4730..................................................... 130To restore the OS/2 backup to the new messaging system ........ 130

APPENDIX G Installing Expansion Boards 131Expansion Board Overview ............................................................ 131

Supported Voice and Fax Boards ................................................ 131Selecting Slots for Expansion Boards .......................................... 131Installing Boards in the Proper Slot............................................. 131Adding or Replacing Boards ....................................................... 131

To add or replace a board in an existing system ....................... 131D4PCI Series Settings................................................................... 132

To set the D4PCI switch settings ............................................ 132D120JCTLS Series Settings............................................................ 133

Combining with D4PCI Boards.................................................... 133To set the switch settings...................................................... 133To set the power budgeting jumper ........................................ 133

VFX41JCTLS Settings.................................................................... 135To set the switch settings...................................................... 135

APPENDIX H Peripherals and UPS 137Connecting Peripheral Devices and the System Key .......................... 137

Connections for a Dell Computer ................................................ 137Uninterruptible Power Supply......................................................... 138

Front Panel of UPS ................................................................... 138Back Panel of UPS .................................................................... 138Connecting the UPS.................................................................. 139

To install the UPS................................................................. 139Checking the UPS Battery.......................................................... 139UPS controls and lights ............................................................ 139

To check the battery leads .................................................... 139Removing and Replacing the UPS Battery .................................... 139

External Modem........................................................................... 140To set up an external modem ................................................ 140

Index............................................................................ 141

CONTENTS ix

UNIVERGE UM4730 INSTALLATION GUIDEx

1CHAPTER
Introduction
About the Messaging SystemThe messaging system simplifies provides the flexibility to access voice messages by phone or e-mail by managing all types of communications in one place with a universal mailbox, The messaging system can be customized for almost any phone system.

About this GuideThis document contains complete instructions for installing the messaging system. Basic integration information is provide for integrating the messaging system with a phone system. Detailed integration information for various phone systems is available in the Integration Guide.

The Installation disc has a /Documentation/en/PDF folder that contains this document, the System Conversation Guide, the Integration Guide, and the User Guide in PDF format. Online help for the Administration Console (formerly referred to as the Administration Console) is available in the /Documentation/en/HTML folder.

Third-party DocumentationCompliance information for third-party electronic devices is provided in the third-party manufacturer documentation supplied with the messaging system package.

Do not use third-party manufacturer documentation to install, upgrade, or manage the messaging system. You should, however, refer to manufacturer documentation for computer hardware and peripheral equipment.

Web Browser Support The only Browsers supported for this release are Internet Explorer 6.0 and newer and FireFox 2.0 and newer. Other browsers might cause problems when viewing the various messaging system interfaces.

Document ConventionsThe following conventions are used in this document:

● Key names. Names of keys on the keyboard are shown in capital letters. For example ALT, ESC, CTRL, and so on.

When two keys must be pressed simultaneously they are joined by a + sign; for example, ALT+TAB.

● Icon and button names. Names of icons and buttons on the application are shown in bold font. The capitalization matches the user interface. For example, OK, Ok, DELETE, or Delete.

NOTE

The System Administrator Help includes pop-up glossary terms. These words are underlined with a green dashed line. Hover the mouse cursor over the term and the definition appears in a pop-up.

NOTE

Firefox browser—Online help glossary definition pop-ups might be truncated. Go to the glossary to see the complete definition. To return to the previous page, right-click the window and select Back.

CHAPTER 1: INTRODUCTION 1

● User input. Information you are required to type is shown in a distinctive font. For example, type msgorder.

Caution is required when typing a zero (0) or capital-O (O) and a one (1) or a lowercase l. For example, in the following command:

vmctl vmail stop ENTER

● Placeholder text. Variable text that is replaced by specific text is shown in italics between angle brackets. For example,

vm_ctl <action> <service>

where <action> = the command and

<service> = the name of the service.

● Hypertext links. When viewing the Adobe® Acrobat® PDF document, links to other locations within the book and to external Internet links appear in blue. Click a link to go to the referenced topic, page, or URL.

● Notes, cautions, and warnings. Text for notes, cautions, and warnings appear as shown:

● Procedural Icons. Different tools can be used to configure the messaging system:

■ Administration Console - Web application for system managers.

■ Mailbox Manager - Web application for subscribers. to read e-mail

■ Phone - your touchtone phone.

■ Maintenance Menu - an SSH tool.

Procedures are identified with an icon to indicate which tool is used:

NOTE

When using the command line prompt, always press the ENTER key after typing a command.

NOTE

Notes provide additional information to supplement the main text. A note provides helpful information, but is not essential to understanding the current topic.

CAUTION!

Cautions advise you that failure to avoid or to take the specified action might lead to unwanted or undesirable results.

WARNING!

Warnings advise you that failure to avoid or to take the specified action might result in physical harm to the user, damage to the hardware, or loss of data.

Icon Tool

Phone. Use the phone to configure settings.

Administration Console. Use the Administration Console to configure settings. This icon is also used for the Mailbox Manager.

Maintenance Menu. Use the maintenance menu to start or stop the messaging system, update the messaging system, and configure the network.

UNIVERGE UM4730 INSTALLATION GUIDE2

Administration Console IconsThe following are Administration Console icons. If an icon is gray, this indicates that it is not available:

Using the Command Line InterfaceCommunicating with the Linux operating system requires the use of tools and shells such as WinSCP and PuTTY.

Some procedures in this document are based on the WinSCP and PuTTY applications. When using these applications, input devices include the keyboard or mouse. Use the input device that you prefer.

Mailbox Manager. Use the Mailbox Manager to read or recall messages, set personal profiles, and set personal preferences for greetings, playback, call transfer/screening, notification, groups, and e-mail.This icon is in the Status icon menu. For detailed information about using the Mailbox Manager refer to the User Guide.

Icon Tool

Icon Description

Find. Click to find a subscriber profile.

Add. Click to add a new subscriber.

Delete. Click to delete a subscriber.

Help. Click to open online help

Next. Click to see the next subscriber.

Previous. Click to see the previous subscriber in the database.

Save. Click to save changes to a setting.

Input Device

Description

Mouse Click to select Maintenance Menu items and buttons; select items in the Administration Console; and select items or buttons in WinSCP.

Keyboard command prompts Type a command with options then press ENTER. For example:

mcedit /cps.ini ENTER

This command opens the cps.ini file in the mcedit tool.

1, 2, 3,... 0 To select a menu item, type the numeric equivalent of a menu item. For example: Type 0 (zero) to Log out of the Maintenance Menu.

TAB Press the TAB key to move through menu items and command buttons in the Maintenance Menu.

, , , and Use the keyboard arrow keys to move between menu items, buttons, or options.

function keys Tools such as mcedit use function keys to execute specific actions. For example: F10, exits mcedit; F2 saves the file, and so on.


Related DocumentationThe documentation set for this product includes the following documents and online resources:

● User Guide. Available as a PDF only. Contains instructions for subscribers about accessing the messaging system and checking and sending messages.

● Quick Reference Card. Contains shortcuts and quick instructions telling subscribers how to access and use the messaging system.

● Conversation Map. Available as a PDF only. Contains tables of system conversation prompts and phrases.

● Documentation Updates. See the reseller web site http://www.necntac.com for documentation updates.

● Online Help. Online help is available to provide immediate assistance while using the Administration Console and Mailbox Manager. Whenever you are using the Administration Console or Mailbox Manager, click the Help icon or Help to see context-sensitive help for the current page.

You must have pop-up windows enabled on your browser to access some features of the Administration Console and Mailbox Manager help. See your browser documentation for information about enabling pop-up windows.

Online help is only supported for Internet Explorer 6.0 or newer. You can view online help using Firefox or other browsers, however, some help features might not work properly. One of the features that does not work properly is the truncation of pop-up glossary definitions.

Supported Phone SystemsThe messaging system is designed specifically for use with the phone systems manufactured by NEC Unified Solutions. The following phone system is supported: NEC NEAX 2000 IPS upgrade.

Site RequirementsSelect a site for the messaging system server that meets the following requirements:

● A 100Mb network installation.

● The messaging system server is physically located close to the phone system.

● The messaging system server remains immobile while in operation.

● The site is dry, cool, and free of dust.

● Control access to the room where the messaging system server is installed. Do not install the computer or other equipment in an area where unauthorized persons can have access to it.

● Do not move the computer while the power is on. Follow the shut down procedure to avoid damage to the hard drive.

● Use a surge suppressor or a UPS (uninterruptible power supply) to protect against sudden variations in electrical power.

SPACEBAR Press the SPACEBAR to toggle check marks off and on. For example,

(*) Messages

Pressing the SPACEBAR clears the check box.

( ) Messages

Input Device

Description

WARNING!

Failure to follow these recommendations can result in unauthorized access to the system and consequent loss of data.


http://www.necntac.com

● Do not block the computer cooling vents.

Web Registration The messaging system must be registered to receive technical support assistance and to receive updates about upcoming releases.

When the messaging system is not registered, the system functionality is not affected. However, a registration reminder continues to appear each time you sign in to the Administration Console from the same Browser or computer. You can set the reminder to a weekly schedule or tell the system not remind you.

Registering the Product Use the following procedure to register the messaging system and validate the registration.

USING THE ADMINISTRATION CONSOLE

To register and validate the messaging system

This procedure assumes that the messaging system server is connected to a network and has Internet access.

1 Start your Web browser. In the address bar type:

http://<server name>/admin

where <server name> is the name or IP Address of the messaging system server.

2 Sign in using the appropriate user and password.

The UNIVERGE UM4730 License Agreement page appears.

3 Read the license agreement then click I accept.

The Licensing page appears.

4 Copy and paste the license number. You should have received the license file from your reseller.

5 Click Save.

The Switch Information page appears.

6 Select the appropriate switch from the Switch list.

7 Click Save.

The Switch Extensions page appears.

8 Click Edit all to type voice mail extensions for each port.

9 After typing the voice mail extensions, scroll down the page and click Save.

NOTE

Be sure that the computer cables are located where they cannot be stepped on, tripped over or damaged.


The Product Registration Form appears.

10 Select one of the following:

● Register. Type the information in the Product Registration form then click Register.

A registration is complete message appears.

● Do not remind me. Click to discontinue registration reminders. The messaging system is available for use, but you will not receive technical support assistance or notifications of updates.

● Remind me in 7 days. Click to be reminded in seven days.

The Administration Console Main page appears.

NOTE

Required fields are denoted by a red asterisk.


Preparing to Install the Messaging SystemThe following is a summary of the major steps required to install a new UNIVERGE UM4730 messaging system:

1 Verify that the installation and site requirements are met.See “Site Requirements” on page 4.

2 Configure the messaging system software.See “Configuring the Messaging System” on page 29.

3 Configure the phone system. See “Configuring the Phone System” on page 42.

4 Configure remote maintenance.See “Remote Maintenance” on page 61.

5 Configure optional features:● E-mail integration. Configure the messaging system for e-mail integration.

See “E-mail Integrations” on page 51.

● Visual Messaging. Refer to the Visual Messaging Installation Guide for information about installing and configuring Visual Messaging.

6 Optional tasks: ● Update version. Update from a previous version of UNIVERGE UM4730.

See “Updating the Messaging System” on page 89.

● Migrate OS/2. Migrate from a messaging system running on the OS/2 operating system.

See “Migrating from AD-40 Messaging Systems” on page 95.

7 Backup the messaging system.See “Backing Up and Restoring Data” on page 67.


2CHAPTER
Pre-Installation
Messaging System OverviewThe messaging system is delivered as a prebuilt messaging system or as kit that you build yourself.

● Prebuilt. A fully assembled and tested messaging system with the required hardware and software installed.

You must verify the components and follow some set up procedures to prepare the messaging system server for use with your phone system.

See “Configuring the Messaging System” on page 29.

● Kits. Consists of the software required to build a messaging system.

You provide a computer, expansion boards, and peripherals when building and configuring a kit for use with your phone system.

See “Building the Messaging System Server” on page 19.

CHAPTER 2: PRE-INSTALLATION 9

Pre-Installation ChecklistBefore installing the system key and the messaging system software. Work with your network system administrator to gather the information required

The messaging system can be connected to the network during the installation or after the installation is completed.

◆ Connect the messaging system to the network during installation.See “Building the Messaging System Server” on page 19.

◆ Connect the messaging system to the network after the installation.See “Configuring the Network” on page 27.

New System Installation StepsThe following outlines the steps for a new system installation.

1 Configure the computer BIOS.See “Configuring the BIOS” on page 11.

2 Install the messaging system. See “Installing the Messaging System” on page 23.

3 Configure the messaging system.See “Configuring the Messaging System” on page 29

4 Create a backup of the messaging system.See “Backing Up and Restoring Data” on page 67.

System UpgradesSystem upgrades include adding new ports to an existing messaging system or installing a new release of the messaging system.

● Add ports to an existing messaging system.

See “Verifying and Changing Licensing Information” on page 86.

● Update an existing messaging system.

See “Updating the Messaging System” on page 85.

Networking Checklist:

IP address

Subnet mast

Default gateway IP address

Host name

TCP/IP domain name

E-mail Integration Checklist:

Path name

IMAP server name

IMAP server IP address

SMTP server IP address

SMTP port

NOTE

The phone system must be programmed for voice mail before the messaging system server is connected to the network.

The messaging system server can be configured for networking before the phone system is programmed as long as it is not connected to the network before the phone system has been programmed.


Configuring the BIOSConfiguring the BIOS is necessary to enable USB ports and other settings in the BIOS. The messaging system uses a USB security key to license messaging system features. For the security key to work correctly, the USB ports on the messaging system must be enabled.

It is possible that the USB ports on the computer are disabled if you are installing a kit, or if you are migrating from previous version of the system on the same server.

Use one of the following procedures to ensure that the USB ports are enabled and to configure other required BIOS settings.

● Dell PCs in general. See “To enable USB ports on Dell Computers” on page 11.

● Dell mini-tower BIOS. See “To configure the Dell mini-tower computer BIOS” on page 12.

● Dell PowerEdge 2900 rack-mounted BIOS. See “To configure the rack-mounted Dell PowerEdge 2900 BIOS” on page 13.

● NEC Express 5800 rack-mounted BIOS. See “Configuring the Rack-Mounted NEC Express 5800 BIOS” on page 14.

● Other brands of PC-based computers. Refer to manufacturer documentation.

If you are installing or migrating to a newer messaging system server it is shipped with the USB ports enabled. Skip the rest of this chapter if you have a server that has USB ports enabled.

Enabling USB Ports on Dell ComputersUse the following procedure to enable USB ports on a Dell PC. The steps to enable USB ports on a PC vary from manufacturer-to-manufacturer. The following procedure is appropriate for most Dell PCs.

To enable USB ports on Dell Computers

1 If the messaging system software is running, shut it down.

2 Restart the computer.

3 Watch the monitor screen during the reboot process. When F2 = Setup appears on the screen, immediately press F2.

The Dell setup menu appears.

4 Scroll through the list of options and select Integrated Devices (LegacySelect Options). Press ENTER.

A submenu of devices appears.

a Scroll through the list of devices, and turn On the USB Controller.

If the USB controller is set to Off, select the USB Controller device, and press the SPACEBAR to turn it On.

b Press ESC to return to the main setup menu.

5 Press ESC again.

If you made any changes, a menu of options appears. Select Save Changes and Exit, then press ENTER.

6 The computer restarts.


Configuring a Dell Mini-Tower Computer BIOSUse the following procedure to configure the Dell Mini-Tower BIOS PC only.

To configure the Dell mini-tower computer BIOS

1 Turn on the computer.

2 When the message Press F2 for setup appears on the screen, press the F2 key.

3 Set System Date to the current date.

4 On the Main BIOS menu, select Boot sequence, then press ENTER.

5 Set the first boot device to CD-ROM or DVD-ROM.

6 On the Main BIOS menu, select Integrated Devices, then press ENTER.

7 Set Sound to On.

8 Set Network interface controller to On.

9 Set USB Controller to On.

10 Set Serial Port 1 to COM1.

11 Set Serial Port 2 to COM2.

12 Set Onboard Video Buffer to 8 MB.

13 Press ESC to return to the Main BIOS menu.

14 Select Power Management, then press ENTER.

15 Set Suspend Mode to S1.

16 Set AC Power Recovery to Last.

17 Set Low Power Mode to Disabled.


19 Select System Security, then press ENTER.

20 Set Password Status to Locked.

21 Set Chassis Intrusion to Enabled.


23 Set IDE Hard Drive Acoustics Mode to Performance.

24 Press ESC to exit the BIOS setup, then press Y to confirm and save the configuration.

CAUTION!

See “Configuring a Rack-Mounted Dell PowerEdge 2900 Computer” on page 13 to configure the rack-mounted pre-built computer.


Configuring a Rack-Mounted Dell PowerEdge 2900 Computer

Use the following procedure to configure the BIOS on a Rack-Mounted Dell PowerEdge 2900.

To configure the rack-mounted Dell PowerEdge 2900 BIOS


2 When the message Press F2 for setup appears on the screen, press the F2 key.

3 On the Main BIOS menu, set System Time to the current time for your time zone.


5 Select Boot sequence, then press ENTER.

6 Set the boot sequence as follows:


8 On the Main BIOS menu, select Integrated Devices, then press ENTER.

9 Set Serial Port to COM1.

10 Set PCI IRQ Assignment to Default.

11 On the Main BIOS menu, select System Security, then press ENTER.

12 Set Password Status to Locked.

13 Press ESC to exit the BIOS setup, then press Y to confirm and save the configuration.

CAUTION!

Do not use these settings for the rack-mounted NEC pre-built computer.

Do not use these settings for the mini-tower Dell pre-built computer.

See “Configuring a Dell Mini-Tower Computer BIOS” on page 12 or “Configuring the Rack-Mounted NEC Express 5800 BIOS.”

Device Messaging system settings

Virtual floppy If DRAC5 is installed.

IDE CD-ROM Enabled

Virtual CD-ROM If DRAC5 is installed.

Hard drive C: Enabled

Embedded NIC1 MBA Enabled

Boot Sequence Retry Disabled

USB flash drive emulation type If DRAC5 is installed.


Configuring the Rack-Mounted NEC Express 5800 BIOS Use the following procedure to configure the BIOS on a rack-mounted NEC Express 5800 computer.

To configure the rack-mounted NEC Express 5800 BIOS


2 When the message F2 = setup appears on the screen, press the F2 key.

3 On the Main BIOS menu, set System Time to the current time for your time zone.


5 Select Advanced, then press ENTER.

6 Select PCI Configuration, then press ENTER.

7 Set Onboard NIC1 ROM to Disabled.

8 Set Onboard NIC2 ROM to Disabled.

9 Press ESC to return to the Advanced BIOS menu.

10 Select Peripheral Configuration, then press ENTER.

11 Set Serial 1 (DB-9) Address to Disabled.

12 Set Legacy USB Support to Disabled.


14 Select Exit, then press ENTER.

CAUTION!

Do not use these settings for the rack-mounted Dell pre-built computer.

See “Configuring a Dell Mini-Tower Computer BIOS” on page 12 or “Configuring a Dell Mini-Tower Computer BIOS.”


3CHAPTER
WinSCP and PuTTY
OverviewWinSCP (file transfer) and PuTTY (SSH utility) are open source programs that have been tested and approved for use with the messaging system.

These programs can be downloaded from the Internet or installed from the Installation disc.

Installing WinSCPThere are two utilities, WinSCP and PuTTY that enable remote maintenance of the messaging system. Each tool provides different capabilities:

● WinSCP. Enables administrators to transfer files from one computer to another.

● PuTTY. Enables administrators to log on to the messaging system command line interface, the Maintenance Menu.

The following procedures assume that WinSCP will be installed on a computer running the Windows XP operating system.

To install the WinSCP client

1 Insert the Installation disc into the disk drive.

The Autostart page appears.

2 Using Windows Explorer browse to the /Utilities/RemoteAccess/WinSCP/ directory.

3 Double-click WinSCP.exe to start the WinSCP installation.

A security alert message appears.

4 Click RUN.

The Select Setup Language page appears.

5 Select the appropriate language from the drop-down list, then click OK.

The Welcome to WinSCP Setup Wizard appears.

6 Click Next.

7 On the License Agreement page, click Next.

8 Accept the default installation path or type a new path, then click Next.

The Select components page appears.

9 Accept the default components. If appropriate, select a language for translation, then click Next.

NOTE

For security reasons WinSCP access is limited to the following messaging system directories:

● /opt/vmail/var/backup● /opt/vmail/var/log● /opt/vmail/var/update● /home/

CHAPTER 3: WINSCP AND PUTTY 15

10 Accept the default Start Menu folder name or type a new name, then click Next.

The Select Additional Tasks page appears.

11 Accept the default additional task settings, then click Next.

The Initial user settings page appears.

12 Select one of the user interface styles, then click Next.

The Ready to Install page appears.

13 Verify that the settings are correct then click Install.

To review or change any of the settings click Back.

When the installation is complete, the Completing WinSCP3 Setup Wizard page appears.

14 Clear Start WinSCP now then click Finish.

Using WinSCP to Access the Messaging SystemThe following instructions assume that WinSCP is installed on a computer running the Windows XP operating system.

To run WinSCP

1 Click Start > Programs > WinSCP3 > WinSCP or the appropriate path for the WinSCP executable.

The WinSCP Login window appears.

2 Click Session.

3 Type the messaging system Host name (or IP address), User name, and Password.

4 Click Save to save the login information for future sessions.

NOTE

All WinSCP procedures in this document assume that the Norton Commander interface is being used.

Interface style Description

Norton Commander

recommended option

Displays source computer directories in the left-hand pane and destination computer directories in the right-hand pane.

Explorer-like Displays directories in the left-hand pane and files in the right-hand-pane.

NOTE

The default IP address for the messaging system is 169.254.0.1.

The user name is admin, and password is voicemail.


5 Click Login.

A potential security breach message might appear.

6 Click Yes.

The WinSCP console appears.

Installing PuTTYAfter configuring the TCP/IP settings, run a PuTTY SSH client on the remote computer to connect to the voice board, and complete the software configuration.

The following procedures assume that PuTTY will be installed on a a Windows XP computer and it is being installed from the Installation disc.

To install the PuTTY application

Use this procedure to install PuTTY on the messaging system, a client computer, or on a remote computer.


The autostart page appears.

2 Using Windows Explorer, browse to /Utilities/RemoteAccess/Putty/.

3 Double-click the PuTTY installation exe file to start the PuTTY installation.

An Open File security alert message appears.

4 Click RUN.

The Welcome to the PuTTY Setup Wizard appears.

5 Click Next.

The Select Destination Location page appears.


The Select Start menu folder page appears.

7 Accept the default components, if appropriate, select a language for translation, then click Next.


The Select Additional Tasks page appears.

9 Select the appropriate tasks to complete, then click Next.

The Ready to Install page appears.

10 Verify that the settings are correct, then click Install.

To review or change any of the settings, click Back.

11 Clear the View README.txt check box, then click Finish.

Configuring PuTTY Use the following procedure to prepare PuTTy for use with the messaging system.

To configure PuTTY

1 On the Windows taskbar, click Start > Programs > PuTTY > PuTTY.

The PuTTY Configuration page appears.

NOTE

Only PuTTY and WinSCP SSH clients are supported.

CHAPTER 3: WINSCP AND PUTTY 17

2 Use a network crossover cable to connect the voice board to a computer.


4 Click Open.

When the first connection is made, a warning message appears. The warning message does not appear for subsequent connections. Click Yes.

After the client connects to the voice board, the login prompt appears. See “Using PuTTY to Log On and Log Off” on page 74.

Using PuTTY to Access the Maintenance Menu The following procedures assume that PuTTY is installed on a computer running the Windows XP operating system and you are using a keyboard and mouse as input devices.

To run PuTTY

Use PuTTY for remote SSH terminal access.

1 Click Start > Programs > PuTTY > PuTTY.

The PuTTY Configuration window appears.


The Maintenance Menu appears.

NOTE



NOTE




4CHAPTER
Building the Messaging System
Server

OverviewA kit contains the messaging system software and a system key. You provide the computer. This chapter describes the steps for assembling a messaging system server.

System ComponentsConfirm that you have all of the components required for the messaging system installation. If any of the kit components are missing, call your sales representative.

❑ Installation disc includes the following:

■ Messaging system application installation.

■ Messaging system documentation.

❑ Voice board(s)

❑ System key

❑ Security File disc

❑ 100 Mbit/s Linux compatible network interface card or on-board NIC.

❑ Antistatic wrist strap.

❑ Printed documentation.

❑ Uninterruptible power supply (UPS).

❑ Any optional software and hardware packages purchased with the messaging system.

CHAPTER 4: BUILDING THE MESSAGING SYSTEM SERVER 19

System RequirementsDepending on the number of voice ports, the number of subscribers, and the combination of options included, the computer might need more than the minimum central processing unit (CPU) power and memory requirements listed below. Call your sales representative for more information.

Minimum System Requirements for 40 or Fewer Ports ❑ Celeron 800MHz CPU

❑ 20GB IDE only hard disk

❑ 512MB memory

❑ For remote-only Web interface, Linux-compatible VGA.

For local and remote Web interface, Linux-compatible VESA 2.0 compliant video card or controller with at least 4 MB of video memory.

❑ Generic VGA for remote only HTML interface; VESA 2.0 compliant video card for local/remote HTML interface

❑ Generic monitor for remote only HTML console; Generic SVGA monitor that supports 1024x768@60Hz for local HTML interface

❑ PS/2 or USB mouse

❑ PS/2 or USB keyboard.

❑ DVD-ROM - internal only

❑ Linux-compatible OHCI/UHCI-based USB controller.

❑ NIC (optional): for Visual Messaging, remote HTML interface and network based remote access

Minimum System Requirements for More than 40 Ports❑ Pentium 1.5GHz CPU

❑ 20GB IDE only hard disk

❑ 512MB memory

❑ For remote-only Web interface, Linux-compatible VGA.

For local and remote Web interface, Linux-compatible VESA 2.0 compliant video card or controller with at least 4 MB of video memory.

❑ Generic VGA for remote only HTML interface; VESA 2.0 compliant video card for local/remote HTML interface

❑ Generic monitor for remote only HTML console; Generic SVGA monitor that supports 1024x768@60Hz for local HTML interface

❑ PS/2 or USB mouse.

❑ PS/2 or USB keyboard.

❑ DVD-ROM - internal only

❑ USB: OHCI/UHCI based controller

❑ NIC (optional): for Visual Messaging, remote HTML interface and network based remote access

These are updated requirements from Kathy, please specify if any are OEM specific: AV or NEC only. or Inswitch (and which one).

Thank you,


System Configuration StepsThe following list is an overview of the steps necessary to build your messaging system computer, install the messaging system software, and configure the messaging system.

1 Gather pre-installation information.See “Pre-Installation Checklist” on page 10.

2 Connect peripheral devices and the system key.See “Connecting Peripheral Devices and the System Key” on page 137.

3 Build the computer. Refer to the manufacturer’s documentation.

4 Install the Linux operating system and the messaging system. See “Installing the Messaging System” on page 23.

5 Configure the messaging system server and setup networking.

6 Configure the voice messaging software.See “Configuring the Messaging System” on page 27.

7 Configure the messaging system server for networking. See “Configuring the Network” on page 27.

8 Configure the messaging system application.See System Administrator Help.

9 Configure the phone system integration.See “Configuring the Phone System” on page 42.

10 Configure Visual messaging, if purchased.Refer to the Visual Messaging Installation Guide.

11 Configure remote maintenance.See “Remote Maintenance” on page 61.

12 Back up the messaging system.See “Backing Up and Restoring Data” on page 67.

CHAPTER 4: BUILDING THE MESSAGING SYSTEM SERVER 21

5CHAPTER
Installing the Messaging
System

IntroductionThis chapter contains instructions for installing the messaging system software.

The Installation Guide content focuses on setting up the messaging software and does not provide detailed support information about the Linux operating system.

Compliance information for third-party electronic devices can be found in the manufacturer documentation included with the messaging system. Do not use third-party manufacturer documentation to install, upgrade, or manage the messaging system. Refer only to the messaging system documentation to install, upgrade, and manage the messaging system.

To install the messaging system


2 Restart the system.

The installation welcome page appears.

Version: 10.0.3.nn

Date: Sep 27, 2007 15:57:17PDT (-0700) This product supports x86 compatible hardware. For more hardware specific information press [F2].

For a new install or if you upgrade from a previous version of UNIVERGE UM4730, press Enter.

For other boot options or if you are migrating from a different product press [F3].

Press the F-key to select a different option[F1-Welcome] [F2-Information] [F3-Advanced] [F4-Boot options]Boot: _

CHAPTER 5: INSTALLING THE MESSAGING SYSTEM 23

3 Press Enter, to start the installation.

To see detailed information about the other options on this page, press the appropriate function key.

The installation requests a language selection. The following text appears:.

4 Type Y to confirm the language selected, then press ENTER.

5 Read the warming before continuing.

6 Type Y to confirm the installation then press ENTER.

7 After the system restarts the Welcome to vmail window appears.

8 Sign in:

a Type admin then click OK.

Click Start Again to type a different user name.

b Type the admin password: voicemail then click OK.

Click Start Again to type a different password.

The Linux desktop appears.

NOTE

U. S. English is the default language.

When you select a different licensed language, it becomes the default language for the desktop, the messaging system tools, and the messaging system conversations.

Input: AT Translated Set 2 keyboard as /class/input/input0* Checking system requirements: success* Detecting hardware: success* Select the default system language for this installation:

* Enter a language number, then press Enter:

1 Cantonese 12 Hebrew 2 Catalan 13 Italian3 Danish 14 Japanese4 Dutch 15 Mandarin5 English (Australia) 16 Portuguese (Brazil)6 English (New Zealand) 17 Portuguese (Portugal) 7 English (United Kingdom) 18 Russian8 English (United States) 19 Spanish (Argentinian)9 French (Canada) 20 Spanish (Latin America) 10 French (France) 21 Spanish (Mexico)11 German 22 Spanish (Spain)

23 Swedish

* You selected U.S. English language. Confirm? [Y/n]?* Default system language is: English (United States) * Configuring installation media: success

* Warning!* To continue the installation, the hard drive (/dev/had) must * be formatted. * All existing data on this hard drive will be lost. * Are you sure you want to continue? [y/N]:* Preparing hard disk (this might take a while):…Remove installation disc, then press ENTER to reboot -


Introducing the Linux DesktopThe Linux desktop includes several icons, it also includes the messaging system tool icons in the taskbar:

● Administration Console. Starts the Administration Console.

● Maintenance Menu. Starts the Maintenance Menu interface.

System Status IconThe system status icon appears in the taskbar. The status icon has two states: Running or Stopped:

Click the status icon to start or stop the messaging system, open the Mailbox Manager, open the Administration Console, or open the Port status page.

The messaging system is running. The icon is green. Click to stop the messaging system software.

The messaging system is in process of stopping or starting.

The messaging system is stopped, the icon is red. Click to start the messaging system software.

System Status

Administration Console

Maintenance Menu

CHAPTER 5: INSTALLING THE MESSAGING SYSTEM 25

6CHAPTER
Configuring the Messaging
System

OverviewThe messaging system has been installed, the next step is to configure the messaging system and the phone system to communicate with each other. Configuring the messaging system to communicate over a network with other systems and the phone systems is required. Use the following procedure to configure the network connections.

Configuring the Network After installing and connecting to the messaging system, configure the phone system and messaging system software features.

USING THE MAINTENANCE MENU

To configure the network settings

Use the following procedure to configure the network.

1 Start PuTTY.

The login prompt appears.

2 Type the messaging system Host name (or IP address) on the PuTTY Configuration dialog box.

3 Click Open.

The PuTTY command window appears.

4 Log on to the messaging system.


5 Select Configuration, then press ENTER.

The Configuration page appears.

Host name or IP address 169.254.0.1 (default)

Domain name

Primary DNS IP address

Secondary DNS IP address

TCP/IP. The following are the minimum required to provide access to the Administration Console and Maintenance Menu (PuTTY).

IP address

Subnet mask

Default gateway

NOTE


NOTE

The log on name is admin, the password is voicemail.

CHAPTER 6: CONFIGURING THE MESSAGING SYSTEM 27

6 Select Network setup then press ENTER.

The Network setting page appears.

7 Select Host name then press ENTER.

The Host name page appears.

8 Type the Host name then press ENTER.

The Network setting page reappears.

9 Select Domain name then press ENTER.

The Domain name page appears.

10 Type the Domain name then press ENTER.


11 Select Primary DNS then press ENTER.

The Primary DNS page appears.

12 Type the DNS server IP address, then press ENTER.


13 Select Secondary DNS then press ENTER.

The Secondary DNS page appears.

14 Type the DNS server IP address, then press ENTER.


15 Select TCP/IP settings then press ENTER.

The TCP/IP configuration page appears. The current settings are shown.

a Type the messaging system IP address then press ENTER.

The TCP/IP page reappears.

b Select Subnet mask then press ENTER.

The Subnet mask page appears.

c Type the Subnet mask, usually 255.255.255.0, then click OK.


d Select the Default gateway then press ENTER.

The Default gateway mask page appears.

e Type the Default gateway then press ENTER.


f Select Apply TCP/IP changes.

An alert message appears.

g Select YES to apply the changes.

16 Select Return to previous menu, then press ENTER.

The Network setting page appears.


The Configuration page appears.

18 Select Return to previous menu, then press ENTER to return to the Main menu.

19 Do not log off or close the Maintenance Menu.


Configuring the Messaging SystemConfiguring the messaging system is managed using two tools:

● Maintenance Menu. The Maintenance Menu is accessible using a monitor and keyboard attached to the phone system or using PuTTY to remotely access the system from a networked computer.

The Maintenance Menu is a user interface that minimizes the need to type lengthy commands at the command line prompt.

Use the Maintenance Menu to specify network configuration settings, set the messaging system software date, time, time zone, and general tone detection. Other messaging system configuration settings are configured using the Administration Console.

● Administration Console. The Administration Console is accessible using an Internet browser that can connect to the messaging system IP address.

Use the Administration Console to stop and start the messaging system software, set hospitality (Property management system - PMS) settings, e-mail settings, add/remove language packs, extension remapping, trunk remapping, update licensing information, specify switch integration information, back up data, restore data, and much more.

Refer to System Administrator Help for details about other features available in the Administration Console.


To configure the messaging system date and time

While still logged on as admin, use the following procedure to set the voice messaging software date and time.

1 Select Configuration then press ENTER.

The System configuration page appears.

2 Select Set date and time then press ENTER.

3 Select the appropriate Time zone.

Use the UP/DOWN arrow keys to scroll through the list of time zones.

4 Select OK then press ENTER.

MOTE

IE 6.0 and newer and Firefox 2.0 and newer are supported.

Please note, that some features in online help, such as popup glossary definitions do not work properly in the Firefox Browser.


5 Select the current date:

■ Press the TAB key to move between fields and command buttons.

■ Press the UP/DOWN arrow keys to change the month.

■ Press the UP/DOWN arrow keys to change the year.

■ Press the UP/DOWN and LEFT/RIGHT arrow keys to change a date.


7 Verify that the current time is correct.

Press the UP/DOWN arrow keys to increase or decrease the field values, press the LEFT/RIGHT arrow keys to move between fields.


The Date and time are set message appears.

9 Select YES, then press ENTER

10 Select Return to previous menu, then press ENTER to return to the Main menu.

11 Select Log out then press ENTER.


To create a new system manager

There is only one system administrator, admin, that is created when the product is installed. There can, however, be multiple system managers. Use this procedure to create a new system manager for the messaging system.

1 Start the Administration Console and sign in using the administrator credentials.

2 Click Subscribers > Subscribers > Profile.

The Subscriber profile page appears.

3 Click Search to find an existing subscriber or click Add to create a new subscriber.

On the Add subscriber page:

a Click Add.

The Add Subscriber page resets.

b Click Done to close the Add Subscriber page.

The Add Subscriber page closes and the information appears on the Subscriber Profile page.

Or on the Search page, type a partial name or extension number, then click Find, select the subscriber.

4 On the Subscriber profile page, select Enable subscriber as system manager.

5 Click Save.

The subscriber now has system manager permissions.

Note

The week number appears on the left-most column of the calendar.


Resetting Third-Party Licensing AgreementsResellers who are assembling messaging systems for delivery to customers must reset the third-party licensing agreements. This enables customers to accept the licensing for third-party software and use the Web registration for the messaging system.


To reset the third-party licensing agreements

1 Close the Internet Browser and all Internet applications.

2 Log on to the Maintenance Menu.

3 Select Maintenance.

4 Select Command Prompt.

5 Type the following command:

sudo ./bin/prepare_system

6 Close the command window.

7 Log out of the Maintenance Menu.

When the client logs on to the Administration Console the third-party licensing agreements appear.

CAUTION

Law requires that end-users accept the End User License Agreement for software installed on their systems.


Configuring System SecurityProtect the messaging system server from unauthorized access and potential damage, by using these procedures immediately after first sign in to the system.

● Use personal identifications (ID). Change the personal ID for the default system manager.

Personal ID numbers are typically assigned based on a pattern such as combining a digit with the extension number. For example, 92234.

Select a personal ID for the default system manager that is difficult for others to guess.

To prevent access to the system manager mailbox by phone, use the $ (dollar sign) at the beginning of the ID. For example, $nec.

● Security codes. Set the system manager security code to one that is difficult for others to guess.

The security code should be a random sequence of four or more digits.

Set a default security code and require all subscribers to use security codes. This ensures that unauthorized persons cannot access unused mailboxes and prevents subscribers from enrolling without setting a security code. See “Additional Recommended Security Practices” on page 32.

● Invalid log on. Limit the number of times a caller can enter an invalid system ID. This setting prevents unidentified callers from accessing the system and trying to guess a valid system ID.

You can also set the action the messaging system takes when a caller exceeds the maximum number of invalid log on attempts.

● Physical security. Control access to the room where the messaging system server is installed. Do not install the computer or other equipment in an area where unauthorized persons have access.

Additional Recommended Security PracticesIn addition to setting system security codes, follow these recommendations to protect the messaging system.

● Limit the number of system managers added to the system. System managers can change system screens, mailboxes, and greetings by phone. Assign system manager status to subscribers who need it to perform system management tasks.

● Delete any unused mailboxes on the system. When adding a range of mailboxes, add only the number of boxes required. Immediately reassign or delete subscriber mailboxes when subscribers leave the organization. This precaution is particularly important if a subscriber is a system manager.

● Create subscriber directory reports. Check for any unused mailboxes. Delete any unused mailboxes. Verify that the correct subscribers are assigned system manager status. Delete any unknown subscribers.

● Create system usage and system log reports. System usage and system log reports show patterns of messaging system activity. Check the reports for unusual activity, particularly during late night or early morning hours. Check for calls that are unusually long in duration. Check the reports for activity by any system IDs you do not recognize.

CAUTION

Failure to follow these guidelines might result in unauthorized access to the messaging system and/or loss of data.

NOTE

This precaution is important to prevent unauthorized persons from guessing the security code and then modifying mailboxes and greetings by phone.


● Educate subscribers about the importance of following recommended security practices. Teach subscribers to avoid security codes that match their birthday, child’s name, or social security number. Teach subscribers not to program a speed-dial key with their security code. Teach subscribers not to write down their security code or share the code with others. Distribute your organizational security policies in writing to all employees.


To change the default system manager personal ID

1 In the Navigation pane, under Subscribers, click Subscribers > Profile.

The subscriber profile page appears.

2 Click Search.

3 In the Find and Select Subscriber dialog box, select Find by Name.

4 Type an * (asterisk) in the text box, then click Find.

5 Select the default system manager.

6 In the Personal ID field, type a new personal ID.

7 Click Save.

USING A PHONE

To set a security code for a system manager

1 Call the system and enter the system manager personal ID.

2 Press 7 to access setup options.

3 Press 7 to access personal options.

4 Press 4 to change the security code.

5 Follow the instructions to change the code.

6 Press * * * to exit the system, then replace the phone handset.


To configure a default password

The default password is used by all subscribers during enrollment. The default password is also used to reset lost or forgotten passwords.

1 In the Navigation pane, click Subscribers > Account Policy.

The Account Policy page appears.

2 To require subscribers to set a password, clear the Permit blank password check box.

3 Type the Minimum number of characters in password check box. The minimum number of characters allowed are 4 through 10.


4 In the Default password for each new subscriber field, type a default password.

5 Click Save.


To set maximum times a caller can enter an invalid ID

1 In the Navigation pane, click System > Configuration > General.

The General page appears.

2 In the Maximum number of attempts to enter a personal ID field, type the maximum number of times a caller can enter an invalid system ID.

The value typed should be at least one more than the selection made in the Maximum security code/password attempts field.

3 In the Maximum security code/password attempts field, select the maximum number of times a subscriber can incorrectly type a password before being re-routed.

The value selected should be at least one less than the value typed in the Maximum number of attempts to enter a personal ID field.

4 In the Callers entering a bad ID is rerouted to field, type the extension a caller is transferred to when the caller exceeds the maximum number of invalid IDs.

5 Click Save.

Next Steps…

◆ Configure e-mail integrationSee “Configuring the E-mail Integration” on page 35.

NOTE

The length of the password must match the minimum length specified in the previous step. This default password must be given to all new subscribers for first time enrollment.

NOTE

The other fields on the General page are covered in the System Administrator Help.


Configuring the E-mail IntegrationBefore you can configure subscribers for e-mail integration, you must have a license for the e-mail integration and you must configure the e-mail server information.

To configure an e-mail integration, you need the following e-mail server information:

● The IP address or exact name of the SMTP server

● DHCP. User name and password required to authenticate.


To configure the e-mail integration

1 Sign in to the Administration Console as $nec.

2 In the Navigation pane, click System > Configuration > E-mail settings.

The E-mail Notification Settings page appears.

3 In the Outgoing e-mail server field, type the IP address of the outgoing e-mail server or localhost.

If your system is set up to recognize server names, type the server name instead of the IP address.

4 In the Port field, type the SMTP port for your e-mail server.

The default value is 25.

5 If appropriate select the Use SSL checkbox.

6 Select Use authentication checkbox.

7 In the Authentication list, select the authentication protocol used by the system: NT LAN Manager (NTLM), PLAIN, or LOGIN.

8 In the User name field, type the user name.

9 In the Password field, type the password.

10 In the Global e-mail field, type the common e-mail address.

11 In the Display Name field, type the display name.

12 Click Save.


Configuring Subscriber Mailboxes for the E-mail IntegrationAfter setting up the messaging system and the e-mail server for the e-mail integration, set up subscribers to access their e-mail messages using the phone.


To set up the default subscriber template for e-mail access


2 In the Navigation pane, click Subscribers > Subscriber Template > E-Mail.

3 Select a server in the Server type list.

4 Select an authentication type in the Authentication method list.

5 In the Server name field, type the IP address of the e-mail server.

If your organization’s system is set up to recognize server names, type the server name instead of the IP address.

6 In the Port field, type the port number for your server. The default value is 143.

7 If the system uses Secure Sockets Layer (SSL) protocol, select the SSL check box.

8 Click Save.

Setting Subscriber E-mail Access OptionsThere are several e-mail access options that can be set for subscribers.


To set the e-mail access options

❚ Click Subscribers > Subscriber Template > Access Options.

For details about the e-mail access options, see System Administrator Help.


To set up an individual subscriber for e-mail access


2 To change settings for individual subscribers, in the Navigation pane click Subscribers > Subscribers > E-mail.

3 In the E-mail address field, type the complete subscriber e-mail address. For example, [email protected].

4 In the Server type field, select an e-mail server type.

NOTE

When SSL is selected the Port field number changes to 993 when the IMAP server type is selected, and 995 when the POP3 server type is selected. To use the original Port number, retype the value in the Port field.

NOTE about Access Options:

When Access e-mail messages from the messaging system is selected, make sure that you provide the appropriate e-mail reader information on the Subscribers > E-mail page.

When Forward voice mail to the e-mail system, Forward faxes to the e-mail system, or Receive e-mail notification of successful or failed faxes are selected, make sure that you provide the subscriber’s e-mail address in the E-mail notification field on the Subscribers > E-mail page. Selecting these fields also activates the E-Mail tab in the Mailbox Manager.


5 Select the authentication method from the Authentication list.

6 In the Server name field, type the IP address of the e-mail server.

If the system is set up to recognize server names, type the server name instead of the IP address.

7 In the User name field, type the subscriber’s user name.

8 In the Port field, type the port number for the server. The default value is 143.

9 If the system uses Secure Sockets Layer (SSL) protocol, select the SSL check box.

10 Click Save.

Next Steps…

◆ Configure Property Management SystemSee “Configuring PMS” on page 38.

NOTE

When SSL is selected the Port field number changes to 993 when the IMAP server type is selected, and 995 when the POP3 server type is selected. To use the original Port number, retype the value in the Port field.


Configuring PMSIf the Property Management system (PMS) package is licensed, use the following procedure to configure PMS. Skip this section if PMS is not licensed.


To configure the Property Management System package


2 In the Navigation pane, click System > Configuration > Hospitality Settings.

The Hospitality Settings page appears.

3 Type a value in the Reset message box ID field.

4 Type a value for the Post check-out ID field.

This is the ID assigned to a guest after they have checked out.

5 Type an ID for the ID guest directory field.

6 In the PMS Device Configuration Section, complete the following steps:

a Select a PMS Integration from the PMS Integration list box.

b Select a PMS Port from the PMS Port list box.

c Select the appropriate Baud Rate for the PMS device.

d Select the appropriate Parity for the PMS device.

e Select the appropriate Stop Bits for the PMS device.

f Select the appropriate Data Bits for the PMS device.

7 In the Wake-up Call section:

a Select Allow guests to set their own wake-up calls to turn on Wake-up calls and allow guests to set their own wake-up calls.

b Specify the number of rings.


c Specify the Ring frequency in minutes.

d Specify the Maximum number of retries for the wake-up call.

e Specify the Wake-up greeting ID.

This is the ID of the recorded wake-up greeting. The length of the greeting appears next to the ID field.

f Specify the On unanswered notify ID.

This is the extension that is called or paged when a wake-up call is not answered.

8 In the Check-in message section:

a Select Enable check-in message to turn on a check-in message.

b Click 00:00 to record the Check-in message ID.

9 Click Save.

Next Steps…

◆ Set up phone system integration.See “Programming the Switch” on page 35.

Record Message


7CHAPTER
Configuring the Phone System
Integration

About the Phone System Integration This chapter describes the steps required to configure the phone system for integration. Details of the integration might vary depending on the particular phone system being used.

This chapter is intended to be used with the phone system documentation. Some phone systems require additional system programing, hardware, or configuration. If your phone system has a chapter in the Integration Guide, follow the instructions provided in the Integration Guide

If the phone system provides caller ID information, the messaging system is configured to automatically use and display an external caller phone number.

Integration Steps

1 Configure the phone system for the integration.See “Configuring the Phone System” on page 42.

2 Connect the phone system to the messaging system computerSee “Connecting the Phone System to the Messaging System” on page 43.

3 Select the phone system integration.See “Selecting the Phone System Integration” on page 43.

4 Learn the phone system tones.See “Using GTDetect” on page 45.

5 Test the integration.See “Testing the Integration” on page 47.

6 Configure messaging system options.Additional messaging system features, such as easy message access, identified subscriber messaging, and trunk mapping for transaction boxes, are configured using the Administration Console.

See “Selecting a Call Transfer Type” on page 48.

See “Changing the Keypad Map” on page 50.

Using the Messaging System Software ToolsSome procedures in this chapter require that you use the Administration Console to configure the messaging system software and others require the use of the Maintenance Menu.

● See “Using the Maintenance Menu” on page 75.

● See “Using the Administration Console” on page 77.

NOTE

This guide and the Integration Guide are intended to be used with the phone system documentation.

CHAPTER 7: CONFIGURING THE PHONE SYSTEM INTEGRATION 41

Configuring the Phone SystemBefore connecting the messaging system server to the phone system, use the following information to configure the phone system for the integration.

The configuration details might vary depending on the particular phone system. For detailed phone system procedures, refer to the phone system documentation.

Extensions must be installed and configured for each messaging system port. Hunt groups, trunk routing, and call overflow must be programmed so that the proper calls are routed to the messaging system.

Phone System Configuration Steps

1 Configure the system to detect hardware.The phone system must detect the boards and other special phone system hardware that has been added to the system or enabled.

2 Assign the extension numbers and hunt groups.■ Assign the extension numbers that the phone system uses to access the messaging

system.

■ Configure the hunt order for the phone system extensions.

For example, port 1 to port 2, and so on. Some phone systems do not support hunt groups. You can simulate a hunt group by forwarding each messaging system extension to the next extension when the extension is busy.

If the phone system supports hunt group access codes, assign a hunt group access code for the messaging system. This code is the number that subscribers dial internally to connect to the messaging system.

If the phone system does not support hunt groups and does not allow forwarding of extensions, use pooled ringing. See “Configuring Pooled Ringing” on page 36.

3 Configure trunk routing.Configure which trunks, if any, route to the messaging system.

If you are using pooled ringing, route all trunks to all messaging system ports. On some integrations, you can also map trunks to a transaction box.

4 Configure call overflow.■ Configure the phone system to handle calls when all system ports are busy or

unanswered. Overflow calls can be handled in one of three ways:

◆ Forward the call to an operator.

◆ Get a busy signal.

◆ Continue to get a ring signal until a port is available.

■ Program all lines that the messaging system answers to ring all of the system ports. When the messaging system answers a call, the phone system stops ringing the other ports.

Configuring Pooled RingingIf the phone system does not support hunt groups and does not allow forwarding of extensions use pooled ringing.


To configure pooled ringing

1 Log on to the messaging system.

2 On the Linux taskbar click the Administration Console and sign in to the Administration Console.

3 In the Navigation pane, click System > Switch > Switch Extensions.

4 Type 0 (zero) in the Rings to answer field.

Repeat this procedure for all ports.


Connecting the Phone System to the Messaging SystemAfter configuring the phone system and testing the extensions, connect the phone system to the messaging system computer.

Connect each phone system voice messaging port to the appropriate messaging system extension.

Procedures for connecting the phone system to the messaging system computer vary depending upon the type of phone system that is installed. In general:

● Voice Board Integrations. Connect the appropriate phone system cable to a connector on the voice board backplate.

● IP Integrations. Connect the appropriate network connector to an ethernet port on the messaging system server.

● SMDI or MCI Integrations. Connect the appropriate phone system data cable to a connector on the messaging system computer.

● Serial Integrations. Connect phone system to the COM1 serial port on the messaging system server.

Selecting the Phone System IntegrationThe messaging system includes a phone system configuration library that contains predefined parameters for integrating the messaging system with most phone systems.

Use the following procedure to select the phone system during the initial messaging system configuration

To select the phone system

1 Sign in to the messaging system.

The Web administration page appears.

2 In the Navigation pane, click System > Switch > Switch Information.

3 From the Switch list, select the phone system.

The phone system parameters appear in the Integration Options field. Depending on the phone system select additional data might appear on the Switch Information page.

4 Click Save.

To assign extensions to the ports

1 Sign in to the messaging system.

2 On the Linux taskbar click the Administration Console.

3 Sign in to the Administration Console.


NOTE

Integration options cannot be changed while the messaging system is stopped.


4 In the Navigation pane, click System > Switch > Switch Extensions.


Status options A/D, Ans, Dial, and Busy apply to voice and fax ports.

5 Click Edit All.

6 Type an Extension for each port.

Password. The Password field is automatically filled with the same value typed in the Extension field. The password field is available for some integrations such as IP Protims, but is not available for digital integrations.

7 Click Save.

8 Restart the messaging system for the new configuration to take effect.

Status Key Description

Options Key Description

A/D Answer and dial out FC Forwarded calls

DID Direct inward dial NL No LAN connects

Ans Answer only, no dial out

Dial Dial out only

Busy Busy

Lamp Light lamps

A/L Answer and light lamps

MD Message delivery

A/M Answer and message delivery

Fax Dedicated fax extensions


Using GTDetectSystem tones vary from one phone system to another. Use the GTDetect utility to learn the phone system tones and configure the messaging system server to recognize these tones.

The GTDetect utility also detects voice boards and checks the status of each port on each board. GTDetect is automatically installed with the messaging system software. The messaging system must be stopped before using the utility. For GTDetect to function properly, at least two of the voice ports must be connected.


To run GTDetect

You must have an extension within reach of the messaging system server.

1 If the messaging system computer is shut down, restart it.

The messaging system VMail log on page appears.

2 On the VMail page type the user name, admin, then click OK.

3 Type the admin password (voicemail), then click Login.


4 On the Linux taskbar click Maintenance Menu.


5 Select Configuration, then press ENTER.

6 Select Global tone detection, then press ENTER.

A confirmation message appears:

7 Click YES.

If any calls are in progress, an alert message appears:

NOTE

To type a different user name, click Start Again.


8 Press ENTER to close the calls and shut down the messaging system software.

Wait for the messaging system software to stop. When the messaging system software has stopped the Global Tone Detection options menu appears.

9 Press ENTER.

When global tone detection is completed, an alert appears telling you that the operation has completed.

10 Click Yes to restart the messaging system. Select Return to previous menu, then press ENTER.

11 Select Log out, then press ENTER to log out and close the Maintenance Menu.


Testing the IntegrationUse the following procedures to test each extension and confirm that the phone system is correctly programmed.

Test RequirementsThe following is required to properly test each extension:

● A test phone. A standard analog phone set with a ringer. If the phone system voice messaging uses feature phone sets, use a feature set for the tests.

● A line splitter. If the boards use RJ-14 connectors with two extensions per connector, use a line splitter to separate the two extensions.

Test Steps

1 Connect the test phone to the phone system.Use a line designated as a messaging system extension to connect the test phone to the phone system.

2 Confirm that the phone system identifies DTMF dialing through the test extension.Use the test phone to dial a station phone. The station phone should ring.

3 Confirm that the phone system transmits DTMF tones to the test extension.

Use the test phone to dial a station phone. Have someone answer the station phone and enter a digit. You should hear the tone on the test phone.

Repeat this test for each type of station connected to the phone system. For example, analog, feature set, or operator.

4 Confirm that the test phone can access outside lines.Use the test phone to dial a number outside of the phone system. The technician should reach this number.

5 Confirm that the phone system generates rings on the test extension.Using a station phone to dial the test phone extension. The test phone should ring.

6 Confirm that trunk routing is configured correctly for extensions that answer trunk calls.Use a line outside the phone system to dial the number designated for the messaging system.

Answer the test phone, use a hookflash, then dial a station phone. Listen for ringing, then hang up the test phone. The call should be transferred to the station that was dialed.

7 Check that trunk routing, if supported, is configured correctly for extensions that only answer calls from stations.Use a station phone to dial the test phone extension. Answer the test phone and use a hookflash, then dial a station phone. Listen for ringing, then hang up the test phone. The call should be transferred to the station that was dialed.

NOTE

If you are using digital phones, skip this step.


Selecting a Call Transfer TypeAfter configuring the messaging system, determine which call forwarding and call transfer settings you want and use the appropriate procedure to configure the call transfer settings.

Selecting Call Transfer TypesCall forwarding on the phone system and call transfer on the messaging system must be configured to work together to avoid overlapping features or conflicts.

The phone system and messaging system capabilities, and unsupported features for each call transfer type. Ensure that the associated unsupported features are not required by the subscribers. Use the appropriate procedure to configure call forwarding on the phone system and call transfer on the messaging system.

Configuring Transfer TypesSet the transfer type on the messaging system default subscriber template to set the call transfer type for each new subscriber added to the system.

If subscribers are already enrolled and their settings conflict with the selected transfer type, change the call transfer setting for each existing subscriber.

You can also set the transfer type for System Operator boxes, Transaction boxes, Voice Detect boxes, and Public Fax boxes. For details, see System Administrator Help.


To configure subscriber call transfer settings

1 On the Linux taskbar click the Administration Console icon and sign in to the Administration Console.

2 In the Navigation pane, click Subscribers > Subscribers > Call Transfer or to configure the subscriber template, click Subscribers > Subscriber Template > Call Transfer.

Call Transfer Settings

If you want to… …and do not need… …then use…

Enable the messaging system to handle calls quickly using the phone system call forwarding capabilities.

The messaging system:

● Call holding● Call transfer or screening

options● Message delivery to an

extension. Available if call forwarding-busy and call forwarding-all calls are disabled.

Release transfer.

See “To configure subscriber call transfer settings” on page 48.

Use one or more of the following messaging system options:

● Call holding● Call transfer or

screening options● Message delivery to

an extension

The phone system:

● Call forwarding-busy● Call forwarding-all calls

Await answer.


Use one or both of the following messaging system options, or if your phone system does not support call forwarding-busy:

● Call holding● Message delivery to

an extension

The messaging system call transfer or screening options and the phone system:

● Call forwarding-busy● Call forwarding-all calls

Wait for ringback.



3 Select a transfer type from the Transfer Type list:

● Await Answer. The system transfers the call to the extension if the call is answered within the number of rings specified in the Wait for…rings field. If the subscriber phone is busy or goes unanswered, the system plays the greeting and then takes the after-greeting action.

In the Wait for … rings field, type the number of times the extension rings before the call is transferred. This setting must be one less than the number of rings set on the phone system. The number should not be set to less than three.

If the number of rings is greater than zero, then the Allow holding, VOX holding, and Transfer Options are activated. Select Allow holding to enable call holding. Select the appropriate call transfer settings in the Transfer Options section. Active only if Await answer selected.

● Wait for ringback. The system transfers the call to the extension if a call is answered within the number of rings specified in the Wait for...rings field. If the call is not answered within the specified number of rings, the call is released to the phone system.

In the Wait for … rings field, type the number of times the extension rings before the call is transferred. This setting must be one less than the number of rings set on the phone system. The number should not be set to less than three.

● Release. The system releases the call after dialing the extension or phone number. If the subscriber phone is busy or goes unanswered, the caller can leave a message if the phone system is configured to transfer the call using call forward to personal greeting.

4 Click Save.

Repeat this procedure for each existing subscriber.


To change existing subscriber call transfer settings

1 On the Linux taskbar click the Administration Console icon and sign in to the Administration Console.


2 In the Navigation pane, click Subscribers > Subscribers > Call Transfer.

3 Select a transfer type from the Transfer Type list:

4 Click Save.

Repeat this procedure for each existing subscriber or box.

Next steps…

◆ Change the keypad mapping. See “Changing the Keypad Map” on page 50.

NOTE

The Release transfer type is recommended for the system operator box. However, if the operator console does not support unlimited camp-on calling, use the Await Answer transfer type.


Changing the Keypad MapCallers use the keypad on their touchtone phones to interact with the messaging system. The keypad map determines how the numeric digits on the keypad are mapped to alphabetic letters in the messaging system.

Each digit on the keypad is mapped to letters in the messaging system. Each keypad map has an associated wild card digit. Callers can enter a wildcard digit in place of any letter when they are not sure of the letter.

For example, when using the Q=7, Z=9 keypad map, the digits 7-1-1 represent P, Q, R, or S, followed by any two letters.

The messaging system supports five different keypad maps:

The mapping of digits to letters should match the phone system and the phones of the outside callers. The default keypad map for the messaging system is Q=7, Z=9. Use the following procedure to select a different keypad map.


To change the keypad map

1 Shut down the messaging system.

2 Log on to the Maintenance Menu.

3 Select Command prompt on the Main Menu, then press ENTER.

4 At the Linux command prompt, type

remap

then press ENTER.

5 Type the number for the keypad map, then press ENTER.

6 Type CTRL + D to return to the main menu.


8 Select Control, then press ENTER.

9 Select Restart the messaging system software, then press ENTER.


11 Select Log out, then press ENTER.

Keypad map Wildcard

Q, Z on the 0 (zero) key 1

Q, Z on the 1 key 0

Q=7, Z=9 1

Numerals (numbers only) 1 (groups only)

Cosmos (Sweden) None

Maria suggested that steps 7-9 be removed, but since we told the user to shut down the messaging system in step 1 we should show how to restart it.


8CHAPTER
E-mail Integrations
OverviewThis chapter explains how to set up an e-mail integration and set up e-mail features for subscribers.

Subscribers can use text-to-speech technology to listen to e-mail messages using a phone. E-mail message counts can be included in message counts. All voice messages and faxes can be forwarded to e-mail inboxes.

The e-mail integration provides 24-hour access to e-mail using a touchtone phone. Standard protocols are used to access, read, and send e-mail messages on the messaging system. The protocols for this integration include IMAP and POP3.

The e-mail server must support SMTP and MIME protocols for outgoing e-mail features to work properly.

E-mail ProtocolsThe following standard e-mail protocols ensure the successful transmission of e-mail messages:

● IMAP. Internet Message Access Protocol (IMAP) provides the messaging system access to e-mail inboxes.

The messaging system uses IMAP to obtain e-mail message headers and body information from a variety of e-mail servers. This information is delivered to the text-to-speech engine to convert the text to audio format for playback.

● MIME. Multipurpose Internet Mail Extensions (MIME) provides the messaging system the capability to read e-mail message header and body information.

Multi-part MIME messages enable the e-mail system to send enhanced versions of the message for messaging clients such as Lotus Notes and Microsoft Outlook. Multipart MIME messages contain plain text messages that can be read to subscribers over the phone.

● POP3. Post Office Protocol. POP3 is a standard internet protocol used for retrieving Internet e-mail and is used by the e-mail client to communicate with SMTP mail servers. With POP3 the user name and password are sent across the network in clear text.

● SMTP. Simple Mail Transport Protocol (SMTP) provides the messaging system the capability to send outgoing e-mail messages. The system forwards voice mail and faxes to the e-mail system, generates and sends e-mail notification of new fax/voice mail, and uses voice mail features to reply to e-mail messages. SMTP can be configured to restrict the type of messages sent such as only allowing SMTP mail to be sent to other users on the same domain.

NOTE

Text-to-speech does not support HTML encoded messages. If HTML tags are heard during message playback, the message is skipped. HTML messages must be encoded using multipart MIME for text-to-speech to work properly.

CHAPTER 8: E-MAIL INTEGRATIONS 51

System E-mail Authentication Protocols● PLAIN. PLAIN is a simple clear text password mechanism. The mechanism uses a user

name and password to authenticate users.

● LOGIN. The LOGIN mechanism is a non-standard mechanism, and is similar to the PLAIN mechanism except that LOGIN lacks the support for authorization identities.

● NTLM. NTLM (NT LAN Manager) is a Microsoft authentication protocol used with the Microsoft Windows Network. This protocol uses a challenge response sequence requiring the transmission of three messages between the client and server.

E-mail Integration ConfigurationThe following is a summary of the steps required to set up the e-mail integration.

1 Configure the e-mail server.See “Configuring the E-mail Server” on page 53.

2 Configure the messaging system server.See “Configuring the Messaging System” on page 55.

3 Configure subscriber mailboxes.See “Configuring Subscriber Mailboxes” on page 57.


Configuring the E-mail ServerThe e-mail server must have POP3 or IMAP enabled to use the e-mail integration.

The e-mail server must be configured to properly integrate with the messaging system.

Supported e-mail servers include:

● Microsoft® Exchange Server 2000, 2003, or 2007

● Lotus® Domino™ 6.0, 6.5, or 7.0

● Novell GroupWise™ 6.0, 6.5 or 7.0

To enable POP and IMAP refer to the e-mail server documentation or consult the system administrator about which settings are appropriate for the organization.

To select an authentication method for the e-mail server refer to the e-mail server documentation.

Converting Existing Domino E-mail Files for UsersSet an Internet password for all existing users before converting any existing e-mail files. Use the following procedure to convert user e-mail files.

To convert existing e-mail files

1 Log on to the Domino e-mail server as root user.

2 On the Windows taskbar, click Start > Programs > Lotus Application > Lotus Domino Administration.

3 Type the Domino password.

The Domino Administrator console appears.

4 Click Console to open the Domino server command prompt.

The command prompt appears. Use one of the following set of commands to convert the existing e-mail:

■ To convert a single user, type the following commands:

tell router quitload convert -e mail\<mailfilename>.nsfload convert -h mail\<mailfilename>.nsfload router

where <mailfilename> is the name of the user.

■ To convert all users in a directory, type the following commands:

tell router quitload convert -e mail\*.nsfload convert -h mail\*.nsfload router

Repeat these steps for each user to be converted.

5 Close the Domino Administrator.

6 Log off the Domino server.

WARNING

The e-mail administrator is required to configure the e-mail server.

NOTE

Refer to the appropriate e-mail server documentation to configure the e-mail server.


The Domino server is now configured for e-mail integration.

NOTE

Refer to the appropriate e-mail server documentation to configure the e-mail server.


Configuring the Messaging SystemThe e-mail server must be configured and connected to the messaging system before subscribers can use the e-mail integration.

The following e-mail server information is required to establish communications with the messaging system server:

● The IP address or exact name of the SMTP server.

● The SMTP port number.


To configure the messaging system for e-mail notification


2 Click System > Configuration > E-mail settings.

3 In the Outgoing e-mail server field, type the IP address of the outgoing e-mail server.

4 In the Port field, type the e-mail server port number.

5 Select SSL to use the Secure Sockets Layer protocol.

6 Select Use authentication to specify user credentials when required by the e-mail server.

7 Select the authentication protocol to use in the Authentication list. If Use authentication is not selected this list is not accessible.

8 Type the User name.

9 Type a Password.

10 In the Global e-mail field, type the common e-mail address used for all outgoing e-mail.

11 In the Display name field, type the common display name used for all outgoing e-mail.

12 Click Save.

Next Step…

◆ Configure the e-mail notification template. See “To configure the e-mail notification template” on page 56.

NOTE

If the system is set up to recognize server names, type the server name instead of the IP address.

Selected protocol Port

SMTP 25

IMAP 143

POP3 110

Selected protocol with SSL Port

SMTP with SSL 465

CAUTION

The PLAIN authentication protocol might not be supported by Microsoft Exchange Servers.

NOTE

If the selected Authentication protocol is NTML and the domain name is required, prefix the user name with the appropriate domain name. For example, domain_name\username.



To configure the e-mail notification template


2 Click System > Configuration > E-mail message template. The e-mail message template page appears.

3 The default language is automatically selected in the Language list.

4 To change the language select a different language from the Language list.

5 Type the information in the Subject and Body fields to customize the message.

The content between [brackets] are field labels. These labels are dynamically replaced by content during runtime. For example, [senderName] is replaced by the sender’s name when a message is sent.

6 Click Save.

Next Step…

◆ Configure subscriber mailboxes.See “Configuring Subscriber Mailboxes” on page 57.

Field labels Content description

[senderName] Sender's name.

[senderPhone] Sender's phone.

[senderAccount] Sender's account. Available only if Transfer/Screening is set to Gather account number in the subscriber profile.

[messageTimestamp] Message received timestamp on the messaging system.

Field labels Content description

[messageDuration] Message length in seconds.

[messageSize] Message size in kilobytes.

[messageFlag] Message Special flags: PRIVATE and URGENT.

[voicemailURL] URL of the messaging system.

[subscriberName] Subscriber's name.

[subscriberExtension] Subscriber's extension.

[notificationType] Message notification type.


Configuring Subscriber MailboxesAfter configuring the messaging system server and the e-mail server for the e-mail integration, set up subscribers to access e-mail messages using a phone.

Configuring the Default Subscriber TemplateConfigure the subscriber template for access to e-mail. The subscriber template is used to pre-configure new subscriber settings. Existing subscribers must be configured individually.


To set up the default subscriber template


2 Click Subscribers > Subscriber Template > E-mail.

3 Select an e-mail server type in the Server type list: IMAP or POP3.

4 Select an Authentication Method: Plaintext or NTLM.

This is an authentication method for fetching messages from an IMAP or POP3 e-mail server.

5 Type the messaging system server name, or IP address, in the Server name field.

6 Select SSL if the Secure Sockets Layer protocol is used.

7 The values displayed in the Port field change depending on the Server type selected.

8 Click Save.

Setting Individual Subscriber E-mail OptionsUse the following procedure to change individual subscriber e-mail settings.


To set subscriber e-mail access options


2 Click Subscribers > Subscribers > E-mail.

Use the Next, Previous, or Find Subscriber icons to select a different a subscriber profile.

3 If e-mail notification is selected, type the subscriber’s full e-mail address in the E-mail address. For example: [email protected].

4 Select an e-mail server type in the Server type list: IMAP or POP3

5 Select an Authentication Method: Plaintext or NTLM.

This is an authentication method for fetching messages from an IMAP or POP3 e-mail server.

6 Type the server name, or IP address, in the Server name field.

Selected protocol Port # Selected protocol Port #

IMAP 143 IMAP with SSL 993

POP3 110 POP3 with SSL 995

NOTE

For subscriber e-mail integration to work, the subscriber must have appropriate access options to e-mail messages from voice mail


7 Type the subscriber’s system ID used to attempt authentication with the e-mail server in the User name field.

For example: POP3 access requires a full e-mail address, while Microsoft Exchange server with IMAP does not.

8 Select SSL if the Secure Sockets Layer protocol is used.

9 The values displayed in the Port field change depending on the Server type selected.

10 Select the subscriber Access Options.

See System Administrator Help to change subscriber access options and Access Options for detailed information about the access options.

11 Click Save.

Repeat this procedure for each existing subscriber.

Setting Individual Subscriber E-mail NotificationsUse the following procedure to change individual subscriber e-mail notification settings. When the subscriber Access Options are set to any one of the following, you must provide an e-mail address:

● Receive e-mail notification on new fax/voice mail

● Allow user to change e-mail notification address

● Receive e-mail notification of successful or failed faxes






3 Type the subscriber’s full e-mail address in the E-mail address. where e-mail notifications are sent. For example: [email protected].

4 Click Save.

Configuring Individual Subscriber E-mail Reader SettingsUse the following procedure to change individual subscriber e-mail notification settings. When the subscriber Access Options are set to any one of the following, you must specify the e-mail authentication method on the Subscribers > E-mail page:

● Access e-mail messages from the messaging system

● Forward voice mail to e-mail system

● Forward faxes to the e-mail system

Selected protocol Port # Selected protocol Port #

IMAP 143 IMAP with SSL 993

POP3 110 POP3 with SSL 995

NOTE

For subscriber e-mail integration to work, the subscriber must have appropriate access options to e-mail messages from voice mail.


https://localhost/admin/onlinehelp/Output/11SubscriberMaintenance.12.6.htm#322867

https://localhost/admin/onlinehelp/Output/98Fields.23.3.htm#330645






3 Select an e-mail server type in the Server type list: IMAP or POP3

4 Click Save.


9CHAPTER
Remote Maintenance
Remote Maintenance OverviewRemote maintenance feature enables system managers to troubleshoot and maintain a messaging system using a remote computer. Remote maintenance can be managed over the Internet or through a dial-up connection.

● For Internet access. The messaging system must be connected to a network that provides access to the Internet. The network administrator must program the firewall to enable remote access. To access the messaging system computer remotely, the IP address of the messaging system computer must be statically mapped to an outside IP address on a per IP address basis or per TCP port basis.

● For dial-up access. The messaging system must be connected to an external modem. The remote access software package must be installed and configured on the messaging system server. The remote computer must also be equipped with a modem. Dial-up Networking must be configured on the remote computer with an SSH client installed.

Dial-up Access Configuration Steps

1 Configure the messaging system for remote accessSee “Configuring Dial-up Access” on page 62.

2 Configure the remote computer for dial-up networkingSee “Configuring Dial-up Access” on page 62.

3 Install remote access on the remote computerSee “Configuring Dial-up Access” on page 62.

Network Access Configuration Steps

1 Install remote access on the remote computerSee “Configuring Dial-up Access” on page 62.

2 Configure networkingSee “Configuring the Network” on page 27.

3 Configure the firewallThe procedures to do this depend on the type of network installed at the site and the network topography. This must be configured by the network administrator.

CHAPTER 9: REMOTE MAINTENANCE 61

Configuring Dial-up AccessTo enable dial-up maintenance for the messaging system, an external modem must be installed and configured. The remote access software was installed during the installation of the messaging system.

To configure dial-up networking on a remote computer

This procedure assumes that a modem is installed and correctly configured on the remote computer, and that the remote computer is using Windows 2000/NT/XP with Dial-up Networking. If a different operating system is being used, refer to the that operating system documentation for instructions to configure dial-up networking.

1 Sign in to the remote computer.

2 On the Windows taskbar, click Start > All Programs > Accessories > Communications > Network Connections.

3 Click New Connection Wizard.

4 On the Location window, type the area code, then click OK.

5 On the next screen, click Next.

6 Select Connect to private network, then click Next.

7 Type the phone number that corresponds to the phone line attached to the modem on the messaging system.

If the number is not a local number, select the Use Dialing rules check box to enter the area code and the country code.

8 Click Next.

9 Select the appropriate option.

10 Clear the Enable Internet Sharing check box, then click Next.

11 Type a name for this dial-up connection, then click Finish.

12 Double-click the new connection icon.

The icon is labeled with the name provided in the previous step.

13 On the Networking tab, from the Components list select Internet protocol (TCP/IP), then click Properties.

14 Click Advanced.

The Advanced TCP/IP Properties screen appears.

15 On the General tab clear the Use this connection as the default gateway to the network, then click OK.

16 Click OK to close the TCP/IP Properties screen.

17 Click OK to save and close the Connect to Private Network settings.

NOTE

This dialog box appears the first time only when you configure a Dial-Up Networking connection on the computer.

NOTE

Select Only for myself if the remote computer is shared with persons other than the voice mail administrator.


Configuring TCP/IP on a Remote ComputerA remote computer that is running a different operating system can be used to access the messaging system. The TCP/IP settings on the remote computer must be set to connect to the default IP address for the voice board.

To configure TCP/IP for the remote computer

This procedure assumes that a network card is installed and correctly configured on the remote computer running the Windows XP operating system. This procedure also assumes that the remote computer is connected to the messaging system using a crossover network cable.

Refer to the system documentation for information about configuring the TCP/IP settings for a remote computer that is running a different operating system.

1 On the Windows desktop click Start.

2 Right-click My Network Places and select Properties.

The Network Connections window appears.

3 Right-click Local Area Connection then select Properties.

The Local Area Connection Properties window appears.

4 Double-click Internet Protocol (TCP/IP).

5 On the General tab:

a Select Use the following IP address.

b Type 169.254.0.5 in the IP address field.

c Type 255.255.0.0 in the Subnet mask field.

d Leave the Default gateway field blank.

e Click OK.

The Internet Protocol properties dialog box closes.

6 Click OK to close the Local Area Connection Properties window.

Next Step…

◆ Install WinSCP and PuTTY. See “Installing WinSCP and PuTTY” on page 64.


Installing WinSCP and PuTTYWinSCP is used to transfer files and PuTTY (telnet and secure shell client) is used for secure shell terminal access. WinSCP and PuTTY are PC-based applications that can be installed on the remote computer.

WinSCP is a SFTP (SSH File Transfer Protocol) and SCP (Secure CoPy) client for Windows that uses SSH (Secure SHell). The main function of WinSCP is to provide safe copying of files between local and remote computers in a secure environment.

You can download WinSCP and PuTTY from the Internet or install them from the Installation disc. WinSCP and PuTTY have been tested and approved for use with the messaging system.

Installing the ClientsThe following procedures assume that WinSCP and PuTTY are being installed on a PC-based computer system.

To install the WinSCP client on a remote computer

1 Insert the Installation disc into the disc drive.

2 Browse to the …/Utilities/RemoteAccess/WinSCP directory.

3 Double-click the WinSCP setup executable file.

4 On the Welcome to WinSCP screen, click Next.

5 On the License Agreement screen, select I accept the agreement then click Next.


7 Accept the default components, then click Next.


9 Accept the default additional settings, then click Next.

10 Select a user interface style, then click Next.

11 Verify that the settings are correct, then click Install. The installation process begins.

12 Clear the Start WinSCP now check box, then click Finish.

To install the PuTTY client on a remote computer


2 Browse to the …/Utilities/RemoteAccess/PuTTY directory.

3 Double-click the PuTTY setup executable file.

4 After PuTTY is installed, from the Windows taskbar, click Start > Programs > PuTTY > PuTTY. The PuTTY Configuration screen appears.

Connecting to the Messaging SystemWinSCP is a SSH tool used to transfer files between Linux and a remote computer. PuTTY is used for remote SSH terminal access.

To connect to the messaging system using WinSCP

1 If you are using a dial-up connection, go to 2. If you are using a network connection, go to step 6.

2 On the Windows Desktop, double-click the Dial-up connection icon.

The Connect screen appears.

3 In the User name field, type admin.



The default password is voicemail.

5 Click Dial. The modem dials the phone number. If the connection is successful, a small icon with two flashing computers appears in the Windows taskbar.

6 On the desktop, double-click the WinSCP icon, or click Start > Programs > WinSCP3 > WinSCP on the taskbar.

The Login window appears.

7 In the Host name field, type the name or IP address of the messaging system server.

8 In the User name field, type the appropriate log on name.


10 Under Protocol, select SFTP (allow SCP fallback).

11 Click Login.

When the first connection is made, a warning screen appears. This screen does not appear for subsequent connections.

12 Click Yes. After authentication is complete, the File Transfer screen appears.

Transferring FilesUse WinSCP to transfer files between the messaging system and the remote computer.

To transfer files using WinSCP

Use this procedure to transfer files from the messaging system server to the remote computer.

1 Select the file or files to copy.

2 Right-click the file name, then select Copy. Alternatively, drag and drop the files.

3 To transfer files from the remote computer to the messaging system server, select the file or files to copy.

4 Click Files > Copy, then click Copy. Alternatively, drag and drop the files.

Opening a Terminal WindowA terminal or command window can be opened using PuTTY:

❚ Double-click the PuTTY icon on the desktop or click Start > All Programs > PuTTY > PuTTY.

Changing the UNIVERGE UM4730 Admin PasswordChanging the admin password secures the computer at the operating system level. The system manager should take additional steps to secure UNIVERGE UM4730 at the messaging system software level. Refer to System Administrator Help for additional information.


To change the admin password

Use this procedure to change the admin password. The procedure assumes that you are logged on as admin or have permissions to change the admin password.

1 On the Maintenance Menu, select Maintenance then press ENTER.

The System maintenance menu appears.

CAUTION!

You must use the IP address when using a dial-up connection.


2 On the System maintenance menu, select Set admin password then press ENTER.

The Set admin password window appears.

3 Type the new password then press ENTER.

4 When prompted, retype the new password then press ENTER.

A message appears stating that the password has been changed.

5 Click OK to return to the System maintenance menu.

6 Select Return to previous menu then press ENTER to return to the Maintenance Menu.

7 Select Log out then press ENTER to log out and close the PuTTY window.

Logging Out of the Maintenance Menu and PuTTYUse one of the following procedures to log off from the Maintenance Menu and close the PuTTY session.

To log off using PuTTY

❚ Click Log Out then press ENTER.


10CHAPTER
Backing Up and Restoring Data
Backing Up the Messaging SystemBack up the messaging system and data on a regular basis by using the back up utility. Backup files are saved with the zip file extension. Backups can also include messages.

Use the restore utility to restore data from back ups. The backup/restore utilities are part of the Administration Console.

Types of Backups● Immediate. Manual back up that immediately backs up the messaging system.

Optionally includes messages. The messaging system must be running to create the online back up.

● Scheduled. Backs up the messaging system, and optionally messages, daily at the time you specify.


To immediately backup the messaging system

1 On the Linux desktop, double-click Administration Console to start the administrator tool.

2 Sign in as $nec.

3 In the Navigation pane, click System > Backup & Restore > Backup.

4 On the Backup page, clear the Enable daily backup and Include messages in backup check boxes.

5 Under Manual Backup, select Include messages in backup to include messages.

6 Select a destination from the Destination list box:

● Hard Drive. Save the backup file to a hard drive on the messaging system server.

● Windows Shared Folder. Save the backup files to a Windows network share. Refer to MS Windows documentation for detailed information setting up a Windows share folder.

◆ Type a Server path.

◆ Type a User name.

◆ Type a Password.

7 Type a File name.

8 Type a Backup Note.

9 Click Backup Now to start the backup.

A progress bar appears. When the back up is complete, the progress bar shows 100% complete.

CHAPTER 10: BACKING UP AND RESTORING DATA 67


To schedule daily backups

Schedule daily backups to occur at the same time every day and in the specified location. The file name is automatically generated using the system date and time. For example, vmbackup-2007090620002.zip.

1 On the Linux desktop, double-click the Administration Console icon.

2 Sign in as $nec.

The messaging system Administration Console page appears.

3 In the Navigation pane, click System > Backup & Restore > Backup.

4 Select the Enable daily backup at checkbox.

5 Specify the time of day for the backup.

6 Select Include messages in backup to include messages in the back up.

7 Select a destination in the Destination list:

● Hard Drive. Save the backup file to a hard drive on the messaging system server.

● Windows Shared Folder. Save the backup files to a Windows shared folder. Refer to MS Windows documentation for detailed information setting up a Windows share.

◆ Type a Server path.

◆ Type a User name.

◆ Type a Password.

8 Click Save. The backup runs at the time you specified.


Restoring Back Up FilesThe restore utility is available in the Administration Console.


To restore back up data

1 On the Linux taskbar, click the Administration Console icon.

2 Sign in as $nec.

3 In the Navigation pane, click System > Backup & Restore > Restore.

The Restore page appears.

4 Stop the messaging system,

a Click Stop the messaging system. If the messaging system is not running, skip this step.

The Server Control page appears.

b Click Stop, then return to the Restore page.

5 If the backup file is not listed on the Restore page, click Browse to browse for and select a backup file.

6 Click Upload File to add the file to the list.

7 Select one action from the Action drop-down list:

● View backup note. Click to display the backup note, then click OK to close the message alert.

● Delete. Click to delete the backup file. Click OK to confirm the deletion.

● Download. Click to download the backup file. Click Save to save the back up file and add it to the list of backup files.

● Restore this backup. Click to restore the backup file.

8 Click OK to confirm you want to restore the file.

9 Click OK once again to restore the messages. This confirmation prompt appears only if the backup file includes messages.

A restore progress bar appears.

NOTE

The messaging system software must be stopped to restore data.

CHAPTER 10: BACKING UP AND RESTORING DATA 69

AAPPENDIX
Using the Messaging System
Sign In and Signing Out of the DesktopThe messaging system requires you to sign in as a system manager before you can change any system settings. Use the following procedures to sign in to and to sign out of the messaging system server.

To sign in to the operating system

1 Restart the messaging system server.

2 On the Welcome to Vmail dialog box, type your sign in name, then click OK.

The Start Again button clears the user name field. This enables you to type a different user name.

3 Type your password, then click OK.


To log off the Linux desktop

❚ Click Quit on the lower right-hand corner of the desktop. Click Log Out, Restart, Shut Down, or Cancel.

Status iconMaintenance Menu icon

Administration Console

APPENDIX A: USING THE MESSAGING SYSTEM 71

The Administration Console Main MenuMany of the Administration Console pages are divided into four sections.

The Administration Console IconsThe task bar in the Administration Console contains one or more command icons at the top. These perform the following functions:

a Title bar. Contains the application name, the link to the Administration Console Main Menu, and page/record information

b Return to Main Menu. Click to return to the Main Menu.c Expand All. Click to expand all of the links.

Collapse All. Click to collapse all of the links in the Navigation pane.d Taskbar. Contains the command icons, user logon information, and the

logoff link.e Navigation pane. Contains links to other Administration Console

pages.f Page. Contains fields where data is entered and displayed.g Version. The current version appears on the Main Menu. h Important Information. Click this link to read additional information

about the administrator tool.

Icon Description

SaveSave changes.

FindSearch for items of the type you are currently viewing.

AddAdd items of the type you are currently viewing.

DeleteDelete items of the type you are currently viewing.

PreviousView the previous record.

NextView the next record.

HelpOpen System Administrator Help.

RunClick to run a report or other Web administration console application.

a

d e

bc

d

g

h


The Administration Console Main MenuWhen the Administration Console starts the Main menu appears in the Navigation pane.

The Navigation pane is located on the left side of each system page. The Navigation pane has links to the Administration Console web pages.

Each link in the Navigation pane might contain one or more pages. These links can be expanded or collapsed. To move to a page, click the link in the Navigation pane. Some links contain multiple pages of related settings.

● Quick Links. Quick links to frequently accessed pages.

● Subscribers. Use these pages to configure settings for individual subscribers and guests, and to create subscriber templates. Settings include schedules, passwords, account permissions, phone greetings, call processing, and transfer options.

● Call Management. Use these pages to specify how UM4730 answers, routes, transfers, and records calls.

Settings include call handling settings for the operator, opening greeting, any routing applications and menus, languages, and voice detect applications.

● Groups. Use these pages to configure or create message and directory groups.

● Hotel Guests. Use these pages to configure settings for hotel guests. Settings include greetings, passwords, wake-up calls, call handling, and message waiting notification.

● Reports. Use the Reports pages to generate reports of subscriber-based or system-based information, including message activity, message groups, phone sign-ins, disk storage, administration access, port usage, and software information.

● Network. Use the network pages to add and view locations within a messaging system network.

● System. Use the System pages to set general information about the messaging system, such as site contact information, message storage and playback settings, system prompts, schedules, port settings, and phone system integration.

● Port Status. Use Port Status page to view the current activity and status of each port or incoming phone line.

● Server Control. Use the Server Control page to start or stop the messaging system software.

Signing in to the Administration ConsoleUse the following procedure to sign in to the Administration Console. using a personal computer. An alternative is to use a monitor and keyboard attached to the messaging system.

To sign in to the Administration Console

1 Make sure the messaging system is running.

2 Start a Web browser and click File > Open.

The Open dialog box appears.

Subscribers Links to subscriber profile page.

Port Status Displays port status page.

Server Control Displays server control page.

NOTE

The hotel guest pages are only available if the optional hospitality package is installed.

NOTE

The network pages are only available if the optional networking package is installed.


3 Type the Administration Console URL:

http://<IP address>/

where <IP address> is the messaging system server IP address.

4 Click OK.

5 If appropriate, select a different language.

6 Type a system manager ID in the User field.

7 In the Password field, type the appropriate security code.

8 Click Login.

The Administration Console appears.

Signing Out of the Administration ConsoleSign out of the Administration Console using the following procedure.

To sign out of the Administration Console

❚ Click Sign Out on the taskbar any page.

System manager ID

New system $nec

Existing system personal ID

Password

New system leave password field blank

Existing system type the administrator password


Using the Maintenance Menu The Maintenance Menu provides a command line user interface used to:

● configure the messaging system network configuration

● set the messaging system date and time and time zone.

● run the Global Tone Detection utility.

● set the admin password.

● restore the default database.

● start and stop the messaging system software.

● shut down the messaging system server.

Accessing the Maintenance Menu There are two ways to log on and use the Maintenance Menu. Log on at the messaging system server or log on using a remote computer.

Use the following procedure to run the Maintenance Menu on the messaging system server.

To log on to the Maintenance Menu

1 If the system is shut down, restart it.

The messaging system VMail log on page appears.

2 Log on as admin, then click OK.



4 On the taskbar, click the Maintenance Menu icon. The Maintenance Menu appears.

After you have successfully logged on to the messaging system server using the command prompt, the Maintenance Menu appears:

The Maintenance Menu has four menu options:

● Configuration. Use the network menu to configure the messaging system network configuration, set the date, time, and timezone, or use the Global Tone Detection utility.

● Maintenance. Use this menu to change the administrator password, open a command prompt window, or restore the default database that shipped with the messaging system.

● Control. Use this menu to stop the messaging system software, stop the messaging system server, or restart the messaging system server.

● Log out. Use to log out and close the Maintenance Menu.

NOTE



To remotely log on to the Maintenance Menu

Use this procedure to log on to the messaging system server from a remote computer.

1 Run PuTTY on the remote computer.

2 Log on as admin, then click OK.


The Maintenance Menu Main menu appears.

To log out of the Maintenance Menu

1 Go to the Main Menu

2 Select Log Out, then click OK.

The Maintenance Menu window closes.


Using the Administration ConsoleThe Administration Console (formerly called Web Administration Console) is the graphical user interface (GUI) for the messaging system. The messaging system manager uses this Web-based application to configure the messaging system, create a subscriber template, add subscribers, and manage other messaging system related activities. Refer to System Administrator Help for detailed information about each page of the application.

Using the Administration Console the First TimeThe Administration Console is a tool used by system administrators to manage the messaging system. The first time you sign in, licensing information appears.


To sign in the first time

This procedure is for new installations only and is only used once. The first time you sign in after an installation the licensing agreements appear. You must accept these licenses before the application appears.


The messaging system VMail log on dialog box appears.

2 Type your user name, then click OK.

3 Type your password, then click Login.


4 On the desktop, double-click the Administration Console icon.

The Administration Console sign in page appears.

NOTE



5 Type the user name $nec, then click Sign in.

The activate licensing page appears:

a Click Browse to locate the Security Key file.

b Select the file, then click OK.

c Click Save.

The License page appears. Read the Terms and Conditions.

6 Click I Accept.

After all of the licenses have been accepted, the Switch Information page appears.

7 Select an appropriate switch from the Switch list. The Integration options field is automatically filled.

See “Selecting the Phone System Integration” on page 43.


8 Click Save.


9 Click Edit All to type the Extension number for each port.

10 Click Save.

The Administration Console Main Menu appears.

NOTE

The example above shows the Switch Extensions page for an IP integration, the Password column is not available in digital and analog integrations


Signing In to the Administration ConsoleThis procedure is used to sign in to the Administration Console after the first time sign in.


To sign in to the Administration Console


The messaging system VMail sign in page appears.

2 Type your user name, then click OK.

3 Type your password, then click Login.


4 Double-click the Administration Console icon.

5 Type the user name $nec, then click Login.

The Administration Console startup page appears.


To log off the Administration Console

❚ Click Sign Out at the top right-hand corner on any page, then close the Web browser.

Closing the Web browser ensures that another user cannot log in using your credentials.

NOTE



Stopping the Messaging System SoftwareSome procedures require that the messaging system software is shut down.

The messaging system can be stopped using the Administration Console or the Maintenance Menu from any networked computer. Using the Maintenance Menu is the preferred tool to use.


To stop the messaging system software

1 On the Linux taskbar, click the Maintenance Menu icon.

2 Log in as admin.


4 Select Stop messaging system software, then press ENTER.

The messaging system shuts down each port as it becomes available, then shuts down the software. This might take a few minutes.





To stop the messaging system software



3 In the Navigation pane, click Server Control.

4 Click Stop to shut down the messaging system.

The messaging system shuts down each port as it becomes available then shuts down the software. This might take a few minutes.


Restarting the Messaging System SoftwareYou can restart the messaging system from any networked computer using the Administration Console or the Maintenance Menu.

If the system does not restart properly, or if the system is behaving erratically, you might need to shut down and restart the operating system. See “Shutdown and Restart the Linux Operating System” on page 84.


To start the messaging system software

1 On the Linux taskbar, click the Maintenance Menu icon


3 Select Restart messaging system software, then press ENTER.

The messaging system might take more than 30 seconds to restart.





To start the messaging system software




4 Click Start to restart the messaging system.

The messaging system might take more than 30 seconds to restart.


Using the System Status IconThe messaging system displays a system status icon in the Linux desktop system tray. This icon can also be used to start and stop the messaging system.

To stop the messaging system on the server

1 On the Linux desktop, click the Status icon in the system tray.

2 Click Stop the voice messaging software.

When asked to confirm that you want to stop the messaging system, click Yes.

3 The system shuts down each port as it becomes available, then shuts down the software.

The messaging system might take more than 60 seconds to completely shut down.

To start the messaging system at the server

1 On the Linux desktop, click the Status icon in the system tray.

2 Click Start the voice messaging system.

When asked to confirm that you want to start voice mail, click Yes.

The messaging system might take more than 60 seconds to start.

Status Icon

Icon in starting or stopping

mode.


Shutdown and Restart the Linux Operating SystemThe Linux operating system can only be shut down at the messaging system server. Use the command prompt to shut down the operating system.


To shut down the Linux operating system

1 Log on to the Maintenance Menu as Admin.


3 Select Shut down messaging system server, then press ENTER.


To restart the Linux operating system

1 Log on to the Maintenance Menu as Admin.


3 Select Restart messaging system server, then press ENTER.

To shut down Linux from the system tray

1 Click Quit on the lower right-hand corner of the desktop.

2 Select Shut Down, then press ENTER.


BAPPENDIX
Updating the Messaging
System

OverviewUpdating the messaging system includes installing new languages, installing additional ports, applying patches or hot fixes, or installing a new version of the messaging system software.

A new activation code is required to add new messaging system software language packs or additional voice ports. The activation code is based on the voice board System Identification Number (SIN).

Contact your sales representative to give the representative your SIN. Your sales representative obtains a new activation code and sends it to you.

This appendix describes the steps to update an existing messaging system. Updates include the following:

● Installing new hardware.

● Installing a newer version of the messaging system software.

Migrating Existing Messaging Systems to a New ServerProcedures for migrating from older existing messaging systems to the new server are available as follows:

◆ Migrating from AD-40 based systemsSee “Migrating from AD-64 Messaging Systems” on page 111.

◆ Migrating from AD-64 based systemsSee “Migrating from AD-64 Messaging Systems” on page 111.

◆ Migrating from DOS based systemsSee “Migrating from OS/2 Messaging Systems” on page 117.

◆ Migrating from O/S 2 based systemsSee “Migrating from OS/2 Messaging Systems” on page 117.

Updating an Existing Messaging SystemTo update an existing messaging system, you need a current back up of the system data. This back up should include voice messages.

◆ To update the from a previous versionSee “Updating the Messaging System” on page 85.

◆ To add new features to the messaging systemSee “Verifying and Changing Licensing Information” on page 86.

◆ To change or add one or more languagesSee “Adding and Removing Language Packs” on page 87.

◆ To restore a database and voice messages See “Restoring the Database and Voice Messages” on page 92.

Use the following procedure to verify current licensing information and to copy new licensing information.

APPENDIX B: UPDATING THE MESSAGING SYSTEM 85

Verifying and Changing Licensing InformationLicensing information for the messaging system is accessible using the Administration Console.

Verifying Licensing InformationUse the following procedure to verify the current licensing status for the messaging system. The licensing page provides the following information:


To verify license information

1 Log on to the messaging system server using the same rights. used to install the operating system.



4 In the Navigation pane, click System > Licensing.

The messaging system licensing page appears. Existing license information is shown on this page.

Changing Licensing Information Use the following procedure to verify current licensing information and to copy new licensing information.


To change license information



3 In the Navigation pane, click System > Licensing.

The messaging system licensing page appears. Existing license information is shown on this page.

4 Copy the new licensing information from the new Security Key file into the License text box.

Alternatively, click Browse to browse for the license file.

5 Click Save.

6 When prompted, restart the messaging system.

● Number of seats

● Number of system languages

● Hospitality languages

● Fax ports

● Voice ports

● Text-to-speech seats

● Automatic speech recognition seats

● Integration licensing

● AMIS/PlusNet

● Hospitality feature


Adding and Removing Language PacksThe following procedures enable you to install new language packs or TTS languages, when available, and remove existing language packs.


To install new language packs



3 In the Navigation pane, click System > Configuration > Languages.

The Languages page appears. The installed System and Hospitality language packs appear on the page. The following is a list of the language files and their corresponding soft keys.

4 Click Browse.

The Choose file dialog box appears.

5 In the Choose file dialog box, browse to the location where the language packs are installed.

6 Select the language file.

NOTE

The solid state language disc for the SV8100 and SV8300 phone systems contains prompt sets for three languages in Australia, Europe, United States and most of Asia.

There is only one SV8300 language pack for Japan.

Language Soft Key Loaded

Argentinian Spanish English

Australian English English

Catalan Spanish Catalan

Cantonese English

German German

Danish English

Madrid Spanish Spanish

Mexican Spanish Mexican Spanish

Canadian French French

Parisian French French

Hebrew English

Italian Italian

Japanese Japanese

Latin American Spanish Spanish

Mandarin Chinese English

Dutch Dutch

New Zealand English English

Iberian Portuguese Portuguese

Brazilian Portuguese Portuguese

Russian English

Swedish English

UK English English

US English English


7 Click Open.

The Choose file dialog box closes and the Install Language button appears on the Languages page.

8 Click Install Language.

The Updating… button appears. It takes a few minutes for the language pack to install.

The list of installed languages is updated when the installation is complete. The following message appears when the language has been installed:

9 Click Restart to restart the messaging system.

The Server control page appears and both the Start and Stop buttons are grayed out while the server shuts down.

Removing Language PacksUse the following procedure to remove language packs from the messaging system.


To remove language packs


2 On the Linux taskbar click the Administration Console icon.

The Administration Console appears.



The Server control page appears.

5 Click Stop.

Wait for messaging system software to stop.

6 In the Navigation pane, click System > Configuration > Languages.

The installed language packs appear on the languages page.

7 To remove a language, click the Remove next to the language.


The Server control page appears.

9 On the Server Control page, click Start to restart the messaging system.

Changes to the voice messaging system have been made. This requires the voice messaging software to be restarted. Restart the voice mail software after all system changes have been completed.

NOTE

The voice messaging software must be stopped to remove language packs.


Updating the Messaging SystemMessaging system software updates are available for download at the Active Voice Support FTP site. When an update is available for download, the Active Voice Support team sends notifications out with the URL and log on information.

Updates for the messaging system software are made available as files that can be downloaded and installed. Notifications are sent when an update is available to be downloaded. You will download the update file from a specified source save it to a GUI (Graphical User Interface)-based operating system such as Windows XP or Linux with a GUI.

Downloading and Installing the Update FileUse a client computer that is running an operating system that offers a graphical user interface such as Windows XP or a Linux operating system that has a similar user interface.


To download and install updates


2 In the Navigation Pane, click System > Update.

The Updates page appears.

3 Click Upload Update/Hotfix, the Choose file dialog box appears.

4 In the Choose file dialog box:

a Browse to the location where the update file is located.

b Double-click the update file name.

The update might take a few minutes depending on the network connection.

5 After the upload is completed, the update file appears in the table of available updates.

The Automatic Updates table provides the following information about the update:

● Package. File name of the update file.

● Status. States whether the update file has been installed or not.

● Description. Describes what the update will do.

● Install. Contains a check mark which denotes that the update has been installed or a checkbox that can be selected to install the update.

6 Click Install to install the selected update.

WARNING!

The messaging system software must be registered or you will not be able to download the updates.

NOTE

Only one update can be installed at a time.

Is the AV Support FTP site still active - what about NECAM site?


A progress page for the update appears.

The following two scenarios might happen:

■ If the update fails, you are notified that the update failed with a reason for the failure.

■ If the update successfully completes, you are notified that the update was successful and a Restart Now button appears.


7 Click Restart Now to restart the messaging system.

When the messaging system restarts, the System > Update page status shows that the update has been applied.


Restoring the Database and Voice MessagesThe new version of the messaging system is installed with the default database. Use the following procedure to restore an old database and voice messages.


To restore files from disks to the messaging system


2 Log on to the Administration Console as $nec.




6 Click Stop.

Wait for the messaging system to stop.


8 If the backup file is not listed on the Restore page, click Upload File to search for and select the back up file.

9 Select one of the following from the Action list:

● View backup note. Select to display the backup note, then click OK to close the note.

● Delete. Select to delete the backup file from the hard drive. Click OK to confirm the deletion.

● Download. Select to download the backup file. Click Save to select a destination and save the back up file.

● Restore this backup. Select to restore the backup file.

An alert message appears asking you to confirm the restore.

10 Click OK to restore the file, or click Cancel to select a different file.

An alert message appears asking if you want to restore messages.

11 Click OK.

The Restoring Backup progress window appears.

Importing and Exporting DataUse the following procedure to import messaging system or to export messaging system data.


To import or export data



3 In the Navigation pane, click System > Import & Export > Import.

The Import page appears.

NOTE

Make sure that all users are logged out of the messaging system.


4 Select the type of data to import.

5 Select the Separator from the list box.

Separators can be a period (.), comma (,), or tab character.

6 If the file has a header row, select Header row. If the file does not contain a header row, clear the Header row check box.

7 Specify the file location. Click Browse to browse for the file location.

The Choose file dialog box appears. Locate the file, select it, and click Next. The Choose file dialog box closes.

8 Review the sample data and mapping dialog box, then click Import.


CAPPENDIX
Migrating from AD-40
Messaging Systems

Migrating DataIf you are replacing an existing messaging system server with a PC-based system, you need to migrate data from the existing system to the current system.

This appendix describes the steps required to migrate an existing messaging system to a PC-based messaging system.

Reviewing Migration Methods● Migrating with disks or USB flash drives. Only the database, subscriber data,

subscriber system settings, transaction boxes, interview boxes, and groups are transferred to the new system.

● Migrating with a network, shared drive, or direct connection. You can transfer messages, voice names, and greetings, as well as the subscribers, subscriber system settings, general system settings, transaction boxes, interview boxes, and groups.

To migrate using a network or a shared drive, the existing system must be connected to the network or a PC-based computer and have access to a network with a shared drive that has sufficient space to store the data.

Selecting a Migration MethodSelect one of the following migration methods:

● Network or shared drive. The existing system is already connected to a local network. See “Backing up OS/2 Database Using a Network Connection” on page 98.

● Network or shared drive. The existing system is not connected to a local network, is running version 7.49 or lower, and is equipped with an Ethernet NIC. See “To back up the OS/2 database messages only” on page 97 or “To back up the OS/2 database messages and log files” on page 98.

● Direct connect. The existing system is not connected to a local network but can be equipped with a 10/100-baseT Ethernet network interface card (NIC), and is running version 7.50 or higher with OS/2 Warp 4. See “Backing up OS/2 Data with a Direct Connection” on page 98.

● USB flash drive or floppy disk. The existing system is not connected to a local network, and there is no OS/2-compatible Ethernet NIC available. See “To back up database files to disks” on page 97

CAUTION!

Make sure that the languages and language configurations are identical on both messaging systems.

APPENDIX C: MIGRATING FROM AD-40 MESSAGING SYSTEMS 95

Migrating from NEAXMail® AD-64

1 Configure the new messaging system server.See “Configuring the Messaging System” on page 27.

2 Migrate from the OS/2 server.■ See “Migrating from OS/2 Messaging Systems” on page 121.

3 Migrate the data to the Linux server.See “Restoring Back Up Files” on page 69.

4 Set up the phone system integration.See “Configuring the Basic Integration” on page 41 for more information.


Backing Up OS/2 Data to DisksWhen migrating with disks, only the subscribers, system settings, transaction boxes, interview boxes, and groups are backed up. Other data, such as prompts, messages, voice names, and greetings are not included in the backup.

To back up the OS/2 database messages only

Use this procedure to backup only the voice messages.

1 On the NEAXMail AD-40 system, double-click Voice Mail Utilities.

2 With the messaging system running, double-click Online Backup Utility.

3 Click Backup > Schedule Backup.

The Online Backup Scheduler appears.

4 Click the Immediate tab.

5 Specify a name for the backup.

6 In the Contents field, select the Messages check box.

7 In the Destination section, select Path and type the full path name.

8 Select Enable backup, then click Save.

9 Click Close to close the Online Backup Scheduler window.

The Immediate backup in progress message appears.

10 After the backup is complete, close the Online Backup Scheduler.

11 Double-click the OS/2 Window icon on the OS/2 desktop.

12 At the OS/2 command prompt, type

cd d:\backup

then press ENTER.

13 At the OS/2 command prompt, type

dir $_backup.ini

then press ENTER.

If the file does not appear, your back up has failed due to lack of sufficient disk space. Delete the older back up and log files then repeat this procedure.

To back up database files to disks

1 Insert the O/S2 Installation disc into the disk drive.

2 Copy the O/S2 Installation disc \Packages\Migration directory to the specified hard drive.

At the OS/2 command prompt, type:

copy <drive letter>:\Packages\Migration *.* A:\

Where <drive letter> is the disc drive.

3 Put the floppy disk into the disk drive.

4 At the messaging system console, double-click OS/2 Window.

NOTE

Several blank formatted disks are necessary for this procedure.


5 At the OS/2 command prompt, type:

a:\dbpack.cmd

then press ENTER.

6 Follow the on-screen instructions.

Backing up OS/2 Database Using a Network Connection Use the following procedure to back up an OS/2 database messages and log files.

To back up the OS/2 database messages and log files

1 On a NEAXMail AD-40 system, double-click Voice Mail Utilities.

2 Double-click Online Backup Utility.

3 Click Backup > Schedule Backup.

4 Click the Immediate tab.


6 Select the Messages, and Logs check boxes.

7 Under Destination, select Path. In the path field, type a directory name of the network or the shared drive where the backup files are stored, for example, S:\Upgrade. A root directory cannot be backed up.

8 Select Enable backup, then click Save.

9 Click Close.

The Online Backup Scheduler window is closed and the Immediate backup in progress message appears.

Backing up OS/2 Data with a Direct ConnectionWhen migrating OS/2 data using a direct connection, you can include messages, voice names, greetings, subscribers, system settings, transaction boxes, interview boxes, and groups.

Connect the OS/2 system to a network if it is not already connected. See “Installing Network Protocols” on page 100.

To back up the OS/2 database with the Online Backup Utility

1 On the OS/2 system, double-click Voice Mail Utilities.

2 While the messaging system is running, double-click Online Backup Utility.

3 Go to Backup > Schedule Backup.

4 Select the Immediate tab.


6 Select Messages and Logs.

7 In the Destination section, select Path.

8 Type a directory name on the local hard disk where the back up files will be stored.

9 Select Enable backup.

NOTE

Close the first DBPack window to view the next DBPkg window with instructions.

NOTE

To enable the backup, network protocols must be installed. For installation instructions, see “Installing network protocols,” on page 97.


10 Click Save.

11 Close the Online Backup Scheduler window.

The backup in progress alert appears.

After the backup is complete you are ready to migrate the data to the new messaging system. See “Restoring Back Up Files” on page 69.

To configure the OS/2 FTP server

Use this procedure to configure the OS/2 FTP server to transfer the backup files to the new system.

1 On the OS/2 FTP Server command prompt, type:

tcpcfg

then press ENTER.

2 On the Security tab under FTP access protection, add a new user. Select a username, a password, and enable access to the E:\backup directory.

3 Write down the IP address of the system.

4 Select Close and Save.


ftp

then press ENTER.


Installing Network ProtocolsTo backup an OS/2-based messaging system using a network or a direct connection to a Windows system requires network protocols to be configured.

If you have not set up the networking protocols, see “Installing Network Protocols” on page 100. Before you begin, review the network back up requirements.

Network Backup RequirementsA TCP/IP or NetBIOS over TCP/IP configuration is required for an OS/2-based network backup. You do not need an activation code or upgrade code to backup the messaging system data.

Ask the network administrator for the following information and/or assistance:

● For NetBIOS over TCP/IP. Configure TCP/IP and specify a Windows network domain name.

If there is no domain, use the procedure in “Configuring a Remote Windows Computer for a Backup” and use a Windows Workgroup name.

● For TCP/IP. Provide the subnet mask, router, domain name, server name, and the TCP/IP address of the OS/2-based messaging system.

● For a network backup. Set up the system to log on to the network using a Windows NT network with NetBios over TCP/IP or a Novell NetWare network.

Refer to “Configuring NEAXMail AD-40 to Log On to a Network” on page 103.

Set up the Windows system to share a drive with the OS/2-based messaging system. See “Configuring a Remote Windows Computer for a Backup” on page 105.

The Windows system should be set up as a workgroup environment with a unique TCP/IP address.

Direct Connection Backup RequirementsA 10/100-baseT Ethernet NIC is required for both OS/2 and Linux systems. Install a CAT-5 cross-over LAN cable between the NEAXMail AD-40 system and the Linux system, or use a network hub and a regular CAT-5 LAN cable.

If the NEAXMail AD-40 system was never connected to the existing network use the following procedure set up a network connection.

To install network protocols for a network or a direct connection backup

1 Shut down the NEAXMail AD-40 software and OS/2 host software, then exit to the OS/2 desktop.

2 Insert the OS/2 Warp 4.0 disc into the disc drive.

3 On the desktop, double-click OS/2 Window.

4 At the command prompt, change the directory to the disc drive.

5 Type install then press ENTER.

6 On the OS/2 Warp Installation window, click Next.

7 Confirm that the C Drive is selected, then click OK.

8 On the Installing IBM OS/2 Warp window, click Advanced Installation, then click Next.

9 In the OS/2 Warp Setup and Installation window, select File and Print Client, then click Next.

NOTE

The NEAXMail AD-40 system should be assigned a unique IP address in the same network as the PC-based system.


10 In the Configuration window, click the icon next to File and Print Sharing services then use the following steps in the File and Print Client dialog box:

a In the Installation drive field, select drive C.

b Type the OS/2 Workstation name.

Use vserver or the default name assigned to the workstation when the NEAXMail AD-40 software was installed.

c Type a description for the OS/2 workstation. For example,NeaxMail.

d Type the domain name for the network connection or the workgroup name for a direct connection. Create one if necessary.

e Verify that the LAN server administration and Install Sharing check boxes are selected.

f Verify that the Delete User ID database check box is not selected.

11 On the Configuration window, click the icon next to the User ID and Password field:

● For a network connection. Type the logon name and password, then type the password in the Verify Password field.

● For a direct connection. Type the name of the shared drive on the Windows system, then type the password for the shared drive and confirm.

12 On the Configuration window, click the icon next to Network adapters and protocol services, then:

■ Confirm that the IBM TCP/IP protocol appears. If it does not, install and set up this protocol.

aExit the OS/2 Warp setup and Installation window.

Refer to the NEAXMail AD-40 Installation Guide installation instructions for the TCP/IP protocol.

bClick Add Protocol, select IBM OS/2 NetBIOS over TCP/IP from the list of protocols, then click OK.

■ If the IBM OS/2 NetBios protocol appears, select it then click Remove.

13 On the Configuration window, click Install, then follow the on-screen instructions to complete the installation.

14 Leave the OS/2 disc in the disc drive.

15 Shut down and restart OS/2.

To set up Multi-Protocol Transport Service (MPTS)

1 When the OS/2 system restarts, shut down the NEAXMail AD-40 and the host software, then exit to the OS/2 desktop.

2 On the OS/2 desktop, double-click OS/2 system.

3 Double-click System Setup.

4 Double-click MPTS, then click OK.

5 On the Multi-Protocol Transport Services window, click Configure.

6 On the Configure window, confirm that LAN adapters and protocols is selected, then click Configure.

7 On the Current Configuration window, double-click IBM OS/2 NetBIOS over TCP/IP.

8 On the NetBIOS over TCP/IP window, select Driver Parameters, then click Configure.

9 On the Parameters for IBM OS/2 NetBIOS over TCP/IP window, scroll down and set the Preload Remote Name Directory setting to Yes.

10 Change the Maximum number of name/IP address pairs in the Names File setting to 200, then click OK.


11 On the NetBIOS over TCP/IP window, select Name List, then click Configure.

12 Click Add.

● For a network connection. Type the server name and IP address of the NT server.

● For a direct connection. Type the Workgroup name, then the IP address of the Windows system. Click OK.

13 On the NetBIOS over TCP/IP dialog box, select Broadcast list, then click Configure.

14 Click Add, then enter the IP address of the primary domain controller, or the IP address of the Windows system.

15 Continue to click OK and Close several times, then click Exit.

16 Confirm that Update Config.sys is selected, then Exit.

17 Click OK, then click Exit once more.

18 Shut down and restart OS/2.

To test the network protocols installation

1 On the OS/2 desktop, double-click OS/2 Window.

2 At the command prompt type

net view

then press ENTER.

The requestor service starts and a log on dialog box appears.

● For a network connection. Type the user name and password used in the network configuration process, then click OK.

● For a direct connection. Type in the name of the shared drive on the Windows system, type the password, then click OK.

A list of shared devices appears. Confirm that the NT/Windows 2000 share is in this list. If the shared device is not in the list, use the following command to map a drive to the shared folder for backups.

net use share: \\ntserver\computer

where:

share is the name of the PC-based shared drive.

ntserver is the PC-based server name.

computer is the name of the PC-based computer.

then press ENTER.

NOTE

An error message that says the messaging service has not started appears. This message always appears until the system is set to automatically log on and automatically map a drive when OS/2 starts.

NOTE

If an error appears after running the net view command, repeat the OS/2 configuration process. Refer to the NEAXMail AD-40 Installation Guide for more information.


Configuring NEAXMail AD-40 to Log On to a NetworkFollow the instructions below to log NEAXMail AD-40 onto a network.

Windows Connection with NetBIOSTo set the NEAXMail AD-40 system to log on to a Windows network with NetBIOS over TCP/IP:

1 Add the Windows user ID and password with network access rights.

2 Log on to the NT domain or workgroup from NEAXMail AD-40.

3 Map a network drive on the computer.

To log on to Windows NT with NetBIOS

1 On the messaging system console, double-click the OS/2 window to go to the command prompt.

2 Use specific words in place of userid, password, and domain.

logon userid /p:password /d:domain

■ If not using a domain, type:

logon userid /p:password

where:

userid is the user name.

password is the user’s password.

domain is the name of the domain. If a network domain is not used, omit this option.

3 Press ENTER.

To map a Windows NT network drive

1 On the messaging system console, double-click OS/2 window to go to the OS/2 command prompt.

2 Type:


where:




Automatic Windows Log OnAfter setting up the system for the network, set up NEAXMail AD-40 to automatically log on to a Windows network using the following procedure.

To avoid the security risks of automatically logging on, manually log on using the “To log on to Windows NT with NetBIOS” and “To automatically log on to Windows NT with NetBIOS” procedures.

To automatically log on to Windows NT with NetBIOS

1 Make a backup copy of the Startit.cmd file.

2 Go to the OS/2 command prompt and type:

tedit c:\startit.cmd

then press ENTER.


3 Insert the following lines on the first two lines of the file:

logon userid /p:password [/d:domain]


where:

userid is the user name.

password is the user’s password.

domain is the name of the domain. If a network domain is not used, omit this option.




4 Save the file, then close it.


Configuring a Remote Windows Computer for a BackupA remote Windows computer can be set up without a Windows network domain for backing up an OS/2-based messaging system.

To set this up, follow the applicable set of procedures on the following pages. For more detailed instructions, ask your network administrator or refer to the Windows network documentation.

To configure a Windows 98 or ME Workgroup computer

1 On the Control Panel on the Windows computer, double-click the Network icon.

On the Configuration tab of the Network window, confirm that File and printer sharing for Microsoft Networks is listed in the list of installed network components.

If File and printer sharing for Microsoft Networks is installed, go to the next step. If it is not installed, install the service.

2 On the Identification tab, confirm that the Computername is one word with no spaces.

3 Confirm that the Workgroup field has a value that is different than any valid network domain name. If the field is blank, type a unique name.

4 Write down the Computername and Workgroup field values. You need these to set up NEAXMail AD-40.

5 On the Access Control tab, confirm that the Share-level access control field is selected, then click OK.

6 When prompted, restart the computer.

To set up share-level access for 98 or ME

1 On the Windows computer desktop, double-click the My Computer icon.

2 Right-click the drive or directory that the computer should share with NEAXMail AD-40, then select the Sharing.

3 Select Shared As.

4 In the Share Name field, type a name.

5 Set the Access Type and Passwords fields, as needed.

6 Set Access Type to Full.

7 Write down the share name and password settings for reference during the NEAXMail AD-40 setup, then click Apply.

Windows NT or 2000 Setup

To configure a NT or 2000 workgroup computer

1 Log on to the Windows NT or 2000 computer with administration access rights.

2 Right-click the My Computer icon, then select the Properties menu.

3 On the Network Identification tab, confirm that the Computer name is one word with no spaces.

4 Click Properties, then set up a unique Workgroup name that is different than any domain on the network.

5 Write down the computer name and Workgroup name for reference during the NEAXMail AD-40 setup, then click OK.


To configure a NT or 2000 user ID and password

1 In Windows NT, click Start > Programs > Administrative Tools> User Manager.

In Windows 2000, click Control Panel > Users and Passwords icon.

On the Advanced tab, under the Advanced User Management section, click Advanced.

2 Use one of the following procedures:

● Windows NT. Click Add and follow the on-screen instructions to set up a new user ID, privileges, and password.

● Windows 2000. Right-click the users folder, then select New user... Follow the on-screen instructions to set up the new user ID and password.

● NEAXMail AD-40. Use the default Guest account on either Windows NT or Windows 2000, enable the single user Guest account, and then confirm that the Guest password is set.

3 For the Guest or new account, clear the User must change password on the next log on check box.

4 Write down the account User ID and password for reference during the NEAXMail AD-40 setup.

5 Click Apply, then click Close to complete the setup.

To set up share-level access for NT or 2000

1 On the Windows computer desktop, double-click the My Computer icon.

2 Right-click the drive or directory for NEAXMail AD-40 to share, then click the Sharing menu.

3 Select the Share this folder field, then set the appropriate Share name.

4 Click Permissions, select Everyone, then click Remove.

5 On the Permissions dialog box, click Add.

6 Add the Guest or new user account set up in the previous procedure.

7 Set up the read/write privileges for this user account, then click Apply.

NOTE

Confirm that the single user Guest account for this step is being used. This is different than the Guests group account.

NOTE

If sharing drive C, do not use the default C$setting. Select New Share and create a new sharing profile.


Upgrading to New HardwareThe current release of the messaging system runs on a PC-based computer and replaces existing hardware such as the OS/2 servers.

Prerequisites● The PC-based computer has been installed.

● The messaging system has been installed and configured.

● One of the following:

■ Backup of the old system to Windows PC. The backup can be:

● On-line. Performed while system is running using the provided backup utilities.

● Off-line. The entire vmail folder is archived in a zip or tar.gz format

■ The VMShare utility is running on the existing system or was used to create an off-line backup to a USB flash drive.

● Network connection between the Windows PC with the backup files and the existing system to be upgraded.

NOTE

If a network connection is not available, a USB flash drive can be used to transfer the archive to the new messaging system.


Upgrading Existing HardwareThis procedure applies to Linux-based systems that operate on hardware that is supported for this release.

Prerequisites The following items are required to upgrade existing hardware.

● Installation disc

● External USB DVD reader [optional item]

● TTS DVD [optional item]

● Current messaging system licensing.

● Backup of the existing system to Windows PC. The backup is created:

● On-line. The complete messaging system is archived using the Administration Console back up utility while the messaging system is online.

● Off-line. The complete messaging system folder is archived in a zip or tar.gz file.

● Network connection between the Windows PC holding the backup data and the system to be upgraded.

If a network connection is not available, a USB flash drive can be used to transfer the archived files to the system to be upgraded.

To use an external USB DVD drive

1 Attach the external USB DVD drive to a USB port on the PC.

2 Change the boot order in the BIOS to boot from the USB DVD drive.


4 Restart the system.

5 Follow the on-screen instructions to install the software.

The process wipes all of the existing data and installation.

6 Install new licenses using the Administration Console, click System > Licensing, on the Licensing page:

a Click Browse to browse to the license file.

b Select the file, then click Open.

c Click Save to save the new license information.

7 Restore the back up files.

See “Restoring Back Up Files” on page 69.

Network Method

To use the network to restore data

1 Configure network on the new system.

2 Install new licenses using the Administration Console, click System > Licensing, on the Licensing page:

a Click Browse to browse to the license file.

b Select the file, then click Open.

c Click Save to save the new license information.


4 Select a backup file to restore, or click Browse to browse the network for the backup file.

5 Select the file, then click Open.


6 Click Upload file.

7 Restart the messaging system software when restore process is complete.


DAPPENDIX
Migrating from AD-64
Messaging Systems

OverviewThe UNIVERGE UM4730 messaging system supports the migration of supported products to the current release. This appendix describes the steps required to migrate data from NEAXMail® AD-64 to the current version.

The migrated data includes the system configuration settings, subscriber accounts, groups, transaction boxes, interview boxes, voice names and greetings, and messages.

When a LAN connection is set up, the backup files can be saved directly to a network location. Alternatively, create the backup files on the local hard drive, then transfer them to a network location or copy them to removable media. Use pcAnywhere can be used to transfer the files.

The AvBackup UtilityAvBackup is a utility provided with the NEAXMail® AD-64 system to create and restore backups.

AvBackup uses the Windows Backup/Restore utility to back up the messaging system data files. AvBackup also backs up and restores additional information that the Windows Backup/Restore utility does not back up, such as the Windows registry information. For this reason AvBackup must be used instead of the Windows Backup/Restore utility to back up the UNIVERGE UM4730 system.

Run AvBackup manually, or schedule AvBackup to run automatically on a regular basis.

Levels of BackupAvBackup allows three different backup levels:

● Basic. Includes all system configuration settings, subscriber account information, greetings, and voice names.

A basic backup does not include subscriber messages or prompts. A basic backup recommended before making any substantial changes to mailboxes and transaction boxes.

WARNING

Customized prompts, MWI configurations, and switch settings cannot be migrated.

CAUTION

Verify that the default language on the UNIVERGE UM4730 messaging system is the identical to the default language on the NEAXMail® AD-64 system. If the default languages are different the language settings might not migrate properly.

WARNING!

It is strongly recommended that you store backup files in a location other than the local hard drive. If there is a hard drive failure, both the messaging system data and the backup data might be lost if these are on the local hard drive.

WARNING!

If AvBackup is not used, parts of the messaging system configuration might be lost.

APPENDIX D: MIGRATING FROM AD-64 MESSAGING SYSTEMS 111

● Normal. Includes all system configuration settings, subscriber account information, greetings, voice names. and all stored subscriber messages.

● Complete. Includes all system configuration settings, subscriber account information, greetings, voice names, and all system prompts.

A complete backup is recommended after customizing prompts and to prepare data to be migrated to a newer messaging system.

Use the Windows Scheduled Tasks utility to run backups automatically on a regular basis. An automatic backup schedule is recommended. This ensures that recent backup is available in the event of a system failure.

Types of BackupsRun backups in either of two modes:

● Online mode. In online mode, the messaging system continues to run while the backup is in progress.

● Offline mode. In offline mode, if the messaging system is running, it is shut down to perform the backup.

If running a manual backup in offline mode, specify whether or not to restart the messaging system when the backup is complete.

If scheduling an automated backup in offline mode, the messaging system automatically restarts when the backup is complete. The messaging system restarts whether or not it was running before the automated backup.

Backup File NamesBackup files are created with a name indicating the type and date of the backup, for example Basic Offline Backup January 28 2005.bkf. If another backup of the same type is created on the same date, the previous file is overwritten.

If another backup of the same type is created on a subsequent date, a separate backup file is created.

Overriding the File Naming ConventionYou can override the file naming convention with automatically scheduled backups. Add the -o parameter at the end of the backup command. This parameter forces all backup files of the same type to be replaced by the current backup.


Backing Up the NEAXMail® AD-64 Messaging SystemCreate a manual backup of the NEAXMail® AD-64 messaging system data to be migrated to the UNIVERGE UM4730 messaging system.

To create a manual backup

1 Sign in to the messaging system server using the same rights. used to install the operating system.

2 Start the AvBackup utility:

■ Double-click the Backup icon on the Windows desktop.

OR

a Click Start > Run.

The Run dialog box appears.

b Type the following in the Open field:

C:\VMail\AvBackup.exe

Alternatively, click Browse to browse and select the AVBackup.exe file.

c Click OK or press ENTER.

The AVBackup window appears.

3 In the Backup Type section select one of the following:

● Online. ■For an online backup.

● Offline. ■For an offline backup.

If an offline backup is selected, select the Restart messaging system check box to restart the messaging system when the backup is complete.

4 In the Backup Contents area, select Complete Backup to create a backup for the migration.

5 The backup files are placed in the C:\Vm Backup\ folder. Click Browse to select a different destination folder.

6 Click Backup.

7 In the confirmation dialog box click OK to begin the backup process.

The Backup Status dialog box appears, reporting the status of the backup process.

8 Click OK on the AVBackup dialog box when backup is complete.

9 Click Close on the AVBackup dialog box to exit the backup utility.

CAUTION

If an offline backup is selected when the messaging system is running, AvBackup will disconnect any active calls and shut down the system before doing the backup.

NOTE

The file name is automatically generated by the AVBackup utility. The file. For example, Complete Offline Backup April 20 2009.bkf.

NOTE

Optionally copy the backup files from the \Vm Backup\ folder to a network location or removable media.


Verifying the AD-64 Back Up File IntegrityUnder very rare circumstances, the backup procedure can create a corrupt or unusable backup. After creating a backup, use the following procedure to verify the backup integrity.

This procedure is mandatory when upgrading the operating system from Windows 2000 to Windows Server 2003 SP1 or Windows Server 2003 R2 or when upgrading to UNIVERGE UM4730.

The upgrade procedure deletes all system data from the hard drive. Therefore, it is critical that the backup integrity is verified before upgrading or installing a new messaging system.

To verify the backup file integrity


2 Open a Windows Explorer window.

3 Navigate to the folder containing the backup file: C:\Vm Backup\.

4 Double-click the backup file.

The Windows Backup utility automatically starts.

5 In the Windows Backup window, click the Restore tab.

6 Click Tools > Create a backup file.

7 In the Backup File Name dialog box, click Browse.

8 In the Select File To Catalog dialog box, navigate to the folder containing the backup file, select the backup file, then click Open.

9 In the Backup File Name dialog box, click OK.

■ If the backup file is OK, a new media catalog for the backup file appears under File in the left pane.

■ If the backup is corrupt, an error message appears indicating that the backup file is unusable or that there is some other problem with the backup.

Create a new backup file and repeat the backup integrity test. If the backup fails the integrity test a second time, contact Technical Support for assistance.

10 Close the Windows Backup window.

11 Copy the backup file to an external USB storage device or a network share that is accessible by the UNIVERGE UM4730 messaging system.


Migrating the AD-64 Database and Voice MessagesThe new version of the messaging system is installed with a default database. Use the following procedure to restore an old database and voice messages.

The messaging system restore utility takes the AD-64 backup data file and converts it into a format that can is recognized by the messaging system database.


To restore the AD-64 back up file to the UM4730 messaging system





5 Stop the messaging system software:

a Click Server Control.

b Click Stop.

Wait for the messaging system to stop.


7 If the backup file is not listed on the Restore page, click Upload File to search for and select the back up file.

8 Select Restore this backup from the Action list to restore the AD-64 database. Other options include:





The Restoring Backup progress window appears.


11 Restart the messaging system software.

a In the Navigation pane click Server Control.

b Click Start on the System Control page.

When the messaging system has restarted, the start icon is greyed out. Click View the startup log file to see the start up process.

NOTE

Make sure that all users are logged out of the messaging system.


EAPPENDIX
Migrating from OS/2
Messaging Systems

OverviewThe UNIVERGE UM4730 messaging system supports the migration of supported products running on the OS/2 operating system to this release.

This appendix describes the steps required to migrate data from OS/2 to Linux.

RequirementsThe following is required to successfully back up and transferOS/2 files to the new messaging system server:

● CoSession. A remote file transfer and system recovery tool.

● Windows computer. A computer running the Windows operating system networked with the OS/2 computer.

Migration StepsThe following is a summary of the major steps required to migrate from OS/2 to Linux. Complete details on each step are provided in subsequent sections of this chapter.

1 Back up the OS/2 database.See “Backing Up the OS/2 Database” on page 118.

2 Compress the OS/2 back up file. See “Compressing the OS/2 Backup Data” on page 119.

3 Transfer the back up OS/2 database to the new UNIVERGE UM4730 system.See “Transferring the backup data” on page 119.

Refer to the NEAXMail® AD-64 OS/2 documentation for more information about these applications or using a modem connection.

WARNING


APPENDIX E: MIGRATING FROM OS/2 MESSAGING SYSTEMS 117

Backing Up the OS/2 DatabaseThe OS/2 database must be backed up before the data can be migrated to the new messaging system server. After the data is backed up, it must be compressed before transferring the data to a support computer. The following types of data can be included in the OS/2 backup:

Because the OS/2 system does not have a floppy disk drive or other removable media drive, it is not possible to use disks for the migration. Instead, you must back up the data from OS/2 to a support computer running the Windows operating system, then transfer the backup data to the messaging system server.

The following procedures assume that CoSession is installed on the support computer running the Windows operating system, and a direct connection between the Windows computer and the OS/2 system has been established.

To back up the OS/2 database

1 At the Windows support computer, start the CoSession Remote client.

2 In the CoSession Remote Viewer Control Center, select the messaging system OS/2 computer in the Name list box.

3 Click Call.

The messaging system Banner page appears.

4 Press ESC to shut down the messaging system.

After the messaging system shuts down, the Utility menu appears.

5 On the Utility menu, select Voice Mail Utilities.

The Voice Mail Utility menu appears.

6 On the Voice Mail Utility menu, select Backup, Restore, Update - BRU utility.

The messaging system restarts.

7 In the CoSession Remote Viewer Control Center, click Hang Up.

The CoSession connection is terminated. Wait approximately two minutes for the BRU host to start.

8 On the support computer, run C:BRU\BRURMT.exe. start the BRU Client. For example, browse to C:\BRU and double-click “BRURMT.EXE.” The BRU client starts.

9 Confirm the connection settings are correct, click Connect to BRU Host via null modem cable, then click OK.

If the BRU is able to connect, the status bar at the bottom of the window says CONNECTED. Repeat this step until a connection is established.

10 On the Main menu, select Backup then press ENTER.

11 On the Backup menu, select Database, OGMs, and Messages then press ENTER.

12 Type the directory name where the backup will be stored on the Windows computer, then click ENTER. For example C:\Backup.

13 Type a description for the backup, then click ENTER. For example AD-8 Backup.

● Messages● Voice names● Greetings● Subscribers

● System settings● Transaction boxes● Interview boxes● Groups


14 Press ENTER to confirm the backup description.

To proceed with the backup, press ENTER.

15 After the backup is complete, press any key to continue.

16 On the Main menu, select Exit the BRU Host and BRU Remote, then click ENTER.

17 Type y to disconnect and exit the BRU Remote session.

Compressing the OS/2 Backup DataAfter the backup is complete, you must compress the files on the Windows computer in the proper format for migration to UNIVERGE UM4730.

This procedure documents how to use WinZip, a common file compression utility. If you are using a different file compression program, make sure the backup files are compressed from the top of the backup directory with the subdirectory structure intact.

To compress the OS/2 backup data

If WinZip is not already installed on the Windows computer, download the evaluation version from the Internet and follow the on-screen instructions to install the application.

1 After WinZip is installed, from the Windows taskbar, select Start > Programs > WinZip.

2 Select File > New Archive...

3 Type the name and path where the compressed backup file will be stored. For example, type C:\temp\backup.zip, then click OK.

The Add dialog box appears.

4 Browse to the directory where the OS/2 backup files are located, for example C:\Backup.

5 In the Folders area, select the Include subfolders check box.

6 Click Add with wildcards. WinZip begins compressing the backup files.

7 After WinZip finishes compressing the files, a list of the compressed files appears. Select File > Exit to exit the program.

This completes the OS/2 backup and compression process.

Transferring the backup data The following procedure assumes that a backup has been completed and compressed.

❚ Transfer the compressed backup file to /opt/vmail/var/backup/ on the messaging system server.

NOTE

Depending on the number of outgoing messages (OGMs) and messages on the system, the backup takes up to three hours to complete.

CAUTION

This option must be selected or the migration process will fail.

APPENDIX E: MIGRATING FROM OS/2 MESSAGING SYSTEMS 119

Migrating the Backup FilesAfter the backup files are transferred use the Administration Console to migrate the data to the new messaging system.


To restore backup data


2 Sign in as $nec.



4 Stop the messaging system, if you have stopped the messaging system skip this step.

a Click here to stop the messaging system.


b Click Stop, then return to the Restore page.

5 If the backup file is not listed on the Restore page:

a Click Browse to browse for and select a backup file.

b Click Upload File to add the selected file to the list of backup files.

6 Select one action from the Action drop-down list:

● View backup note. Click to display the backup note, then click OK to close the message alert.

● Delete. Click to delete the backup file. Click OK to confirm the deletion.

● Download. Click to download the backup file. Click Save to save the backup file and add it to the list of backup files.

● Restore this backup. Click to restore the backup file.





FAPPENDIX
Migrating from OS/2
Messaging Systems

OverviewThe UNIVERGE UM4730 messaging system supports the migration of supported products, IM-16 running on OS/2 to IM-16 LX 10.x, this release. This appendix describes the steps required to migrate data from OS/2 to Linux.

Migration of most existing data from OS/2 to the new messaging system is possible. The migrated data includes the system configuration settings, subscriber accounts, groups, transaction boxes, interview boxes, voice names and greetings, and messages.

RequirementsThe following is required to successfully back up and transfer DOS files to the new messaging system server:

● Windows computer. A computer running the Windows operating system on the same network as the OS/2 computer.

● CoSession. A remote file transfer and system recovery tool.

● PKZIP. Utility used to compress the back up file.

Migration Configuration StepsThe following is a summary of the major steps required to migrate from OS/2 to Linux. Complete details on each step are provided in subsequent sections of this chapter.

1 Prepare a remote Windows computer for backup.See “Configuring a Remote Windows Computer for a Backup” on page 122.

2 Configure OS/2 NetBIOS to transfer files. See “Configuring the OS/2 NetBIOS to Transfer Files” on page 123.

3 Back up the OS/2 database.See “Backing Up OS/2 Data” on page 127.

4 Compress the back up file. See “Compressing the OS/2 Backup Data” on page 127.

5 Transfer the back up file to the new UNIVERGE UM4730 system.See “Transferring the Backup Files” on page 128.

WARNING


CAUTION

Verify that the default language on the UNIVERGE UM4730 messaging system is the identical to the default language on the OS/2 system. If the default languages are different the language settings might not migrate properly.

APPENDIX F: MIGRATING FROM OS/2 MESSAGING SYSTEMS 121

Configuring a Remote Windows Computer for a BackupWhen creating a back up of the OS/2 system, set up a Windows computer without a Windows network domain.

To set up this configuration use the following set of procedures. For more detailed instructions, ask your network administrator or refer to the Windows network documentation.

Windows NT, 2000, or XP ConfigurationUse the following procedure to configure Windows 2000, Windows NT, or Windows XP for remote backup.

To set up an NT, 2000, or XP workgroup

1 Log on to the Windows NT or 2000 computer with administration access rights.

2 Right-click the My Computer icon, then select the Properties.

3 On the Network Identification tab, confirm that the computer name is all one word with no spaces.

4 Click Properties, then type a unique Workgroup name that is different from any domain on the network.

5 Write down the computer name and Workgroup name. This information is required to set up OS/2.

6 Click OK.

To set up an NT or 2000 user ID and password

1 Configure new accounts, use the operating system documentation to set up new accounts.

Alternatively, if you want the OS/2 system to use the default Guest account, enable the single user Guest account and confirm that the Guest password is set.

2 Confirm that the single user Guest account for this step is being used. This is different from the Guests group account.

3 For either the Guest or new account, clear the check box for the User must change password on the next log on field.

4 Write down the account user ID and password. You need these values to set up OS/2.

5 Click Apply, then click Close to complete the setup.

To set up share-level access for Windows NT, 2000 or XP

1 On the Windows Desktop, double-click the My Computer icon.

2 Right-click the drive or directory to share with OS/2, then click Sharing.

3 Select the Share this folder field, then set the appropriate Share name.

4 If sharing drive C, do not use the default C$ setting. Instead, select New Share and create a new sharing profile.

5 Click Permissions, click Everyone, then click Remove.

6 In the Permissions dialog box, click Add, then add the Guest or the new user account set up in the previous procedure.

7 Configure the read/write privileges for the user account, then click Apply.


Configuring the OS/2 NetBIOS to Transfer FilesNetwork protocols must be installed to transfer an OS/2 system database using a NetBIOS over TCP/IP configuration. Activation or upgrade codes are not required for network configurations.

Make sure that the following installation information is available before starting the NetBIOS data transfer:

Configuring NetBIOS over TCP/IPConfigure TCP/IP and specify a Windows network domain name. If a domain does not exist, use the procedure described in see “Configuring a Remote Windows Computer for a Backup” on page 122.

For a network backup using NetBIOS over TCP/IP, you also need to set up the system to log on to the network. After installing network protocols, see “To install network protocols for a NetBIOS backup” on page 123.

Finally, set up a Windows computer to share a drive with the OS/2 system. See “Logging on to Windows Automatically” on page 126.

To install network protocols for a NetBIOS backup

1 Log on to the OS/2 messaging system.

The Banner page appears.

2 Press ESC on the Banner page and follow the system prompts.

3 Start an OS/2 command prompt.

4 On the OS/2 command prompt, type

f: ENTER

cd\ ENTER

setup ENTER

5 Type y to proceed with the messaging system set up utility.

6 On the Select Setup Type menu, type 2 to select Configure System, then ENTER.

7 Press OK to confirm that the messaging system is installed on drive E.

8 Press OK to confirm that the messaging system is installed in the E:\VMAIL\ directory.

9 The Setup menu displays the features and options available on the system. Review the available options, then ENTER.

The Update Configuration menu appears.

10 Click Configure Network Protocols (for Network Backup/Restore).

Make sure that all other options are cleared, then press ENTER.

Subnet mask

Router

Domain name

Server name

OS/2 server TCP/IP address

NOTE

The Windows system should be set up as a workgroup environment with a unique TCP/IP address.


11 On the Select Network Protocols to Install/Configure menu, type:

2 (TCP/IP) ENTER

3 (NetBIOS over TCP/IP) ENTER

The TCP/IP Setup menu appears.

12 Type 1 ENTER

13 Type the correct value for the TCP/IP Address field, then ENTER.

14 Type 2 ENTER.

15 Type the correct value for the Subnet Mask field, then ENTER.

16 Type 3 ENTER.

17 Type the correct value for the Default Router field, then ENTER.

18 Type 4 then ENTER.

19 Type the correct value for the Domain field, then ENTER


21 Type the correct value for the Name Server field, then ENTER.

The NetBIOS over TCP/IP Setup menu appears.


23 In the Workstation Name field, type the name of the messaging system server, then ENTER.


25 In the NT Domain Name field, type the name of the Windows network domain of the messaging system, then ENTER.


27 In the Workstation Description field, type a description for the messaging system, then ENTER.

28 Review the entries to confirm that they are correct, then ENTER to continue.

Setup configures the network protocols according to the information provided.

29 When the configuration is complete, the Setup Complete menu appears. Press ENTER to exit the setup utility.

30 Shut down the OS/2 board by moving the Shutdown Switch to the UP position.

31 After the system has fully shut down, move the Shutdown Switch back to the DOWN position then click the Reset button to restart the system.

Connecting an OS/2 system to a networkUse the following procedure to enable the OS/2 system to log on to a Windows network with NetBIOS over TCP/IP.

To log on to a Windows network

1 Add a Windows user ID and password with network access rights.

2 Specify the IP address of the network Primary Domain Controller (PDC).

3 Log on to the Windows domain or workgroup from the OS/2 system.

4 Map a network drive.

NOTE

If there is no Windows domain, type the Windows workgroup name instead.


5 Configure the OS/2 system to automatically log on to the Windows network (optional).

To add a user with network access rights

1 On the messaging system, go to an OS/2 command prompt.

2 Log on as an administrator by typing:

logon admin /p: ENTER

3 Add a user with network access rights by typing:

net user <userid> <password> /add ENTER

where <userid> and <password> are a valid user name and password on the Windows computer.

The userid and password must match the settings on the Windows computer.

4 Type logoff, then ENTER.

To specify the network Primary Domain Controller IP address


2 Type mpts, then ENTER.

The Multi-Protocol Transport Services application starts.

3 In the Multi-Protocol Transport Services dialog box, click Configure.

4 In the Configure dialog box, click LAN Adapters and Protocols, then click Configure.

The Adapter and Protocol Configuration dialog box appears.

5 In Current Configuration click IBM OS/2 NetBIOS over TCP/IP, then click Edit.

6 Click Broadcast list, then click Configure.

7 Make sure the IP address listed in the broadcast list is the correct IP address of the Primary Domain Controller (PDC) for the Windows domain.

Consult with your network administrator to determine the correct PDC IP address.

8 Click OK to apply the change.

9 Click Close to close the Configure dialog box.

10 Click Exit to close the Multi-Protocol Transport Services application.

11 Double-click the Shutdown icon on the desktop to restart OS/2.


To log on to the Windows domain or workgroup using NetBIOS


2 The command options used depend on if you are logging on to a domain or a workgroup:

To map a Windows network drive


2 Specify a drive name for the NetBIOS share directory by typing:

net use x: \\<server>\<share> ENTER

Where <server> is the name of the Windows computer and <share> is the name of the shared directory on the Windows computer.

Go to the beginning of the file and insert the following command lines.

If you are not using a domain, insert everything except /d:domain.

logon <userid> /p:<password> /d:<domain> ENTER

net use h: \\<server>\<share> ENTER

Use the correct values in place of <userid> and <password>. <Server> is the Windows computer name and <share> is the Windows directory share name.

3 Save the file, then exit the text editor.

4 Move the shutdown switch on the OS/2 board to the UP position.

After the system has shut down, move the shutdown switch back to the DOWN position then press the Reset button to restart the system.

Logging on to Windows Automatically NEAXMail IM-16 OS/2 can be configured to automatically log on to the Windows network using the following procedure.

To automatically log on to Windows using NetBIOS

1 Make a backup copy of the Startit.cmd file.

2 Go to the OS/2 command prompt and type:

e c:\startit.cmd ENTER

Domain type:

logon <userid> /p:<password> /d:<domain> ENTER

where

user id = Windows user name.

password = Windows password.

domain = Windows domain name.

Workgroup type:

logon <userid> /p:<password> ENTER

where

userid = Windows user name.

password = Windows password.


Backing Up OS/2 DataAfter the backup is complete, compress the files in the proper format to migrate to UNIVERGE UM4730. This requires transferring a compression utility to the OS/2 board.

To backup the OS/2 database

1 Back up the OS/2 messaging system database to a directory named OrigDB.

2 Run dbchk and fix any reported problems.

3 Run upgchk and fix any reported problems.

4 Start the OS/2 messaging system.

Compressing the OS/2 Backup DataThe following procedure uses CoSesssion to compress the data, and FTP to transfer the compression utility if the OS/2 FTP server is already configured.

To compress the OS/2 backup data

1 On the remote support computer, insert the UNIVERGE UM4730 Support disc into the disk drive.

2 Using the CoSession client, connect to the OS/2 system.

3 Browse to PKOS2250.EXE on the Support disc and transfer it to the E:\ directory on the OS/2 board.

4 Open a command prompt window on the OS/2 system. Type the following commands:

E: ENTER

cd\ ENTER

mkdir archive ENTER

move PKOS2250.EXE \archive ENTER

cd archive ENTER

PKOS2250.EXE ENTER

The program extracts the PKZIP.EXE utility to E:\archive.

cd \backup ENTER

5 To compress the backup file type:

\archive\pkzip /add /dir=current E:\backup.zip ENTER

where backup.zip is the name of the compressed file.


Transferring the Backup FilesAfter completing a local backup and compressing the backup files, transfer the files from the OS/2 messaging system to another computer for temporary storage.

There are two methods for transferring the files:

● FTP connection. The OS/2 system is set up for networking.

● CoSession. The OS/2 system is connected to a remote computer using a direct-connect null modem cable.

Using FTP to Transfer FilesAn FTP connection requires a network connection to a Windows computer. Configure the OS/2 FTP server before transferring the files. See “Configuring the OS/2 NetBIOS to Transfer Files” on page 123.

To transfer the backup file using FTP

1 On the Windows computer, open a command prompt window and type the following command:

ftp <IP address> ENTER

where <IP address> is the IP address of the OS/2 system.

2 When asked for the user name, type support ENTER.

3 When asked for the password, type voice ENTER.


lcd <directory name> ENTER

where <directory name> is the destination directory on the Windows computer for the compressed backup file.

5 Type binary ENTER.

This sets the file transfer mode to binary.


get <filename> ENTER.

where <filename> is the name of the compressed backup file, for example backup.zip. If the file transfer is successful, you should see a File send OK message.

7 Type quit ENTER, to exit the FTP client.

Using CoSession to transfer filesCoSession requires a network connection to a Windows computer.

To set up the OS/2 FTP server

1 Use CoSession to connect to the OS/2 system.


c: ENTER

cd \mptn\etc ENTER

WARNING

The file transfer mode must be set to binary or the migration will fail.

NOTE

File names are case-sensitive when using FTP. If you see a Failed to open file error message, type dir ENTER to view the correct file name.


3 Open a text editor. Type: e TRUSERS ENTER.

This command creates a new file, TRUSERS, and opens the text editor.

4 Type the following lines into the TRUSERS file:

user support voice

rd e:\

wr e:\

5 Save the file and exit the text editor.

6 Start the OS/2 FTP server. Type

c:\tcpip\bin\ftpd ENTER

NOTE

The file name must be TRUSERS without a file extension.


Migrating to UNIVERGE UM4730After the OS/2 backup data has been transferred to the UNIVERGE UM4730 system start the migration.

Use the following procedure to migrate the OS/2 data to the UNIVERGE UM4730 messaging system.


To restore the OS/2 backup to the new messaging system

After creating and uploading the backup OS/2 database, use this procedure to import the data.


2 Stop the messaging system:



b Click Stop.

When the messaging system has stopped, the stop icon is greyed out and a message, the messaging system is currently stopped, appears. Click View the stop log file to see the stop process.



4 If the backup file is not listed on the Restore page:

a Click Browse to browse for and select a backup file.

b Click Upload File to add the selected file to the list of backup files.

5 Select an action from the Action list:




● Restore this backup. Select to restore the backup file.





b Click Start on the System Control page.

When the messaging system has restarted, the start icon is greyed out. Click View the startup log file to see the start up process.

NOTE

The migration cannot be completed if there is a user logged on to the UNIVERGE UM4730 Administration Console. Make sure that all users are logged off the Administration Console before migrating.


GAPPENDIX
Installing Expansion Boards
Expansion Board OverviewExpansion boards are circuit boards that are installed in the messaging system server and provide additional functionality for the system. You can add more voice boards to increase the number of voice ports in an existing system. This appendix provides instructions for installing voice and fax boards.

Supported Voice and Fax Boards The following boards are supported in this release.

* UM4730 supported fax boards.

Selecting Slots for Expansion BoardsSelecting slots for the voice, fax, and other expansion boards depends on the computer, the type and number of boards being installed, and whether or not you are using an expansion chassis.

PCI express (PCIe) slots are serial connections (similar to SATA) that have one or more lanes. The x16 slot is currently the slot with the most bandwidth and is commonly used by video cards. More lanes equates to more bandwidth and available power.

Installing Boards in the Proper Slot● 32-bit PCI boards might be installed in either 32-bit or 64-bit PCI slots.

● PCIe voice boards must be installed in PCIe x 4 lane or wider slots.

● Non-universal PCI voice boards can only be installed in 5-volt PCI slots.

Adding or Replacing BoardsUse the following procedure to add or replace a voice or fax board in an existing messaging system.

To add or replace a board in an existing system

◆ If you are adding a voice or fax board.Use the applicable procedures to set the switches and jumpers on the board that you are installing.

◆ If you are replacing a voice or fax board.a Remove the board that is being replaced.

b Set the jumpers on the replacement board exactly the same as the board being replaced.

c Press the board firmly into place.

Board Name Bus Ports Type

D4PCI PCI (5 volt) 4 Analog

D4PCIUF * Universal PCI 4 Analog

VFX41JCTLS * Universal PCI 4 Fax

APPENDIX G: INSTALLING EXPANSION BOARDS 131

D4PCI Series SettingsThe D4PCI series are four-port, PCI network/resource voice boards. Each board installed in a system requires a unique ID, which is set by performing the following procedure. The illustration below provides the switch locations and pinout details.

To set the D4PCI switch settings

1 Set switch SW1 as shown in the following illustration.

Each board setting is based on its port order in the voice messaging system and the lines connecting it to the phone system.

2 Set SW4 to OFF on all D4PCI boards in the system.

First PCI board Fourth PCI board

Second PCI board Fifth PCI board

Third PCI board Sixth PCI board

Voice Board Backplate

Line 1

Line 2

Line 3

Line 4

Location of connectors and switches on the D4PCI and D4PCIUF

Pin 1: Not connectedPin 2: Not connectedPin 3: RingPin 4: TipPin 5: Not connectedPin 6: Not connected

SwitchSW1

Switch SW4

Voice Board Top View

Connection PinoutsThe D4PCI and D4PCIUF use four RJ-11 connectors

1 4

2 5

3 6


D120JCTLS Series Settings

The D120JCTLS series consists of 12-port, PCI network/resource boards. Each board installed in a system requires a unique ID, which is set by performing the procedure below. The illustration on page 125 provides the connector and switch locations.

Combining with D4PCI BoardsIf you combine a D120 board with D4PCI boards, we recommend that you set the ID of the boards so that the board with the most ports has the lowest ID, starting at ID 1. For example, if you are combining one D120 board with two D4PCI boards, set SW100 on the D120 board to 1 and SW1 on the D4PCI boards to 2 and 3.

To set the switch settings

❚ Set switch SW100 as shown in the following illustration.

To set the power budgeting jumper

Use with PCIe boards only.

NOTE

The ISA edge retainer must be removed from the board before installing in most computers.

Jumper P8Voice board side view

Voice board top view

CT bus connector

Voice board backplate

36-positionmini-D

connector

Board IDdisplay

First PCI board Fourth PCI board

Second PCI board Fifth PCI board

Third PCI board

1 4

2 5

3


❚ Shunt must be strapped to pins 1 and 2 to disable power budgeting.

Each board setting is based on its port order in the messaging system and the lines connecting it to the phone system.

NOTE

Do not use a x1 lane PCIe slot.

NOTE


Power budgeting jumper

Shunt on pins 1 and 2

Voice boardbackplate

Connection pinoutsThe D120JCTLSU uses RJ-14 connectors.

Lines 1 and 2

Lines 3 and 4

Lines 5 and 6

Lines 7 and 8Pin 6: Earth recall 2

Pin 5: Ring 2Pin 4: Tip 1

Pin 3: Ring 1Pin 2: Tip 2

Pin 1: Earth recall 1

Switch SW100 Switch SW1

Voice board side view - Universal

Lines 9 and 10

Lines 11 and 12

CT bus connector

Voice board top view


VFX41JCTLS SettingsThe VFX41JCTLS consists of four-port PCI fax boards. Each board installed in a system requires a unique ID which is set using the procedure on the following page. The following illustration provides the connector and switch locations.

To set the switch settings

❚ Set switch SW30 as shown in the following illustration.

Each board setting is based on its port order in the messaging system and the lines connecting it to the phone system.

NOTE


First fax board

Second fax board

Fax board backplate

Connection pinoutsThe VFX41JCTLS uses RJ-11 connectors

Fax board top view

Fax board side view

Pin 1: Not usedPin 2: Earth recall (Euro only)Pin 3: RingPin 4: TipPin 5: Not usedPin 6: Not used

Line 1Line 2

Line 3

Line 4

E

F


HAPPENDIX
Peripherals and UPS
Connecting Peripheral Devices and the System KeyWhen connecting peripheral devices and the system key to the computer refer to your computer documentation to locate the appropriate ports. The image below is just an example of one computer.

Connect the power cords into a power strip or uninterruptible power supply (UPS).

Connections for a Dell Computer

Serial modem. Use the modem cable to connect the COM1 serial port on the messaging system server to the serial port connector on the modem.

USB modem. Use the USB cable to connect a USB port on the messaging system server to the USB port connector on the modem.

1 Connect a public phone line to the modem.

Serial modem. Connect the phone line to the Telco phone jack on the modem.

USB Modem. Connect the phone line to the Line phone jack on the modem.

2 If installing a serial modem, connect the modem power cord into a power strip or UPS and turn on the modem.

3 Turn on the messaging system server.

4 Check the light-emitting diode (LED) display on the front of the modem.

The LEDs labeled CS and TR are lit when the:

■ modem is receiving power.

■ modem is connected to the messaging system.

■ host software is running.

If only the CS LED is lit, the modem is receiving power but it is not connected to the computer, or the host software is not running, or the host is not configured properly.

Refer to the manufacturer documentation to troubleshoot your connectivity.

A Serial port

B Monitor port

C Diagnostic lights

D USB slots

E Network adapter

C

D E

A

B

APPENDIX H: PERIPHERALS AND UPS 137

Uninterruptible Power SupplyThe information in this section describes how to install a stand-alone uninterruptible power supply (UPS).

The UPS ensures a constant flow of power, even when there are fluctuations or interruptions in the power supplied by the electrical outlet.

Updated manuals and additional information about the UPS can be found on the APC website.

Front Panel of UPS

Back Panel of UPS


Connecting the UPSUse the following procedure to connect the UPS to the messaging system.

To install the UPS

1 Connect the UPS power cord to a two-pole, three-wire, grounded outlet. Avoid using extension cords and adapter connections between the UPS and the power supply.

2 Connect power cables from the computer, monitor, and modem to the UPS output outlets.

3 Confirm that the Site Wiring Fault LED light is not lit.

4 Turn on the UPS.

Checking the UPS BatteryRegularly check the replace battery light on the UPS. The replace battery light turns on if the UPS battery is weak, has discharged, or if the battery leads are not properly connected to the UPS. Always refer to the manufacturer’s Web site for updated instructions and service guidelines.

UPS controls and lights

If the light is on, follow the procedure below to remove the battery and check the battery leads. If the leads are OK, and the light remains on, replace the battery.

To check the battery leads

1 While the battery is removed, confirm that the leads are firmly connected and that the insulation is not cracked or damaged. If the insulation on the leads is damaged, replace the leads.

2 Return the battery to the UPS and allow the UPS to charge the battery for four hours. If the replace battery light is still on, replace the battery.

Removing and Replacing the UPS BatteryUse the product documentation to remove or replace the UPS battery.

WARNING

This indicator light warns you that there are problems with the building wiring that might result in a shock hazard.

If the site wiring fault light is on, immediately disconnect the UPS from its power source and contact an electrician to have the fault corrected.

WARNING!

Carefully follow all instructions for removing the battery from the UPS. Refer to the manufacturer’s web site for detailed photographs.

APPENDIX H: PERIPHERALS AND UPS 139

External ModemAn external modem is required for off-site remote maintenance of the messaging system. An external modem requires either a serial port or USB port connection. Refer to the manufacturer documentation to connect and set up the modem.

External Serial Modem Backplate

To set up an external modem

1 Shut down the messaging system server.

2 Set the SW1 switch on the modem as shown above.

3 Connect the modem to the messaging system server following the manufacturer’s instructions.

SW1

A Connector for dedicated, single-line analog modem line (labeled Telco)

B Switch SW1

C Serial port connector

D Power connector


■ INDEX

Aadministration 41Administration Console 29

icons 72links 73Main Menu 73Navigation pane 73pages 72–73Sign in 73Sign out 74–75

administratorsign in and out 41

arrow keys 3AvBackup utility 111

Bbackup

delayed backup 67immediate backup 67messaging system software 67OS/2 database 127scheduled backup 67transfer OS/2 files 128

backup datacatalog backup file 114verify backup integrity 114

backupsAvBackup utility 111creating manually 113immediate 67levels of backup 111online versus offline 112

basic backup 111battery, UPS 139

Ccommand line interface 3complete backup 112compliance information, third-party devices 1configuration

prompt set 111, 121configuring

dial-up maintenance 62connecting

phone system 43conventions used in documentation 1CoSesssion

compress backup 127

DD4PCI voice board settings 132D82JCTU voice board settings 133

D120JCTLS voice board settings 133default subscriber setting for transfer type 48default subscriber setting screen 48diagrams

D4PCI voice board 132D42JCTU PCI voice board 133D82JCT-U voice board 133Dell connections 137external modem 140VFX41JCTLS fax board 135

documentation, related 4

Ee-mail

configuring 35, 55integration 55subscriber mailbox 57subscriber settings 57

e-mail administrator 53e-mail integration 7, 35, 51, 55

configuring the messaging system 35, 55setting up subscribers 36

e-mail protocols 51IMAP 51MIME 51POP3 51SMTP 51

e-mail server protocolsPOP and IMAP 53

e-mail servers 53expansion boards

See also voice boardschoosing slots 131

external modem, installing 140

FFTP

OS/2 transfer backup 128

GGlobal tone detection 85GTD 85GTDetect 45

See also integration

Hhard disk, backing up 67http 5hypertext links 2

INDEX 141

I - Jicons

Administration Console 72Input devices 3

mouse 3input devices

keyboard 3installation

PuTTY 17WinSCP 15

installingexpansion boards 131external modem 140remote maintenance software 64UPS 138

integrationGTDetect 45learning tones 45selecting phone system 43

integration. See phone system integration

KKey names 1Keyboard 3keyboard

arrow keys 3keypad map, changing 50

LLAN

Windows NT with NetBIOS logon 103language packs

add 87language prompts & TTS

remove 87languages

supported 87learning tones. See GTDetectlevels of backup 111license

change 85License Agreement 5license number. 5licensing information 85

MMaintenance Menu 29maintenance, remote 61mcedit 3messaging system

about 41backing up 113configuration 27environment 23sign in and sign out 41

messaging system serverbuilding 19

messaging system softwarebacking up 67

migratingOS/2 data 130

Migration 121migration

OS/2 121overview (DOS) 117, 121

modem, installing external modem 140Mouse 3

NNavigation pane 73NEAXMail 111NetBIOS 123NetBIOS backup 123NetBIOS over TCP/IP

configuration 123network

Networking checklist 10setup checklist 137

network protocolsNetBIOS over TCP/IP 103

normal backup 112

Ooffline backup 112online backup 112OS/2 backup

migrating 130transfer 127

OS/2 databaseshare backup 127

OS/2 NetBIOS 123

P - Qpassword

security code 33Personal Directory screen, messaging system

changing a subscriber’s transfer type 48phone integration

pooled ringing 42phone system

communication 27information 43

phone system integrationabout 41changing the keypad map 50testing 47

Placeholder text 2pooled ringing 42ports

assigning hunt order 42product registration 5


Product Registration Form 6prompt set configuration 111, 121protocols

IMAP 51MIME 51POP3 51SMTP 51

PuTTY 3installation 17SSH client 18

Rregistration 5related documentation 4remote languages

languagesremove 87

remote maintenanceabout 61installing PuTTY on remote computer 64installing WinSCP on remote computer 64

remote SSH 18removing

the UPS battery 139replacing

the UPS battery 139

Sscreens

Default subscriber settings 48Personal Directory 48

securityprecautions 32recommended practices 32

security coderequiring 32setting minimum length 32

server nameURL 5

shutting down and restarting the system 81Sign in

messaging system 77system manager 77

sign inAdministration Console 77system manager 77

sign in and out 41slots, choosing for expansion boards 131software

remote maintenance 61SPACEBAR 4SSH clients

PuTTY 3WinSCP 3

SSH utilityPuTTY 15

subscriber settings screen, default 48

subscriberschanging transfer type for 48

supported languages 87Switch Extensions 5Switch list 5switch settings, viewing switch information 43system components 19system date and time 29system key

connecting, installation 137system manager

changing default ID 32sign in 77

TTCP/IP

See also NetBIOS over TCP/IPconfiguring for a Windows computer 63

TCP/IP settings 63testing

phone system integration 47touchtones, troubleshooting. See GTDetect.

Uunidentified callers, limiting misdials from 32uninterruptible power supply. See UPSupdating

hardware and software 85overview 85

Upgrading. See updatingUPS

checking the battery 139installing 138

URLserver 5

URLsAdministration Console 5

User input 2using WinSCP 16

VVFX41JCTLS fax board settings 135voice boards

D4PCI 132D82JCTU PCI 133D120JCTLS 133

voice ports, adding 131

W - ZWeb registration 5Windows NT, log on with NetBIOS over TCP/IP 103WinSCP 3

installing 15Interface style 16using 16

INDEX 143

WinSCP client 15wiring fault with UPS 139


um4730 installation guide

Documents

property of nec infrontia

messaging system overview

system upgrades

new system installation

installation checklist

document conventions

exclusive use

product names