Norstar Manager Reference Guide

Norstar Manager Reference Guide Norstar is a trademark of Northern Telecom. Microsoft, MS-DOS and Windows are registered trademarks and Windows is a trademark of Microsoft Corporation in the United States and other countries. InstallShield is a registered trademark of InstallShield Corporation. Published in Canada P0866625 Issue 02

Table of contents About this guide 1-1 Introduction 1-1 How this guide is organized 1-1 Other documents 1-2 Conventions 1-2 Setting up Norstar Manager 2-1 Introduction 2-1 PC hardware requirements 2-1 Norstar firmware requirements 2-2 Memory manager requirements 2-3 Changing Norstar Manager preference defaults 2-3 Creating different databases 2-6 Setting up your printer 2-7 Modem requirements 2-7 Norstar Manager performance tips 2-8 Removing Norstar Manager from your PC 2-9 Troubleshooting Norstar Manager 2-9 Norstar Manager Error Messages 2-11 Norstar Manager operation flow charts 2-12 Setting up Norstar Manager on a LAN 3-1 Introduction 3-1 LAN requirements 3-1 Setting up Norstar Manager on the network 3-2 Setting up the central database 3-3 The Network Job Queue 3-3 Starting multi-user mode 3-4 Using Norstar Manager in multi-user mode 3-5 Unlocking customer database files 3-5 Unlocking the customer database 3-6 Unlocking the Job Queue 3-6

2 Table of contents Communicating with the KSU 4-1 Introduction 4-1 Setting up the PC to communicate with the RAD 4-1 Using a DCI 4-3 Setting up a RAD alarm center 4-4 RAD alarm codes 4-4 File handling 5-1 Introduction 5-1 Norstar Manager database structure 5-1 Appendix A: External modem connections A - 1 Introduction A - 1 Hardware required A - 1 Modem Specifications A - 1 Preparing the Remote Modem A - 2 Sample Configuration A - 2 Remote Equipment Installation A - 3 Configuring Norstar Manager A - 3 Glossary Glossary - 1 Index Index - 1

About this guide 1 Introduction This guide is designed to assist the system administrator in setting up Norstar Manager. It provides information on Norstar Manager requirements for a personal computer (PC), local area network (LAN), Remote Access Device (RAD), printer and modem. This guide contains technical information a user does not need for the day to day operation of Norstar Manager. This section explains what is contained in this guide and the conventions used to show commands and options. How this guide is organized The is divided into five sections that cover: About this guide This section explains how this guide is organized and the conventions used in the guide. Setting up Norstar Manager This section explains how you configure your PC to operate Norstar Manager. Setting up Norstar Manager on a LAN This section explains how to configure Norstar Manager for use on a local area network (LAN). Communicating with a KSU This section explains how a PC communicates with a KSU and how this communication link is established. File handling This section provides information about the Norstar Manager database structure, and how to maintain the files within this structure.

1 2 Section 1: About this guide Other documents For more information about Norstar Manager, refer to the: Norstar Manager for Windows User Guide RAD Installation Guide Remote Tools User Guide Conventions This guide uses certain conventions to present information about Norstar Manager. These conventions address: pressing keys choosing action buttons entering information Pressing keys As you work through this guide you will notice some words appear in smaller type, surrounded by a square box. These words represent keys on a PC keyboard. For example: Press Tab Choosing action buttons Words that appear with grey boxes behind them represent action buttons. They perform the task they are labeled with or change the display to a different Norstar Manager screen. For example: Choose Entering information When this guide shows words in a different type face, you are required to type this information. For example: Type cd \wnors3

Setting up Norstar Manager 2 Introduction Before you can begin using Norstar Manager, the software must first be installed and set up on your personal computer (PC). Setting up Norstar Manager on your PC involves: making sure your PC is configured to run the application installing the software on the PC's hard drive changing Norstar Manager defaults creating different databases setting up your printer modem requirements This section explains how you install and set up Norstar Manager on your PC. There is also information about optimizing performance, removing the Norstar Manager software and troubleshooting. See the README.WRI file included with your installation package for installation troubleshooting information. PC hardware requirements The Norstar Manager software is installed on the hard disk of your PC. Before you install Norstar Manager, make sure your computer is a 100% IBM compatible PC equipped with: a 486 or higher microprocessor at least 16 Mbytes (MB) of Random Access Memory (RAM) 400+kilobytes of conventional memory available in Windows 20 MB of virtual memory a hard disk (minimum 100 MB of free space) a 1.44 MB inch floppy drive MS-DOS 5.0 or later Microsoft is a registered trademark and Windows is a trademark of Microsoft Corporation.

