NEC Call Forward Control Installation And Operations Manual
Have a look at the manual NEC Call Forward Control Installation And Operations Manual 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-30030-003 Revision 3Page 21 Call Forward Control - Installation & Operations Manual INSTALLATION INTRODUCTION APPLICATION CONFIGURATION (CONT) STEP 3: USER-DEFINED PARAMETERS Make the entries below through the UserDefined command on the Configuration Entry screen: This completes the configuration of Call Forward Control in the APM. Now go to the Tenant Database Section to set up the Tenant Database. U-D # Entry Parameter Definition #1/dev/tty1aIdentifies the UAP port used in the communication with the NEAX2400 IMS. #2/dev/tty2a Identifies the UAP port used in communication with the voice mail system.
Page 22NDA-30030-003 Revision 3 INSTALLATION INTRODUCTION Call Forward Control - Installation & Operations Manual TENANT DATABASE The Tenant Database is an APM database that is used by the HFC application and other OAI applications. It provides a mechanism for retrieving the tenant number of an extension. Since the Tenant Database may be used by other OAI Applications installed under the APM, it is configured using the APM and can not be modified by the Call Forward Control Administrator program. TENANT DATABASE RECORDS During CFC installation, the files tenant_m.mdf and tenants.adf are copied to the /oai/db/cur directory. The tenant_m.mdf file specifies the master database fields and contains the following definitions: The tenants.adf file specifies the application database fields and contains the following definitions: The Tenant Number field contains the Tenant Number that is used by one or more extensions. Tenant Numbers are associated with extensions using the following methods: A Tenant Number may be associated with a set of extensions defined by the First and Last Extension fields. The First Extension field contains the smallest extension number in the set, and the Last Extension field contains the largest extension number in the set. A Tenant Number may be associated with a single extension by setting the First and Last Extension fields to the same extension value. A Tenant Number may be associated with a single extension that contains a non-numeric character such as ’*’ or ’#’. The First Extension field contains the extension value, and the Last Extension field is left blank.Field Description Type Size Minimum 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
NDA-30030-003 Revision 3Page 23 Call Forward Control - Installation & Operations Manual INSTALLATION INTRODUCTION TENANT DATABASE EXAMPLES The following examples display how the Tenant Database may be configured: Example 1 All extensions use Tenant Number 1. Example 2 Extensions 2000-2500 use Tenant Number 1. Extensions 1000-1500 use Tenant Number 2. Extensions 1900, 2900, and 3900 use Tenant Number 3. Extensions “#68” and “*69” use Tenant Number 4. All other Extensions use Tenant Number 5. TENANT DATABASE CONFIGURATION The Tenant Database is configured using the Database Administration utilities provided by the APM. The following steps are required: STEP 1: BUILD THE MASTER DATABASE From the APM System Administration menu, use the arrow keys to select the Database Administration command and press . The Database Administration menu is displayed. From the Database Administration menu, use the arrow keys to select the Build Master Database command and press . The Master File Selection menu is displayed. From the Master File Selection menu use the arrow keys to select the tenant_m database and press . The Database Entry menu is displayed.First Extension Last Extension Tenant Number 0 99999 1 First Extension Last Extension Tenant Number #68 4 *69 4 0 999 5 1000 1500 2 1501 1899 5 1900 1900 3 2000 2500 1 2501 2899 5 2900 2900 3 2901 3899 5 3900 3900 3 3901 99999 5
Page 24NDA-30030-003 Revision 3 INSTALLATION INTRODUCTION Call Forward Control - Installation & Operations Manual Use the Add, Delete, and Modify commands to change the database. Use the Quit command when all changes have been made, answering ’Y’ when prompted “Do you want to save changes? (Y,N)”. The Master File Selection menu is displayed. At the Master File Selection menu press to return to the Database Administration Menu. STEP 2: PROCESS THE APPLICATION DATABASE At the Database Administration Menu use the arrow keys to select the Process Application Database command and press . The Process Application Database menu is displayed. From the Process Application Database menu use the arrow keys to select the tenant_m database and press .The APM will process the database, and the message “Database process operation complete” will be displayed. Press to return to the Database Administration Menu. STEP 3: INSTALL THE APPLICATION DATABASE At the Database Administration Menu use the arrow keys to select the Install Application Database command and press . The Install Application Database menu is displayed. From the Install Application Database menu use the arrow keys to select the tenant_m database and press .The APM will install the database, and the message “Installing application database ’tenants’ will be displayed. After the database is installed, the Database Administration Menu is displayed. At the Database Administration Menu use the arrow keys to select the Quit command and press . The APM System Administration menu is displayed. This completes the configuration of the Tenant Database in the APM. Now go to the MAT Assignments Section to make the necessary assignments at the NEAX Maintenance Administration Terminal.
NDA-30030-003 Revision 3Page 25 Call Forward Control - Installation & Operations Manual INSTALLATION INTRODUCTION MAT ASSIGNMENTS This guide assumes that data settings that affect the operation of all OAI software on a system-wide basis have already been assigned on the NEAX Maintenance Administration Terminal (MAT). Such settings include, for instance, system index values and assignment of Interface I/O Port Data in the Interface Processor (IP). For more information about these system data settings and for instructions in making the following Call Forward Control settings, consult the OAI Module Installation Manual for the NEAX2400 IMS. AMNO Command (Assignment of Monitored Numbers): Whenever a call comes into a monitored number, CRC is informed and implements forwarding activity. Use this command to assign each number (forward busy, forward no answer, and forward all) to be monitored. TN:Tenant to which the monitored number is assigned. MNO:The actual extension number that is to be monitored. NMI:An unique and arbitrary number from 1 to 4000 assigned to the monitored number for internal use by the PBX. (Use LNMI to list indexes to determine which are available.) UCD:A flag specifying the course of action to be taken with any call that is dialed into the monitored number when CRC is not operative, using the following values: 0 =(No) Call is not redirected to a UCD group, and caller hears re-order tone. 1 =(Yes) Call is redirected to a UCD group, which must then be specified. AKYD Command (Assignment of Function Keys): Use this command to assign function keys on each D term that has previously been assigned through the ASDT command and is to be supported by CRC. (Note: In making these assignments, the D term type must be indicated as Dterm.) Station Number:Corresponds to one assigned through the ASDT Command. D term Type:Must be entered as Dterm. Function Keys:Forward – all calls, Forward – busy, Forward – no answer This completes the MAT assignments for Call Forward Control. Now go to the Initialization/Termination Section to initialize the CRC and HFC applications.
Page 26NDA-30030-003 Revision 3 INSTALLATION INTRODUCTION Call Forward Control - Installation & Operations Manual INITIALIZATION/TERMINATION INITIALIZATION The CRC and HFC applications must be initialized through the Non-CRT Application option on the APM Operations Menu according to instructions provided in the APM Operations Manual. If an on-site voice mail system exists and the MCI_Server has been configured and named in the CRC configuration under User-Defined Parameter #2, MCI_Server must also be initialized from the Non-CRT Application option. CRC can perform its functions with or without MCI_Server, but CRC cannot communicate with a voice mail system without it. Once the CRC, HFC, and optional MCI_Server applications are initialized, use an Alt F(#) key combination to switch to an unused screen, then enter the cfcadm at the system login prompt and press ENTER. The CFC Administrator Main Menu is displayed (refer to Chapter 3). TERMINATION Exit the CFC Administrator Main Menu either by selecting the Quit option or by pressing the ESC key. The cursor is positioned at the UNIX prompt. Then enter the Non-CRT Application option on the APM Operations Menu and terminate CRC and HFC. (Note: If MCI_Server has been initialized to enable CRC communication with a voice mail system, terminate it in the same manner.)
NDA-30030-003 Revision 3Page 27 Call Forward Control - Installation & Operations Manual ADMINISTRATOR MAIN MENU INTRODUCTION Chapter 3 ADMINISTRATOR MAIN MENU INTRODUCTION A brief discussion of how the CRC and HFC applications process calls will show how the Administrator Main Menu assignments fit together to equip CRC and HFC for the variety of rerouting tasks that it is capable of performing. Here are some examples: Example 2: Hard Forward The Engineering Department has a lunch hour from 12:00 noon to 1:00 p.m. Monday through Friday. During this time all calls received by members of this department will be handled by Pat the receptionist at extension 3470. HFC can automatically forward all engineering department telephones to Pat’s extension using the following settings: All Engineering Department extensions are assigned to Hard Forward Group 1 (Engineering Department). Hard Forward Group 1 uses to Hard Forward Pattern 3, which specifies the following forwarding schedule: Date and Time Destination Action Mon-Fri, 12:00 noon 3470 Set Mon–Fri, 1:00p.m. 3470 Cancel At 12:00 noon Monday through Friday HFC will forward all extensions in Hard Forward Group 1 (Engineering Department) to extension 3470. At 1:00 p.m. Monday through Friday HFC will cancel the forwarding on all extensions in Hard Forward Group 1 (Engineering Department). Example 1: Call Routing At 9:00 Monday morning, Susan, who works in the Engineering Department, forwards her extension (3465) to the CRC monitored number 3995 so that she can attend a meeting. At 9:25 her phone receives a call from another internal extension. CRC detects the incoming call that has been forwarded from Susan’s extension. In response CRC checks its database for information about how to reroute calls to the Engineering Department and finds the following information: Extension 3465 is assigned to Call Routing Group 1 (Engineering Department). Call Routing Group 1 uses Call Routing Pattern 3, which specifies the following routing schedule: Date and Time Internal Destinations External Destinations Mon–Fri, 6:00 p.m. to 8 a.m. 2308, 2307, 2303, 2305 3300, 3301 Daily, 12:00 noon to 1:00 p.m. 2304, 2305, 2301, 2302 3400, 3401 Mon–Fri, 8:00a.m. to 5:00 p.m. 2300, 2301, 2302, 2303 3500, 3501 Sat & Sun, all day long 2300, 2301, 2302, 2303 3600, 3601 CRC examines the pattern and determines that extensions 2300, 2301, 2302, and 2303 should be used at 9:25 a.m., Monday for internal calls. CRC first checks 2300 to see if it is busy or idle. If it is idle, CRC reroutes the incoming call the extension. If 2300 is busy, CRC checks the remaining extensions until the call is successfully connected to a destination. If a call from an external source is received by Susan’s phone, CRC will route the call to extensions 3500 or 3501.
Page 28NDA-30030-003 Revision 3 ADMINISTRATOR MAIN MENU INTRODUCTION Call Forward Control - Installation & Operations Manual ADMINISTRATOR MAIN MENU INTRODUCTION (CONT) The information which CRC and HFC use to manage the call forwarding processes described in previous examples is constructed through the CFC Administrator Main Menu options. Although it is not necessary to enter information through these Main Menu options in any particular sequence, the information must correspond from one option to another. Example 3: Call Routing and Hard Forward The Engineering Department has a lunch hour from 12:00 noon to 1:00 p.m. Monday through Friday. During this time all internal calls received by members of this department will be handled by receptionists at extensions 2304, 2305, 2301, and 2302. External calls will be handled by receptionists at extensions 3400 and 3401. CRC and HFC together can accomplish these tasks using the following settings: All Engineering Department extensions are assigned to Call Routing Group 1 (Engineering Department). Call Routing Group 1 uses Call Routing Pattern 3, which specifies the following routing schedule: Date and Time Internal Destinations External Destinations Mon–Fri, 6:00 p.m. to 8 a.m. 2308, 2307, 2303, 2305 3300, 3301 Daily, 12:00 noon to 1:00 p.m. 2304, 2305, 2301, 2302 3400, 3401 Mon–Fri, 8:00a.m. to 5:00 p.m. 2300, 2301, 2302, 2303 3500, 3501 Sat & Sun, all day long 2300, 2301, 2302, 2303 3600, 3601 All Engineering Department extensions are also assigned to Hard Forward Group 1 (Engineering Department). Hard Forward Group 1 uses to Hard Forward Pattern 3, which specifies the following forwarding schedule: Date and Time Destination Action Mon-Fri, 12:00 noon 3995 Set Mon–Fri, 1:00p.m. 3995 Cancel At 12:00 noon Monday through Friday HFC will forward all extensions in Hard Forward Group 1 (Engineering Department) to extension 3995, which is a CRC monitored number. When CRC detects an incoming call on the monitored number, it checks its database for information about how to reroute the call. CRC will examine the Call Routing pattern, determine that from 12:00 noon to 1:00 p.m. extensions 2304, 2305, 2301, and 2302 should be used for internal calls and extensions 3400 and 3401 should be used for external calls, and route the call to the appropriate destination. At 1:00 p.m. Monday through Friday HFC will cancel the forwarding on all extensions in Hard Forward Group 1 (Engineering Department).
NDA-30030-003 Revision 3Page 29 Call Forward Control - Installation & Operations Manual ADMINISTRATOR MAIN MENU INTRODUCTION STARTING THE CFC ADMINISTRATOR PROGRAM The CFC Administrator program is started as described below: Figure 3-1 CFC Administrator Main Menu Action Result At the UAP system console, press the Alt key and a function key (F1...F12) at the same time to select a login screenThe UNIX login prompt is displayed Ty p e cfcadm at the UNIX prompt and press EN- TER. If prompted for a password, then type the and press ENTER.The CFC Administrator Main Menu is displayed as shown in Figure 3-1. Once inside the CFC menus, selection of an option or a command line function is made simply by typ- ing the highlighted key letter. It is not necessary to press ENTER after making the selection. Also notice that the key letter is not always the first letter of the menu option or command. Refer to the following pages for information and instructions in the use of each option and com- mand line function. To exit the CFC Administrator Main Menu, type q to select the Quit menu option. The CFC Administrator Main Menu is cleared, and the cursor is positioned on the UNIX prompt. CFC AdministratorFri Apr 1 16:10 pm *** Main Menu *** E xtensions H ard Forward Control C all Routing Control T ime Parameters S pecial events V alidate and Install Q uit Arrow keys to move cursor, to select, to quit
Page 30NDA-30030-003 Revision 3 ADMINISTRATOR MAIN MENU INTRODUCTION Call Forward Control - Installation & Operations Manual MAIN MENU OPTIONS The CFC Administrator Main Menu contains the following options: Extensions - Phone extensions supported by CRC and HFC are assembled into Call Routing and Hard Forward groups according to common needs. That is, if the phones in the Human Resources department are to be routed to the Operator at 5:00 p.m., all of these phones can be assembled into a Call Routing group which will route calls received by any phone in the group to the Operator after 5:00 p.m. Extensions can also be added to and deleted from the extensions database, they can be viewed on the display, or a hard copy can be printed. Each extension has a Call Routing and Hard Forward group index number which specifies the groups to which the extension belongs. One or both index values may be left blank to disable Call Routing and/or Hard Forwarding for an extension. Hard Forward Control - The Hard Forward Control option is used manipulate Hard Forward Control data. This option displays a sub-menu that contains Groups and Patterns options. Hard Forward groups and patterns may be created, deleted, modified, displayed, and printed using selections from this sub-menu. Call Routing Control - The Call Routing Control option is used manipulate Call Routing Control data. This option displays a sub-menu that contains Monitored Numbers, Groups, Patterns, and Destinations options. Call Routing groups, patterns, and destinations may be created, deleted, modified, displayed, and printed using selections from this sub-menu. Call Routing monitored numbers may also be set from this sub-menu. Time Parameters - Each Start Time Index identifies a schedule, or time frame, that is defined in hour, minute, month, and day detail. A time frame can be illustrated as “Daily at midnight”, “The first Monday of every month at 8:00 a.m., or “Monday through Friday, from 8:00 a.m. to 5:00 p.m.”. It is by these schedules that different Call Routing and Hard Forward patterns can be instituted for the same group at difference times. For instance, all of the phones in Accounting can be forwarded to the operator at noon every day, Monday through Friday, and to the Accounting receptionist console on Monday morning from 9:00 to 10:00 a.m. Special Events - There will occasionally be times during which the scheduled Call Routing and Hard Forward settings will need to be altered to accommodate holidays, organizational events, etc. The Special Events option is used to instruct CRC and HFC in the pattern changes that are to be implemented for holidays or scheduled events.