GTE Omni Si Database Technical Practices Issue 1 Manual
Have a look at the manual GTE Omni Si Database Technical Practices Issue 1 Manual online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 3 GTE manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
TL-130500-1001H/HC (HOTEL/HEALTH19.0 The H/HC printer provides hard-copy records of the CARE) PRINTER H/HC services. Any combination of outputs from the message metering, room status, do not disturb, room restriction, message waiting, and wake-up features can be obtained on the H/HCprinter. Each of these six features can be selectively controlled to print whenever the feature is activated and/or deactivated (from any authorized control point), or whenever a print command is issued from a KEDU. The system can support up to two H/HC printers. This provides hard copy for related services and activities . Examples of the printer applications are: l Cleaning service operations where room status print-outs provide records of maid service activities (required, in progress, and complete). l Front desk where a print-out is required to advise when maid service is finished and a room is available. l Accounting department where a continuous audit record of all message metering is required.The checkout/billing area may only want this information on request (from a KEDU) for guest billing/receipt purposes. Typically, a narrow 40-column printer manufactured by Axiom (Figure 19.1) is used for the H/HC printer applications; however, a wide 80-column format can also be used. Data properties of either 110 or 1,200 baud, odd/even parity, one- or two-stop bits, and seven- or eight-bit words can be specified. This allows almost any printer to be used as long as it is 20 ma. SVR 5210 8187S-253
TL-130500-1001Figure 19.1 Axiom Printer Used with (or without) KEDU in Hotel/Health Care Applications H/HC Printer/System19.1 The printer interfaces with the system via the SIDML card, located in a PCMUS slot. Interfacel The card provides a 20ma transmit circuit to the H/HC printer. l A single simplex data pair from the card supports the printer. l The printer is slaved to the system. NOTE: For description of the SIDML card, see paragraph 3.6.17. Power for the H/HC printer typically comes from a local 115 VAC power outlet . S-254 8187SVR 5210
MAINTENANCE TERMINALMaintenanceTerminal/System InterfaceSVR 5210TL-130500-1001 20.0 The maintenance terminal records system traffic data and system faults and provides the means for performing data base changes and requesting maintenance procedures and diagnostics. The system uses a TTY printer or video display terminal as a maintenance terminal. The maintenance terminal can be equipped with a printer when a hard-copy print-out is required. 20.1 The maintenance terminal interfaces with the system via one port of the FB-20992 NSDC (Narrow Serial Device Controller) card, located in slot 6 of the Get Started File. NOTE: The NSDC card is described in paragraph 3.4.7 The NSDC card is a programmable serial device controller with two full-duplex ports, designated port 0 and port 1. Each NSDC port can be manually configured for a 20-ma, 12 volt, current loop or RS-232-C operation mode. Under software control, each NSDC port can be individually programmed for baud rate. The NSDC port is addressed via the CPU address bus and data is transferred between the maintenance terminal NSDC port and system CPU via the CPU data bus. If the maintenance terminal is a TTY, the associated port on the NSDC card is configured for 20-ma current loop operation. If the maintenance terminal is a printer or equivalent EIA (Electronic Industries Association) compatible device, the associated port on the NSDC card is configured for partial RS-232-C operation. Modems are available for remote TTY or terminal operation. Maintenance terminal power connections, cabling, and installation procedures are described in TL-130300-1001. The following characteristics are needed to interface a CRT or TTY to the system: * EIA RS-232-C communication e ASCII character set. 0 Full- or half-duplex operation @ Baud rate of 110, 300, or 1,200 0 Display format of 24 by 80 characters e Character mode transmission 8!87S-255
TL-130500-1001Terminal Types20.2 The user is required to identify the terminal(s) to be used and Mode offor the ports of the interface card. The terminal types are Operationentered into the data base via CPG or Recent Change. The terminal types are listed in Table 20.1. Table 20.6 Terminal Types 11/ 2 = XT300GTE XT300 i3= LS31Lear Siegler ADM31, ADM32 S-256 /4= TELE Televideo 900 Series , 15 = ASGN-1Customer define j-1 6= ASGN-2Customer defined-2 ‘7= TTYHard copy terminals or “DUMB” CRTs Other parameters defined in the data base tables that can be displayed or changed via Recent Change include the following: l Transmission rates * Security lock time-out 0 Input time-out . Echo l Printer equipped 8187SVR 5210
TL-130500-1001 MDR (MESSAGE21.0 The MDR feature in the system is implemented via DETAIL RECORDING) software and common system hardware. The software HARDWAREassociated with the MDR feature uses common or shared memory.MDR Printer/21.1 The MDR printer interfaces with the system via one port System Interface of the FB-20992 NSDC (Narrow Serial Device Controller) card located in slot 6 of the Get Started File. NOTE: The NSDC card is described in paragraph 3.4.7. The system can only support one NSDC card (two ports). The MDR output records can be transferred to external equipment through either serial port 0 or serial port 1. Manual switches on the NSDC card allow these two ports to be selected individually for RS-232-C mode or 20-ma current loop mode. Under software control, each port can be individually programmed for baud rate, character length, parity checking, synchronous or asynchronous operation, number of stop bits, and interrupt capability. l Port 0 - interfaces to a local or remotely located TTY or similar terminal which provides a hard copy of MDR records - controlling software output does not react to control signals from the TTY -MDR output is provided independently of the condition of the receiving TTY With the use of port 0, the system works on a real-time basis (i.e., the call records are printed as they become available). Header data is output whenever a system start occurs, when a change in date or time occurs, every 64/32 call records or upon command from the administrative facilities (64 call records for single-line output or 32 for double-line output). The call record is output whenever an assembled call record is available and is in single format. The data base programmable output rates are 110, 300, and 1200 baud. 0 Port 1 - typically configured for RS-232-C operation - interfaces to a minicomputer or remote polling device - MDR output format is the GTE-modified EBCDIC (Extended Binary Coded Decimal Interchange Code) shown in Table 21 .l.SVR 5210 8187S-257
TL-130500-1001 NSDC card port 1 output is programmed to transmit data at speeds fast enough to avoid loss of data under the heaviest traffic conditions. The baud rates are 110, 300 and 1200. The baud rate and other options are programmable in the office-dependent data base. When selecting the speed for the output device from MDR port 0 or MDR port 1, the amount of traffic being handled by the system must be considered. The MDR file is capable of buffering a fixed amount of call record blocks, after which the additional call information is completely lost. Therefore, the worst case peak traffic must be considered, along with work group and trunk group screen options. These factors will determine the probability of losing a call record block. The MDR is capable of buffering 12 call record bloc::s (132 calls). As each call record is output by the MDR, an additional call record block can be generated and the data saved for output. If, however, 72 call record blocks are already in use at the time another call record block is generated, the data in the block will. be lost for output to that port. The speed of the TTY or other output receiving device must therefore be chosen so that call record blocks are not lost. Cabling for the MDR is described in TL-130300-1001. Figure 21 .l shows a typical MDR configuration. NOTE: When a call block is lost, no indication of the loss is provided, nor is there any means to recover the data. S-258 8187SVR 5210
TL-130500-1001FB-20992-A NARROW SERIAL DEVICE CONTROLLER (NSDC) :. I PORT 0-------- I1 PORT 1 20 ma LOOP+ FGTE MODIFIED EBCDICCOMPUTER / OR <
TL-130500-1001 Table 21.1Fujitsu GTE-Modified EBCDIC DECIMALHEXADECIMAL CHARACTEREQUIVALENTiO 11 2 2 3 3 44 55 66I 88BLANK /llALPHA a/l 2 C1100identifying character/the number 12-1 (See Note 2) BETA 6/l 3 EI 15II=1111/ The number 15 (See Note 2)IBINARY EQUWALENTMDR USEThe number zero (See Note 1) The number one The number five The number six The number seven The number eight The number nine The number 10 (dialed digit zero) (See Note 1) A blank space/identifying character/ the number 11 (See Note 2) Identifying character/the number 13 (See Note 2)1 The number 44 (See Note 2) NOTES: 1. The hexadecimal zero is always used for the decimal zero. He-xadecimal A is used as zero in calling and called numbers. 2. Hexadecimals A, E, and F are always used for the decimals 10, 14, and 7 5, respectively. Hexadecimals B, C, and D may have three different uses; however, their meaning is fully defined by the position occupied in the record. 8187SW 5210
SW 5210TL-130500-1001 The MDR feature is an option that provides the means for recording call information pertaining to incoming trunk calls, outgoing trunk calls, and trunk-to-trunk calls. Hardware associated with the MDR feature provides the following: l Interface with the program and data base memory l Interface with the buffer memory l Interface the input/output to external equipment8l87S-261
TL-130500-1001S-262THIS PAGE IS INTENTIONALLY LEFT BLANK.8l87SW 5210