2 2 Section 2: Setting up Norstar Manager Microsoft Windows 3.1; Windows for Workgroups 3.11; or Windows 95. a VGA color monitor (640 X 480 pixels or higher resolution. If a higher resolution is used, the Windows font setting should be Small Fonts by default.) a Windows compatible mouse a Hayes compatible modem if you have ordered Norstar Remote Utilities on compact disc, you need a CD-ROM drive to install the program Note: If you are installing Norstar Manager on a LAN, refer to Section 3 of the. Note: For all remote connections, you require a Hayes compatible modem capable of operating at 1200, 2400, 4800, 9600, or 19,200 baud. The modem should also have a separate line port and phone port. To avoid any conflicts or performance delays, we recommend that you do not have any other programs running on the PC while you are working with Norstar Manager. If your computer supports the Control Panel named Display Driver, select small fonts from this control panel. Using large fonts may cause some of the display fields to be cut off. For more information about Control Panel, refer to your Microsoft Windows documentation. Norstar firmware requirements Norstar Manager operates with Norstar DR5 and Norstar-PLUS MICS 1.1 KSU software. Any DR5 or MICS 1.1 software with a version number equal to or greater than those listed will work with Norstar Manager: 3X8 DR5 4.0 Compact DR5 9.20 Compact DS DR5 4.2 Centrex+ 9.20 Modular DR5 9.20 Norstar-PLUS T1 Release 1 Norstar-PLUS Centrex Release 1 Norstar-PLUS CDA-MICS-XC 1.0 Norstar-PLUS USA-MICS-XC 1.0 Norstar-PLUS NA-MICS-DR 1.1 Norstar-PLUS CDA-MICS-XC 1.1 Norstar-PLUS USA-MICS-XC 1.1

Section 2: Setting up Norstar Manager 2 3 Note: Norstar Manager supports full backup and restore operations for DR 5.1, but only supports remote programming of DR 5.1 configuration features which are common to DR5 and DR5.1. Any new configuration features found in DR5.1 (additions to DR5 found in DR5.1) must be remotely programmed using the Remote Set tool. Memory manager requirements Norstar Manager is designed to operate with HIMEM.SYS, the extended memory manager that comes with Microsoft Windows. We strongly recommend that you use this memory manager. If you use a different memory manager application, Norstar Manager may not operate properly. For information about installing and using HIMEM.SYS, see your Windows documentation. Changing Norstar Manager preference defaults Several of the Norstar Manager preference default settings can be customized to suit your specific application. Default settings for the preferences are the values that first appear in a field when you access the Norstar Manager Preference screen. Note: Norstar Manager preference default settings are provided to ease the use of Norstar Manager. Most of the default parameters can be changed on Norstar Manager screens when non-default parameters are required. Listed below are the preference default settings choices and a description of what each setting affects. COM port: This is the communication port on the personal computer that Norstar Manager uses to communicate with the KSU. You can select COM1, COM2, COM3 or COM4. Connect type: Norstar Manager uses three different ways to connect to the KSU: Direct, Remote or Operator Assisted. The connection type used depends on where the KSU is located, relative to the PC, and how the Remote Access Device (RAD) is connected to the KSU. Baud rate: This is the communication rate used by Norstar Manager to communicate with a KSU in an online session, a backup, or a restore.the default is 19200. If you are using a direct connection, the local baud rate at the RAD must match the baud rate chosen for the direct connection in Norstar Manager. If you are using a remote type of connection, 1200, 2400, 4800, 9600 or 19200 baud can be used. If you choose a baud rate for a remote connection that is higher than the rate supported by the RAD, your modem will auto-baud down to the modem speed of the RAD. It is strongly recommended that you use 9600 baud or higher for Remote or Operator Assisted connections. Connection device: This is the device used by the PC to communicate with the RAD. You can choose either a modem or a Norstar Data Communications Interface (DCI) as the connection device. If you choose a DCI, you must change the Modem init string. Refer to Section 4, Using a DCI for more information. Note: The DCI is not supported by Norstar-PLUS MICS systems. On these systems you can only use a modem.

2 4 Section 2: Setting up Norstar Manager Dial mode: The dial mode used by Norstar Manager can be either pulse or tone. Norstar Manager Modem init string: Some modems require special codes to be sent to them before they are ready to communicate. Use this field to enter any special codes that Norstar Manager must send to your modem before it is ready to communicate with the RAD. Note: For on-line help, click on the icon called Norstar Manager Error Messages. This brings up a file in Write (Windows 3.1) or WordPad (Windows 95). See Modem Initialization String Problems. The default value for the Modem init string is &FQOV1&C1&D2S7=85&S0. If your modem cannot connect to a RAD, you may have to change this string. Refer to your modem manual for information on what codes must be included in the Modem init string. There is a default or existing internal string that the application automatically displays in the Modem Init String field which contains the following elements: &F Q0 V1 &C1 &D2 Load default factory configuration Return response codes Return verbal response codes Set the carrier detect (CD) high when the remote carrier is detected and drop the CD when the remote carrier is lost Accept commands only when data transfer ready (DTR) is high and drop the call when DTR is low S7=85 Wait up to 85 seconds for the remote carrier to be detected &S0 Data set ready (DSR) always on If your modem cannot connect to a RAD, you may use the modem init string field to include additional commands at the beginning or end of the string, or to edit the existing string to be sent to your modem. Refer to your modem manual for information on what codes must be included in the Modem init string, and whether the codes you add should be sent before or after the default ones. Note: In general, you should not delete or alter any of the commands in the default string. However, the modem wait for carrier delay (S7) must be set to include both the delay before the RAD auto-answers and the time for the call to be dialed and connected. Some modems have a maximum wait of 60 seconds. If this is the case, you may set S7 in the modem init string to a lower value. If you lower the S7 value and also want the RAD to auto-answer before the modem times out, you must ensure that the seconds to wait before answering at the RAD is less than the S7 value. For best results, set the maximum modem speed to the maximum connect speed. Note for US Robotics modem users: Be sure to add &I0 and &B1 to your modem init strings. &I0 Software flow control disabled

