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 71 Sentry Installation Guide Emergency Conference Tenant Number DatabaseThe Tenant Number database is shared with other Sentry applications, so you might not have to build it for Emergency Conference. You will receive a message from the APM if you try to build the Tenant database and it already exists. The Tenant Number database contains a list of extensions and associated tenant numbers used by the PBX. A tenant number can be associated with an individual numeric extension or a range of numeric extensions. A given tenant number can have more than one record if all of the extensions associated with it are not consecutive. Tenant numbers can also be associated with individual extensions that contain non- numeric characters such as ‘*’ or ‘#’. If all extensions have the same tenant number, then this database is not required and the tenant number provided by the OAI configuration may be used by default. Each tenant number database record contains the following fields: First Extension - The first extension in the range of extensions. Last Extension - The last extension in the range of extensions. Te n a n t N u m b e r - This field contains the associated tenant number. The Tenant Number master database fields is named “tenant_m” and contains the following fields. Table 4-5 Tenant Master Database Fields The Tenant Number application database is named “tenants” and contains the following fields. Table 4-6 Tenant Number Application Database Fields Field Description Type SizeMinimum Va l u eMaximum Va l u e First Extension ASCII 10 Last Extension ASCII 10 Tenant Number Numeric 3 1 255 Field Description Data Type First Extension ASCII Last Extension ASCII Tenant Number Short Integer
Page 72NDA-30080 Revision 1.0 Emergency Conference Sentry Installation Guide Building DatabaseThe Building database is shared with other Sentry applications, so you might not have to build it for Emergency Conference. You will receive a message from the APM if you try to create the Building database and it already exists. The Building database contains a list of extensions and the location of each extension. A building location can be associated with an individual numeric extension or a range of numeric extensions. A given building can have more than one record if all of the extensions located in it are not consecutive. Each building database record contains the following fields: First Phone - The first extension in the range of extensions. Last Phone - The last extension in the range of extensions. Building ID - An ASCII string containing the building location. The Building master database is named “blding_m” by default and contains the following fields. Table 4-7 Building Master Database Fields The Building application database is named “blding” by default and contains the following fields. Table 4-8 Building Application Database Fields Field Description Type SizeMinimum Va l u eMaximum Va l u e First Phone Numeric 5 0 99999 Last Phone Numeric 5 0 99999 Building ID ASCII 24 Field Description Data Type First Phone Long Integer Last Phone Long Integer Building ID ASCII
NDA-30080 Revision 1.0Page 73 Sentry Installation Guide Emergency Conference Contacts DatabaseEach conference may have an optional contacts database file containing a list of contacts that are called by the conference application when the conference is initiated. The contacts database must be created manually and can be given any name that you want, such as conf1. A separate file may be used by each conference, or files may be shared between conferences. Each database record contains the following fields: Extension: The extension number of the contact. Prime Line: If the contact extension is a secondary line on a D term, this field contains the Dterm’s prime line value. If the contact extension is the prime line, then this field contains the same value as the extension field. Control Station Flag: If this field is set to “Y” or “y”, then this contact is designated as a control station. All control stations must be answered and released before the conference is terminated. When all callers and answered contacts have released from the conference, all ringing contacts will continue to ring until all control stations have answered and released. Each Contacts master database must have a unique name. An example database named “confl_m” is provided. All contacts master databases must have the following fields. Table 4-9 Contacts Master Database Fields Each Contacts application database must have a unique name. An example database named “confl” is provided. All contacts application databases must have the following fields. Table 4-10 Contacts Application Database Fields Field Description Type SizeMinimum Va l u eMaximum Va l u e Extension Numeric 5 0 99999 Prime Line Numeric 5 0 99999 Control Station Flag ASCII 1 n Field Description Data Type Extension Long Integer Prime Line Long Integer Control Station Flag ASCII
Page 74NDA-30080 Revision 1.0 Emergency Conference Sentry Installation Guide Authorized Caller DatabaseEach conference may have an optional authorized caller database file containing a list of extensions that are authorized to initiate a conference. The contacts database must be created manually. A separate file may be used by each conference, or files may be shared between conferences. If the conference contacts are the only extensions allowed to initiate a conference, then the contact database may also be specified as the authorized caller database. Each database record contains the following fields: Extension: The extension number that is authorized to call this conference. Prime Line: If the contact extension is a secondary line on a D term, this field contains the Dterm’s prime line value. If the contact extension is the prime line, then this field contains the same value as the extension field. Control Station Flag: This field is not used by the authorized caller database. Each Authorized Caller master database must have a unique name. An example database named “caller1_m” is provided. All Authorized Caller Master databases must have the following fields. Table 4-11 Authorized Caller Master Database Fields Each Authorized Caller application database must have a unique name. An example database named “caller1” is provided. All Authorized Caller Databases must have the following fields. Table 4-12 Authorized Caller Application Database Fields Field Description Type SizeMinimum Va l u eMaximum Va l u e Extension Numeric 5 0 99999 Prime Line Numeric 5 0 99999 Control Station Flag ASCII 1 n Field Description Data Type Extension Long Integer Prime Line Long Integer Control Station Flag ASCII
NDA-30080 Revision 1.0Page 75 Sentry Installation Guide Executive Override Chapter 5 Executive Override This chapter describes the field entries to make during the installation and configuration of the Executive Override software. Overview Executive Override is a versatile OAI telephony application that allows callers to monitor and/or join a two-party conversation from a Dterm telephone. Executive Override contains special security features which limits who may use it and how it may be used, and history logging provides real time logging of events to file systems and/or serial devices such as printers. The following paragraphs briefly describe the various features of Executive Override. Executive OverrideThe Executive Override application supports the following features. Override Type Three types of override types are specified. Basic Immediately joins a user with a two party conversation. Automatic Allows a user to camp-on a busy destination extension for a configurable time interval. If the destination extension becomes idle before the time inter- val expires, then the user is connected to the destination; otherwise, the user is joined with the conversation. Monitor Allows the user to silently listen to a two party conversation. The user has the option of joining the conversation later by pressing the OAI function key again. Warning Tone Flag This flag specifies whether a warning tone is heard by all parties before a user joins a conversation. The warning tone flag is used by basic and automatic overrides only. Monitor overrides are always initiated with no warning tone, but all parties will hear a warning tone if a user joins the conversation. Join Method This flag specifies how a user is joined with a two party conversation. The following types are used: Three Way All parties are connected together in a three way conference. Two Way The user is connected with only one member of the two party conversation; the other party is disconnected.
Page 76NDA-30080 Revision 1.0 Executive Override Sentry Installation Guide Ta b l e 5 - 1 , “Executive Override Options,” on page 76 lists all the valid feature combinations supported by Executive Override. A unique combination of override options defines an override category (Basic Override with warning tone and three way conference, etc.). Table 5-1 Executive Override Options Override SecurityEach Executive Override category allows the following security options: Authorization Codes The user is normally required to enter an authorization code before an Executive Override can be performed. Authorization codes are unique numeric values (up to ten digits) which are assigned to individuals. Protected Stations Any telephone can be designated a protected station. Conversations which take place on a protected station can not be monitored or joined using Executive Override. Secure Stations Any telephone can be designated a secure station. When Executive Override is executed from a secure station, no authorization code is required. Installation and ConfigurationThe installation and configuration of Executive Override includes the following procedures: Software Installation Application Configuration Database Requirements Override Type Warning Tone Join Method Basic Yes Three Way Basic Yes Two Way Basic No Three Way Basic No Two Way Automatic Yes Three Way Automatic Yes Two Way Automatic No Three Way Automatic No Two Way Monitor Not Applicable Three Way Monitor Not Applicable Two Way
NDA-30080 Revision 1.0Page 77 Sentry Installation Guide Executive Override Additional ManualsIn addition to this guide, use instructions in the following manuals for this installation: Applications Manager (APM) Installation Manual - Contains step-by-step instructions for installing the software from the release media. Applications Manager (APM) Operations Manual - Explains how applications like Executive Override are configured in the APM environment and how the Executive Override databases are created, using the entries and values provided in this chapter.
Page 78NDA-30080 Revision 1.0 Executive Override Sentry Installation Guide Software Installation The Executive Override software must first be loaded from the release media. Remember to use the Applications Manager (APM) Installation Manual if you need further instructions for installing software using the APM. Note:You will be prompted for several values when you install the software. For more information about these and other parameters, refer to the next section, Config- uration on page 87. 1. To begin the Executive Override software installation, log in to the APM Platform Management Menu by typing apmadm at the UNIX login prompt, then press Enter. The login and password prompts are shown below. If your “apmadm” account requires a password, enter the appropriate password at the subsequent password prompt. The APM Administration main menu displays, as illustrated below: login: apmadm password: NEC America APM Administration Wed Jan 31, 1996 APM Platform Release Rel2.0 (Oct 09, 1995 ) Main Menu APM Debug Facilities Halt APM System File Archive Installation of Applications/Packages Removal of Packages Start-up APM System Logout UNIX Enter Option: [] APM Status: ACTIVE
NDA-30080 Revision 1.0Page 79 Sentry Installation Guide Executive Override 2. Type i and press Enter to select the Installation of Applications/Packages option. The Installation of Application/Packages screen displays. 3. At the “ Enter Package to be installed” prompt, type applications and press Enter. The “ Enter Release Media Device” prompt displays. Installation of Applications/Packages Available Packages are: applications asl mtl tcpip update x25 Enter Package to be installed: NEC America APM Administration Wed - Jan 31, 1996 NEC America APM Administration Wed Jan 31, 1996 Installation of Applications/Packages Available Packages are: applications asl mtl tcpip update x25 Enter Package to be installed: applications Release Media Devices are: (F)loppy Disk Device (C)artridge Tape Device Enter Release Media Device:
Page 80NDA-30080 Revision 1.0 Executive Override Sentry Installation Guide 4. Select the floppy disk device as the installation media by typing f and pressing Enter. The following screen displays: 5. Insert the Executive Override diskette into the floppy disk device, and press Enter to continue. The screen displays files in the application installation. Many files may scroll off the screen, until all of the files from the diskette have been processed. The “ Has all release media been loaded” prompt displays, as illustrated below: Installation Procedure Installing from /dev/fd0 Insert OAI Release Media #1 Enter to continue: Has all release media been loaded [y or n] ? x oai/app/override/install/overDb.cfg, 2183 bytes, 5 tape blocks x oai/app/override/install/listx, 673 bytes, 2 tape blocks x oai/app/override/install/Movr.cfg, 161 bytes, 1 tape blocks x oai/chksum_app, 688 bytes, 2 tape blocks x oai/app/override.ins, 8135 bytes, 16 tape blocks x oai/app/override/bin/override, 395053 bytes, 772 tape blocks