NEC Sentry Installation Guide
Have a look at the manual NEC Sentry Installation Guide online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 1168 NEC manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
NDA-30080 Revision 1.0Page 101 Sentry Installation Guide MAT Assignments and PBX Information AKYD Command: (Assignment of Dterm Function Key) The AKYD command can only be used to assign key data on those Dterms that have already been assigned through the ASDT command. MAT Function Key Indexes #34 to #47 have been designated for use in the OAI system and correspond to the 14 OAI Key Codes as illustrated in Figure 6-1 on page 100. The AKYD command is used to assign a D term function key to the specific MAT Function Key Index that, in turn, corresponds to the previously assigned OAI Key Code. This command must be used to assign the function key on each D term that is to be set up with access to Executive Override. 1. In this example, D term function key #8 was designated in the application configuration as the key that is to be pressed to activate Executive Override from the D term. 2. Enter the same tenant number that is configured for the application in the APM Application Configuration option (Tenant #1). 3. Enter the station number of the D term on which the function key is being assigned. 4. Enter the D term function key to the MAT Function Key Index that in turn corresponds to the previously assigned OAI Key Code. Figure 6-2 OAI Function Key Assignment APM Application Configuration Sentry Alarm Control Terminal configured for MSF #129 MAT AOKC Command OAI Key Code #10 given MSF facility type and Op-Code #129 MAT AKYD Command Function Key Index #43 assigned to D term Function Key #8 . . . . .. . . . . . . . . . . PBX Correspondence of AOKC AKYD OAI Function Key Codes Key Indices 1 < . . . .> 34 2 < . . . .> 35 3 < . . . .> 36 4 < . . . .> 37 5 < . . . .> 38 6 < . . . .> 39 7 < . . . .> 40 8 < . . . .> 41 9 < . . . .> 42 10 < . . . .> 43 11 < . . . .> 44 12 < . . . .> 45 13 < . . . .> 46 14 < . . . .> 47
Page 102NDA-30080 Revision 1.0 MAT Assignments and PBX Information Sentry Installation Guide AKYD Command: (Assignment of Dterm Function Key) (Cont) In the example in Figure 6-2, MSF was selected in the APM Application Configuration, and its Op-Code was determined to be #129. MSF #129 is then assigned through the AOKC command to an OAI Key Code. In this example the Key Code is #10. The D term function key that is to be used to access Executive Override is configured as function key #8. Since OAI Key Code #10 corresponds in the PBX to MAT Function Key Index #43, D term function key #8 is assigned to Function Key Index #43 using the AKYD command. Now whenever a phone user presses function key #8 on any assigned D term, MSF 129 initiates communication with Executive Override for display of calling party information. Annoyance TrapAnnoyance Trap requires the following PBX programming: AMNO: Assignment of Monitored Number Assigns a monitored number that is controlled by Annoyance Trap. Enter the same tenant number (except 0) configured for Annoyance Trap, the monitored number that Annoyance Trap will monitor, and the optional UCD pilot number to which calls will be routed when Annoyance Trap is not monitoring the monitored number. Dummy Phone If an audio device is used, a dummy phone must be created. This phone is used to place a call to the audio device, which causes the audio device to make noise. Emergency ConferenceEmergency Conference requires the following PBX programming: 1. A monitored number for each conference. See “AMNO: Assignment of Monitored Number” on page 102 for information on creating a monitored number. 2. A monitored number used to override callers. See “AMNO: Assignment of Monitored Number” on page 102 for information on creating a monitored number. 3. Restrict transfers of route/trunks to a conference monitored number. If such a transfer is attempted, the transferred party should be re-connected to the transferring party. 4. Create a dummy phone used to provide a warning tone when a caller is overridden, using a D term phone with off hook suppression enabled. 5. Use the ASFC MAT command to create an OAI service feature class that enables SFI 24 (the Emergency Call feature). This feature is used to disable a station’s flash hook ability while connected to a conference. For example: SFI = 24; SFC = 3; RES = 1. The SFC you use here must equal the User Define #9 parameter. 6. You can use the ARSC command to prevent any outside phone from joining he conference. RSC for the conference line should be restricted.
NDA-30080 Revision 1.0Page 103 Sentry Installation Guide MAT Assignments and PBX Information No Dial Alarm ConferencingNo Dial Alarm Conferencing requires the following additional PBX programming: 1. The off hook alarm must be enabled, and it must be configured to terminate to a station. Modify the following ASYD index as follows: System 1 Index 168 bit 4=1, bit 5=1 Use the ASID command to specify the off hook alarm station. 2. The off hook alarm station must be set to forward all calls to the No Dial Alarm monitored number using the ACFS command. 3. To set the off hook alarm timer modify the following ASYD indexes: System 1 Index 128 bit 0-3 The value specified by bits 0-3 may range from 0 to 15. A value of 0 will specify a timer interval of 12 seconds. A value of 1 to 15 specified a timer interval that is twice the number value. For example, 1 = 2 seconds, 2 = 4 seconds, etc. 4. All stations that will activate the no dial alarm must have SFI 30 turned on to enable the off hook alarm using the ASFC command, and must be placed in a single group using the ASGD command. Conference Cards PA-CFTB Conference CardsPA-CFTB Conference Cards require the following settings: 1. EPROM #1 should be the following version: SP863 D1 001 This EPROM will allow conference lines to answer calls more quickly. If you use another EPROM version, there will be a delay before the conference lines answer. 2. Conference card switch settings should be as follows: Switch 0 1 3 On 2 4 5 6 7 8 Off Switch 1 1 2 3 4 5 6 7 On 8Off Switch 2 1 2 3 4 5 6 On 7 8 Off 3. When assigning the CFTB card, set TEC=3. RSC and SFC settings for the conference should be different than the RSC and SFC settings for the other phones.
MAT Assignments and PBX Information Sentry Installation Guide Page 104NDA-30080 Revision 1.0 4. Conference card lines must have the following SFI values enabled: 70, 95, 103, 104 (ASFC). 5. Conference cards may be daisy chained together.
NDA-30080 Revision 1.0Page 105 Sentry Installation Guide Platform Maintenance Chapter 7 Platform Maintenance This chapter describes how to use the platform maintenance utility program to perform administrative functions. Logging In To access the platform maintenance utility, use the following steps: 1. Log in to the Sentry Platform Maintenance Main Menu by typing sntryadm at the UNIX login prompt, then press Enter. The login and password prompts are shown below. If your “sntryadm” account requires a password, enter the appropriate password at the subsequent password prompt. The Sentry Platform Maintenance Main Menu displays, as illustrated below: Note: The following sections describe the actions performed by each option. login: sntryadm password: *** Main Menu *** Enter Option: [] Attendant Terminals > Error Log FileUNIXLogout NEC America Inc. Sentry Platform Maintenance Thu May 7, 1998
Page 106NDA-30080 Revision 1.0 Platform Maintenance Sentry Installation Guide Attendant Terminal Maintenance The Sentry Alarm Control Terminal application may be assigned to one or more UNIX tty devices using the attendant terminals option. When you select the Attendant Terminals option from the Sentry Platform Maintenance Main Menu, the Attendant Terminals screen displays with a list of the active terminals. You can use the Attendant Terminals screen to activate, deactivate, or reset attendant terminals. These procedures are described in more detail below. To activate, deactivate, or reset an attendant terminal: 1. Log in to the Sentry Platform Maintenance Main Menu, as described in Logging In on page 105. After a successful login, the main menu displays. 2. Type a and press Enter to select the Attendant Terminals option. The Attendant Terminals screen displays, as illustrated below: *** Main Menu *** Enter Option: [] Attendant Terminals > Error Log File UNIX Logout NEC America Inc. Sentry Platform Maintenance Thu May 7, 1998 NEC America Inc. Sentry Platform Maintenance Thu May 7, 1998 *** Attendant Terminals *** Enter Option: [] Attendant terminals currently activated: Press ‘a’, ‘d’, or ‘r’ to activate, deactivate or reset, respectively, an attendant terminal (or ‘q’ to quit): >
NDA-30080 Revision 1.0Page 107 Sentry Installation Guide Platform Maintenance 3. Do one of the following: To activate an attendant terminal, type a and press Enter. To reset an attendant terminal, type r and press Enter. To deactivate an attendant terminal, type d and press Enter. 4. At the “Enter name of terminal” prompt, type the tty that you want to activate, reset, or deactivate (such as tty12) and press Enter. The tty name must match a tty file name in the “/dev” directory, but does not include the “/dev/” prefix (tty01, tty02, etc.). If an invalid tty name is entered, an error message displays which indicates that the tty that you entered is not a valid device. If you are activating or deactivating the terminal, the “Please enter su/root Password” prompt displays. 5. Type the root password and press Enter, if necessary. If an invalid password is entered the message “su: Sorry” is displayed; otherwise, the procedure continues. A series of prompts display at the bottom of your screen while the terminal is being activated, reset, or deactivated. These prompts may include: “Updating system files”, “Terminal started”, “Terminal updated”. When the process you selected is complete, the Attendant Terminals screen displays, listing the active terminals, as shown in the following example: NEC America Inc. Sentry Platform Maintenance Thu May 7, 1998 *** Attendant Terminals *** Enter Option: [] Attendant terminals currently activated: Press ‘a’, ‘d’, or ‘r’ to activate, deactivate or reset, respectively, an attendant terminal (or ‘q’ to quit): >
Page 108NDA-30080 Revision 1.0 Platform Maintenance Sentry Installation Guide Error Log File Browser This option will be supported in later versions of the software. UNIX Prompt You can use this option to display the UNIX prompt in order to perform UNIX commands, such as cat and ls. To display the UNIX prompt: 1. Log in to the Sentry Platform Maintenance Main Menu, as described in Logging In on page 105. After a successful login, the main menu displays, as illustrated below: 2. Type u and press Enter. The screen clears and the UNIX prompt displays. 3. To return to the Platform Maintenance Main Menu, type sntryadm and press Enter. Log OutYou may log out of the platform maintenance application by doing the following: 1. At the Sentry Platform Maintenance Main Menu, type l and press Enter. The screen clears and the UNIX log in prompt displays. 2. You may return to the platform maintenance main menu by logging in as described in Logging In on page 105. *** Main Menu *** Enter Option: [] Attendant Terminals > Error Log File UNIX Logout NEC America Inc. Sentry Platform Maintenance Thu May 7, 1998
NDA-30080 Revision 1.0Page 109 Sentry Installation Guide History Logging Appendix A History Logging History Logging is controlled through configuration files located in the “/oai/app/ sentry/cfg/history” directory. Events can be logged to one or more serial printers and/or UNIX text files. Unique message formats can be specified for each printer or file. Master Configuration Files Each Sentry OAI Application has a master configuration file located in the “oai/ app/sentry/cfg/history” directory. The master configuration file contains the path names of each configuration file used by the application. The “oai/app/sentry/cfg/history/Mannoy.cfg” master configuration file is created during the Annoyance Trap installation. It contains the following lines: /oai/app/sentry/cfg/history/printDb.cfg /oai/app/sentry/cfg/history/printers.cfg /oai/app/sentry/cfg/history/annoyDb.cfg /oai/app/sentry/cfg/history/annoyLog.cfg The “oai/app/sentry/cfg/history/Mconf.cfg” master configuration file is created during the Emergency Conference installation. It contains the following lines: “/oai/app/sentry/cfg/history/printDb.cfg” “/oai/app/sentry/cfg/history/printers.cfg” “/oai/app/sentry/cfg/history/confDb.cfg” “/oai/app/sentry/cfg/history/confHist.cfg” The “oai/app/sentry/cfg/history/Movr.cfg” master configuration file is created during the Executive Override installation. This file may be shared with all Executive Override installations, or it may be copied to allow different history logging configurations for each application. It contains the following lines: .“/oai/app/sentry/cfg/history/printDb.cfg” “/oai/app/sentry/cfg/history/printers.cfg” “/oai/app/sentry/cfg/history/overDb.cfg” “/oai/app/sentry/cfg/history/overHist.cfg” These files are discussed in greater detail in the following sections. Printer Configuration Files Serial printer links are configured using the printDb.cfg and printers.cfg files which are shared with all Sentry database applications. The printDb.cfg file contains baud rate, parity, data bits, and stop bits configuration constants. This file is created during installation and does not require any modification.
Page 110NDA-30080 Revision 1.0 History Logging Sentry Installation Guide The printers.cfg file contains unique definitions for each printer tty. A template version of this file is created during installation, but printer definitions must be entered after installation. Printer configuration variable names use the format PRINTER_X_????, where X is a sequential number (1, 2, 3, etc.) and the ???? is the variable type (NAME, BAUD, PARITY, etc.). Printer configuration variable names must occur in sequential order, starting with 1. For example, if there are 3 printers in the system, the configuration variables for the first would be called PRINTER_1_????, the second PRINTER_2_????, and the third PRINTER_3_????. The following sections describe the configuration variables defined in printers.cfg. Printer CountThe configuration variable PRINTER_COUNT specifies the number of printers and uses the following syntax: INTCONST PRINTER_COUNT X where X is the number of printers connected to the system (1, 2, etc.). Printer Device NameThe printer tty device name is specified with the PRINTER_X_NAME variable, which uses the following syntax: STRCONST PRINTER_X_NAME “/dev/tty????” where X is the sequential printer number (1, 2, etc.) and the name contained in quotes is the tty device name that is connected to the printer (/dev/tty1a, /dev/tty2a, etc.). Printer Device Baud RateThe printer device baud rate is specified with the PRINTER_X_BAUD variable, which uses the following syntax: INTCONST PRINTER_X_BAUD BAUD_???? where X is the sequential printer number (1, 2, etc.) and BAUD_???? is one of the following baud rate constants defined in printDb.cfg: BAUD_0 BAUD_50 BAUD_75 BAUD_134 BAUD_150 BAUD_200 BAUD_300 BAUD_600 BAUD_1200 BAUD_1800 BAUD_2400 BAUD_4800 BAUD_9600 BAUD_19200 BAUD_38400 Printer Device ParityThe printer device parity is specified with the PRINTER_X_PARITY variable, which uses the following syntax: INTCONST PRINTER_X_PARITY PARITY_????