Section 2: Setting up Norstar Manager 2 5 &B1 Fixed serial port rate Note: For on-line help, click on the icon for Norstar Manager Error Messages. This brings up a file in Write (Windows 3.1) or WordPad (Windows 95). See Modem Initialization String Problems. Language: Norstar Manager is designed to provide all of the screens and prompts in either English or French. Use this field to change the language displayed by Norstar Manager. The language will change when you exit from Norstar Manager and log on again. Job Queue path: Enter the path for the directory where the Job Scheduler will be run. To run a local Job Scheduler, enter the path for a directory on the hard drive of your PC. To run a network Job Scheduler, enter the path for a directory on the network drive. If you are using a network Job Scheduler, you should enter the same path on each PC running Norstar Manager. For more information about the Job Scheduler, refer to Section 7, of the Norstar Manager for Windows User Guide. Default customer path: Enter the path for the default directory where the customer databases are stored. If you enter the pathname for the network drive, Norstar Manager will start in multi-user mode the next time you log on. Backup speed dialers: When you perform a backup of a Norstar system, all of the information stored in the KSU is copied to the Norstar Manager database. On certain systems, you may want to backup all of the Norstar system information except the personal speed dial numbers. To backup all of the information except the personal speed dialers, make sure this check box does not contain an X. To change the Norstar Manager preference defaults: 1. Log on to Norstar Manager. The display must show the Systems Directory screen before continuing. 2. Choose the Preferences menu. The Preferences screen appears.

2 6 Section 2: Setting up Norstar Manager Figure 2.1 The Preferences screen 3. Select the field of the default setting you want to change and choose or type the new value. Repeat this step for each default setting you want to change. 4. Choose to exit from this screen and implement your changes. Creating different databases When Norstar Manager is installed on your PC's hard drive, you can create multiple databases. For example, you may want to set up a database for Norstar systems installed in a specific city. Before you begin, make sure the Systems Directory screen appears on your monitor. To create a new database: 1. Choose the File menu and then the Change Customer Path menu item. 2. Type the new database pathname. Note: You must specify a directory name. Norstar Manager will not create a database in the root directory of any drive. 3. Choose You can also create a new database when you start Norstar Manager. To create a new database: 1. From the Windows Program Manager, choose the Norstar Manager icon (Windows 3.1); or click Start, then select Norstar Manager from the Program menu (Windows 95). 2. Enter your User ID and Password.

Section 2: Setting up Norstar Manager 2 7 3. Select the Current customer path field and type the pathname of the new database. 4. Choose Note: Do not change the customer path to the directory c:\wnors3\template. If you use this directory, you may corrupt the blank database files used to add new systems. If these files become corrupted, you must re-install Norstar Manager. Setting up your printer Norstar Manager has a report feature that allows you to print a listing of a Norstar system's configuration, either to file on your PC's hard drive or to a printer. Before you can use this feature to print a listing to a printer, you must set up your printer correctly. Refer to your Windows manual for instructions on setting up your printer. Modem requirements Norstar Manager uses either a 1200, 2400, 4800, 9600, or 19200 baud modem to communicate with a remote KSU. This modem must be a Hayes compatible modem which supports the standard attention code (AT) commands shown in Table 2.1. Norstar Manager controls baud rate, parity, and stop bit settings and automatically sets your modem to the proper configuration. Note: It is recommended that you use 9600 baud or higher (depending on the rate the RAD supports) to optimize communication performance. You must connect to the FastRAD using 4800 baud or higher. Code &F V1 Q0 &C1 &D2 Meaning Recall factory setting as active configuration. Verbal form Modem returns result codes. Track presence of data carrier. Hang up and assume command state when an on-to-off transition of DTR occurs. Sr=n Set register r to value n. X1 Enables result codes 0-5, 10-12, 14. &S0 Data set ready (DSR) always on. Table 2.1 Standard AT commands

2 8 Section 2: Setting up Norstar Manager Norstar Manager performance tips In certain situations you may find that Norstar Manager is operating too slowly. If you do, we recommend you do one or more of the following things to increase the speed of Norstar Manager: Use a faster PC. Using a faster PC, such a Pentium-based PC, is the most effective way to increase Norstar Manager performance. Do not run any other programs. All programs that are operating on a PC, even those reduced to a icon, require some of the PC's resources to operate. This means that any program that is running while you are using Norstar Manager will cause Norstar Manager to slow down somewhat. For this reason we recommend that you do not run any other programs while you are using Norstar Manager. Use the MS-DOS application SMARTDrive. SMARTDrive is an application that decreases the time it takes to read data from the hard disk. This application is included with MS-DOS. See your DOS manual for information about setting up SMARTDrive. Use 9600 baud. Use 9600 baud or higher, if supported by the RAD, when you are using Norstar Manager to perform a backup, restore or remote online session. Use clean telephone lines. Using telephone lines that have very little noise reduces the number of communication errors that occur between the KSU and Norstar Manager. With fewer errors, the data is transmitted to and from the KSU faster. Use public network lines. Private network lines are usually compressed to make transmission more economical, but the compression can interfere with the connection between the PC and KSU. Use public network lines when making a connection to the KSU, or arrange ahead of time to have an uncompressed 64 kbps line available on your private network.

