==================================================================== UA-Simulator Installation (Alarm Server Application) Version 3.0 (1998-02-02) ==================================================================== Overview: --------- This Alarm Server Application notifies a configurable amount of extensions about a specific alarm condition. This is done via a call to each subscriber. If the called subscriber answers, a special alarm-tone or text is connected, and the Extensions display shows the Alarm type (= callers name). If the called extension doesn't answer after expiration of a timeout, this state is stored in database and the next extension is selected. Similar actions are performed on busy subscribers. After the complete list of extension is walked through, processing starts at the beginning of the table, calling again all busy or not answering extensions from the previous pass. This is repeated till all extensions have answered. The Alarm Server can be started by dialling a specific extension number, or if an external alarm contact is closed. Stopping the Alarm Server can be done by closing another type of external contact. This functionality is realised, by using a EMTL coupler with dedicated firmware. This coupler acts as UA16 interface with 16 virtual MR2 subsets connected. All this 16 virtual MR2 (4034) subsets are processing a single table, which contains the extension numbers of the stations to be alarmed. Extensions can be splitted into 6 groups. Each group alarm is started by one of 6 contacts (E-wire input). For this special case the maximum number of extensions to be alarmed is 16. There is currently no STOP contact for the group alarm. The alarm is terminated after the timeout "TO-ANSW" and "TO-MSG". Values for 'Alarm-tone-source-timeslot', timeout 'wait-for-answer' (TO-ANSW)and timeout 'duration-of-alarm-tone' (TO-MSG) can be configured individually for each group. Group mode is selected by entering the command 'MODE GROUP'. Up to 6 external alarm contacts can be connected to the EMTL's E-wire inputs. The type of each contact can be configured in firmware (see .cfg file): external contacts can act as o Alarm server start contact o Alarm server stop contact o Single extension alarm contact o Group Alarm start contact The type of contact (make or break) can be determined by a harware jumper on the EMTL cpl board (X102 .. X602). The list of extensions to be alarmed (Alarm table) should be maintained using an on-board (EMTL) configuration utility (see APPENDIX C). This information is stored in a non-volatile memory. The tone or text which should be applied to the alarmed extension, has to be selected, using the cpls built-in configuration tool (TSOURCE command). The Source for this tone, may be any tone, permanently present at the A4400's Crystals Backplane. EMTL cpl and Tone Source cpl must reside in the same crystal !! Possible choices for tone sources are: o Tone Present on CPU, GPA, USCVG ... o Analogue tone Interface on CPU3 o Any tone connected to Z-Cpls a/b wires In this case, the associated Z-Terminal has to be configured as "Waiting Message" in the Managers "System" menue. A conversion table from Z-Terminals to PCM timeslot numbers is shown in APPENDIX f. The Tone Source configuration requires a LINK and TIMESLOT information. LINK number is equivalent to the CPL nbr of the tone source (0 .. 27), TIMESLOT number means the PCM input timeslot on this CPL's C1-Chip (0 .. 127). There is a fixed relationship between Terminal number and PCM timeslot for each A4400 Coupler. The table in APPENDIX F shows this for a Z24 - Coupler. The "default" Tone Source configuration uses 2 Timeslots on CPU to generate the cadenced alarm tone. In addition two Timeouts may be configured: TO-ANSW (in seconds) This timeout specifies the time, how long the alarm sever waits till the alarmed subscriber ANSWERS the call. TO-MSG (in seconds) This timeout specifies the time, how long the alarm tone is applied to the alarmed extension. Block diagram: ============= +-------------------------------------------------------+ __ | | / \ | A4400 +-----|| Ext. 0000 | | . | | . | | __ . | | / \ . | +-----|| Ext. 1999 | | | +------------------------------------------+ | | | UA16 (EMTL) coupler | | 2000 | | with special firmware | | alarmed +--+-+------------+-------------+-----------+-+---------+ Extensions | | | | | | | | | | +----+----+ +----+----+ |Alarm Ext| 16 Alarm Extensions |Alarm Ext| +-+-----+-+ +-+-----+-+ |4034 | |4034 | +-----+ +-----+ \_______________ virtual UA subsets _____________/ in cpl firmware STEP 1: A4400 Configuration: ---------------------------- Before this special UA coupler can be plugged in, the configuration has to be verified with a standard UA-Coupler and a UA subset (Type 4034) plus AddOn Module(s) (4081) SHELF: Board type = UA16 (UA32 should work also, but leads to Error messages on console) All 16 Terminals should be mounted: USERS: Set type = 4034 Language Id. = ENGLISH (2) STEP 2: Configuration of UA16 Coupler / Simulator binary (see included floppy-disc) ----------------------------------------------------------------------------------- Configuration is applied by 'merging' a configuration file into the couplers binary. This is done using the PC utility "uacfg" (under MSDOS): uacfg ATTENTION: "uacfg" Version 1.3 or above is required Example: "uacfg ua_dwn.bin binXX.txt sv.cfg" Parameters: ua_dwn.bin .... 'master' binary for UA16/Sim cpl binXX.txt .... modified (configured) binary ready for download XX .. depends on CPL-position (see below) sv.cfg ..... Configuration file (self explantory - see comments) Determines, which channels (=subsets) are mounted, and the type of application to be used by the specific channel. ATTENTION: Never use a wordprocessor (WinWord, WordPad, ...) to edit this .cfg file - Use a pure text editor instead, eg. (Edit, Q, Pfe, Notepad, ...). Chorus/MiX: Enable Downloading of UA16 (Simulator Version) ----------------------------------------------------- ----- Coupler firmware is stored on the A4400 CPU's hard disk in binary form. This binaries are "downloaded" into the couplers on request. According to the naming rules of downloadable binaries, eg. all UA couplers are loaded with a file neamed "binua". Because of the fact, that System CPU doesn't know of the existance of a special UA coupler, it has be forseen, that downloading of standard binaries to this coupler has to be disabled. There is a possibility to load a coupler at a fixed hardware position with a specific binary. This is done by including the coded hardware position in the binaries file name. This has to be done for the boot-binary (normally named "binstart8") as well. Details see below. To be shure, that UA16/Sim is not loaded with the default UA binary "binua" we have to 'hide' this two binaries (temporary): mv binua binua.old mv binemtl binemtl.old mv binstart8 binstart8.old NOTE: it may be necessary to modify the file access permissions to to this ! Now, we have to determine the Hardware slot (Crystal number & shelf position) to be used for this Coupler Files "binXX.txt" and "bootXX.txt" ,which are provided on the installation disk, have to be copied to the directory "/usr2/downbin" on the A4400's CPU's hard disk, where "XX" has to be renamed as shown below: XX = 1 + (Position * 2) + (( crystal_number * 30) * 2) ATTENTION: Use "BINARY" mode, if FTP tool or Kermit is used for uploading binaries !! Example: UA/Sim Coupler at position 5 in crystal 0 (= main crystal) XX = 1 + ( 5 * 2) + 0 = 11 copy resp. rename: binXX.txt -> bin11.txt bootXX.txt -> boot11.txt ATTENTION: Always use 2 digits for XX (eg: 01, 03, ... 19, 21 ..) ** Be shure, that bootXX.txt has the same file permissions as binstart8 ** ** Be shure, that binXX.txt has the same file permissions as binua ** otherwise the CPL may be flashed with a wrong binary !! If you receive an 'unprepared' Coupler, the boot program in flash-eprom has to be replaced by a modified one, otherwise go to STEP 4. STEP 3: Programming CPL's Flash Eprom: -------------------------------------- The boot loader file "ua_start.hex" (provided on the installation disk) has to be programmed manually into the flash eprom, using the "PHENIX" software utility (in EPROM) and the "PDI" Test Adaptor. NOTE: Be shure, not to load a standard "start.hex" file into flash eprom ! Coupler Jumper settings for flash programming using PHENIX software (shown at EMTL board): ------------------------------------------------------------------- Loading "ua_start.hex" using Phenix SW and PDI: o EMTL Board: o o-o o X2,X3 | o PDI Adaptor (old Version): X3 o 1 | o 2 o 3 X2 o 1 | o 2 o 3 PDI Adaptor (new Version, PDI2): See Appendix B (set jumpers for Flash programming) Terminal Emulator setup (eg: Windows Terminal): 7bit, even parity, 9600 Baud, Software Handshake (Xon/Xoff) Be shure to use the proper PDI cable All inputs are in UPPERCASE !! Plug in the coupler: * PHENIX 186 V1.3 (C) 1991 (V. DHS3) * Jumpers position enables the Phenix copy from EPROM to FLASH ! .. Y : start copy. .. N : cancel. N <---- Answer "N" > "CODE_FLASH_ERASE" > "CODE_FLASH_LOAD" -> upload your hex-file <---- Upload "ua_start.hex" using menue "TRANSFER" -> "SEND TEXT FILE" > <--- wait till the prompter re-appears !!. If upload has completed successfully, restore jumper positions, and boot/reset the CPL: Jumper-positions: o EMTL Board: o-o o-o o PDI Adaptor (old version): X3 o 1 | o 2 o 3 X2 o 1 o 2 | o 3 NOTE: PDI Adaptor (new Version, PDI2): See Appendix B (set jumpers for normal operation) Use "config 0" command on A4400 console, to see if downloading is started. If download has completed and the UA cpl is working successfully, make the stabdard UA binaries visible again (to be used by all other UA Couplers): STEP 4: Restoring old binaries for "standard" UA-CPL's: ------------------------------------------------------- after CPL has booted sucessfully: mv binua.old binua mv binemtl.old binemtl mv binstart8.old binstart8 NOTE: Mark this UA coupler with a special label, if not already done. APPENDIX A: Using PDI to see Debug information =============================================== It is possible to read out some debug information at the couplers PDI interface using a Terminal program on a PC. It may be a good idea to log this output to a file on the PC's Hard-disk. COMx Setup: 8bit, no parity, 9600 Baud, Software Handshake (Xon/Xoff) Commands: see the current state of an UA-terminal: ctxt examples: ctxt 0 (terminal 00) ctxt c (terminal 12) enable trace output: debug 3 enable UA-set display output: debug 2 disable all output: do this after debugging activities are finished !! debug 0 CONTENT OF THE INSTALLATION DISK: -------------------------------- ua_dwn.bin coupler binary, unconfigured binXX.txt coupler binary, configured bootXX.txt boot binary for download ua_start.hex boot program to be programmed into flash-eprom uacfg.exe configuration program (DOS) cfg.bat configuration BATCH file sv.cfg configuration file (flash) extensions.dat list of extensions to be alarmed (to upload) install.txt this file ------------------------------------------------------- Appendix B: Configuration of new PDI (PDI2) =========================================== +--------------------------------------------------------------+ | | | 3o | | | | | 2o X9 | | | | 1o | | | +---+ | |V24| X3 X4 | to | | o o-o o o-o | PC--<--+ | 1 2 3 1 2 3 | | | | | |AUX | +---+ 1o | | | | +---+ 2o X5 | |V24| 3 2 1 | to | | X7 o-o o 3o | PC--<--+ | | | | +---------------------+ X6 o-o o 1o | | |PDI | | 3 2 1 | | +---+ | CPL Connector | 2o X11 | | | 40 pin | | | +---------------------+ 3o | +--------------------------------------------------------------+ | X4 | -------------------+-----+ Flash Programming | 1-2 | Normal Operation | 2-3 | APPENDIX C: Configuration Utility ==================================== Configuration data is stored in the non - volatile RAM on the PDI2 card. This RAM is backed-up by a "Gold Capacitor" with a value of 1 Farad. Configuration can be done via a simple terminal program, using the second UART on PDI2 (AUX - Port / 9600 Bd, no par, 8bits, Xon-Xoff) This tool provides several functions: Commands for NORMAL and CONTINOUS mode: INS Insert extension into alarm table DEL delete extension from alarm table RM delete index from alarm table LIST list alarm table CLEAR clear alarm table INIT put all extensions in idle state STAT print alarm statistics START Start alarm STOP Stop alarm TO-ANSW [] Set answer timeout TO-MSG [] Set message timeout VER Show Version info MODE [NORMAL|CONTINOUS|GROUP] Set alarm mode TSOURCE [ ] Set alarm tone source TSOURCE default Set alarm tone source to default slot Commands for GROUP mode: INS Insert extension into alarm table DEL delete extension from alarm table RM delete index from alarm table LIST list alarm table CLEAR clear alarm table INIT put all extensions in idle state STAT print alarm statistics START Start alarm STOP Stop alarm TO-ANSW [] Set answer timeout TO-MSG [] Set message timeout VER Show Version info MODE [NORMAL|CONTINOUS|GROUP] Set alarm mode TSOURCE [ ] Set alarm tone source TSOURCE default Set alarm tone source to default slot If a lot of extensions have to be inserted in table ("INS" command), this commands can be written to a text file which is uploaded to the EMTL cpl. You have to use a communication program, which allows to set up a character send-delay, eg. Hyperterminal or ProComm-Plus. send-delay per character -> 15 ms send-delay per line -> 150 ms Hyperterminal setup (Win95/NT4.0): ---------------------------------- File Properties Settings . ASCII-Setup . . Line delay = 150 ms . Character delay = 15 ms . Connect To Configure Baud = 9600 Databits = 8 Parity = None Stopbits = 1 Flow Control = Xon/Xoff To upload the configuration file, use Menuitem "Transfer -> Send Text File" Example of a Configuration File: ---------------------------------- mode normal clear ins 200 ins 201 tsource default to-msg 10 to-answ 15 init Some Hints: ----------- A good idea would be, to place the most important extensions first in the list. It's also possible to insert extensions multiple times in the list. Extensions may have up to 5 digits. Extension number "00000" isn't allowed. APPENDIX D: Hardware modifications on EMTL cpl (if necessary !!) ================================================================ PCM - Loopback -------------- To enable connection of tones by the calling extensions, we need loopbacks on PCM0 & PCM1 outputs of the Crystal-1 chip. Altough this should be already done on your cpl (by Dept. AOH), here is described what to do, if you receive a brand new cpl from the factory or stock: Connect pin33 to pin34 and pin35 to pin36 +---------------+ /|33 1| | | \|34 | | | /|35 | | | \|36 | | | | | | | | | | | | | | | |Crystal1 chip | | | |128 pins | | | +---------------+ | | | | | |Metral | |Connector +-+-+to Backpanel | ------------------------------------------+ ** be careful not to make any other connections !! ** Polarity of E - wire: -------------------- Jumper X102 -> pos 2-3 (Interface 1) Jumper X107 -> pos 1-2 . . . Jumper X602 -> pos 2-3 (Interface 6) Jumper X607 -> pos 1-2 APPENDIX E: EMTL E & M wire connector ====================================== Wiring of external alarm contacts: Alarm contact (make) _|_ +-----o o------+ | | eXa eXb (X = 1 .. 6) A C --------------------------- 01 a1 b1 02 c1 d1 03 m1a m1b 04 e1a e1b START Alarm or GROUP 0 Start 05 fv_isol1 --------------------------- 06 a2 b2 07 c2 d2 08 m2a m2b 09 e2a e2b STOP Alarm or GROUP 1 Start 10 fv_isol2 --------------------------- 11 a3 b3 12 c3 d3 13 m3a m3b 14 e3a e3b GROUP 2 Start 15 fv_isol3 --------------------------- 16 a4 b4 17 c4 d4 18 m4a m4b 19 e4a e4b GROUP 3 Start 20 fv_isol4 --------------------------- 21 a5 b5 22 c5 d5 23 m5a m5b 24 e5a e5b GROUP 4 Start 25 fv_isol5 --------------------------- 26 a6 b6 27 c6 d6 28 m6a m6b 29 e6a e6b GROUP 5 Start 30 fv_isol6 --------------------------- APPENDIX F: Z24 Cpl to Timeslot assignment chart ================================================ Z24-terminal PCM-Timeslot ---------------------------- 0 120 1 8 2 24 3 40 4 56 5 72 6 88 7 104 8 121 9 9 10 25 11 41 12 57 13 73 14 89 15 105 16 122 17 10 18 26 19 42 20 58 21 74 22 90 23 106 --------------------------------------------------------- Date of creation: 1998-02-02 Author: M. Lemberger (ex AOHE) Tel: 29121 - ???? email: Manfred.Lemberger@aut.alcatel.at