Section 2: Setting up Norstar Manager 2 9 Removing Norstar Manager from your PC In the event that you want to remove Norstar Manager from your PC, you must delete the program files and the customer database files from the hard disk. If you are using Windows 3.1, you can uninstall Norstar Manager using the uninstall icons included in the Norstar Remote Utilities Program Group. If you are using Windows 95, you can use Add/Remove Programs from the control panel. You will still have to remove the customer directory information (CUSTOMER.DB) manually as described in the following procedure. Note: On PCs that are working on a network, the customer database files are normally stored on the network drive. If the customer files are stored on the network drive, you only have to perform step 6 to remove the program files. If the uninstall or Add/Remove Programs options are not available, use the following steps to remove Norstar Manager from your PC: 1. Log on to Norstar Manager and access the Preferences screen. 2. Write down the pathname of the directory specified in the Default customer path field. 3. Quit the Norstar Manager application. 4. Use MS-DOS or Windows to check the hard drive for any other customer directories. Write down the pathnames of all the directories you find. 5. Make a copy of all of the customer database files that are in the directories you wrote down. These copies can be used as a record of the customer programming or to re-install the customers on a different PC. 6. Use MS-DOS or Windows to delete all of the files and subdirectories contained in the directory WNORS3 and then delete the directory itself. This removes all of the Norstar Manager program files. Note: If your customer database files reside on a network drive, you are now finished removing Norstar Manager. 7. Delete all of the files and subdirectories stored in the customer directories and then delete the customer directories themselves. The pathnames of the customer directories are the pathnames you wrote down earlier. See your MS-DOS manual or Windows manual for instructions on deleting files and directories. Note: The uninstall process does not remove your Norstar Manager customer database, preferences, or backup files from a previous installation of Norstar Remote Utilities. Troubleshooting Norstar Manager If Norstar Manager or other applications unexpectedly exit to the Windows Program Manager, you should cold boot the PC before starting Norstar Manager again. To cold boot the PC, exit Windows, turn the PC off, wait a few moments and then turn the PC on. This clears the memory in the PC and ensures that Norstar Manager will run properly. After cold booting the PC, run the CHKDSK and SCANDISK commands. Delete any files that were created when you ran CHKDSK or SCANDISK.

2 10 Section 2: Setting up Norstar Manager For more information about the CHKDSK or SCANDISK command, see your MS-DOS manual. Norstar Manager is designed to work with the default configuration of Windows. Varying from the default Windows configuration may cause a conflict with Norstar Manager. If you feel there is a conflict between Norstar Manager and another Windows application, check with a Windows reference guide such as the Microsoft Windows Resource Kit for Program Manager Version 3.1 manual.

Section 2: Setting up Norstar Manager 2 11 Norstar Manager Error Messages When you get an error message from Norstar Manager, you need to determine what the error message means and how it affects the Norstar system and Norstar Manager. To determine what the error message means, read the Norstar Manager Error Messages file. This file uses Write (Windows 3.1) or WordPad (Windows 95). See your Windows documentation for an explanation of how to use the program. To access this file in Windows 3.1: 1. Move to the Windows Program Manager. 2. Open the Norstar Manager program group. 3. Open the Norstar Manager Error Messages file. 4. Scan through the list of error messages to find the one you require. 5. When you are finished with the error message file, close the file and return to Norstar Manager. To access this file in Windows 95: 1. Click Start. 2. From the Program menu, select the Norstar Manager program group and the Norstar Manager Error Messages file. 3. Scan through the list of error messages to find the one you require. 4. When you are finished with the error message file, close the file and return to Norstar Manager. In most cases, the description of the error in the error messages file clearly defines what is wrong and what needs to be done. In some cases however, you need to know more about Norstar Manager processes to determine what affect the error has. For example, if an error occurs in the restore process it is important to determine if the sets were enabled or disabled when the error occurred. The following diagrams show the three processes that interact with the KSU: backups, restores, and on-line sessions. You can use these diagrams to become familiar with the processes, better determine the cause of an error message, and determine a solution for it.

2 12 Section 2: Setting up Norstar Manager Norstar Manager operation flow charts User or scheduler selects the customer database and initiates a restore Establish a connection to the KSU Validate the KSU type Disable the CAPs Program the CAPs Enable the CAPs Disable the sets Restore the data tables Enable the sets Warm reset the KSU Disconnect from the KSU Clean up the database and return control to the user or scheduler Figure 2.2 The process for a restore

Section 2: Setting up Norstar Manager 2 13 User or scheduler selects the customer database and initiates a backup Establish a connection to the KSU Validate the KSU type Check the table tags (if a partial backup) Back up the data tables Update the tables tags Disconnect from the KSU Clean up the database and return control to the user or scheduler Figure 2.3 The process for a backup

2 14 Section 2: Setting up Norstar Manager User selects the customer and initiates an on-line session Establish a connection to the KSU Validate the KSU type Read screen data from the KSU Write changes to the KSU User ends the on-line session Disconnect from the KSU Figure 2.4 The process for an on-line session

Setting up Norstar Manager on a LAN 3 Introduction To use Norstar Manager in a local area network (LAN) configuration, you must: install Norstar Manager on each personal computer (PC) that will use Norstar Manager and is connected to the LAN set up a central database on the LAN's file server This section explains how you add Norstar Manager to your network. LAN requirements Norstar Manager operates on any LAN that supports NETBIOS. Specifically, Norstar Manager is designed to operate on a Banyan or Novell network. We recommend that your LAN also has the following characteristics: printer spooling services 1 Gbyte of hard disk space Each PC running Norstar Manager on the network must be at least a 486 PC with a 100 MB of free hard disk space and VGA color monitor. Note: To avoid any conflicts or performance delays, we recommend that you do not have any other programs running while you are working in Norstar Manager. A typical LAN configuration is shown in Figure 3.1

3 2 Section 3: Setting up Norstar Manager on a LAN PC running Norstar Manager Printer with print spooler File Server with 1Gbyte of hard disk space PC running Norstar Manager Remote PC running Norstar Manager Figure 3.1 Example of a LAN configuration Setting up Norstar Manager on the network Before you install Norstar Manager, you must setup the network. Norstar Manager must be installed on each PC attached to the Norstar Manager network. For instructions about installing the Norstar Manager software, refer to Section 2. After you have the Norstar Manager software installed on each PC, you must alter the settings on the Preferences screen so it specifies: where the central database files are to be located where the Job Scheduler is located which Job Queue you are using For more information about the Preferences screen, refer to Section 2, Changing Norstar Manager preference defaults.

Section 3: Setting up Norstar Manager on a LAN 3 3 Setting up the central database A centralized database directory allows network users to access and update a common set of Norstar system files. You can create a central database directory once you have defined where the database will be located. When you first start up Norstar Manager, a central database directory named c:\wnors3 already exists. You need to create a new central database directory only if you want to use a directory other than the one that exists. To create a the new central database: 1. Begin from the Systems Directory screen. 2. Choose the File menu and then the Change Customer Path menu item. The Change Customer Path dialog box appears. 3. Select the Enter customer data base path field and type in the pathname of the central database. 4. Choose to return to the Systems Directory screen. After the central database is created, you can move to the new database using the method described above. You can also have the new database appear when you start Norstar Manager using one of the two methods described below. To start Norstar Manager with the new central database: 1. From the Windows Program Manager, choose the Norstar Manager icon (Windows 3.1); or click Start, then choose Norstar Manager from the Program menu (Windows 95). 2. Enter your User ID and Password. 3. Select the Current customer path field and type the pathname of the central database. 4. Choose To change the default directory to the new central database: 1. Navigate through Norstar Manager until the Systems Directory screen appears on your monitor. 2. Choose the Preferences menu. The Preferences screen appears. 3. Select the Default customer path field and type in the pathname of the central database. 4. Choose to return to the Systems Directory screen. The Network Job Queue When you are using Norstar Manager on a network, you have the option of running the Job Queue on the network server. The Job Queue that operates on the network server is called the Network Job Queue. All of the Norstar Manager users on the network can schedule jobs to run on the Network Job Queue.

3 4 Section 3: Setting up Norstar Manager on a LAN To schedule a job to operate on the Network Job Queue, you must access the Preferences screen and change the Job Queue path field to the pathname of the network drive. The advantage of using the Network Job Queue is that it is easier to keep track of jobs being scheduled. Since all of the jobs being sent are on the same queue, you have to check only one screen to see which jobs are pending. This reduces the possibility of missing a job or inadvertently repeating a job. Any Norstar Manager user that can submit a job to the Network Job Queue can also run a job from the queue. To run the Network Job Queue, move to the Job Queue screen and then choose the Queue menu and the Run menu item. Jobs from the Network Job Queue will now be run from your PC. For more information about Job Queues, refer to Section 7 of the Norstar Manager for Windows User Guide. The Network Job Queue can be run by several Norstar Manager PCs. The advantage of running jobs from several PCs is that several jobs can be run at the same time. Each PC running the Network Job Queue can run a job. Therefore, you can have as many jobs running at one time as you have PCs running the Network Job Queue. When you are viewing the Network Job Queue, Norstar Manager does not automatically update the screen to show the job added or deleted by other users. To make Norstar Manager update the Network Job Queue, choose Starting multi-user mode Norstar Manager will switch to multi-user mode when you change the customer path to the pathname of the network drive. To change to multi-user mode: 1. Move to the Systems Directory screen. 2. Choose the File menu and then the Change Customer Path menu item. 3. Type in the pathname of the network drive. 4. Choose The Systems Directory screen appears. Norstar Manager is now operating in multi-user mode. Norstar Manager will automatically start in multi-user mode when you have the network server chosen as your default customer path. To have Norstar Manager start in multi-user mode: 1. Move to the Systems Directory screen. 2. Choose the Preferences menu. The Preferences screen appears. 3. Select the Default customer path field and type in the pathname of the network drive. 4. Choose The Systems Directory screen appears.

Section 3: Setting up Norstar Manager on a LAN 3 5 Norstar Manager will now start in multi-user mode. Using Norstar Manager in multi-user mode Norstar Manager operates the same in multi-user mode as it does in single-user mode. The difference is that you are using customer files from the network server. In multi-user mode, is used to update the data shown on the Job Queue screen and the Systems Directory screen. When you choose this action button on the Job Queue screen, the screen changes to show any jobs that were added by other users. On the Systems Directory screen, this action button changes the screen to show any new customer databases that were added by other users. Unlocking customer database files Norstar Manager locks customer database files to prevent more than one user from accessing a file at the same time. If you try to access a customer file that is in use by another user, Norstar Manager will give you a message that states the customer file cannot be opened because it is locked. The database files are locked when you: start an on-line session edit the customer information using the Edit System Details screen copy system attributes copy systems delete a system When you exit from the on-line session or the System Details screen, Norstar Manager releases the lock. Other users can then use the customer database file. However, if Norstar Manager stops functioning before you exit from any of these five situations, Norstar Manager cannot remove the lock. The customer database file is then unavailable for use by any user until you remove the lock. An example of a situation where Norstar Manager can leave a file locked is if there is a power fail while you are copying a system. To remove the lock: 1. Exit from Norstar Manager. 2. Exit from the Windows Program Manager (Windows 3.1); or click Start, then choose the MS-DOS prompt (Windows 95). The DOS prompt is now displayed. 3. Move to the default customer directory. For example, if the Norstar Manager database resides on drive f, type f: to switch to the drive.then, type cd\wnors3 to move to the default customer directory. Note: If you are using a directory other than the default (wnors3), move to that directory. 4. Type del wnorsmgr.loc This removes the lock.

3 6 Section 3: Setting up Norstar Manager on a LAN 5. Start the Windows operating environment and log back on to Norstar Manager. Important: Before you unlock a file, check with the other Norstar Manager users to ensure they are not using that file. If you unlock a file that is in use by another user, you may damage the file. Unlocking the customer database In certain situations, such as when you are adding a new customer to the database, Norstar Manager will briefly lock the entire customer database. If Norstar Manager stops functioning while the customer database is locked, users will not be able to view the Systems Directory screen and thus will not be able to use Norstar Manager. To unlock the customer database: 1. Exit from Norstar Manager. 2. Exit from the Windows Program Manager (Windows 3.1); or click Start, then choose the MS-DOS prompt (Windows 95). The DOS prompt is now displayed. 3. Move to the default customer directory. For example, if the Norstar Manager database resides on drive f, type f: to switch to the drive.then, type cd\wnors3 to move to the default customer directory. Note: If you are using a directory other than the default (wnors3), move to that directory. 4. Type del customer.loc This removes the lock from the customer database. 5. Start the Windows operating environment and log back on to Norstar Manager. Note: Due to the very short time that the customer database is locked, it is very unlikely that you will have to unlock it. Unlocking the Job Queue In certain situations, Norstar Manager will briefly lock the Job Queue. If Norstar Manager stops functioning while the Job Queue is locked, users will not be able to view the Job Queue screen. To unlock the Job Queue: 1. Exit from Norstar Manager. 2. Exit from the Windows Program Manager (Windows 3.1); or click Start, then choose the MS-DOS prompt (Windows 95). The DOS prompt is now displayed. 3. Move to the default customer directory. For example, if the Norstar Manager database resides on drive f, type f: to switch to the drive.then, type cd\wnors3 to move to the default customer directory. Note: If you are using a directory other than the default (wnors3), move to that directory.

Section 3: Setting up Norstar Manager on a LAN 3 7 4. Type del jobqueue.loc This removes the lock from the Job Queue. 5. Start the Windows operating environment and log back on to Norstar Manager. Note: Due to the very short time that the Job Queue is locked, it is very unlikely that you will have to unlock it.

3 8 Section 3: Setting up Norstar Manager on a LAN

Communicating with the KSU 4 Introduction Norstar Manager uses a Remote Access Device (RAD) to communicate with a Norstar KSU. The RAD receives calls from the PC, and authorizes access to the KSU. The RAD also reports KSU alarms to a printer or terminal located on-site or at a remote location. This section explains how you connect your PC to the RAD, and how the PC uses the RAD to communicate with a Norstar KSU. Note: The Internal RAD (I-RAD) used with the Compact ICS does not support Norstar Manager. Use Remote Tools to administer a Compact ICS. Setting up the PC to communicate with the RAD The PC is connected to the RAD either through a direct connection, or a remote connection. In a direct connection the PC communicates directly with the RAD, while a remote connection requires the use of a modem. In a direct connection, the RAD is connected to one of the PC's COM ports by an RS-232 cable. In this type of connection, the data transfer rate between the PC and the KSU is 9600 baud. This cable must be constructed as shown in the pinout diagram in Figure 4.1. When connecting with a global RAD or FastRAD, refer to Figure 4.2. When you are using a direct connection, you do not need a modem, and you do not specify a phone number for the RAD in Norstar Manager programming. For more information on RAD programming, refer to the Norstar Manager for Windows User Guide.

4 2 Section 4: Communicating with the KSU RAD 25 pin D-type male connector TX RX CTS DSR GND DCD DTR 2 3 5 6 7 8 20 2 3 5 6 7 8 20 Personal computer port 25 pin D-type female connector RAD 25 pin D-type male connector TX RX CTS DSR GND DCD DTR 2 3 5 6 7 8 20 3 2 8 6 5 1 4 Personal computer port 9 pin D-type female connector Figure 4.1 Pinout diagram for RAD to PC cable Global RAD/ FastRAD 9 pin D-type male connector DCD RX TX DTR GND DSR CTS 1 2 3 4 5 6 8 8 3 2 20 7 6 5 Personal computer port 25 pin D-type female connector Global RAD/ FastRAD 9 pin D-type male connector DCD RX TX DTR GND DSR CTS 1 2 3 4 5 6 8 1 2 3 4 5 6 8 Personal computer port 9 pin D-type female connector Figure 4.2 Pinout diagram for Global RAD to PC cable

Section 4: Communicating with the KSU 4 3 In a remote connection, the RAD is located on site with the Norstar KSU, and the PC is located elsewhere. Figure 4.3 shows an example of a remote connection. A modem handles communication between the PC and the RAD. The modem is connected to the public telephone network, and dials a phone number that connects the PC with the RAD. The RAD then checks the RAD password. If the password is correct, the RAD allows the PC access to the Norstar KSU. If you plan to use an Operator assisted connection, a standard analog telephone must be attached to the modem. The modem is connected to the PC by an RS-232 cable. This cable must be constructed according to the instructions contained in the manual that came with your modem. This modem must follow the standards outlined in Section 2, Modem requirements. To configure your modem correctly, refer to the manual that came with your modem. To configure the RAD correctly, refer to the RAD Installation Guide. RAD Key Service Unit (KSU) PC Modem RS-232 Cable Figure 4.3 Example of a Remote Connection Using a DCI When you are using a Norstar Data Communications Interface (DCI) for a remote connection, you must add the required prefix digits to the RAD telephone number. The RAD telephone number must be preceded by 1x+ (where 1 indicates an external line, x is the CO line number, and + indicates a DCI is being used). For example, if the RAD's telephone number was 263-6805, you would enter 12+2636805

4 4 Section 4: Communicating with the KSU You must also change the Norstar Manager default Modem init string to contain S7=55. The modem init string used for a DCI is &FQ0V1&C1&D2S7=55. You should also use &S0 (Data set ready always on) in the string. For more information about the modem init string, see Section 2, Changing Norstar Manager preference defaults. When using a DCI for a remote connection, you must program the RAD to answer the call within 55 seconds (approximately eight rings). Note that this 55 seconds includes the connection time through the public switched network. If there is a significant delay in connecting to the RAD, you may have to program the RAD to answer in less than eight rings. For more information about connecting a DCI to a KSU, see the DCI User Guide. Setting up a RAD alarm center The RAD can be programmed to report alarms to a dedicated alarm device. An alarm device can be a printer, a terminal or a PC that is set up to log incoming reports. Usually, the alarm device is located in a central location, perhaps near your PC, and collects alarm reports from several systems. Figure 4.4 shows how a RAD alarm center is set up. RAD Distribution block Norstar KSU CO line Modem Terminal Figure 4.4 Overview of how a RAD alarm center is set up RAD alarm codes When a RAD receives an alarm from the KSU, it dials the telephone number of the modem attached to the dedicated alarm device and transmits an alarm string. This string identifies the System ID number and the alarm code.

Section 4: Communicating with the KSU 4 5 In some cases RAD alarm codes do not match KSU alarm codes. Table 4.1 shows the KSU alarm code equivalents to RAD alarm codes. Use this table when you are trying to interpret RAD alarm codes. KSU reported 52-X-1 52-X-2 52-X-3 61-X-1 61-X-2 61-X-3 RAD reported 52-X-0-1 52-X-0-5 52-X-0-9 61-X-0-1 61-X-0-5 61-X-0-9 Table 4.1 KSU and RAD alarm cross reference In Table 4.1: X is the port number (1-8) 52 means the Trunk Cartridge is disconnected from the Trunk Module 61 means the Trunk Cartridge is incompatible 1,2,3 indicates the Trunk Cartridge number 1,5,9 indicates the Trunk Cartridge line number Note: For more information about Alarm Codes, see the appropriate Norstar Installer Guide, or the Norstar Companion Alarm and Event Code Manual.

4 6 Section 4: Communicating with the KSU

File handling 5 Introduction When Norstar Manager refers to a database, it is referring to a collection of files that reside in a directory on your PC's hard drive or the network file server. These files are organized in a hierarchical structure. This section explains the Norstar Manager database structure. Norstar Manager database structure When Norstar Manager is first installed on your PC s hard drive, standard directories and files are created and installed. Norstar Manager's standard directories and their structure are shown in Figure 5.1.

5 2 Section 5: File handling Wnors3 Dd Customer Jobqueue KSU Preferen Startup template 3x8 Cds Cmp Ct1 Ctx Dr 11 Mega Metq Mod Nat1 Customer.db Jobqeue.db Figure 5.1 Norstar Manager standard directory structure Each of the standard directories contains a number of files. The wnors3 directory contains Norstar Manager's program files. The wnors3\template directory contains default files Norstar Manager uses to create new databases.

Section 5: File handling 5 3 Wnors3 Current.kcp Customer.db Dbstartw.exe English.dll Errcodes.wri Ferrcode.wri Francais.dll Jobqueue.db Nstarras.dll Preferen3.db Ras.exe Rasfont.fon Wnorsmgr.exe wnors3\template Cmp Empty.db Mod Empty.db Figure 5.2 Norstar Manager files When a Norstar system is added to the Norstar Manager database, a subdirectory containing default KSU data files is automatically created. This subdirectory is formed under Norstar Manager's default directory and is labeled with the Norstar System ID. For example, if the default customer directory is customer and you add Norstar system number 1234567890, the database structure shown in Figure 5.3 is formed. Customer 12345678.90 Archive Ksu.db current Ksu.db Figure 5.3 Adding a Norstar system to the database The Current directory stores the latest backup of the customer programming. This copy contains the programming data that was in the KSU at the time of the last backup. When you perform a backup, programming information from the Norstar KSU is stored in this directory.

5 4 Section 5: File handling The Archive directory stores the previous version of the information in the current directory. When you perform a backup on a KSU, the backed up information from the KSU is placed in the current directory, and information in the current directory is placed in the archive directory. Note: The Archive directory is not created until you use the backup feature to make an archive copy of the Norstar system. The Backup and Restore tool can also be opened through Norstar Manager for systems which support Norstar Remote Tools. Current backup files are stored as.new files, and the archive versions are stored as.old files. See the Remote Tools User Guide for more information. Customer 12345678.90 FNVRAM.NEW FNVRAM.OLD AATTEND.NEW AATTEND.OLD Figure 5.4 Backup files for Norstar systems which support Remote Tools Note: When you use Norstar Manager s copy systems feature, the backup files created by Norstar Remote Tools may have to be manually copied to another location. For more information on copying Norstar systems, see Section 8 of the Norstar Manager for Windows User Guide.

Appendix A: External modem connections Introduction This appendix provides information required for a remote connection from Norstar Manager to the RAD at 9600 baud. Note: This does not apply to the FastRAD. Hardware required The following is a list of the hardware required at the remote KSU end: RAD Hayes compatible external modem 9600 baud or higher standard RJ11 telephone cable null modem cable or adaptor 25 pin RS-232 female/male gender changer may be required direct telephone line Modem Specifications The modem must be configured from a PC prior to connecting it to the RAD. Modem manufacturers use different commands for implementing the features listed below. For more information, refer to the manual that came with your modem. 1. The modem must be set to answer at a maximum of 19200 Baud. Note: The RAD will not communicate at speed higher than 19200. 2. The modem must be set to Auto Answer (the standard ATS0=1 command will work on all Hayes Compatible modems). 3. The modem must be commanded to control the Data Set Ready (DSR) as per CCITT standards (ITU-T). By default most modems come configured to with DSR High as Always ON. 4. The modem must be set to ignore the Data Terminal Ready (DTR) signal. The modem needs to assume that DTR is Always ON.

A 2 Appendix A: External modem connections 5. The modem must be configured to allow the DTE/DCE rate to follow the link rate. This means that the modem to RAD baud rate will be set to the same rate as Norstar Manager connects with the modem. Since Norstar Manager will be set to connect at 9600 baud with this modem, the modem will in turn communicate with the RAD at 9600. 6. These setting must then be saved in the Modems NVRAM (Non Volatile Memory) so the settings will become the modems power up defaults. Note: If the settings are not saved and the modem is powered off and on, they will disappear, and the modem will not communicate with a RAD until it is reprogrammed. Preparing the Remote Modem To prepare the remote modem, connect it to the PC. The Windows installation process puts Terminal in the Accessories folder by default. Open Windows and from the Terminal program: 1. Choose Settings from the pull down menu. 2. Choose Communications from the pull down menu. 3. Set the COM port to the port that has the modem connected using a compatible baud rate. 4. Click to return to the Terminal screen. 5. Enter the ATZ command. If OK appears, enter each command required to set the modem. Note: If OK does not appear, the port is not configured correctly, the modem is not properly connected, or isn t powered on. When you have entered the commands appropriate for the modem being used, exit the Terminal Program. The modem is now ready to be hooked up to the remote RAD. 6. Enter the commands required to initialize the modem. Each command is terminated with a carriage return. Refer to the Sample Configuration, later in this appendix. Sample Configuration Northern Telecom (Nortel) has tested a configuration using a Zyxel U-1496E modem connected to the RAD using the following commands to program the modem: AT&N3 ATS0=1 AT&S1 AT&D0 AT&B0 AT&W // Force modem to make maximum 9600 baud // Connects // This has modem auto answer on first ring // This configures modem to control DSR // This configures the modem to ignore DTR // DTE/DCE rate follows link rate // This instructs modem to write the new // settings into NVRAM Note: This is a sample, and will probably not work with any other type of modem. Refer to the manual that came with your modem.

Appendix A: External modem connections A 3 Remote Equipment Installation To install remote equipment for a direct connection: 1. Connect the RAD to the KSU port with a standard TCM cable. 2. Connect the pre-configured modem to the RS-232 port on the RAD using the null modem cable. 3. Connect the modem to the direct line using the standard RJ11 telephone cable. TCM cable to KSU RAD RS-232 null modem cable Modem RJ11 telephone cable To direct line Figure A.1 Remote equipment installation Configuring Norstar Manager To configure Norstar Manager 2.1 or greater, run Norstar Manager as if you were doing a remote connection to the KSU. Specify a connection type of remote, a baud rate of 9600, and supply the telephone number of the direct line that the remote modem is connected to.

A 4 Appendix A: External modem connections

Glossary Access The method by which you gain entry to the Norstar Manager database or a Norstar Manager screen. Alarm Indicates an error condition in the RAD or KSU. Analog Terminal Adapter (ATA) A device that allows analog telecommunication devices, such as a single line telephone, to connect to the Norstar system. ASCII (American Standard Code for Information Interchange) text file A standard text file that can be read by several different software programs. When Norstar Manager prints a report to a file, it puts information in this format. Backup The process of making a copy of a Norstar KSU's programming. This copy is stored in the Norstar Manager database. Block A section of text or data. Command An action or task. Communicate The exchange of information between your PC and a Norstar KSU. Configuration A type of programming that assigns certain settings to Norstar systems, lines, and sets. Connection A link between a KSU and PC. This link is either established through a modem or directly through an RS-232 connection.