acom system maintenance 025-9619.pdf

Acom System Maintenance

025-9619A

Software License

The Zetron software described in this manual is subject to the terms and conditions of Zetron’s Software License Agreement, a copy of which is contained on the product distribution media or otherwise provided or presented to buyer. Installation and/or use of the Zetron software constitutes acceptance of Zetron’s Software License Agreement.

Limited Warranty

Buyer assumes responsibility for the selection of the Products and Services to achieve buyer's or its customer’s intended results and for the results obtained from the Products and Services. If buyer has provided Zetron with any requirements, specifications or drawings, or if Zetron provides buyer with such materials, such materials are provided solely for buyer’s convenience and shall not be binding on Zetron unless agreed contractually by Zetron. UNLESS AGREED CONTRACTUALLY BY ZETRON, ZETRON DOES NOT WARRANT THAT THE PRODUCTS OR SERVICES WILL MEET BUYER'S OR ITS CUSTOMER’S REQUIREMENTS OR SPECIFICATIONS OR THAT OPERATION OF THE PRODUCTS WILL BE UNINTERRUPTED OR ERROR FREE. SUBJECT TO THE LIMITATIONS SET FORTH BELOW, Zetron warrants that all Zetron Products and Services will be free from material defects in material and workmanship for one year from date of shipment or performance of the Services (except where indicated otherwise in the Zetron Price Book). For buyer’s convenience, Zetron may purchase and supply additional items manufactured by others. In these cases, although Zetron’s warranty does not apply, buyer shall be the beneficiary of any applicable third party manufacturer’s warranties, subject to the limitations therein. Zetron's warranty covers parts and Zetron factory labor. Buyer must provide written notice to Zetron within the warranty period of any defect. If the defect is not the result of improper or excessive use, or improper service, maintenance or installation, and if the Zetron Products or Zetron Accessories have not been otherwise damaged or modified after shipment, AS ZETRON'S SOLE AND EXCLUSIVE LIABILITY AND BUYER'S SOLE AND EXCLUSIVE REMEDY, Zetron shall either replace or repair the defective parts, replace the Zetron Products or Zetron Accessories, reperform the Services or refund the purchase price, at Zetron's option, after return of such items by buyer to Zetron. Shipment shall be paid for by the buyer. No credit shall be allowed for work performed by the buyer. Zetron Products or Zetron Accessories which are not defective shall be returned at buyer's expense, and testing and handling expense shall be borne by buyer. Out-of-warranty repairs will be invoiced at the then - current Zetron hourly rate plus the cost of needed components. THE FOREGOING WARRANTY AND THE THIRD PARTY MANUFACTURER'S WARRANTIES, IF ANY, ARE IN LIEU OF ANY AND ALL OTHER WARRANTIES EXPRESSED, IMPLIED OR ARISING UNDER LAW, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, NON-INFRINGEMENT AND FITNESS FOR A PARTICULAR PURPOSE.

Limitation of Liability

Zetron makes no representation with respect to the contents of this document and/or the contents, performance, and function of any accompanying software. Further, Zetron reserves the right to revise this document or the accompanying software and to make changes in it from time to time without obligation to notify any person or organization of such revisions or changes.

This document and any accompanying software are provided “As Is.” ZETRON SHALL NOT UNDER ANY CIRCUMSTANCES BE LIABLE TO BUYER OR ANY THIRD PARTY FOR ANY INCIDENTAL, SPECIAL, CONSEQUENTIAL OR INDIRECT LOSS OR DAMAGE ARISING OUT OF OR CONNECTED WITH BUYER’S PURCHASE OR USE OF ZETRON PRODUCTS, ZETRON ACCESSORIES OR ZETRON SERVICES. IN NO EVENT SHALL ZETRON’S LIABILITY (WHETHER FOR NEGLIGENCE OR OTHER TORT, IN CONTRACT OR OTHERWISE) EXCEED THE PRICE PAID TO ZETRON FOR THE ZETRON PRODUCTS, ZETRON ACCESSORIES OR ZETRON SERVICES.

IP networks by their nature are subject to a number of limitations, such as security, reliability, and performance. Anyone using non-dedicated IP networks, such as shared WANs or the Internet, to connect to any Zetron Products or systems should consider and is responsible for these limitations.

© Zetron, Inc. All rights reserved. This publication is protected by copyright; information in this document is subject to change without notice. Zetron and the Zetron logo are registered trademarks of Zetron, Inc. Other company names and product names may be the trademarks or registered trademarks of their respective owners. This publication may not be reproduced, translated, or altered, in whole or in part, without prior written consent from Zetron, Inc.

3

Compliance Statements

Compliance certificates for the hardware mentioned in this manual can be found in either the Acom Hardware Module manual that applies (part numbers 025-9598 to 025-9617) or in the “as built” documentation for the system.

Safety Summary

Warning! For your safety and the protection of the equipment, observe these precautions when installing or servicing Zetron equipment.

• Follow all warnings and instructions marked on the equipment or included in documentation.

• Only technically qualified service personnel are permitted to install or service the equipment.

• Be aware of and avoid contact with areas subject to high voltage or amperage. Because some components can store dangerous charges even after power is disconnected, always discharge components before touching.

• Never insert objects of any kind through openings in the equipment. Conductive foreign objects could produce a short circuit that could cause fire, electrical shock, or equipment damage.

• Remove rings, watches, and other metallic objects from your body before opening equipment. These could be electrical shock or burn hazards.

• Ensure that a proper electrostatic discharge device is used, to prevent damage to electronic components.

• Do not attempt internal service of equipment unless another person, capable of rendering aid and resuscitation, is present.

• Do not work near rotating fans unless absolutely necessary. Exercise caution to prevent fans from taking in foreign objects, including hair, clothing, and loose objects.

• Use care when moving equipment, especially rack-mounted modules, which could become unstable. Certain items may be heavy. Use proper care when lifting.

4 025-9619A

Change List for Rev A, 30 Sep 2011

• Initial Release

Contents

5

Contents

Getting Started................................................................................................13 About this document ............................................................................................................13

Audience ......................................................................................................................13 What is in this manual..................................................................................................13

Where to find further help ....................................................................................................14 Acom System Overview.......................................................................................................15

System Conceptual Diagrams .....................................................................................15 Console Hardware .......................................................................................................16 Common Control Equipment (CCE) ............................................................................18 DS3 Switches...............................................................................................................19 Intersite Bearers...........................................................................................................20 Time Slots ....................................................................................................................21 Capacity .......................................................................................................................22

About the Maintenance Computer.......................................................................................23

Preventive Maintenance .................................................................................25 Maintaining Backups of Configuration Files ........................................................................25

Full Backups.................................................................................................................25 IMS Backup..................................................................................................................25 ACS Backup.................................................................................................................26 Standby Backup...........................................................................................................26

Monitoring the System for Faults .........................................................................................26 Using IMS Terminal .....................................................................................................26 Viewing Fault Logs.......................................................................................................29 Observing Device LEDs...............................................................................................29 Keeping a Maintenance Log ........................................................................................29

Testing Backup or Redundant Elements .............................................................................30 Checking for Environmental Issues .....................................................................................30

Environmental Specifications.......................................................................................30

Optimizing System Levels .............................................................................31 Overview.............................................................................................................................. 31

Theory .......................................................................................................................... 31 Terms ........................................................................................................................... 32

Receive Audio Adjustments.................................................................................................33

Acom System

6 025-9619A

Alignment Basics ......................................................................................................... 33 Radio Base Station Alignment..................................................................................... 34 RIU Card Receive Alignment ...................................................................................... 34 EIE and TIE Card Level Alignment and Balance ........................................................ 35 Headset Microphone Alignment .................................................................................. 39 Console Desk Microphone Adjustment ....................................................................... 40

Transmit Audio Alignment ................................................................................................... 41 Tone Remote Control Adjustments ............................................................................. 41 Radio Base Station Alignment..................................................................................... 42 EMU and RIU Card Transmit Alignment ..................................................................... 43 Telephone Transmit Alignment ................................................................................... 44

Managing Fault Alarms.................................................................................. 45 Overview of the Alarm System............................................................................................ 45

Input Alarms ................................................................................................................ 45 Output Alarms.............................................................................................................. 46

IMS Fault Logs .................................................................................................................... 47 IMS Fault Log Tool ...................................................................................................... 48 Fault List ...................................................................................................................... 49 Alarm Types ................................................................................................................ 50

Clearing Faults .................................................................................................................... 51

Managing Console Databases ...................................................................... 53 Operator Databases ............................................................................................................ 53

Profile Management Utility .......................................................................................... 54 User Management System.......................................................................................... 58

Paging Configuration Database .......................................................................................... 58 New Configuration File Format.................................................................................... 58 Page Global................................................................................................................. 59 Page Format................................................................................................................ 59 Instant Pages............................................................................................................... 67 M25ES Option ............................................................................................................. 72

MDC 1200/GE Star Subscriber ID Database...................................................................... 73

Other Console Configuration ........................................................................ 77 Text Messaging ................................................................................................................... 77

Text Messaging Server Configuration ......................................................................... 77 Integrator Instant Recall Recorder ...................................................................................... 79

Hardware Interface ...................................................................................................... 79 Software Installation .................................................................................................... 85 Sound Card Selection.................................................................................................. 85 Record Control Configuration...................................................................................... 87 ACOM Configuration ................................................................................................... 88

Editing Predefined Dialing Information ........................................................ 93 Speed Dials ......................................................................................................................... 93

Dial Strings .................................................................................................................. 94 Lines ............................................................................................................................ 94 Caption ........................................................................................................................ 95

Contents

7

Contact Lists ........................................................................................................................ 95 Alpha Search Lists............................................................................................................... 95

Backup/Restoring Configurations and Upgrading Firmware......................99 Backing Up a Device Configuration.....................................................................................99

Equipment Required ....................................................................................................99 ADS/DCU Configuration Backup ...............................................................................100 ALS/MCU Configuration Backup ...............................................................................101

Restoring a Device Configuration......................................................................................102 ADS/DCU Configuration Restore...............................................................................102 ALS/MCU Configuration Restore...............................................................................103

Performing a Firmware Update..........................................................................................104 DCU Firmware Update...............................................................................................104 ALS Firmware Update................................................................................................106 ADS/MCU4 Firmware Update....................................................................................107

Distributing Updated Console Configuration Files.............................................................109 Installation..................................................................................................................110 The User Interface .....................................................................................................113 Using ZFD..................................................................................................................121

Radio Resources...........................................................................................125 Radio Lines - RIU Installation ............................................................................................126

Required Materials.....................................................................................................126 Standby Subrack Procedures ....................................................................................126 Main Subrack Procedures..........................................................................................128

Local PTT Radio Control ...................................................................................................129 Required Resources ..................................................................................................129 Connections and Programming .................................................................................130 Testing .......................................................................................................................131 Troubleshooting .........................................................................................................132

Local BCD Radio Control...................................................................................................132 Required Resources ..................................................................................................132 Theory ........................................................................................................................132 Programming..............................................................................................................134 Testing .......................................................................................................................136

Tone Remote Control ........................................................................................................136 Required Resources ..................................................................................................137 SMU Configuration.....................................................................................................137 Radio Tone Database Configuration .........................................................................138 Radio Line Programming ...........................................................................................140 Testing .......................................................................................................................141 Troubleshooting .........................................................................................................142

Muting Received Tone Remote Tones ..............................................................................142 Required Resources ..................................................................................................142 SMU Programming ....................................................................................................143 Radio Tone Database Programming .........................................................................145 Radio Line Programming ...........................................................................................146 Testing .......................................................................................................................147 Troubleshooting .........................................................................................................147

Configuring MDC-1200 Signaling ......................................................................................148 Required Resources ..................................................................................................148

Acom System

8 025-9619A

SMU Programming.................................................................................................... 148 MDC-1200 Dial Types Database Programming........................................................ 150 Radio Line Programming........................................................................................... 150 Editing the Console Screen File ................................................................................ 151 File Settings in AcomConsole.ini............................................................................... 153 Testing....................................................................................................................... 154 Troubleshooting......................................................................................................... 154

Configuring GE-Star Signaling .......................................................................................... 155 Required Resources.................................................................................................. 155 SMU Programming.................................................................................................... 156 GE-Star Definitions Programming ............................................................................. 157 Radio Line Programming........................................................................................... 158 File Settings in AcomConsole.ini............................................................................... 159 Call History Panel Setup............................................................................................ 159 GE-Star Line Button .................................................................................................. 161 Testing....................................................................................................................... 162 Troubleshooting......................................................................................................... 162

Configuring EnRoute Signaling ......................................................................................... 163 Required Resources.................................................................................................. 163 SMU Programming.................................................................................................... 163 Radio Line Programming........................................................................................... 165 Console Button Resources Setup ............................................................................. 167 Testing....................................................................................................................... 170 Troubleshooting......................................................................................................... 171

Configuring Two-tone Paging............................................................................................ 171 Required Resources.................................................................................................. 172 SMU Programming.................................................................................................... 172 Radio Line Programming........................................................................................... 174 Setting up a Two-tone Paging Database................................................................... 175 Setting up an Instant Page ........................................................................................ 175 Setting up a Page Stack............................................................................................ 176 Testing....................................................................................................................... 178 Troubleshooting......................................................................................................... 178

Configuring Analog Radio Function and Resource Buttons.............................................. 179 Channel Set Function Button .................................................................................... 179 Instant Monitor Function Button ................................................................................ 183 Instant TX Function Button........................................................................................ 186 Resource Audio Volume Function Button ................................................................. 188 Marker Tone Button................................................................................................... 192 Squelch Disable......................................................................................................... 196

Telephone Line Resources.......................................................................... 201 Enabling Caller ID for Incoming Calls ............................................................................... 202

Required Resources.................................................................................................. 202 SMU Programming.................................................................................................... 202 Line Resource Programming..................................................................................... 203 Editing the AcomConsole.ini File Settings................................................................. 204 Testing....................................................................................................................... 205 Troubleshooting......................................................................................................... 205

Setting up a Call History Panel ......................................................................................... 206 Required Resources.................................................................................................. 206

Contents

9

Console Screen Changes — Add Telephone Call History Panel ..............................206 Editing the AcomConsole.ini File Settings for Lines and Hunt Group .......................207 Testing .......................................................................................................................207 Troubleshooting .........................................................................................................208

Setting up an Answer Next Function Button......................................................................208 Required Resources ..................................................................................................208 Console Screen Changes — Add an Answer Next Function Button.........................208 Editing the AcomConsole.ini File Settings .................................................................209 Testing .......................................................................................................................209 Troubleshooting .........................................................................................................210

Setting up a Call Queue Function Button ..........................................................................210 Required Resources ..................................................................................................210 Console Screen Changes — Add a Call Queue Function Button .............................211 Editing the AcomConsole.ini File Settings — Determining Sort Order......................211 Testing .......................................................................................................................212 Troubleshooting .........................................................................................................212

Setting up a Console Telephone Line Transfer Function Button.......................................213 Required Resources ..................................................................................................213 Console Screen Changes — Add a Transfer Function Button ..................................213 Editing the AcomConsole.ini File Settings .................................................................214 Testing .......................................................................................................................214 Troubleshooting .........................................................................................................215

Setting up a Hold Function Button.....................................................................................215 Required Resources ..................................................................................................215 Console Screen Changes — Add a Hold Function Button ........................................216 Editing the AcomConsole.ini File Settings .................................................................216 Testing .......................................................................................................................218 Troubleshooting .........................................................................................................219

Setting up a Hunt Group Dialpad Function Button ............................................................219 Required Resources ..................................................................................................219 Console Screen Changes — Add a Speed Dial - Telephone Function Button .........220 Editing the AcomConsole.ini File Settings .................................................................221 Testing .......................................................................................................................222 Troubleshooting .........................................................................................................222

Setting up a Ring Enable/Disable Function Button............................................................223 Required Resources ..................................................................................................223 Console Screen Changes — Add a Ringer Disable - Function Button......................223 Testing .......................................................................................................................224 Troubleshooting .........................................................................................................225

Setting up a Selected Telephone Line Dialpad Function Button .......................................225 Required Resources ..................................................................................................225 Console Screen Changes — Add a Speed Dial - Telephone Function Button .........226 Testing .......................................................................................................................227 Troubleshooting .........................................................................................................228

Setting up a Speed Dial Function Button...........................................................................228 Required Resources ..................................................................................................228 Console Screen Changes — Add a Speed Dial Function Button..............................229 Testing .......................................................................................................................229 Troubleshooting .........................................................................................................230

Acom System

10 025-9619A

Auxiliary Devices.......................................................................................... 231 Foot Switch........................................................................................................................ 231

Digital I/O Programming ............................................................................................ 231

System Clocking .......................................................................................... 233 Device Real-time Clocks ................................................................................................... 233

Onboard Tab ............................................................................................................. 233 External Clocking Sources ................................................................................................ 234 Daylight Saving Time ........................................................................................................ 236 Intersite Considerations..................................................................................................... 237

Device and System Shutdown and Restart................................................ 241 Subrack Change-over ....................................................................................................... 241

Changeover Hardware .............................................................................................. 242 ADS Changeover Wiring Example ............................................................................ 247 How to Force a Change-over .................................................................................... 249

Shutting Down the System................................................................................................ 249 Restarting the System....................................................................................................... 250

Power-Up Sequence ................................................................................................. 251 Cloning an ALS ................................................................................................................. 252

Equipment ................................................................................................................. 252 Procedure .................................................................................................................. 252

Replacing Hardware Modules ........................................................................................... 253 Replacing Acom CCC Cards..................................................................................... 254 Replacing COV-T, COV-R, and COV-V Cards ......................................................... 255 Replacing DCU Cards ............................................................................................... 256 Replacing Acom Console Units................................................................................. 262 Replacing Acom Console Unit Daughter Cards ........................................................ 265 Replacing EIE, TIE, RIU, or EMU Cards ................................................................... 266 Replacing Jackbox 950-0474 .................................................................................... 267 Replacing MCU Cards in an ALS .............................................................................. 268 Replacing MCU Cards in an ADS ............................................................................. 272 Replacing MSU Cards............................................................................................... 275 Replacing RVA Cards................................................................................................ 277 Replacing SMU Cards............................................................................................... 278 Replacing Telephone Radio Handset Interfaces (TRHI)........................................... 280 Replacing UIO Cards................................................................................................. 281

Troubleshooting........................................................................................... 283 General.............................................................................................................................. 283 Specific .............................................................................................................................. 284

Audio Problems ......................................................................................................... 284 Console Problems ..................................................................................................... 286 Other Problems ......................................................................................................... 288

Recommended Actions ..................................................................................................... 288

Contents

11

Glossary ........................................................................................................307

Appendix A: Alarms......................................................................................319 IMS Fault Logs...................................................................................................................319

Fault Log Input Alarms...............................................................................................319 Fault Log Output Alarms............................................................................................324

General Alarms..................................................................................................................325 ADS Alarms .......................................................................................................................327

Input Alarm Description..............................................................................................327 Input Alarm Handling .................................................................................................346 Alarm Outputs ............................................................................................................346

ALS Alarms........................................................................................................................348 Input Alarm Handling .................................................................................................362 Alarm Output Defaults................................................................................................364

Acom Console Unit (ACU) Alarms.....................................................................................366 Supervisor Alarms in IMS ..................................................................................................373 Acom Console Alarms (ACU) in IMS.................................................................................374

Appendix B: System Failure Worksheet .....................................................379 Purpose..............................................................................................................................379 DCU LEDs .........................................................................................................................380 MCU3/4 LEDs (in ALS)......................................................................................................382 MCU4 LEDs (in ADS) ........................................................................................................384 MSU LEDs .........................................................................................................................386 Acom Console Unit (ACU) LEDs .......................................................................................388

Index ..............................................................................................................391

Acom System

12 025-9619A

About this document

13

Getting Started

About this document

This manual covers maintenance for the Acom system. The manual content is designed for those users who are responsible for maintaining the system hardware and software. This content includes overview descriptions, specifications, pinouts, configuration details, diagrams, and other important information.

Audience

The intended audience is that group of technicians who will be maintaining the system after its initial installation is complete and the system has been placed in regular service.

What is in this manual

This manual contains a brief overview of system architecture followed by sections covering maintenance procedures and procedures for adding components to the system after the initial installation and configuration is complete.

Getting Started

14 025-9619A

Where to find further help

The following list identifies all of the documents needed to fully describe, install, operate, and maintain this Acom system.

Title Part Number

Acom Software Installation and Configuration 025-9529

Acom Console Operation 025-9530

Network Management System 025-9575

Acom Console Design 025-9587

Acom EVO 025-9642

Acom Entity Manager 025-9653

Acom Console Unit 025-9598

Acom Line Subrack 025-9599

Acom DS3 Subrack 025-9600

Change-Over Subrack 025-9601

Main Control Unit (MCU) 025-9602

Main Supply Unit (MSU) 025-9603

Ring Generator Unit (RGU) 025-9604

Acom Radio Interface Unit (RIU) 025-9605

Recorded Voice Announcement Card (RVA) 025-9606

Signaling Management Unit (SMU) 025-9607

Telephone Interface Card (TIE) 025-9608

Universal Input/Output Card (UIO) 025-9609

Change-Over Control Card (CCC) 025-9610

Change-Over V-T Card (COV-T) 025-9611

Change-Over V-V and V-R Cards (COV-V and COV-R) 025-9612

DS3 Control Unit (DCU) 025-9613

Data Interface Unit (DIU1-2) 025-9614

Data Interface Unit (DIU1-4) 025-9615

Exchange Interface Unit (EIE) 025-9616

E&M Unit (EMU) 025-9617

Acom Ethernet Interface Unit (EIU) 025-9620

SMU FIPS 140-2 Compliant Daughter Board Option 025-9621

Acom System Overview

15


Note Acom specific terms and acronyms can be found in the Glossary

on page 307.

The Acom system is based on three major hardware groups and one primary software application, the Integrated Management System (IMS). The primary hardware components that make up the Acom system are the Console Hardware (hardware components that make up the operator position, possibly including an Audio Facilities Dock), the Acom Console Unit (ACU), and the Common Control Equipment (CCE), including the DS3 Switches.

System Conceptual Diagrams

Figure 1 is a conceptual diagram showing the overall hardware and the associated connections for an Acom system; only one cabinet is shown for simplicity.

Figure 1. Basic Hardware Arrangement

Getting Started

16 025-9619A

Console Hardware

The system console hardware is the hardware located at the operator position; mainly the computers and the Acom Console Unit (see Figure 2) or Audio Facilities Dock (AFD)(see Figure 3). The console hardware consists of a PC with monitor that has the necessary software applications to operate the system. The operator position typically includes speakers, headset, jackbox, and microphone equipment for voice capability.

The operator position computers are connected to each other by the use of a Local Area Network (LAN). The LAN is used to distribute management data, application information, and configuration files.

Figure 2. Example System Console (typical operator position)

Speaker 1

Foot Switch(optional)

IRR Box(optional)

Speaker 2

IPNetwork

Acom Console Unit

Headset

Jackbox 2Jackbox 1

Handset

DIGITAL OUTPUTS

DIGITAL INPUTS

O

A B C D 1 2 3 4 5 6

COM1 COM2 COM3 COM4

DUAL E1

PORT 1 PORT 2H/S 1

OPERATOR’S AUDIO

CTRLAUDIOH/S 2

DUAL 4W E & M

PORT 1 PORT 2VREF

DUAL 4W E & M

PORT 1 PORT 2VREF

Deskmic

DeskmicAmplifier

The Acom Console Unit interfaces the operator’s position to the DS3 Switch with its main function being to switch and process audio and data to and from the operator’s position. The Acom Console Unit utilizes the Dual E1 card to connect to the DS3 switch. Only a single E1 connection is required; however, utilizing both E1 connections is preferred to provide redundancy and resiliency.


17

The Acom Console Units are also connected to each other, forming E1 loops in some cases that ensure that no cabling or CCE failure will isolate an operator position. The Acom Console Unit can utilize an RS232 or USB connection to the computer at the console position.

Figure 3: Example System Console (using an AFD)

The following list identifies the circuits used between the different components of the system console hardware:

• Operator Positions IP Network

• Acom Console Unit (ACU) E1 loops

• Console position computer and ACU RS-232 or USB

• Audio Facilities Dock (AFD) IP Network

• Console computer to AFD USB

• IMS Maintenance Terminal IP Network or E1

Getting Started

18 025-9619A

Console Hardware Requirements

The recommended minimum hardware and software requirements for the System Console PC are as follows:

• Intel Duel Core or equivalent x86-class CPU, 1.7 GHz 32-bit and 64-bit OS supported

• 4 GB of RAM

• 40 GB (or larger) hard drive

• CD-ROM/DVD drive required for installation

• 2MB (or more) video card 24-bit color depth (16 million colors) 1280 x 1024 resolution(minimum resolution required) 1680 x 1050 resolution (widescreen)

• Keyboard and two-button mouse

• 1 x RS-232 serial port (or more)

• USB ports (2.0 or later)

• LAN card, 10/100 MB

• Flat panel or CRT monitor:

• 19 inch minimum

• 1280 x 1024 minimum resolution

• Touch screen optional

• Microsoft .NET Framework 1.1 (included on installation media) Microsoft .NET Framework 3.5 SP1 (included on installation media)

Note The operating systems supported are Windows 7 Professional

and Windows XP Professional SP3.

Electrical Requirements

• The power for the system console is 110 or 220 VAC. A selection switch is located on the back of the PC.

Connectors and pin-outs

• DB9 to RJ45 cable to Acom Console Unit. (P/N 709-7615)

• RJ-45 connector for LAN

Common Control Equipment (CCE)

The CCE includes the 19-inch, 6-unit equipment racks that contain the Acom Line Subracks (ALS), Acom Digital Switches (ADS), and their associated circuit cards. The


19

CCE is networked to operator positions, providing switching for voice and data communication and dispatch console functions.

Each subrack can hold up to 13 Acom cards. The Acom Line Subracks contain all of the required interfacing to line services. The equipment rack also contains rate converters, modems, power supplies, plus all of the necessary cabling, including the DS3 backbone.

The Acom system provides the necessary signaling functions to properly interface to the external interfaces. The CCE also provides interfaces to the operator console positions using DS3 Switches and an E1 link. See Figure 1.

The Acom system supports the distribution of console configuration files using a Local Area Network (LAN). A maintenance computer running the Integrated Maintenance Software (IMS) provides the system with configuration and diagnostic reporting tools.

DS3 Switches

The Acom system employs a DS3 bus-based architecture with distributed switching nodes (see Figure 4).

Current Acom systems use a DS3 backbone supported by DS3 switching equipment consisting of multiple ADS units (Acom DS3 Subracks) connected to Line and Console interfacing equipment (ALS and ACU respectively). Each ADS consists of DS3 (DCU) and E1 (MCU) interfacing equipment. On systems that use AFDs, the ADS racks will contain EIU cards.

Figure 4. Basic System Hardware Components

Getting Started

20 025-9619A

The Acom Console Unit (ACU) and the Acom Line Subrack (ALS) interconnect to the DS3 Switches using time slots on a digital E1 link. Time slots within the E1 protocol are assigned for both voice-frequency (VF) and data information. Each Acom DS3 Subrack (ADS) supports up to 6 E1 links, depending upon the number of MCU cards installed inside the subrack.

The DS3 ring is made up of 21 E1 buses, of which 1 bus is reserved for system messaging. Of the remaining 20 buses, time slot 0 is reserved for E1 framing, leaving 20 x 31 = 620, 64Kbps time slots available for audio switching.

The DS3 consists of a dual DS3 bus that is “self-healing” under failure conditions. Failure in the equipment or in a section of the ring itself will cause the adjacent DS3 equipment within the ring to loop back the buses, maintaining functionality. The DS3 switching equipment and associated line and channel interfacing equipment can be fully duplicated with “hot-standby” change over capability. This approach allows the Acom system to employ multiple interfaces per card, while ensuring no single point of failure.

Intersite Bearers

An intersite bearer (ISB) is a means of sharing resources among two or more sites that are connected within the same Acom system but may be miles apart. Using ISB links, resources at one site can be used by console operators at any connected site. A console operator at Site A can answer a call being received at Site B and can transmit over a line that is physically located at Site B. Console operators at remote sites can be included in conferences, patches, and intercoms just as if they were local. A typical usage is transmitting from Site A to a radio that is out of range of Site A but within range of Site B.

No difference should be noticed between local and remote lines, except possibly a slightly slower response time on lines that actually reside at another site. Line and console numbers are unique among all sites to prevent resource collisions.

Optionally, ISBs can also carry digital I/O for voting monitor and control of remote radio lines. When this option is enabled, some digital I/O can be configured to pass over ISBs with other digital I/O remaining local.

ISB connections are implemented between ADSs of separate Acom sites, by way of E1 or T1 connections on the MCU4 cards. Every ISB has an Incoming and an Outgoing side. That is, one MCU4 port must be configured as an Incoming bearer, and the mating MCU4 port on the other site must be configured as an Outgoing bearer. Each ADS can support up to six ISBs, and there can be up to 16 ISB groups in a network. Extended bearers are used on a point-to-point basis to complement the Main bearer.

Each ISB port is monitored for stability. If a certain number of destabilizing events should occur within a certain period, the port would be temporarily disabled. If port is configured for redundancy, this would cause a changeover to a Backup ISB link. The port


21

would remain unavailable until a certain number of stabilizing events occurred within a certain period. The port would then be enabled again, and the Main bearer will be in standby. The event types, time parameters, and redundancy are specified by way of IMS ADS.

In addition to IMS ADS, some ISB setup may need to be done in IMS ALS and/or IMS ACU, as well as in Acom Console Designer. For more information on ISBs, and for configuration procedures, see To set up intersite bearers (ISBs) in Acom Software Installation and Configuration.

Time Slots

A time slot can be thought of simply as a data transmission unit on the E1 link. (For a more detailed definition, see time slot and frame in the glossary.)

Backbone Time Slots for Local Resources

Each uniquely identifiable resource (radio lines, phone lines, ringdown lines, intercom lines, and utility audio devices) requires a backbone time slot for communication between the console and the CCE. Each console also requires a backbone time slot, and each system tone generator requires a backbone time slot. Consoles automatically request a backbone timeslot as soon as the operator is online (logged into ACS software).

Console screens can be designed to have a Backbone Status indicator that monitors the supply of backbone time slots. If the indicator should turn from green (which indicates <90% of the backbone time slots are in use) to yellow (which indicates that 90-99% are in use), the console operator would be expected to review the resources in use by that console and determine whether any can be released. If the indicator should turn to red (which indicates that 100% are in use), resource selection is possible, but the audio is not available until another active resource is released.

Phone/Radio line resources can be allocated backbone time slots either permanently or dynamically:

• Permanent allocation — The time slot will be allocated from the time slot pool when the line first starts up, guaranteeing that the line can always receive and send audio.

• Dynamic allocation — The time slot will be allocated from the time slot pool on an as-needed basis (for example, when an operator selects or monitors a line).

The rationale behind the dynamic allocation design is the same as with all trunking type designs, such as all public phone networks: all physical circuits are not typically in use at any given time. As long as the traffic model is understood, it is possible to have many more potential connections than there are physical circuits.

Getting Started

22 025-9619A

The Acom dynamic allocation model supports prioritization of the circuits to be switched in case the backbone time slots are ever full when an attempt to access a circuit is made. If an accurate traffic model is known and Acom is configured correctly, this situation should not occur. However, if it does, the following priorities are used (listed with highest priority first):

1. consoles

2. permanent phone lines

3. permanent radio lines

4. fixed connections

5. system tones

6. utility audio

7. dynamic phone lines

8. dynamic radio lines

Bearer Time Slots for Intersite Resources

Each audio resource usage (such as monitoring a line, selecting a line, or joining a conference) over an ISB link requires a bearer time slot.

Like backbone time slots, bearer time slots can be made available for resource use across an intersite bearer either dynamically (as needed) or permanently.

Console screens can be designed to have a Bearer Status indicator that monitors the supply of bearer time slots. If the indicator should turn from green (which indicates <90% of the bearer time slots are in use) to yellow (which indicates that 90-99% are in use), the console operator would be expected to review the resources in use by that console over ISB links and determine whether any can be released. If the indicator should turn to red (which indicates that 100% are in use), resource selection is possible, but the audio is not available until another active resource is released.

Capacity

Using dynamic allocation of backbone time slots, an Acom system can support up to 200 consoles and 2,200 lines. The actual maximum number of consoles and lines that can be active in the system at any given time depends on the extent to which dynamic allocation is used.

In a multi-site system employing intersite bearers, the maximum number of consoles and lines that can be active in the system at any given time further depend on how many consoles and lines are configured for replication, and the extent to which the bearer time slots are allocated dynamically.

About the Maintenance Computer

23

About the Maintenance Computer

This computer is sometimes also referred to as the IMS terminal. This computer is host to all of the Acom software applications except the console operational software.

• IMS Terminal — to monitor the system for faults, view alarms, see Using IMS Terminal on page 26

• Can be used to run other IMS modules as well, may be used to connect to a subrack or card to update firmware or configuration, see Backup/Restoring Configurations and Upgrading Firmware on page 99

• Paging Configuration — can be used to modify Instant Paging definitions, see Paging Configuration Database on page 58

• Profile Configuration — can be used to maintain the database of console operators, see Operator Databases on page 53

• Subscriber Configuration — can be used to maintain the database of radio operator IDs, see MDC 1200/GE Star Subscriber ID Database on page 73

• Acom Console Designer — to modify console screen forms, especially to modify line and function buttons, see the Acom Console Design manual, part number 025-9587

• ZFD — to connect to consoles and distribute updated console configuration files, see Distributing Updated Console Configuration Files on page 109

Getting Started

24 025-9619A

Maintaining Backups of Configuration Files

25

Preventive Maintenance

This chapter provides recommended preventative maintenance tips for an Acom system.

Maintaining Backups of Configuration Files

Creating current backups of the system’s configuration is critical to recovering from a failure quickly. Make backups whenever the configuration changes.

Note When using the Windows 7 OS, the program files are located

under the C:\Program Files (x86)\Zetron folder.

Full Backups

Make full backups of the computer on a regular basis. A full computer backup can be quickly restored, simplifying the recovery process. It may be possible to automate backups.

IMS Backup

When changing the configuration of an Acom device such as an Acom Console Unit, save the configuration to disk on the maintenance terminal in one of the “C:\WorkingConfig\” subfolders. Backup the “C:\WorkingConfig\” folder and all its subfolders on a regular basis to archive the configurations off the server.


26 025-9619A

ACS Backup

Backup the latest copy of your ACS configuration by copying the entire C:\WorkingConfig\AcomConsole\ folder to disk or other backup medium. This only needs be done for one position.

Note The \Logs sub-folder found in the \AcomConsole folder usually

contains a large number of files that do not need to be backed up in order to help restore operation to a console station.

Standby Backup

Backing up also means copying the system configuration between the main and standby subracks. Any changes you make to the system MAIN racks should be duplicated or cloned on the system STANDBY racks.

Monitoring the System for Faults

The most important preventative maintenance you can do for your Acom system is to watch for faults and alarms. Many faults can occur that do not cause a loss of service. You can identify these issues using the IMS fault logs, the IMS alarm displays, and the LEDs associated with the equipment.

Using IMS Terminal

IMS is the Acom software application used to manage the Acom infrastructure and network via a user-friendly graphical user interface (GUI). IMS is used by those responsible for configuring and maintaining the system and is generally installed on the Acom maintenance PC connected to the back room equipment.

For information on how to respond to alarms, see Managing Fault Alarms on page 45.

IMS ALS Module

The IMS ALS module provides a user interface to the ALS racks, which allows you to perform the following functions:

• Configure connections, parameter values, and modes of operation.

• Monitor link status, alarms, system faults, and signaling status.

• Check system diagnostics such as self-tests.


27

General Configuration

In an ALS, the Primary MCU functions as a master controller for the other cards and has a non-volatile memory that contains the configuration information. When the Primary MCU is reset, it uses the configuration data in the memory to set the connections, parameter values, and modes of operation for all cards in the subrack.

By using IMS ALS, the configuration of the subrack can be changed and if desired, the changes can be saved to the non-volatile memory so that the subrack uses that configuration after reset. If no configuration has been saved to the non-volatile memory, then the Primary MCU uses a default configuration that includes connections to line cards, which may or may not be fitted in the subrack.

The complete configuration description is located in Acom Software Configuration, P/N 025-9529. A brief overview is given in Table 1.

Table 1. Overview of Acom Configuration

Item Description

Configuration Data The Primary MCU is capable of storing two sets of configuration information. It can use one set only or can switch between the two sets upon an event occurring (e.g., alarm becoming active).

Connections Connection types and definitions must be set for all channels.

Data Formats The G.703 links can be set for double frame or CRC4 with CAS enabled or disabled. DIU card interfaces can be configured for synchronous or asynchronous operation at various data rates.

Alarming Include settings for slip time and alarm pulse operation. Alarms can be individually defined.

Synchronization Clock sources for the subrack may be listed in order of priority for use.

Signaling Signaling bits may be individually inverted. The handling of signaling for certain cards can be selected from a set of options.

Ringers Ringers can be configured for single or dual operation.

Gain Channel gain for audio circuits may be set.

Other Date, time, password, and rack address can be changed.

Monitoring

The Acom system is designed for two levels of monitoring. LEDs are provided on the cards for basic monitoring of the state of the link and channel operation. These are described in Observing Device LEDs on page 29.

The IMS ALS software provides a means for more detailed and informative monitoring and includes facilities for observing the status of links, alarms, system faults, and signaling states. A brief summary is shown in Table 2.


28 025-9619A

Table 2. Summary of Acom Monitoring

Item Description

Link Status The status of each G.703 link, including the status of alarms relating to the link may be observed.

Alarm Status The status of input alarms and of alarms defined by the user may be viewed and acknowledged.

Signaling Status Windows are provided for observing the status of signaling bits for G.703 links and for channels of individual cards.

Remote Management

Remote management can be accomplished with either a dial up method or VPN access. For dial up access, a dedicated phone line and modem will be required on the IMS computer. A software package like pcAnywhere can be used for the dial up access method.

Note pcAnywhere is a third-party product sold and supported by

Symantec Corporation.

For VPN, please consult your IT department on the method, protocol, and software to be used.

Diagnostics

Physical system diagnostics can be accomplished by viewing the LEDs on Acom cards.

The IMS software allows monitoring of past and active faults. It also has the ability to inform the user if cards in the rack are not working or installed properly with slot details. Self-tests and loop-back functions are available on some cards. A summary of the diagnostics information is given in Table 3.

Table 3. Summary of Acom Diagnostics

Item Description

System Faults Fault logs are generated for the system and may be viewed to determine the sequence and occurrence of faults.

Card Details The type, slot position and revision level of cards is displayed.

Loopback Loopback connections can be set for any type of card for diagnostic and operational checks.

Self Tests The MCU3 and other cards can perform self-tests to check the operation of major circuits.

SIM Mode An alarm simulation mode allows the MCU3 to simulate a number of alarms at a G.703 link.


29

Item Description

Alarm Indication Signal (AIS) Injection

AIS may be injected on any G.703 link.

Ping When connected in a network, the Ping command shows the addresses of other connected subracks.

Viewing Fault Logs

The fault log is a long-term record of all input alarms, output alarms, and events for the rack. It provides a history to help explain what has happened in the past.

See IMS Fault Logs on page 47 for more information on how to access the fault logs.

Observing Device LEDs

The LEDs on the front of the equipment may be the first thing that makes you aware of an issue. On a periodic basis, walk by the common control electronics and check for any red, yellow, or amber LEDs that might indicate a problem. The LEDs may direct you to check the alarms of the associated device. Refer to the applicable hardware module documentation for detailed information concerning the LEDs presented on a particular card.

Keeping a Maintenance Log

When performing maintenance, changes, upgrades, or troubleshooting the system, make a record of the date and time with a short description of the action taken. Note in the log when backups are made. Note intermittent symptoms and any Zetron trouble ticket numbers you received as part of a trouble call. The maintenance log should be kept in the equipment room accessible to you.

Table 4. Example Maintenance Log

Date

Time

Description

Corrective Action

Zetron EFO Ticket #

Jan 1 8:12a Urgent alarm on ALS1A – Fault logs show EMU card 5 removed

Talked with Joe at Zetron, replaced EMU card

123456

Jan 15 12:30p Scheduled backup Backed up IMS configurations to disk.

-


30 025-9619A

Testing Backup or Redundant Elements

If the Acom system was delivered with a redundant backup system (main/standby), the system should be switched to the backup system a few times a year to verify operation and configuration. It is advised to do this during a maintenance hour to avoid impacting the end user.

Checking for Environmental Issues

When the Acom system was installed, the site was checked for environmental issues such as dust, moisture, vibration, and temperature. If these conditions have changed, they may cause operating problems. Check the environmental specs for each piece of equipment on a periodic basis. Check the equipment room and console positions for moisture, high or low temperature, and dust on a periodic basis.

Other guidelines relating to the installation environment are as follows:

• The installation environment must be free of dust, moisture, and vapor. The subrack is designed for ease of access to cards and for cable entry. It is not protected against ingress of particles or liquids that may deposit on the surfaces of the circuit cards and on the metallic surfaces of connectors.

• The installation environment must be free of excessive vibration and shock.

Environmental Specifications

The following ratings apply to the conditions surrounding the equipment racks.

Table 5. Absolute Maximum Ratings

Parameter Conditions

Storage Temperature -10° to 70° C (14° to 158°F)

Operating Temperature 0° to 60° C (32° to 140°F)

Operating Humidity 45% RH (non-condensing) @ 45° C (113° F)

Note Absolute maximum rating for individual cards and associated

interfaces are described in the card sections.

Overview

31

Optimizing System Levels

Overview

The purpose of this chapter is to provide the system maintenance technician with an audio level alignment procedure for the Acom Console System.

Theory

The overall goal of the alignment procedure can be summed up in single word: balance. You will attempt to get the receive audio from radio sources, the incoming voice audio from telephone sources, and the microphone audio from local console positions to all three be as close as possible to the same level. Adjusting each of these sources as it comes into the Acom system will make each of these sources sound about the same. The use of AGC can assist in achieving this outcome.

The primary benefit from achieving this balance is that anytime you have a patch or conference situation all three parties to the call sound the same to all of the participants in the call. (In Fact, the console operator voice audio is usually set a little lower than the telephone and radio receive audio to compensate for the slightly broader frequency range of the local microphone audio.)

The technician should choose a nominal digital reference level that keeps the voice audio below the point where it is clipping at the peaks. (PCM audio will clip at +3.14 dB0.) At the same time, the level should not be so low that it is difficult to bring it back up to a decent level to drive connected circuits. The adjustment procedures described here should allow you to obtain reference levels of -10 dB0 for average voice audio and -6 dB0 for tones.


32 025-9619A

Terms

Brief descriptions of the following terms are provided here because understanding them is important to the procedures which follow.

Term Description

AGC This is the standard abbreviation for Automatic Gain Control. In the Acom system, AGC is implemented using DSP to normalize inbound audio.

Codec This is an abbreviation for the term COder/DECoder. Codec circuits are used to convert analog audio into digital signals and digital signals back into analog ones. Their digital interface is often PCM audio.

DSP This is an abbreviation for Digital Sound Processing. DSP circuits are used to process digital audio.

PCM This is an abbreviation for Pulse Code Modulation. PCM is an encoding technique that represents audio signals in 8-bit samples taken 8,000 times per second. This makes PCM a good match for covering a frequency response of 300 Hz to 3000 Hz. The digital audio carried on the Acom DS3 and E1 links is encoded in PCM; using D/A codecs or DSP.

dBm600 This is a power measurement that expresses power as a fraction of a reference signal. The reference signal is defined as 1 milliwatt into a 600Ω termination. (0 dBm) A negative dBm reading is less than the reference level and a positive dBm reading is greater than the 1-milliwatt reference.

dBm600 = log (measured power / 1 mW) x 10 Example: log (0.75mW / 1mW) x 10 = -2.87 dBm600

dB0 This is a power measurement used in this document to refer to a digital signal referenced at -3.14 dB below full scale PCM output (maximum digital level). The codecs in the Acom system produce a 0 dB0 PCM level in response to a 0 dBm600 analog input signal; assuming no gain is added by the interface card.

dB This term is used only to indicate the relative strength of two signals compared to each other. It cannot be used to indicate an absolute value. For example, a signal strength of -9 dBm600 is 6 dB lower in level than a signal of -3 dBm600. A difference of 3 dB indicates that the higher signal is twice as strong as the lower one.

Receive Audio Adjustments

33


Alignment Basics

There are several methods that can be employed in order to set the receive audio level in an Acom console system. They can be divided up based on the test equipment used.

• You can use an E1 test set to monitor the audio at the DS0 level (while it is still a digital signal on the E1 link)

• You can create an analog logger port for the circuit/console under test and use analog test equipment to measure the signal coming out of the logger port

• You can create a VU meter on the console screen and use it to measure the level of the select audio (this is once again a measurement of the audio level while in digital format on the E1 link)

This manual will use the VU meter method. While it is not as accurate as using an E1 test set, it is accurate enough for our purposes and has the added attraction of being both simple and readily available. The VU meters that can be programmed to be displayed on the console screen measure the digital PCM level on the E1 links to and from the Acom console.

You will begin the alignment process by adjusting the receive levels coming from the radios, telephone lines, and console microphones. Once all of the audio levels coming into the system have been set to approximately the same level, you can then adjust the output gains to the desired level.

The line card levels are adjusted by setting the fixed gain setting in the cards codec. (This includes the EMU, EIE, RIU, and OAM cards.) Once the codec levels are set to bring the range desired, the AGC can be enabled to normalize a wide range of audio signals.

The Acom system does not provide any method for adjusting the gain of audio on T1 or E1 links. If your system is using an ISDN telephone line or radio audio is being brought into the system over a T1 link, you should consider reducing your target PCM level to match the digital links.

When the AGC is enabled, it is normal for voice audio to read about 4 dB lower than a solid tone signal for the same Acom gain setting.

VU Meter Calibration

If the default console screen form file for your system does not provide a set of VU meters with the following characteristics, then you must use the Acom Console Designer software to create a form file that does have them in order to use the method described in this manual.


34 025-9619A

• Two VU meters are required. One is assigned to the Handset-Transmit audio and the other is assigned to the Handset-Receive. This allows you to both directions of the audio in primary E1 timeslot of the console.

• The percentage of meter range versus power levels measured should be set as follows for both meters.

40% VU meter = -10 dB0 70% VU meter = -6 dB0

Radio Base Station Alignment

Adjusting the radio base station audio:

1. Align the audio level out of the radio base stations to be approximately the same for all radios. You may use either of the two following methods.

• Inject a tone into the receiver at 65% deviation and adjust the line output from the receiver to drive the line at -6 dBm600.

• Alternatively, use a field radio to send a DTMF “5” and adjust the base station receiver line output to -6 dBm600.

2. Repeat this process with all of the radio base stations supplying receive audio to the console system. (The console can compensate for line losses and small differences between radios, but not gross differences.)

RIU Card Receive Alignment

For detailed information about working with the RIU and the SMU, refer to their respective manuals. These are:

• RIU 025-9605

• SMU 025-9607

Note The use of a power meter function in IMS for the RIU card

requires that a dynamic level meter be enabled in the SMU. If the system was shipped configured from Zetron this will already have been done. If you have replaced cards or unsure of the set up of the system, check that the SMU level meter is enabled and available to the RIU before starting the procedure.

To align RIU receive audio:

1. At one of the console positions, clear the line under test and make sure that it is not selected by any console position. It must remain this way during the level setting procedure.

2. At the IMS maintenance terminal, open the IMS ALS software, right-click on the icon for the RIU card under test, and choose Card Settings from the menu.


35

3. In the dialog that opens, locate the Setup button for Rx gain for the line under test and click it.

4. Adjust the Rx gain for the RIU card channel using one of the following methods:

• Method A (preferred) Generated a test tone on the radio channel at 60% FM deviation, full quieting. In the RIU dialog, adjust the receive gain for a PCM level of -7 dB0.

• Method B Use a field mobile to generate a DTMF “5” at 60% FM deviation. In the RIU dialog, set the Rx gain level to -7 dB0 PCM.

• Method C Speak over the radio channel in a normal voice and adjust the receive gain to obtain a -10 dB0 PCM level. This is often made easier by saying a long, steady vowel sound, for example “Threeeeeee”.

5. Use IMS ALS to enable the AGC for the line under test. When configured for 0 dB attenuation, the SMU AGC available in the ALS will drive the incoming audio level to -6 dB0 for tone (and -10 dB0 for voice).

Note You should set the AGC threshold low enough to pick up weak

transmissions and restore them to -6 dB0. Remember though that setting the threshold also determines the maximum gain used to recover weak signals and that the more gain used, the more that background noise in the signal is increased.

6. Set the AGC attack time to 10 ms and the decay to 500 ms.

7. The Bypass Gain can be used to attenuate the level of paging tones sent back to the console. (In the [Paging] section of the AcomConsole.ini file, set PlayTones=True.) A good starting point for setting this level is -12 dB.

8. Repeat these steps for all of the remaining radio lines.

EIE and TIE Card Level Alignment and Balance

The telephone line alignment procedure consists of two parts, the adjustment of the hybrid balance and the audio level adjustment.

Note The Acom equipment does not provide any level adjustments for

digital telephone lines (E1/T1). In addition, Digital telephone lines may require artificial sidetone from the console to sound natural.


36 025-9619A

Resources Needed

• IMS ALS and/or access to the system IMS terminal

• 709-7345-xxx Zetron straight-through cable - required if connecting the computer running IMS ALS directly to the ALS

• Acom Software Configuration manual (025-9529)

• Acom Exchange Interface Unit (EIE) manual (025-9616)

• Monitoring equipment - used to listen to and measure audio levels at the demarcation block for troubleshooting purposes

Telephone Hybrid Adjustment

With any transmission line, the objective is to achieve the most forward power transmission and the least reflected power. Doing this requires a good impedance match at all points in the line. An analog POTS line from a central office is a 600Ω copper pair. The central office end is terminated in either a 600Ω or a 900Ω load. The length of the line from the C.O. to the Acom equipment can also affect its impedance.

While simple hybrid circuits most often employ transformers to handle both impedance matching and the conversion from 2-wire to 4-wire audio, the Acom EIE card (part number 950-0522, V41 and later) uses a digital hybrid chip to adjust the impedance. The IMS ALS software allows you automatically test all possible settings of the hybrid balance and select the one with the best results.

Note It is assumed a phone line is already programmed in the system

and only requires the hybrid adjustment be performed. If a new phone line needs to be programmed from scratch, please contact technical support.

Tip This adjustment will require one person at the console and

another in the backroom at the maintenance computer.

Setting the hybrid balance:

1. At the IMS maintenance terminal, open the IMS ALS software and connect to the ALS rack, right-click on the icon for the EIE/TIE card under test, and select Gain from the menu. Set the Country as required and save any changes before closing the dialog.

2. Right-click on the EIE/TIE card under test again and select Learn Line Parameters.

3. At an Acom console position, select the telephone line under test and take it off hook to dial an outgoing call to a “quiet” number. Some Central Offices offer a number for this purpose. If one is not available, you could call a number where an assistant is stationed and then have the assistant mute the handset mic on that telephone once the call is answered.


37

Tip Alternatively, you could just take the line off hook and dial a

single digit to silence the dial tone. If you use this method, you must complete the next two steps promptly since in most telephone systems you will get only 5 to 10 seconds of silence before the reorder tone is generated.

4. Mute the console microphone in order to prevent its input from influencing the outcome of the test.

5. Back at the IMS terminal, in the Learn Line Parameters dialog, click the ellipse (…) on the Learn button (far right column) for the selected line to start the test. Wait for the test to end (approximately 5 seconds). The test will run a number of trials and determine which impedance setting returns the smallest echo. If the test is completed properly, the label on the Learn button for that line will change to Success. The software will automatically configure the card to use these impedance settings at the end of the test.

6. Hang up the line you just tested and then repeat the test on the remaining telephone lines.

Note After hybrid adjustments have been made, make sure to check

the line gain and make any necessary adjustments to compensate for the hybrid adjustment.

The condition of the C.O. equipment and the transmission lines can change over time. For this reason, it is a good maintenance policy to check the hybrid balance on the lines into your system every 6 to 12 months.

Receive Level Adjustment

The receive level of audio coming from the telephone should be balance to match the audio levels coming from the radio and the console position microphone. This would be the -10dB0 PCM level discussed before under radio level setting.


38 025-9619A

The audio arriving from the telephone company often arrives at -30 dBm to -10 dBm. The following procedure will use the dial tone as an indicator of the line loss and the required gain to bring the audio to the desired level.

Note The following procedure should be performed after the hybrid

balance has been set for the line in question. The ideal incoming voice level on a phone line connected to an Acom system is -20dBm.

Setting the telephone receive gain:

Note Disable the AGC function for the line under test. This can be

done from the Level tab of the IMS ALS Acom Definitions page. The AGC function should not be used with analog telephone lines.

1. At the IMS maintenance terminal, open the IMS ALS software, right-click on the icon for the EIE/TIE card under test. Select Gain Setting and set the gain for the line under test to 0 dB.

Tip Make sure the Impedance and Country are set correctly for

your region. If the hybrid adjustment has already been performed on a line, do not adjust the impedance setting.

2. From an Acom console position, select the line under test and place a call to an assistant at another location. Have the assistant press the DTMF “5” key for 3 to 5 seconds at a time while you adjust levels. From the IMS ALS terminal, adjust the EIE/TIE card Rx gain to obtain -6 dB0 (approximately 70% range of the on-screen VU meter).

3. After setting the tone gain in the pervious step, have the assistant speak into the telephone in a normal voice or make long, sustained vowel sounds (for example


39

“threeeee”). Verify that the voice audio level is approximately -10 dB0 (40% of range on the VU meter).

4. Click the Save button to save these settings.

5. Repeat this level adjustment procedure for the remaining telephone lines.

Testing

At this point, the phone line has been configured in this rack only. To test the phone line, verify that the rack that was programmed is the active rack (ALS) and make an outbound call to an outside line from the console. If the gain level sounds adequate on an outbound call, make an inbound call and check the voice level.

Once the phone line is confirmed to have adequate voice level, always perform an Update to Rack to permanently save your settings. If an Update to Rack is not performed, any programming settings configured will be lost if the rack is reset.

Note Repeat configuration steps for other ALS (Main or Standby

depending on which rack was currently configured to assure both Main and Standby ALS racks have the same configuration.).

Troubleshooting

• If audio level is not adequate, execute the hybrid adjustment again then adjust gain setting.

• Is the issue on a specific line or all lines? If a specific line has an issue, try swapping the problem phone line with a known good working phone line. Then perform the hybrid and gain setting adjustments. This will help isolate the issue to an external phone line or the EIE line.

Headset Microphone Alignment

The sensitivity of the handsets or headsets used at the console positions will determine the required gain for this alignment. The expected input level for voice audio from the headset/handset falls between 245 mVrms to 77 mVrms.

Experience indicates that setting the Rx gain for the handset/headset input to +5 dB and the AGC minimum threshold to -21 dB0 will allow a wide variety of headsets to be used.

To set the headset microphone gain:

1. At the IMS maintenance terminal, open the IMS ACU software and log on to the console position being adjusted. Right-click on the icon for the OAM module to which the headset/handset is connected. Set the gain for Channels 1 and 3 to 0 dB.

2. Disable the AGC for channels 1 and 3.


40 025-9619A

3. From the console position being adjusted, select a radio line.

4. Speak into the headset/handset microphone while observing the transmit VU meter on the console screen. Adjust the Rx gain for the OAM channel in use until the voice audio averages -10 dB0 (approx. 40% VU meter scale). Make this adjustment for both OAM channels 1 (HS1) and 3 (HS2).

5. At the IMS ACU terminal, turn AGC back on for both OAM channels 1 (HS1) and 3 (HS2). The threshold setting determines when the AGC starts and stops adjusting the gain. This also determines the maximum gain used by the AGC function. The threshold should be set above the noise floor, but low enough to allow for variations in equipment. The recommended starting point is -21 dB0.

6. Set the AGC attenuation to -7 db. This should make the mic audio sound similar to the audio coming from a radio channel or a telephone line. (Mic audio tends to have a broader range of frequency components than radio or telephone audio, and therefore can be attenuated a little more and still sound the same.)

7. Set the AGC attack time to 10 milliseconds and the decay time to 500 milliseconds.

8. Save the changes in the OAM settings and release the radio line.

Console Desk Microphone Adjustment

Desk microphones typically require more amplification than headset/handset microphones to produce a useable signal. Because of this, an external mic amplifier is used with the Acom system to boost the mic output approximately 70 dB. The desk microphone gain should be set so that the level coming into the system is -10 dB0 when the console operator is speaking and no background noise is picked up when he or she is silent.

To set the desk microphone gain:

1. At the IMS maintenance terminal, open the IMS ACU software and log on to the console position being adjusted. Right-click on the icon for the module to which the desk mic is connected. Set the gain for the desk mic channel to 1.6 dB.

2. Enable the Rx AGC for the desk mic channel.

3. Set the AGC minimum threshold to -6 dB0 (limiting AGC only).

4. Set the AGC attenuation to -6 dB (PCM level will be -6 dB0 tone).

5. Set the AGC attack time to 10 milliseconds and the decay time to 500 milliseconds.

6. Verify that when speaking into the desk microphone from approximately 1 foot away that the console position transmit VU meter registers 40% of full scale (-10 dB0).

Transmit Audio Alignment

41


The procedures in this section should not be performed unless the receive audio level adjustments have been completed and all of the audio input sources have been normalized to -10 dB0 for voice (-6 dB0 for tone).

Tone Remote Control Adjustments

The following figure shows the relationships between the typical tones used by Tone Remote Control (TRC) controllers.

120m

s

40m

s

Ta

lk

Tim

e

• High Level Guard Tone (HLGT) at +10 dBm600

• Function Tone (FT) at 0 dBm600

• Low Level Guard Tone (LLGT) at -20 dBm600

It may be required that you reduce these levels in order to pass the audio over a digital link (T1 line or microwave) on its way to the radio transmitter site. The maximum level that can be sent over a PCM link is +3.14 dB0. To achieve a +9 dBm High Level Guard Tone requires adding another 5.8 dB of gain to the single coming out of the link and attenuating your voice to compensate.

Because of these differences, you should consider creating two sets of TRC level settings; one for use with digital links and one for 4-wire leased lines. Use Radio Tone Database #1 with channels connected to the radio base station over leased lines (copper). Use Radio Tone Database #2 with channels connected to the radio base station by T1 trunks or microwave links.


42 025-9619A

4-Wire Leased Lines

From the IMS ALS Configure menu, configure the Radio Tone Database #1. These settings will be used to control TRC radios over leased lines (copper). The levels have been increased a little to allow for some line loss between the Acom equipment and the radio site.

• HLGT level = 3 dBm600

• LLGT level = -27 dBm600

• FT level = -7 dBm600

• Voice Audio = -6 dBm600

Program the function tones as required. Setting channel 1 to equal 1950 Hz is common. Program the EMU/RIU card transmit gain for +5.8 dB and use the Audio level setting in the Radio Tone Database #1 to adjust the voice audio level for proper deviation on the radio channel.

Microwave and T1 Links

From the IMS ALS Configure menu, configure the Radio Tone Database #2. These settings will be used to control TRC radios over digital links (microwave links and T1 circuits). The maximum audio level in these situations will be 0 dBm.

• HLGT level = 0 dBm

• LLGT level = -30 dBm

• FT level = -10 dBm

• Voice Audio = 0 dBm

Program the function tones as required. Setting channel 1 to equal 1950 Hz is common. Program the EMU/RIU card transmit gain for 0 dB and use the Audio level setting in the Radio Tone Database #2 to adjust the voice audio level for proper deviation on the radio channel.

Note If a squealing sound is heard over the radio channel when the

base station radio is keyed by the console, the LLGT level may be set to high. Try reducing the levels of your guard tones generally, while maintaining the same ratio between tone levels (+10/0/-20). The easiest way to do this is by reducing the Tx gain of the card.

Radio Base Station Alignment

Before getting into the specific alignment of the TX audio for individual radio channels, you should consider setting up all of your transmitters to a common test signal from the Acom console. With this done, the final TX level adjustments will simply be


43

compensating for variations in line loss between the Acom equipment and the various radio base station sites.

Tip It is suggested that you set the transmitter sensitivity so that a

tone arriving from the console at -6 dBm600 will cause 65% deviation on the transmitter channel (90% modulation for AM).

EMU and RIU Card Transmit Alignment

To set basic interface card transmit levels:

1. Prior to starting the level alignment, use the Console Designer software to add an Alert Tone button to the screen at a console position. (Unless the console form file already provides one.)

2. Using IMS ACU, configure the ACU to generate a test tone at -6 dB0 when the Alert Tone button is used.

3. Select the radio line under test and activate the test tone.

4. From the IMS terminal, adjust the RIU/EMU card in use to produce a transmitter deviation of 65% on that radio channel.

5. Release the test tone. Key the transmitter manually.

6. Speak into the microphone in louder than normal voice and verify that the radio channel is not driven past full channel deviation. (No clipping.)

If you will be doing tone-based paging on a radio channel, it is important that the paging tones are sent out with sufficient deviation to alert pagers, but not to the point of over-deviating the transmitter. The paging adjustment should not be done until the basic voice adjustment has been completed.

To set transmit audio levels for paging:

1. If radio transmitter you will be paging from uses pre-emphasis for voice audio, you will need to enable de-emphasis for paging tones in order for them to have a flat frequency response coming out of the transmitter. Using the IMS ALS software, access the setup for the SMU card, and in the Acom Definitions Level tab enable the de-emphasis filter for paging.

2. The 2-tone, 5/6-tone, and DTMF paging levels are set in the IMS ALS line definitions in the RIU/EMU Levels tab. Begin with both the Paging level and the DTMF level set to -6 dB. The paging tones must pass through the RIU/EMU card for the line under test, so the TX level of that card will also affect the final transmit level for the page.

3. From an active console position (user logged on), manually create and send a 2-tone page with 500 Hz followed by 1000 Hz for the two tones and 4 second/4second timing. This will provide a decent test signal to allow you to check that the frequency response for paging tones is flat.


44 025-9619A

4. Use a radio service monitor to measure the deviation level of the transmitted paging tones. In addition to confirming that the frequency response is flat during a page, adjust the Paging Level in the line definitions to obtain a 65% deviation during the paging tones.

5. From the same console position used earlier, manually create and send a 2-tone page with 1500 Hz followed by 2000 Hz for the two tones and 4 second/4second timing.

6. Use the radio service monitor to measure the deviation level of the transmitted paging tones. Verify that the frequency response is still flat and that the deviation is still 65%.

7. Repeat this procedure on all remaining radio lines that will support tone-based paging.

Telephone Transmit Alignment

Reducing the level at which audio is transmitted from the console to a telephone line will reduce the amount of reflected energy at the hybrid. This will result in less sidetone (echo) and thus make the audio sound better to the console operator.

To adjust telephone transmit audio level:

1. From a console position, make a call to an off-site telephone where a technician is waiting to assist you.

2. Adjust the EIE/TIE card transmit audio level to suite your needs. The lower the level is set, the less sidetone the operator hears. The technician on the other end can tell you if the voice audio is still loud enough at the other end of the call.

3. When you have this line set satisfactorily, hang up and repeat the process for all phone lines in the system.

Overview of the Alarm System

45

Managing Fault Alarms

Overview of the Alarm System

Aside from the visual alarms that can be defined and monitored, there are relay contacts on the MSU card. The contacts may be connected to a wide range of external circuits and equipment; they may be configured to activate when a user-defined alarm occurs. They can be deactivated in many ways, depending on the alarm mode (see Output Alarms on page 46).

Typical applications may include connection of the urgent alarm relay to a visual or audible alarm, alerting personnel of a link failure.

Note Many of the alarms identified in this manual are listed as “not

used with Acom.” These alarms, although not used with Acom hardware, appear in the IMS software because other hardware systems use the alarms. All alarms are included here for completeness.

Input Alarms

Input Alarm Status

The status of an alarm is stored as a two-bit code in the alarm log viewable in Acom Console Software (see “Alarm Log Display Panel” in Acom Console Operation, P/N 025-9530). Table 6 shows status bits and what they mean.


46 025-9619A

Table 6. Input Alarm Status

Alarm Status Bits Alarm Status

00 Idle

01 Was active. Shows that at some point the alarm was raised but is not currently active

10 Acknowledge. The input alarm is still active but the output alarm is not asserted

11 Active. The only state during which an alarm output is active

Figure 5 shows the input flow.

Figure 5. Alarm Input States

11Active

01Was Active

10Acknowledge

00Idle

Alarm inputdetected as active

Alarm input still active, buthas been acknowledged

Alarm input no longer active

Alarm inputacknowledged

Idle

Alarm inputbecomes

active

Alarminput isdeactivated

The “was active” state is functionally different from the “idle” state, in that the “was active” state is used to indicate to a user that an alarm has been active.

Note Never acknowledge an active alarm. This can mask a critical

issue that may require attention. Let active alarms clear automatically when the alarm condition clears on its own.

Output Alarms

Each input alarm can be sent to one, many, or all output alarms. One, many, or all input alarms can be sent to the same output alarm. The required configuration is set through IMS (see “Alarm Menu” in Acom Software Configuration, P/N 025-9529).

Passive Mode

In passive mode, the alarm output becomes active when alarm input becomes active; it is deactivated only when it is acknowledged from within IMS or the ACK ALL output alarm or the input alarms become deactivated. Passive mode is the default operating mode for alarm outputs.

IMS Fault Logs

47

Locked Mode

In locked mode, the alarm output becomes active when the alarm input becomes active. It can only be deactivated when acknowledged from IMS or the ACK ALL output. The alarm input becoming deactivated does not put the alarm output into the idle state. The alarm output can be set active from IMS, but again it is only cleared by acknowledging it. In this mode a brief failure, such a temporary link failure, is latched until the alarm is acknowledged.

Pulsed Mode

In pulsed mode, the alarm output becomes active when alarm input becomes active. The output will stay active for a set time and then become deactivated. The active pulse time is set from IMS and is common for all pulsed outputs. Before the output can become active again, the alarm input has to be deactivated or the alarm acknowledged.

Protected Mode

In protected mode the alarm output becomes active when the alarm input becomes active. It can only be deactivated when the input alarm is deactivated. The alarm input becoming acknowledged from IMS or the ACK ALL does not put the alarm output into the idle state.

Protected mode outputs are used for scenarios where acknowledging input alarms does not change the system state, for example Acom subrack redundancy state. Refer to ISB Status in the manual Acom Software Configuration (P/N 025-9529).

IMS Fault Logs


Note If your system has multiple IMS Terminal computers and they

are utilized to access the same system, please only use one computer to review fault logs. The fault logs are flushed to disk once viewed and if more than one computer is used to view fault logs, there will not be an all inclusive history of all faults on a single disk drive.


48 025-9619A

IMS Fault Log Tool

The following screen shot shows the IMS Fault Log tool. The Fault Log tool enables you to view, save, and clear the rack’s fault log. All fault records are stored in the rack until viewed or deleted by this tool.

Warning! Once the logs are retrieved (using Show Current Faults),

the rack’s fault log is cleared. The logs exist in an encrypted file that may only be viewed with IMS software while connected to a device. To view the logs off-line without using IMS, you must save the logs to a suitable file on the computer that flushed them.

Using the Show Current Faults option does not show all the logged faults. Enter a date range to see a specific range of events.

For detailed information on using this tool, see “Fault Log” in Acom Software Configuration, P/N 025-9529.

Figure 6. IMS Fault Log Tool

Table 7. Using the IMS Fault Log Tool

Control Description

Clear Rack Fault Log The faults stored in the rack will be cleared without saving them to disk.

Delete All Saved Faults

The fault logs for this device will be deleted from the local PC fault database.

Delete Selected The selected start/stop range will be deleted from the local PC fault database.

Close Closes the fault log selection form without displaying any faults.

Display Opens a display window showing either the current faults or a range of saved faults. Depends on the selection.

Show Current Faults With this selected, clicking Display will retrieve the current fault list from the rack. Once retrieved the fault log will be cleared and the downloaded faults are saved to a database on the local PC or the IMS Router. After being saved the faults are shown to the user, an opportunity to save the faults to a plain text file is available at this time. This option is only available when on-line.

IMS Fault Logs

49

Show Selected Faults The range selection fields are enabled for choosing the start and stop time/data to view. After selecting the range, click Display to view the historical faults stored in the PC database. This does not retrieve any faults from the subrack. This option is available on-line and off-line.

Fault List

When you click Display (to view either all current or selected saved fault records), the Fault List window is displayed:

The information displayed is as follows, reading left to right.

Field Example Description

Source 0MCU Slot position in the rack and name of card.

Time 02:48:26 Time the fault occurred, as reported by the rack.

Date 29/May/2009 Date the fault occurred, as reported by the rack.

Event Type Input Alarm Type of event. See the Alarms appendix of the Acom System Maintenance manual for details.

State (Active) Current state of the fault, if it is an alarm condition. Always either Active or Inactive.

Detail :LCB Alarm Some further information about the fault.

From the Fault List window, you have the following options:

• Click Print to send the list to a printer.

• Click Save to save the list to a text file. You will be prompted for a destination folder and file name.

• Click Delete the delete the listed fault records from the database.


50 025-9619A

Alarm Types

Alarms will be one of three types: Input Alarms, Output Alarms, or Other Events.

Input Alarms

Prefixed by alarm text “Input Alarm (InActive)” or “Input Alarm (Active)”. Input alarms are created by digital inputs on the MSU card, an internal fault or message, or an E1/T1 fault.

For a complete list of fault log input alarms, see Fault Log Input Alarms on page 319.

Output Alarms

Prefixed by alarm text “Output Alarm (InActive)” or “Output Alarm (Active)”. Output alarms are created because of one or more connected/mapped input alarms. They may trigger LEDs, relays, E1/T1 alarms, or internal messages. See the Output alarm list for a complete description of the output alarms and their meaning.

For a complete list of fault log output alarms, see Fault Log Output Alarms on page 324.

Other Events

Other internal messages are logged to the fault log as they happen. Table 8 provides descriptions for some of the more common events.

Alarm Names

Table 8. Alarm Names in the Fault Log

Alarm Text Examples Description

Rack was reset The ALS, DS3 Switch (ADS), or Acom Console Unit was reset.

Saved configuration is corrupt

This can occur during power up if the configuration location does not have a valid configuration. This may occur because Acom does not make use of the 2nd configuration location so it is always corrupt.

New clocking source selected. Slot 0 [Default]

The rack has a list of E1 clock sources that should be used. All of the preferred sources have been lost so the rack is generating its own clocking. [Default]

Musac Conf Resource Low

The MCU card has 2 Musac chips for conferencing time slots. Each Musac can create 21 connections. When the MCU reaches this limit this alarm can occur. The system may operator fine with this alarm, but a check should be done to verify the number of logged lines/access channels does not exceed the racks ability.

Clearing Faults

51

Alarm Text Examples Description

Selftest Good The rack finished a power on self-test.

MCU installed in slot 0 The rack found an MCU card in the first slot. This may be part of a normal power up sequence.

Lcb Bad or Lcb OK The LCB is a data communications link over time slot 16 of the E1 between the subrack and the ADS. This may occur because of a break in the E1 link.

Max DSP instruction cycles exceeded - DSP 0

The SMU resource use has exceeded its maximum cycle limit. This may cause the rack to stop decoding/encoding signaling. Check the SMU programming, the error message will indicate what card and DSP is overloaded (see “SMU Card Options” in Acom Software Installation and Configuration, P/N 025-9529).

Codec has died in slot 6 The MCU card has lost communications with the CODEC (Coder/Decoder) chip on this card. This may occur because the card has died or has been removed.

SMU installed in slot 10 The MCU has found an SMU card in slot 10. This can occur as part of a normal power up sequence. It could occur as part of an SMU reset.

EIE removed from slot 6 The MCU has detected that the EIE in slot 6 has been removed or is dead.

Card in slot 7 has reset The card in slot 7 has reset on its own. This may be because of a problem with the card or because it was commanded to do so from the debug prompt.

2Mb Link 1 has gone faulty

The first E1 link on this card is bad. Could be caused during a reset or because of a device or cable failure.

2Mb Link 1 is bad, signaling was reset

The first E1 link on this card is bad. Could be caused during a reset or because of a device or cable failure.

Unknown Error. Code: 134

Often seen as part of a reset, this error code represents that link 1 has failed. Error code 135 would indicate that link 2 has failed.

Reset – Watchdog The rack has reset because of a watchdog fault. The processor may have died or the MCU card may have been removed.

Console Reset The ACS has reset its serial link with the Acom Console Unit. A timeout may have expired.

Console Ok or Console Bad

The ACS has lost (bad) or established (OK) serial communications with the Acom Console Unit.

DSP IDMA read/write failure

This could occur if the SMU has been over allocated. Check the resource programming. The maximum memory may have been exceeded.

Clearing Faults

The Fault Log option (on the IMS ALS Tools menu) enables you to view, save, and clear the rack’s fault log. The fault log records all input and output alarms and other events that


52 025-9619A

occur in the rack. All fault records are stored in the rack until viewed or deleted by this utility.

To delete all fault records in the rack’s fault log without displaying them or saving them in the local database

Click Clear Rack Fault Log button.

To display all fault records in the rack’s fault log, save them in the local database, and delete them from the rack

1. Select Show Current Faults.

2. Click Display. See Fault List on page 49.

To display fault records that have been saved in the local database

1. Select Show Selected Faults.

2. Enter the time and date range in Start From and Stop At.

3. Click Display. See Fault List on page 49.

To delete certain fault records that have been saved in the local database

1. Select Show Selected Faults.

2. Enter the time and date range in Start From and Stop At.

3. Click Delete Selected.

To delete all fault records that have been saved in the local database

Click Delete All Saved Faults.

Operator Databases

53

Managing Console Databases

Operator Databases

This section describes how to update the database of operators. The two primary tools available to perform the necessary tasks are the Acom Profile Management (APM) utility and the User Management System (UMS). When either one of these programs is used, their function is not only to control who may log on to a console position, but also to allow various aspects of the user interface and console functionality to be customized based on the specific user logging on. If they were not used, the consoles would be restricted to using the same default settings contained in their .ini files all the time.

The usual preference would be to use APM since it allows you to configure more features and settings on a user-specific basis. Both programs can be used in the same system as long as the user names and passwords are the same in both databases. In this case, the APM profile is referred to for name, password, OpenSky ID, PTT Priorities, and Line Group associations, while the UMS file controls which screen forms are available to the user.


54 025-9619A

Profile Management Utility

When the Acom Profile Management program is used, as described in this chapter, it may handle any of the tasks UMS is used for and in addition to:

• Set an operator’s OpenSky ID and password.

• Specify the hunt groups that the operator can use (variants of, and/or in addition to, those defined in AcomConsole.ini).

• Specify the ACD queues that the user will be automatically attached to.

• Set the priority of an operator’s transmit audio over handset/headset and/or audio panel interfaces.

• Specify whether the person is a Supervisor that should receive alarms. (If so, this requires that the screen form loaded for this user have an Alarm button defined in it.)

• Restrict an operator from transmitting on certain lines.

• Specify user role number for routing incoming calls to specific consoles, based on Lookup Data matching the role number.

• Add Line Groups

These extra tasks can also be available to a UMS user if the UMS account is added to Profile Management.

When you start the Acom Profile Management utility, it loads the Profiles.xml file that is in the AcomConsole Admin folder, if that file exists. If it does not, nothing is loaded and you will have to browse to the folder that contains it on that computer. You can save profile information under other filenames, but once the file is copied to a console position computer, ACS checks for the file name Profiles.xml in the AcomConsole folder whenever a user attempts to log on or perform certain other actions. That is the only file for which it will check.

The main screen shows the Operator Profile window, which lists all users of ACS who have been defined in Profiles.xml.

Note If the computer you are working on has multiple versions of the

Profiles.xml file stored on it, always make sure to read the path and file name shown at the bottom of the Operator Profile window of the management utility to confirm you are editing the correct file.

To add or edit a Profile entry

1. To add a new entry, click Add. To edit an existing entry, either double-click the entry, or select it and click Edit. In any case, the Update operator information window appears.

Operator Databases

55

2. Edit the fields according to the descriptions provided in Table 9. The only required information is the Logon name.

3. Click OK, or Cancel to discard changes.

4. On the main screen, click Save File.


56 025-9619A

Table 9: Acom Profile Management Operator Information Parameters

Field Description

Name This function is not currently supported (though, if you enter anything here, it will be displayed under Role on the main screen).

Operator Logon Information

Logon is also displayed under Operator Logon on the main screen. This is the ID to be entered in the Logon field of the ACS User Details window when the user attempts to log on. If a Password is typed, the Verify Password field will appear below it. Type the password again in that field for confirmation. Default is no password. The password will be saved in Profiles.xml in encrypted form. If UMS is used, this logon information must match that entered in the UMS database.

OpenSky Registration Information

If an OpenSky network is in use, Mobile ID is the user’s ID for registering with the network. This is automatically passed to the network when the user logs on. If a Password is typed, the Verify Password field will appear below it. Type the password again in that field for confirmation. The password referred to here is the OpenSky network password assigned by M/A-COM Wireless. Default is no password. This logon information must match that entered for Voice End User in the OpenSky network database.

Forms This area specifies all screen forms that the user is entitled to open if UMS is not being used. See To add or edit a Form entry on page 57. (If UMS is being used, form names are given in the [UMS.Screens] section of AcomConsole.ini.) The forms referred to here are the .dfm files created for ACS using the Console Designer application.

ACD Automatic Queue Attachment

If ACD is enabled, and if this user is to participate, enter the name(s) of ACD queues to which the user should be automatically attached. Use a comma to separate names.

HS Priority and AP Priority

Enter a number to specify the user’s transmit priority over the headset/handset interface (HS) and/or the audio panel (AP) interface. Range is 0 to 3. Values are relative to those specified for other users and lines.

Supervisor Check this box if the user has supervisor rights to alarms.

Disable Tx Line Group

Lines and/or line groups specified here cannot be used by this operator for transmitting. They cannot even be selected. They can only be monitored. Use a comma-separated list of individual line numbers, ranges of line numbers, and/or line group names.

Role Number To have Selcal calls directed to the user’s console according to role, enter a number here. It must be the same number entered in IMS ALS under Configure, Lookup Data. (When the Detect Type entered there is Selcal, and the Response Type is Match Acom Call ID, use this number for the R#.)

Line Groups If more than one user can have access to the same line group name, but with different line assignments for different users, define them here instead of in AcomConsole.ini. If the same line group name is defined in both places, the definition in AcomConsole.ini will override this one.

Operator Databases

57

To add or edit a Form entry

1. To add a new entry, click Add under the Forms pane. To edit an existing entry, either double-click the entry, or select it and click Edit. In any case, the EditFormFile window appears.

2. Type a Display Name. This will be used in the drop-down list in the b field in the ACS User Details window when the user attempts to log on.

3. Type the corresponding filename of the screen form file (*.dfm). The file must reside in the AcomConsole folder.


To add or edit a Line Group entry

1. To add a new entry, click Add under the Line Groups pane. To edit an existing entry, select it and click Edit. In either case, the Edit Line Group window appears.

2. In the Name field, type a name by which the group of lines can be easily referred to. It must match a name used in the Line(s) field of a component in Acom Console Designer.

3. In the Line(s) field, type a comma-separated list of and/or a hyphen-separated range of line numbers.

Examples:

1,3,5 1-10 1,3,5,11-20,40,60-65 s(1-10)



58 025-9619A

User Management System

When UMS is used, the Zetron Account Management program (ZAM), as described in the User Management System Product Manual (025-9516), is used to:

• Change an operator’s logon name, password, or role.

• Update the list of screen forms that an operator can load.

• Add an operator.

• Delete an operator.

• Show a list of users that are currently logged on to ACS.

• Log a user off remotely (force logoff).

Paging Configuration Database

The Acom Paging Configuration utility enables you to specify various parameters for the paging module in ACS, including types of instant pages. The utility displays three primary areas of interest, for configuring instant paging, page formats, and global paging parameters. These areas are presented in the following subsections, followed by a typical procedure for setting up a page format.

New Configuration File Format

The format of the file that stores paging configuration may have been changed since your last installation. If you are upgrading from a previous version of the Acom Paging Configuration utility, you must migrate the old data into the new format.

To migrate a paging configuration to the latest format

1. From the Windows Start menu, open a Command Prompt window.

2. Go to the folder containing the existing paging configuration file. For example, cd \Program Files (x86)\Zetron\AcomConsole

3. Make a backup copy of the existing paging configuration file. For example, copy AcomPaging.config AcomPaging.old.config

4. Enter the migration command: PagingSchemaConversion AcomPaging.config

When the command completes, the paging file is ready for use with the newer version of the Acom Paging Configuration utility and ACS.


59

Note The name of the paging configuration file must be

AcomPaging.config to be recognized by the software. If the machine you are working on has multiple AcomPaging.config files, be sure that you browse to the correct location and file before you start editing.

Page Global

Use this area to specify the file to save the paging configuration information in.

Field Description

Paging configuration file The name of the file in which paging configuration information is saved. AcomPaging.config is the default. To save in a different file, type the file name here, and/or Browse to a different folder.

NOTE: You can save files under as many names as you want, but the only one that the software will load is AcomPaging.config.

New Configuration To create a new (empty) paging configuration file, check this box and type the new filename in the Paging configuration file field.

Page Format

Use this area to configure paging formats used in instant or manual paging. The window initially shows the Page Formats List.


60 025-9619A

To add a page format

1. Click Add. The Page Format Configuration window displays.

2. Select the desired format from the Formats list.

3. Adjust the format settings as necessary in the Properties list.

4. Click OK.


61

Field Description

Name A short, descriptive name for the type of page. This will appear in the Format Name list in the Page Capcode and Line Definitions window.

Formats ACS supports these paging formats: Standard Two Tone, Custom Two Tone, Standard DTMF, Knox DTMF, Alert Tone, and 1500/2805 H.E.A.R.

Standard Two Tone Format Settings

Tone Type Reach Call 1000, Two Tone 100 Call, or Two Tone 1000 Call

Code Plan For Reach Call 1000: None (unused)

For Two Tone 100 Call: GE A´, GE B´, GE C´, Mot 1, Mot 2, Mot 3, Mot 4, Mot 5, Mot 6, Mot 10, Mot 11, Mot A, Mot B, or Mot Z

For Two Tone 1000 Call: GE X, GE Y, GE Z, Mot B, Mot C, Mot D, Mot E, Mot F, Mot G, Mot H, Mot J, Mot K, Mot L, Mot M, Mot MT, Mot N, Mot P, Mot Q, Mot R, Mot S, Mot T, Mot U, Mot V, Mot W, or Mot Y

See the radio’s documentation for details

Diagonal Type First Tone or Second Tone. Applies only if Group Plan is set to Diagonal

Group Plan None, Group, or Diagonal

Timing Plan For Reach Call 1000: fast with gap, fast with no gap, slow with gap, or slow with no gap

For Two Tone 100 or 1000 Call: Mot, Mot/GE, NEC A, NEC B, NEC C, NEC D, NEC L, or NEC M See Two-Tone Timings on page 66 for details

Custom Two-Tone Format Settings1

Tone 1 duration Duration of the first part of the two-tone signal. 0 to 6553.5 (ms)

Tone 1 frequency Frequency of the first part of the two-tone signal. 0 to 6553.5 (Hz)

Tone 2 duration Duration of the first part of the two-tone signal. 0 to 6553.5 (ms)

Tone 2 frequency Frequency of the first part of the two-tone signal. 0 to 6553.5 (Hz)

Tone gap duration Time between the first and second parts of the two-tone signal. 0 to 6553.5 (ms)

DTMF Format Settings (both Standard and Knox)1

Tone Off Duration Time between signals. 0 to 4095 (ms)

Tone On Duration Duration of the signal. 0 to 4095 (ms)

Alert Tone Settings

Alert tone identifier

The ID of the Custom Tone to use, as defined in IMS ALS. Range is 1-20. See Alert Tones in the Acom Software Configuration manual


62 025-9619A

Field Description

Tone cycles The number of times to repeat the custom tone. If set to 0, Tone duration is used instead

Tone duration Used only if Tone cycles is set to 0. The length of time to play the custom tone

1500/2805 H.E.A.R. Settings

Make Freq Either 1500 Hz or 2805 Hz. The tone to be output indicating the start of dialing

Break Freq Either 600 Hz or None (that is, silence). The tone to be output indicating the end of dialing

Call Size The number of digits in a pulsed tone page. Range is 1-8 digits. If fewer than 8 digits are required, keyboard entry can be lessened by setting a lower value

Interdigit delay Amount of time Acom will wait between digits during transmission

Lead Tone period Amount of time Acom will transmit the lead tone

Digit Straps If any of the digits will always be the same, in the same order of entry, you can eliminate the need to enter it by keyboard by “strapping” it to a specific value. For example, if the first digit will always be 0, enter 0 here. The fields for digits greater than Call Size are unavailable.

1 - The combination of tone on/off durations in a single page cannot exceed 10 seconds. If it does, the tone generator is stopped at 10 seconds and there is no indication to the operator that the page was terminated.

To modify a page format:

Note You cannot modify a page format that is used in an Instant Page

definition. You must remove it from the Instant Page definition first.

1. Select the Format.

2. Click Edit. The Page Format Configuration window displays.

3. Enter the appropriate settings according to the preceding table.

4. Click OK.

To delete a page format:

1. Select the Format.

2. Click Delete. You will be prompted for confirmation.


63

Paging Plans and Groups

Two-Tone — Motorola and GE Tone Groups

Frequencies shown in the following tables are given in Hertz.

Mfr. Tone Groups

Mot 1

Mot 2

Mot 3

Mot 4

Mot 5

Mot 6

Mot A

0 330.5 569.1 1092.4 321.7 553.9 1122.5 358.9

1 349.0 600.9 288.5 339.6 584.8 1153.4 398.1

2 368.5 634.5 296.5 358.6 617.4 1185.2 441.6

3 389.0 669.9 304.7 378.6 651.9 1217.8 489.8

4 410.8 707.3 313.0 399.8 688.3 1251.4 543.3

5 433.7 746.8 953.7 422.1 726.8 1285.8 602.6

6 457.9 788.5 979.9 445.7 767.4 1321.2 668.3

7 483.5 832.5 1006.9 470.5 810.2 1357.6 741.3

8 510.5 879.0 1034.7 496.8 855.5 1395.0 822.2

9 539.0 928.1 1063.2 524.6 903.2 1433.4 912.0

Diagonal 569.1 979.9 569.1 569.1 979.9 979.9 979.9

Mfr. Tone Groups

Mot B

Mot Z

GE A'

GE B'

GE C'

Mot 10

Mot 11

0 371.5 346.7 682.5 652.5 667.5 1472.9 1930.2

1 412.1 384.6 592.5 607.5 712.5 1513.5 1989.0

2 457.1 426.6 757.5 787.5 772.5 1555.2 2043.8

3 507.0 473.2 802.5 832.5 817.5 1598.0 2094.5

4 562.3 524.8 847.5 877.5 862.5 1642.0 2155.6

5 623.7 582.1 892.5 922.5 907.5 1687.2 2212.2

6 691.8 645.7 937.5 967.5 952.5 1733.7 2271.7

7 767.4 716.1 547.5 517.5 532.5 1781.5 2334.6

8 851.1 794.3 727.5 562.5 577.5 1830.5 2401.0

9 944.1 881.0 637.5 697.5 622.5 1881.0 2468.2

Diagonal 979.9 979.9 742.5 742.5 742.5 none none


64 025-9619A

Two-Tone — Motorola and GE Code Plans

Pager Code

Mot B

Mot C

Mot D

Mot E

Mot F

Mot G

Mot H

Mot J

Mot K

0xx 2+4 N/A N/A N/A N/A N/A N/A N/A N/A

1xx 1+1 1+1 1+1 1+1 1+1 1+1 1+1 1+1 1+1

2xx 2+2 2+2 2+2 2+2 1+3 1+3 1+3 1+4 1+4

3xx 3+3 1+2 1+2 1+2 3+3 3+3 3+3 4+1 4+1

4xx 1+2 4+4 1+5 2+1 4+4 3+1 3+1 4+4 4+4

5xx 1+3 1+4 5+5 1+6 3+1 5+5 1+6 5+5 1+6

6xx 2+1 2+1 2+1 6+6 1+4 1+5 6+6 1+5 6+6

7xx 3+1 4+1 5+1 6+1 4+1 5+1 6+1 4+5 6+1

8xx 2+3 2+4 2+5 2+6 3+4 3+5 3+6 5+4 4+6

9xx 3+2 4+2 5+2 6+2 4+3 5+3 6+3 5+1 6+4

Groups Used 1,2,3,4 1,2,4 1,2,5 1,2,6 1,3,4 1,3,5 1,3,6 1,4,5 1,4,6

Pager Code

Mot L

Mot M

Mot N

Mot P

Mot Q

Mot R

Mot S

Mot T

Mot U

0xx N/A 4+2 4+2 4+2 4+2 4+2 4+2 4+2 4+2

1xx 1+1 2+3 2+3 2+3 2+4 2+4 2+5 3+4 3+4

2xx 1+5 2+2 2+2 2+2 2+2 2+2 2+2 4+3 4+3

3xx 5+1 3+3 3+3 3+3 4+2 4+2 5+2 3+3 3+3

4xx 1+6 4+4 3+2 3+2 4+4 4+4 2+6 4+4 4+4

5xx 5+5 3+2 5+5 2+6 5+5 2+6 5+5 5+5 3+6

6xx 6+6 2+4 2+5 6+6 2+5 6+6 6+6 3+5 6+6

7xx 6+1 4+2 5+2 6+2 4+5 6+2 6+2 4+5 6+3

8xx 5+6 3+4 3+5 3+6 5+4 4+6 5+6 5+4 4+6

9xx 6+5 4+3 5+3 6+3 5+2 6+4 6+5 5+3 6+4

Groups Used 1,5,6 2,3,4 2,3,4,5 2,3,4,6 2,4,5 2,4,6 2,4,5,6 2,3,4,5 2,3,4,6

Pager Code

Mot V

Mot W

Mot Y

Mot MT

GE X

GE Y

GE Z1

0xx 4+2 4+2 N/A 4+2 A'+A' B'+B' A'+A'

1xx 3+5 4+6 A+A 1+1 B'+A' C'+B' C'+A'

2xx 5+3 6+4 B+B 2+2 B'+B' C'+C' C'+C'

3xx 3+3 5+6 Z+Z 1+2 A'+B' B'+C' A'+C'


65

4xx 3+6 4+4 A+B 4+4 C'+C' N/A N/A

5xx 5+5 5+5 A+Z 5+5 C'+A' N/A N/A

6xx 6+6 6+6 B+A 2+1 C'+B' N/A N/A

7xx 6+3 4+5 Z+A 4+5 A'+C' N/A N/A

8xx 5+6 5+4 B+Z 5+4 B'+C' N/A N/A

9xx 6+5 6+5 Z+B 2+4 N/A N/A N/A

Groups Used 4,5,6 2,4,5,6 A,B,Z 1,2,4,5 A',B',C' B',C' A',C'

1- GE 100-call plan Z is tone groups C’ + C’; use (100-call format).

For capcodes ending in double-digits that use the same tone group for both tones (for example, pager capcode 122 in a code plan C), use the diagonal tone as one of the tones.

Two-Tone — General Encoding Plans

General Plan Modified General Plan General Alternate Plan

Pager Capcode

Tone Groups

Diagonal Tone1

Tone Groups

Diagonal Tone1

Pager Capcode2

Tone Groups

0xx 4+2 N/A N/A N/A 0xx N/A

1xx 1+1 569.1 1+1 569.1 1xx 953.7 + Mot 1

2xx 2+2 979.9 2+2 979.9 2xx 953.7 + Mot 2

3xx 1+2 N/A 3+3 569.1 3xx 979.9 + Mot 2

4xx 4+4 569.1 4+4 569.1 4xx 953.7 + Mot 4

5xx 5+5 979.9 5+5 979.9 5xx 953.7 + Mot 5

6xx 2+1 N/A 6+6 979.9 6xx 979.9 + Mot 1

7xx 4+5 N/A N/A N/A 7xx 979.9 + Mot 5

8xx 5+4 N/A N/A N/A 8xx 979.9 + Mot 4

9xx 2+4 N/A N/A N/A — —

Axx 3+3 569.1 N/A N/A — —

Tone Groups 1,2,3,4,5 1,2,3,4,5,6 — —

1 - On General and Modified General plans, there are different diagonal tones for different pager blocks.

2 - For General Alternate Code Plan, last two digits of capcode are the same as each other.


66 025-9619A

Two-Tone Timings

Durations are given in seconds.

1st Tone Silent Gap 2nd Tone Group Call Pager Brand

1.0 0.25 3.0 8.0 GE Tone + Voice

1.0 None 3.0 8.0 Motorola Tone + Voice

0.4 None 0.8 8.0 Motorola Tone only

1.0 0.25 3.0 6.0 NEC Type A

1.0 None 3.0 6.0 NEC Type B

1.0 None 1.0 4.0 NEC Type C

0.4 None 0.4 3.0 NEC Type D

0.5 None 0.5 3.0 NEC Type L

0.4 None 0.8 4.0 NEC Type M

0.13 None 0.13 1.4 Reach Fast

2.0 None 0.7 4.5 Reach Slow

Tone Groups for Reach Encoding

Tone Number

Z1

Z2

Z3

Z4

Z5

0 1980.0 1177.0 1400.0 832.0 588.0

1 2704.0 1608.0 1912.0 1137.0 804.0

2 2612.0 1553.0 1847.0 1098.0 776.0

3 2523.0 1500.0 1784.0 1061.0 750.0

4 2437.0 1449.0 1723.0 1025.0 725.0

5 2354.0 1400.0 1664.0 990.0 700.0

6 2274.0 1352.0 1608.0 956.0 676.0

7 2196.0 1306.0 1553.0 923.0 653.0

8 2121.0 1261.0 1500.0 892.0 631.0

9 2049.0 1219.0 1449.0 862.0 609.0


67

Reach Code Plan

Pager Capcode

Individual Call Tone Groups

0yx Z5+Z3

1xy Z1+Z2

2yx Z2+Z1

3xy Z3+Z4

4yx Z4+Z3

5xy Z1+Z4

6yx Z4+Z1

7xy Z1+Z5

8yx Z5+Z1

9xy Z3+Z5

Instant Pages

You will first need to define page formats. See Page Format on page 59.

Use this area to configure the parameters for ACS Instant Page buttons. The window initially shows the Instant Pages List.


68 025-9619A

To add or modify an instant page:

1. Click Add to add a new instant page, or select an existing instant page in the Name column and click Edit to modify it. In either case, the Instant Page Configuration screen opens.

2. Configure as described in the following table.

Field Description

Name A brief descriptive name for the page. This is used as the dial number in ACS. The string entered for Name is case sensitive and must match the name for its Instant Page function key exactly. Matching the two Name parameters is how the ACS software associates the key appearing on screen with the Instant Page definition it is supposed to call.

Instant Pages configured for use in a CAD system connected by way of the M25ES option must have names of the form “M25_nnnn”, where nnnn is the instant page number that will be typed in from the CAD interface when initiating a page. See M25ES Option on page 72.

Description An optional brief description indicating the purpose of the page.

Inter-Capcode Delay

Delay between pages in a stack. 0 to 10 (seconds), in 0.1-second increments. The purpose of this parameter is to prevent falsing between adjacent pages.

Page Stacks Lists the page stack(s) to include in this instant page. The Name comes from the Page Stack Configuration screen. A paging button on the console screen can only be associated with a single Instant Page definition. However, a single Instant Page definition can contain one or more page stacks.

Add Page Stack Click to add a new page stack to the Page Stacks list. See following subsection.


69

Field Description

Edit Page Stack Click to edit the selected page stack in the Page Stacks list. See Page Stack Configuration on page 69.

Remove Page Stack

Click to delete the selected page stack in the Page Stacks list. You will be prompted for confirmation.

Lines Lists the lines to transmit this instant page over. Includes some further configuration parameters.

Add Line Click to add a new line configuration to the Lines list. See following subsection.

Edit Selected Line Click to edit the selected line configuration in the Lines list. See Line Configuration on page 72.

Remove Line Click to delete the selected line configuration in the Lines list. You will be prompted for confirmation.

End of page selected lines

The lines to be selected after all Instant Call pages have been sent.

Line — The line number assigned when configuring the ALS. From 1 to 2200.

Frequency — Channel frequency for the selected line. 1 to 4 or No Change. If you want to change the frequency of the line when it becomes selected at the end of the page transmission, enter the new frequency value in the Frequency field.

To delete an instant page:

1. Select the instant page in the Name column.

2. Click Delete. You will be prompted for confirmation.

Page Stack Configuration

Use the Page Stack Configuration screen to add pages to the stack, delete pages from the stack, or edit pages in the stack. Each Page Stack can contain one or more page/alerts. Each Page Stack can be steered to a set of channels so that each page in the stack is sent sequentially on all configured lines at the same time.

The Lines list at the bottom of the form lists the lines to transmit this instant page over. It includes some further configuration parameters.

Clicking Add Line or Edit Line leads to the Selected Line Configuration window. See Line Configuration on page 72.


70 025-9619A

Page Configuration

The Page Configuration screen appears when you click Add Page or Edit Page on the Page Stack Configuration screen. Use this area to specify page names, capcodes, and formats to use in the Instant Page you are defining on the Page Configuration screen.

Field Description

Name This field lists the name by which this page is identified. It is displayed in the page stack.

Capcode This field holds the address or dial string for making the page. Alert tones and Custom Call 2-tone pages do not require a capcode entry. For additional information on how two tone capcodes are made see Paging Plans and Groups on page 63.

OK Click to save changes and return to the Instant Page Configuration screen.

Cancel Click to cancel changes and return to the Instant Page Configuration screen.

Apply Click to save changes but not leave this screen.


71

To add an Instant Page definition:

Note Before you can add Instant Pages, you must select the paging

formats that will be available and add them to the Paging Formats List.

1. On the Page Stack Configuration screen, click the Add Page button.

2. Type a name for the page in the Name field.

3. Open the Format list and select a paging format for the page.

4. Enter a capcode or dial string in the Capcode filed if appropriate.

5. Click OK to save changes and return to the Page Stack Configuration screen.

6. Repeat steps 2 through 5 to add other page names, capcodes, and formats as appropriate.

To modify an Instant Page definition:

1. On the Page Stack Configuration screen, select the page you want to edit and click Edit Page button.

2. Add, delete, or modify page parameters as appropriate.

3. Click OK to save changes and return to the Page Stack Configuration screen.

To delete an Instant Page definition:

1. On the Page Stack Configuration screen, select the page you want to remove from the list.

2. Click Remove Page.

3. Click Apply to update the configuration file.

Line to Select at End of Page

After the page transmission is complete, the console will select the line(s) specified as “end of page select lines” in the page’s definition. If a page stack (two or more pages sent sequentially automatically) is sent, all such lines will be selected.

On the Instant Page Configuration screen, use the End of Page Selected Lines area to specify the Line Number(s) to be automatically selected when the page is completed. You can also select a different Frequency to switch to on the line, or specify that No change is necessary.

To specify a new line, click Add Selected Line. To modify an existing line selection, click Edit Selected Line. Both choices lead to the Selected Line Configuration window. See Line Configuration on page 72.


72 025-9619A

Line Configuration

If you reach this window from the Page Stack Configuration screen, you will see two other options:

• Sometimes, prior to transmitting a page, the radio line requires a frequency change. This is configured in the PCT page capcode and line definitions. Selecting Revert will cause the frequency to be changed back to what it was prior to the page transmission, at the completion of the transmission.

• Selecting a value for Voice Hold Time will keep mobile decoders open for reception of voice transmissions, by applying carrier for the specified number of seconds following the actual paging tones. Use this feature for types of mobiles that will squelch if carrier drops between paging tones and operator TX. Typical value is 1 second.

M25ES Option

The Zetron Model 25 Emulator Service (M25ES) is available as a paging option. It provides an interface to a computer-aided dispatch (CAD) program that uses the same protocol as Zetron’s Model 25 Programmable Encoder (for example, Intergraph’s I/CAD). Tone-out commands executed from the CAD program are automatically translated into Acom Instant Pages and transmitted appropriately, by way of ACS.

To install M25ES:

1. An installer is provided in the form of an .exe or .msi file. Run it and follow its simple steps. The application files will be installed in the following folder (default): C:\Program Files\Zetron\M25Emulator

2. M25ES is installed as a Windows service. You can verify that it is installed by looking under Control Panel > Administrative Tools > Services.

3. A null modem cable must be connected between the console PC and the CAD PC. The cable may be purchased from Zetron or procured elsewhere.

4. Install M25ES on every console PC that interfaces with a CAD PC.

MDC 1200/GE Star Subscriber ID Database

73

To configure M25ES:

1. In the folder where M25ES was installed, open the configuration file ZetronM25Emulator.exe.config with a text editor such as Windows Notepad.

2. Find the appSettings section. It looks like this: <appSettings> <add key="CAD_CommPort" value="Com6" /> <add key="CAD_CommPortBaudRate" value="4800" /> <add key="ACS_StackProcessingTimeoutInSeconds" value="5" /> <add key="ACS_BusyTimeoutInSeconds" value="20" /> <add key="M25CADCallsLoggingActive" value="True" /> <add key="M25CADCallsLog" value="c:\m25CADCalls.log" /> </appSettings>

3. Edit the key values as needed, according to the following table:

Key Description

CAD_CommPort Com port on the console PC, by which the console PC is connected to the CAD PC. Any valid Com port number may be used.

CAD_CommPortBaudRate Baud rate at which the CAD PC communicates with the console PC. M25ES can use any valid rate, but consult the CAD program’s documentation for any limitations.

ACS_StackProcessingTimeoutInSeconds

Number of seconds M25ES will wait for a response from ACS after sending any request. Minimum = 1. No maximum. Recommended = 1. If ACS seems slow to respond to requests, try a larger number.

ACS_BusyTimeoutInSeconds Every one second, M25ES requests ACS to send the requested paging stack, until ACS responds or this number of seconds is reached. Minimum = 1. No maximum. Recommended = 30.

M25CADCallsLoggingActive Whether to log (True) or not log (False) interaction between the CAD PC and M25ES.

M25CADCallsLog Path and filename of the log file, if M25CADCallsLoggingActive is set to true.

4. See also the note under Name in the table describing the Acom Paging Configuration utility’s Instant Page Configuration window, under Instant Pages on page 67.


This section describes how to use the Acom Subscriber Configuration program to update the database of radio subscriber IDs. This database is used by ACS to provide meaningful


74 025-9619A

text labels for incoming MDC 1200/GE Star radio calls listed in the Call History window on the ACS screen. Use the Acom Subscriber Configuration program to:

• Add a subscriber.

• Change a subscriber’s radio ID.

• Delete a subscriber.

When you start the program, it presents the Subscriber Information screen.

The default filename is AcomSubscriber.xds (at individual console positions, it is found with the Zetron program files in the subfolder named AcomConsole). If that file exists in the ACS Admin folder, it will be loaded. If not, you will need to do one of the following:

• Load a different existing file. Click Browse, find the file you want to load, and then click Load File.

• Start a new file. Enter a name for it in the Subscriber configuration file field.

Note ACS will only load the file named AcomSubscriber.xds at the

console. If the machine you are working on has multiple .xds files, always make sure that you are editing the correct file.

The Radio Assignments pane lists the subscriber entries. Each entry includes the subscriber alias (User), radio identity (Assigned Radio), and the radio lines they may use (Lines).


75

To add a subscriber entry:

1. Click Add. The Subscriber Properties window displays.

2. Type a brief, descriptive Subscriber Alias for the user, to be displayed in ACS when in communication with the user. This will show in the User column on the Subscriber Information screen.

3. Type the corresponding Radio/Talkgroup/Channel Identity of the subscriber (the Selcal, MDC, or GE-Star string to be decoded).

4. Type the Radio Lines this subscriber may use. Separate line numbers with a comma.

5. Select the appropriate Device Type for the radio equipment used by the subscriber from the drop down list.

6. Click OK to save this entry and return to the Subscriber Information screen. (Alternatively, click Cancel to cancel changes and return to the Subscriber Information screen.)

7. Be sure to save the database file before exiting the program. To do so, click Save File. Otherwise, all of your changes will be lost. You will not be prompted to save the file.

8. The database file will be saved in the ACS Admin folder. It must be copied to the ACS folder on the consoles. This must be done each time you update the file.

To edit a subscriber entry:

1. Select it, and click Edit. The Subscriber Properties window displays.

2. Edit the fields as appropriate. Refer to the previous procedure.

To delete a subscriber entry:

Select it, and click Remove. It is deleted from the list.


76 025-9619A

Text Messaging

77

Other Console Configuration

Text Messaging

This section covers configuration of the Text Messaging option for Acom systems. In addition it covers the creation and editing of canned messages that become part of the option library.

Text Messaging Server Configuration

The computer acting as the Text Messaging Server (TM server) will have the TM server software installed at the factory. The TM server and other required software will be loaded in this order:

• Zetron AMI Server

• Zetron UMS Server and ZAM (user interface software for UMS)

• Zetron Text Messaging Server

• .NET Framework (the Acom Console Software has been installed then .NET Framework will already be installed on this computer)

Once the necessary pieces of software have been installed on the server machine, it is necessary to create “Role Permissions” for several user groups in order for the Text Messaging option to be available from within the Acom Console Software (ACS).


78 025-9619A

Configuring UMS roles of text messaging:

1. Start the ZAM application on the server machine and log on under the user name “installer”.

2. In the center pane, open the General Settings folder and select the General Options item from the list that appears.

3. In the right pane, if the categories VDU and Role Permissions do not already appear in the Enabled Categories list, select both of them from the Disabled Categories list and use the Enable button to move them to the other side.

4. If any changes were made, click on the Apply button to record these changes.

5. Return to the center pane and open the Administration folder. Then select the Define Permissions item.

6. In the right pane near the bottom, use the three fields Name, Description, and Category to define the necessary permissions. After filling in the three fields for each role, click on the Create button to record that role. A typical set of roles would Dispatcher, Supervisor, and Test Screen.

Note The field Name that appears in the Define Permissions

window is also the parameter used in the AcomConsole.ini file to relate roles to console form files. For this reason, some care should be taken to assign names that are clear, descriptive, and unique.

7. Now the role permissions must be assigned to each user. The following steps (8 through 11) must be repeated with each user that is going to use the Text Messaging option.

8. In the user pane on the left, select the correct group or simply list All Users. From the list that appears, select the individual user to work on.

9. In the center pane, open the Account Settings folder and select Account Permissions from the list that appears.

10. In the right pane, select the item Role Permissions from the Category list. The newly created permissions should appear in the Available Permissions list.

11. Select the new permissions from the Available Permissions list and then click the Add Permissions button. The selected permissions will move to the Assigned Permissions list, indicating that they are now assigned to the selected user.

12. Repeat steps 8 through 11 as necessary to program additional users.

13. In the center pane, open the Workstation Settings folder and select the item Configuration from the list that appears.

14. In the right pane, under Remote Server Communications Settings, select the Enable online mode item to enable it.

15. Log off as the Installer and exit the ZAM application (shut it down).

Integrator Instant Recall Recorder

79


The Integrator Instant Recall Recorder (Integrator IRR) is an optional voice recording/replay feature for use in conjunction with Integrator or Acom console systems. Integrator IRR consists of both hardware and software components that record the voice messages as files on the hard drive of the computer at the console position.

• The system requirements for installing Integrator IRR are very similar to the basic requirements for a generic console position computer, which is where the option must be installed.

• While there are three different modes of operation to control when Integrator IRR records audio (software control, contact-closure, and VOX control), only the preferred method of software control is presented here. For details on the other two methods, please refer to the Integrator IRR product manual.

The Zetron part number for the Integrator Instant Recall Recorder is 025-9496.

Note The use of Integrator IRR along with other applications that

perform a great deal of audio recording and playback is not recommended due to unpredictable interactions between Integrator IRR and the other applications as they compete for resources.

Hardware Interface

Figure 7 shows the Integrator IRR Interface module connected to an Acom system. Figure 8 shows the approximate location of the jumpers referred to in this section.

Table 10 lists the cables used connect the Acom system, the Integrator IRR interface module, and the console position computer.

Note You must provide the cabling if you do not have modular jack

compatible equipment or your equipment does not include contact-closure signals within the modular jack.


80 025-9619A

Table 10: IRR Interface Connections

Connection Description

INPUT 1 and 2 A special Acom to IRR cable should be used; Zetron part number 709-7728

PC USB Port to Interface Module

Standard DA-15F to DA-15M straight-through cable (Part number 709-0054) connected in line with a USB-to-game port adapter (Part number 802-0211). These are not included with the IRR. They are available together as Part number 950-0833

PC Sound Card (line-in) to PC Interface Module

Standard 1/8 inch stereo plug to 1/8 inch stereo plug audio cable for connection between the PC Interface Module and the PC sound card line-in jack (Part number 709-0055)

Figure 7: Integrator IRR interfaced to an Acom ACU (Digital Switch) 4-Wire Card

Integrator IRRInterface Module(950-0396)Game

Port

AudioOut

To PC

Input 1(PHONE)

Input 2(RADIO)

START1START COMSTART2AUX IN 1AUX IN COMAUX IN 2

RECORD CONTROLCONTACT CLOSUREINPUTS

PC

PC MultimediaSpeakers (Left/Right)

Analog Audio - Stereo

(Phone/Radio)

USB Port

Line-Level InBlue

Line-Level OutGreen (Speaker)

Contact ClosureControl (optional)

Analog Audio

(Playback Only)

JP2 & JP3 = OUT

JP4 & JP5 = OUT

Acom ACU4-Wire Card

Cable Part # 709-7728

Port 1 or 2


81

Figure 8: Jumper Locations on the Integrator IRR Interface board

T1 T2

P2P1

J1J2 J3

JP1 (Not used)

JP2

JP3

JP4

JP5

S3200 INTEGRATOR IRR INTERFACE

Table 11 and Table 12 give details about the connections available on the Integrator IRR Interface unit. Please note that the preferred method of interfacing Integrator IRR with an Acom console position is to use software control of the recording function. The cable connection for hardware control (the connection between the Game port on the interface unit and the USB port on the computer) is shown only for completeness sake.

Table 11: Descriptions of IRR Interface Module Connectors


GAME PORT (to computer)

DA-15M connectors, 2 pair. See Table 12 for pin assignments. This port is for use with the contact closure mode of record control only. The mode of control is primarily used with the Model 3230 telephone.

AUDIO OUT (to computer)

Audio jack, 1/8 inch, 3-conductor (stereo) Audio from INPUT 1 (PHONE) is on TIP, INPUT 2 (RADIO) is on the RING, and ground is referenced to SLEEVE terminal (computer analog GND), 3 Vp-p

INPUT 1 (PHONE) (from PSAP telephone)

Input J2 = RJ-14 jack, 6-position, 4-conductor Audio on center pair (pins 3 and 4) Start Recording on pins 2 and 5, using pins 2 and 5 requires that jumpers JP2 and JP3 are both IN, JP2 connects pin 2 to P2-pin 1 (connects to pin 2 of GAME PORT connector), JP3 connects pin 5 to ground

INPUT 2 (RADIO) (from dispatch console)

RJ-14 jack, 6-position, 4-conductor Audio on center pair (pins 3 and 4) Start Recording on pins 2 and 5, using pins 2 and 5 requires that jumpers JP4 and JP5 are both IN, JP4 connects pin 5 to ground, JP5 connects pin 2 to P2-pin 3 (connects to pin 7 of GAME PORT connector)


82 025-9619A


RECORD CONTROL INPUTS

The six-position screw connector signals are connected to the GAME PORT as follows: 1 - START 1 (connects to GAME PORT pin 2) 2 - START COM (connects to GAME PORT pin 4) 3 - START 2 (connects to GAME PORT pin 7) 4 - AUX IN 1 (connects to GAME PORT pin 10) 5 - AUX IN COM (connects to GAME PORT pin 5) 6 - AUX IN 2 (connects to GAME PORT pin 14)

If software or VOX is used to control IRR, then the 709-7728 interface cable must be used. If hardware control employing pins 2 and 5 is used, then interface cable 709-7639 must be used.

Table 12: Pin Values for the DA-15 Connector

Pin # Game Port Function IRR Interface Function Pin #

1 Not used Not used —

2 Joystick A, Button 1 INPUT 1 / START 1 contact closure 1


4 Ground INPUT / START COM contact closure 2

5 Ground AUX IN COM contact closure 5


7 Joystick A, Button 2 INPUT 2 / START 2 contact closure 3



10 Joystick B, Button 1 AUX IN 1 contact closure 4




14 Joystick B, Button 2 AUX IN 2 contact closure 6


Microsoft Windows® Sound Settings

Microsoft Windows sound settings must be configured manually for each audio device (provided by way of a sound card or on the motherboard) to be used with Integrator IRR. The following procedure describes how to configure the sound settings.


83

Configuring Windows Sound Settings:

1. Under Settings, Control Panel, open Sounds and Audio Devices.

2. In the Sounds and Audio Devices Properties window, select the Audio tab.

3. Under Sound Playback, from the Default device: drop-down list, select the audio device you want Windows to use to play recorded messages played back in IRR.

4. Under Sound Playback, click Volume. The Volume Control window appears.

Note The columns displayed in the Volume Control window will

vary, depending on your operating system and the controls that have been selected for display.

5. Open the Options menu and select Properties.

6. In the Mixer device drop-down list, verify that the device shown is the same as the Default device: you selected on the Audio tab.


84 025-9619A

7. Under Adjust volume for, select Playback.

8. In the Show the following volume controls list, select Line In. (Other controls may also be selected.)

9. Click OK.

10. In the Volume Control window, unselect Mute under Line In, and select Mute under all controls for devices that you do not want to play through the Default device you selected on the Audio tab. You are muting these so that they will not be able to play over an IRR message being played back.

11. Center the Balance for all unmuted controls.

12. Open the Options menu and select Properties.

13. Under Adjust volume for, select Recording.

14. In the Show the following volume controls list, select Line In. (Other controls may also be selected.)

15. Click OK. The Recording Control window shown in the following figure appears.

Note The columns displayed in the Recording Control window will

vary, depending on your operating system and the controls that have been selected for display.


85

16. Mark the Select checkbox under Line In. (All other controls will be unselected.)

17. Close the Recording Control window.

18. In the Sounds and Audio Devices Properties window, click OK.

Software Installation

The following procedure describes how to install Integrator IRR software for Acom systems, including how to disable the UMS requirement for Integrator IRR.

If you ever need to restore the requirement for UMS on the console computer, a procedure for this purpose is provided in the Integrator Instant Recall Recorder Product manual, part number 025-9496.

Installation procedure:

1. Insert the Acom Software Installation CD into the CD drive. The CD should auto run and display a menu of items for installation. If auto run is disabled, run setup.exe from the CD.

2. Click Integrator IRR. If you are prompted with a UMS Required window, press OK.

3. Click Next or Accept at each window to complete the install.

4. When prompted to view the Readme file, uncheck the box and click Finish.

5. Open the Integrator IRR folder on the Acom Software Installation CD.

6. Run Disable UMS for IRR.reg. This changes a Registry setting that allows Integrator IRR to run without UMS.

Licensing Integrator IRR for an Acom Console

After installing Integrator IRR, copy the “.lic” file provided by Zetron into the folder:

C:\Program Files\Zetron\Licenses

If you do not have a license file yet, contact Zetron Technical Support.

Sound Card Selection

A sound card should be selected before configuring audio settings and record control. Although it is possible to select a different sound card later, changing the sound card selection will require that the audio settings and record control settings be adjusted again.


86 025-9619A

Note When Integrator IRR was originally released, it was installed

exclusively with after-market sound cards. As the software has evolved, it now supports most sound cards, or the use of sound capability built into the motherboard. This makes it very important that the proper sound card be identified in the following procedure.

Selecting the sound card:

1. Start the Integrator IRR application.

2. From the Integrator IRR menu bar, select Edit, Options.

3. On the Options screen, click the Sound Card tab.

4. Select the sound card from the Sound Playback and Sound Recording lists. If you have more than one sound card (or the motherboard has onboard sound card capability), select the sound card connected to the Integrator IRR Interface Module.

5. Click OK.

6. Click File, Exit.

7. Restart Integrator IRR.

Notes about Specific Computer Models

Currently, many newer computers have their sound card capability built right in to the motherboard. The motherboard sound card capability is used with Integrator IRR.

In some cases, the Line In and Mic inputs share the same physical jack and you must select in software which class of input is actually connected to the jack. As long as the hardware stays connected to the audio connections, the computer can be turned on and off any number of times without changing the settings. However, if the cabling to the motherboard audio jacks is not connected when the computer is turned on, the computer will do two things:


87

• It will default the setting for the audio in jack back to being a microphone input.

• The next time it senses any hardware connected to the audio input, the computer will request that you select the type of input (line audio or mic) again.

Note Do NOT check the box for “Don’t detect new audio devices in the

future.” Doing so does not prevent the computer from resetting the audio input to default if it finds it empty on power-up. It merely prevents the computer from prompting you to make a selection the next time you connect something to the audio input jack.

To avoid running into this problem, never turn on the computer running Integrator IRR without having connected the interface cable to the audio connectors.

If you do run into this problem, simply open the list in the dialog box and select “Line-In Device”, as shown in the figure here. Alternatively, you can make sure that Line In is the selected input under the Recording settings for Windows Sound Settings.

Record Control Configuration

There are three possible versions of recording control: contact closure, VOX sense control, and software control. Since software control is the preferred method, it is the only one described here. If you require information about the other two methods, refer to the Integrator Instant Recall Recorder Product manual, 025-9496.

Before starting the record control configuration procedure, make sure that the audio source is properly connected and that you are able to produce representative input (preferably with both a caller and a call taker).


88 025-9619A

Setting record-control to software mode:

1. Start Integrator IRR.

2. From the main window menu bar, select Edit, Options.

3. In the Options dialog box, click the Record Control tab.

4. Select an audio source from the Input Sources list. (These sources are defined on the Audio Settings tab.)

5. Select the Software Control button.

6. Hold Time specifies the period to wait before starting a new recording. Increasing this number can make Integrator IRR more effective with radio-style audio patterns. If multiple stop/start requests are received while recording within this window, Integrator IRR keeps recording using the current message, providing an uninterrupted audio flow. When the time between stop and start requests exceeds the Hold Time specified here, Integrator IRR starts a new recording. Valid range is 1 to 30 seconds, but entering a value of 1 or 2 basically disables the Hold Time, because the minimum resolution attainable is 2 seconds.

7. If the source is a telephone or other device without built-in AGC, we recommend checking the Record with AGC checkbox, so that both sides of the conversation are approximately equal in level. If the audio source has its own, built-in AGC, we recommend clearing this checkbox.

8. Test the volume level by recording a message and playing it back.

a. If playback volume is too low or is distorted, increase Input Gain.

b. If playback volume is too high, it is preferable to use the volume control in the Integrator IRR main window to reduce it.

9. When you have verified positive recording control and have arrived at a satisfactory Input Gain setting, click OK to close the Options screen.

ACOM Configuration

If you are using Integrator IRR with an Acom system, you must also configure IMS ACU and AcomConsole.ini as described in this section.

Configuring for IMS ACU

Procedure:

1. In IMS ACU, right-click the 4W E&M module, and click Acom Definitions. The Channel Definitions window appears.

2. Select Port 1. The Channel Definition Details window appears.

3. For Connection Type select Voice Logger.

4. On the Connection Data tab, for Interface select IRR (Instant Recall Recorder).

5. For Console Number select the appropriate number from the drop-down list.


89

6. Select the logger Interface: IRR to enable the short-term logger, or the Long Term Logger option.

7. In the Logger Sources column, select the audio sources that you want the logger to record.

8. Click Save.

9. Click Exit on the Channel Definitions window.

10. Right-click the 4W E&M module again, and click Signaling Inversion. The Signaling Inversion window appears.

11. Select the checkbox for Channel 1, M1.

12. Click Save.

13. Right-click the 4W E&M module again, and click Gain Setting. The Set Gains window appears.

14. For Channel 1, in the Gain TX field type “6.0”.

15. Click Save.

16. On the File menu, select Update to NVRam.

17. On the Tools menu, select Reset Rack.

18. Close IMS ACU.


90 025-9619A

Configuring ACS

The following file is the configuration file that Acom Console Software reads on startup:

C:\Program Files\Zetron\AcomConsole\AcomConsole.ini

It can be edited with a text editor such as Notepad to configure specific features in Acom Console Software. (Some of these features can also be changed from within the program.)

The following list of entries from the AcomConsole.ini file only covers those entries that are related to configuring Integrator IRR. For a full description of AcomConsole.ini entries, see the Acom Software Installation and Configuration (part number 025-9529).

To configure AcomConsole.ini for Integrator IRR, configure the following entries appropriately:

EnableIRR

This parameter specifies whether the Integrator Instant Recall Recorder application should be accessible from Acom Console Software.

EnableIRR=True IRR is enabled.

EnableIRR=False IRR is disabled. Default.

If Integrator IRR is enabled, but UMS is disabled, it is also necessary to execute the .reg file that is in the Integrator IRR folder on the distribution CD.

EnableIRRSoftwareControl

This parameter specifies whether Integrator IRR is to use software-controlled recording. If not enabled, Acom Console Software will expect recording to be controlled by way of contact closure or VOX.

EnableIRRSoftwareControl=True Instructs Integrator IRR to use software controlled recording.

EnableIRRSoftwareControl=False Software-controlled recording is disabled. Default.

This entry is only valid if EnableIRR is set to True.

IRRChannelAlias

Specifies the Integrator IRR audio channel to use during software-controlled recording. Text must match the Source Alias defined in Integrator IRR for the recording channel to


91

be used. Setting this value to “acom” in both the AcomConsole.ini file and Source Alias in Integrator IRR is recommended. For example:

IRRChannelAlias=acom

This entry is only valid if both EnableIRR and EnableIRRSoftwareControl are set to True.

IRRHoldTime

Specifies the interval of time to keep Integrator IRR recording once a Stop Record request has been issued by Acom Console Software to Integrator IRR. Use of this parameter can reduce the number of starts and stops, because if a Start Record request is issued during this time, Integrator IRR will simply continue recording. The time is set in milliseconds. Specifies a numeric string that indicates the prefix for the Tetra ID of the console. Range is 1-to-60000. Default is 3000 (3 seconds). For example:

IRRHoldTime=3000


92 025-9619A

Speed Dials

93

Editing Predefined Dialing Information

Speed Dials

Speed Dial buttons are used to dial over telephone lines, make 5/6-tone Selcal pages over the radio, or to make AVCall2+2 Selcal pages over the radio.

Speed dial buttons may be defined completely in Acom Console Designer, or they may be defined in XML files, or a combination of these two techniques may be used. Typically they reside on a sub form, which is populated by one XML file, but there might be an XML file for a single speed dial button. Many speed dial XML files may be implemented.

Regardless of where and how the speed dial XML files will be used, they must all have the same internal format. That format is shown in the preceding figures.

Caution! While editing Speed Dials, you should edit only the values for dialString, lines, and caption. Leave any other editing tasks for a Maintenance Technician.


94 025-9619A

Dial Strings

A dial string (the value for the dialString attribute) may be one of three types:

• It may be a complete dial string, such as for dialing an external phone number or for transferring a call to a specific console number.

When used with a telephone line, the dial string may be from 1-20 characters long. It can contain the characters 0 to 9, A through D, #, *, -, T (tone), P (2 second pause), Z (ISDN dial termination), a comma (0.5 second pause), or a space.

For example: 9,1-425-555-1212pp#123

• It may be a pre-dial string, such as for getting an outside line and pausing for dial tone. The rest of the dial string must then be entered, perhaps by way of a Dial Pad or possibly by another speed dial button.

• It may be a post-dial string, such as for entering expected voice menu option numbers or an access code. This assumes that a line is already selected and a call is already in progress.

Lines

The value for the lines attribute indicates how the speed dial button should select a line to use to dial the dial string on. It can be in any one of the following formats:

• If the call must be made on a specific line, enter the line number. Example: 101

• If the call may be made on any line within a certain group, enter the range of numbers, separated by commas or hyphens. Example: 1,3,5,10-20

• If the call may be made on any line that is in Selected state within a certain group, enclose the range in parentheses and precede with an s. Example: s(1-10)

• A set of lines can be given a name in the AcomConsole.ini [Line Groups] section, and then the name can be used here. Line Groups may also be defined in the Acom Profile Management tool. Hunt groups are now implemented by way of Line Group names. Example: HG1

If there is no available line in the specified lines or group, the function will go Active and the operator will need to select a line manually.

Contact Lists

95

Caption

The value for the caption attribute is the label that will appear on the speed dial button. To force a line break within the caption, insert a tilde (~) where you want the new line to begin.

Contact Lists

The XML file that populates a contact list must be of the same format as that for speed dial buttons. You could even use the exact same file. This is a good case of how different media can use the same XML file for different purposes. In a contact list, the Name column in the panel is populated by the attribute caption, the Number column by dialString.

Note If an entry does not include a caption or does not include a

dialString, it will not be displayed in the contact list.

Alpha Search Lists

The format of XML files that are used to populate alpha search lists is shown in the figures on the next page. You can edit the values for any of the attributes: name, description, and number. The description field is unlabeled on the form. It appears just below the list pane. The resulting list as displayed in the Alpha Search form is shown in the following figure.


96 025-9619A

Alpha Search Lists

97


98 025-9619A

Backing Up a Device Configuration

99

Backup/Restoring Configurations and Upgrading Firmware

This chapter covers how to backup and restore equipment configurations as well as how to upgrade the firmware installed in various cards. Be aware that the procedures for each operation can and do vary depending on the hardware being worked on.


Equipment Required

• Zetron PC to Acom Console Unit cable: 709-7615-xxx (xxx = cable length), for use with DCU cards only

• Zetron straight-through RS232 serial cable (part number 709-7345), for use with ALS cards only

• PC/Laptop equipped with Windows, a terminal program capable of serial communication, and a DB9 RS232 Serial Com Port

• IMS ADS and/or IMS ALS software (installation setup for this software is located on the Acom Install CD)

• The network address of the ADS or ALS housing the card having its configuration backed up


100 025-9619A

ADS/DCU Configuration Backup

To save the DCU configuration to a backup file:

1. If this is a standalone ADS, skip to Step 2. If this ADS is part of a redundant setup with two or more ADS units, then continue with the following sub-steps:

a. In order to successfully remove a DCU card with little disturbance to the system, ensure that there are no E1 links resources active between the ADS and an ALS. This can be verified by viewing the second row of green LEDs on each MCU4 card in the ADS (LEDs A2 and B2 in Figure 9).

Figure 9: LED Indicators on an MCU4 Card

b. If these LEDs are NOT solid green, there is no active E1 link on this ADS and you can skip to Step 2.

c. If either of these two LEDs ARE lit solid green, there is a link from this ADS to either a Acom Console Unit (ACU) or an ALS. To determine which, consult your system’s network diagram or follow the cables.

If the link is to a Acom Console Unit (ACU), you can skip to Step 2.

If the link is to an ALS, you must first ensure all ALS E1 links are switched active to another ADS.

2. Connect the 709-7615-xxx cable from the PC to the left RJ45 connector on the bottom of the DCU card.

3. Start the IMS ADS program.

If you do not have IMS ADS loaded on your PC, install it from the Acom Install CD.

4. Select the Communications menu, click Settings, and verify that the baud rate is 38400 and the Com Port matches the one being used on the PC. Click OK to save settings.

5. Select the Communications menu and click Connect. When prompted for the Network address, enter the ADS Network address and click OK.

(The network address typically appears on a sticker on the ADS and may appear in the “As-Built” documents for your particular system).

Note Make note of the Network address because it will be needed if

you are installing a replacement card.

6. When prompted with the password dialog, click the Default button and it should allow access to the ADS.


101

7. Access the File menu and select Save to Disk. When prompted for the configuration file name, use a descriptive file name. For example: ADS<network address>.bin

Note A Progress Meter window will appear when saving the file to

disk. It may take up to 30 seconds to save the file. When saving the file is complete, the Progress Meter window will disappear.

8. Once the file has been saved, select the Communications menu and select Disconnect.

Note The DCU card holds the configuration for the ADS.

9. Close the IMS ADS program.

ALS/MCU Configuration Backup

If an MCU card is installed in slot 0 of an ALS, it is considered the primary MCU; it holds the configuration for the subrack and controls all rack messaging.

To backup the MCU/ALS configuration:

1. Connect the serial com port of the laptop to port 1 of the MCU card. (Port 1 of the MCU card is the top 9-pin serial connector on the front of the MCU card, labeled X17 on the PCB.)

2. Launch IMS ALS on the laptop.

3. From the main menu, select Communications then Connect.

4. When prompted, enter the Network Address of the subrack, and click OK. (The network address typically appears on a sticker on the subrack and may appear in the "As-Built" documents for your system.)

5. At the password screen click the default button.

6. If this ALS is part of a Main-Standby setup, force control to the other ALS:

a. From the Tools menu in IMS Terminal, select Change Over.

b. Select the Manual option and select the other ALS.

c. Verify the ALS icon in IMS turns light blue to show that the other ALS is in control.

d. Once the other ALS has taken control, select the Automatic option and exit the Change Over menu.

7. Once connected choose File then Save to Disk. Save the file with a descriptive name, for example: ADS<network address>.cfg


102 025-9619A


disk. It can take several minutes to completely save the file. When the file has been saved, the Progress Meter window will close.

8. Choose Configure, then Subrack Address, and then write down the subrack address. Also note if this is the Main or Standby ALS.

9. Select the Communications menu then Disconnect to disconnect from the ALS.

Restoring a Device Configuration

ADS/DCU Configuration Restore

To restore ADS configuration:

1. Launch IMS ADS on the PC. Select Communications then Connect. Enter the network address of 1 when prompted, click OK.

If using a network address of 1 does not allow you access to the MCU, try using 0 or 255.

2. At password screen click default.

3. Click File, Load From Disk, and select the file name that was saved earlier (see To save the DCU configuration: on page 71).

4. Click File, Update to rack.

5. When prompted for the network address, use the address that provided access in Step 1.

6. When prompted for the Configuration name, use the one supplied, which should be the name of the DCU that was replaced.

7. Access the Configure menu and select Set Address. Enter the Network Address recorded earlier in To save the DCU configuration on page 257.


9. To finalize the changes, click Tools, then Reset Rack from the IMS menu.

10. When the DCU is back up and running (top right LED on DCU card is blinking slowly) proceed to the following section.

Restoring a Device Configuration

103

ALS/MCU Configuration Restore

To restore the ALS configuration: (only if replacing MCU in slot 0)

1. On the laptop, launch IMS ALS.

2. Open the Communications menu and select Connect.

3. Enter the network address of 1 when prompted, and click OK.


4. At the password screen, click default.

5. Click File, then Load From Disk and choose the file name that was saved (see ALS/MCU Configuration Backup on page 101.

6. Select File, then Update To Rack to transfer the new file to the ALS.

7. When prompted for the network address, use the one that worked correctly in Step 3.

8. When prompted for the configuration name, use the one supplied, which should be the name of the MCU that was replaced.

9. Click Tools, then Reset Rack from the IMS menu to finalize the changes.

10. Click File, Update To Rack.

11. When the rack is back up and running (top right LED on MCU card is blinking slowly), reconnect and verify the network and subrack addresses.

12. Select Configure, then Subrack Address.

Set the subrack address to the value recorded when the backup file was made (see ALS/MCU Configuration Backup on page 101), then click Save.

13. Click Configure, then Network Address.

Set the network address to the same value recorded when the file was made (see ALS/MCU Configuration Backup on page 101), then click Save.

14. Power down the rack and reconnect the SMB cables to the MCU.

15. Power up the rack.

Within a minute or two, the rack should be operating normally. Only the top right green LED on the MCU should be flashing and on if everything is normal.


104 025-9619A

Performing a Firmware Update

DCU Firmware Update

The firmware version of the card should be checked prior performing an update to confirm that it is what you think it is.

To record the DCU firmware version:

1. Open a terminal program capable of serial communication.

2. Open a terminal connection using the COM port connected to the DCU. The COM port should be configured for the following settings:

Bits per second = 38400 (default for an DCU) Data bits = 8 Parity = None Stop bits = 1 Flow Control = None

3. Press Esc on your keyboard until you see a “Password:” prompt. It should only take three presses. If you do not get the “Password:” prompt, check the COM port and its settings.

4. When the Password prompt appears, type “8564888” and press Enter.

5. A menu should appear with some selections. Press 1, and then Enter.

6. Once logged in, type ver and press Enter. Record the results for Release and Library.

7. To exit debug mode, press Esc, then X.

Note The following procedure assumes two things.

1) You have verified the firmware version of the card you are about to update 2) You have received a copy of the firmware file from Zetron it will be named something like: Ds3<version>.compressed

The following procedure is an alternate method for updating the firmware in a DCU card using the FTP protocol. Before you perform it, you must uncompress the file you received from Zetron and rename the uncompressed file dcu.binary.


105

Updating the DCU firmware (FTP method):

1. Place the DCU firmware file in a location on the IMS console computer where you can easily find it and FTP it to the DCU. The firmware file must be uncompressed and it must be named “dcu.binary”.

Warning! Sending a Compressed file or using the wrong file may

result in an inoperable DCU.

2. At a Windows Command Prompt, navigate to the location of the firmware file.

3. Use the following command to FTP to the DCU where [IP Address] is the IP address of the DCU: > FTP [IP Address]

4. Press Enter for the user name (none).

5. Type the password (default is 8564888).

6. Select binary mode: FTP> binary

Warning! Failure to use binary mode will cause FTP to send a corrupt

file to the DCU card firmware. This may result in an inoperable DCU.

7. Upload the firmware file: FTP> put dcu.binary (This may take a few minutes.)

8. When the FTP prompt returns, check the directory for file errors: FTP> dir If there are file errors in the directory, the firmware update has failed. Press the reset button on the DCU.

9. Exit FTP. FTP> quit

10. Press the reset button on the DCU.

11. The resetting DCU will put on an LED “lightshow” while booting up. The status LEDs will return to normal in a minute or two.


106 025-9619A

ALS Firmware Update

The procedures offered here apply to updating the firmware on MCU cards used as the primary card (slot 0) in an ALS subrack. You should not start this procedure until you have received a compressed MCU3 firmware update file from Zetron. The supplied file will have a name similar to “ALS_100.zip”.

Note The sub rack will not function while updating the firmware on a

Primary MCU card.

To verify firmware version and update the MCU card:


2. Open a terminal connection using the COM port connected to the MCU. The COM port should be configured for the following settings:

Bits per second = 38400 (default for an MCU) Data bits = 8 Parity = None Stop bits = 1 Flow Control = None


4. When the Password prompt appears, type the password (default 8564888) and press Enter.

5. Once logged in, type ver and press Enter.

Note If the firmware version currently installed in the card is the same

as that of the file you intend to install, then skip the remaining steps in this procedure and exit from the card.

6. At the prompt, type Download and press Enter. This command will cause the MCU to prompt for a Xmodem transfer by sending a “C” character repeatedly.

7. Using your terminal program, send the compressed firmware file using the 1K xmodem protocol.

Warning! Choosing the incorrect file or file transfer protocol may

result in a dead MCU card. The only way to recover a dead MCU card is to send it to Zetron for repair.


107

Note The MCU supports the compressed file format. After the

compressed file has been transferred, the MCU will CRC check the compressed file, uncompress it, and update to flash. It is recommended that you keep the firmware update in the compressed file and do not uncompress it before transferring to the MCU. This will minimize the transfer time and protect the bin file with the CRC checking provided by the compressed format.

8. After the MCU has reset itself and appears to be operating again, press Esc three times to get another “Password” prompt.

9. Type ver and note the results.

ADS/MCU4 Firmware Update

The procedure presented here only applies to an MCU4 card installed in an ADS subrack.

To verify MCU4/ADS is not active:

1. If this is a standalone ADS, skip to the procedure for verifying the firmware version.

If this ADS is part of a redundant setup with two or more ADS units, then continue.

2. Make sure no E1 links are active on the ADS. This can be verified by viewing the second row of green LEDs (right below the top right flashing green LED) on each MCU4 card in the ADS. For a diagram of MCU LEDs, see Figure 10.

If any of these LEDs are lit solid, there is either a link to a Acom Console Unit/ACU or an active link to an ALS. Consult the system Network Diagram or follow the cables and make sure it is NOT an active E1 link to an ALS.

If there are no active E1 links to an ALS, skip to the firmware version procedure. If there are active links to an ALS, make sure that all ALS E1 links are switched active to the other ADS:

a. At the IMS console, launch IMS Terminal, and login.

b. Double click the ALS. From the Tools menu, select Change Over, select the Manual option, and select the ALS NOT in control.

c. Verify that the icon in IMS turns blue for the other ALS.

d. Select the Automatic option and exit the Change Over menu.

Figure 10: MCU4 Status Indicators for ADS


108 025-9619A

To determine/record the firmware version:



Bits per second = 38400 (default for a MCU) Data bits = 8 Parity = None Stop bits = 1 Flow Control = None


4. When the Password prompt appears, enter 8564888 and press Enter.

5. A menu should appear with some selections. Enter 1 and press Enter.

6. Once logged in, type ver and press Enter.

7. Record the results for Release and Library.

8. Press the Esc key then press X to exit debug.

Before proceeding with the update, you must obtain a copy of the firmware from Zetron. The file name will be something similar to MCU4<version>.zip. If you do not have this file, contact Zetron before going any farther.

To update the MCU4 card firmware:





4. When the Password prompt appears, enter “8564888” and press Enter.

5. A menu should appear with some selections. Enter 1 then press Enter.

6. At the MCUX> prompt, type download. The download process will begin.


Distributing Updated Console Configuration Files

109


result in a dead MCU4 card. The only way to recover a dead MCU4 card is to send it to Zetron for repair.

Note The MCU4 supports the compressed file format. After the

compressed file has been transferred, the MCU4 will CRC check the compressed file, uncompress it, and update to flash.

8. After the file has been transferred, the MCU4 will flash the file to memory then reset. This will take about 60 seconds.

9. After the MCU4 is online, check the firmware version to verify that the uploaded firmware is now active.


This chapter describes the Zetron File Distributor application (ZFD). ZFD enables you to distribute necessary configuration files to PCs being used as Acom consoles.

ZFD will be installed on a maintenance PC so that configuration files and various databases can be maintained centrally and distributed to the consoles when needed. If you need to make any changes to a configuration file or database, do it on the maintenance PC, then distribute the changed file(s) to the appropriate console(s). The maintenance PC and all of the console PCs must be on the same subnet or be using DNS, or all the console names can be defined in an LMHOSTS file.

When ZFD is running and instructed to Copy Files, it looks in a specified directory on the PC it is running on for a specified list of files and copies those files into a specified destination directory on each of the console PCs it was told to update. This mode of operation dictates certain requirements for setting up and using ZFD.

• While ZFD does not need to be installed on a console PC (in fact, it should not be), it does need to be installed on a PC that can reach each console PC by way of the network, using the network name of each console.

• The path to the target directory must be the same on each console PC. To reach the target directory on each machine, ZFD combines the computer name (the name by which it is known to Windows) of the console PC with the path string recorded in the configuration file.

• The target directory on each console PC must have the sharing attribute enabled under Properties. This is necessary to allow ZFD to write files to, and delete files from the target folder on each of the console PCs.


110 025-9619A

Installation

The ZFD is a freestanding executable that can be run without having to be installed in the commonly understood sense of the term (it does not need to alter the OS Registry). However, it does have some requirements of the machine it is running on and it does require access to several companion files to perform its duties, so it cannot just be copied to the desktop either.

Requirements

• ZFD requires that the computer have Microsoft .NET Framework (.NET) installed on it. An installer for this purpose is included in the Acom distribution. It is named dotnetfx_2.0.exe

• If prompted to install or update the Windows Installer utility prior to installing .NET, do so. The installer is named WindowsInstaller-KB893803-v2-x86.exe

• ZFD expects to find all of the files that will be used to update console computers in the same folder. You can create this folder and populate it with the files prior to installing ZFD and then just point out the path to the folder the first time you run ZFD. ZFD will only notice the files it has been instructed to look for.

• You should create a folder in which to install ZFD. You can use an existing folder if you wish; however, creating a dedicated folder makes the files easier to find and keep track of.

• All consoles must have the same logon name and password configured as the computer running ZFD.

Preliminary Steps

Preparing to install Zetron File Distributor:

1. Create a folder to act as the source path for ZFD to copy files from. A suggested path is: C:\Program Files\Zetron\Working Config\AcomConsole

2. Create a folder to hold the ZFD executable and its companion data files. A suggested path is: C:\Program Files\Zetron\FileDistributor

3. On each of the console PCs, you need to share the path C:\Program Files\Zetron so that ZFD will be able to write to its subfolders over the network. To do so, do the following on each console PC:

a. Right-click the Zetron folder and select Sharing and Security.

b. Select Share this folder.

c. In the Share name field, type Zetron.

d. Under User limit, select Maximum allowed.


111

e. Click Permissions.

f. Add the user who will be running ZFD.

Installing

Installing ZFD:

1. Place the software distribution disk in the appropriate drive on the PC that is to run ZFD.

2. Open the folder on the distribution disk that contains the ZFD files.

3. Run the WindowsInstaller-KB884016-v2-x86.exe file to install .NET.

4. Copy the files FileDistributor.exe and FileDistributor.xml from the distribution disk into the folder you prepared for ZFD.

5. Copy the current version of the console .ini file and .dfm files into the ~\Zetron\Working Config\AcomConsole folder you prepared earlier for the working directory files. (You can and will add to this later, but these two files will provide something to confirm that ZFD is looking in the correct folder.)

6. Create a shortcut on the PC desktop that points to the FileDistributor.exe file.

Initial Startup

The default FileDistributor.xml file will point to the folder locations suggested in this manual but it will not contain the names of any of the console PCs on your system. The first time you run the program the Main window will open so that the consoles can be defined. The following procedure will lead you through setting the paths used by ZFD and the console names for the first time.

Setting ZFD parameters during the first start up:

1. Use the desktop shortcut to start ZFD. Alternatively, open the Start menu and use the RUN command to start the program. If you used the suggested paths when installing the program, the entry in the RUN command will be: C:\Program Files\Zetron\File_Distributor\FileDistributor.exe

2. Click the Add Consoles button in the upper right corner of the Main window. The Select Consoles window opens.

3. Use the options provided in the Select Consoles window to populate the list of consoles to be supported by this installation of ZFD. If you know the names of the console PCs you can type them into the field at the top of the window one-at-a-time and click the Add button. ZFD will ping that name on the network and if it fails will display a message to confirm if the console is to be added. If the console is added, the name is appended to the list on the right. You can also use the tools in the lower left to search the network for PC names and then add names from that list to the list on the right.


112 025-9619A

4. Save the changes to the consoles list and close the Select Consoles window by clicking the Save button. The new consoles will now appear in the Selected Consoles column on the far right of the Main window.

5. If the recommended Source Path was used then no change is required otherwise use the Browse button to navigate to the folder that contains the source files.

6. If the recommended Destination Path was used then no change is required otherwise use the Browse button to navigate to the required path. Note that if the Maintenance computer does not have ACS installed on it, it will not have the required folder and you will need to type the path into the field.

Note For ZFD to do its job correctly, the path to the destination folder

must be the same on every console PC in the system.

7. The One Button Config will be the default configuration selected on the Main window. Verify the Selected Files and Selected Consoles are correct for the One Button window to use. If not select those required and click the Save button to save the changes.


113

The User Interface

This section describes the four major screens found in ZFD, and the parameters found on each screen.

One Button Window

If ZFD has been initialized properly and no command line options have been added to the shortcut used to start it, the software will open the One Button window. If the software cannot find the FileDistributor.xml file, or there are no consoles defined in the FileDistributor.xml file, then the program opens the Main window.

The One Button window can also be opened by clicking on the button for that purpose located in the lower left corner of the Main window.

The upper half of the One Button window contains a single button labeled Send Files to All Consoles. Clicking on this button causes ZFD to execute the configuration called One Button Config as it is currently programmed. By default the One Button Config sends all of the files in the Source Path to all of the console PCs that ZFD has on file. From the Main window, you can alter the One Button Config to include only certain consoles or some subset of all files if you wish to do so.

The bottom half of the One Button window contains a list and a button labeled Send Files to Selected Console. You may select an individual console from the list of consoles covered by the One Button Config and then click the button to send all of the files covered by that configuration to that single computer.

When either button is clicked, the program starts copying the files, and the progress of the copy operation is displayed.

This window allows people unfamiliar with the details of the system to refresh the Acom console configuration files on console computers.


114 025-9619A

Main Window

The Main window is used by those personnel that setup and maintain the Acom console system. This window displays the consoles to which ZFD can copy files, the files it has to copy, the important paths for locating files and where to copy them to, and the controls necessary for editing the One Button Config or creating additional configurations.

The Main window can also be used to manually copy selected files to individual machines when the need arises.

Note The selection methods available in any of the lists in the Main

window are the standard selection methods found in Windows-based software. To select a single item, click on it. To select multiple random items, hold down the Control (Ctrl) key and click on them. To select a contiguous block, click the first item, hold down a Shift key, and click the last item. The first item, last item, and all of the items in between the two are selected.


115

Main Controls

The column on the left side of the Main window contains a number of controls.

Copy Files

Clicking on this button will copy the currently selected files to the currently selected consoles. If there are no files or consoles selected (at least one of each is required), either manually or by selecting a Configuration, ZFD will respond by prompting to finish selecting them. Then the progress of the copy operation will be displayed.

Saved Configurations

The saved configurations allow you to set up a predefined list of consoles and a list files to be copied to them. ZFD comes with one configuration set up by default: One Button Config. Until or unless you modify it, it is set up to copy all of the files in the Source Path to all of the consoles listed by ZFD.

You can create new configuration files or edit existing ones. For the procedure on creating a configuration file, see Creating Configurations on page 122.

To select an existing configuration, click the name in the displayed list. To delete a configuration, select it and then click on the Delete button.

Delete All Files

ZFD copies files to each of the console PCs in the system one-at-a-time. Checking this box causes the program to delete any files it finds in the destination directory on a console PC before it copies the new files from the Source Path on the PC running ZFD. This is used if test or temporary files had been distributed to the consoles which must be cleaned up before going live. Note that this option deletes all files so the copy will replace all the necessary file, including *.exe, *.dll, and so on.

Open One Button Window

Clicking this button opens the One Button window. See One Button Window on page 113.

Open Simple Window

Clicking this button opens the Simple window. See Simple Window on page 117.

Selected Files List

The center area of the Main window is made up of three lists that are related in function. The main list shows the files and folders found in the directory shown in the Source Path field shown at the bottom. This list can be sort by name or date, ascending or descending


116 025-9619A

by clicking on the column heading. The top left list shows the File Types that can be used to select the files. For example if you click the *.dfm file type then all ACS form files will be selected. Note that if you unselect a file that was selected by way of the file type then the file type will also be unselected because it no longer selects all files of that type. Under the File Type list is a list of Excluded File Types. When these Excluded File Types are selected then all files of this type are removed from the File list to make it easier to see only the file required to be distributed. For example when make a change to an ACS form file a backup copy is made with a .bak extension, which is not required to be copied.

Above these lists is four buttons used to aid unselecting/selecting files from the lists below.

The Unselect button on the far left is used to clear any existing selections in the list of File Types under it.

The Select All button selects all the files and folders listed below it.

The Refresh button forces ZFD to read the file names found in the Source Path again and to update the list.

The Unselect All button is used to clear any existing selections listed below it.

Under the lists is the Source Path field. This directory holds all of the files that can be copied by ZFD on to console PCs in the system. Clicking on the Browse button under it opens a browser dialog to allow you establish the correct path by navigating to the correct folder. Note that you can all open any folders shown in the File list by double clicking on them. The Back button takes the Source Path up one folder.

Selected Consoles List

This pane is on the far right of the Main window. The list displayed here is all of the console computers that ZFD is aware of. The names can be selected individually. Clicking on the Select All button at the top of the pane selects the entire list at once. Clicking on the Unselect All button clears the selection for any console names that are currently selected.

Clicking on the Add Consoles button at the top of the pane opens the Console Selection window. It is from this window that you can add new/delete console names to the list and add a description to each Console name.

Destination Path

Under the Consoles list is the Destination Path. The parameter field is used to specify the remainder of the path to the destination folder on the console computers. ZFD takes the console name provided and adds the string found in this field to come up with the full path from the machine running ZFD to the console folder to which it is copying the files. This means that the path must be the same on all of the console computers.


117

This parameter can be entered by just typing the path into the field, if you know what it is. You can also click on the Browse button under it and navigate to the correct folder on one of the maintenance computers to establish the path if it is setup the same as a Console computer.

Clicking on the Restore button will change the path to the default value of: Zetron\AcomConsoles

This default path is the one recommended in this manual when the Zetron folder is shared on each Console computer.

Simple Window

The Simple window is the same as the main window but with all the buttons and options removed. This can be used by customers that want to use more than the one configuration provided by the One Button window. The Selected Files and Selected Consoles can only be changed by clicking on a different configuration name. When a configuration name is clicked the selected files and consoles are sorted to the top of the lists.


118 025-9619A

Select Consoles Window

Clicking on the Add Consoles button at the top of the Consoles List opens this window.

Manual Entry

If you already know the computer name for the PCs you wish to add to the list, you can simply type them one-at-a-time into the field in the upper-left of the Select Consoles window and click the Add button.

To obtain the list of computer names, go to each machine and use the following procedure. This example is based on a machine running Windows XP; however, it should be similar enough to machines running Windows Vista to be useful.

Finding out a computer name:

1. Go to the computer you wish to find out the name of and click the Start button.

2. From the Start menu, click the Control Panel option.

3. Scroll down the Control Panel list and double-click on the System option.

4. In the System Properties dialog that opens, click on the Computer Name tab.


119

5. On the Computer name tab, locate the two lines Full computer name: and Domain:. Subtract the entry found under Domain: from the Full Computer name: entry to arrive at the computer name that ZFD is looking for.

For the example dialog shown here, you would subtract zetron.com from TP-BKIRK.zetron.com to end up with a computer name of TP-BKIRK.

Let the Computer Find the Consoles

In many systems, the console computers will be dedicated machines that were purchased and configured specifically to be used at console positions. In cases like this, the computers will have been given names during their set up that follow some sort of logical/sequential convention. An example would be a three-position system with console computers named POS-1, POS-2, and POS-3 for positions 1, 2, and 3. If this is true, then you can use the options found in the lower-left portion of the Select Consoles dialog to instruct the computer running ZFD to search the portion of the network accessible to it for computers that have names which fall within the parameters entered.

Console Prefix

This field is for the non-numeric portion of the console names. ZFD does not allow for any wild-card character in between this string and the sequential number portion of the console names. This means that this string must be complete and identical for each of the console computers. The only character that can differ in their names is the number at the very end.

Maximum Number

This field sets the maximum console number that ZFD will search for. For example, if it is set to 10 and there are computers on the network with the correct prefix but their name ends in a number higher than 10, they will not be displayed on the Available Consoles list.

Verify Network Connection

If this check box is selected, ZFD will attempt to ping each console as it works its way through the list of possible combinations defined by Console Prefix and Maximum Number. If there is no response to its ping, ZFD will prompt you to choose whether to add that console name to the list of available consoles. This way, if there are gaps in the


120 025-9619A

consoles available on the system, you do not end up with your list cluttered with useless machine names.

List the Consoles

Clicking this button causes ZFD to carry out the PC name search defined by the Console Prefix, Maximum Number, and Verify Network Connection parameters. If the Verify Network Connection check box is selected, names will be added to the Available Consoles list as their presence on the network is confirmed. If the ping attempt to a particular name fails, ZFD will notify you of this fact and ask if you want to add the name in question to the Available Consoles list anyway.

Search for Consoles

This button allows you to take a different approach to compiling a list of console PCs; one that can be very helpful in systems where the console PC names do not follow any uniform convention.

When you click on the Search for Consoles button, ZFD goes out and tries to ping all of the computers it can access on its portion of the network and it displays the PC names of all of the successful attempts in the Available Consoles list.

All, >>, and << Buttons

The three buttons that appear in the space between the Available Consoles list and the Selected Consoles list are used to move computer names from one list to the other.

Clicking the All button will move all of the PC names on the Available Consoles list to the Selected Consoles list in one operation.

Clicking the >> button will move whichever PC names are currently selected on the Available Consoles list to the Selected Consoles list.

Clicking the << button will move whichever names are currently selected on the Selected Consoles list to the Available Consoles list.

The computer names can also be moved between lists by the normal drag-and-drop operation.

Sort the Consoles

Clicking the Sort Consoles button causes the Selected Consoles list to be sorted alphabetically by the PC names.

Add Description

This button is used to add a brief description next to an individual console PC name. This feature is used to make it easier for technicians to tell which PC is being referred to when the console PC name does not really provide enough information by itself.


121

To use this feature, you would select a name from the Selected Consoles list, type a brief description in the Description field, and click the Add Description button. Descriptions can be edited or removed simply by repeating this procedure.

Save

When the computer names in the Selected Consoles list is complete click the Save button to save the changes and close the window. Any names shown on the Available Consoles list are lost. Only those names that have been moved to the Selected Consoles list are retained.

Using ZFD

For detailed information about setting up and configuring the Zetron file Distributor, please see the Acom Software Installation and Configuration manual (part number 025-9529). The material the follows covers using ZFD once it is installed.

Editing the Selected Consoles List

To use the procedures described here it is important that you know the name assigned to each of the console computers in your network. If you are uncertain of what they are, use the procedure described under Finding out a computer name: on page 118 to find out.

Adding one or two PCs to the Select Consoles list:

1. Start ZFD with the command-line options to open the Main window.

2. Click the Add Consoles button in the lower left corner to open the Select Consoles window.

3. Type the new console names into the field at the top of the Select Consoles window one-at-a-time and click on the Add button next to the field.

Adding a large number of consoles to the Select Consoles list:


2. Click the Add Consoles button in the lower left corner to open the Select Consoles window.

3. Use the search tools on the lower left of the Select Consoles window to populate the Available Consoles list.

4. Select the names you wish to add from the Available Consoles list and use the >> button to move the names to the Selected Consoles list.

5. If you wish to add a description to any of the new names:

a. Select that name in the Selected Consoles list.

b. Type a brief description in the Description field.

c. Click the Add Description button.


122 025-9619A

6. Close the Select Consoles window.

Creating Configurations

While ZFD comes with only one Configuration set up (One Button Config), you can create as many more Configurations as you find to be useful. You may also edit the parameters of the One Button Config if you find the default settings to not be useful.

Creating or editing a Configuration:


2. In the Configuration section of the window (on the left side), select a configuration (or simply type the name in the box if you are creating a new configuration).

3. Verify that the Source Path is correct. If not, click the Browse button under the field and navigate to the folder you have previously set up to hold the files that will be used by console PCs in the Acom system.

4. From the center column of the window, select the files, or the file types, that will be copied to the console PCs under this configuration.

5. From the column on the right side of the window, select the console PCs that will receive files under this configuration.

6. If you have selected some File Types and you always want all of the files of this Type to be selected for this Configuration then tick the Include File Types checkbox. This means, for example, if *.DFM was saved then if further ACS form files are added to the Source Path directory then they will also be selected when this Configuration is used. If the Include File Types option is not used then only the files selected when the Configuration is saved will be used.

7. Click on the Save button to save this information under the name showing in the Configuration Name field.

You may also delete configuration files from the list.

Deleting Configuration files:


2. In the Configuration section of the window (on the left side), select the configuration you want to delete.

3. Click on the Delete button. When ZFD prompts you about whether or not you are serious, answer Yes.

Determine What needs to be Changed

When the Acom console files are distributed to the console computers some files require the console to be restarted before the new files are used by the console and others do not require any action. You can use the following table as a guide to adjust the configuration.


123

What has changed? What needs to be sent? How to activate the changes.

Console form file Form files (*.dfm) Reload configuration file, or log off/on.

Console initialization setting(s) AcomConsole.ini Reload configuration file, or log off/on.

Console Speed-Dial XML files Example: Speed-Dial.xml A console log off or “Refresh” in the browser window will be required.

Alpha Search XML file alphasearch.xml No action necessary.

Memory Dials XML files Example: MemoryDials.xml A console log off or “Refresh” in the browser window will be required.

Console sound files *.wav In use .wav files referenced in AcomConsole.ini cannot be updated while ACS is running. Exit to Windows, send *.wav, then restart ACS.

Acom Console Software (update)

AcomConsole.exe Send the new AcomConsole.exe to the ACS_SOFTWARE_UPDATE folder then log off ACS and log on.

Paging Subscriber File AcomPaging.config No action necessary.


124 025-9619A


125

Radio Resources

This section contains information taken from various application notes developed at Zetron covering the management of radio-related line resources in an Acom system.

The following is a quick list of the topics covered and the pages they start on:

Radio Lines 126

Local PTT Radio Control 129

Local BCD Radio Control 132

Tone Remote Control 136

Muting Received Tone Remote Tones 142

Configuring MDC-1200 Signaling 148

Configuring GE-Star Signaling 155

Configuring EnRoute Signaling 163

Configuring Two-tone Paging 171

Channel Set Function Button 179

Instant Monitor Function Button 183

Instant TX Function Button 186

Resource Audio Volume Function Button 188

Marker Tone Button 192

Squelch Disable 196

Radio Resources

126 025-9619A

Radio Lines - RIU Installation

This section provides instructions to install a new Radio Interface Unit (RIU) card to an existing Acom system. Only the most basic configuration of the card is covered here. Each RIU can provide 6 radio line interfaces with analog logging outputs. For the purposes of the instructions presented here, the following assumptions are made:

• The Acom system in question uses a redundant line subrack configuration

• The installed SMU cards can accommodate the new radio lines

• The subrack still has enough E1 timeslots available to service the new card

Required Materials

The specific materials would be determined by Zetron. Just because there is free space in the line subrack does not mean the rack can accept additional cards. The equipment listed here is a generalization.

• 2 x RIU card 950-0838

• 2 x COV-R card 950-0837

• 1 x COV-R to RIU Upper cable 709-0161-fff

• 1 x COV-R to RIU Lower cable 709-0102-fff

• 1 x COV-R to RIU Logger Upper cable 709-7882-fff (one for every 4 RIU cards)

• 1 x COV-R to RIU Logger Lower cable 709-7883-fff (one for every 4 RIU cards)

• 1 x COV to RJ21 cable 709-0146-fff

Zetron will also provide system documentation, card location, and line assignment instructions specific to your system.

Standby Subrack Procedures

Begin with the Standby subrack (rack not in control). The RIU card may be installed while power is applied.

Hardware

Installing RIU hardware in the standby subrack:

1. Install the new RIU card into the designated slot. Zetron will instruct you what slot should be used. The extraction lever will be at the top. Align the bottom card edge with the guide, then the top. Press the card firmly to seat the rear connector.

2. Install a COV-R changeover card in the designated slot of the changeover sub rack. Zetron will instruct you what slot should be used.

Radio Lines - RIU Installation

127

3. Install the provided RIU to COV cable 709-0102-fff between the first new COV-R card lower RJ21 J2 and the corresponding RIU lower RJ21 J2.

4. Install the provided RIU Logger to COV cable 709-7883-fff between the second new COV-R card upper RJ21 J2 and the RIU upper RJ21 J1.

5. Install the provided COV to RJ21 cable 709-0146-fff between the rear COV-R connector J3 and the cabinet’s RJ21 patch panel. Connect your radios to this point. The pinout for this RJ21 is provided in table 1 below.

6. Configure the Standby line subrack before continuing with the Main (in control) subrack.

Software

Configuring the standby subrack software:

1. Connect to the Standby subrack using IMS_ALS and verify the new RIU is recognized. It will appear red because the newly installed card does not match the saved configuration for the rack.

2. From the File menu choose Update to Rack.

3. Accept the popup to save the new card configuration to NVRam. All cards should show a green status when this step is complete.

4. Zetron can link in and complete the needed configuration of the RIU based on your specific use. Otherwise contact Zetron for configuration instructions specific to your use of the RIU card.

5. From the IMS_ALS Tools menu choose Change Over.

6. Select Manual control, and then click the Standby button from Select Active Device. This will force control to the Standby subrack.

7. Move the manual control selection back to Automatic!

8. Close IMS.

Figure 11. RIU Cable Connections for Main and Standby Subracks

Radio Resources

128 025-9619A

Table 13. Pinout for RIU Connector RJ21

Channel Signal Pin Channel Signal Pin TX A 26 TX A 38 TX B 1 TX B 13 RX A 27 RX A 39 RX B 2 RX B 14

E+ 28 E+ 40 E- 3 E- 15

PTT 29 PTT 41

1

PTT 4

4

PTT 16 TX A 30 TX A 42 TX B 5 TX B 17 RX A 31 RX A 43 RX B 6 RX B 18

E+ 32 E+ 44 E- 7 E- 19

PTT 33 PTT 45

2

PTT 8

5

PTT 20 TX A 34 TX A 46 TX B 9 TX B 21 RX A 35 RX A 47 RX B 10 RX B 22

E+ 36 E+ 48 E- 11 E- 23

PTT 37 PTT 49

3

PTT 12

6

PTT 24 None 50 None 25

Main Subrack Procedures

Hardware

Installing the main subrack hardware:

1. Install the new RIU card into the designated slot. Zetron will instruct you what slot should be used.

2. Install the provided RIU to COV Upper cable 709-0161-fff between the first new COV-R card upper RJ21 J1 and the corresponding RIU lower RJ21 J2.

3. Install the provided RIU Logger to COV Upper cable 709-7882-fff between the second new COV-R card upper RJ21 J2 and the RIU upper RJ21 J1.

Local PTT Radio Control

129

Software

Configuring the main subrack software:

1. Connect to the Main subrack using IMS_ALS and verify the new RIU is recognized. It will appear red because the newly installed card does not match the rack’s saved configuration.

2. From the File menu choose Update to Rack.

3. Accept the popup to save the new card configuration to NVRam. All cards should show a green status when this step is complete.

4. Zetron can link in and complete the needed configuration of the RIU based on your specific use. Otherwise contact Zetron for configuration instructions specific to your use of the RIU card.

5. From the IMS_ALS Tools menu choose Change Over.

6. Select Manual control, and then click the Main button under Select Active Device. This will force control to the Main subrack.

7. Move the manual control selection back to Automatic!

8. Close IMS.


This section covers setting up a radio interface to control a radio base station that is local to the Acom system backroom. The RIU module PTT relay is used to locally control the transmitter. It is assumed the system has already been configured with radio lines and only requires that PTT be enabled. If you need to create a new radio line that does not exist in the system for PTT control, please contact technical support.

Required Resources

• IMS ALS and/or access to IMS Terminal

• 709-7345-xxx Zetron straight-through cable – required if direct connecting to ALS with IMS ALS

• Acom Software Configuration manual (part number 025-9529)

• Acom Radio Interface Unit manual (part number 025-9605)

• Monitoring equipment – used to listen to transmission on demarcation block for troubleshooting

• A DVM – used for troubleshooting PTT relay

Radio Resources

130 025-9619A

Connections and Programming

Radio Line Programming

Note It is assumed a radio line is already programmed in the system

and only requires local PTT to be enabled. If a new radio line needs to be programmed from scratch, please contact technical support.

Programming a radio line for local PTT:

1. Using IMS ALS or IMS Terminal, access the ALS then right click on the MCU card in slot0 or slot1, select Acom Definitions and select Link1 or Link2. Once the Radio line has been located, click on it to open its properties.

2. Once the Radio line properties window is displayed, click the Configure Line Options button to display all tabs and settings.

3. Click on the Settings tab and select not defined under the Radio Type.

4. Once the settings have been established, click Save and the window will close and save the settings.

Note The radio interface card (RIU) Acom Definitions should be

checked to verify that the programming is correct (the same).


131

Configuring activation of the PTT relay:

1. Right click on the RIU card with the line being configured and select Card Settings.

2. Verify that the box next to PTT Enable has an “X” on the line/channel in which you are configuring.

3. Set the Line Interface Type to Local Control Simplex or Local Control Duplex. Use the setting that is required for your application/interface.

4. Click Save to save the settings.

Equipment Connections

Review your As-Built documents to get details on your RIU connections for TX/RX audio and PTT contacts for the specific line/channel being configured. Make the appropriate connections to your transmitter. Refer to the Acom hardware manual as needed for specific RIU pin out details and their function.

Testing

At this point, the radio line has been configured in this rack only. To test the radio line, verify that the rack that was just programmed is the active rack (ALS) and transmit to the base station from the console.

Once the radio line is confirmed to be functional, always perform an Update to Rack to permanently save your settings. If an Update to Rack is not performed, any programming settings configured will be lost if the rack is reset.

Note Repeat configuration steps for the other ALS (Main or Standby

depending on which rack was currently configured) to assure that both Main and Standby ALS have the same configuration.

Radio Resources

132 025-9619A

Troubleshooting

• If the base station does not key up, check the RIU PTT relay for closure using the DVM in ohmmeter mode. If the PTT relay is working make sure you have the correct bias (ground or voltage) on the PTT for proper transmitter PTT activation.

• If the PTT is functional, listen to the transmit audio output of the radio line at the demarcation block (or RJ21) with test equipment and listen for voice. If voice is not heard, a rack reset may be needed. Prior to a rack reset, duplicate the programming on the inactive rack (if the system has a Main/Standby configuration). Once both racks have been programmed, access the File menu and Update to Rack on both racks. Then reset the inactive rack, wait 2 minutes, change over to the rack that was reset, and then reset the other rack.

Local BCD Radio Control

The purpose of this section is to describe how to configure a local/direct radio interface using the RIU and UIO cards. The Acom will activate UIO digital outputs to set the channel/frequency of the local base station.

Required Resources




• Acom Radio Interface Unit (RIU) manual (part number 025-9605) and Universal Input/Output Card (UIO) manual (part number 025-9609)


• A DVM – used for troubleshooting PTT relay

Theory

The UIO outputs are used to control the local base station frequency. The two following tables provide a comparison between Binary and BCD numbering used for control.

Binary Control — all of the bits in a string are part of a single binary number


133

Channel Bit 0 Bit 1 Bit 2 Bit 3 Bit 4 Bit 5 Bit 6

1 ON

2 ON

3 ON ON

4 ON

8 ON

9 ON ON

10 ON ON

11 ON ON ON

21 ON ON ON

22 ON ON ON

23 ON ON ON ON

24 ON ON

BCD Control (Binary Coded Decimal) — the first 4 bits represent the low digit of the channel (0-9), the next 4 bits the next higher decimal digit (10s digit).

Channel Bit 0 Bit 1 Bit 2 Bit 3 Bit 4 Bit 5 Bit 6

1 ON

2 ON

3 ON ON

4 ON

8 ON

9 ON ON

10 ON

11 ON ON

21 ON ON

22 ON ON

23 ON ON ON

24 ON ON

Radio Resources

134 025-9619A

Programming

Note It is assumed a radio line is already programmed in the system

and only requires local BCD/Digital channel control to be enabled. The line has been assigned to an MCU timeslot and a RIU channel. If a new radio line needs to be programmed from scratch, please contact technical support.

Configuring a radio line for BCD control:

1. Right click on the MCU card in slot0 or slot1, select Acom Definitions, and select Link1 or Link2. Access the MCU Acom Definitions until you locate the radio line you wish to program. Once the Radio line has been located, left-click on it to open its properties.


3. Click on the Settings tab and select the desired Radio Type. BDC or Binary.

4. Set the Default Radio Channel as required.

5. Set the remaining Acom radio line parameters as required.

6. Once the settings have been made, click the Save button. The settings will be saved and the window will close.

Configuring the UIO card:

1. Right-Click on the UIO card and choose Acom Definitions.

2. Select the Digital Output tab.

3. For the desired output, set the Mode to “Radio Ctrl Bit0”.

4. Set the Extra field to the Acom line number for this output.


135

5. Set as many additional “Radio Ctrl BitX” outputs as needed. The following figure shows outputs 13 through 16 as radio control bits for line 51.

6. Click the Save button, then click the Exit button.

7. Access the File menu and select the Update to Rack option.

8. Click OK when prompted for configuration name.

Tip As always, remember to clone/copy your programming changes

to the opposite half of the main/standby shelves.

ACS Console Design Setup

Radio Resources

136 025-9619A

Configuring console buttons for BCD output:

1. Use the Acom Console Designer to create a screen form file containing the necessary frequency select buttons (Fx) for the radio to controlled.

2. Select each of the frequency select function buttons in turn and set its function type to Channel Set.

3. For each Fx button, set the parameter Dial String to the decimal number required to tune the radio to the desired frequency.

4. Save the new version of the console form file and copy it into the appropriate folder on every console position that will require this functionality.

Equipment Connections

Review the As-Built documents supplied with your system to get details on your RIU and UIO connections. Make the appropriate connections to your transmitter. The module-specific manuals (RIU = 025-9605, UIO = 025-9609) will provide generic pinouts for the RIU and UIO cards; however, the signals pass through a changeover shelf and may be arranged differently at the demarcation point for each system.

Testing

Place the Acom system in the normal operating mode and use the various Channel Set buttons at one or more console positions. Verify that the correct outputs activate and the desired channel is selected at the base radio.

Tone Remote Control

This section covers how to configure a radio interface to utilize Tone Remote Control (TRC) tones for controlling the transmissions of a base station that is not located with the Acom system back-room equipment. This section will detail steps necessary to setup a radio line on the system for TRC. The setup steps can be used on a digital MCU or RIU/EMU radio interface. It is assumed that the system has already been configured with radio lines and only requires that the TRC signaling be configured for a given line. If you need to create a new radio line that does not exist in the system for TRC signaling, please contact technical support.

Tone Remote Control

137

Required Resources




• Acom hardware module manuals for Radio Interface Units (RIU) (025-9605) and Signaling Management Units (SMU) (025-9607)


SMU Configuration

A radio resource/line that is operating in tone remote mode requires an SMU resource to generate the tone remote control signals. The assignment of SMU resources is accomplished using either IMS ALS or the IMS Terminal. It is best if the SMU assigned is physically in the same rack as the radio line that will be using it.

Early in the process of setting up the Acom system, you should create a table or spreadsheet listing all of the SMU cards and their resource information. For each SMU, the table should contain the SMU card slot number, the SMU time slot, and the resource settings per timeslot. In some cases this spreadsheet may have been created as part of the system “As-Built” documentation. Either way, having this information available will give you a better grasp of the SMU resource in use as well as those available for future expansion.

Tip Reference the Acom Software Configuration manual (part

number 025-9529) for details on accessing SMU resources.

Once the spreadsheet has been created/located, review it to determine whether SMU resources have been assigned to the radio line that will be used for tone remote control and whether or not those resources are receive or transmit in nature. VOX, AGC, as well as any resources labeled “decoder”, “detector”, or “filter” all qualify as receive resources. Any resources with a label of “encoder” are transmit resources.

In a typical system, all of the transmit resources are assigned to the same time slot in the SMU resource. For example, an MDC Encoder and a Guard Tone Encoder would be assigned to the same SMU time slot. For the same reasons, receive resources such as VOX and AGC would also be assigned to the same SMU time slot.

Tip To locate the line number for your radio line, open the screen in

Console Design, select the line, and note the Resource Identifier number.

Radio Resources

138 025-9619A

Configuring the SMU resource:

1. Use either IMS ALS or IMS Terminal to access the ALS, then right-click on the SMU to be configured and select Acom Definitions from the menu that opens.

2. Assign a Guard Encoder for the radio line. For example, the following graphic shows lines 50, 51, 52, and 53 with Guard Encoders assigned.

3. After assigning a Guard Encoder, check that the DSP Memory required does not exceed the allocated amount. If the limit for DSP Memory is exceeded, the memory information in the bottom of the SMU dialog turns red.

If the limit for DSP Cycles is exceeded, it too will turn red. In the case of DSP Cycles, you may take a calculated risk and leave it this way if you have good reason to believe that the system will never require all of the resources assigned to this SMU channel/DSP to used simultaneously. Still, it is advised that you try to stay within the allocated limits of DSP Cycles whenever possible.

4. When you have finished programming the SMU resources, click the Save button. The window will close automatically.

Radio Tone Database Configuration

For each ALS rack, there are four programmable Radio Tone Databases for each channel. Any one of these databases can be assigned to any radio line that also originates in that rack. Details on programming this database can be found in the Acom Software Configuration manual (part number 025-9529) in the chapter on Configuring ALS Parameters (Configure Menu).

Tone Remote Control

139

Each Radio Tone Database allows programming HLGT (High Level Guard Tone), LLGT (Low Level Guard Tone), Function Tone, and Channel set frequencies and level.

Note The gain levels shown in this dialog window are added to the

general transmit gain setting for the radio line. For example, if the line gain is set to 5dB, using the setting shown in the preceding graphic, the HLGT gain will be 8 dB, the LLGT gain -22 dB, the Function tones gain -2 dB, and voice gain approximately -1 dB.

Radio Tone database programming:

1. Use either IMS ALS or IMS Terminal to access the ALS, then open the Configure menu and select the Radio Tone Database option.

2. Select the tab for the Tone Index you wish to configure.

3. Set the tone frequencies and gain levels desired for both the HLGT and LLGT. Also set the duration for the HLGT.

4. Set the Audio gain level.

5. Set the gain and duration for each of the four function tones.

Radio Resources

140 025-9619A

6. Assign anywhere from one to four function tone frequencies to specific channel slots by:

a. Select a channel slot button.

b. Set the Channel: number. (It is recommended that the channel number and the channel slot be the same in order to minimize confusion in keeping track of which one you are working on. The channel number set here is the same channel number referenced when changing channel from the console.)

c. Enter the frequencies (in hertz) for the desired Function tones for that channel.

d. Click on the Save button.

7. Repeat the sub-steps in step 6 as necessary to configure all of your radio channels. Then click the Exit button to close this window.

Mode:

In order to key up the radio and transmit by means of Tone Remote Control, the Mode setting Tx enabled (generate tones) must be enabled as shown in the Radio Tone Database graphic. The use of the RX enabled (remove tones) setting is discussed in Muting Received Tone Remote Tones starting on page 142.


Now that the SMU resource and Radio Tone Remote Database have been configured, the radio line is ready to be programmed.

Programming a radio line for TRC service:

1. Use either IMS ALS or IMS Terminal to access the ALS, right click on the MCU card in slot0 or slot1, then select Acom Definitions and select Link1 or Link2.

Access the MCU Acom Definitions and links until you locate the radio line you wish to program. Once the Radio line has been located, click on it to open its properties.


3. Click on the Settings tab, assign the appropriate Radio Tone Database (Tone Remote X) under the Radio Type, and set the Default Radio Channel as desired.

Tone Remote Control

141

4. Once the settings have all been made, click the Save button. All the settings are save and the window closes automatically.

Note The radio interface card (RIU, EMU, or MCU) should be checked

to verify that the programming is correct (the same). This would be the card connecting to the radio equipment.

Testing

At this point, the radio line has been configured in this rack only. To test the radio line, verify that the rack just programmed is the active rack (ALS) and transmit to the base station from the console.

Once the radio line is confirmed to be functional, always perform an Update to Rack to permanently save your settings. If an Update to Rack is not performed, any programming settings configured will be lost if the rack is reset.

Note Repeat configuration steps for other ALS (Main or Standby

depending on which rack was just configured) to assure that both the Main and Standby ALS racks have the same configuration.

Radio Resources

142 025-9619A

Troubleshooting

• If the base station does not key up, listen to the transmit audio output of the radio line at the demarcation block with test equipment and listen for the tone remote key up tones/sequence. If they are not heard, a rack reset may be needed but prior to a rack reset, duplicate the programming on the inactive rack (if the system has a Main/Standby configuration). Once both racks have been programmed, access the File menu and Update to Rack on both racks. Then reset the inactive rack, wait 2 minutes, change over to the rack that was reset then reset the other rack.

• If key up tones are heard and the radio is not keying up, the levels or frequency may need to be adjusted for HLGT & LLGT. Verify that you have the correct HLGT and LLGT frequency programmed.

• Check SMU programming and verify that the line has a Guard Encoder allocation.

Muting Received Tone Remote Tones

This section explains how to configure a radio interface to mute (remove) incoming tone remote tones. This is usually required when a radio line interface that requires tone remote control (TRC) is shared with another device or console that utilizes the same radio base station. Since the base station requires TRC for key up, the other devices will send the TRC tones which will be heard by the Acom console unless they are muted (removed). This section will detail steps necessary to setup a radio line on the system to mute incoming TRC from other devices. The setup steps can be used on a digital MCU or RIU/EMU radio interface.

It is assumed that the system has already been configured with radio lines and only requires that TRC muting be configured. If you need to create a new radio line that does not exist in the system, please contact technical support.

Required Resources




• Acom hardware module manuals for Radio Interface Units (RIU) (025-9605) and Signaling Management Units (SMU) (025-9607)



143

SMU Programming

A radio resource/line that is operating in tone remote mode requires an SMU resource both to generate the outgoing tone remote control signals and to remove incoming TRC signals generated by other equipment sharing the line.

Early in the process of setting up the Acom system, you should create a table or spreadsheet listing all of the SMU cards and their resource information. For each SMU, the table should contain the SMU card slot number, the SMU time slot, and the resource settings per timeslot. Either the IMS ALS or the IMS Terminal can be used to gather this information. In some cases this spreadsheet may have been created as part of the system “As-Built” documentation. Either way, having this information available will give you a better grasp of the SMU resources in use as well as those available for future expansion.



Once the spreadsheet has been created/located, review it to determine whether SMU resources have been assigned to the radio line that will be used for tone remote control and whether or not those resources are receive or transmit in nature. VOX, AGC, as well as any resources labeled “decoder”, “detector”, or “filter” all qualify as receive resources. Any resources with a label of “encoder” are transmit resources.

In a typical system, all transmit resources for a line are assigned to the same timeslot in the SMU resource. For example, an MDC Encoder and Guard Tone Encoder would be on the same SMU time slot. The same is true for receive resources; both VOX Detector and AGC are assigned to the same SMU time slot.

The following example shows Line 1 and Line 3 with Guard Detector and Guard Filter assigned. In most cases, the Guard Detector, Guard Filter, VOX Detector and AGC should be programmed on the same timeslot for the line since they are all receive resources permanently assigned to the line.



Radio Resources

144 025-9619A



2. Assign a Guard Detector and a Guard Filter for the radio line. For example, the following graphic shows lines 1, and 3 with Guard Detectors and Guard Filters assigned.

3. After making the Guard Encoder and Guard Filter assignments, check that the DSP Memory required does not exceed the allocated amount. If the limit for DSP Memory is exceeded, the memory information in the bottom of the SMU dialog turns red.




145

Radio Tone Database Programming

For each ALS rack, there are four programmable Radio Tone Databases. Any one of these databases can be assigned to any radio line that also originates in that rack. Details on programming this database can be found in the Acom Software Configuration manual (part number 025-9529) in the chapter on Configuring ALS Parameters (Configure Menu).

Each Radio Tone Database allows programming HLGT (High Level Guard Tone), LLGT (Low Level Guard Tone), Function Tone, and Channel set frequencies and level.

Note The only items you need to set in the Radio Tone Database

window for removing tones is the HLGT and LLGT frequency and Mode. Other settings only pertain to transmission of TRC.

Radio Resources

146 025-9619A

Radio Tone database programming:

1. Use either IMS ALS or IMS Terminal to access the ALS, then open the Configure menu and select the Radio Tone Database option.

2. Select the tab for the Tone Index you wish to configure.

3. Confirm that the tone frequencies and gain levels have been set for both the HLGT and LLGT, as well as the duration for the HLGT.

4. In the Mode section of the Radio Tone Database window, select the Rx enabled (remove tones) option. (If the same database is to be used for transmitting TRC tones, confirm that the Tx enabled (generate tones) option is selected as well.

5. Click the Save button to save your settings and then click the Exit button to close the window.


Once the SMU resource and the Radio Tone Remote Database have been configured, it is time to configure the radio line with which they will be used.

Programming the radio line for muting TRC tones:

1. Use either IMS ALS or IMS Terminal to access the ALS, then right-click on the MCU card in slot0 or slot1, select Acom Definitions and select Link1 or Link2. Continue to access the MCU Acom Definitions and links until you locate the radio line you wish to program. Once the correct radio line has been located, click on it to open its properties.

2. With the radio line properties window open, click the Configure Line Options button to display all tabs and settings.

3. In the right pane of the window, click on the Settings tab. Under the Radio Type section, assign the appropriate Radio Tone Database (Tone Remote X) and set the Default Radio Channel as desired.


147

4. Once all the settings have been made, click the Save button to save the changes and close the window.


to verify that the programming is correct (the same). This would be the card to which the radio equipment is interfaced.

Testing

Testing TRC tone muting on a radio line:

1. Verify that the rack that was just programmed is the active ALS rack.

2. Select the radio line at the console and transmit on that line from another device sharing the base station.

3. If the mute function is operating correctly, the TRC tones should not be heard at the console. Only the voice audio coming from the other device should be heard.

Tip Once the radio line is confirmed to be functional, always perform

an Update to Rack to permanently save your settings. If an Update to Rack is not performed, any programming settings configured will be lost if the rack is reset.

Note Repeat configuration steps for the other ALS rack (Main or

Standby depending on which rack was just configured) to assure both Main and Standby ALS racks have the same configuration.

Troubleshooting

If the TRC tones can still be heard at the console position, try the following checks:

• Check SMU programming and verify that the line has a Guard Filter and Guard Detector allocated.

• Check Radio Tone Remote Database and verify settings are correct.

• Verify radio line is configured/assigned with the appropriate Radio Tone Database.

• Reset the ALS rack.

Radio Resources

148 025-9619A

Configuring MDC-1200 Signaling

This section covers how to configure a radio line interface to utilize MDC-1200 signaling for transmissions and/or decoding. An EMU or a RIU card can be used to interface to the radio. It is assumed the system has already been configured with radio lines and only requires that MDC-1200 signaling be configured. If you need to create a new radio line that does not exist in the system for MDC-1200, please contact technical support.

Required Resources




• Acom hardware module manuals for Radio Interface Units (RIU) (025-9605) and E&M Units (EMU) (025-9617)


SMU Programming

The radio line used to handle MDC-1200 signaling requires a separate SMU resource be assigned both to generate signaling tones for outbound calls and to decode signal tones for incoming calls.




Once the spreadsheet has been created/located, review it to determine whether SMU resources have been assigned to the radio line that will be used for MDC-1200 signaling and whether or not those resources are receive or transmit in nature. VOX, AGC, as well as any resources labeled “decoder”, “detector”, or “filter” all qualify as receive resources. Any resources with a label of “encoder” are transmit resources.


149

In a typical system, all transmit resources for a line are assigned to the same timeslot in the SMU resource. For example, an MDC Encoder and Guard Tone Encoder would be on the same SMU time slot. The same is true for receive resources; both VOX Detector and MDC-1200 decoder are assigned to the same SMU time slot.

After reviewing and documenting the SMU resources, assign an MDC-1200 Encoder to transmit tones and an MDC-1200 Decoder to decode tones for the radio line. The following example shows Line 50 and 51 with both Guard Encoder and MDC-1200 Encoder assigned for the transmit timeslot and VOX, AGC and MDC-1200 Decoder for the decode time slot.



An MDC-1200 Encoder is required if you intend to receive MDC-1200 emergency calls and acknowledge them. An MDC-1200 Decoder is required to decode MDC-1200 calls and display the calling radio’s ID on the console line button and/or Call History panel.



2. Assign a MDC-1200 Detector and a MDC-1200 Filter for the radio line.

3. After making the MDC-1200 Encoder and MDC-1200 Filter assignments, check that the DSP Memory required does not exceed the allocated amount. If the limit for DSP Memory is exceeded, the memory information in the bottom of the SMU dialog turns red.



Radio Resources

150 025-9619A

MDC-1200 Dial Types Database Programming

For each ALS rack, there are four programmable MDC-1200 Dial Types databases. Any one of these databases can be assigned to any radio line that also originates in that rack. Details on programming this database can be found in the Acom Software Configuration manual (part number 025-9529) in the chapter on Configuring ALS Parameters (Configure Menu).

Each MDC-1200 Dial Types database allows enabling PTT ID transmission and various other settings. A typical configuration is shown here:

Note Consult the Acom Software Configuration manual (part number

025-9529) for details on these settings.

Note If Emergency Auto Ack is enabled, the console will still alert upon the reception of the MDC-1200 emergency call but the alert will be acknowledged and silenced immediately.


Now that the SMU resource and MDC-1200 Dial Types database have been configured, the radio line is ready to be programmed.

Programming the radio line for MDC-1200 signaling:




151

3. Click on the right arrow indicator in the upper right corner of the window until the MDC-1200 tab is displayed. Select the MDC-1200 tab.

4. For MDC Type, assign the appropriate MDC-1200 Dial Types database that was configured.

5. Adjust the Individual ID and Group ID fields as needed or leave them at their default values.

6. It is advisable to leave the Line Levels settings at default. Only make adjustments if MDC-1200 signal transmission and decoding are unreliable.

7. When the settings have been completed, click the Save button to save your settings. The window will close automatically.



Editing the Console Screen File

MDC-1200 Call History

It is recommended that an MDC-1200 Call History panel be placed on the console screen. Doing so allows the console dispatcher to see a brief history of the last several incoming MDC-1200 call ID strings and clearly display both normal and emergency calls. The size of the window can be adjusted as needed.

Radio Resources

152 025-9619A

Note It is recommended that someone who is familiar with Console

Design and screen changes perform this task. You may also want to consult with Zetron technical support for guidance or they may be able to perform the screen changes for you.

Adding a call history stack to the console screen:

1. Make a backup file for the screen definition file to be edited.

2. Start the Console Designer program and open the screen .dfm file.

3. Locate the area of the screen that will hold the MDC-1200 Call History stack.

Note The Call History panel can also be placed on a tab if needed. See

the Console Design manual (part number 025-9587) on how to add new tabs.

4. Select the Panel icon from the Console Design tool bar, and then click the area on the screen in which you would like to place the panel. The panel will initially be displayed as a small button sized panel. Adjust the panel size to meet your needs. It is recommended that the panel size be at least 2” high by 5” wide.

5. On the panel Object Inspector (Properties) window, select the Panel Type of Call History MDC-1200.


153

6. When the new panel is first displayed, it will look similar to the one that follows here. The one shown at the beginning of this section was modified to have a particular look.

7. Adjust the screen size of the new panel as needed.

8. Notice that there is no Emergency Ack button. This button is required if your MDC Dial Types does not have Emergency Auto Ack set to enabled and you intend to receive MDC-1200 emergency calls. If this button is required, it must be place on the panel manually by placing a function button on the panel and assigning the Function Type as MDC-1200 Emergency Alert Ack. For more details on function buttons, see the Console Design manual.

MDC-1200 Line Button

The MDC-1200 line button is programmed like any other radio button. The only option that may need to be enabled is Display Emergency. This allows MDC-1200 emergency calls received to be alerted and responded to correctly by the console. If the Display Emergency option is not enabled, MDC-1200 emergency calls will be responded to like a normal inbound calls and no emergency alert will be sounded.

To enable the Display Emergency option for an radio line button:


2. To enable the Display Emergency option, right-click on the line button being configured and select Edit Resource from the pop-up menu.

3. The Object Inspector window opens. On the line for the Display Emergency option, change the setting to Enabled.

4. From the File menu, save the change to the screen settings.

File Settings in AcomConsole.ini

The following changes need to be made to the AcomConsole.ini file for each console that uses this screen .dfm file.

Radio Resources

154 025-9619A

• [MDC] section This section allows configuration of how IDs will be displayed in the Call History panel and line button. There is also a setting for displaying unique messages for GE-Star Status. Review the AcomConsole.ini for details on these settings.

• [Sounds] section This section allows specific sounds to be played during a specific event. The only one of concern for MDC-1200 is the MdcEmergency= setting. This setting allows a specific wav file to be played when an emergency MDC-1200 alert is received from the field. The wav file must exist in the AcomConsole folder. This wav file will be played continuously with an approximately 5 second pause between each playback until the MDC-1200 emergency has been acknowledged.

Testing

Testing MDC-1200 signaling on a radio line:


2. Select the radio line at the console and transmit a call to a field radio using MDC-1200 signaling. Confirm that the field radio receives the call and unmutes.

3. Key up the field radio and transmit back to the console. Confirm that the console displays the correct radio ID on the line button.

4. If the MDC-1200 encoding and decoding are working correctly, the Call History stack should show the proper details for MDC-1200 signaling both sent and received.





Troubleshooting

If the no MDC-1200 tones are transmitted:

• listen to the transmit audio output of the radio line at the demarcation block with test equipment and listen for the MDC-1200 key up tones/sequence

• if they are not heard, a rack reset may be needed but prior to a rack reset,

• duplicate the programming on the inactive rack (if the system has a Main/Standby configuration)

Configuring GE-Star Signaling

155

• once both racks have been programmed, access the File menu and Update to Rack on both racks

• then reset the inactive rack, wait 2 minutes, change over to the rack that was reset then reset the other rack

If MDC-1200 key up tones are heard and the field radio is not detecting the tones, the output levels may need to be adjusted under the MDC-1200 tab on the radio line settings.

If incoming MDC-1200 calls are not be detected, the threshold level may need to be adjusted under the radio line settings:

• a rack reset may be needed but prior to a rack reset, duplicate the programming on the inactive rack (if the system has a Main/Standby configuration)

• once both racks have been programmed, access the File menu and Update to Rack on both racks

• then reset the inactive rack, wait 2 minutes, change over to the rack that was reset then reset the other rack

Check SMU programming and verify that the line has the proper MDC-1200 resources.


This section covers the steps necessary to setup a radio line on the system for GE-Star signaling. The setup steps can be used on a digital MCU or RIU/EMU radio interface. It is assumed the system has already been configured with radio lines and only requires that GE-Star signaling be configured. If you need to create a new radio line that does not exist in the system for GE-Star signaling, please contact technical support.

Required Resources




• Acom hardware module manuals for Main Control Units (MCU) (025-9602), Radio Interface Units (RIU) (025-9605), and E&M Units (EMU) (025-9617)


Radio Resources

156 025-9619A

SMU Programming

The radio line used to handle GE-Star signaling requires a separate SMU resource be assigned both to generate signaling tones for outbound calls and to decode signal tones for incoming calls.




Once the spreadsheet has been created/located, review it to determine whether SMU resources have been assigned to the radio line that will be used for GE-Star signaling and whether or not those resources are receive or transmit in nature. VOX, AGC, as well as any resources labeled “decoder”, “detector”, or “filter” all qualify as receive resources. Any resources with a label of “encoder” are transmit resources.


You may assign a GE-Star Encoder and/or GE-Star Decoder for the radio line. The following example shows Line 7 with only a GE-Star Decoder assigned and Line 8 with a GE-Star Encoder and GE-Star Decoder assigned. A GE-Star Encoder is typically needed if the console/radio line is sending a specific unique ID to the field radios or will be acknowledging GE-Star Emergency calls. A GE-Star Decoder is needed if the radio line is to decode incoming GE-Star IDs from field radios and display them on the console radio button or call history.


157





2. Assign a GE-Star Detector and a GE-Star Encoder for the radio line.

3. After making the GE-Star Detector and GE-Star Encoder assignments, check that the DSP Memory required does not exceed the allocated amount. If the limit for DSP Memory is exceeded, the memory information in the bottom of the SMU dialog turns red.



GE-Star Definitions Programming

For each ALS rack, there are four programmable GE-Star Definitions types databases. Any one of these databases can be assigned to any radio line that also originates in that rack. Details on programming this database can be found in the Acom Software Configuration manual (part number 025-9529) in the chapter on Configuring ALS Parameters (Configure Menu).

There are various settings for each GE-Star type. A typical configuration is shown in the following figure, in the Type 1 row. If you intend to encode the GE-Star format for transmissions, you must be sure to select Encode Enabled and select one of the options for Console PTT ID.

Radio Resources

158 025-9619A

Once you have program the types, click the Save button to save settings and close the window.


When the SMU resource and GE-Star Definitions have been configured, the radio line is ready to be programmed.

Programming the radio line for GE-Star signaling:



3. Click on the right arrow indicator in the upper right corner of the window until the GE-Star tab is displayed. Select the GE-Star tab.

4. In the GE-Star Type section, assign the same GE-Star Type x that was used when you configured the GE-Star Definitions.

5. Leave the Line Levels settings at default.

6. When you have finished with the settings, click the Save button. The changes will be saved and the window closes.


159



File Settings in AcomConsole.ini

There are three settings in the AcomConsole.ini file that apply to the configuration of GE-Star signaling.

• [GE-Star] This section configures the GE-Star ID to be transmitted. In most cases, this is not setup. If this section is setup, then you may need to maintain a separate AcomConsole.ini for each console if each console is to have its own unique GE-Star ID for transmissions. Review the AcomConsole.ini for details on this setting.

• [MDC] This section allows configuration of how IDs will be displayed in the Call History panel and line button. There is also a setting for displaying unique messages for GE-Star Status. Review the AcomConsole.ini for details on these settings.

• [Sounds] This section allows specific sounds to be played during a specific event. The only one of concern for GE-Star is the MdcEmergency= setting. This setting allows a specific wav file to be played when an emergency GE-Star alert is received from the field. The wav file must exist in the AcomConsole folder. This wav file will be played continuously with an approximately 5-second pause between each playback until the GE-Star emergency has been acknowledged.

Call History Panel Setup

The Call History panel allows the dispatcher to view activity of GE-Star receptions to the console. The panel has columns for the time of reception, alias name, status, and shows indications if the inbound reception was an emergency.

To add a Call History panel to the screen, first determine a location on the screen to place the panel. Once a location/space has been determined, use the following procedure to add and edit the Call History panel.

Note It is recommended that someone who is familiar with Console

Design and screen changes perform this task. You may also want to consult with Zetron technical support for guidance or they may be able to perform the screen changes for you.

Radio Resources

160 025-9619A

Adding a GE-Star call history panel to the console screen:



3. Select the Panel button icon in the Console Design tool bar then click on the area of the screen to place the panel.

4. Select Call History MDC-1200 for the Panel Type.

5. Adjust the panel size as needed but do not remove any of the buttons.

6. If desired, you may customize the panel’s appearance by doing such things as adding a label to the panel or rearranging the positions of the buttons.

7. From the File menu, use the Save option to record your changes to the console screen file.

Emergency Acknowledgement

If the console operator is to receive GE-Star Emergency calls, it is recommended that you place a GE-Star Emergency Acknowledgement button on the screen. Unless you enabled the Emergency Auto Ack option in the GE-Star Definitions type you configured for this console, the button will be required in order to acknowledge GE-Star emergency calls. The notification alert will play indefinitely if the call is not acknowledged.


161

Adding a GE-Star Emergency Alert Ack button to the console:

1. Using Console Design open the desired screen.

2. Select the Function button icon in the Console Design tool bar then click on the area of the screen to place the button. (The button can also be added to the Call History panel.)

3. Select MDC Emergency Alert Ack for the Function Type.

4. Enter the appropriate button caption.

5. Adjust the button size and color as needed.

GE-Star Line Button

The GE-Star line button is programmed like any other radio line button. The only option that may need to be enabled is Display Emergency. This allows GE-Star emergency calls received to be alerted and responded to correctly by the console. If this option is not enabled, GE-Star emergency calls will be responded to like a normal inbound calls and no emergency alert will be sounded.

Configuring a GE-Star radio line button:

1. Using Console Design open the desired screen.

2. Using the mouse, right-click on the line button and select Edit Resource from the pop-up menu.

3. In the Object Inspector window that opens, select the Display Emergency attribute and set its condition to Enabled.

4. From the Console Designer File menu, Save this change to the screen file.

Radio Resources

162 025-9619A

Testing

Testing GE-STAR signaling on a radio line:


2. Select the radio line at the console and transmit a call to a field radio using GE-Star signaling. Confirm that the field radio receives the call and unmutes.

3. Key up the field radio and transmit back to the console. Confirm that the console displays the correct radio ID on the line button.

4. Place an Emergency Call to the console, and then confirm that the Emergency Alert Ack button works correctly to acknowledge the call.

5. If the GE-Star encoding and decoding are working correctly, the Call History stack should show the proper details for GE-Star signaling both sent and received.





Troubleshooting

If GE-Star is not being decoded/encoded, check the following:

Encode/Transmit issues:

• Listen to the transmit audio of the radio line at the demarcation block with test equipment. Listen for the GE-Star tones. If they are not heard, a rack reset may be needed but prior to a rack reset, duplicate the programming on the inactive rack (if the system has a Main/Standby configuration). Once both racks have been programmed, access the File menu and Update to Rack on both racks. Then reset the inactive rack, wait 2 minutes, change over to the rack that was reset then reset the other rack.

• Check all GE-Star configurations in the ALS rack including SMU resources and make sure the line has GE-Star enabled.

Configuring EnRoute Signaling

163

Decode/Receive issues:

• Listen to the receive audio of the radio line at the demarcation block with test equipment. Listen for GE-Star tones. If tones are not heard, check the field radio for GE-Star capabilities and configuration. If tones are heard, a rack reset may be needed but prior to a rack reset, duplicate the programming on the inactive rack (if the system has a Main/Standby configuration). Once both racks have been programmed, access the File menu and Update to Rack on both racks. Then reset the inactive rack, wait 2 minutes, change over to the rack that was reset then reset the other rack.

• Check all GE-Star configurations in the ALS rack including SMU resources and make sure the line has GE-Star enabled.


This section will detail steps necessary to setup a radio line on the system to Enable EnRoute signaling. These setup steps can be used with either RIU or EMU radio interfaces. It is assumed the system has already been configured with radio lines and only requires that EnRoute signaling be configured. If you need to create a new radio line that does not exist in the system for EnRoute Signaling, please contact technical support.

Required Resources




• Acom hardware module manuals for Radio Interface Units (RIU) (025-9605) and E&M Units (EMU) (025-9617)


SMU Programming

The radio line used to handle EnRoute signaling requires a separate SMU resource be assigned both to generate signaling tones for outbound calls and to decode signal tones for incoming calls.

Early in the process of setting up the Acom system, you should create a table or spreadsheet listing all of the SMU cards and their resource information. For each SMU, the table should contain the SMU card slot number, the SMU time slot, and the resource

Radio Resources

164 025-9619A

settings per timeslot. Either the IMS ALS or the IMS Terminal can be used to gather this information. In some cases this spreadsheet may have been created as part of the system “As-Built” documentation. Either way, having this information available will give you a better grasp of the SMU resources in use as well as those available for future expansion.




In a typical system, all transmit resources for a line are assigned to the same timeslot in the SMU resource. For example, an MDC Encoder and Guard Tone Encoder would be on the same SMU time slot. The same is true for receive resources, both VOX Detector and MDC-1200 decoder are assigned to the same SMU time slot.

Assign a Guard Encoder for the radio line. The following example shows Lines 50, 51, 52 and 53 with Guard Encoders assigned on SMU timeslots 0, 2, 4, and 6.



Now assign an EnRoute Detector, Vox Detector, and AGC for the same radio lines. The following example shows Line 50, 51, 52 and 53 with a EnRoute Detector, Vox Detector, and AGC assigned to timeslots 1, 3, 5, and 7.


165



2. Assign a Guard Encoder to the transmit time slot for the radio line(s) using EnRoute signaling.

3. Assign an EnRoute Detector, VOX Detector, and AGC to the receive time slot of the same radio line(s) programmed in step 2.

4. After making the encoder and detector assignments, check that the DSP Memory required does not exceed the allocated amount. If the limit for DSP Memory is exceeded, the memory information in the bottom of the SMU dialog turns red.




After the SMU resources have been configured, it is time for the radio line to be programmed.

Radio Resources

166 025-9619A

Programming the radio line for EnRoute signaling:



3. Click on the Settings tab, set the Radio Type selection to EnRoute. In the Default Radio Channel field, enter the desired setting. (a setting of 3 = both channels keyed)

4. Click on the right arrow indicator in the upper right corner of the window until the EnRoute tab is displayed. Select the EnRoute tab and configure the settings as desired.


167


Note The radio interface card (RIU or EMU) should be checked to

verify that the programming is correct (the same). This would be the card to which the radio equipment is interfaced.

Console Button Resources Setup

An Enroute will consist of a radio line button on the AcomConsole screen and optional channel selection and base station answer back tone detection. The radio line button does not require any special setting and can be configured like a standard radio line button.

Radio Resources

168 025-9619A

Standard radio line button properties

Channel Selection Buttons

To add channel selection buttons:

1. Make a back up copy of appropriate screen dfm form file for archival purposes.

2. Start the Console Designer application and open the screen form file.

3. Locate an area around the radio line button to place the channel selection buttons.

Tip You may also place a panel on the screen and place all items

related to the Enroute radio on a single panel as shown in the following example.


169

4. Select the Function icon in the Console Designer toolbar and click on the area of the screen to place the channel select button. Adjust the button size as needed.

5. Set the Function Type to Channel Set.

6. Set the Dial String to the channel that will be set.

7. Repeat steps if all channel selection choices are required on the screen. Channel 1, Channel 2 and Channel 3 (3= both channel 1 and channel 2).

8. From the Console Designer File menu, Save the changes to the .dfm file.

Answer Tone Detection Capability

To add Answer tone detection:

1. Make a back up copy of appropriate screen dfm form file for archival purposes.

2. Start the Console Designer application and open the screen form file.

3. Locate an area around the radio line button to place the Answer tone detection buttons. Please note that you will need a button for each Answer tone you wish to monitor. The following example below shows 12 Answer tone displays.

Tip You may also place a panel on the screen and place all items

related to the Enroute radio on a single panel as shown in the following example.

Radio Resources

170 025-9619A

4. Select the Label icon in the Console Designer toolbar and click on the area of the screen to place the Answer tone display button.

5. For the Label Type, select GP Binary Status.

6. Set the Bit properties to the Answer tone to monitor.

7. Repeat steps 4 through 6 as necessary to add more Answer tone monitor/detection buttons to the EnRoute button panel.

8. From the Console Designer File menu, Save the changes to the .dfm file.

Testing

Testing EnRoute signaling on a radio line:


2. Select the radio line at the console and transmit a call to a field radio using the EnRoute channel buttons. Confirm that the field radio receives the call and unmutes.

Configuring Two-tone Paging

171

3. Key up the field radio and transmit back to the console. Confirm that the console displays the correct EnRoute channel number on the line button.





Troubleshooting

• If the base station does not key up, listen to the transmit audio output of the radio line at the demarcation block with test equipment and listen for the key up tone sequence. If they are not heard, a rack reset may be needed but prior to a rack reset, duplicate the programming on the inactive rack (if the system has a Main/Standby configuration).

• Once both racks have been programmed, access the File menu and Update to Rack on both racks. Then reset the inactive rack, wait 2 minutes, change over to the rack that was reset then reset the other rack.

• If key up tones are heard and the radio is not keying up, the levels or frequency may need to be adjusted. Verify that you have the correct tones programmed for the channel under the EnRoute tab in the ALS line settings. Adjust Tx audio levels as needed.

• If there is no answer tone detection occurring, verify that the answer tones are heard at the demarcation block and the correct frequencies are being sent to the radio line. Also check answer tone detection buttons on the screen for correct configuration.

• If channels are not being able to be changed, make sure the console Channel Set buttons are programmed correctly. Also monitor the demarcation block for the correct frequency for each channel being selected.

• Check SMU programming and verify that the line has a Guard Encoder, VOX Detector, AGC, and EnRoute Detector allocated for the radio line.


This section will detail steps necessary to setup a radio line on the system for Two-tone Paging. The setup steps can be used on a digital MCU or RIU/EMU radio interface. It is assumed the system has already been configured with radio lines and only requires that

Radio Resources

172 025-9619A

Two-tone Paging be configured. If you need to create a new radio line that does not exist in the system for Two-tone Paging, please contact technical support.

Required Resources






SMU Programming

The radio tone remote resource/line used to handle two-tone signaling requires a SMU resource be assigned to generate signaling tones for outbound calls.







173





2. Assign some dynamic Selcal Encoders. The Selcal Encoders are assigned to various time slots instead of being assigned to specific radio lines. In the following example, the Selcal Encoders are assigned to timeslots 0 through 2.

3. After you have assigned the required number of Selcal Encoders, check that the DSP Memory required does not exceed the allocated amount. If the limit for DSP Memory is exceeded, the memory information in the bottom of the SMU dialog turns red.



Radio Resources

174 025-9619A


Once the SMU resources have been assigned, the radio line programming may be carried out.

To program a radio line for two-tone paging:



3. Click on the Miscellaneous tab. If you intend to allow paging on the line even if there is communications (receive audio) on the air, enable the Override CD when dialing option. Otherwise, you must make sure it is not enabled.

4. Click on the Levels tab. Under the Sequential section, there are various settings. Refer to the Acom Software Configuration manual (part number 025-9529) for details on these settings. Otherwise, leave them at their default values.



175



Setting up a Two-tone Paging Database

To utilize two-tone paging, a paging database must be created and maintained for using specific buttons to send specific pages or manual paging. Refer to the section Paging Configuration Database on page 58.

Setting up an Instant Page

To call out an Instant Page from the Paging database, an Instant Page button must be created on the console screen.

Creating an instant page button on the console screen:

1. Save a backup copy of the console screen .dfm file before you start to work.

2. Using Console Designer, open the desired screen .dfm file.

3. Find an area on the screen to place the button. (You can also place Instant Page buttons on a pop up screen or tab.) If you require assistance with this, contact technical support.

4. Once you have decided on a place to locate the button, select the Function button icon in the Console Design tool bar, and then click on the area of the screen to place the button.

5. In the Object Inspector dialog box, select Instant Page for the Function Type for the new button.

6. From the same dialog, select the button Caption attribute and fill in the caption to be displayed on the button.

7. From the same dialog, select the Instant Page Name attribute and enter the same name assigned to the Instant Page in the Paging Database under the Instant Page Configuration. This name is both case and space sensitive.

Radio Resources

176 025-9619A

8. Adjust the button size and color on the console screen form as desired.

9. Once you have completed all of the editing for the instant page button, open the Console Designer File menu and use Save to record the changes to the console screen .dfm file.

10. Repeat this procedure as needed to add other Instant Page buttons.

Tip You may also copy existing Instant Page buttons, locate them in

new location on the screen and change the Caption and Instant Page Name as needed. Just be cautious when copying buttons. Refer to the Console Design manual on how to copy buttons and placing them on the screen.

Setting up a Page Stack

In order to send pages, a Page Stack must exist on the screen. However, if both of the two following conditions are true, the Page Stack can be hidden; the pages would be sent out immediately, without the need for a Send button.

• In the AcomConsole.ini file, under the [Paging] section, if the attribute Safety Mode= is set to False

• In the Object Inspector window for the Instant Page button, the attribute Stack Entry is set to Disabled

Configuring a page stack on the console screen:




177

3. Determine the location on the console screen to place the Page Stack panel. The page stack will usually take up the same screen real estate as 9 to 12 buttons grouped in a square.

4. Select the Panel icon on the Console Design tool bar, and then click on the area of the screen in which the Page Stack will be inserted.

5. In the Object Inspector window for the new panel, select Pager Stack as the Panel Type setting.

6. Once the Panel Type has been selected, the Page Stack attributes will appear within the panel on the screen. Adjust the panel size as needed, but do not remove any of the buttons. Move the buttons to the desired location on the Page Stack. The following example is typical.

7. For now, until your needs become better defined, you may leave all other properties at default.

8. Once you have completed all of the editing for the page stack panel, open the Console Designer File menu and use Save to record the changes to the console screen .dfm file.

Radio Resources

178 025-9619A

Testing

Testing two-tone paging signaling on a radio line:


2. Select the radio line at the console that has been configured for two-tone paging and use the paging stack configured for that line to place several pages.

3. Confirm that the correct field radios/pagers have received the calls and unmuted.

4. If any instant page buttons have been configured, use these buttons to place pages. Confirm that the appropriate pagers or radios received the pages.





Troubleshooting

If pages are not transmitting, check the following:

• If Instant Page buttons are grayed out/inactive on the console screen, this means page name entry for the attribute Instant Page Name for the instant page button does not match the name used in the paging database. Double check the button name against the Instant Page Configuration name in the database.

• If a specific radio line is not assigned to a page in the paging database, the radio line to be used for transmitting the page must be manually selected.

• If a page gets a red X next to it in the Page Stack, this usually means there are no Selcal encoders available. Check SMU programming and verify that there are Selcal Encoders assigned to the radio lines used for paging.

• Listen for paging tones at the demarcation point. If they are not heard, an ALS rack reset may be needed.

Caution! Prior to performing a rack reset, duplicate the programming on the inactive rack (if the system has a Main/Standby configuration). Once both racks have been programmed, perform an Update to Rack on both racks.

• Then reset the ALS rack that is currently inactive

• Wait 2 minutes, change system operation over to the ALS rack that was reset

• Then reset the other ALS rack

Configuring Analog Radio Function and Resource Buttons

179

• If paging tones are heard but the pager is not alerting, double check the Instant page capcode/frequency called out in the paging database. Also try alerting several other pagers.

• If everything looks good in the database, check the deviation of the paging tones over the air. The RF signal should be approximately at 70% of full channel deviation when the paging tones are transmitting. An RF service monitor will be required to confirm this requirement.

• If deviation appears to fluctuate erratically, try to determine if this fluctuation is specific to low or high frequencies. Enable/disable the de-emphasis option as needed.


This section will cover the set up of various common analog radio function buttons and resource buttons. The function buttons include channel set, instant monitor, instant TX, and resource audio volume. The resource buttons include marker tone and squelch disable.

Channel Set Function Button

Covers setting up the TRC interface to allow remotely setting the RF channel selected at the radio base station.

The following assumptions are made for this subsection:

• The line resource should already be setup for tone remote control. If not, refer to Tone Remote Control on page 136

• Radio line resources should also be programmed on the console screen. For the purposes of this set up description, we will use “Radio Line 1” as our radio resource. “Radio Line 1” should already be setup on the console screen .dfm file and in the ALS rack. This also assumes that specific channels for selection have been setup in the ALS.

Required Resources





Radio Resources

180 025-9619A


• Tone remote equipment – used to verify the channel changes when the channel set feature is used

Console Screen Changes — Add Channel Set Function Button

The following procedure will outline the steps required to add the Channel Set function button to the screen.

Creating a channel set function button:



3. Right click on the Function button tool and then click on the console screen form in the approximate location you wish to add the Channel Set button. The new function button form should appear with default settings.

4. In the Object Inspector window for the new button, click on the Function Type property and open the list for that setting. Scroll down the list and select the Channel Set function type and click on it. The Object Inspector window will refresh itself, now showing the default attributes for a Channel Set button.

5. Click on the DialString property and type the number 1. This specifies the channel we intend to use when pressing this button.

6. Click on the Line(s) property and type the number 1. This specifies the radio line resource within the ALS rack we intend to change the channel for.

7. Move the new Channel Set button to an acceptable location on the main screen. Preferably, a location that helps to remind you that the button relates to the specified line resource.

8. Select the button property Caption and enter a caption string that will indicate that the button’s function is to change the radio on line 1 to channel 1. Perhaps something like “Ln1 to Chn1”.

9. Repeat steps 3 through 8 for each additional channel set button you wish to add to the screen. Be sure to modify the line numbers and channel set numbers as necessary.

10. Once you have completed all of the editing for the new channel set buttons, open the Console Designer File menu and use Save to record the changes to the console screen .dfm file.

To modify existing channel set buttons, use the Console Designer application to open the appropriate console .dfm file. Alter the DialString and Line(s) attributes for the existing channel set buttons as necessary.


181

Set Up a Channel Set Dial Pad

This procedure will walk you setting up a channel set dialpad. The dialpad can configured to be dynamic (allows you to change channels on any line resource) or static (assigned to a specific channel).

The procedure presented here assume that a !ChannelSelect.dfm file already exists in the same file directory on the console computer that holds your Acom Console software.

Setting up a dynamic allocation channel select dialpad:





5. Click on the SourceFile property and change it to !ChannelSelect.dfm, which will call out that specific form. If the name of the file is different, modify the property to whatever the actual file name is.

6. Move the button to an acceptable location on the main screen.

7. Click on the function button Caption attribute and change it to something useful, for example Channel Select, to identify it as the control for changing a line resource channel selection.

8. Leave the remaining button attributes as they are. Save the changes and close the form file.

Setting up a static channel select dialpad:





5. Click on the SourceFile property and change it to !ChannelSelect.dfm, which will call out that specific form. If the name of the file is different, modify the property to whatever the actual file name is.

Radio Resources

182 025-9619A

6. Move the button to an acceptable location on the main screen. A good choice would be one that helps to indicate the button is for selecting a radio channel for the specific line resource. Most appropriate would be to place the button on a line resource panel that also holds the line resource.

7. Click the Caption property and change it to something like Line #~Channel Select, to identify it as allowing selection of a radio channel for the specific line.

8. Click the Line(s) property and enter the specific line number for the resource to which you intend to dedicate this button.

9. Leave the remaining button attributes as they are. Save the changes and close the form file.

Testing

At this point, the console screen .dfm file should have either dedicated channel set buttons, a dynamic channel set dialpad, or static channel set dialpads. It could be some combination of the three. The following procedures out line steps to test these various arrangements.

Verifying static channel set button operation:

1. Log into the console position that uses the .dfm file to be tested.

2. Click on one of the Channel Select buttons to be tested. Verify that it turns yellow and that the associated line button turns yellow as well. The line button caption should change to something like “Ch#”, where the # is the channel number you just selected.

3. Verify that the radio connected to this line resource has changed to the correct channel.

4. Select a different channel set button and confirm that once again the resource line button and the radio behave as they should.

Verifying a channel set dialpad — dynamic allocation:


2. Click on the Channel Select button. The button will change to the active function color.

3. Click on the radio line button for the radio on which you wish to change channels. The channel select dialpad should appear.

4. In the channel select dialpad, enter the channel number to which you want to switch the radio. Click the Change button.

5. The message Dialing Complete should appear in the status area at the bottom of the channel select dialpad. The new channel number should appear on the radio resource line button.

6. Verify that the correct tone was sent to the radio and that the radio changed to the requested channel.


183

7. Repeat steps 2 through 6 with several other channels and radio lines in order to confirm that the console programming is correct.

The Channel Select Dialpad can be programmed to automatically close itself after a set period. You may always close the dialpad manually by clicking on the Close button.

Verifying a channel set dialpad — static allocation:


2. Click on the Channel Select button associated with a specific line. The channel select dialpad appears on the screen.

3. In the dialpad panel, enter the channel number to which you want the radio to change. Click the Change button.

4. The message Dialing Complete should appear in the status area at the bottom of the channel select dialpad. The new channel number should appear on the radio resource line button.

5. Verify that the correct tone was sent to the radio and that the radio changed to the requested channel.

6. Repeat steps 2 through 5 with several other channel numbers in order to confirm that the console programming is correct.

The Channel Select Dialpad can be programmed to automatically close itself after a set period. You may always close the dialpad manually by clicking on the Close button.

Troubleshooting

Various factors can affect if the system sends the proper function tone, if at all. Several steps can be performed to troubleshoot, should the system not be operating correctly.

• Improper function tone sent — Verify ALS programming to ensure that the function tone sent for the channel change is what is intended.

• No function tone was sent — Consult the Tone Remote Control section, on page 136, to verify the system is programmed correctly for tone remote to function. Also consult its troubleshooting steps for its proper operation.

Instant Monitor Function Button

The Instant Monitor button is used to allow a radio resource line to be placed in the monitor mode by the single press of an on-screen button.


• The line resource should already be setup in the system.

• Radio line resources should also be programmed on the screen. For the purposes of this example, Radio Line 1 as our radio resource line, which should already be setup on the screen and in the ALS rack.

Radio Resources

184 025-9619A

Required Resources





• Test equipment – used to inject audio on the demarcation block for troubleshooting

Console Screen Changes — Add Instant Monitor Function Button

The following procedure outlines the steps for adding an Instant Monitor function button to the console screen. For the purposes of this example, Monitor Speaker 1 will be used.

Adding an instant monitor function button:



3. Right-click on the Function button tool in the Console Designer tool bar, and then click in the console screen in the approximate location of the new button. A blank button with default settings should appear.

4. In the Object Inspector window for the new button, click on the property Function Type, open the list and scroll down to Monitor Speaker 1, and then select that function. The Object Inspector window will refresh to display the default settings for that type of function button.

5. Select the button attribute Caption and enter the string MON.

6. Select the button attribute Line(s), enter the value 1 (this is the radio line resource for this example).

7. Move the new monitor function button a position on the console screen that helps to indicate that it is tied to a specific line resource. If the line has a dedicated resource panel, that would be the preferred place.

8. Repeat steps 3 through 7 as necessary to add more dedicated instant monitor buttons to the screen .dfm file.

9. Once you have completed all of the editing for the new instant monitor buttons, open the Console Designer File menu and use Save to record the changes to the console screen .dfm file.

To modify existing instant monitor buttons, use the Console Designer application to open the appropriate console .dfm file. Alter the Function Type, Caption, and Line(s) attributes for the existing instant monitor buttons as necessary.


185

Instant Monitor Button — Console Designer Properties

The Console Designer has various properties allowing for customization of the instant monitor function button. The following is several of the common properties:

• Function Type — Settings for this parameter range from Monitor Speaker 1 through Monitor Speaker 4 as well as Monitor Speaker Default. This setting determines which speaker the audio comes out of when the line is being monitored.

• Caption — The text entered for this attribute appears on the face of the function button.

• Color — This attribute sets the default color for the function button.

• Line(s) — This attribute determines which radio line resource is being monitored when the button is selected.

Instant Monitor INI File Settings

The color setting for when the radio line resource has been placed in monitor mode can be changed. The default value is “DBB0B0”. It is located in the [Colors] section, under the Monitor= property. The setting is as follows:

[Colors] Monitor=D9B0B0

Testing

At this point, the Instant Monitor button, or buttons, should be setup on the console form file. The following procedure is for testing the Instant Monitor buttons setup on the screen to ensure they work correctly. Colors referred to are default colors; however, they may be changed inside the AcomConsole.ini file for the console position.

To verify instant monitor button operation:


2. Click the MON button associated with radio line resource 1. If no audio is present on the line, the line resource button should turn orange, with M0(1) displayed at the bottom of the button.

3. Inject audio at the demarcation point and verify that it is present at monitor speaker 1 and that the line resource button turns green.

4. Remove the audio and verify that the line returns to its previous state, button color orange.

5. Click the MON button again and verify that the button changes to its idle state, the color white.

6. Repeat steps 2 through 5 for all of the radio line resources for which instant monitor buttons have been configured.

Radio Resources

186 025-9619A

Troubleshooting

No audio on monitor speaker even though audio is confirmed to be present at the demarcation point

• Verify that the line resource is properly configured in the ALS rack. Also, verify that it has been properly setup on the console form file/screen.

• Verify that the resource is available on the screen (i.e. button not grayed out). If audio is being injected, verify that the button (if so programmed), shows VOX indication that audio is present.

• Verify that the speaker is plugged in and powered on.

Instant TX Function Button

An Instant TX button allows a console operator to transmit on a radio resource line by means of a single press or a single on-screen button.




Required Resources






Console Screen Changes — Add Instant TX Function Button

The following procedure outlines the steps for adding an Instant TX function button to the console screen.

Adding an instant monitor function button:




187


4. In the Object Inspector window for the new button, click on the property Function Type, open the list and scroll down to Instant TX, and then select that function. The Object Inspector window will refresh to display the default settings for that type of function button.

5. Select the Caption attribute and enter the text string Instant TX.

6. Select the Line(s) attribute and set it to 1, which is the radio line resource number being used for this example.

7. Move the new instant TX function button a position on the console screen that helps to indicate that it is tied to a specific line resource. If the line has a dedicated resource panel, that would be the preferred place.

8. Repeat steps 3 through 7 as necessary to add more instant TX buttons to the console screen. Be sure that you modify the Line(s) and Caption settings as necessary to reflect the individual radio line resources to which the function buttons are assigned.

9. Once you have completed all of the editing for the new instant monitor buttons, open the Console Designer File menu and use Save to record the changes to the console screen .dfm file.

To modify existing instant TX buttons, use the Console Designer application to open the appropriate console .dfm file. Alter the Caption, and Line(s) attributes for the existing instant TX buttons as necessary.

Instant TX Button — Console Designer Properties

The Console Designer has various properties allowing for customization of the instant monitor function button. The following is several of the common properties:

• Function Type —This setting determines which the button performs.

• Caption — The text entered for this attribute appears on the face of the function button.

• Color — This attribute sets the default color for the function button.

• Line(s) — This attribute determines which radio line resource is being affected when the function button is selected.

Instant TX Button INI File Settings

The color setting for when the radio line resource has been placed in instant TX mode can be changed. The default value is “FF0000”. It is located in the [Colors] section, under the InstantTX= property. The setting is as follows:

[Colors] InstantTX=FF0000

Radio Resources

188 025-9619A

Testing

At this point, the Instant Tx button or buttons should be programmed on the console form file. To perform an effective test, you should have at least two line resources with two Instant Tx buttons programmed on the form file. The colors indicated in the following procedure are default, however may be changed inside the console’s INI file.

To verify instant TX button operation:


2. Click on the Instant TX button assigned to radio line resource #1. The radio line resource button should turn blue and its caption yellow. The Instant TX button should turn red.

3. Speak into the desk microphone while holding the Instant TX button and verify that the on-screen TX audio level meter fluctuates along with the audio being sent.

4. Have someone check at the demarcation point to verify that the TX audio is reaching that point when the Instant TX button is used.

Troubleshooting

Various factors can affect if the system allows proper operation of the radio line resource.

No audio when instant transmit button is pressed

• Verify that the line resource is properly configured in the ALS rack.

• Verify that the function button has been properly setup on the console form file/screen.

• Verify that the resource is available on the screen (that is, the button is not grayed out).

Resource Audio Volume Function Button

This sub-section covers adding volume control function buttons to the console .dfm file to allow making independent volume setting on individual radio line resources.




Required Resources



189





Console Screen Changes — Add Volume Increase Function Buttons

The following procedure covers the steps required to add function buttons to the screen for increasing the Resource Audio Volume for the selected interface. For the purposes of this example, the radio resource line #1 is used.

To add volume increase function buttons to the screen:




4. In the Object Inspector window for the new button, click on the property Function Type, open the list and scroll down to Resource Audio Volume Increase, and then select that function. The Object Inspector window will refresh to display the default settings for that type of function button.

5. Select the Caption attribute and enter the text string UP.

6. Select the Color attribute and set it to the desired color for that button.

7. Select the Line(s) attribute and set it to 1. This is the radio line resource for this example.

8. Select the Resource Audio Path attribute and set it to Select.

9. Move the new Resource Audio Volume Increase function button a position on the console screen that helps to indicate that it is tied to a specific line resource. If the line has a dedicated resource panel, that would be the preferred place.

10. Make you final size and proportion adjustments to the button.

11. Repeat steps 3 through 10 as necessary to add more Resource Audio Volume Increase function buttons to the console screen. Be sure to modify the Line(s) attribute as necessary to reflect the specific radio line whose audio is to be adjusted.

12. Once you have completed all of the editing for the new Resource Audio Volume Increase buttons, open the Console Designer File menu and use Save to record the changes to the console screen .dfm file.

Radio Resources

190 025-9619A

Console Screen Changes — Add Volume Decrease Function Buttons

The following procedure covers the steps required to add function buttons to the screen for decreasing the Resource Audio Volume for the selected interface. For the purposes of this example, the radio resource line #1 is used.

To add volume decrease function buttons to the screen:




4. In the Object Inspector window for the new button, click on the property Function Type, open the list and scroll down to Resource Audio Volume Decrease, and then select that function. The Object Inspector window will refresh to display the default settings for that type of function button.

5. Select the Caption attribute and enter the text string DN.

6. Select the Color attribute and set it to the desired color for that button.


8. Select the Resource Audio Path attribute and set it to Select.

9. Move the new Resource Audio Volume Decrease function button a position on the console screen that helps to indicate that it is tied to a specific line resource. If the line has a dedicated resource panel, that would be the preferred place.

10. Make you final size and proportion adjustments to the button.

11. Repeat steps 3 through 10 as necessary to add more Resource Audio Volume Decrease function buttons to the console screen. Be sure to modify the Line(s) attribute as necessary to reflect the specific radio line whose audio is to be adjusted.


Console Screen Changes — Adding Volume Gauges

The following procedure will outline the steps required to add a volume gauge to the screen for viewing the Resource Audio Volume level for the selected interface. For the purposes of this example, the radio resource line #1 is used.


191

To add volume gauges to the screen:



3. Right-click on the Gauge tool in the Console Designer tool bar, and then click in the console screen in the approximate location of the new gauge. A blank gauge with default settings should appear.

4. In the Object Inspector window for the new gauge, click on the property Gauge Type, open the list and scroll down to Resource Volume, and then select that function. The Object Inspector window will refresh to display the default settings for that type of gauge.

5. Select the ActiveColor attribute and select the desired color for the gauge.

6. Select the Audio Path attribute and set it to Select.


8. Move the new Resource Volume gauge a position on the console screen that helps to indicate that it is tied to a specific line resource. If the line has a dedicated resource panel, that would be the preferred place.

9. Make you final size and proportion adjustments to the gauge.

10. Repeat steps 3 through 9 as necessary to add more Resource Volume gauges to the console screen. Be sure to modify the Line(s) attribute as necessary to reflect the specific radio line whose audio level is to be viewed.


Modifying Existing Buttons and Gauges

To modify existing volume buttons or gauges, use the Console Designer application to open the appropriate console .dfm file. Once open, click on the button or gauge you wish to alter. This should display the properties for that object. Use the steps in the preceding procedures as guides for the properties that require modification. Save the modified form file when complete.

Testing

At this point, the Resource Audio Volume Adjust buttons (Increase or Decrease) and Volume Gauges should be programmed on the console form file. To perform an effective test, you should have at least two line resources. The colors indicated in the following procedure are default, however may be changed inside the console’s INI file.

Radio Resources

192 025-9619A

To verify volume adjust button and volume gauge operation:


2. At the demarcation point, inject audio on the radio resource line 1.

3. Confirm that the line button for line 1 indicates VOX activity (button blinks a lime green color) and that no audio is heard at the Select audio interface (the line has not been selected yet).

4. Select the radio resource line 1 button. The button should turn solid green with white text on it. Audio should be heard at the selected interface.

5. While listening to the incoming audio, decrease its level by clicking the DN button. The gauge should indicate it is decreasing, as well as the actual audio level dropping. The “V#” label (where # = level) at the bottom of the line key should also indicate the level is reduced.

6. Now click the UP button. Again, note the changes in audio level, the gauge reading, and the “V#” label on the line button.

7. Repeat steps 2 through 6 for all of the lines that have volume buttons or gauges configured.

Troubleshooting

No audio on indication when injecting audio at the line demarcation point


• Verify that the resource is available on the screen (i.e. button not grayed out).

• If audio is being injected, verify that the button (if so programmed), shows VOX indication that audio is present.

• Verify that the speaker is plugged in, powered on, and turned up.

• Verify that the volume resource volume is not already turned down.

Marker Tone Button

This subsection describe how to set up a marker tone for use on radio resource lines.





193

Required Resources






ALS Rack Configuration

For each ALS rack that supports radio line resources that will utilize marker tones, some configuration will need to be done to allow the marker tone to work.

To configure the ALS rack for marker tone operation:

[Configure SMU]

1. Start the IMS ALS terminal.

2. Connect to the ALS rack that holds the line resources you intend to use with the Marker Tone.

3. Locate the SMU card within the rack. Right click on it and select Acom Definitions.

4. Select a channel which has enough DSP Cycles and DSP Memory available to allow adding of the Marker Tone.

5. If creating a new channel definition, select SMU Resource under the System tab of the Connection Type option group to the left of the window.

6. Select User Defined in the SMU Resource in the option group at the top of the window.

7. Locate a timeslot which does not have a black tick mark in the upper right hand corner, which indicates that there is already programming for that timeslot.

8. For the Type column, change the setting from None to Maker Tone.

9. Locate the Tone Encoder column toward the right and check its checkbox.

10. Ensure that the DSP Cycles and DSP Memory values do not exceed the posted maximum.

11. Click the Save button toward the bottom right of the window, which should close it.

12. Click the Close button toward the bottom right of the Channel Definitions window.

[Configure Tone Interval & Duration]

13. Go to the Configure menu and select System Parameters.

Radio Resources

194 025-9619A

14. In the Output Voting option group, change the Idle Time (Sec) to the desired interval/gap, in seconds between the tones. Common interval times are 7 to 10 seconds.

15. Under the same option group, change the Duration (msec) to the duration of the tone in milliseconds. Common tone length is 500ms.

16. Click the Save button

[Save changes to ALS rack]

17. Choose the File menu and select Update to Rack. Follow the guided prompts to allow the configuration to be updated to the rack.

Console Screen Changes — Add Marker Tone Function Button (Dynamic Allocation)

The following procedure covers the steps required to add the Marker Tone function button to the screen. This button will be dynamic, allowing you to set whichever line resource you choose to have the Marker Tone.

To add marker tone function buttons (dynamic) to the screen:




4. In the Object Inspector window for the new button, click on the property Function Type, open the list and scroll down to Priority Marker, and then select that function. The Object Inspector window will refresh to display the default settings for that type of function button.

5. Select the attribute Caption and enter the text string “Priority Marker”.

6. Select the attribute Color and set it to the desired color for the button.

7. Move the new Marker Tone function button an acceptable position on the console screen. Make any necessary final adjustments to its size.

8. Once you have completed all of the editing for the new Marker Tone button, open the Console Designer File menu and use Save to record the changes to the console screen .dfm file.

Console Screen Changes — Add Marker Tone Function Button (Static Allocation)

The following procedure covers the steps required to add a Marker Tone function button to the screen. This button will be statically linked to a specific line resource, allowing you to place the Marker Tone on that line resource.


195

To add marker tone function buttons (static) to the screen:




4. In the Object Inspector window for the new button, click on the property Function Type, open the list and scroll down to Priority Marker, and then select that function. The Object Inspector window will refresh to display the default settings for that type of function button.

5. Select the attribute Caption and enter the text string “Priority Marker”.

6. Select the attribute Color and set it to the desired color for the button.


8. Move the new Marker Tone function button an acceptable position on the console screen. Make any necessary final adjustments to its size.

9. Once you have completed all of the editing for the new Marker Tone button, open the Console Designer File menu and use Save to record the changes to the console screen .dfm file.

Testing

At this point, the ALS rack should be programmed to allocate the necessary resources. The Priority Marker button setup on the console screen should be complete. The following procedures test the Priority Marker (Marker Tone) button to ensure that a tone is being sent out the appropriate radio line resource.

The colors used in the following procedures are defaults. Should the colors on your screen deviate, consult the AcomConsole.ini file and console designer properties for that object to determine the correct color that should be displayed.

Testing a Maker Tone button (dynamic):


2. Click on the Priority Marker button. Verify that the button turns yellow and that the Active Function button shows the priority marker as the active function.

3. Click on the radio line resource button (Line 1 for this example). Verify that the bottom of the line button shows the “PM” label.

4. Monitor the radio line resource at the demarcation point and verify that you hear a tone at the specified interval for the duration previously set.

5. Remove the tone by clicking the Priority Marker button again, and then clicking the line resource button to which the Marker Tone was applied. The tone should no longer be heard at the demarcation point for that radio line resource and the “PM” should disappear from the bottom of the line button.

Radio Resources

196 025-9619A

Testing a Maker Tone button (static):


2. Click on the Priority Marker button.

3. Verify that the bottom of the radio line resource button shows the “PM” label. (Line 1 for this example)

4. Monitor the radio line resource at the demarcation point and verify that you hear a tone at the specified interval for the duration previously set.

5. Remove the tone by clicking the Priority Marker button again. The tone should no longer be heard at the demarcation point for that radio line resource and the “PM” should disappear from the bottom of the line button.

Troubleshooting

No marker tone present

• Verify SMU resources have not been exceeded.

• Verify “PM” is displayed on the intended line resource button.

• Ensure audio is passing through the line by sending voice.

Squelch Disable

The Squelch Disable function button allows a console operator to remotely disable a base radio’s squelch function through the radio interface.


• The line resource should already be configured for Tone Remote Control (TRC)

• Radio line resources should also be programmed on the screen. For the purposes of this example, Radio Line 1 as our radio resource line, which should already be setup on the console screen and in the ALS rack.

Required Resources







197

ALS Rack Configuration

For each ALS rack that hosts radio line resources that will utilize the Squelch Disable feature, some configuration will need to be done to allow the Squelch Disable function to work.

One of the following setup procedures assumes the use of a specific Radio Tone Database. For the purposes of this example, the assumption is that it is “Tone Index 1”.

To configure the ALS rack for squelch disable operation:

[Configure Function Data in ALS Rack]

1. Start IMS ALS.

2. Connect to the ALS rack which holds the line resources you intend to use with the Squelch Disable function.

3. Go to the Configure menu and select Function Data.

4. For the Type column, click in the blank space. Open and expand the list. Scroll down and select Tone Remote Radio.

5. The window will refresh to allow entry of the TRC frequency information. Enter the frequency used for Squelch Disable in Function 1 Freq (this will generally be “2050”.

6. Select the Tone Database you intend to use. In this example, “1”. (Again, this corresponds to the information within the Configure > Radio Tone Database menu option.

7. When you have finished entering tone selections, click the OK button. The window should change back to the function matrix.

8. Under the Feature column, choose the Squelch Disable option from the dropdown box.

9. Click the Save Function Data button. Then click the Exit button to close the window.

[Save Changes to ALS rack]

10. Choose the File menu and select Update to Rack. Follow the guided prompts to allow the configuration to be updated to the rack.

Console Screen Changes — Add Squelch Disable Function Button

The following procedure outlines the steps required to add the Squelch Disable to the console screen .dfm file.

Radio Resources

198 025-9619A

To add the squelch disable function button:




4. In the Object Inspector window for the new button, click on the property Function Type, open the list and scroll down to Acom Function, and then select that function. The Object Inspector window will refresh to display the default settings for that type of function button.

5. Select the Caption attribute and enter the text string Squelch Disable.

6. Select the Color attribute and set it to the desired color for the button.

7. Select the Function Number attribute and set it to the function number configured during the ALS programming. For this example, that is function number “1”.

8. Select the Line(s) attribute and set it to the desired radio resource line number. For this example, the number is “1”.

9. Move the new Squelch Disable function button an acceptable position on the console screen. Make any necessary final adjustments to its size.

10. Once you have completed all of the editing for the new Squelch Disable button, open the Console Designer File menu and use Save to record the changes to the console screen .dfm file.

Testing

At this point, the ALS rack should be programmed to allocate the necessary resources. The Squelch Disable button setup on the console screen should be complete. The following procedures test the Squelch Disable button to ensure that a tone is being sent out the appropriate radio line resource.

The colors used in the following procedures are defaults. Should the colors on your screen deviate, consult the AcomConsole.ini file and console designer properties for that object to determine the correct color that should be displayed.

To test the squelch disable button:


2. While monitoring the demarcation point for the line resource, click on the Squelch Disable button.

3. Verify that the correct TRC tone is sent by the system and that the bottom of the radio line resource button now displays the “SD” label.

4. Transmit on that channel and verify that the “SD” label is removed from the radio line resource button.


199

Troubleshooting

Various factors can affect if the system sends the proper function tone, if at all. Several steps can be performed to troubleshoot the problem, should the system not be operating correctly.

• Improper function tone sent Verify ALS rack programming to ensure that the function tone sent for squelch disable is what is intended.

• No function tone was sent Consult the Tone Remote Control section on page 136 to verify the system is programmed correctly for tone remote to function. Also consult its troubleshooting steps for its proper operation.

Radio Resources

200 025-9619A


201

Telephone Line Resources

This section contains information taken from various application notes developed at Zetron covering the management of telephone-related line resources in an Acom system.

The following is a quick list of the topics covered and the pages they start on:

Enabling Caller ID for Incoming Calls 202

Setting up a Call History Panel 206

Setting up an Answer Next Function Button 208

Setting up a Call Queue Function Button 209

Setting up a Console Telephone Line Transfer Function Button 213

Setting up a Hold Function Button 215

Setting up a Hunt Group Dialpad Function Button 219

Setting up a Ring Enable/Disable Function Button 223

Setting up a Selected Telephone Line Dialpad Function Button 225

Setting up a Speed Dial Function Button 228


202 025-9619A

Enabling Caller ID for Incoming Calls

This subsection explains how to enable the Caller ID function for a Telephone line resource.

Required Resources




• Acom hardware module manuals for Main Control Units (MCU) (025-9602), Exchange Interface Units (EIE) (025-9616), and E&M Units (EMU) (025-9617)

• Telephone line simulator or an actual telephone system capable of sending caller ID information to the Acom system

SMU Programming

A telephone resource/line requires an SMU resource be assigned to decode incoming Caller ID signals.




Once you have reviewed all SMU resources in the rack, see if there is already an SMU resource assigned for Caller ID Decoder. Generally this type of resource is dynamic and is not static to a specific telephone line. The SMU Type and Extra column will show None and “0”. The Caller ID Decoder column will simply be checked.

Since the telephone resource/line should already be setup in the system, there should be SMU resources already allocated to act dynamically for VOX Detector. In a typical system, there should be enough dynamic resources for all the telephone lines in the system to use those resources. For example, if you have 3 telephone lines, you should have 3 dynamically allocated VOX Detector resources setup in the SMU.


203

If you find the VOX Detector resources, but not the Caller ID Decoder, you simply need to enable the decoder for the caller ID on the same resource that supports the VOX detector. Generally speaking, transmit and receive resources are setup on their own timeslots. For instance, DTMF encoders would be on separate timeslots from the DTMF decoder, etc. In this case, our receive resources for the telephone line would require VOX detectors and the addition of the caller ID decoder, to work correctly.

Note AGC is not necessary on telephone lines as this is generally

handled by the CO. No AGC resource should be checked for the timeslot used for VOX Detector or Caller ID Decoder.



2. Assign a dynamic VOX Detector and Caller ID Detector for the telephone lines.

3. After making the VOX Detector and Caller ID Detector assignments, check that the DSP Memory required does not exceed the allocated amount. If the limit for DSP Memory is exceeded, the memory information in the bottom of the SMU dialog turns red.



Line Resource Programming

The telephone resource/line will require options set to enable Caller ID decoding.

Programming the telephone line for caller ID decoding:

1. Use either IMS ALS or IMS Terminal to access the ALS rack that contains the resource, and then right-click on the MCU card in slot0 or slot1, select Acom Definitions and select Link1 or Link2. Continue to access the MCU Acom Definitions and links until you locate the telephone line you wish to program. Once the correct telephone line has been located, click on it to open its properties.

2. With the telephone line properties window open, in the Connection Type pane on the left, click the Line Channel button to display all tabs and settings.


204 025-9619A

3. Click on the right arrow indicator in the upper right corner of the window until the Caller ID tab is displayed. Select the Caller ID tab.

4. In the Type sub-pane, click the Enable Decoder button.

5. The Decoder sub-pane should appear. The default settings for this pane are: Standard = Bellcore (Bell 202), Minimum Decode Level = -40.0 dBm, and Ring Interval = 6.0 secs. Leave the default settings as they are.

6. Click the Save and then the Close button.

Editing the AcomConsole.ini File Settings

The AcomConsole.ini file has a section labeled [Telephone Lines], which contains various options. It is recommended that you leave all settings at their default values, with the exception of removing the several parameters that may be commented out (that is, the line is preceded by a “;” semicolon).

AnswerLongString=text

Specifies a long version of the string to be displayed in conjunction with the answering phone number. Used in the Call Queue Panel. Any ASCII text string is valid. Default is Number Called.

AnswerShortString=text

Specifies a short version of the string to be displayed in conjunction with the answering phone number. Used as a prefix to the number on dynamic line buttons. Any ASCII text string is valid. Default is CND.


205

Generally the INI file should look something like the following: [Telephone Lines] AnswerLongString=Number Called AnswerShortString=CND

If either of the two options AnswerLongString= or AnswerShortString= are preceded by a semicolon (;), remove the semicolon from the beginning of the line.

Testing

To verify that caller ID is displayed on telephone line resource button:

1. With the telephone line in its idle state, generate a telephone call to it. This call should have the ability to send caller ID information with the call.

2. The caller ID information that is sent should show up on the button as well as the Telephone Call History panel.

Tip Once the telephone line is confirmed to be functional, always

perform an Update to Rack to permanently save your settings. If an Update to Rack is not performed, any programming settings configured will be lost if the rack is reset.



Troubleshooting

• If caller ID information is not displayed, verify that the telephone simulator/phone switch used to call into the Acom system is sending a proper caller ID string within the telephone call.

• A rack reset may be needed to make the changes to card programming take effect. Prior to performing the reset, duplicate the programming on the inactive rack (if the system has a Main/Standby configuration). Once both racks have been programmed, access the File menu and perform an Update to Rack on both racks. Reset the inactive rack and wait 2 minutes. Perform a change over to the rack that was reset then reset the other rack.

• If caller ID information still is not displayed, go through all changes in the ALS and AcomConsole.ini file to ensure they were setup correctly.


206 025-9619A

Setting up a Call History Panel

This section describes the steps necessary to create an on-screen display of telephone call history.

For the purposes of this section, it is assumed that the telephone lines have already been set up in the ALS rack and buttons programmed for them on the console screen.

Required Resources






Console Screen Changes — Add Telephone Call History Panel

The following procedure covers the steps to add a Call History - Telephone panel to the console screen .dfm file.

Adding a telephone call history panel to the console screen:



3. Right-click on the Panel button in the tool bar. Click on the console screen in the approximate location for the telephone call history panel. The new panel should appear in that location with default settings.

4. In the Object Inspector window for the new panel, click on the Panel Type attribute. Open the list for that setting and scroll down to Call History Telephone and select it. The Object Inspector window should refresh with the default settings for that panel type.

5. Make any desired adjustments to the panels size and location.

6. Once you have completed all of the editing for the telephone call history panel, open the Console Designer File menu and use Save to record the changes to the console screen .dfm file.

Setting up a Call History Panel

207

Editing the AcomConsole.ini File Settings for Lines and Hunt Group

The following AcomConsole.ini file settings determine which line activity gets included in the Call History window. These settings ensure that dynamic line buttons are included (dynamic line buttons cannot be checked at startup). Generally static type lines are not required to be added to this list.

For the purposes of this example, lines 201 to 206 are dynamically assigned. The next setting allows specification of a hunt group to be used for answering entries in the call history window.

[Call History] IncludeLines=201-206 Huntgroup=HG1

If any of the above sections or settings are commented out by the presence of a semicolon (;) at the beginning of the line, remove it. The AcomConsole.ini file has comments for easy reference to options or even how a setting operates. In addition, unused settings are commonly commented out, while others require the setting to be present with nothing after the equals sign. It is STRONGLY recommended to leave all options as default, unless otherwise advised by Zetron technical support.

Testing

At this point, the Call History Telephone panel should be programmed on the console screen. To perform an effective test, you should have at least two telephone line resources setup on the screen.

To verify Call History Telephone panel operation:

1. Log in to the Acom console position with the newly configured Call History Telephone panel.

2. Verify that all line resources are in their idle states.

[Inbound Call Test]

3. Generate an inbound call to the console on a line that provides caller ID information. Answer the call.

4. Verify that the line resource indicates the call and displays the caller ID information on the line button.

5. Check the Call History panel. It should display the date/time, caller ID (in the Number column), type of call (inbound/outbound), and the call duration. The duration should be counting up.

6. Answer the call, and then release it. The duration counter should have stopped.

[Outbound Call Test]

7. Generate an outbound call from the console.


208 025-9619A

8. After verifying voice communications on the line, the call history panel should display the date/time, the number dialed, type of call, and the duration (still counting up).

9. Release the call. The duration counter should stop.

Troubleshooting

• Verify that the telephone line resources are properly configured in the ALS rack

• Verify the telephone line resources and the call history panel are properly configured in the console screen .dfm file

• Verify that the resources are available on the active console screen (that the buttons are not grayed out)

• If the entry does not populate in the call history panel on an inbound call, verify that the line resource does not have its ringer disabled (RD).

Setting up an Answer Next Function Button

This section covers setting up an Answer Next button for use with telephone lines. This type of button allows a console operator to answer the next call in the queue of incoming calls by means of a single press of an on-screen button.


Required Resources






Console Screen Changes — Add an Answer Next Function Button

The following procedure covers the steps to add an Answer Next function button to the console screen .dfm file.

Setting up an Answer Next Function Button

209

Adding an Answer Next function button to the console screen:



3. Right-click on the Function button in the tool bar. Click on the console screen in the approximate location for the Answer Next button. The new button should appear in that location with default settings.

4. In the Object Inspector window for the new button, click on the property Function Type, open the list and scroll down to Answer Next, and then select that function. The Object Inspector window will refresh to display the default settings for that type of function button.

5. Select the button attribute Caption and enter the string Answer Next.

6. Select the button attribute Color, enter the desired button color.

7. Move the new Answer Next function button a position on the console screen that helps to indicate that it is tied to a specific line resource. If the line has a dedicated resource panel, that would be the preferred place.

8. Once you have completed all of the editing for the new function button, open the Console Designer File menu and use Save to record the changes to the console screen .dfm file.


The AcomConsole.ini file has a setting to allow the radio lines to be answered by clicking the Answer Next button. Consider this setting when planning the use of the Answer Next button. The following is an example of the setting within the AcomConsole.ini file:

[Incoming Call Queue] AllowRadioInAnswerNext=False

Testing

At this point, the Answer Next button should be programmed on the console screen. To perform an effective test, you should have at least two telephone line resources setup on the screen.

Verifying Answer Next button operation:

1. Log in to the Acom console position with the newly configured Answer Next button.

2. Generate an inbound call on the first telephone line. Make sure that the Call Queue or Call History panel is displayed and that the inbound call show up on it.

3. Generate a second inbound call on another telephone line. Verify that it too shows up on the list. (The queue is sorted according to whatever sorting order is defined in the AcomConsole.ini file.)


210 025-9619A

4. Click on the Answer Next button. Verify that the call at the top of the list is answered and that voice communications are possible. The call should be removed from the queue list.

5. Click on the Answer Next button again. Verify that the second call is answered and that voice communications are now possible. The second call should be removed from the queue list. The original telephone call should have been disconnected and its line placed back in its idle state.

6. Release the second call and verify that its line returns to its idle state.

7. The call queue should now be empty and both phone line should be idle.

Note The sorting order for the call queue can affect which call is

answered when using the Answer Next button.

Troubleshooting

Nothing happens when Answer Next button is pressed.

• Verify that the line resource is properly configured in the ALS. Also, verify that it has been properly setup on the console form file/screen.

• Verify that the resource is available on the screen (i.e. button not ‘grayed’ out).

• Verify the sorting order for the queue.

Setting up a Call Queue Function Button

This section covers the setup of a Call Queue button on the console screen. A Call Queue function button is used to display the call queue window, when pressed. Whether or not the contents of the call queue window are sorted in any specific manner is controlled by settings contained in the AcomConsole.ini file.


Required Resources




Setting up a Call Queue Function Button

211



Console Screen Changes — Add a Call Queue Function Button

The following procedure covers the steps to add an Call Queue function button to the console screen .dfm file.

Adding a Call Queue function button to the console screen:



3. Right-click on the Function button in the tool bar. Click on the console screen in the approximate location for the Call Queue button. The new button should appear in that location with default settings.

4. In the Object Inspector window for the new button, click on the property Function Type, open the list and scroll down to Call Queue, and then select that function. The Object Inspector window will refresh to display the default settings for that type of function button.

5. Select the button attribute Caption and enter the string Call Queue.


7. Move the new Call Queue function button a position on the console screen that helps to indicate that it is tied to a specific line resource. If the line has a dedicated resource panel, that would be the preferred place.


Editing the AcomConsole.ini File Settings — Determining Sort Order

The AcomConsole.ini file contains a parameter that determines whether the contents of the Call Queue window get sorted, and if so how. The following is an example of the default setting (no sorting).

[Incoming Call Queue] OperationMode=-1

When the parameter OperationMode= is set to -1, no sorting occurs in the call queue window. The settings 1, 2, and 3 cause the call records to be sorted on specific fields.

1 = by Time

2 = by Line

3 = by Call Type


212 025-9619A

If you require that the call queue sort the calls, change the OperationMode= parameter to provide the sorting you require.

Note If the start of the line in the AcomConsole.ini file for the option

or section above is commented out by the presence of a “;” (semicolon), simply remove it. This only applies to the section heading [Incoming Call Queue] and OperationMode= setting.

Testing

At this point, the Call Queue button should be programmed on the console screen. To perform an effective test, you should have at least two telephone line resources setup on the screen.

To verify the Call Queue button operation:

1. Log in to the Acom console position with the newly configured Call Queue button.

2. Click on the Call Queue button. The Call Queue window should open.

3. Generate an inbound call on the first telephone line. The call should be displayed in the Call Queue window.

4. Generate a second inbound call on another telephone line, without picking up the first call. Verify that it too shows up in the Call Queue window. (The queue is sorted according to whatever sorting order is defined in the AcomConsole.ini file.)

5. Click on either one of the line resource buttons. Verify that it is now the selected telephone line and that voice communications are now possible. That line should also have been removed from the Call Queue list.

6. Click on the other line resource button. Verify that it is now the selected telephone line and that voice communications are now possible. The line picked up in step 5 should now be disconnected. The Call Queue list should now be empty.

7. Click the active line button again to terminate the call. The telephone resources should all be idle at this point.

Troubleshooting

The Call Queue does not sort calls correctly

• Verify that the queue sort order has been set in the AcomConsole.ini file.

• Verify that the necessary section and option lines in the AcomConsole.ini file are not commented out by semicolons (;).

Setting up a Console Telephone Line Transfer Function Button

213

Setting up a Console Telephone Line Transfer Function Button

This section covers setting up a function button to transfer a telephone call from one console to another console in the Acom system.

For the purposes of this section, it is assumed that the telephone lines have already been set up in the ALS rack and buttons programmed for them on the console screen. In addition, a direct console intercom button must be created between this console and another console in the system.

Required Resources






Console Screen Changes — Add a Transfer Function Button

The following procedure covers the steps to add an Transfer function button to the console screen .dfm file.

Adding a Transfer function button to the console screen:



3. Right-click on the Function button in the tool bar. Click on the console screen in the approximate location for the Transfer button. The new button should appear in that location with default settings.

4. In the Object Inspector window for the new button, click on the property Function Type, open the list and scroll down to Transfer, and then select that function. The Object Inspector window will refresh to display the default settings for that type of function button.

5. Select the button attribute Caption and enter the text string Transfer.


7. Move the new Transfer function button an acceptable position on the console screen. Generally, telephone buttons of a similar nature are grouped together for ease of use.


214 025-9619A



The AcomConsole.ini file offers the following parameters for configuring the operation of the Transfer button.

• AlternateTransfer This parameter specifies which method is used to transfer a call to another console, the standard method or alternate method. The standard method requires an intercom call to be established between the two consoles prior to selecting the Transfer button. The alternate method requires the Transfer button to be selected first, after which the target console is selected by way of a console selection panel. Please note that False (use the standard method) is the default for this option.

• UseDynamicIfStaticDisabled This specifies whether to redirect the call to a dynamic line button if a call is transferred to a console that has the static line disabled.

Example of both options from the AcomConsole.ini file: [Call Transfer] AlternateTransfer=False UseDynamicIfStaticDisabled=True

If any of the [Call Transfer] options are commented out (preceded by a semicolon (;)), remove the leading semicolon.

Testing

At this point, the Transfer button should be programmed on the console screen. To perform an effective test, you should have at least two telephone line resources setup on the screen.

To verify the Transfer button operation:

1. Log in to the Acom console position with the newly configured Transfer button.

2. Generate an inbound call (or place an outbound call) on the first telephone line.

3. Connect the call and verify that voice communications are possible on the line.

4. Initiate an intercom call to another console position. When the other console answers, verify that voice communications are possible between the two positions.

5. Click on the Transfer button. The telephone line should now be ringing at the target console. The telephone line resource button at the originating console should display the text “H Tr-Op#”, where the # shown is console position

Setting up a Hold Function Button

215

number of the console receiving the call. At the target console position, the telephone line button should display the text “TR-Op#”, where the # indicates the console position that is transferring the call

6. At the target console position, answer the line and verify that the telephone call was successfully transferred. In addition, verify that the telephone line resource is no longer selected at the console that originated the transfer.

7. At the target console, click the active line button to terminate the telephone call. The telephone resources should all be idle at this point.

Troubleshooting

Transferring a call does not appear to work correctly

• Verify that the line resource is properly configured in the ALS. In addition, verify that it has been properly setup on the console form file/screen.

• Verify that the resource is available on the screen (that is, button not grayed out).

• Verify the console intercom button has been setup on the screen and is available (that is, button not grayed out).

• Double check AcomConsole.ini file settings.


This section covers setting up a function button to place a telephone call on hold.


Required Resources







216 025-9619A

Console Screen Changes — Add a Hold Function Button

The following procedure covers the steps to add an Transfer function button to the console screen .dfm file.

Adding a Hold function button to the console screen:



3. Right-click on the Function button in the tool bar. Click on the console screen in the approximate location for the Hold button. The new button should appear in that location with default settings.

4. In the Object Inspector window for the new button, click on the property Function Type, open the list and scroll down to Hold, and then select that function. The Object Inspector window will refresh to display the default settings for that type of function button.

5. Select the button attribute Caption and enter the text string Hold.


7. Move the new Hold function button an acceptable position on the console screen. Generally, telephone buttons of a similar nature are grouped together for ease of use.



This section covers configuration of the AcomConsole.ini file settings.

Button Colors

The color of the telephone line resource that is placed on hold can be configured the AcomConsole.ini file. Under the [Colors] section in the file, there should be a Hold= parameter. Change this parameter to determine the color of the line button when it is placed in hold. There is an additional parameter to determine the color of a telephone line placed on hold by another console in the system (remote). This parameter is called RemoteHold=.

Note When a line is remotely placed on hold by another console, all

other consoles in the system will show an “H” at the bottom of the telephone line resource button as well as change the button color to the color set by the RemoteHold= parameter.


217

The following is an example of what you would find in the AcomConsole.ini file. The color settings used are the default values for these parameters.

[Colors] Hold=0080FF RemoteHold=00FFFF

If the Colors heading or either of the Hold color parameters are commented out by a semicolon, uncomment them by removing the semicolon from the start of the line.

Hold Functionality

The functionality of the Hold button can be specified by changed the number that appears after the HoldFunctionality= parameter.

• 0 = If only one line is currently selected, clicking Hold puts that line on hold. If multiple lines are selected, the operator must first click Hold, and then click the line to be put on hold. Clicking the Hold button cannot be used to take lines off hold. This is the default setting for HoldFunctionality=.

• 1 = Lines are put on hold by clicking Hold, then clicking the line to be put on hold. If one or more lines are on hold, and there are no other selected lines, clicking the Hold button takes longest held call off hold.

The following is an example of what you would find in the AcomConsole.ini file. [Line Selection] HoldFunctionality=0

Hold Priority

This setting within the AcomConsole.ini file that allows for specifying the line priority level at which the line may no longer be placed on hold. For example, if the parameter HoldPriority= is set to 2, only lines with a priority of 0 or 1 can be put on hold. Default setting for this parameter is to leave it blank. This allows for all lines (of any priority) to be placed hold.

The following is an example of the default setting for HoldPriority= in the AcomConsole.ini file.

[Line Selection] HoldPriority=

Hold Warning

The console has the capability to play an audible warning tone whenever a line has been left on hold for longer than the hold warning timeout period. Both the timeout period and the Wave file to be played as a warning can be configured with parameters found in the AcomConsole.ini file.


218 025-9619A

The following lines provide an example of the parameters found in the AcomConsole.ini file.

[Timeout Periods] HoldWarning=30 [Sounds] HoldWarning=HoldWarning.wav

Testing

At this point, the Hold button should be programmed on the console screen. Any editing of the parameters in the AcomConsole.ini file should have been completed. To perform an effective test, you should have at least two telephone line resources setup on the screen. This will only test the defaults.

To verify Hold button operation — standard operation:

1. Log in to the Acom console position with the newly configured Hold button. Verify that all of the telephone lines are in their idle states.

2. Generate an inbound or outbound telephone call on one of the lines.

3. Answer the call and verify that two-way voice communications are possible.

4. Place the call on hold by clicking the Hold button. Verify that the line resource button changes to the programmed hold color.

5. Click the line resource button and verify that the call came off of hold. The line button should change back to its call-in-progress color and the voice audio resumes.

6. Release the line and it should return to its normal idle state.

To verify Hold button operation — the hold timeout test:

1. Log in to the Acom console position with the newly configured Hold button. Verify that all of the telephone lines are in their idle states.

2. Generate an inbound or outbound telephone call on one of the lines.

3. Answer the call and verify that two-way voice communications are possible.

4. Place the call on hold by clicking the Hold button. Verify that the line resource button changes to the programmed hold color.

5. Wait for 30 seconds and verify that the audible alert is played over the console speaker.

6. Click on the line resource button for the line on hold. Verify that the alert stops, the line button changes back to the color for a selected line, and that voice communications are restored.

7. Release the line and it should return to its normal idle state.

Setting up a Hunt Group Dialpad Function Button

219

Troubleshooting

Hold button does not appear to work correctly

• Verify that the AcomConsole.ini file settings are set correctly for the intended operation.

• Verify that the line resource is properly configured in the ALS. In addition, verify that it has been properly setup on the console form file/screen.



This section covers setting up a function button on the console screen to open the Hunt Group Dialpad window.

Hunt group dialing is used when you wish to dial out a specific set of lines, letting the Acom system pick the specific idle line to use. Using the button on the screen will open the dialpad. Enter the number you intend to dial, and then press send. The Acom will determine the next available/idle line in a predetermined list, select it, and dial the number entered.


Required Resources







220 025-9619A

Console Screen Changes — Add a Speed Dial - Telephone Function Button

The following procedure covers the steps required to add the function button for displaying the Hunt Group dialpad to the screen.

To add a speed dial- telephone function button to the console display:



3. Right-click on the Function button in the tool bar. Click on the console screen in the approximate location for the Hunt Group Dialpad button. The new button should appear in that location with default settings.

4. In the Object Inspector window for the new button, click on the property Function Type, open the list and scroll down to Speed Dial - Telephone, and then select that function. The Object Inspector window will refresh to display the default settings for that type of function button.

5. Select the button attribute Caption and enter the text string Hunt Group~Dialpad.


7. Select the button attribute Line(s) and enter the number for a predefined hunt group set up in the AcomConsole.ini file. This would be an entry like “HG1”. Alternatively, you may just define a range of telephone lines directly, for example “201-206” (minus the quotation marks).

8. Select the button attribute SourceFile and enter the location and name for the dialpad.dfm file to be used for this dialpad. The label “!DialPad.dfm” is the one most commonly used for this file.

Note The dialpad DFM file “!DialPad.dfm” is generic and should not

require modification directly. Most properties affecting it can be modified on the function button being created, in the Object Inspector window.

9. Move the new Hunt Group Dialpad function button an acceptable position on the console screen. Generally, telephone buttons of a similar nature are grouped together for ease of use.


The following graphic shows an example of the Object Inspector window filled out with typical settings for a Hunt Group Dialpad function button.


221


To enter a hunt group name in the Line(s) property for the dialpad, that hunt group must be setup in the AcomConsole.ini file.

Locate the [Line Groups] section within the AcomConsole.ini file. Below that section heading and before the next section in brackets, you will enter a line/hunt group. Use the examples within the AcomConsole.ini file for guidance. The general structure of the group is as follows:

• Individual Line: text=#

• Non-consecutive Lines (separated by commas): text=#,#

• Consecutive Lines (starting line then hyphen followed by last line): text=#-#

The “text” variable is a set of ASCII characters without spaces. Then, depending upon the group of lines you wish to use, you either enter one telephone line, non-consecutive multiple telephone lines, or a set of consecutive lines, that is 201-206.

Generally if you require the use of only one line in the group, to limit confusion, it is best to enter that line directly in the Line(s) property of the function button in the Console Designer.


222 025-9619A

An example of a properly setup hunt group in the AcomConsole.ini file would be: [Line Groups] HG1=201-206

Testing

To verify that a Hunt Group Dialpad function button works:

1. Log in to the Acom console position with the newly configured Hunt Group Dialpad button. Verify that all of the telephone lines are in their idle states.

2. Click on the Hunt Group Dialpad function button. The dialpad window should open.

3. In the dialpad window, enter the telephone number to dial and click the Send button.

4. Verify that the first available telephone line in the hunt group is selected and the number you entered is dialed.

5. At this point the dialpad window should either time out (defined in the AcomConsole.ini file) and close on its own or you may manually close it.

Troubleshooting

Dialpad is displayed however nothing happens after you click Send

• Verify that the correct telephone line resources are being called out in the hunt group and that those resources are available.

• Consult the Maintenance manual for troubleshooting steps related to telephone line resources.

Dialpad is displayed but does not work

• In the console designer, ensure that the Function Type selected for this button is Speed Dial – Telephone and NOT Screen – Show. While the screen will display with this button, the console will not understand how to use it correctly.

Dialpad does not display

• Verify that the dialpad DFM file called out in the function button exists in the location specified.

• Verify that the location and filename called out, are correct.

Setting up a Ring Enable/Disable Function Button

223

Setting up a Ring Enable/Disable Function Button

This section covers setting up a function button that will disable or enable the ringer for a telephone line resource.


Some Basics of Telephone Line Ringers

The ringer of the telephone line resource can either be enabled or disabled by a single button press. Which occurs depends on current state of the ringer. If the ringer for a particular line is currently disabled, pressing the ring disable button will actually enable the ringer. This is particularly important as you can setup the telephone line resource to disable its ringer when the console is started. If the telephone line resource button text says RD at the bottom, this indicates that the ringer has been disabled for that line.

Required Resources






Console Screen Changes — Add a Ringer Disable - Function Button

The following procedure covers the steps required to add a Ring Disable function button to the console screen.

To add a ringer disable- telephone function button to the console display:



3. Right-click on the Function button in the tool bar. Click on the console screen in the approximate location for the Ring Disable button. The new button should appear in that location with default settings.

4. In the Object Inspector window for the new button, click on the property Function Type, open the list and scroll down to Ring Disable, and then select


224 025-9619A

that function. The Object Inspector window will refresh to display the default settings for that type of function button.

5. Select the button attribute Caption and enter the text string Ring~Disable.


7. Select the button attribute Line(s) and enter the line number for the telephone line resource for which you wish to disable the ringer.

8. Move the new Ring Disable function button an acceptable position on the console screen. Generally, telephone buttons of a similar nature are grouped together for ease of use. Since this button is line specific, a position close to its line resource button would make sense.

9. Repeat steps 3 through 8 as necessary to additional Ring Disable buttons for each telephone line that requires one.


Testing

At this point, the Ring Disable button should be programmed on the console screen. To perform an effective test, you should have at least two telephone line resources setup on the screen.

To verify Ring Disable button operation — test starts with ringer enabled:

1. Log in to the Acom console position with the newly configured Ring Disable button. Verify that all of the telephone lines are in their idle states.

2. Generate an inbound telephone call on one of the lines with a Ring Disable button assigned to it. The console should play a ring sound to announce the incoming call.

3. Answer and release the call in order to return the line to an idle state.

4. Click the Ring Disable button assigned to the line you used in step 2. Note that the label RD should now be displayed at the bottom of the line button.

5. Generate an inbound call on the same line used in step 2. Note that this time, while there is a visual indication that there is an incoming call, no audible ringer is heard.

6. Answer the line and verify that voice communication is possible.

7. Disconnect the line and enable the ringer again by clicking the Ringer Disable button. The RD label should disappear from the in button.

8. If desired, generate another incoming call to confirm that the ringer for this line is once again enabled.

Setting up a Selected Telephone Line Dialpad Function Button

225

Troubleshooting

Ring Disable button does not appear to work correctly


• Verify that the resource is available on the screen (i.e. button not grayed out). If the button already has an RD label on the bottom line of the button, its ringer is already disabled.

• Check the button properties to verify whether the line is configured to be disabled when the console starts up.


This section covers adding a function button to the console screen that will display a Selected Telephone Line Dialpad.

This dialpad is used when you wish to dial through a specific line, much in the same way you would a cell phone. After displaying the dialpad, you can enter the number in the dialpad; however, you have to click the Send button before the line is selected and the digits are dialed.


Required Resources







226 025-9619A

Console Screen Changes — Add a Speed Dial - Telephone Function Button

The following procedure provides the steps necessary to add a function button to the console screen that will display the Selected Telephone Line Dialpad.

To add a speed dial - telephone function button to the console display:



3. Right-click on the Function button in the tool bar. Click on the console screen in the approximate location for the Speed Dial - Telephone button. The new button should appear in that location with default settings.


5. Select the button attribute Caption and enter the text string Dialpad.


7. Select the button attribute Line(s) and enter SELECTED. Another option would be to enter group of line numbers. The format for this is A-B (where A is the starting line number and B is the ending line number, for example 201-206). That allows only selected liens within that group to be used with this function button.

8. Select the button attribute SourceFile and enter the location and name for the dialpad.dfm file to be used for this dialpad. The label “!DialPad.dfm” is the one most commonly used for this file.

Note The dialpad DFM file “!DialPad.dfm” is generic and should not

require modification directly. Most properties affecting it can be modified on the function button being created, in the Object Inspector window.

9. Move the new Dialpad function button an acceptable position on the console screen. Generally, telephone buttons of a similar nature are grouped together for ease of use.


The following graphic shows a typical Object Inspector window for Speed Dial - Telephone function button.


227

Testing

To verify the selected telephone line dialpad function button works:

1. Log in to the Acom console position with the newly configured Dialpad function button. Verify that all of the telephone lines are in their idle states.

2. Click on the Dialpad function button. The button should begin flashing yellow.

3. Click on the telephone line resource button for the line on which you intend to place the outbound call.

4. Enter the telephone number to be dialed on the dialpad and then click the Send button.

5. After clicking the Send button on the dialpad, verify that the line you indicated is selected, the number is dialed, and ringing starts on the other end of the call.

6. The dialpad should timeout and close on its own as defined in the AcomConsole.ini file. Alternatively, you can click on the Close button in the dialpad to close it manually.


228 025-9619A

Troubleshooting

Dialpad is displayed however nothing happens after send

• Consult the Maintenance manual for troubleshooting steps related to telephone line resources.

Dialpad is displayed but does not work

• In the console designer, ensure that the function button has its Function Type set to Speed Dial – Telephone and NOT to Screen – Show. While the console screen will display a Screen – Show button, the console will not understand how to use it correctly.

Dialpad does not display

• Verify that the dialpad DFM file called out in the function button Object Inspector window actually exists in the location specified.

• Verify that the location and filename called out, are correct.

Setting up a Speed Dial Function Button

This section covers adding a function button to the console screen which opens a dialpad window from which the operator can quick dial a predefined telephone number on a predefined telephone line.


Required Resources






Setting up a Speed Dial Function Button

229

Console Screen Changes — Add a Speed Dial Function Button

The following procedure provides the steps necessary to add a function button to the console screen that will display the Speed Dial dialpad.

To add a speed dial function button to the console display:



3. Right-click on the Function button in the tool bar. Click on the console screen in the approximate location for the Speed Dial - Telephone function button. The new button should appear in that location with default settings.


5. Select the button attribute Caption and enter a text string that identifies this function button by its purpose, line, and preset telephone number.


7. Select the button attribute DialString; enter the telephone number to be dialed when this function button is used.

8. Select the button attribute Line(s) and enter telephone resource line number that is to be used when this function button is used.

9. Move the new Speed Dial function button an acceptable position on the console screen. Generally, telephone buttons of a similar nature are grouped together for ease of use.


Testing

At this point, the Speed Dial – Telephone button should be programmed on the console screen. To perform an effective test, you should have at least two telephone line resources setup on the screen.

To verify the speed dial function button works:

1. Log in to the Acom console position with the newly configured Speed Dial function button. Verify that all of the telephone lines are in their idle states.

2. Click on the Speed Dial function button.

3. Verify that the telephone line defined in the Line(s) attribute is selected and that the telephone number entered under DialString is dialed.


230 025-9619A

4. Verify that the call starts ringing on the other end.

5. Answer the call and verify that voice communications are possible. Other telephone lines on the console should remain idle.

6. Release the line and verify that it returns to its idle state.

Troubleshooting

Nothing happens Speed Dial – Telephone function button is pressed



• Verify the line is in an idle state before pressing the speed dial button.

Foot Switch

231

Auxiliary Devices

Foot Switch

A console position ACU can be configured to accept and external footswitch that can supply a contact closure when active. This section will detail steps necessary to connect an external footswitch to the ACU and configure the required parameters.

Required Tools

• IMS ACU and/or access to IMS Terminal

• 709-7615-xxx Zetron cable – required if direct connecting to ACU with IMS ACU

• Acom System Maintenance manual (025-9619)


• Acom ACU manual (025-9598)

• DVM – used to ohm out ACU digital output pin

Digital I/O Programming

To configure an ACU for a footswitch:

1. Using IMS ACU or IMS Terminal, access the ACU that is receiving the footswitch.

2. Select the Configure menu and then select the Digital I/O option.

3. In the Digital Input/Output dialog, select the Digital Input tab.

Auxiliary Devices

232 025-9619A

4. Set the Function Type to ACS I/O and the Function Data to the console network address on I/O Circuit 6.

On older systems built prior to 2007, set Function Type to ACS Function 1.

5. Click Save to save the settings and close the window.

6. Access the File menu and select Update to NVRAM.

7. Click OK when prompted for configuration name.

8. Before connecting the footswitch to the ACU, use the VOM to measure the resistance from ACU Digital Output +6 to ground. Verify that connection Digital Output +6 is connected to ground. Once you have verified that connection is grounded, continue to the next step.

Note Refer to the Acom ACU hardware manual (part number

025-9598) for the ACU Digital I/O pin out.

9. Connect the footswitch cable to ACU Digital Input -6 and Digital Output +6.

10. Select a line on the console of the ACU just programmed and transmit using the on screen PTT/Transmit button to verify that a successful transmission can be accomplished. Now use the footswitch to transmit.

Device Real-time Clocks

233

System Clocking

Device Real-time Clocks

Each device on the Acom network has an internal real time clock (RTC). Acom uses the device’s RTC time when it records the date and time for each logged alarm or other event. The ADS can be configured to have its RTC receive time updates from an external source — another ADS, an independent clocking device or application connected by way of a serial port, or a Network Time Protocol (NTP) server. In addition, the ADS will automatically update the RTCs of other Acom network devices on its loop. If ADS switches are configured to rely on a master clocking source, the time indicated by all RTCs can be synchronized across the system, even across multiple sites if ISBs are implemented.1

The ADS RTC is on the DCU card. The Real Time Clock option can be used to view the RTC time, and to change it manually, but mainly it is used to specify external clocking source options. It is available only in On Line mode.

Onboard Tab

ADS switches are typically configured to have their RTC automatically set and periodically updated, by synchronizing with an external clocking source, as described in External Clocking Sources on page 234. If necessary, you can use the Onboard tab to set the clock of an ADS manually. If this is done, it will still be updated when an update is received from an external source, if so configured.

1 No attempt is made to adjust for time differences due to messaging delays, so there may be slight differences in time among sites, but these differences should be negligible.

System Clocking

234 025-9619A

The Onboard tab displays the time and date of the ADS DCU and that of the connected PC. The ADS time and date can be changed from here. It can be entered manually, or it can be set to use the connected PC date and time.

To set the ADS time manually

1. Do one of the following:

• Click Use PC. The time and date are retrieved from the PC, and the fields under DCU are refreshed.

or

• Type the PC time and date in the corresponding fields under DCU. Use the format shown to the left of the fields.

2. Click Save Time. The DCU card RTC is updated.

3. Click Close.

External Clocking Sources

External Clocking Sources

235

On each ADS that is declared as a Main and Backup (on the Modes tab), use this tab to specify where the ADS RTC will get its time input from. If both Enable checkboxes are selected, the Serial source will be preferred — it will be polled first, then, if the Serial source is not found, the NTP source(s) will be polled. If neither Enable checkbox is selected, the ADS will use its own RTC to update the other ADS switches.

On non-Main and non-Backup ADS switches, leave both Enable checkboxes unselected, and the ADS will automatically have its RTC updated by a Main or Backup ADS.

To use an NTP server time source

Note This will enable the ADS to use the Internet standard Network

Time Protocol to synchronize Acom network devices. Do this only on Main and Backup ADS switches.

1. Check the Enable NTP Server Polling checkbox.

2. In the NTP Server X fields, enter the IP address of up to three NTP servers. The ADS will prefer the #1 server; that is, it will always attempt to connect to it for a time update before trying any other source. If #1 is unavailable or unspecified, it will try #2. If #2 is unavailable or unspecified, it will try #3. If #3 is unavailable or unspecified, the ADS will use its own RTC to update the other ADS switches.

3. Leave the Enable NTP Server Polling checkbox unselected.

4. Click Save and Close.

To use a serial interface time source

Note This will enable the ADS to use an independent clocking device

or application, connected by way of serial port 2 on the DCU card, to synchronize Acom network devices. Do this only on Main and Backup ADS switches.

1. Select Enable on Serial Port 2.

2. Specify the communication settings for Serial Port 2. They typically depend on the specific clocking device being connected to. These settings are saved in the IDS_ADS.ini file in the IMS ADS installation folder.

a. Port Type is configurable by way of jumpers on the DCU card to either RS232 or RS485/422.

b. Baud Rate (1200-38400).

c. The Initialization string is sent to the connected time source when the ADS polls it for the time. Click the ellipsis button ( ) next to the field to display possible values (<NULL>, <VT>, and so on), but you have to type the value into the field.

d. Data is an ASCII string representing the format of the incoming time data stream from the serial clock. This is used to parse the stream. Several Preset

System Clocking

236 025-9619A

Format options are predefined. They are included in the IMS_ADS.ini file upon installation, and that is the source of the entries in this drop-down list.

If you need to use an undefined format, type it into the field. Click the ellipsis button ( ) next to the field, and you will see some data elements displayed that might be helpful. The Data can be entered in one of two configurations: start mode or end mode.

• Start mode is used when the first part of the data stream is known. To use this mode, enter the first part of the data stream, followed by the required time/date elements. You do not need to define how the data stream ends. For example: $GPS 123 ?? HH?MM?SS The first character cannot recur in the data stream. For example, in the preceding example you could not use $T somewhere after $GPS.

• End mode is used when the first part of the data stream is unknown but the ending is. To use this mode, enter the time format, followed by the ending characters. For example: HH:MM:SS ??<CR><LF> The first character must correspond to a time or date code character (H, M, D, and so on).

3. Click Save and Close.

Daylight Saving Time

While each device on the Acom network has its own internal clock, and that clock may have its time set in several ways (see Device Real-time Clocks on page 233), an ADS controls the offset from GMT and whether DST is observed, for all devices on its loop. Use the Time Zone tab of the System Parameters window to specify these operating parameters.

It is only necessary to specify these parameters on, and they are only used by, a Master Source ADS. Therefore this tab’s fields are grayed out unless Master Source is checked on the General tab. If two Master Source ADS switches are configured, they must have the same settings on the Time Zone tab.

Intersite Considerations

237

Field Description

GMT Offset Enter the number of hours (hh) and minutes (mm) that the site’s time zone is away from Greenwich Mean Time (GMT). Use the format hh:mm, and precede it with a minus sign if the zone is behind (west of) GMT.

DST Offset If the site is in a location that observes Daylight Saving Time (DST) (or any other variety of Summer Time), check this field.

If the site is in a location that does not observe DST or Summer Time, uncheck this field and ignore all of the Start and End fields.

Start and End Specify the day (first three fields) and time (last field, in 24-hr format) on which the switch to DST (Start) and back to standard time (End) are to be made. There is considerable variance among these days and times around the world from region to region as well as from year to year. For an illustration and list, see (for example) http://www.worldtimezone.com/daylight.html. You should consult an authority to ascertain the correct values for your site(s).

Note: In the northern hemisphere, Start is associated with a Spring date, End with an Autumn date. In the southern hemisphere, it is the reverse case.


In multisite systems, if the sites are to be synchronized, the System Main will also disseminate time updates to the other sites across ISBs. In addition, each site needs to have one ADS configured as the Local Main, which will disseminate time updates to the other local devices. One other ADS at each site should be configured as the Local Backup, which would take over for the Local Main if it should fail. In the case of a communication failure between sites (that is, site isolation), each site’s Local Main will

System Clocking

238 025-9619A

act as System Main for its site until communication with the designated System Main is restored.

Use this tab to specify the role of this ADS in the time update distribution scheme between the external clocking source and other ADS switches.

If an external clocking source will not be used, select Disabled under Local Modes and ignore the rest of this section. The ADS will have its RTC automatically updated by the active System or Local source ADS.

If an external clocking source will be used, one ADS must be configured as the System Main. This ADS will disseminate time updates to the other ADS switches. One other ADS should be configured as the System Backup, which would take over for the System Main if it should fail.

A Local Main may also be configured as the System Backup. The System Main may also be configured as the Local Backup.

Each ADS will be configured to prefer either the Local clock source or the System one.

The options are summarized in the following table:

Field Description

Local Modes Disabled — This ADS will have its RTC updated by another ADS (the active Local or System source).

Main — This ADS will be the Local Main. It will send updates to other devices on the local DS3 ring.

Backup — This ADS will be the Local Backup. If the Local Main should fail, this ADS would send updates to other devices on the local DS3 ring.


239

Field Description

Source Preference Local — If this ADS receives time updates from a Local Main or Local Backup, and it receives time updates from a System Main or System Backup, the updates from the Local source will be implemented and those from the System source ignored.

System — If this ADS receives time updates from a System Main or System Backup, and it also receives time updates from a Local Main or Local Backup, the updates from the System source will be implemented and those from the Local source ignored.

System Modes Disabled — This ADS will not send updates across ISBs to other sites.

Main — This ADS will be the System Main. It will send updates to other ADS switches on the local DS3 ring and across ISBs to ADS switches at other sites.

Backup — This ADS will be the System Backup. If the System Main should fail, this ADS would send updates to other ADS switches on the local DS3 ring and across ISBs to ADS switches at other sites.

NOTE: ADS switches that will be configured as System Main or System Backup should have two DCU cards, for local redundancy. In ISB implementations, the System Main and System Backup should be on different sites.

System Clocking

240 025-9619A

Subrack Change-over

241

Device and System Shutdown and Restart

Subrack Change-over

This document explains the use of a Changeover Subrack to switch Acom radio or telephone resources between redundant Acom Line Subracks (ALS).

Use of a main and standby subrack is supported to maximize Mean Time Between Failures (MTBF). A failure in one rack will not result in a lost resource because a duplicate resource is available in the standby subrack. If the currently selected ALS


242 025-9619A

triggers an alarm because of a major fault, the other ALS will lose confidence and demand control of the lines from the changeover subrack.

Note The main rack and standby rack should have the same hardware

and same configuration (except for addresses). See Cloning an ALS on page 252.

Changeover Hardware

The Acom changeover control system is primarily composed of a main, standby, and changeover subrack. Each rack is equipped with cards to support the hot standby application. The E1 links from the subrack to the ADS (Acom DS3 Switch) are not switched, a combination of signaling lines between the racks determine which E1 link is considered active to be presented to the system backbone.

The Acom Line Subrack (ALS)

An Acom Line Subrack consists of a Main Control Unit (MCU), a Main Supply Unit (MSU), a subrack assembly, and line cards. Each redundant pair of ALS units in the changeover system should be equipped and configured identically with all of the same resources so switchover is seamless to the user.

An ALS will demand control when it loses confidence in the opposite subrack. By monitoring the Watchdog (AI13) and Standby Fault (AI21) alarm outputs of the opposite subrack, the MSU card can demand a switchover to take control by asserting the System Select (AO11) output. By momentarily grounding this output, the MSU will signal the Changeover Control Card (CCC) in the Changeover subrack that it wishes control of the radio and phone lines. The CCC will command all COV-V, COV-R, and COV-T relay cards to switch lines over to give the subrack control and will assert the System A Selected or System B Selected outputs to tell the subracks which ALS now has control. This CCC output is connected to the MSU “System Selected” input (AI11) and a parallel connection is made to the ADS input.

MSU

The Main Supply Unit (MSU) serves many functions in an Acom system, system tone generation, DC-DC conversion, and alarm inputs and outputs. The MSU has six input and six output alarms. MSU input alarms are pulled high to – 48 volts by the MSU card’s internal jumpers JP1-JP6. A ground on any of these inputs will cause the input to become active. The output alarms of the MSU are opto-isolated common collector outputs that pull to ground (+VV) when active.

Subrack Change-over

243

System Selected and Select System (AO11/AI11)

The SYSSEL output (AO11) is grounded by the MSU card to signal the CCC card that it wishes to take control. AI11 is then grounded by the CCC card to signal the MSU that it has control. The subrack will take control when it sees its Standby Fault input go active or its Watchdog Fault input go inactive. The subrack may additionally take control if the local alarms clear and the opposite subrack still has either a Standby Fault or Watchdog Fault.

Standby Fault (AO21/AI21)

This is the primary health alarm of the subrack. It is used to signal the other subrack when it has an urgent alarm. The output is programmable; it is useful to configure this alarm identically to the Urgent Output alarm.

This input is expected to be normally inactive and if it becomes active a fault in the standby rack is assumed. This signal is used in conjunction with the Watchdog Fault to provide communication between main and standby subracks. If the Standby Fault input goes active, the local subrack will take control of the lines.

Watchdog (AO13/AI13)

The Watchdog output (AO13) is in an active state under normal operation. Two alarms are hard coded (fixed) to the Watchdog output alarm. Should the Primary MCU card in the ALS go dead, or the MSU lose power, the Watchdog output will go inactive to indicate it has failed. In addition to these two non-configurable triggers, additional alarm inputs can be mapped to this MSU output to trigger a changeover (see “Alarms” in Acom Software Configuration P/N 025-9529). It is common to connect all operational alarms to the Standby Fault output and leave only the loss of power and failure of a primary MCU to trigger the watchdog.

The Watchdog input (AI13) monitors the Watchdog output of the other sub rack. If this input goes inactive the MSU will demand control by asserting the SYSSEL Output (AO11).

Bad E1 (AO23/AI23)

The AI23 input is commonly used to detect a problem associated with the E1 link connected to the rack. The ADS that services this subrack provide this signal if any of the E1 links from the ALS to the switch fail. It provides a faster indication of a lost E1 than waiting for a LOS, NOS, or RRA signal and will result in a quicker changeover between subracks.


244 025-9619A

Changeover Subrack

A Changeover Subrack consists of a Changeover Control Card (CCC), a subrack assembly without the lower backplane, and one or more COV-V/COV-R/COV-T cards. The lower backplane of the Changeover Subrack is removed to allow for the connection of IDF cables to the back of each changeover card (COV-V/COV-R/COV-T). Unlike an Acom Line Subrack, the Changeover Subrack does not require an MCU or MSU card to function.

In an Acom system, to minimize the number of resources affected by a problem, only two ALS units should be connected to one Changeover subrack. The complexity involved in switching more than two ALS units from a single Changeover is more trouble than its worth. If a fault existed in one of the “MAIN” ALS units and one of the “STANDBY” ALS units, then there is no good state where all resources are in working order, unless each ALS pair is switched independently. There are applications where two ALS units could be switched together but that is beyond the scope of this document.

Changeover Control Card (CCC)

The CCC card is designed to take changeover control commands from the connected subracks and command the installed COV-V, COV-R, or COV-T relay cards to switch the common connections to the subrack in control. The CCC card accepts dual 48vdc power inputs so it does not lose power if one supply fails. Signaling leads in the audio/alarm interface from each MSU power supply connect to the CCC DB9 ports on the front edge of the CCC card. The CCC signals the Changeover Subrack COV-V/COV-R voice circuit cards or COV-T coaxial circuit cards to switch between the A and B system. LEDs on the front of the CCC card indicate "A" power, "B" power, and a status of which system is in control.

Changeover Card - 48/96 Way Switch (COV-V / COV-R)

The COV-V and COV-R cards switch 24 2-wire circuits (or pairs) between an A and B system through a bank of relays. LEDs on the front of the card indicate the switched state of the card’s relays. Another LED on the front of the card indicates if it is receiving power from the CCC card. Each of the six LEDs on the front of the card reflects the switched state for 2 of the 12 relays on the card.

Inputs from the A ALS are connected to the top connector of the COV card (P2 on the COV-V card or J1 on the COV-R card). Inputs from the B ALS are connected to the bottom connector (P3 on the COV-V or J2 on the COV-R). The common outputs of the COV-V and COV-R cards are connected to the back connector P1 and are terminated at an independent distribution frame (IDF) for connection to the physical line or circuit.

Subrack Change-over

245

Changeover Card - 3 Way Coaxial Switch (COV-T)

A COV-T card switches three sets (pairs) of coaxial links between an A and B system. This card is typically used to switch E1 or ISDN links from the phone system and the A and B rack. It is not used to switch E1 links between subracks and the backbone switch (ADS). The COV-T is not meant to switch E1s between the Acom Console Unit loops and backbone switch. These connections are already redundant and do not need to pass through a changeover card.

The common pair of coaxial lines connects to the top SMB pair on each of the three connection sets. The first set of connections is on the top front of the COV-T card. The top pair is the common, the second pair is the A-side, and the third pair is the B-side. Just below these coaxial connections are the second set and the third set of coaxial links is connected to the rear of the COV-T card. Unlike the COV-V and

COV-R cards, the common connections are NOT made through the back; instead there are two common sets of connections on the front of the card, and one on the back.

Card Placement

The CCC card should be located in slot 0 (far left) of the changeover cabinet The COV-V, COV-R, and COV-T cards should be located in slots 1 through 12 of the Changeover Subrack.

Additional Hardware

The common connections secure to the back of the rack and changeover cards using screw terminal connections. Care should be taken to verify the card seats completely into the back cable.

Backbone Switch Signaling

The backbone switch is an Acom DS3 Switch (ADS). The ADS switches E1 circuits to/from the high-speed backbone.

The CCC card’s SYSSEL output is used by the backbone switch to determine which E1 is to be switched onto the high-speed backbone (DS3). With the E1s of both the A and B subracks permanently connected to backbone switch, the system needs to know which E1 is the valid signal (in control) for the associated lines of the subrack. The E1 signal from the subrack that is in control of the physical circuits will be connected to the backbone to be made available for other Acom devices.

The CCC card has two outputs for the SYSASEL signal and two for the SYSBSEL signal. One of each signal is connected to the ALS, and the other is connected to the backbone switch associated with the ALS. The SYSSEL input signals the backbone


246 025-9619A

switch that the associated E1 link is connected to the active ALS and should be considered the valid signal (and connected to the backbone).

An output from the backbone switch is connected to the ALS as an advanced indicator of a problem on the E1 links from the ALS. This signal is connected between one of the backbone switch digital outputs and the ALS MSU alarm input AI23 “Bad E1”. If the backbone switch detects a problem with the E1 on the corresponding link (such as NOS/LOS) it will signal this output to give the ALS advanced warning and prompt a changeover. This output can provide a faster indication of a bad E1 than just monitoring for LOS, NOS, or RRA on the MCU card.

Acom DS3 Switch (ADS)

The ADS digital I/O for changeover control is connected via a 25-pin connector on the front of the DS3 Control Unit (DCU). The DCU has 8 inputs and eight outputs. The inputs are pulled to – 48 volts using the externally provided bias voltages on the front of the DCU. An external bias voltage must be provided; the DCU does not have a way to internally bias these I/Os. To signal the DCU that the ALS on the corresponding E1 circuit is in control and its E1s should be used, an input is pulled low (0 Vdc). ADS inputs and outputs are programmable; any input may be used to set one or more E1 links as active. Any output can be programmed to activate on a bad E1 link.

The ADS can be signaled which ALS is in control by grounding the corresponding input on the DCU I/O connector. The input is programmable; any input can be configured to represent any number of links that are active (in control). This input is typically connected to the Changeover Control Card (CCC) output SYSASEL or SYSBSEL. The input is pulled to –48vdc internally by the ADS and is taken active by grounding it (0 Vdc).

Once an ALS is communicating with the connected ADS on E1 TS16, the MCU4 LED B1 (link 1) or B2 (link 2) will come on solid for the ALS that has control and will slowly flash green on the link(s) connected to the standby ALS (see Main Control Unit (MCU) on page 180).

ADS outputs indicating the link status are also available from the DCU I/O connector. The output is programmable; any output may represent any number of bad E1 links. These outputs should be connected to MSU AI23 (input 6) and programmed to trigger an Urgent Alarm LED and Standby Fault when active. The output will indicate active by being pulled to 0vdc (ground). The connected equipment should pull this output high to –48vdc and watch for the ground. The programmed DCU output will be pulled to +VV (ground) by the ADS when there is a failure (NOS/LOS) on the corresponding 2Mbit port.

Subrack Change-over

247

ADS Changeover Wiring Example

The following figure is provided as an example only. Every Acom system is provided with custom wiring diagrams included in the package of on-site documentation.


248 025-9619A

Shutting Down the System

249

How to Force a Change-over

• A technician can force a changeover using IMS (see Change Over in the Tools Menu section of Acom Software Configuration, P/N 025-9529). Alternatively, a technician can force a changeover to an ALS by removing the front edge connector of the MSU card. These are the preferred methods to cause a changeover because they are the least disruptive.

Warning! If you change over using IMS, be certain to set Mode back

to Automatic. Leaving this in manual mode will prevent an ALS from taking control in the event of a failure.

Caution! If a change over is performed on an ALS with digital resources, such as ISDN phone lines, T1/E1 radio interface, OpenSky, P25, or T1/E1 Loggers, these resources can take up to 2 minutes to become available again after the change over. The reason is that after the resources detect a momentary loss of signal, it can take that long for them to re-establish synchronization with the far end of the link. An ALS with only analog resources will not experience any such outage.

• Incorrect wiring of the changeover signaling between the CCC and MSU may cause the subracks to switch continuously between the A and B system. This could happen if both racks have Watchdog and Standby faults active. Check your changeover wiring diagrams against the actual wiring in the Krone blocks.

• If the ALS never switches to the other sub rack even though a Watchdog failure has been triggered, the sub rack may be automatically acknowledging the alarms, check the mapping for the “Alarms ACKed” output alarm in IMS (see “Alarms” in Acom Software Configuration, P/N 025-9529).

• If the ALS will not switch to the other subrack even though it has no alarms and the Watchdog has triggered on the active rack, it may be caused by a lack of confidence that the other rack is operating correctly. It may be that the SYSSEL output of the CCC card is pulled low by an unpowered DS3 Switch alarm I/O. Make sure the backbone switch alarms are biased by providing an external -48 Vdc reference. It may also be caused by the Watchdog alarm not being seen at the other subrack, the Watchdog input should normally be active. The OK alarm should be normally inactive.

Shutting Down the System

The system devices can be shutdown randomly without causing them any harm; however, it is best to do a sequential shut down of devices to assure they have all been powered down correctly. In an event of a power outage or brown out, it is recommended that a


250 025-9619A

system shutdown and restart be performed to assure that the system has been properly initialized and online without any errors or alarms.

The following procedure requires access to the system IMS terminal.

Manually shutting down an Acom system:

1. At all Acom Console (ACS) positions, exit the console program to Windows.

2. Shutdown all of the Acom Console (ACS) computers.

3. Turn off the power to all ACU units in the system.

4. Turn off power to all ALS racks in the system.

5. From the system IMS terminal, verify that all devices except ADS racks are indicating No Coms. If this is not the case, then some ACU units and/or ALS racks have not been shut down. Recheck their status and power down the devices you missed.

6. Turn off the power to all the ADS racks in the system.

At this point, all of the Acom devices in the system should be powered off.

7. Use the IMS terminal to verify that all devices in the Acom system now show the status No Coms.

The follow two items are optional.

8. Turn of all third-party equipment connected to the Acom system, such as T1/E1 rate convertors, IP tubes, or loggers.

9. Turn off the Power Supply main switch for each equipment cabinet.

Tip To power the system back on, follow the power up sequence in

the Restarting the System section, which follows. If the Power Supply main switch and third party equipment has been turned off, make sure to power them on first.

Restarting the System

The redundant and self-healing nature of the system design implies that only an unusual event (like a total power failure) would require restarting the entire system. In such an event, the procedure is no different than it was for the initial startup.

In the case of system components that were switched off for repair or replacement, they may be started again at any time. Once they have cleared reset and finished their self-tests, the IMS application is used to finish any configuration required and returns them to service.

Restarting the System

251

The power up procedure in this section is to be used on an Acom system that is known to be configured and functional.

Power-Up Sequence

Note Verify that all Acom equipment is powered down/off before

starting the power up sequence. This includes all Acom Console Units, DS3 Switches, ADS units, and ALS units in the system. Also verify that Acom Console Software is not running. If Acom Console Software is running, select the Configure button and select Exit to Windows.

To power up an Acom system:

1. If they were secured, power on the main power supply in each equipment cabinet.

2. Power on any third-party equipment that was powered down.

3. Power up all ADS and/or DS3 Switches.

4. Wait two minutes after all the DS3 Switches have been powered on before proceeding to next step.

5. Power up side A of the Acom system ALS units. These would normally be all ALS units with the names of ALS1A or an A in the name after the word ALS. These ALS units are sometimes referred to as the Main ALS units. (They may also has designators like ALS-1M, or have no letter at all, such as ALS-2, ALS-1, ALS-4, etc.)

6. Wait one minute after all ALS units on the A side have been powered on before proceeding to the next step.

7. Power up side B of the Acom system ALS units. These would normally be all ALS units with the names of ALS1B or a B in the name after the word ALS. These ALS units are sometimes referred to as the Standby ALS units and will have designators like ALS-1S.

8. Wait one minute after powering on the last of the B-side ALS units before proceeding to the next step.

9. The system should be active on the A side of the Acom Equipment. This can be verified by looking at the Information Alarm LED on the ALS units. This is the Green LED located on the MSU card right below the power switch next to the Yellow and Red LED’s. All ALS units on the A-side should have the Information Alarm LED on and the B-side ALS units should have the Information Alarm LED off.

10. If IMS Terminal/Net_Mgr is available, verify that all ALS units are now reporting to the software.

11. Power up all Acom Console Units (ACUs) in the system.

12. Wait at least one minute after the last Acom Console Unit in the system has been powered on for all Acom Console Units to come online.


252 025-9619A

13. If IMS Terminal/Net_Mgr is available, verify that all Acom Console Units (ACUs) are now reporting to the software.

14. Start the console computer at each console position and then start the Acom Console Software. Logon to a screen.

15. The Acom system should now be up and ready for operation.

Cloning an ALS

This section provides instructions for a Zetron Certified Acom technician to clone the ALS configuration from the main rack to the backup. Cloning the main configuration into the backup is a fast way to copy your changes to the standby ALS and keep both racks in sync. It is assumed that both ALS units have identical cards.

Equipment

• Straight through RS-232 serial cable (DB9 to DB9), Zetron part # 709-7345-xxx, used to establish a direct connection between the ALS rack and the computer running IMS ALS

• Computer with IMS software installed


Procedure

Caution! You must ensure that the following are true.

you are using the IMS ALS software

The connection from the IMS computer is a direct connection to the ALS X17 RS232 port

Make sure that the ALS being cloned is not the active ALS

Cloning an ALS subrack:

1. Disconnect the E1 cables between the ALS and the ADS. This is a precaution to prevent any resource conflicts while the ALS is being cloned.

2. Connect to the MCU connector X17 of the Main ALS using a straight-through RS-232 cable.

3. Start IMS and choose Communications-Connect from the IMS menu to connect directly to the ALS being cloned.

Replacing Hardware Modules

253

4. Hover the cursor over the MCU card in slot 0. The firmware version should be displayed in the bottom of the status bar. Make sure that the version displayed is the correct one for your system. If not, you will need to perform a firmware update prior to cloning this rack.

5. Once the firmware version has been verified to be correct, note the ALS network address displayed in the title bar. Make sure this is correct. Review the Network Diagram in your As-Built documents if needed. If this is incorrect, access the Configure menu and use the Set Address option to change it to the correct address.

6. Once connected, click File, Save to Disk from the IMS menu.

7. Disconnect from the Main ALS and move the RS-232 cable from the Main to the Standby ALS.

8. From the IMS menu, click File, Load from Disk, and select the file you previously saved from the Main ALS.

9. The only options that should be different between the Main and Standby ALS are the Sub-rack Address and External Clocking. Click Configure, Subrack Address from the IMS menu. Set the option to Standby and click Save.

10. Again click Configure and then select External Clock. If the option Master is currently selected, change it to Backup being selected. If the option None is the one currently selected, leave it set to None. Click Save.

11. Choose File, Update to Rack from the IMS menu to transfer the configuration to the ALS. A progress bar is displayed while the upload takes place. You will be prompted for the ALS name. Enter the correct name or leave it as-is and select OK.

12. Reset the Standby ALS by turning off its power to finalize the changes.

13. Reconnect the E1 cables to the rack.

14. Return power to the rack.


This chapter provides procedures for replacing failed Acom cards and devices. Generally, you should only replace devices and cards after consulting with Zetron Technical Support.


254 025-9619A

Replacing Acom CCC Cards

Warning! Please exercise electro-static discharge (ESD) precautions

when handling all cards.

The Changeover Control Card (CCC) signals the COV-V, COV-R, and COV-T relay cards to switch from main to standby.

Note These cards are HOT SWAPPABLE but removing the CCC will remove

power from the Change Over Subrack rack backplane and the COV-T, COV-R, or COV-V cards will default to the primary/main (A) side of the system. Although these cards are hot swappable, it is preferable to turn off the power when swapping out any cards in the system.

Subrack programming is not required when replacing these cards.

Equipment Required

Small flat head screwdriver

To remove the CCC card:

1. When removing a CCC card, change the system over to the primary/main (A) side of the system. This will assure that audio/data from the ALS to the demark will remain active and available.

a. Launch IMS Terminal, and login to the Main ALS that will be active.

b. Double click the ALS. From the Tools menu, select Change Over, select the Manual option, and select the Main ALS.



2. Use a grounding wrist strap to prevent ESD damage to the equipment.

3. If you are replacing a CCC card, removing all connectors from the front of the card. Make sure the cables are labeled. If they are not labeled, label them now so they can be properly connected to the replacement card.

4. The DB9 connectors can be removed using the small flat head screwdriver. The orange Weidmuller plug can be pulled out if there are wires connected to them. The power plugs can be removed by squeezing the locking latch on the right side of the plug. It may be easier to pull the CCC card out partially to get a good grasp on the connector/latch to remove the plugs.

5. Flip the top lever on card upward to dislodge it from the backplane. Slide card out slowly and carefully.

6. Once all connectors have been removed, remove the CCC card.

7. Place the old card in the ESB bag.


255

To install the replacement CCC card:

1. Ground yourself with an ESD wrist strap connected to the rack.

2. Remove the new card from the ESD bag.

3. Align the card with the card guides at the top, then bottom of the slot.

4. Slowly and carefully slide the card into the rack.

5. Press the card into the rear connector using two hands on the front of the card.

6. Connect the cables to the connectors on the front of the card.

7. The LED’s on the COV-T, COV-R, or COV-V card should indicate that they are active on the primary/main (A) side.

8. Change the system over to the backup/standby (B) ALS and verify that audio/data is passed and the COV-T, COV-R, or COV-V indicates they are switched over to backup/standby (B).

9. After you are satisfied that the Backup/Standby (B) rack is functional, change system back over to the Primary/Main (A) rack for normal operation.

Replacing COV-T, COV-R, and COV-V Cards



The COV-T card is fitted with relays that can switch 6 coaxial SMB connections between the main and standby subracks. This card is hot-swappable.

The COV-V and COV-R cards are fitted with relays that can switch 50 conductors (25 pairs) between the main and standby subracks. There is a common connector on the rear of the card for the line interfaces and 2 connections on the front for the main and standby subracks. This card is hot-swappable.

Note Although these cards are hot swappable, it is preferable to turn

off the power when swapping out any cards in the system.


To remove the COV-T, COV-R, or COV-V card:

1. When removing a COV-T/COV-R/COV-V card, any line resources using the card will not be able to get audio/data to the outside world/demark. The ALS units will be transparent to this and will not know but the operators should be aware not to use the line resources associated to the card because they will not be available when the card is removed.



256 025-9619A

3. Ensure the connectors are labeled so they can be reconnected in the correct order.

4. Carefully disconnect the six SMB coax connectors (COV-T) or two EURO96 connectors (COV-V) from the front of the card by squeezing at the top and bottom of the connector while pulling straight out. For COV-R cards, you may have to loosen a screw at the top of the two RJ-21 connectors first.

5. Flip top lever on card upward to dislodge it from the backplane connector. Slide card out slowly and carefully.

6. Place card in ESD bag.

To install the replacement COV card:




4. Slowly and carefully slide the card into the rack.


6. Connect the six SMB coax connectors (COV-T), two EURO96 connectors (COV-V), or two RJ-45 connectors (COV-R) to the front of the card.

7. The LEDs on the COV card should indicate that the card is active.

8. Perform some tests on the primary/main (A) side and backup/standby (B) side to make sure both sides are functional.

Replacing DCU Cards



The DCU card performs audio and data switching for two DS3 (T3) links. This card holds the configuration for the ADS subrack and controls all rack messaging.

Note The DCU card is NOT hot-swappable.

Equipment Required

• Zetron PC to Acom Console Unit cable: 709-7615-xxx (xxx = cable length)

• PC/Laptop equipped with Windows, a terminal program capable of serial communication, and a DB9 RS232 Serial Com Port

• IMS ADS software (installation setup for this software is located on the Acom Install CD)

• File compression utility (this may be required if the firmware file is not in compressed format)

• The network address of the ADS housing the DCU to be replaced


257

Replacing a DCU card

To save the DCU configuration:

1. If this is a standalone ADS, skip to Step 2. If this ADS is part of a redundant setup with two or more ADS units, then continue with the following sub-steps:

a. In order to successfully remove a DCU card with little disturbance to the system, ensure that there are no E1 links resources active between the ADS and an ALS. This can be verified by viewing the second row of green LEDs on each MCU4 card in the ADS (LEDs A2 and B2 in Figure 12).

Figure 12. LED Indicators on an MCU4 Card

b. If these LEDs are NOT solid green, there is no active E1 link on this ADS and you can skip to Step 2.

c. If either of these two LEDs are lit solid green, there is a link from this ADS to either an Acom Console Unit (ACU) or an ALS. To determine which, consult your system’s network diagram or follow the cables.

If the link is to an Acom Console Unit (ACU), you can skip to Step 2.

If the link is to an ALS, you must first ensure all ALS E1 links are switched active to another ADS. See Replacing MCU Cards in an ALS on page 268 for instructions describing how to safely switch an ALS to its redundant clone.

2. Connect the 709-7615-xxx cable from the PC to the left RJ45 connector on the bottom of the DCU card.

3. Start the IMS ADS program.

If you do not have IMS ADS loaded on your PC, install it from the Acom Install CD.

4. Select the Communications menu, click Settings, and verify that the baud rate is 38400 and the Com Port matches the one being used on the PC. Click OK to save settings.

5. Select the Communications menu and click Connect. When prompted for the Network address, enter the ADS Network address and click OK.

(The network address is typically on a sticker on the ADS and can be found in the “As-Built” documents for your particular system).

Note Make note of the Network address because it will be needed

when installing the replacement card.


258 025-9619A

6. When prompted with the password dialog, click the Default button and it should allow access to the ADS.

7. Access the File menu and select Save to Disk. When prompted for the configuration file name, use a descriptive file name. For example: ADS<network address>.bin


disk. It may take up to 30 seconds to save the file. When the file save operation is complete, the Progress Meter window will disappear.

8. Once the file has been saved, select the Communications menu and select Disconnect.

Note The DCU card holds the configuration for the ADS.

9. Close the IMS ADS program.

To record the firmware version:

1. Move the programming cable to the right RJ45 connector at the bottom of the DCU.


3. Open a terminal connection using the COM port connected to the DCU. The COM port should be configured for the following settings:

Bits per second = 38400 (default for an DCU) Data bits = 8 Parity = None Stop bits = 1 Flow Control = None


5. When the Password prompt appears, type 8564888 and press Enter.

6. A menu should appear with some selections. Press 1, and then Enter.

7. Once logged in, type the command ver and press Enter. Record the results for Release and Library.

8. To exit debug mode, press Esc, then X.


259

To remove the failed DCU:

Warning! The DCU card is NOT hot-swappable. Power down the ADS

before removing the DCU card.

1. Turn off power to the ADS by switching the MSU power switch off (up).

2. Ground yourself with an ESD wrist strap to the ADS rack.

Tip If the cables are not labeled, label them now so you know where

to connect them on the replacement card.

3. Disconnect the RJ45, BNC coax, and other connections from the front of the card.

4. Use the card removal handle at the top of the card to slide the card forward.

5. Remove the card and place it in an ESD bag.

To install and update the new DCU:

Warning! The new DCU must be the same revision as the one you are

replacing.

1. Ground yourself with an ESD wrist strap to the rack.



4. Slide the card into the subrack and press the card into the rear connector using both hands on the front of the card.

5. Apply power to the subrack by turning on (down) the MSU card and verify LED activity.

6. It is necessary to make sure the DCU card installed has the same version of the DCU card removed. Verify firmware version:

a. Determine the firmware version of the new card (see To record the firmware version: on page 258) and compare with the version of the old card.

b. If the DCU firmware is the same, skip to the topic To restore ADS configuration: on page 261. If the firmware versions are different, continue:

7. Before you proceed with updating the firmware, make sure you have a copy of the Ds3<version>.compressed firmware file. If you do not have this file, call Zetron (see http://www.zetron.com).

8. Uncompress the firmware file and save it to a convenient location on the IMS terminal computer.

9. Proceed to the FTP method of updating the DCU firmware.


260 025-9619A

Updating the DCU firmware (FTP method):

Use the following procedure to update the firmware on one DCU, or the first of many DCU subracks.

1. Place the DCU firmware file in a location on the IMS console computer where you can easily find it and FTP it to the DCU. The firmware file must be uncompressed and it must be named “dcu.binary”.

Warning! Sending a Compressed file or using the wrong file may

result in an inoperable DCU.

2. At a Windows Command Prompt, navigate to the location of the firmware file.

3. Use the following command to FTP to the DCU where [IP Address] is the IP address of the DCU:

> FTP [IP Address]


5. Type the password (default is 8564888).

6. Select binary mode:

FTP> binary

Warning! Failure to use binary mode will cause FTP to send a corrupt

file to the DCU firmware. This may result in an inoperable DCU.

7. Upload the firmware file:

FTP> put dcu.binary

(This may take a few minutes.)

8. When the FTP prompt returns, check the directory for file errors:

FTP> dir

If there are file errors in the directory, the firmware update has failed. Press the reset button on the DCU.

9. Exit FTP.

FTP> quit

10. Press the reset button on the DCU.

11. The resetting DCU will put on an LED “lightshow” while booting up. The status LEDs will return to normal in a minute or two.


261

To update the firmware for all networked DCU subracks:

If you have not already, use the previous procedure to update the firmware on the first DCU. The following procedure “copies” the updated firmware from that first DCU to all other networked DCU subracks.

Caution! Using this procedure to update all DCU cards at once will take the entire system off line until the file transfer is complete and all of the DCU cards have reset. This procedure should only be used when the entire system can safely be taken out of service for an upgrade.

1. At a Windows Command Prompt, Telnet to the DCU with the updated firmware:

> telnet [IP Address]

where [IP Address] is the IP address of the DCU.


3. Type the password (default is 8564888) and press Enter. You should have an LR> or a DCU> prompt.

4. Use the following two commands to check the version of this DCU and all other networked DCU subracks:

ver

rver

5. The first DCU should have a newer version than the other networked DCU subracks.

6. Update the networked DCU subracks:

rdown /M

7. As each DCU is being updated, you should see the following message where XXX is the DCU address and YY is the slot holding the DCU.

“Rack Address XXX in slot YY is burning.”

After several minutes of updating DCU firmware, the prompt returns. This is an indication that the update process is complete.

8. Each DCU will reboot itself after the firmware update is complete.

To restore ADS configuration:

1. Move the programming cable to the right RJ45 connector at the bottom of the DCU.

2. Launch IMS ADS on the PC. Select Communications then Connect. Enter the network address of 1 when prompted, click OK.


3. At password screen click default.


262 025-9619A

4. Click File, Load From Disk, and select the file name that was saved earlier (see To save the DCU configuration on page 257).


6. When prompted for the network address, use the address that provided access in Step 1.

7. When prompted for the Configuration name, use the one supplied, which should be the name of the DCU that was replaced.

8. Access the Configure menu and select Set Address. Enter the Network Address recorded earlier in To save the DCU configuration on page 257.


10. To finalize the changes, click Tools, then Reset Rack from the IMS menu.

11. When the DCU is back up and running (top right LED on DCU card is blinking slowly) proceed to the following section.

To reconnect the cables


2. Re-connect the cables to the front of the card.

3. Turn power on the ADS.

4. Wait 120 seconds for the ADS to come on line.

5. Make ALS units connected to this DCU/ADS active by performing an ALS changeover described in Replacing MCU Cards in an ALS on page 268.

6. Test some line resources to verify that the system resources are functional on this DCU/ADS.

Replacing Acom Console Units

The Acom Console Unit provides the console data and voice interfaces for the position. The unit holds up to four expansion modules.

To remove an Acom Console Unit:

1. Back up the unit configuration to disk using IMS. (See Acom Software Configuration, P/N 025-9529.) Note the network address of the Acom Console Unit is displayed in the title bar of IMS ACU.

2. Make a note of the unit firmware version; the new Acom Console Unit must be the same revision. Using IMS ACU, access the ACU and hover the mouse over the Dual E1 card and the firmware version will appear in the status bar on the bottom of the IMS ACU program.

3. Turn off power to the Acom Console Unit using the switch on the rear of the unit.

4. Disconnect AC power from the rear of the unit.


263

5. Disconnect all serial connections from the data ports, noting their connection and marking if needed.

6. Disconnect all voice connections from the OAM or 4-Wire E&M Modules.

7. Disconnect the Digital Input and Digital Output connectors if used.

8. Remove the ground lead from the Acom Console Unit.

9. Remove the E1 cables from the Dual E1 card.

10. With all leads disconnected, remove the ACU from the desk.

To install a Acom Console Unit/ACU:

Note If a firmware update is needed, then a compressed ACU

firmware update file is required for this procedure. This file is typically supplied via email from Zetron technical support or located on the Acom Install CD. The supplied file may be titled ACU_101.zip or similar.

Note This procedure requires a terminal program capable of serial

communication and file transfers using the 1K xmodem protocol.

1. If the ACU is not being mounted under the desk, skip to Step 5.

2. Install any required modules in the ACU. See Replacing Acom Console Unit Daughter Cards on page 265.

3. Install the under desk mounting option.

4. Screw the ACU to the under side of the work surface using self-tapping screws.

5. Make all serial connections to the data ports. The ACS serial connection often uses ACU COM1.

6. Make all voice connections to the OAM or 4-Wire E&M Modules. Refer to the position layout drawing for your system for specific details on position connections.

• Jackbox or TRHI

• Speakers

• PC Tones

7. Connect any digital I/Os. This may include foot switches, TRHI, or active conversation lamps.

8. Connect the ground lead to the ground post near the power connection. Do not connect the E1 cables at this time.

9. Connect the AC power cable and turn on the ACU using the power switch on the rear of the unit.

10. Access the ACU using IMS ACU. When prompted for the network address, try using 2, 0, or 255.

11. Hover the mouse over the Dual E1 card and note the firmware version. If the firmware version is NOT the same as the ACU being replaced, continue to the next step. Otherwise, skip to Step 19.


264 025-9619A

12. Move the ACS cable currently plugged in the ACU Data Port COM1 to COM4.

13. Open a terminal connection using the COM port connected to the ACU. The COM port should be configured for the following settings:

Bits per second = 38400 (default for a ACU) Data bits = 8 Parity = None Stop bits = 1 Flow Control = None


15. When the Password prompt appears, type 8564888 and press Enter.

16. Once logged in, type the command ver and press Enter and record the current version.



result in a dead ACU. The only way to recover a dead ACU is to send it to Zetron for repair.

Note The ACU supports the compressed file format. After the

compressed file has been transferred, the ACU will CRC check the compressed file, uncompress it, and update to flash. It is recommended that you keep the firmware update in the compressed file and do not uncompress it before transferring to the ACU. This will minimize the transfer time and protect the bin file with the CRC checking provided by the compressed format.

18. After the firmware has been uploaded, the ACU will reset itself. Once it appears that the ACU is operating again, press Esc three times to get another Password prompt. Enter 8564888 and type the command ver to verify that the ACU now has the current version.

If the version is correct, type Exit to end the debug session.

19. Using IMS ACU, access the File menu and select Load from disk.

Locate the save file and load it.

20. From the File menu, select Update to NVRAM.

When prompted for the Network address, try 2, 0, or 255.

When prompted for the Configuration name, use the one supplied.

21. Access the Configure menu and select Network Address.

22. Enter the appropriate Network Address recorded earlier.

23. Access the File menu and select Update to NVRAM.

24. Power down the ACU and connect the E1 cables to the Dual E1 card.

25. Power on the ACU and verify that it is online and ACS is operational.


265

Replacing Acom Console Unit Daughter Cards

The Acom Console Unit daughter cards are available in several varieties:

Card Type Description

Dual E1 Module Provides multiple E1 connections for installing the position in an E1 loop. The Dual E1 must be installed in slot 0 (farthest away from data ports).

Dual 4-Wire E&M Module

Provides two 4-wire E&M interfaces for IRR, desk mic, speakers, or other purposes.

Operator's Audio Module (OAM)

Provides voice and data ports for speakers, handsets, mics, and more.

Removal:



1. Ground yourself to the Acom Console Unit using an ESD wrist strap.

2. Remove the Acom Console Unit (see Replacing Acom Console Units on page 262).

3. Remove the screws that secure the top cover on the Acom Console Unit using a medium Phillips screwdriver.

4. Remove the Allen screws that secure the cover plate on the rear of the module.

5. Remove the two Phillips screws that secure the card inside the Acom Console Unit.

6. Gently pull the card toward the rear of the Acom Console Unit to unseat the connector.

7. Lift the module out over the guideposts and place it in an ESD bag.

8. Secure the top cover of the Acom Console Unit using the existing screws.

Installation:

1. Ground yourself to the Acom Console Unit using an ESD wrist strap.

2. Follow the instructions for removing the Acom Console Unit.

3. Remove the screws that secure the top cover on the Acom Console Unit using a medium Phillips screwdriver.

4. If there is a cover plate at the intended location for the module, remove the Allen screws that secure the cover plate and set the plate aside.

5. Set the module into the Acom Console Unit slot so it fits over the guideposts and gently slide it into the connector.

6. Secure the card inside the Acom Console Unit with two provided Phillips screws.


266 025-9619A

7. Attach the new cover plate using the existing Allen screws.

8. Secure the top cover of the Acom Console Unit using the existing screws.

9. Install the Acom Console Unit (see Replacing Acom Console Units on page 262).

Replacing EIE, TIE, RIU, or EMU Cards



The EIE card provides six independent ring in/loop out channels that interface to CO provided POTS circuits. This card is hot swappable.

The TIE card provides six independent ring out/loop in channels that interface to local phones. This card is hot swappable.

The EMU card provides six independent 4-wire E&M channels that interface to radios or other 4-wire circuits. This card is hot swappable.

The RIU card provides six independent 2- or 4-wire channels that interface to radios or other 2- or 4-wire circuits. This card also can provide a PTT relay closure. This card is hot swappable.

Note Although these cards are hot swappable, it is preferable to turn off the

power when swapping out any cards in the system.


To remove the old card:

1. If this ALS is part of a Main-Standby setup and it is currently in control, force control over to the other ALS:

a. Launch IMS Terminal, and login.




2. Power down the subrack by setting the toggle switch on the MSU card to the UP position.


4. Carefully disconnect the EURO96 connectors from the front of the card by squeezing at the top and bottom of the connector while pulling straight out.




267

To install the replacement card:



3. For an EIE card with part numbers 950-0522 or 950-0637, check jumpers JP6, JP8, and JP9. These jumpers need to be set to “Dual” or “Single” (as printed on the board itself), depending on whether the subrack has dual or single backplanes. EIE cards with part number 950-0491 do not have jumpers for this purpose and are compatible with dual backplanes only.

Note For a 5v-12v version of the EMU card (P/N 950-0841), jumpers

J1 through J12 must always be in the 2-3 position.


5. Slowly and carefully slide the card into the subrack.


7. Connect the EURO96 connectors to the front of the card.

8. Apply power to the subrack.

9. Verify in IMS Terminal that the new card appears and the slot box for it is green.

10. If this ALS is part of a Main-Standby setup, force control back to this ALS:


b. Select the Manual option and select this ALS.

c. Verify the ALS icon in IMS turns light blue to show that this ALS is in control.

d. Once this ALS has taken control, select the Automatic option and exit the Change Over menu.

11. Test the new card. Verify that the run LED flashes.

Replacing Jackbox 950-0474

The jackbox is the headset or handset interface for the Acom Console Unit.

Removal:

1. Remove the jackbox audio connection from OAM RJ45 port on the rear of the Acom Console Unit.

2. Using a flat head screwdriver, remove the cover plate of the jackbox.

3. Remove the jackbox by unscrewing it from its mounted location.


268 025-9619A

Installation:

1. Using a flat head screwdriver, remove the cover plate of the jackbox.

2. Secure the jackbox to the underside of the work surface using self-tapping screws. Mount the jackbox far enough away from the front edge of the work surface to prevent the handset connector from protruding.

3. Install the jackbox cover plate using the existing flat head screws.

4. Route the audio connection to the OAM module of the Acom Console Unit and connect it to one of the HS ports (HS1/HS2).

Replacing MCU Cards in an ALS

This procedure is only for an MCU3 or MCU4 in an ALS. For an MCU4 in an ADS, see Replacing MCU Cards in an ADS on page 272.

If an MCU card is installed in slot 0 of an ALS, it is considered the primary MCU; it holds the configuration for the subrack and controls all rack messaging.

Warning! The Primary MCU is NOT hot swappable. Only secondary

MCU cards are hot swappable.

Caution! The new MCU must be the same revision as the one you removed.

Note It is preferred that the power be turned off when swapping out

any cards in the system.

Required Equipment

• Straight-through RS232 serial cable

• (Zetron cable part number 709-7345)

• Laptop/PC with Windows or better and a serial port.

• IMS Program. (Typically installed from the Acom install disk)

• File compression utility if installing using an emailed compressed file.

To backup the MCU configuration:

1. Connect the laptop’s serial com port to port 1 of the MCU card. (Port 1 of the MCU card is the top 9-pin serial connector on the front of the MCU card, labeled X17 on the PCB.)

2. Launch IMS ALS on the laptop.

3. From the main menu, select Communications then Connect.


269

4. When prompted, enter the Network Address of the subrack, and click OK. (The network address is typically on a label on the subrack. Additionally, it may be found in the As-Built documents for your system.)

5. At the password screen click the default button.

6. If this ALS is part of a Main-Standby setup, force control to the other ALS:


b. Select the Manual option and select the other ALS.

c. Verify the ALS icon in IMS turns light blue to show that the other ALS is in control.

d. Once the other ALS has taken control, select the Automatic option and exit the Change Over menu.

7. Once connected choose File then Save to Disk. Save the file with a descriptive name, for example:

ALS<network address>.cfg


disk. It can take several minutes to completely save the file. When the file save operation is complete, the Progress Meter window will disappear.

8. Choose Configure then Subrack Address write down the subrack address. Also note if this is the Main or Standby ALS.

9. Select the Communications menu then Disconnect to disconnect from the ALS.

To record the current firmware version:



Bits per second = 38400 (default for an MCU) Data bits = 8 Parity = None Stop bits = 1 Flow Control = None



5. Once logged in, type in the command ver and press Enter.

6. Record the results.


270 025-9619A

To remove the old MCU card:

1. Power down the subrack by setting the toggle switch on the MSU card to the up position.


3. If the cables are not labeled, label them now so you know where to plug them in on the new card.

4. Disconnect all cables from front of MCU card.

For SMB connections, grab them at the elbow with the thumb and index finger, and pull gently straight out.

If a net clock connection exists, make a note of the port it is connected to before removing it.

5. Flip the top lever on MCU card to dislodge it from the backplane connector. Slide the card out slowly and carefully.


To install the new MCU card:






Do NOT connect the SMB cables to the new MCU at this time.

6. Apply power to the subrack and verify that the top right green LED is blinking slowly approximately once per second. This shows that the MCU up and running.

To verify or upgrade the firmware of the card:

Note The sub rack will not function while updating the firmware on a

Primary MCU card.

Requirements:

• A compressed MCU3 firmware update file. This is typically supplied via email from Zetron technical support or located on the Acom Install CD. The supplied file may be titled “ALS_100.zip” or similar.



Bits per second = 38400 (default for an MCU) Data bits = 8 Parity = None


271

Stop bits = 1 Flow Control = None




Note If the firmware version is the same as recorded in To backup the

MCU configuration: on page 83, then skip the remaining steps in this procedure and proceed to the next procedure.

6. At the prompt, type Download and press Enter. This command will cause the MCU to prompt for an Xmodem transfer by sending a “C” character repeatedly.



result in a dead MCU card. The only way to recover a dead MCU card is to send it to Zetron for repair.

Note The MCU supports the compressed file format. After the

compressed file has been transferred, the MCU will CRC check the compressed file, uncompress it, and update to flash. It is recommended that you keep the firmware update in the compressed file and do not uncompress it before transferring to the MCU. This will minimize the transfer time and protect the bin file with the CRC checking provided by the compressed format.

8. After the MCU has reset itself and appears to be operating again, press Esc three times to get another “Password” prompt.

9. Type ver and note the results.

To restore the ALS configuration: (only if replacing MCU in slot 0)

1. On the laptop, launch IMS ALS.

2. Select “Communications” then “Connect”.

3. Enter the network address of 1 when prompted, and click OK.


4. At the password screen, click default.

5. Click File, then Load From Disk and choose the file name that was saved in To backup the MCU configuration on page 268.

6. Select File, then Update To Rack to transfer the new file to the ALS.


272 025-9619A

7. When prompted for the network address, use the one that worked correctly in Step 3.

8. When prompted for the configuration name, use the one supplied, which should be the name of the MCU that was replaced.

9. Select Configure, then Subrack Address.

Set the subrack address to the value recorded in To backup the MCU configuration on page 268, then click Save.

10. When the rack is back up and running (top right LED on MCU card is blinking slowly), reconnect and verify the network and subrack addresses.

11. Click Configure, then Network Address.

Set the network address to the same value recorded in To backup the MCU configuration on page 268, then click Save.

12. Click Tools, then Reset Rack from the IMS menu to finalize the changes.

13. Click File, Update To Rack.

14. Power down the rack and reconnect the SMB cables to the MCU.

15. Power up the rack.

Within a minute or two, the rack should be operating normally. Only the top right green LED on the MCU should be flashing and on if everything is normal.

To switch back to this rack and test:

1. Select Tools, and then Change over.

2. Set “Mode” to manual.

3. Under “Select Active Device” click the button for the offline rack. This should force a cut over back to this ALS.

4. Set “Mode” back to Automatic.

5. Verify in IMS Terminal that this subrack is now blue (active-OK) and the other rack is green (standby-OK)

Replacing MCU Cards in an ADS

This procedure is only for an MCU4 in an ADS. For an MCU3 or MCU4 in an ALS, see Replacing MCU Cards in an ALS on page 268.

Required Equipment

• Zetron straight through cable part number 709-7345

• PC/Laptop equipped with Windows or better and an RS232 Serial Com Port

• IMS ADS software (installation for this software is located on the Acom Install CD)

• File compression utility (this may be required if the firmware file is not in compressed format)


273

To verify MCU4/ADS is not active:

1. If this is a standalone ADS, skip to the next procedure To record the firmware version: on page 258.

If this ADS is part of a redundant setup with two or more ADSs, then continue.

2. Make sure no E1 links are active on the ADS. This can be verified by viewing the second row of green LEDs (right below the top right flashing green LED) on each MCU4 card in the ADS. For a diagram of MCU LEDs, see Figure 12. LED Indicators on an MCU4 Card on page 257.

If any of these LEDs are lit solid, there is either a link to an Acom Console Unit/ACU or an active link to an ALS. Consult the system Network Diagram or follow the cables and make sure it is NOT an active E1 link to an ALS.

If there are no active E1 links to an ALS, skip to the next procedure, To record the firmware version: on page 258. If there are active links to an ALS, make sure that all ALS E1 links are switched active to the other ADS:





To record the firmware version:

1. Connect the programming cable to the DB9 connector on the MCU. This is X17.






6. A menu should appear with some selections. Enter 1 and press Enter.


8. Record the results for Release and Library.

9. Press the Esc key then press X to exit debug.

Warning! The new MCU4 must be the same revision as the one you

are replacing.


274 025-9619A

Note Although the MCU4 card is hot swappable, it is preferred that the

power be turned off when swapping out any cards in the system.

10. Ground yourself with an ESD wrist strap to the ADS rack.

Warning! If the cables are not labeled, label them so you know where

to connect them on the replacement card.

11. Disconnect the SMB connections from the front of the MCU4 card by grasping the gold connectors and pulling on them. DO NOT pull on the cable itself or you may damage the cable. If your MCU is equipped with RJ45 connectors, disconnect them now.

12. Disconnect the DB9 serial cable.


14. Remove the card and place in an ESD bag.

To install the MCU4:

1. Ground yourself with an ESD wrist strap to the rack.



4. Slide the card into the subrack and press the card into the rear connector using both hands on the front of the card.

5. Apply power to the subrack by turning on (down) the MSU card.

6. Verify LED activity.

To verify and update the firmware version:

1. It is necessary to make sure the MCU4 card installed has the same firmware version of the MCU4 card removed.

2. Check the firmware version of the new card and compare it with the firmware version you recorded for the old card (see To record the firmware version: on page 258).

3. If the MCU4 firmware is the same, skip to the topic To reconnect the cables: on page 275.

4. Before you proceed, make sure you have a copy of the MCU4<version>.zip firmware file. If you do not have this file, call Zetron.



Bits per second = 38400 (default for a MCU) Data bits = 8 Parity = None


275

Stop bits = 1 Flow Control = None


8. When the Password prompt appears, enter “8564888” and press Enter.

9. A menu should appear with some selections. Enter 1 then press Enter.

10. At the MCUX> prompt, type download. The character “C” should be displayed repeatedly. This indicates that the MCU is ready for a file upload.



result in a dead MCU4 card. The only way to recover a dead MCU4 card is to send it to Zetron for repair.

Note The MCU4 supports the compressed file format. After the

compressed file has been transferred, the MCU4 will CRC check the compressed file, uncompress it, and update to flash.

12. After the file has been transferred, the MCU4 will flash the file to memory then reset. This will take about 60 seconds.

13. After the MCU4 is online, check the firmware version to verify that the uploaded firmware is now active (see To verify and update the firmware version: on page 274).

To reconnect the cables:


2. Re-connect the cables to the front of the card.

3. Restore power to the ADS by switching the MSU power switch on (down).

4. Wait 120 seconds for the ADS to come on line.

5. If any ALS units were connected to the MCU that was replaced, make the ALS units connected to this MCU4/ADS active by performing a changeover described in Replacing MCU Cards in an ALS on page 268.

6. Test some line resources to verify that the system resources are functional on this MCU4/ADS.

Replacing MSU Cards

Note Please exercise electro-static discharge (ESD) precautions when

handling all cards.


276 025-9619A

Warning! The MSU card is NOT hot-swappable.

To remove the old MSU card from an ALS:

1. If this ALS is part of a Main-Standby setup and it is currently in control, force control over to the other ALS:






3. Remove power from the rack at the fuse or breaker panel.


5. Carefully disconnect the EURO96 connector from the front of the card by squeezing at the top and bottom of the connector while pulling straight out.

6. Remove the Weidmuller 48V power connection from the front of the MSU by pulling straight out.


Install replacement card:

1. Verify that power has been removed from the subrack at the fuse or breaker panel.



4. Review the jumpers on the old card and verify all jumpers are set the same on the new card.

5. Place card old card in ESD bag.

6. Verify MSU power switch is in the UP position.




10. Connect the EURO96 connector and Weidmuller power connector to the front of the card.

11. Apply power to the rack using the fuse panel or circuit breaker.

12. Push the power switch DOWN on the MSU.


277

13. Verify in IMS Terminal that the ALS with the replaced MSU card appears and has no Urgent Alarms.



b. Select the Manual option and select this ALS.

c. Verify the ALS icon in IMS turns light blue to show that this ALS is in control.

d. Once this ALS has taken control, select the Automatic option, and exit the Change Over menu.

15. Test the new card. Verify that the run LED flashes.

Replacing RVA Cards

The RVA card provides Acom with the capability of using recorded voice announcements. The RVA card is hot-swappable. Recorded announcements are stored in non-volatile memory, so recordings are retained even if the RVA card loses power. This also means you can move the RVA card from one slot to another without losing the recordings.



To remove an RVA card:

1. If the ALS that contains the RVA card is part of a Main-Standby setup, force control over to the other ALS:


b. Double click the ALS. From the Tools menu, click Change Over, click the Manual option, and then select the ALS NOT in control.



2. In IMS, make a note of the card’s firmware version; the new card must be the same revision. Ground yourself with an ESD wrist strap attached to the rack.

3. If there is an audio device connected to the headset jack, remove the device.


5. Remove the card and place it in an ESD bag.

To install an RVA card:

1. Ground yourself with an ESD wrist strap attached to the rack.




278 025-9619A

4. Slide the card into the subrack.

5. Press the card into the rear connector using both hands on the front of the card.

6. If applicable, reconnect the audio device to the headset jack.

7. Verify that the card can be seen in IMS and that the run LED flashes.

8. Upgrade the unit firmware if necessary (contact Zetron Technical Support).

9. If necessary, use IMS to download or record your voice announcements to RVA card. (See Acom Software Configuration, P/N 025-9529.)

Replacing SMU Cards

Caution! Please exercise electro-static discharge (ESD) precautions when handling all cards.

The SMU card provides all signaling for the subrack (VOX, DTMF, TRC, AGC, …). It may alternatively be used for VoIP radio interfaces such as OpenSky. This card is hot-swappable.

Note Although these cards are hot swappable, it is preferable that the

power be turned off when swapping out any cards.

No subrack programming is required when replacing these cards.

Required Equipment

• Zetron SMU cable, part number 709-7592-xxx (xxx=cable length)

• PC with Windows, serial com port, and terminal software capable of serial communications

To record the current Firmware version:

1. If the ALS that contains the SMU card is part of a Main-Standby setup, force control over to the other ALS:


b. Double click the ALS. From the Tools menu, click Change Over, the Manual option, and then select the ALS NOT in control.



2. Connect the SMU cable between the PC and the front connector on the SMU. The connector on the SMU is keyed and can only fit properly one way.


4. Open a terminal connection using the COM port connected to the SMU. The COM port should be configured for the following settings:


279

Bits per second = 38400 (default for a SMU) Data bits = 8 Parity = None Stop bits = 1 Flow Control = None



7. Once logged in type the command ver and press Enter, record the results.


1. If the ALS that contains the SMU card is part of a Main-Standby setup, force control over to the other ALS:








To install the replacement card:






6. Verify in IMS Terminal that the ALS is reporting no Urgent Alarms.


280 025-9619A

To verify or upgrade the firmware of the SMU:

Warning! The sub rack will not function properly while updating the

SMU firmware.

Tip SMU update file. This is typically supplied via email from

Zetron technical support or located on the Acom Install CD. The supplied file may be titled “smu_141.raw” or similar.

1. Open a terminal session as described in To record the firmware version: on page 258.

2. Press Esc until you see a “Password:” prompt, it should only take three presses. If you do not get the “Password:” prompt, check the COM port and its settings.


4. Once logged in type the command ver and press Enter, record the results.

Note If firmware version in the new card is the same as the firmware

version recorded earlier in the old card, then the install has been completed.

5. Type Download and press Enter. This command will cause the SMU to prompt for an Xmodem transfer by sending a “C” character repeatedly.



result in a dead SMU card. The only way to recover a dead SMU card is to send it to Zetron for repair.

7. Press Esc three times to get another Password prompt.

8. Type 8564888 and press Enter.

9. Type the ver command again and note the results.

Replacing Telephone Radio Handset Interfaces (TRHI)

The Telephone Radio Handset Interface (TRHI) provides a common point between a phone and radio system to allow a single headset to service both systems. It functions as a jackbox and handset interface, but also as an audio amplifier and switching device.

Removal:

1. Disconnect the ground wire from the rear of the TRHI.

2. Disconnect power from the TRHI.

3. Disconnect the DB9 and Weidmuller connections from the rear of the TRHI.


281

4. Remove the side screws that hold the TRHI to the top cover and remove the unit from under the desk. If you are not replacing this unit, remove the top cover as well.

Installation:

1. Remove the top cover and set the jumpers as required. Refer to the settings of the previously installed unit or refer to your as built documents.

2. Secure the TRHI top cover to the bottom of the writing surface using the supplied screws. Mount the TRHI far enough away from the front edge of the work surface to prevent the handset connector from protruding.

3. Attach the body of the interface to the top cover.

4. Connect the case ground, located on the rear panel, to the central earth ground.

5. Install cable 709-7684 between the DB9 connector of the TRHI and one of the HS ports of the OAM (HS1/HS2). If the TRHI connects to an Acom AIU, then use cable number 709-7629.

6. Reconnect the leads from the TRHI with the labels PTT and HSE to the ACU Digital Input/Output. Refer to your As-Built documents if you are unsure of the connections.

7. Connect the 12V power source to the TRHI.

Replacing UIO Cards

Caution! Please exercise electro-static discharge (ESD) precautions when handling all cards.

Note Although these cards are hot swappable, it is preferable that the

power be turned off when swapping out any cards in the system.


1. If the ALS that contains the UIO card is part of a Main-Standby setup, force control over to the other ALS:







4. Carefully disconnect the EURO96 connector from the front of the card by squeezing at the top and bottom of the connector while pulling straight out.


282 025-9619A


Install replacement card:



3. Review the jumpers on the old card and verify all jumpers are set the same on the new card.

4. Place the old card in ESD bag.




8. Connect the EURO96 connector to the front of the card.

9. Apply power to the subrack.

10. Verify in IMS Terminal that the new card appears and that the slot box for it is green.




c. Verify that the icon in IMS turns blue for this ALS.


12. Test some of the UIO input to make sure they are functional.

General

283

Troubleshooting

General

Use the following general methods to detect and identify problems.

Gather symptoms by running a functional test and checking for alarms and faults.

Other symptoms may arise if you exercise the system. These symptoms may help you find the source of the problem. Check fault logs, system alarms, and LEDs, as they may lead you to the solution.

What has changed?

Ask yourself and others what has changed with the system that might have caused this. For example, recent configuration updates.

Reset the associated device

If you can, reset the associated Acom Console Unit, ALS, or ADS. If your system is redundant, you may not lose any functionality. While this does not help you understand what was wrong, it may correct the fault very quickly.

Troubleshooting

284 025-9619A

Isolate

Break the problem into blocks and isolate them. Can you isolate the problem to one position? One loop? A particular ADS? Is it common to a single line or circuit? A group of lines shared by a line card?

Switch to the backup system and retest; if the problem is now resolved, it may have been localized to the main system. Once you have isolated a problem, understanding what has caused it becomes easier.

Substitute

Once you have isolated the issue, try substituting a spare. Switching to the standby system is a method of substitution. Substitution can help you isolate problems as well.

Call for help

Zetron technical support is available Monday through Friday between the hours of 6:00 AM and 5:00 PM PST. After hours support is available but requires either an MSP or Service Agreement. Your support contract will determine if support is free or requires a credit card. Please have your System ID ready when you call (the ID number is often found on the front of the Zetron cabinets).

For contact information, see http://www.zetron.com.

Specific

Audio Problems on page 284

Console Problems on page 286

Other Problems on page 288

Audio Problems

Incorrect Audio or No Audio

There is no transmit audio from one position; all other positions are fine on page 288

Specific

285

One line has no transmit audio on all positions on page 289

Users cannot hear selected lines in the handset/headset on one console only on page 289

There is no receive audio from a monitored line on one console only on page 289

There is no audio from a line on any console on page 290

Selected or monitored lines do not present parallel operator transmit audio, only receive audio on page 292

Selected lines do not appear in the select speaker on page 293

Select audio does not appear in the select speaker on page 297

Monitored or selected lines are unmonitored or unselected by themselves on page 304

Mute Not Working

Some functions like “Ring Mute” and “Mute All” time out on page 293

The “All Mute” or “Monitor Mute” function does not completely mute the receive audio on page 293

Volume and Audio Quality

Adjacent operators are too loud in my speakers on page 306

The level of the monitored channels cannot be changed on page 294

Crackle or static sound at position on page 304

Noise in speaker, clicking/ticking sound at times. Happens the most during logon on page 305

60 Hz buzz in speakers on page 305

Hearing conversation from an adjacent position in headset or speaker on page 305

Troubleshooting

286 025-9619A

Console Problems

General

The ACS crashes on startup with a Windows error when run from a Windows login without administrative permissions on page 297

Cannot exit to Windows on page 291

Cannot log off ACS on page 291

Cannot select a radio channel on the ACS, console plays a “Bing” sound when line clicked on page 291

The ACS does not show TX indication (yellow text) on radio line on page 291

The ACS did not bring up the dial pad, the button is stuck in the depressed position on page 292

The ACS popup forms, such as dial pad, monitor, and conference, are blocking access to other buttons and cannot be moved on page 292

The time on the console is wrong on page 294

All lines on the ACS gray out during operation on page 294

Intercom fails and ACS plays a “Bing” without connecting to selected console on page 305

Integrator IRR

Integrator IRR is not recording messages on page 302

Integrator IRR is recording blank (silent) messages on page 302

Popup message “IRR failed to record” on page 303

IRR not working. Message: “irr.exe has generated errors and will be closed by Windows, you will need to restart this program, an error log is being created” on page 303

Integrator IRR failure “the currently recording message has exceeded the imposed size limit for a single recorded message. Ensure that your record control configuration parameters are optimally set to avoid recording messages that are too large” on page 304

Specific

287

Console Error Messages

The console displays “Heartbeat Timeout” message on page 290

The console displays “No Audio Interface” message on page 290

The status bar says “SOMETHING.WAV does not exist” on page 292

The Status bar shows “Console Waiting ##” on page 296

The ACS pops up a dialog “Cannot open quick dial database” and does not start on page 298

The ACS pops up a dialog “Line key XX type does not match physical line XX” when loading the form file on page 298

The ACS logon dialog box shows “Fail Over” mode instead of “Online” on page 300

The ACS logon dialog box shows “Offline” mode instead of “Online” on page 300

Popup message “IRR failed to record” on page 303

IRR not working. Message: “irr.exe has generated errors and will be closed by Windows, you will need to restart this program, an error log is being created” on page 303

Integrator IRR failure “the currently recording message has exceeded the imposed size limit for a single recorded message. Ensure that your record control configuration parameters are optimally set to avoid recording messages that are too large” on page 304

Missing or Unavailable Functions

There are missing monitors in the Monitor selection popup. MS1/MS2/MS3/MS4 are gray and not selectable on page 296

The Dial Pad does not have a Send button when an ISDN line is selected / Cannot make calls on ISDN lines on page 297

The Alpha Search button is missing from the Dial Pad on page 298

The Broadcast and Announce buttons are missing from the Intercom popup on page 298

Troubleshooting

288 025-9619A

Headset/Handset/Footswitch

The foot switch does not key the selected radio channel on page 299

The handset/headset does not key the selected radio channel, does not show yellow text on line on page 299

Other Problems

The phone line turns green but will not ring for inbound calls on page 293

The ACS is slow to respond to button presses such as line selection or PTT on page 295

Right-clicking on a radio channel causes a popup dialog to appear instead of causing an instant transmit on page 300

The passwords for the ACS have been lost or forgotten on page 301

The passwords for the ACU, DCU, or MCU have been lost or forgotten on page 301

Hunt Groups are not working; a line is not selected on page 306

Recommended Actions

There is no transmit audio from one position; all other positions are fine

Possible Cause Recommended Action

Handset not detected. If the Status Panel in ACS shows “Speaker”, the handset is not detected. Check its connection and try a different handset. The ACS uses the microphone current to detect the headset/handset.

Console in Demo mode. Check status bar that console is “Online”. May have gone into demo mode because of communications errors.

Microphone is muted. Check the Mute function. If it is flashing, the operator’s microphone is muted.

Recommended Actions

289

One line has no transmit audio on all positions


Bad radio/phone. Check for Tx audio on demarc out of Acom system.

Incorrect radio signaling. Check for Tx audio on demarc out of Acom system. Check for guard tone out of Acom. In IMS, check that TRC frequencies in Radio Tone Database match radio requirements. (See “Radio Tone Database” in Acom Software Configuration, P/N 025-9529.)

Bad line card. Switch to standby system.

Swap card with spare.

Users cannot hear selected lines in the handset/headset on one console only


Handset volume turned down. Check volume controls for handset and for line. Check physical volume control if using a TRHI.

Handset not detected. Check connections, replace handset.

Console in Demo mode. Check status bar that console is “Online”. IMS may have gone into demo mode because of communication errors.

There is no receive audio from a monitored line on one console only


Mute All is active. Check for flashing indication on Mute All function key.

Monitor Mute active. Line may be in Monitor Mute; try toggling the Monitor Mute when there is active audio.

Speaker volume turned down. Check physical volume control on speaker. Check that LED on speaker is lit (indicating the speakers has power).

Line is selected. Selected lines are removed from the monitor speaker.

Troubleshooting

290 025-9619A

There is no audio from a line on any console


ADS digital I/O incorrectly wired. Check LEDs on ADS. The active E1 links for the connected ALS should have solid green LEDs, not flashing green. Check changeover wiring and ADS I/O power. Only active ALS receive audio is connected to backbone.

Line is not triggering VOX. Check for VOX indication on line. VOX or CD is required to gate audio on half-duplex conference or patch.

Bad radio/phone. Check demarc for Rx audio. Generate tone into Acom to test.

The console displays “Heartbeat Timeout” message


Loss of communications with Acom Console Unit.

Click Retry on popup.

Check serial cable between PC and Acom Console Unit.

Check ACS baud rate and port in AcomConsole.ini file. (9600 baud and COM2 are the default, but your system may be different.)

Loss of communications with ADS. Check Acom Console Unit LEDs A and B for green indication indicating ADS communications.

Check ADS for faults or alarms.

Duplicate Acom Console number in system.

Check all serial and audio interfaces for console number. In IMS, verify the console ID against the network diagram. Turn off other Acom Console Units, reset all ADS, and retry ACS. Turn on one position at a time to find conflict.

The console displays “No Audio Interface” message


Audio definitions were changed. Click OK and retry ACS.

Reset Acom Console Unit after making changes to OAM.

ACS looking for audio interface for radios.

Check AcomConsole.ini file for HandsetOnly setting. If you have only configured Headset audio interfaces on OAM then you must have HandsetOnly=True in the AcomConsole.ini file to combine radio and telephone audio into one time slot on an E1.

Recommended Actions

291

Cannot select a radio channel on the ACS, console plays a “Bing” sound when line clicked


ACS looking for audio interface for radios.

Check AcomConsole.ini file for HandsetOnly setting. If you have only configured Headset audio interfaces on OAM then you must have HandsetOnly=True in the AcomConsole.ini file to combine radio and telephone audio into one time slot on an E1.

Console not communicating with ADS. Check the status bar to see if the console is online.

Cannot log off ACS


Lines are selected or monitored. Clear lines and monitors before logging off.

Edit the following AcomConsole.ini setting:

AllowLogoffIfLinesActive=True

If this setting is not in the AcomConsole.ini, add it within the [ACS] section.

Cannot exit to Windows


Operator forgot exit password. Delete all ACS.#PW files from folder to reset password to “8564888”.

UMS permissions are preventing user from exiting.

Check UMS using Zetron Account Manager application (ZAM).

Log off and log on as “admin”.

The ACS does not show TX indication (yellow text) on radio line


AcomConsole.ini not set to show yellow text.

Verify that DisplayOutgoingPTT=True in [Radio Lines] section of AcomConsole.ini.

IMS is not configured to pass PTT status. Check that the line has the “Indicate PTT Source” checked in IMS. (See “MCU 3/4 Card Options” in Acom Software Configuration, P/N 025-9529.)

Troubleshooting

292 025-9619A

Selected or monitored lines do not present parallel operator transmit audio, only receive audio


IMS not configured to present operator transmit audio.

Check that “Tx and Rx on Monitor” and “Tx and Rx on Group” are checked in IMS for the line. (See “MCU 3/4 Card Options” in Acom Software Configuration, P/N 025-9529.)

Console Cross Mute enabled. Check Acom Console Unit audio interface configuration for any console cross mute. (See “Console Interface Tab” in Acom Software Configuration, P/N 025-9529.)

The status bar says “SOMETHING.WAV does not exist”


Sound file SOMETHING.WAV was not found. The console attempted to play it because of an event.

Copy the file into the ACS folder.

Change the AcomConsole.ini file to point to another sound.

The ACS did not bring up the dial pad, the button is stuck in the depressed position


Multiple phone lines are selected. If more than one phone line is selected, the program does not know which to dial on. In these conditions, the Dial Pad button will appear in the depressed position, waiting for the operator to touch/click one of the selected lines to use for dialing.

The ACS popup forms, such as dial pad, monitor, and conference, are blocking access to other buttons and cannot be moved


The title bar is not enabled for pop-ups. The pop-ups may have been locked in place by the AcomConsole.ini file; check the [Screen Positions] section for a “N” option that would disable the title bar on these pop-ups.

Recommended Actions

293

The “All Mute” or “Monitor Mute” function does not completely mute the receive audio


The mute level is set too high. This function attenuates the monitored line to a preset level setup in the AcomConsole.ini file. The Monitor Mute Set function can override this level. The default mute level is also set in the AcomConsole.ini file.

Some functions like “Ring Mute” and “Mute All” time out


Time-out set too low in the AcomConsole.ini file.

The time-outs are set in the AcomConsole.ini file for these options. Check the [Timeout Periods] section. Set the timeout to 0 seconds to disable.

Selected lines do not appear in the select speaker


The Speaker Enable function is not active.

Use the Speaker Enable function to place the console in “Dual” mode where selected channels are in the handset and speaker.

The wrong speaker has been selected for select audio.

Use the Locate Audio function to choose the speaker to receive select audio. This can be defaulted in the AcomConsole.ini file under the [Interfaces] section.

The phone line turns green but will not ring for inbound calls


The line is ring disabled. Check the line’s ring enable state. If the state shows “RD” at the bottom of the key, its ring is disabled. Use the Ringer Enable function key to enable your phone lines.

The PC sound properties are adjusted to levels that will not work correctly.

Open the Windows volume control and move the master volume and wave volume to half way. Verify they are not muted.

The monitor speaker is turned off or the volume is down.

Check the volume settings on the monitor speakers. PC tones play through the monitor speakers.

The console has the Ring Mute function active.

Check that the Ring Mute function is not active.

Troubleshooting

294 025-9619A

The level of the monitored channels cannot be changed


Operator error. There is a specific order of steps that must be followed:

Press the “Level” button on the Monitor popup.

Click channels to apply the set level to them. (Their level will be shown on the line key in negative dB.)

The time on the console is wrong


The system time is wrong. The console time is set by the Acom Console Unit on startup. The Acom Console Unit time is set by the first ALS in the system. Change the time on that ALS or your setting will not keep.

The console is set to not take the time from the system.

Check the Acom Console Unit IMS data port setting; verify that the “No Time Updates” option is NOT checked. (See “Console Data” in Acom Software Configuration, P/N 025-9529.)

The console’s time zone is incorrectly set. The ACS Time and Date controls use the local PC time zone info to convert the Acom system time to the needed Time and Date controls. Check the Windows Time Zone setting.

The ACS time control is set to the wrong time zone.

Check the “TimeSourceZone” setting of the AcomConsole.ini file.

All lines on the ACS gray out during operation


The ADS has reset or been lost. Check the ADS for alarms or faults. It holds the line key database for the connect ALS units.

The ALS that provides the lines has been lost.

Check the ALS that provides the lines, it may have lost power or E1 connectivity with the ADS. The redundant ALS may not have taken control; check changeover signaling.

Recommended Actions

295

The ACS is slow to respond to button presses such as line selection or PTT

ACS slowdowns and unresponsiveness is caused by excessive E1 messaging.


Bad or high-loss E1 links. Bad E1 links that repeatedly make, and then break their connection can cause consoles to log on repeatedly.

Check for E1 alarms/faults to find the break.

Use an E1 meter/test set to measure loss on the loop.

Many consoles logging on at once. After the consoles finish logon, the system will speed up. Try only logging on a few positions at a time.

Many PTT messages from consoles. The system design could reduce the effect of many console PTTs. Move busy consoles off of ADS with radio ALS units or a lot of other consoles to an ADS with phone lines. (Contact Zetron Technical Support.)

There are duplicate console addresses in the system.

In IMS, check that the Console ID of this Acom Console Unit is unique. Check all data and audio interfaces. Reset the entire system (all ADS/Acom Console Units), if you feel there are duplicate addresses, to clear the problem.

Many CD messages from ALS. Radio ALS units generate many CD messages as the carrier goes active/inactive.

Increase the VOX hold time. (See “Level Settings Tab” in Acom Software Configuration, P/N 025-9529.)

Increase the E-Lead tail debounce. (See “EMU Card Options” in Acom Software Configuration, P/N 025-9529.)

Enable the PTT sliding window in IMS to limit the max number of CD messages.

Find the source of the carrier detects; there may be a bad radio or radio link.

Troubleshooting

296 025-9619A

There are missing monitors in the Monitor selection popup. MS1/MS2/MS3/MS4 are gray and not selectable


IMS configuration incorrect. Verify you have configured each monitor speaker in the Acom Console Unit’s OAM. (See “Configuring Acom Console Unit Parameters” in Acom Software Configuration, P/N 025-9529.)

E1 time slots have been exceeded. Verify that you have not assigned more audio interfaces than you have time slots on the E1 loop. (See “Acom Definitions” in Acom Software Configuration, P/N 025-9529.)

The Status bar shows “Console Waiting ##”

The ACS is talking to the Acom Console Unit but not the ADS and issues this message to notify the user.


The Acom Console Unit has just reset. Wait for at least 30 seconds for the Acom Console Unit to regain communication with the ADS. Check the fault logs.

There are duplicate console addresses in the system.

Check that the Console ID of this Acom Console Unit is unique. In IMS, check the addresses all data and audio interfaces. Reset the entire system (all ADS/Acom Console Units) if you feel there are duplicate addresses, to clear the problem.

There is a duplicate network address in the system.

Check that all Acom Console Units have a unique Acom network address. Reset the system if a duplicate is found.

The ADS servicing the Acom Console Unit is bad.

Check the A and B LEDs on the back of the Acom Console Unit for indication on ADS connectivity.

Check the fault logs and alarms.

Recommended Actions

297

Select audio does not appear in the select speaker


The Speaker Enable function is off. Check that the Speaker Enable function is active (blinking). If the handset is removed, it should move select audio to the speaker as well.

Speaker has become disconnected. Check the physical connection to the speaker.

Speaker volume turned down or unplugged.

Check the volume level and the power LED on the speaker.

Select audio routed to wrong speaker. Check AudioPanelLocation and HandsetLocation in the AcomConsole.ini file in the [Interfaces] section. These settings may have been set to a non-existent speaker.

The Dial Pad does not have a Send button when an ISDN line is selected / Cannot make calls on ISDN lines


The console does not know the line is ISDN.

Change the AcomConsole.ini setting [Line Key Data] “Check” to a value of True. When True, the ACS will compare each line against the ALS configuration.

The IMS configuration does not identify the line as ISDN.

Check the IMS programming for the phone line. It should have a sub type of ISDN. (See “Acom Definitions” in Acom Software Configuration, P/N 025-9529.)

The ACS crashes on startup with a Windows error when run from a Windows login without administrative permissions


The Borland database user file has restricted access and is causing an access violation when the ACS attempts to load the Borland databases.

Give full permissions to Everyone for the file “C:\PDOXUSRS.NET”. User or Super User accounts may not have read/write access to this file, thus causing an access violation.

Troubleshooting

298 025-9619A

The ACS pops up a dialog “Cannot open quick dial database” and does not start


The Borland database engine has not been installed.

Install or re-install the Borland database engine (BDE). It is used for database access by the ACS.

The Quickdial database files are missing or corrupt.

Replace the quicktel.*, quickpage.* files with backups or reinstall the ACS.

The ACS pops up a dialog “Line key XX type does not match physical line XX” when loading the form file


The ACS form configuration does not match the IMS programming for the line.

Radios should be Radio Base buttons.

EIE phones lines should be Autolines buttons.

TIE hotlines should be CB Phone buttons. CB Phone lines should have the default dial type set to “None”.

Check the button line assignments in Console Designer.

The installer does not want the operator notified of the bad line configuration, how do I stop this notice from appearing?

Change the AcomConsole.ini setting [Line Key Data] HideMismatchResults to a value of True.

The ACS form has lines that do not exist in the IMS configuration.

Remove the lines or accept the popup.

The Alpha Search button is missing from the Dial Pad


The button has been removed in the AcomConsole.ini.

Setup the following setting in the [Dial Pad] section of AcomConsole.ini.

ShowAlphaSearchButton=True.

The Broadcast and Announce buttons are missing from the Intercom popup


The button has been removed in the AcomConsole.ini.

Change the AcomConsole.ini setting [Intercoms]

ShowAnnounce= and ShowBroadcast= to a value of True.

Recommended Actions

299

The foot switch does not key the selected radio channel


Foot switch incorrectly wired. Check connections between foot switch and console. It may be connected to TRHI, a digital input, or the DCOAM. (See “Foot Switch” in the “as built” drawings.)

The digital input is not configured correctly.

Check the digital input programming in IMS (see “Acom Definitions” in Acom Software Configuration, P/N 025-9529) and the AcomConsole.ini file [Digital Inputs] section.

The handset/headset does not key the selected radio channel, does not show yellow text on line


The TRHI is set for use with a 4-wire handset.

Check the jumper settings if using a TRHI jackbox. (See the Telephone Radio Headset Interface Product Manual, P/N 025-9553.)

Radio channel is configured as full duplex.

In general, radios should not be configured as Full Duplex, even if you can Tx and Rx at the same time. Just leave off CD Muting if the channel is full duplex. The full duplex option activates the M1 and M2 leads whenever the line is selected. (See “Acom Definitions” in Acom Software Configuration, P/N 025-9529.)

The radio is keying but the yellow channel text is turned off.

Check that the AcomConsole.ini setting [Radio Lines] DisplayOutgoingPTT is set to True.

The OAM audio interface is set for volume control.

Configure the OAM port for “Use vol pot as PTT”. (See “Operator’s Audio Module” in Acom Software Configuration, P/N 025-9529)

The ACS is in demo mode. Because of a serial timeout the ACS has entered demo mode (Offline). Shut down and restart the ACS and watch for Online in the status bar.

Troubleshooting

300 025-9619A

Right-clicking on a radio channel causes a popup dialog to appear instead of causing an instant transmit


The ACS is in “Maintenance Mode” Press CTRL-ALT-M to return the console to normal mode. Maintenance mode is used for troubleshooting and will cause problems with instant transmit. Check the properties of the ACS shortcut for a “/m” command line argument. The “/m” argument starts the console in maintenance mode.

The ACS logon dialog box shows “Fail Over” mode instead of “Online”


The ACS is unable to connect with the UMS Server.

Retry server.

The ACS can make use of Zetron’s User Management System for controlling permissions. Check for a network problem.

Try to ping the UMS server.

Check that the UMS Server service and the Apache service are running on the server. You can check services from Control Panel -> Administrative Tools.

If other consoles are successfully communicating with the UMS, try rebooting the PC.

Open ZAM to check the configuration of this console. Ensure that it is pointing to the correct server.

The ACS has been incorrectly configured to require UMS on a non-UMS system.

Check that the AcomConsole.ini parameter [ACS] EnableUMS= is set to False.

Try to log in using an offline account to get the ACS running.

Offline accounts are “z_admin” or “zg_admin” with no password (leave blank).

The ACS logon dialog box shows “Offline” mode instead of “Online”


ZAM is not configured for Online mode. When offline it will not attempt to connect to the UMS server, it will use the local offline databases.

Open ZAM and login with user “z_admin” (no password).

Change the Workstation settings to Online mode. Set the Server Host to the name of the UMS Server and click Apply.

Recommended Actions

301

The passwords for the ACS have been lost or forgotten


Operator forgot exit password. Delete file ACS.1PW from folder to reset password to “8564888”. You can use the Chg_psw.exe application to change it to something else.

Operator forgot logon password and is using UMS.

Use the Zetron Account Manager (ZAM) to change the password on the account. If you cannot get into ZAM, try using logon admin with no password, or else try “zg_admin” with no password.

Operator forgot logon password and is NOT using UMS.

Delete file ACS.3PW from folder to reset password to “8564888”. You can use the Chg_psw.exe application to change it to something else.

Operator forgot supervisor password (databases).

Delete file ACS.2PW from folder to reset password to “8564888”. You can use the Chg_psw.exe application to change it to something else.

The passwords for the ACU, DCU, or MCU have been lost or forgotten

The default password for all of these devices is 8564888. If you have changed the password from its default and cannot remember or find the password, it can be recovered by calling Zetron Technical Support.

Troubleshooting

302 025-9619A

Integrator IRR is not recording messages


Using contact closure control. Did you configure a 2-axis, 2-button joystick in Windows?

Use the Windows Game Controls control panel to view the state of the joystick inputs. Button 2(Radio) should turn on when the Acom Console Unit commands the IRR to record.

Look at the LED on the back of the Acom Console Unit’s 4-Wire E&M Module. The M1 LED should turn red when the Acom Console Unit commands the start of recording.

Double-check the jumpers in the IRR module and on the 4-Wire E&M Module for the Acom Console Unit. (See Integrator Instant Recall Recorder, P/N 025-9496, and Integrator Instant Recall Recorder on page 79.)

The orange connector “VREF” on the Acom Console Unit may be upside down; screws should face up.

Using VOX record control. VOX threshold may be set too high or too low. Use the IntIRR VOX Threshold Adjustment to change the threshold. (See “VOX Threshold Adjustment” in Integrator Instant Recall Recorder, P/N 025-9496.)

Using software record control. Ensure the [ACS] EnableIRR= is set to True, EnableIRRSoftwareControl= is set to True, and IRRSoftwareAlias= is set equal to the alias programmed into IntIRR channel setup.

Integrator IRR is recording blank (silent) messages


Playback level set too low. Check IRR playback volume slider control. (See Integrator Instant Recall Recorder, P/N 025-9496.)

IRR playback muted. Check IRR playback mute control. (See Integrator Instant Recall Recorder, P/N 025-9496.)

Recording problem (vs. playback problem).

Verify the PC plays other wave files properly. Try to play the recordings manually from the IntIRR recordings folder.

Recommended Actions

303


No audio from Acom Console Unit. Check the Acom Console Unit voice logger output configuration in IMS. Listen to the audio out of the Acom Console Unit to isolate.

Using wrong SoundBlaster drivers. During the installation of the IRR, you should have canceled the Windows driver install wizard and used the SoundBlaster installation CD to install the drivers.

Installing the other drivers will result in empty recordings. Uninstall the sound drivers and reinstall from the CD.

Popup message “IRR failed to record”


IRR is closed. Launch Integrator IRR. If EnableIRR=True then it should launch on ACS startup.

Problem with SoundBlaster drivers. Uninstall and reinstall the SoundBlaster drivers from the SoundBlaster install CD.

IRR not working. Message: “irr.exe has generated errors and will be closed by Windows, you will need to restart this program, an error log is being created”


Hardware problem with sound card. Remove and reinstall SoundBlaster card.

If problem continues, replace sound card.

Permissions problem. Verify IRR has full access to its folder and registry privileges. Your system administrator sets these permissions.

Troubleshooting

304 025-9619A

Integrator IRR failure “the currently recording message has exceeded the imposed size limit for a single recorded message. Ensure that your record control configuration parameters are optimally set to avoid recording messages that are too large”


Large message warning threshold set too low.

Check the options page of Integrator IRR (Edit -> Options) for the warning threshold for max record length. This warning will not stop recording; it only presents the popup. The long recording may be valid; try extending the max length and see if the issue reoccurs.

Recording triggers are not set correctly. Check that the IRR can start and stop recording. If it is set to use VOX, the threshold may be too low.

Monitored or selected lines are unmonitored or unselected by themselves


ADS has reset. Check fault logs and alarms for signs of a reset.

Check power into ADS.

Contact Zetron for more info on monitoring ADS resets.

Acom Console Unit has reset. Check fault logs and alarms for signs of a reset.

A/C power cable may be loose.

ALS has reset. Check fault logs and alarms for signs of a reset.

Crackle or static sound at position


Hardware problem with backbone switch. Force system from A- to B-side and retest, may be ADS issue.

Noise is isolated to one Acom Console Unit.

Replace Acom Console Unit.

Crackle is from lines. Listen on demarc for sound, may be coming from some external source.

Recommended Actions

305

Noise in speaker, clicking/ticking sound at times. Happens the most during logon


Speaker cables run next to serial data cable.

Re-route audio and data cables away from each other to prevent coupling of noise.

60 Hz buzz in speakers


Transformer coupling onto speaker cable. Re-route audio away from transformer.

Try moving transformer to another A/C receptacle.

PC-tones cable not grounded to PC. Check that PC-tones audio cable is connected to PC sound card. Try replacing cable with spare.

Hearing conversation from an adjacent position in headset or speaker


Parallel console has been assigned the same E1 time slot as the local position.

Check IMS E1 definitions (see “Dual E1 Module” in Acom Software Configuration, P/N 025-9529). Two consoles may be using the same time slot. Reset Acom Console Units to force reallocation of audio interface time slots. When the Acom Console Unit is reset, it is assigned audio interface E1 time slots by the ADS if configured for “Define External Device” or “Configure Acom Console Unit over E1 Link” in IMS.

Cross-talk occurring on external circuits. Check punchdown blocks for possible cross talk on the system’s receive.

Intercom fails and ACS plays a “Bing” without connecting to selected console


The destination console is busy. The destination console may not have another free intercom button to receive the intercom call on.

The destination console is not online. The destination console may not be logged in or the ACS is not started.

Troubleshooting

306 025-9619A

Adjacent operators are too loud in my speakers


Operator’s microphone sensitivity is too high.

Use IMS ACU to reduce the Rx gain on the OAM microphone channel. (See “Operator’s Audio Module” in Acom Software Configuration, P/N 025-9529).

Try disabling operator AGC on the Acom Console Unit to reduce input gain. (See “Operator’s Audio Module” in Acom Software Configuration, P/N 025-9529).

Operator is too close, causing feedback. Enable position cross muting for the adjacent positions in IMS. (See “Operator’s Audio Module” in Acom Software Configuration, P/N 025-9529).

Turn off the “Enable Tx and Rx on Group” and “Enable Tx and Rx on Monitor” to remove parallel operator Tx audio from selected and monitored channels.

Hunt Groups are not working; a line is not selected


The AcomConsole.ini file can point toward the Acom Console Unit or the PC database for the Hunt Group configuration.

Check the AcomConsole.ini file setting [Hunt Groups] UseDatabase= setting. If =True it will use the DBEditor database, or else it will use the IMS ACU configuration for the Hunt Groups.

None of the lines in the Hunt Group are visible on the screen.

You must configure the lines in the Hunt Group on the ACS form file.

All of the lines in the Hunt Group are in use.

Clear and unmonitor the lines in the Hunt Group.

The Dial pad is not using the hunt group when no lines are selected.

Check the AcomConsole.ini setting [Line Selection] DialPadHuntGroup=X

X = the number of the Hunt Group (1-8)

Recommended Actions

307

Glossary

Term Description

2-Wire Interface A term used to describe Tip and Ring connections to telephone handsets and exchanges. The Acom TIE and EIE cards use 2-wire to 4-wire converters to allow connection to 2-wire interfaces and provide separate receive and transmit audio paths to the MCU card in the ALS.

ACD Automatic Call Distribution

ACS Acom Console Software

ACU Acom Console Unit

ADS Acom DS3 Switch

AFD Acom File Distributor

AIS (Alarm Indication Signal)

A signal that replaces the normal data stream with a continuous string of 1s when a maintenance alarm has been activated. Such maintenance alarms include NOS and LOS.

A-Law A nonlinear companding (compressing-expanding) function for analog-to-digital conversion of voice signals. It provides a higher digital resolution at low signal levels to give an improved signal-to-noise ratio.

ALI Automatic Location Information

ALS Acom Line Subrack

AMUX Acom multiplexer

ANI Automatic Number Identification

Backplane Each Acom subrack contains two backplanes, an upper and a lower. They are used to connect signals and power supplies to each of the cards contained in the subrack.

Bearer A communication link. For example, a point-to-point digital radio link may have two bearers — one at 2.4 GHz and one at 2.5 GHz. Each bearer could be used independently or in a redundant configuration.

BER (Bit Error Rate)

The ratio of bit errors to bits received in a given period. For example, a BER of 1x10-6 means that for every million bits received, on average one bit has been corrupted. BER is used to measure the quality of a digital communication path.

Glossary

308 025-9619A

Term Description

Branching Connection Used to describe a point-to-point connection, such as the connection of a time slot to a line card channel. In the IMS package the term “normal connection” is used to describe a branch connection.

Broadcast Connection Used to describe a point-to-multipoint connection. With this type of connection, one time slot (or line card channel) is broadcast to a multiple number of line card channels.

CAD Computer-Aided Dispatch

CAS (Channel Associated Signaling)

CAS is a transmission protocol used by G.704 systems to transmit signaling data associated with the line cards. Such signaling data includes handshaking signals for the DIU1-2 card and E&M signals for an EMU card. The CAS protocol places the signaling data in TS16 of each frame.

CCC Changeover Control Card

CCC-E Changeover Controller Extender Card

CCE (Common Control Equipment)

Comprises all backroom system elements such as racks and card cages.

CCU Common Controller Unit

CDS Console Design Software

Channel Used to describe the point-to-point communication path with in the Acom system. It is also used to describe and single interface circuit on any of the system line cards.

CLI Calling Line Identification

Clipping Audible distortion that occurs when a signal’s level exceeds the limits of the amplifier circuit. When the analog signal is a sine wave, clipping results in a waveform with a “flat top.” Clipping can be reduced by decreasing the input signal amplitude to the amplifier or by reducing the gain of the amplifier.

Clock

Clock Signal

Clock Source

A precise timing signal generated by a quartz crystal. In the Acom system the clock is used for system synchronization and as a timing base for the G.704 links.

CMOS Complementary Metal Oxide Semiconductor

CND Calling Number Display. The phone number of the service used by the calling party will be displayed automatically to customers who subscribe to CND Services.

COC Changeover Control card

CODEC (Coder/Decoder)

A CODEC (Coder/decoder) is a device that converts analog signals to digital signals and vice versa. In the Acom system, Codecs are used to convert the analog voice signals to and from 8-bit PCM bit streams.

Codirectional Interface Codirectional is normally used to describe an interface where both data and timing signals are transmitted in the same direction. This means that a receiver is sent both data and a synchronizing clock signal from the transmitter.

Recommended Actions

309

Term Description

Companding Literally means compression and expanding. It is a term used to describe a type of signal conditioning that is used to improve some characteristics of audio signals. See A-law and Mu-Law.

COR Carrier Operated Relay

COS Changeover Subrack

COV-R Changeover card (RJ-21) for voice

COV-T Changeover card (SMB coax) for data

COV-V Changeover card (Euro/DIN96) for voice

CRC (Cyclic Redundancy Check)

CRC is a technique used by G.704 systems to detect errors in transmitted data. A 4-bit CRC code (called CRC-4) is generated for a block of data, which is then sent along with the data. The receiver compares the received CRC-4 code against the CRC-4 code generated from the received data. If the two codes do not match, then some of the data has been corrupted during transmission.

Crosspoint Switch Also called a “Digital Crosspoint Switch” in this set of manuals. This is a key component that provides the physical switching (connecting) of time slots within the MCU3. The crosspoint switch has an internal switching matrix that allows any input to be connected to any output.

CSR Conferencing Subrack

CTCSS Continuous Tone-Coded Squelch System

CTS Clear To Send

DCD Data Carrier Detect

DCE (Data Circuit Equipment)

This term is used in serial data communication to refer to a device that provides the signal conversion and coding between a DTE and a transmission line. A modem is an example of a DCE device. Two DCE devices are usually connected using a “null modem” serial cable.

DCU DS3 Control Unit Card

Decadic Signaling A system for transmitting telephone numbers using loop break/make (disconnect/connect) pulses. Each break pulse momentarily interrupts the DC voltage on the line. The number of pulses equals the number of the digit transmitted (ten pulses are used to represent the number 0). Also known as pulse dialing.

DID (Direct Inward Dialing)

A phone line dedicated for incoming calls.

Differential Data A method of increasing transmission distances by transmitting data on two wires simultaneously at opposite polarities. The receiver only responds to the difference in voltage between the wires and therefore cancels out the noise picked up on both wires during transmission. RS-422/485 protocols use differential data transmission.

Glossary

310 025-9619A

Term Description

Digital Multiplex Hierarchy This system (described in CCITT Recommendations) allows connection of lower rate multiplexers to higher rate multiplexers in order to construct larger networks. The system is arranged in a hierarchy so that each level in the hierarchy can combine and transmit a whole number of channels from the system below. For example, a system at the 8 Mbps level contains four 2 Mbps channels, each of which in turn contains 32 64 Kbps channels. The Acom system conforms to the Recommendations and can be used with other equipment to form a large communication system.

DIU Data Interface Unit

DPLL Digital Phase Locked Loop

DS3 Digital Signal, level 3 (44.736 Mbps)

DSR Data Set Ready

DTE (Data Terminal Equipment)

A DTE is a device that functions as a data source or sinks for a DCE device. An example of a DTE is a PC; it sends and receives data to and from a DCE device, such as a modem. A straight through cable is usually used to connect a DTE to a DCE device.

DTMF Dual Tone Multi-Frequency

DTR Data Terminal Ready

E&M (Ear and Mouth Signaling)

E&M (Ear and Mouth) signaling originated from early telephone systems to provide a means of establishing calls between exchanges. Modern systems do not use E&M signaling and use either in-band signaling or dedicated data channels to set up calls. E&M leads are now commonly used as multipurpose signaling connections. To avoid confusion, the terms E and M are often replaced by SO (Signaling Out) and SI (Signaling In) throughout this manual set.

Earth Recall Signal A signaling method used in 2-wire analog telephone systems. An earth recall signal is sent by grounding one wire of the 2-wire interface. This function is currently not implemented by the Acom system.

EBER Excessive Bit Error Rate

EIE (Exchange Interface Equipment)

In Acom “EIE” may also refer to the EIE card, which provides an interface to PSTN or PABX lines.

EMC Electromagnetic Compatibility

EMI Electromagnetic Interference

EMU E&M Unit card

EPIC Extended PCM Interface Controller. A type of integrated circuit.

ESD Electrostatic Discharge

ETSI European Telecommunications Standards Institute. A standardization organization in the telecom industry in Europe. They have been successful in standardizing the GSM cell phone system and the TETRA professional mobile radio system.

Recommended Actions

311

Term Description

FAS (Frame Alignment Signal)

A special bit sequence is contained in TS0 of a frame, which allows the receiver to synchronize itself to the incoming data. This frame is transmitted only once per multiframe using the double frame format, 8 times per multiframe if the CRC-4 format is used.

FPGA (Field Programmable Gate Array)

A type of integrated circuit.

Frame Alignment Frame alignment is used by each G.704 interface to gain synchronization with other G.704 devices. The MCU3 achieves frame alignment by looking for frame alignment words within the G.704 data stream. Once frame alignment has been achieved, the MCU3 knows the exact position/time slot of the incoming G.704 data stream.

Frame A fixed-length cross-section of a data stream. A 2 Mbps E1 link has 8-bit long frames, each frame containing one segment of each of the 32 time slots. The relative position of each time slot remains constant from frame to frame. The time slots in a frame are numbered 0-31. TS0 is the first 8 bits (first time slot) of a frame and is used to carry the frame alignment word and other control/error code bits. TS16 is used to carry CAS signaling information and multiframe alignment words in the G.704 link. TS16 may also be used as a standard data channel when using in-band signaling instead of CAS.

Framer A circuit on the MCU3 card that performs the HDB3 conversion and frame alignment of the incoming G.704 data.

Gain A figure used to describe amplification. For example, an amplifier with a gain of two will produce an output signal that is twice the amplitude of an input signal.

Handshaking Handshaking is a term used to describe the signaling lines (RTS, CTS, etc.) of serial communication links such as RS-232.

HDB3 (High Density Bipolar of Order 3)

A tertiary level form of line encoding used in the G.703 specification. HDB3 allows the receiver to extract a synchronized clock regardless of the content of the incoming stream.

HDLC (High Level Data Link Control)

HDLC is a communication protocol used within the Acom system to communicate between devices on the backplane. It is a synchronous, full duplex, framed protocol that allows multiple devices to communicate on one bus.

Hot Plugging

Hot Plug Capable

Hot plugging means inserting or removing a card into a subrack while the power is still applied to the system. All cards within the Acom system are designed to be hot plugged. (MSU3 has some exceptions.)

IDF Intermediate Distribution Frame (or Floor) Distribution

IMS Terminal (Integrated Management System)

A top-level applications package that manages access to the IMS applications for configuration, monitoring, and diagnostics for each part of every CCE and Acom Console Unit in your system. ACS may have the following modules installed: IMS ALS, IMS ADS, and IMS ACU.

Glossary

312 025-9619A

Term Description

IMS (Integrated Management System)

A software suite produced by Zetron for the management of Acom systems. The suite contains several IMS modules that can each run in a stand-alone environment or within ACS. IMS provides a fully functional network management system capable of configuration, remote reconfiguration, fault detection, and diagnostics through a graphical display interface. IMS allows easy configuration and maintenance for the entire system, from general component setting and network adjustments, to individual card configuration.

In-band Signaling In-band signaling is a method use to transmit signaling information. The signaling information is placed into the same time slot as the data for that channel.

IOM-2 (ISDN Oriented Modular bus, version 2)

This is a communication bus used internally by the Acom system that provides a means for communication with voice and signaling interfaces on line cards. It is a framed protocol with data sent in time slots between cards in the subrack.

IPAT (ISDN Primary Access Transceiver)

A type of integrated circuit.

IRR (Instant Recall Recorder)

IRR is an application used to control the voice recording process.

ISB (Intersite Bearer)

A means of interconnecting two or more Acom systems located at different sites to provide remote or backup operation. ISB connections are implemented between ADSs of separate Acom sites, by way of E1 or T1 connections on the MCU4 cards.

ISDN (Integrated Services Digital Network)

A network that provides or supports a range of telecommunication services by providing digital connections between user network interfaces.

LCB Link Control Block

Line Break A term used in telephone systems to indicate a break (opening) of a telephone line. Brief line breaks are used in decadic dialing, while an extended line break is used to release (hang up) a connection.

Line Card This general term refers to the voice and data cards. A line card contains a number of channels to decode/encode local signals that can then be branched to other channels or time slots by using a G.703 link.

Link This term is used to describe a communication path that is used to transfer multiple channels of information. In the case of the Acom documentation, “link” means a connection from a 2048 or 1544 Kbps G.703 interface.

LIT Line Integrity Test card

LLCB Line Logic Control Block — memory that contains information about the lines. See also OLCB.

LMFA Loss of Multiframe Alignment

Recommended Actions

313

Term Description

Loop Detect A term used in telephone line connections. It is a system that detects a call has been answered by checking the status of the DC loop. In the Acom system, the TIE card uses loop detection to determine when a call has been answered. If a loop is detected, the TIE card switches the line from a ringer to an audio circuit.

Loop Out

Loop Seize

Line Loop

Loop out is a DC loop for signaling to the other end of a telephone line. See “Loop Detect.”

LOS (Loss of Synchronization)

This is an alarm condition within the Acom system that is active when synchronization of the G.703 link is not present. This means that the MCU3 Framer is unable to detect the frame alignment word.

Master Clock Each MCU3 card within a subrack has clock generation and selection circuits that are used to generate the timing and synchronization required for data transmission. When an MCU3 is installed in slot 0 of a subrack, it becomes the primary MCU3, and its clock signal is used as a Master Clock for all other cards contained in the subrack. By default the subrack will synchronize to the Master Clock of the primary MCU3 but can be changed to synchronize to other clock signals if required.

MCU (Main Control Unit)

The core of the Acom system is the MCU. The MCU3 comprises a Framer, a digital crosspoint switch and G.703 interfaces and controls the internal backplane interfaces and connections.

MDF Main Distribution Frame (or Building) Distributor

MSU Main Supply Unit card

Multiframe A cyclic set of consecutive frames, in which the relative position of each frame is known. In 2 Mbps G.704 systems, a multiframe may comprise two frames (Double Frame mode) or sixteen frames (CRC-4 mode).

MUSAC A type of integrated circuit; a digital cross point switch used for multipoint switching and conferencing

MUX (Multiplexer)

In Acom documentation the term multiplexer means digital multiplexer: a device that uses time division multiplexing (TDM) to combine multiple digital signals into a single composite digital signal.

Non Urgent Alarm This is a G.732 prompt maintenance alarm condition.

NOS No Signal

NRZ Non-Return to Zero

NTP (Network Time Protocol)

An internationally recognized standard that can be used to synchronize clocking devices on computers and other network devices over the Internet. It is used by Application Layer client-server applications that communicate by way of UDP port 123. Its primary benefit is to counter the effects of variable latency caused by queuing on packet-switched networks. An NTP client fetches a time data stream from an NTP server at regular intervals and corrects local time-keeping devices. It synchronizes to Universal Time Coordinated (UTC) only; it has no knowledge of time zones, Daylight Saving Time, or Summer Time. For more information, see www.ntp.org.

Glossary

314 025-9619A

Term Description

OAM Operator’s Audio Module

OLCB Operator Logic Control Block — memory that contains information about the consoles. See also LLCB.

Omnibus Connection A conference connection where voice signals are converted from A-law to linear and summed before conversion back to A-law. Data signals and channel signaling are also added.

Order Wire A conference connection where an input to a channel is output on all other channels and not the originating channel. May be used for 2-wire telephone conferencing.

P25 (Project 25)

Project 25, also known as APCO-25 but most commonly as P25, Project 25 encompasses a suite of standards to advance interoperability among digital wireless communication products and systems. The P25 standards were created by a committee representing manufacturers, public safety agencies, and other communication professionals, with the intent of ensuring that all purchasers of P25-compatible equipment can communicate with each other. For more information, see www.apcointl.org.

PABX (Private Automated Branch Exchange)

A telephone network commonly used by medium and larger offices, call centers, and other businesses and organizations. PABX provides an efficient internal telephone service with, typically, a single number for outside callers and a limited number of outgoing lines.

Partial Time Slot Allocation Portions of a time slot may be allocated to multiple lower rate devices. For example, two 32 Kbps data sources may be allocated one time slot, with each 32 Kbps data stream only requiring each alternate frame (or 4 of the 8 bits per time slot). See also Subrate Communication.

PCM (Pulse Code Modulation)

PCM is a technique used to convert an analog signal to a serial bit stream. In the Acom system, analog voice signals are digitized into 8-bit words at a sample rate of 8 kHz, producing a serial bit stream of 64 Kbps for each voice signal.

PCM-30 PCM-30 generally refers to the specific case of PCM G.704 where TS0 and TS16 contain framing and Channel Associated Signaling (CAS). The CAS signals contain the signaling information for the other 30 information (voice or data) channels. The data format containing 30 information channels, together with the associated signal data in time slot 16, is referred to as PCM-30.

PE Protective Earth

PLL (Phase Locked Loop)

A circuit that synchronizes an internal oscillator to an incoming signal. A PLL circuit is used on the MCU3 to produce a stable clock signal from the incoming G.703 link.

Primary MCU When the MCU is installed in slot 0 of the Acom Line Subrack, it becomes the Primary MCU, which functions as a system master and provides configuration setup parameters for other MCU cards and line cards installed in the subrack. The MCU detects that it has been installed in Slot 0 and then enables the Primary MCU circuits and functions.

Recommended Actions

315

Term Description

Primary Rate The primary rate is the data rate from which all other rates (both higher and lower) in the digital multiplexing hierarchy are derived.

Protective Earth (PE) An earth point in the building installation that provides earthing for safety purposes. This may also be called “grounding conductor.”

PSTN Public Switching Telephone Network

PTT “Push to talk” or “press to talk”.

Recovered Clock A clock signal derived from the incoming data signal. In the Acom system, this is possible because the G.703 signals use HDB3 line coding, which allows the receiver to extract a synchronized clock regardless of the content of the incoming stream.

Redundant Bearer A channel used to carry the traffic of a failed bearer.

RF Radio frequency

RGU Ring Generator Unit card

Ring Cadence The timing of a ring signal (e.g., 1 second ring, 1 second pause, 1 second ring, 5 second pause, then repeat).

Ring out Signaling

Loop in Signaling

This is a signaling scheme used by 2-wire telephone lines. The signaling is by means of a current loop when the handset is picked up to initiate either a ring out or a loop in.

Ring Signal

Ring Voltage

An AC waveform used to drive the ring circuit of a telephone.

RMS Root Mean Square

RRA Received Remote Alarm

RTC Real Time Clock

RTS Request To Send

RVA Recorded Voice Announcement card

RX Receive

RXD Receive Data

SCC Serial Communication Controller

SDI Slip Direction Indication

SELV (Safety Extra Low Voltage)

A SELV circuit is circuit with no direct connection to mains power. It obtains power from an isolating transformer, isolated power, or a battery. Under a single fault condition, a SELV circuit should not exceed 71V peak or 120VDC.

Service Word This is a term used to describe the contents of time slot 0 in a frame. If the time slot does not contain a frame alignment word, it is called a service word.

Signaling Binary information passed between communicating devices to manage the establishment, clearing, and control of connections. An example of signaling is the handshake used in an RS-232 communication channel.

Glossary

316 025-9619A

Term Description

Slave Clock A clock whose timing output is phase-locked to the timing signal received from another clock.

Slip The loss of a data bit on a T-1 or E-1 link, due to a frame misalignment between the timing on a transmit node and the timing on a receive node.

Slot As distinct from a “time slot,” a slot refers to the physical space and electrical connector available in a subrack for a circuit board.

SMB Coaxial connector for RG179 Cable

SMU Signal Management Unit card

Submultiframe A term used to describe the first 8 frames or the last 8 frames of a CRC-4 multiframe structure.

Subrack This term is used to distinguish from a larger “rack,” which may support several subracks. A subrack is a standard 6RU 19-inch assembly that supports a backplane with sockets for connecting up to 13 cards.

Subrate Communication Connection of one or more low data rate devices to a single time slot. For example, two devices that transmit data at a rate of 32 Kbp/s could be connected (using IMS) to one time slot.

Synchronous Communication A protocol that allows bits of data to be sent at a fixed, synchronized rate between the transmitter and receiver. Sending synchronized data eliminates the need for start and stop bits as used with asynchronous communication.

TIE Telephone Interface Equipment card.

Time Division Multiplexing

TDM

A technique employed in the Acom system for combining multiple electronic signals into one stream by sampling each signal at regular intervals and coding each sample into a separate time slot of the combined stream. A period containing one time slot per signal is termed a frame. Frames are repeated at the signal sampling rate. A G.704 E1 link carries 8,000 frames per second.

Time Slot

TS

In the context of TDM, the data stream is divided into parallel time slots. An E1 link carries 32 time slots, each representing one 64 Kbps channel. Each time slot is divided into serial frames, each 8 bits long.

TNV (Telecommunication Network Voltage)

A circuit that under normal operating conditions carries telecommunication signals. Telecommunication signals are a steady state, varying amplitude, or intermittent voltage or current intended for use on a telecommunication network. A TNV circuit, which is connected to a telecommunication network, may be subject to over-voltages due to lightning or power system faults. TNV excludes the mains supply, TV cable systems, and SELV circuits.

Traffic General reference to data signals, that are intended for multiplexing and demultiplexing within an Acom system. Intended to distinguish from and exclude signals that are used internally to the system, such as for system coordination and CPU operations.

Transceiver A circuit that can connect to a shared bus for the purpose of receiving and transmitting. A cooperative protocol for the bus ensures that only one transceiver on a bus transmits at any one time.

Recommended Actions

317

Term Description

TRC Telecom Reference Conductor

TS Time Slot

TSI Time Slot Interchange

TTL Transistor-Transistor Logic

TX Transmit

TXD Transmit Data

UIO Universal Input/Output card

UMS (User Management System)

UMS is a client/server application used to control system access and privileges.

Urgent Alarm This is a G.732 service alarm condition.

VF (Voice Frequency) An audio signal in the band 300-3400 Hz.

VoIP (Voice over Internet Protocol)

A method for using IP-compatible networks such as a LAN or WAN to convey voice communication or other audio such as radio control tones.

Watchdog Timer A watchdog timer is a circuit that monitors a microprocessor. If the microprocessor stops responding, the watchdog timer will reset the microprocessor in an attempt to resume normal operation.

Glossary

318 025-9619A

IMS Fault Logs

319

Appendix A: Alarms

IMS Fault Logs


Fault Log Input Alarms

Alarm Numbers

IMS Alarm Name

Alarm Description

0 – 7 Digital Input 1 – 8 External Digital Inputs

8 Internal Link Error MCU A link 1

9 Internal Link Error MCU A link 2

10 Internal Link Error MCU B link 1

11 Internal Link Error MCU B link 2

12 Internal Link Error MCU C link 1

13 Internal Link Error MCU C link 2

Internal (FW) alarm generated when the system has detected an error in the E1 link.

14 Internal Link Error MCU reserved for future MCU D link 1

15 Internal Link Error MCU reserved for future MCU D link 2

16 Internal Link Error MCU reserved for future MCU E link 1

17 Internal Link Error MCU reserved for future MCU E link 2

18 Internal Link Error MCU reserved for future MCU F link 1

19 Internal Link Error MCU reserved for future MCU F link 2

20 Internal Link Master MCU A link 1

Appendix A: Alarms

320 025-9619A

Alarm Numbers

IMS Alarm Name

Alarm Description

21 Internal Link Master MCU A link 2

22 Internal Link Master MCU B link 1

23 Internal Link Master MCU B link 2

24 Internal Link Master MCU C link 1

25 Internal Link Master MCU C link 2

Internal (FW) alarm generated when the LCB associated with an E1 link has been set as the active in a changeover system.

26 Internal Link Master MCU reserved for future MCU D link 1

27 Internal Link Master MCU reserved for future MCU D link 2

28 Internal Link Master MCU reserved for future MCU E link 1

29 Internal Link Master MCU reserved for future MCU E link 2

30 Internal Link Master MCU reserved for future MCU F link 1

31 Internal Link Master MCU reserved for future MCU F link 2

31 Card Configuration Difference between saved and installed cards. (Difference may be revision or type.)

32 DS3 Link A Loss of Signal Loss of signal on DS3 Link A

33 DS3 Link B Loss of Signal Loss of signal on DS3 Link B

34 DS3 Link A Loss of Framing Loss of frame alignment/synchronization on DS3 Link A

35 DS3 Link B Loss of Framing Loss of frame alignment/synchronization on DS3 Link B

36 DS3 Link A AIS Alarm Received an Alarm Indication Signal on DS3 Link A.

37 DS3 Link B AIS Alarm Received an Alarm Indication Signal on DS3 Link B.

38 DS3 Link A Failed Unable to remove wrap on Link A.

39 DS3 Link B Failed Unable to remove wrap on Link B.

40 DS3 Link A Wrapped DS3 Link A is currently in “wrapped” mode.

41 DS3 Link B Wrapped DS3 Link B is currently in “wrapped” mode.

42 DS3 Ring Offline The Backbone DS3 ring has come online or gone offline.

43 Incorrect DS3 Port Connection The DS3 Link was unable to negotiate a communications link with the remote end, due to the fact that Port A (or Port B) on the current ADS has been incorrectly connected to Port A (or Port B) on the remote ADS.

44 DCU NV Configuration DCU NV configuration corrupted

45 No backplane time slots available A connection failed because no time slot available on the backplane.

IMS Fault Logs

321

Alarm Numbers

IMS Alarm Name

Alarm Description

46 DCU Packet Memory Exhausted No more memory available in memory pool to allocate to packets for the DS3 backbone or the ADS Backplane HDLC messaging queues.

47 DCU Packet Memory Insufficient Available memory free in memory pool smaller than requested allocation size for a new packet for the DS3 backbone or the ADS Backplane HDLC messaging queues.

48 MCU A Packet Memory Exhausted

No more memory available in memory pool to allocate to packets for the ADS Backplane or E1 messaging queues.

49 MCU A E1 Loss of Signal MCU4 Slot A Link 1 Loss of signal on an E1 Link.

50 MCU A E1 Loss of Framing MCU4 Slot A Link 1 Loss of frame alignment or synchronization on an E1 Link

51 MCU A E1 AIS Alarm MCU4 Slot A Link 1 Received an Alarm Indication Signal on an E1 Link.

52 MCU A E1 Remote Alarm MCU4 Slot A Link 1 Received a remote alarm on an E1 Link.

53 MCU A E1 Remote Alarm 1 MCU4 Slot A Link 1 Received a remote alarm 1 on an E1 Link.


55 MCU A LCB missing MCU4 Slot A Link 1 An LCB is expected but not present (expected is based upon the system receiving a signal on the E1 link).

56 MCU A E1 Framing Slip MCU4 Slot A Link 1 Received an E1 framing slip.

57 MCU A Backup Mode Change MCU4 Slot A Link 1 An LLCB for an LSR is entering/leaving backup mode.

58 MCU A E1 Loss of Signal MCU4 Slot A Link 2 Loss of signal on an E1 Link.

59 MCU A E1 Loss of Framing MCU4 Slot A Link 2 Loss of frame alignment or synchronization on an E1 Link

60 MCU A E1 AIS Alarm MCU4 Slot A Link 2 Received an Alarm Indication Signal on an E1 Link.

61 MCU A E1 Remote Alarm MCU4 Slot A Link 2 Received a remote alarm on an E1 Link.



Appendix A: Alarms

322 025-9619A

Alarm Numbers

IMS Alarm Name

Alarm Description

64 MCU A LCB missing MCU4 Slot A Link 2 An LCB is expected but not present (expected is based upon the system receiving a signal on the E1 link).

65 MCU A E1 Framing Slip MCU4 Slot A Link 2 Received an E1 framing slip.

66 MCU A Backup Mode Change MCU4 Slot A Link 2 An LLCB for an LSR is entering/leaving backup mode.

67-71 MCU A Spare reserved for future

72 MCU B Packet Memory Exhausted


73 MCU B E1 Loss of Signal MCU4 Slot B Link 1 Loss of signal on an E1 Link.

74 MCU B E1 Loss of Framing MCU4 Slot B Link 1 Loss of frame alignment or synchronization on an E1 Link

75 MCU B E1 AIS Alarm MCU4 Slot B Link 1 Received an Alarm Indication Signal on an E1 Link.

76 MCU B E1 Remote Alarm MCU4 Slot B Link 1 Received a remote alarm on an E1 Link.

77 MCU B E1 Remote Alarm 1 MCU4 Slot B Link 1 Received a remote alarm 1 on an E1 Link.


79 MCU B LCB missing MCU4 Slot B Link 1 An LCB is expected but not present (expected is based upon the system receiving a signal on the E1 link).

80 MCU B E1 Framing Slip MCU4 Slot B Link 1 Received an E1 framing slip.

81 MCU B Backup Mode Change MCU4 Slot B Link 1 An LLCB for an LSR is entering/leaving backup mode.

82 MCU B E1 Loss of Signal MCU4 Slot B Link 2 Loss of signal on an E1 Link.

83 MCU B E1 Loss of Framing MCU4 Slot B Link 2- Loss of frame alignment or synchronization on an E1 Link

84 MCU B E1 AIS Alarm MCU4 Slot B Link 2- Received an Alarm Indication Signal on an E1 Link.

85 MCU B E1 Remote Alarm MCU4 Slot B Link 2- Received a remote alarm on an E1 Link.


IMS Fault Logs

323

Alarm Numbers

IMS Alarm Name

Alarm Description


88 MCU B LCB missing MCU4 Slot B Link 2 An LCB is expected but not present (expected is based upon the system receiving a signal on the E1 link).

89 MCU B E1 Framing Slip MCU4 Slot B Link 2 Received an E1 framing slip.

90 MCU B Backup Mode Change MCU4 Slot B Link 2 An LLCB for an LSR is entering/leaving backup mode.

91-95 MCU B Spare reserved for future

96 MCU C Packet Memory Exhausted


97 MCU C E1 Loss of Signal MCU4 Slot C Link 1 Loss of signal on an E1 Link.

98 MCU C E1 Loss of Framing MCU4 Slot C Link 1 Loss of frame alignment or synchronization on an E1 Link

99 MCU C E1 AIS Alarm MCU4 Slot C Link 1 Received an Alarm Indication Signal on an E1 Link.

100 MCU C E1 Remote Alarm MCU4 Slot C Link 1 Received a remote alarm on an E1 Link.

101 MCU C E1 Remote Alarm 1 MCU4 Slot C Link 1 Received a remote alarm 1 on an E1 Link.


103 MCU C LCB missing MCU4 Slot C Link 1 An LCB is expected but not present (expected is based upon the system receiving a signal on the E1 link).

104 MCU C E1 Framing Slip MCU4 Slot C Link 1 Received an E1 framing slip.

105 MCU C Backup Mode Change MCU4 Slot C Link 1 An LLCB for an LSR is entering/leaving backup mode.

106 MCU C E1 Loss of Signal MCU4 Slot C Link 2 Loss of signal on an E1 Link.

107 MCU C E1 Loss of Framing MCU4 Slot C Link 2- Loss of frame alignment or synchronization on an E1 Link

108 MCU C E1 AIS Alarm MCU4 Slot C Link 2- Received an Alarm Indication Signal on an E1 Link.

109 MCU C E1 Remote Alarm MCU4 Slot C Link 2- Received a remote alarm on an E1 Link.

Appendix A: Alarms

324 025-9619A

Alarm Numbers

IMS Alarm Name

Alarm Description



112 MCU C LCB missing MCU4 Slot C Link 2 An LCB is expected but not present (expected is based upon the system receiving a signal on the E1 link).

113 MCU C E1 Framing Slip MCU4 Slot C Link 2 Received an E1 framing slip.

114 MCU C Backup Mode Change MCU4 Slot C Link 2 An LLCB for an LSR is entering/leaving backup mode.

115-119 MCU C Spare reserved for future

120 DCU Boot Error Error starting DCU code, running from backup or failsafe image

121 2Mb Clock Source Error A 2Mb clock source configured to generate an alarm has failed.

Fault Log Output Alarms

Alarm Number

Function

0 Urgent Alarm

1 Non-urgent Alarm

2 Information Alarm

3-10 Represents External Digital Output 1-8

11-16 Internal System Select.

(Used to tell the DS3 that the LCB is the selected active for a changeover. Usually driven by a digital input that is wired to a CCC changeover controller.)

11 – MCU A, E1 Link 1 12 – MCU A, E1 Link 2 13 – MCU B, E1 Link 1 14 – MCU B, E1 Link 2 15 – MCU C, E1 Link 1 16 – MCU C, E1 Link 2

General Alarms

325

General Alarms

The following events will cause an alarm. The columns “urgent” and “non urgent” show the default programming for alarms to the system alarm outputs. (The alarm numbers are used to identify the alarms uniquely within MCU3 and IMS.)

Table 14. Input Alarm Names

No. Alarm Name Urgent Non-Urgent MCU B7 LED

0 Configuration Alarm X

1 64kbp/s G703 NOS X

2 64kbp/s G703 Slip X

3 64kbp/s G703 AIS X

4 2Mbps Slot 0 P1 NOS X

5 Remaining 2Mbp/s NOS X

6 2Mbps Slot 0 P1 LOS X

7 Remaining 2Mbp/s LOS X

8 2Mbps Slot 0 P1 RRA X

9 Remaining 2Mbp/s RRA X

10 2Mbps Slot 0 P1 EBER X

11 Remaining 2Mbp/s EBER X

12 2Mbps Slot 0 P1 Slip X

13 Remaining 2Mbp/s Slip X

14 2Mbps Slot 0 P1 MFA X

15 Remaining 2Mbp/s MFA X

16 2Mbps Slot 0 P1 CRC4 X

17 Remaining 2Mbp/s CRC4 X

18 2Mbps Slot 0 P1 AIS X

19 Remaining 2Mbp/s AIS X

20 2Mbps Slot 0 P1 MRRA X

21 Remaining 2Mbp/s MRRA X

22 Acom Self Test Failure X

23 Ringer Failure

24 Alarms Acknowledged

25 No Alarms Active

26 Not used with Acom

Appendix A: Alarms

326 025-9619A


27 MSU In1 (AI11) System Selected

28 MSU In2 (AI21) Standby Fault X

29 MSU In3 (12) X

30 MSU In4 (AI22) X

31 MSU In5 (AI13) Watchdog

32 MSU In6 (AI23) X

33 Loopback Present X

34 Maintenance Terminal

35 DIU4 Slip

36 DIU4 No Clock

37 DIU4 No HDLC

38 Acom Rack Alarm

39 Acom Site Alarm

40 Console Alarm

41 Backup Alarm

42 Data Alarm

43 Line Alarm

44 Bearer Alarm

45 Remote Alarm

46 LCB Alarm

47 E1-T1 Converter RA (Pri)

48 E1-T1 Converter RA (Sec)

49 Excessive Clipping

50 NA

51 NA

52 NA

53 NA

54 NA

55 NA

56 NA

57 NA

58 SMU Alarm

59 2Mbit Clocking Alarm

ADS Alarms

327


60 MCUx Slot 0 P1 RA1 X




The following input alarms should be monitored closely and will trigger an urgent alarm:

• Standby Fault - Monitors the health of the other rack (main or standby ALS).

• MSUin4 - Monitors power supply alarm.

• MSUin6 - Monitors the health of an ADS.

• MSUin3 - If you have a slave ALS, this alarm is programmed in the master ALS. This is to monitor the health of the slave ALS.

• SMU Alarm - Monitors SMU DSP resources and alarms.

ADS Alarms

This section describes ADS alarms and how they are detected.

Input Alarm Description

Digital Inputs

Purpose

The Digital Inputs are for any general-purpose external alarm input to be used by the ADS. The first six inputs are typically configured to allow the current state of a Changeover Subrack to be known by the ADS.

Appendix A: Alarms

328 025-9619A

Alarm IDs

Note The following table shows a typical configuration.

Alarm Number

Alarm Name

Comment

0 Digital 0 Is typically used internally by the ADS as the Changeover state indicator for MCU Slot 1 Link 1






6 Digital 6

7 Digital 7

Description

The DCU supports eight optically isolated digital inputs. The digital inputs shall be polled at a rate of 100ms. The Digital Input alarm shall be active when a voltage is applied to the digital input.

The first six digital inputs are typically configured to monitor the Changeover State for the first three MCU cards. In this case, each E1 link on an MCU card is assigned a digital input. Therefore, when a digital input is active it indicates that the ALS connected to the associated E1 link is active.

Internal Link Error

Purpose

The Internal Link Error alarm is required to provide a method for the ALS to discover if the ADS it has been connected to is working correctly. A normal setup of the system would define a Digital Output as being activated when the Internal Link Error is active. This Digital Output is then connected to the ALS. The ALS will use this signal to decide if it can be the master ALS or if it must release control to the standby ALS.

ADS Alarms

329

Alarm ID

Alarm Number

Alarm Name

Comment

8 MCU A Link1 MCU Slot 1 Link 1

9 MCU A Link 2 MCU Slot 1 Link 2

10 MCU B Link 1 MCU Slot 2 Link 1


12 MCU C Link 1 MCU Slot 3 Link 1


Description

Each E1 link on an installed MCU card in an ALS system shall support an Internal Link Error alarm. An Internal Link Error alarm can only be generated after an ALS/ACU has started communication with the ALS on an E1 link and caused a Link Control Block to be created (A Link Control Block is only created when the ADS has received a CREATE_OLCB or CREATE_LLCB command from the ACU or ALS). An Internal Link Error alarm shall be activated when any of the following is present for the specified E1 link:

E1 link: No Signal

E1 link: Loss of Sync

E1 link: AIS being received

Link Control Block in Standby mode and Digital Input from Changeover Subrack for this E1 link indicates it is selected.

When the Link Control Block is destroyed (due to the ALS or ACU being removed from the system or having a fatal failure) then the Internal Link Error alarm shall maintain its active state. The alarm can only be cleared once the Link Control Block is created again and all error conditions are cleared.

If a Link Control Block has never been created then the Internal Link Error alarm shall be inactive.

Description for Intersite Bearer

If the port is configured for use as an Intersite Bearer (ISB main, ISB main backup, ISB standby, or ISB standby backup port), the alarm indicates that the port is unable to be used for main/backup/standby.

Appendix A: Alarms

330 025-9619A

Internal Link Master

Purpose

This alarm enables the IMS Maintenance Terminal to indicate which of the ALS links are active.

Alarm IDs

Alarm Number

Alarm Name

Comment







Description

Each E1 link on an installed MCU card in an ADS system shall support an Internal Link Master alarm. A total of six MCU cards are allowed for but support is only implemented for the first three MCU cards. An Internal Link Master alarm can only be generated when an ALS has started communication with the ADS on an E1 link and caused a Link Control Block to be created. An Internal Master alarm shall be activated when the Link Control Block is in the active mode. As such this alarm is actually a state indicator and not a real alarm.

Note This alarm is never generated if an ACU is connected to the E1

link.

When the Link Control Block is destroyed, the Internal Link Master alarm shall be returned to its idle state.

Description for Intersite Bearer

If the port is configured for use as an Intersite Bearer (ISB main, ISB main backup, ISB standby, or ISB standby backup port) the alarm takes a different meaning.

ADS Alarms

331

This alarm would typically be mapped to the information output alarm for all ISB controller ports, so at a glance a user can tell if any port at this ADS is actively controlling. Likewise, backup or standby controller ports can also map this alarm to the major output alarm notifying users of the critical condition that their 1:1 redundancy has been called upon and they may no longer be resilient to further failures.

Card Configuration

Purpose

This alarm shall indicate when the installed cards do not match what the ADS system was expecting. This could be that a new card has been installed, or an existing card has failed.

Alarm IDs

Alarm Number

Alarm Name

Comment

31 Configuration

Description

When IMS does an Update to NVRAM the current list of installed cards is saved. The DCU will then use this saved list and the list of cards present to decide if the Configuration alarm is to be active. If extra cards are found in the rack, or if the saved configuration indicates a card is missing, then the configuration alarm shall be activated.

DS3 Loss of Signal

Purpose

This alarm shall indicate when a DS3 link is not connected or has failed. A DCU card has two DS3 links.

Alarm IDs

Alarm Number

Alarm Name

Comment

32 Link A LOS Loss of Signal for DCU Link A

33 Link B LOS Loss of Signal for DCU Link B

Appendix A: Alarms

332 025-9619A

Description

Loss of Signal from a DS3 Link is detected by the PM4328 IC. (Bit 0 of register 0x100F). Whenever a change in state occurs an interrupt is generated and the new state is passed to the alarm handler.

DS3 Loss of Frame

Purpose

This alarm shall indicate when a DS3 link is connected but cannot detect the DS3 frame. This can be due to AIS being received, errors on the DS3 link, or insufficient signal level. A DCU card has two DS3 links.

Alarm IDs

Alarm Number

Alarm Name

Comment

34 Link A LOF Loss of Frame for DCU Link A

35 Link B LOF Loss of Frame for DCU Link B

Description

Loss of Frame from a DS3 Link is detected by the PM4328 IC. (Bit 1 of register 0x100F). Whenever a change in state occurs an interrupt is generated and the new state is passed to the alarm handler.

DS3 Alarm Indication Signal

Purpose

This alarm shall indicate when a DS3 link is connected but has detected all ones on the link. A DCU card has two DS3 links.

Alarm IDs

Alarm Number

Alarm Name

Comment

36 Link A AIS Alarm Indication Signal for DCU Link A

37 Link B AIS Alarm Indication Signal for DCU Link B

ADS Alarms

333

Description

Alarm Indication Signal from a DS3 Link is detected by the PM4328 IC. (Bit 2 of register 0x100F). Whenever a change in state occurs an interrupt is generated and the new state is passed to the alarm handler.

DS3 Link Failure

Purpose

This alarm shall indicate when a DS3 link is unable to be used to pass audio/data around the ADS ring.

Alarm IDs

Alarm Number

Alarm Name

Comment

38 Link A Failed Link A not usable

39 Link B Failed Link B not usable

Description

The Link Failed alarm is made active whenever the DCU discovers that it cannot use the link to talk to the adjacent racks. This alarm shall be set when any of the following conditions are present:

• DS3 Loss Of Signal

• DS3 Loss Of Frame

• DS3 Alarm Indication Signal

• Failure of C-Bit messaging to talk to adjacent rack

• Lockup of adjacent rack

DS3 Link Wrapped

Purpose

This alarm shall indicate when a DS3 link has been placed into the wrapped mode. Wrapped mode is used to cause all data and audio to go around the ring in the opposite direction and hence skip the broken link.

Appendix A: Alarms

334 025-9619A

Alarm IDs

Alarm Number

Alarm Name

Comment

40 Link A Wrapped Link A is wrapped

41 Link B Wrapped Link B is wrapped

Description

The Link Wrapped alarm is made active whenever the DCU discovers that it cannot use the link to talk to or pass audio to an adjacent rack. This alarm shall be set when any of the following conditions are present:

• DS3 Loss Of Signal

• DS3 Loss Of Frame

• DS3 Alarm Indication Signal

• Failure of C-Bit messaging to talk to adjacent rack

• Lockup of adjacent rack

• Failure of Link startup negotiations

• Forced wrap by the IMS maintenance terminal

DCU Ring Off-Line

Purpose

This alarm shall indicate when both sides of the DS3 link have failed and hence this DCU card has been isolated.

Alarm IDs

Alarm Number

Alarm Name

Comment

42 Ring Offline

Description

The Ring Off Line alarm is made active whenever the DCU discovers that it cannot use either DS3 links. This implies that both DS3 Link A Wrapped and DS3 Link B Wrapped shall be active. The alarm is cleared when either of the wraps is removed.

ADS Alarms

335

Incorrect DS3 Port Connection

Purpose

This alarm shall indicate if a DCU has been connected to the incorrect port on an adjacent DCU. An incorrect connection is defined as connecting Port A to Port A or Port B to Port B.

Alarm IDs

Alarm Number

Alarm Name

Comment

43 Incorrect Port Connection

Description

When the DCU communicates with an adjacent DCU they shall exchange information about the DS3 port being used. If the DS3 ports are different (i.e. Port A connected to Port B) then the alarm is cleared. If the DS3 ports are the same then the alarm is set.

DCU NV Configuration

Purpose

This alarm shall indicate if the saved configuration is valid.

Alarm IDs

Alarm Number

Alarm Name

Comment

44 NV Configuration

Description

When the loads its configuration from NVRAM it shall generate a checksum for the data read and compare it to the expected value. If the values do not match the NV Configuration alarm is set and the saved configuration is not restored. The NV Configuration alarm shall only be cleared once a valid saved configuration is loaded.

Appendix A: Alarms

336 025-9619A

No Backplane Time Slots Available

Purpose

This alarm shall indicate if an audio connected failed due to there not being any free time slots on the ADS rack backplane bus.

Alarm IDs

Alarm Number

Alarm Name

Comment

45 No Backplane Time Slots

Description

When an audio channel is required to be passed on an E1 link to an ALS or ACU then the DCU card must connect the required channel on the DS3 ring to the backplane bus. If the backplane bus is fully used the No Backplane Time Slots alarm shall be activated. This alarm shall remain active until a new connection is required and a free time slot on the backplane is found.

DCU Packet Memory Exhausted

Purpose

This alarm shall indicate when the DCU was unable to send a message due to there being no memory available to store the message to be sent. This is a serious alarm since it indicates that a message has failed and hence the system can enter an unknown state. (i.e. message to turn PTT off might be lost and hence some radio resources might be left keyed up)

Alarm IDs

Alarm Number

Alarm Name

Comment

46 Packet Memory Exhausted

ADS Alarms

337

Description

When the DCU attempts to send a message on the Ring it must allocate a temporary storage for the message. If the temporary storage cannot be allocated then the Packet Memory Exhausted alarm is set. This alarm shall only be cleared once the IMS terminal is used to ACK the alarm.

DCU Packet Memory Insufficient

Purpose

Reserved for future use

Alarm IDs

Alarm Number

Alarm Name

Comment

47 Packet Memory Insufficient

Description

This alarm is unused.

MCU Packet Memory Exhausted

Alarm IDs

Alarm Number

Alarm Name

Comment

48 MCU A Packet Memory Exhausted

MCU Slot 1

72 MCU B Packet Memory Exhausted

MCU Slot 2

96 MCU C Packet Memory Exhausted

MCU Slot 3

Appendix A: Alarms

338 025-9619A

MCU E1 Loss of Signal

Purpose

Alarm is used to indicate if an E1 link on an MCU card is receiving a signal or not.

Alarm IDs

Alarm Number

Alarm Name

Comment

49 MCU A Link 1 LOS MCU Slot 1, Link 1

58 MCU A Link 2 LOS MCU Slot 1, Link 2

72 MCU B Link 1 LOS MCU Slot 2, Link 1

81 MCU B Link 2 LOS MCU Slot 2, Link 2

96 MCU C Link 1 LOS MCU Slot 3, Link 1

105 MCU C Link 2 LOS MCU Slot 3, Link 2

Description

The E1 Loss of Signal shall be detected by the FALC54 or FALC55 IC bit 7 of register FRS0) on the MCU4 card and passed to the DCU card. (If LOS is detected the alarm shall be set

MCU E1 Loss of Framing

Purpose

Alarm is used to indicate if an E1 link on an MCU card is receiving a signal but cannot detect or sync to the E1 framing.

Alarm IDs

Alarm Number

Alarm Name

Comment

50 MCU A Link 1 LOF MCU Slot 1, Link 1

59 MCU A Link 2 LOF MCU Slot 1, Link 2

73 MCU B Link 1 LOF MCU Slot 2, Link 1

82 MCU B Link 2 LOF MCU Slot 2, Link 2

ADS Alarms

339

Alarm Number

Alarm Name

Comment

97 MCU C Link 1 LOF MCU Slot 3, Link 1

106 MCU C Link 2 LOF MCU Slot 3, Link 2

Description

The E1 Loss of Frame shall be detected by the FALC54 or FALC55 IC (bit 5 of register FRS0) on the MCU4 card and passed to the DCU card. If LOF is detected the alarm shall be set.

MCU E1 Alarm Indication Signal

Purpose

Alarm is used to indicate if an E1 link on an MCU card is receiving an alarm indication signal.

Alarm IDs

Alarm Number

Alarm Name

Comment

51 MCU A Link 1 AIS MCU Slot 1, Link 1

60 MCU A Link 2 AIS MCU Slot 1, Link 2

74 MCU B Link 1 AIS MCU Slot 2, Link 1

83 MCU B Link 2 AIS MCU Slot 2, Link 2

98 MCU C Link 1 AIS MCU Slot 3, Link 1

107 MCU C Link 2 AIS MCU Slot 3, Link 2

Description

The E1 Alarm Indication Signal (AIS) shall be detected by the FALC54 or FALC55 IC (bit 6 of register FRS0) on the MCU4 card and passed to the DCU card. If AIS is detected the alarm shall be set.

Appendix A: Alarms

340 025-9619A

MCU E1 Remote Alarm

Purpose

Alarm is used to indicate if an E1 link is receiving a Remote Alarm indication from the far end.

Alarm IDs

Alarm Number

Alarm Name

Comment

52 MCU A Link 1 RA MCU Slot 1, Link 1

61 MCU A Link 2 RA MCU Slot 1, Link 2

75 MCU B Link 1 RA MCU Slot 2, Link 1

84 MCU B Link 2 RA MCU Slot 2, Link 2

99 MCU C Link 1 RA MCU Slot 3, Link 1

108 MCU C Link 2 RA MCU Slot 3, Link 2

Description

The E1 Remote Alarm shall be detected by the FALC54 or FALC55 IC (bit 4 of register FRS0) on the MCU4 card and passed to the DCU card. If RA is detected the alarm shall be set.

MCU E1 Remote Alarm 1

Purpose

Alarm is used to indicate if the CCS signaling on an E1 link is receiving a Remote Alarm 1.

Remote Alarm 1 is defined as bit 2 of the CCS stream for time slot 16.

ADS Alarms

341

Alarm IDs

Alarm Number

Alarm Name

Comment

53 MCU A Link 1 RA1 MCU Slot 1, Link 1


76 MCU B Link 1 RA1 MCU Slot 2, Link 1


100 MCU C Link 1 RA1 MCU Slot 3, Link 1


Description

The E1 Remote Alarm 1 shall be detected by the DCU card. When the ALS or ACU activates its Remote Alarm 1 output a CCS message for time slot 16 is sent. This is passed by the MCU4 card to the DCU card. The DCU card shall then check if the CCS message was for time slot 16 and if so shall test bit 2. If bit 2 is a 0 the alarm shall be made active.

MCU E1 Remote Alarm 2

Purpose

Alarm is used to indicate if the CCS signaling on an E1 link is receiving a Remote Alarm 2.

Remote Alarm 3 is defined as bit 2 of the CCS stream for time slot 16.

Alarm IDs

Alarm Number

Alarm Name

Comment







Appendix A: Alarms

342 025-9619A

Description

The E1 Remote Alarm 2 shall be detected by the DCU card. When the ALS or ACU activates its Remote Alarm 2 output a CCS message for time slot 16 is sent. This is passed by the MCU4 card to the DCU card. The DCU card shall then check if the CCS message was for time slot 16 and if so shall test bit 3. If bit 3 is a 0 the alarm shall be made active.

MCU LCB Missing

Purpose

Alarm is used to indicate if an Link Control Block had been created (by either the ALS or ACU sending the required create message) and is then destroyed (due to failure or the ALS/ACU, etc.).

This Alarm is used mainly to indicate that some external device was present but is now missing. This alarm can be activated by the user changing the system configuration (e.g. moving an ACU loop to a different MCU).

Alarm IDs

Alarm Number

Alarm Name

Comment

55 MCU A Link 1 LCB MCU Slot 1, Link 1

64 MCU A Link 2 LCB MCU Slot 1, Link 2

78 MCU B Link 1 LCB MCU Slot 2, Link 1

87 MCU B Link 2 LCB MCU Slot 2, Link 2

102 MCU C Link 1 LCB MCU Slot 3, Link 1

111 MCU C Link 2 LCB MCU Slot 3, Link 2

Description

When an ALS or ACU communicates with the ADS and request an Operator Link Control Block or a Line Link Control Block is created the ADS shall record this creation request. If this Link Control Block is later destroyed (could be due to failure of the ALS/ACU, failure of the E1 link, or a configuration change) it shall activate the LCB Missing alarm. This alarm can only be cleared by a Link Control Block being created for the link or a reset of the system. When the system first powers up there shall be no LCB Missing alarms active.

ADS Alarms

343

MCU E1 Framer Slips

Purpose

Alarm is used to indicate if an E1 link on an MCU card is slipping (2Mb clock different between the internal source and the source on the other end of the E1 link).

Alarm IDs

Alarm Number

Alarm Name

Comment

56 MCU A Link 1 Slip MCU Slot 1, Link 1

65 MCU A Link 2 Slip MCU Slot 1, Link 2

79 MCU B Link 1 Slip MCU Slot 2, Link 1

88 MCU B Link 2 Slip MCU Slot 2, Link 2

103 MCU C Link 1 Slip MCU Slot 3, Link 1

112 MCU C Link 2 Slip MCU Slot 3, Link 2

Description

The E1 Slip shall be detected by the FALC54 or FALC55 IC (bit 3 of register FRS0) on the MCU4 card. When a slip is detected a 60-second timer shall be started. If a second slip is detected within this 60-second period then the Slip alarm is set and passed to the DCU card. The slip alarm shall only be cleared if there are no more slips within a 60-second window.

MCU LCB Backup

Purpose

Alarm is used to indicate if a Link Control Block is in the standby mode. This alarm shall only be active if a Link Control Block has been created.

Appendix A: Alarms

344 025-9619A

Alarm IDs

Alarm Number

Alarm Name

Comment

57 MCU A Link 1 Backup MCU Slot 1, Link 1

66 MCU A Link 2 Backup MCU Slot 1, Link 2

80 MCU B Link 1 Backup MCU Slot 2, Link 1

88 MCU B Link 2 Backup MCU Slot 2, Link 2

103 MCU C Link 1 Backup MCU Slot 3, Link 1

112 MCU C Link 2 Backup MCU Slot 3, Link 2

Description

An ALS must be connected and a Link Control Block must have been created for this E1 link. If the ALS is in the standby mode then the LCB Backup alarm shall be active. When the ALS becomes the master the LCB Backup alarm shall be cleared.

DCU Boot Error

Purpose

The DCU Boot Error is used to indicate if a fault occurred when the DCU started. This alarm cannot be cleared unless the DCU is reset.

Alarm IDs

Alarm Number

Alarm Name

Comment

120 DCU Boot Error

Description

When a DCU first boots it runs a boot loader. The boot loader shall verify the following items:

• RAM is OK

• Meta File Checksum is OK

• Meta File Version is valid

• Boot Loader Checksum is OK

• Valid application firmware present

ADS Alarms

345

• Application firmware can be uncompressed ok.

If any of the above checks fails then the failsafe code shall be loaded and the reason recorded. The failsafe code shall then generate the DCU Boot Error alarm. This alarm can only be cleared by fixing the boot problem and rebooting the DCU card.

2Mb Clock Source Error

Purpose

The 2Mb Clock Source Error shall be set if IMS had defined one or more 2Mb clock source and had triggered the clock source to cause an alarm.

Alarm IDs

Alarm Number

Alarm Name

Comment

121 2Mb Clock Source

Description

IMS is used to define what 2Mb clock sources the DCU card is to use. Each of these clock sources can be specified to trigger an alarm when they become the active source. When the DCU checks for a valid 2Mb clock to use it shall scan the provided list and select the first active clock source. If this clock source is defined as triggering an alarm then the 2Mb Clock Source alarm is set.

DCU Selftest Failure

Purpose

The Selftest Failure alarm shall be set if any of the tests done during a self-test fails.

Alarm IDs

Alarm Number

Alarm Name

Comment

122 Self Test

Appendix A: Alarms

346 025-9619A

Description

A DCU self-test is done at power up and can be done via IMS. The failure of any of the self-test shall result in the Selftest Failure alarm being set. Once this alarm is set it cannot be cleared except via a power cycle.

Input Alarm Handling

Alarm Storing

The alarms specified in section Input Alarm Description above are stored in an alarm log in RAM storing 123 alarms. The alarm log is lost at restart of the DCU (reset or power up). The change of state of an input alarm shall also be stored in the DCU Fault Log. The Fault Log is stored in NVRAM and hence shall not be lost when the DCU is restarted. The Alarm Fault Log entry shall include the time the alarm changed states and what the new state is.

Alarm Outputs

General

Each input alarm can be sent to one, many or all alarm outputs. One, many or all input alarms can be sent to the same alarm output. The required configuration is entered via IMS.

Alarm Outputs

The following table contains a list of the alarm outputs.

Output Alarm Name

Alarm Output

No.

Purpose

Urgent Alarm LED 0 This is a RED Led on the MSU. It is used to indicate a condition exists that requires immediate action.

Non Urgent Alarm LED 1 This is a YELLOW Led on the MSU. It is used to indicate a possible fault exists that might require action.

Information Alarm LED 2 This is a GREEN Led to indicate that there might be a fault. No action is required.

Digital Output 1 3 Optical Isolated digital output


ADS Alarms

347

Output Alarm Name

Alarm Output

No.

Purpose







MCU A Link 1 System Select 11 Alarm reserved for MCU Slot 1 Link 1

MCU A Link 2 System Select 12 Alarm reserved for MCU Slot 1 Link 2

MCU B Link 1 System Select 13 Alarm reserved for MCU Slot 2 Link 1

MCU B Link 2 System Select 14 Alarm reserved for MCU Slot 2 Link 2

MCU C Link 1 System Select 15 Alarm reserved for MCU Slot 3 Link 1

MCU C Link 2 System Select 16 Alarm reserved for MCU Slot 3 Link 2

Output Alarm Operating Modes

An output alarm can be set to be in one of three operating modes:

• Passive Mode In passive mode the alarm output becomes active when an alarm input becomes active and is de-activated only when it is acknowledged from IMS. This is the default operating mode for alarm outputs.

• Locked Mode In locked mode the alarm output becomes active when an alarm input becomes active. It can only be de-activated when acknowledged from IMS. The alarm input becoming de-activated does not put the alarm output into the idle state. (In this mode a brief failure, such a temporary link failure is latched until the alarm is acknowledged.)

• Pulsed Mode In pulsed mode the alarm output will become active when an alarm input becomes active. The output will stay active for a set time and then become de-activated. The active pulse time is set from IMS and is common for all pulsed outputs.

Before the output can become active again the alarm input has to be de-activated or the alarm acknowledged.

Appendix A: Alarms

348 025-9619A

ALS Alarms

Configuration Error

ALARM No. 0 CE

On power up the MCU3 checks to see if all the line cards and smart cards (those that use the HDLC backplane bus) are present and configured according to the setup stored in the configuration Flash RAM. If any change is detected, then the “Configuration Error” alarm is made active. The alarm is only cleared if the configuration is updated (using IMS), or the subrack configuration is changed to match the configuration saved in Flash RAM. During normal operation, the MCU3 checks that all cards are present at least once every minute. The MCU3 will also check the status of the smart cards. The CE alarm will be raised if the card reports a failure of some kind. The CE alarm will also be raised if the MCU3 does not detect the cards normal heartbeat message. The alarm log stores which card caused the alarm.

Note The check of the CODECs does not indicate if the analog portion

of the CODEC circuit is operating, only that the MCU3 can communicate with the CODEC.


The installed cards do not match the programmed configuration. One is missing or an unexpected card was found. Communications may have been lost with the card.

Look for a slot with a red or yellow indicator as the problem slot.

Check the fault log for fault details.

To clear a Configuration alarm the faulty/missing cards can be replaced or the current subrack configuration can be updated to Flash RAM using IMS.

Loss of Signal at 64k G703 Interface

ALARM No. 1 64K NOS

DIU3 card alarm.

Alarm No. 1 is an application for the DIU3. If any of the DIU3 channels lose receive signal, then the loss of signal alarm will be raised. The alarm will only be automatically cleared when a signal is detected again or that channel is disabled by IMS.

The alarm log stores which one of the 60 possible DIU3 channels raised the alarm. This information is available through IMS.

ALS Alarms

349

This alarm is part of the G.735 and G.737 requirements.

Slips at 64k G703 Interface

ALARM No. 2 64K SLIP

DIU3 card alarm.

This alarm is raised if there is one slip (elastic buffer empty or overfilled) in 60 minutes or less (exact time set in IMS). It is cleared by disabling the channel, or correcting the cause of the synchronization fault. This alarm condition needs to be averaged over a long time to avoid setting it to detecting one slip, which might only be occurring at a rate of once every one hundred days. This alarm should not be activated when there are alarms like NOS and LOS active for the same link. It is automatically cleared only after a slip free period (60 minutes). The averaging time is programmable from IMS.

The alarm log stores which one of the 60 possible DIU3 channels raised the alarm. This information is available through IMS.

AIS from Remote End of 64k G703 Interface

ALARM No. 3 64K AIS

DIU3 card alarm.

If the DIU3 receives a remote AIS (all 1s) on a channel then this alarm is raised. This alarm is cleared by either the removal of the AIS signal from the remote end (64K port) or by disabling the channel through IMS.

The alarm log stores which of the 60 possible DIU3 channels raised the alarm. This information is available through IMS.

Loss of Incoming Signal at 2 MBPS Interface

ALARM No. 4 and 5 2M NOS P and 2M NOS S

NOS stands for NO Signal. If any 2 Mbps-bit receive signal falls below a level of approximately 1-volt, then this alarm is raised. This corresponds to a loss of 6 dB. In a system that has more than two MCU3s, alarm 4 corresponds to the 2 Mbps link of the primary MCU3 in slot 0, and alarm 5 corresponds to an “OR” function of all the other 2 Mbps interfaces. When an MCU3-DUAL is installed in slot 0, and both of the 2 Mbps channels are in operation, Alarm 4 is for the first 2 Mbps link of the MCU3 in slot 0. Alarm 5 is an “OR” function of all the other 2 Mbps channels in the system (this includes the second 2 Mbps link on the MCU3 in slot 0).

Appendix A: Alarms

350 025-9619A

This alarm is cleared by either disabling the MCU3, replacing the MCU3, or restoring the signal. It is automatically cleared only when the 2 Mbps signal is fully restored.

The operation of this alarm is controlled directly by the framer IC on the MCU3. The framer raises the NOS alarm if the following conditions are detected:

• Three or less ones are received in a time internal of 250 micro-seconds,

or

• The receive clock pulse fails to occur in a time interval of 4 internal clock cycles (4096 kHz).

The alarm log will store alarm 4 and which of the 6 remote ends raised alarm 5. This information is available through IMS. This alarm is part of the G.732 requirement.


The MCU does not detect an E1/T1 signal from the connected device on the alarming port.

Check E1/T1 connections between the MCU and connected equipment using the system map.

This alarm is cleared by either disabling the MCU3 framer, replacing the MCU3, or restoration of the signal. It is automatically cleared only when the 2Mbps signal is fully restored.

The E1/T1 signal is not strong enough. The inbound E1/T1 signal may not be strong enough to drive the circuit input. No more than 6dBm @ 1000Hz may be allowed.

Use E1/T1 test set to check inbound signal strength.

Swap Tx/Rx pairs on both ends and see if the problem follows the cable.

Check/replace connectors on Rx cable.

Loss of Frame Alignment of the G.703 2 MPBS Link

ALARM No. 6 and 7 2M LOS P and 2M LOS S

Alarm 6 is for link 1 (2 Mbit) of the primary MCU3. Alarm 7 is for the remaining 2 Mbps links. Loss of frame alignment is in reality a loss of synchronization or frame synchronization (LOS = Loss of synchronization).

The LOS alarm is asserted when the Framer chip detects three consecutive incorrect Frame Alignment Signal (FAS) words. After loss of synchronization, the Framer chip will resynchronize automatically if the following conditions are met:

• The presence of the correct FAS word in frame n

• The presence of the correct service word in frame n + 1

• For a second time the presence of a correct FAS word in frame n + 2

ALS Alarms

351

After this, the sequence synchronization is regained and the LOS alarm is cleared.

When CRC multiframe structure is enabled (using IMS), the CRC multiframe alignment (as opposed to frame alignment outlined above) is assumed to be lost if pulse frame synchronization has been lost. In this state the LOS alarm is asserted.

CRC multiframe alignment is regained after two consecutive CRC multiframes have been received without a framing error. At this point the LOS alarm is cleared.

The alarm log stores alarm 6 and which of the 6 remote ends raised alarm 7. This information is available through IMS.

This alarm is part of the G.732 requirement.


No signal from the E1/T1 port. LOS would be accompanied by a NOS alarm.

See NOS alarm.

Noise or poor signal strength has made the frame alignment difficult or impossible to detect.

Check E1/T1 connections between the MCU and connected equipment using the system map.

The quality of the inbound link may be questionable, isolate circuits and troubleshoot.

Use E1/T1 tester to measure signal strength.

Check and replace connectors on cable.

Received Remote Alarm

ALARM No. 8 and 9 2Mbps RRA P and 2Mbps RRA S

The 2 M RRA alarm is raised when the Framer chip receives a RRA (Receive Remote Alarm, all “1s”) from the device connected to the remote end of the G.703 link.

Alarm 8 is the RRA for the first 2 Mbps link of MCU3 in slot 0. Alarm 9 is the RRA for the remaining MCU3 2 Mbps links.

The alarm log stores alarm 8 and which of the six remote ends raised alarm 9. This information is available through IMS.



The connected device is reporting a remote alarm (all “1s”) on the E1 link.

Follow the circuit to the alarming device looking for an open E1 and/or an RRA output alarm on the connected device.

Appendix A: Alarms

352 025-9619A

Excessive EBER G703 2 MBPS for Channels 1 and 2

ALARM No. 10 and 11 2Mbps EBER P and 2Mbps EBER S

Alarm 10 is for link 1 of the primary MCU3 and alarm 11 is for remaining G.703 links. The EBER alarm will be raised if the received G.703 data has an error rate greater than 10-3.

The alarm log stores which of the six remote ends raised alarm 11. This information is available through IMS.



No signal from the E1/T1 port (loss of signal is accompanied by a NOS alarm).

See NOS alarm.

High loss on the E1 circuit. Check E1/T1 connections between the MCU and connected equipment using the system map.




Slips Occurring on 2 MBPS Link

ALARM No. 12 and 13 2Mbps SLIP P and 2Mbps SLIP S

Alarm 12 is for link 1 of the primary MCU3 and alarm 13 is for the remaining G.703 links.

This alarm is raised for each slip except the first slip after restart. It is cleared by disabling the channel, or replacing the card (at either end). It is cleared automatically only after a slip free period of 60 minutes or less (programmable in IMS).


ALS Alarms

353


Clocking sources for E1/T1 devices are not in sync causing intermittent slips.

Allow the Acom device to accept clocking from the E1/T1 link using IMS.

1. From the IMS menu select Configure->System Clocking.

2. Add all of the Available Clocking Sources to the list of clocking sources.

3. Repeat for the other Acom devices.

2 MPPS Multi-frame Sync Loss

Alarm no. 14 and 15 2Mbps MFA P and 2Mbps MFA S

Alarm 14 is for link 1 of the primary MCU3 and alarm 15 is for remaining G.703 links.

Multiframe synchronization is lost when the Framer chip does not detect the multiframe sync bit. If this occurs, the MFA alarms are raised. The MFA alarms are cleared when the first correct multiframe alignment signal is detected.


Connected device is not using TS16 for the same purpose as the alarming device.

TS16 can be used as a data channel, CAS signaling bits, or as a clear voice channel. The expected signaling was not detected on TS16, check E1/T1 configuration on both ends.

1. From the IMS menu right-click on the MCU card and select Link Signaling->Link1 or Link2.

2. Choose an LCB Signaling Scheme if the port is connected to a DS3 Switch E1 port or choose CAS if operating the subrack as an MX-3.

2 MBPS-CRC-4 Error

ALARM No. 16 and 17 2Mbps CRC P and 2Mbps CRC S

Alarm 16 is for link 1 of the primary MCU3 and alarm 17 is for the remaining G.703 links.

This alarm is raised when a CRC error is reported by the Framer chip and cleared when it has received 2 correct CRC multiframes.

The alarm log stores alarm 16 and which of the 6 remote ends raised alarm 17. This information is viewed through IMS.

Appendix A: Alarms

354 025-9619A



TS16 can be used as a data channel, CAS signaling bits, or as a clear voice channel. The expected signaling was not detected on TS16, check E1/T1 configuration on both ends.

Noise or poor signal strength. Check E1/T1 connections between the MCU and connected equipment using the system map.




AIS Detection at 2 MBPS Input

ALARM No. 18 and 19 2Mbps AIS P and 2Mbps AIS S

The alarm indication signal (AIS) is a continuous stream of ones. This alarm is raised when the incoming bit stream has less than two zeros in a time interval of 250 us (that is, two G.704 frames).



The remote device is running a test. Stop test.

Remote Multiframe Alarm on 2 MPBS Input

ALARM No. 20 and 21 2Mbps MRRA P and 2Mbps MRRA S

MRRA alarm is raised when the Framer detects a Multiframe Receive Remote Alarm. The Acom system is capable of both sending and receiving this alarm.

The MRRA bit is set on a transmitted multiframe under the following conditions:

• Loss of incoming 2 Mbps signal

• Loss of multiframe align signal on incoming 2 Mbps link (alarm 6 and 7)


ALS Alarms

355


Remote device has detected loss of incoming 2Mbps signal.

Follow MRRA and RRA alarms to the source.

Remote device has detected loss of multiframe alignment signal.

Follow MRRA and RRA alarms to the source.

Acom Fault During Restart or Self-test

ALARM No. 22 Acom Self Test Failure

Alarm 22 is raised when a fault is detected during a restart or self-test.


Bad MCU. Repeat self-test, replace MCU if you receive a second failed self-test.

Ring Fail Alarm

ALARM No. 23 RFA

The RGU sets a signal on the subrack backplane. This signal is checked by the MCU3. When the signal stops the RGU has failed and MCU3 raises this alarm.


One of the ringers has been removed. Check the IMS configuration on the number of expected ringers (see “Configuring ALS Parameters” in Acom Software Configuration, P/N 025-9529).

One of the ringers has failed. Replace the faulty RGU card or external ring source.

Alarms Acknowledged

ALARM No. 24 ACK

This alarm is raised when any alarm is acknowledged but not yet cleared.


The system is automatically ACKing alarms. Remove all input alarms from the “ACK All” output alarm definition in IMS (see “Define Alarms” in Acom Software Configuration, P/N 025-9529).

A technician has pressed the ACK All button on the Input Alarms panel and acknowledged all alarms.

Technicians should not press ACK All button on the Input Alarms panel.

Appendix A: Alarms

356 025-9619A

No Alarms

ALARM No. 25 OK

When no alarms are active (excluding the OK alarm), the OK alarm is raised. This alarm can be considered an “ALL OK” alarm.


The normally active Watchdog alarm from the standby subrack has been lost.

The standby ALS may be dead. Check its input and output alarms in IMS.

The system is operating in a non-redundant mode. This is normal for a non-redundant ALS.

Local Input Alarms

ALARM No. 27 to 32 LIN1 to LIN6

These alarms are received through the local MSU alarm input ports.

LIN1 and LIN2 are the defaults used as SI1 and SI2 inputs for the audio channel on the MSU board. These inputs can be programmed as alarm inputs through IMS (see “Define Alarms” in Acom Software Configuration, P/N 025-9529).

System Selected MSU, Input 1 (AI11)

The SYSSEL output (AO11) is grounded by the MSU card to signal the CCC card that it wishes to take control of the lines in the Changeover subrack. Input AI11 is then activated by the Changeover Control Card (CCC) to signal the MSU that it is in control.

AI11 is used as an E1 lead if the MSU audio channel is enabled.


The local subrack is in control. None required.

Standby Fault MSU, Input 2 (AI21)

This is the health alarm of the standby subrack. This input is expected to be normally inactive and if it becomes active a fault in the standby rack is assumed. Like the Watchdog alarm it provides communication between main and standby MSU cards. It is common to duplicate the same type of alarm mapping to the Standby Fault alarm as the Urgent Alarm Output in order to switch control if an Urgent alarm was to occur.

AI11 is used as an E2 lead if the MSU audio channel is enabled.

ALS Alarms

357


The redundant standby subrack has a problem. Use IMS to view the input/output alarms of the standby subrack.

MSU Input 3 (AI12)

This MSU input alarm may be used for other purposes such as monitoring the power supply alarms.

MSU Input 4 (AI22)

This MSU input alarm may be used for other purposes such as monitoring the power supply alarms.

Watchdog, MSU Input 5 (AI13)

Note The Watchdog output (AO13) is in an active state under normal

operation. For this reason a redundant ALS will never have the “All OK” alarm active.

Should the Primary MCU card in the ALS go dead, or the MSU lose power, this output will go inactive to indicate it has failed. In addition to these two non-configurable triggers, additional alarm inputs can be mapped to this MSU output to trigger a changeover (see “Define Alarms” in Acom Software Configuration, P/N 025-9529). It is common to connect all operational alarms to the Standby Fault output and leave only the loss of power and failure of a primary MCU to trigger the watchdog. The Watchdog input (AI13) monitors the Watchdog output of the other subrack. If this input goes high (inactive) the MSU will demand control by asserting the SYSSEL Output (AO11).

MSU Input 6 (AI23)

The AI23 input is commonly used to detect a problem with the E1 link associated with the local subrack. The backbone switch (ADS) connected to the E1 ports of the Primary MCU card provides this signal. It provides a faster indication of a lost E1 than waiting for a LOS, NOS, or RRA signal on the E1 link and will result in a quicker changeover between subracks.

Appendix A: Alarms

358 025-9619A

Test Condition

ALARM No. 33 TEST

This alarm is raised when a loopback test is initiated from the maintenance terminal.


A loopback test is underway on an E1 link in this subrack.

Use IMS to remove the loopback test. (See “Loopback” in Acom Software Configuration, P/N 025-9529).

Maintenance Terminal Active

ALARM No. 34 MAINT

This alarm is raised when a maintenance terminal is opened on the ALS.


A local IMS connection is active with this subrack. Not a problem, this indicates there is a local RS232 IMS session active.

DIU4 Alarms

ALARM No. 35, 36, 37 DIU4 SLIPS, DIU4 NO CLOCK, DIU4 NO HDLC

These alarms are raised when the DIU4 board detects a slip, loss of clocking, or loss of HDLC (High-level Data Link Control) communication with the Primary MCU3.

ALARM No. 40 Console Alarm

Indicates a console from the local Operator Subrack (OSR) has lost serial communications with the console PC.


Console PC turned off. Check the power to the console PC and that it is turned on.

ACS application not running. Check that the ACS application is running and logged in. Acknowledge any popup messages it might display and check the status bar to verify communications with the Acom Console Unit.

Baud rate or serial settings wrong in DIU configuration.

Check the IMS and ACS configuration for the serial port and baud rate (see “Serial Port” in Acom Software Configuration, P/N 025-9529).

The physical RS422 port to the console PC is bad. Check DIU connection to console.

ALS Alarms

359

ALARM No. 41 Backup Alarm

Not used with Acom.

ALARM No. 42 Data Alarm

The Data Alarm is generated by the External Clock serial port. The ALS expects regular time updates from the external time source. If the Alarm Timeout in the External Clock programming of IMS expires, the Data Alarm will activate. If a time source has never been connected, this alarm will not activate.


The ALS is not receiving time updates. Check the serial connection to the ALS. It may be connected to an MCU port or a DIU card.

At the debug prompt, issue the command “Test 8 80” to show time updates. To get to the debug prompt: With a laptop, use cable 709-7345 and a terminal program to connect directly to the Primary MCU card’s serial port 1 (38400 baud, 8N1). Press ESC three times to get a login, and type in your password (default 8564888).

ALARM No. 43 Line Alarm

The Line Alarm is generated by the LIT card. If a line test fails the alarm is activated.

ALARM No. 44 Bearer Alarm

Not used with Acom.

ALARM No. 45 Remote Alarm

Not used with Acom.

ALARM No. 46 LCB Alarm

Not used with Acom.

If the ALS loses communications with the Acom DS3 Subrack (ADS), this alarm will activate.

Appendix A: Alarms

360 025-9619A


The E1 link to the ADS has been broken. Check for any associated RRA, NOS, or LOS alarms.

Check for a physical break in the link. Check the SMB connectors for slippage.

The ALS can no longer communicate with the ADS over time slot 16.

Check the Link Signaling Scheme in IMS (see Acom Software Configuration, P/N 025-9529). The Link Signaling Scheme should be set to LCB 1-4, the number refers to the physical port the ALS is connected to on the ADS.

ALARM No. 47 E1-T1 Converter RA (Pri)

When the Acom subrack is configured as an E1 to T1 protocol rate converter, this alarm indicates a problem on the primary side (local to the ADS).

ALARM No. 48 E1-T1 Converter RA (Sec)

When the Acom subrack is configured as an E1 to T1 protocol rate converter, this alarm indicates a problem on the secondary side (local to the remote console end).

ALARM No. 49 Excessive Clipping

Not used with Acom.

ALARM No. 56 SMU LAN Alarm

Not used with Acom.

Generated by the SMU on an OpenSky VoIP system.

ALARM No. 57 SMU Ping Alarm

Not used with Acom

Generated by the SMU on an OpenSky VoIP system.

SMU Alarm

ALARM No. 58 SMU

This alarm indicates a problem has developed with the SMU card.

ALS Alarms

361


DSP signal processing loop has too many modules enabled, exceeding the maximum number of DSP instruction cycles allowed.

Check the SMU programming. If using User Defined resource allocation, verify the number of resources does not exceed the CPU clock cycles or memory of the DSP. (See “SMU Card Options” in Acom Software Configuration, P/N 025-9529.)

From the SMU debug prompt, issue the command “SMU” and verify that the each DSP does not exceed 100% clock cycles. To get to the debug prompt: With a laptop, use cable 709-7345 and a terminal program to connect directly to the SMU card’s debug serial port (38400 baud, 8N1). Press ESC three times to get a login, and use password 8564888.

SMU host processor believes DSP is running at the wrong speed. (A corrupt EEPROM can cause this.)

Replace SMU.

EEPROM cannot be read. Replace SMU.

EEPROM read error (checksum bad). Replace SMU

Any of the three DSPs have a fault (watchdog, self-test).

Replace SMU.

DSP IDMA read/write failure. Replace SMU.

FPGA failed to load. Replace SMU.

2MBPS Clocking

Alarm No. 59 2M CLK

The current clocking source has been programmed to trigger a clocking alarm.


The current clocking source has been programmed to trigger a clocking alarm.

Check the ALS System Clocking programming. A checkbox next to an available clocking source will cause this alarm if the checked clock is used to drive the 2Mbit links of the ALS.

Remote End Alarms

ALARMS No. 50 to 63 RAIN101-262 (with exception of alarms 58 and 59)

Two alarms are available for each of the remote ends connected to the G.703 links. If these input alarms are to be used the remote end must be capable of sending these alarm signals.

Appendix A: Alarms

362 025-9619A

ALARM No. 60 and 62 MCU Slot 0 PX RA1


The connected backbone-switching device (ADS) is reporting a remote alarm because of a failed backbone link.

Check for a broken DS3 link on the connected backbone switch (ADS) port A.

ALARM No. 61 and 63 MCU Slot 0 PX RA2


The connected backbone-switching device (ADS) is reporting a remote alarm because of a failed backbone link.

Check for a broken DS3 link on the connected backbone switch (ADS) port B.

Input Alarm Handling

Alarm Storing

When a General Alarm is raised (see General Alarms on page 173), the time and type of alarm is stored in non-volatile memory on the MCU in the ALS. The memory has space for a total of 256 individual alarm events. The alarm memory also stores the time of the last restart.

Alarm Urgency

Alarm urgency defines how urgent a maintenance action is following an alarm. The level of alarm urgency is defined by the user to suit the level/type of maintenance the system is intended to receive. The following levels are common:

Table 15. Alarm Urgency

Urgency Maintenance Action

High Immediate action any time of the day

Medium Immediate action but only during normal work hours

Low Action during next scheduled visit

None Information only

The user can set any alarm output for any of the above alarm urgency levels. The alarms that require actions of a desired urgency are simply programmed to go to the port allocated for this level of urgency. This means that the alarm is assigned to an output to indicate a particular urgency rather than assigning an urgency level to an alarm. This output is then “labeled” the appropriate urgency level.

ALS Alarms

363

Alarm Acknowledgment

The acknowledgment can be initiated from IMS or when one or more of the input alarms become active. Which input alarms initiate an acknowledgment is defined in IMS (see “Alarm Menu” in Acom Software Configuration, P/N 025-9529).

Alarm Outputs

Table 16 contains a list of the alarm outputs. The default column shows the default programming for each output. You can change this configuration using IMS.

Table 16. Alarm Outputs

Output Alarm Name Default Output No.

Urgent Alarm LED URGENT ALARM 1

Non Urgent Alarm LED NON-URGENT ALARM 2

Information Alarm LED OK ALARM 3

MSU OP 1 (AO11) SO1 4

MSU OP 2 (AO21) SO2 5

MSU OP 3 (AO12) URGENT ALARM 6

MSU OP 4 (AO22) NON-URGENT ALARM 7

MSU OP 5 (AO13) SYS ALARM 8

MSU OP6 (AO23) OK ALARM 9

IMS Output Alarm NONE 10

MCU3 Slot 0 Port1 RRA RRA 11

MCU3 Slot 0 Port1 MRRA MRRA 12

MCU3 Slot 0 Port1 RA1 NONE 13


MCU3 Slot 1 RRA RRA 15

MCU3 Slot 1 MRRA MRRA 16

MCU3 Slot 1 RA1 NONE 17








Appendix A: Alarms

364 025-9619A

Output Alarm Name Default Output No.



MCU3 Slot 0 Port2 RRA RRA 27

MCU3 Slot 0 Port2 MRRA MRRA 28











Primary MCU3 LED B7 URGENT ALARM 39

ACK All LIN5 + RAIN01 40

Application Software Use — —

Alarm Output Defaults

This section defines the input alarm conditions that cause a default alarm to become active. See Table 15 for definition of input alarms.

Table 17. Alarm Output Defaults

Alarm Type Default Input Alarm

URGENT CE, 2M NOS P, 2M NOS S, 2M LOS P, 2M LOS S, 2M EBER P, 2M EBER S, 2M MFA P, 2M MFA S, 2M AIS P, 2M AIS S, ACOM, RFA, LIN3, LIN6

NON URGENT 64K NOS, 64K SLIP, 64K AIS, 2M SLIP P, 2M SLIP S 2M RRA P, 2M RRA S+ 2M MRRA P, 2M MRRA S, LIN4, TEST

OK OK

SYS WATCHDOG, URGENT

RRA CE, 2M NOS P, 2M LOS P, 2M EBER P, 2M NOS S +2M LOS S, 2M EBER S

MRRA 2M NOS P, 2M MFA P, 2M NOS S, 2M MFA S

ALS Alarms

365

Alarm Type Default Input Alarm

SO1, SO2 These MSU outputs are default set up as SO1 and SO2 outputs (SO = E+M Signal Output) associated with the audio channel on the MSU board. These outputs can be programmed as alarm outputs through IMS.

ACK ALL LIN5, RAIN101. This “output” is only used to initiate acknowledgment of all existing alarms. Although this is not an ordinary output, it can be programmed as any other output.

Alarm Outputs over the G.703 Link

The Acom system is capable of transmitting alarm signals over any of the G.703 links. This can be used to inform remote devices or other systems of any alarms that are currently active. The Acom system provides 4 alarm outputs over a single G.703 link according to the following:

• RRA Received Remote Alarm

• MRRA Multiframe Remote Received Alarm

• RA1 Remote Alarm 1 (multiframe error)

• RA2 Remote Alarm 2 (multiframe error)

These alarm names are used because they are part of the G.704 standard, however in the Acom system they become arbitrary, as any input alarm can be used to raise any of these output alarms. These output alarms are configured through IMS (see “Alarm Menu” in Acom Software Configuration, P/N 025-9529).

MSU Alarm Inputs/Outputs

Refer to the Acom Software Configuration manual P/N 025-9529.

Appendix A: Alarms

366 025-9619A

Acom Console Unit (ACU) Alarms

Configuration Error

ALARM No. 0


The installed modules do not match the programmed configuration. One is missing or an unexpected module was found. Communications may have been lost with the module. This alarm is usually accompanied by an active “C” LED on the back of the Acom Console Unit.

In IMS or on the Acom Console Unit itself, look for a red or yellow indicator as the problem slot.

Check the fault log for fault details. (See “Fault Log” in Acom Software Configuration, P/N 025-9529.)

To clear a Configuration alarm the faulty/missing cards can be replaced or the current Acom Console Unit configuration can be updated to Flash RAM using IMS.

Amux Alarm

ALARM No. 1

Raised when a fault is detected during a restart or self-test.


Bad Acom Console Unit. Reset the Acom Console Unit. Replace Acom Console Unit if you receive a 2nd alarm.

Acked Alarms

ALARM No. 2 ACK

This alarm is raised when any alarm is acknowledged but not yet cleared.


The system is automatically ACKing alarms Remove all input alarms from the “ACK All” output alarm definition in IMS. (See “Define Alarms” in Acom Software Configuration, P/N 025-9529).

A technician has ACKed alarms Technicians should not ACK active alarms.


367

All OK

ALARM No. 3

No alarms appear in the system. This is a good alarm to have.

Test Condition

ALARM No. 4 TEST

This alarm is raised when a loopback test is initiated from the maintenance terminal.


A loop back test is underway on an E1 link in this Acom Console Unit.

Use IMS to remove the loopback test. (See “Loopback” in Acom Software Configuration, P/N 025-9529).

Maintenance Terminal Active

ALARM No. 5 MT

The IMS maintenance terminal is connected to this Acom device.


A local IMS connection is active with this Acom Console Unit.

Not a problem, this indicates there is a local RS232 IMS session active.

Digital Input 1 (through 6)

ALARMS No. 6 through 11

Programmable input alarm using IMS. These inputs may be active when the local input is programmed as an “Acom Alarm” and the input is active. Not used with Acom.

Link A Offline

ALARM No. 12

The Acom Console Unit has lost communications with the Acom DS3 connected to E1 port 1. This alarm is accompanied by a red “A” LED on the back of the Acom Console Unit.

Appendix A: Alarms

368 025-9619A


An Acom Console Unit is not passing the data to the ADS.

Reset the Acom Console Units between this device and the ADS. Each Acom Console Unit is responsible for passing data from E1 port to E1 port.

Acom Console Units hooked up incorrectly. Check the connections between Acom Console Units and the ADS. Port 1 on an Acom Console Unit should connect with E1 port 2 on the next. There should not be any E1 port 1 links connected to an adjacent E1 port 1.

Broken E1 link. The E1 link that is serviced by the Dual E1 card port 1 does not have a data connection to an ADS on time slot 16. Check for breaks in the E1 down the line. Check for red LEDs on the Dual E1 cards of the Acom Console Units between the local and the ADS.

Link B Offline

ALARM No. 13

The Acom Console Unit has lost communications with the Acom DS3 connected to E1 port 2. This alarm is accompanied by a red “B” LED on the back of the Acom Console Unit.

Console Alarm

ALARM No. 14

This Acom Console Unit has lost previously established communications with the ACS.


Serial cable unplugged. Check RS-232 cable between ACS COM port and Acom Console Unit COM1 port.

PC turned off. Check the power to the console PC and that it is turned on.

ACS turned off. Check that the ACS application is running and logged in. Acknowledge any popup messages it might display and check the status bar to verify communications with the Acom Console Unit.

Baud rate or serial settings wrong in Acom Console Unit data port.

Check the Acom Console Unit programming for the console data port. The Acom Console Unit baud rate should match the AcomConsole.ini setting (see “[Digital Outputs]” in Acom Software Configuration, P/N 025-9529).


369

Console Audio Facilities Alarm

ALARM No. 21

Not used with Acom.

The Audio Facility Alarm is generated when the Acom Console Unit was in communications with an audio interface through the “Data” connector on the OAM and has since lost the heartbeat signal.


OAM “Data” cable unplugged from audio interface.

Check the data cable between the Acom Console Unit OAM “Data” port and the audio interface.

Audio interface turned off. Check the power to the audio interface and that it is turned on.

Resetting the Acom Console Unit will remove this alarm; it will no longer expect an audio interface.

E1 Slot 0 Link X No Signal

ALARM No. 33 and 44 NOS


The Acom Console Unit does not detect an E1 signal from the connected device on the alarming port.

Check E1 connections between the Acom Console Unit and connected equipment using the system map.

This alarm is cleared by either disabling the E1 framer, replacing the E1 daughter card, or restoration of the signal. It is automatically cleared only when the 2 Mbps signal is fully restored.

The E1 signal is not strong enough. The inbound E1 signal may not be strong enough to drive the circuit input. No more than 6 dBm @ 1000 Hz may be allowed.

Use an E1 test set to check inbound signal strength.

Swap Tx/Rx pairs on both ends and see if the problem follows the cable.

Check/replace connectors on Rx cable.

Appendix A: Alarms

370 025-9619A

E1 Slot 0 Link X Loss of Sync

ALARM No. 34 and 45 LOS


No Signal from the E1 port. LOS would be accompanied by a NOS alarm.

See NOS alarm.

Noise or poor signal strength has made the frame alignment difficult or impossible to detect.

Check E1 connections between the MCU and connected equipment using the system map.

The quality of the inbound link may be questionable; isolate circuits and troubleshoot.

Use an E1 tester to measure signal strength.


E1 Slot 0 Link X Receive Remote Alarm

ALARM No. 35 and 46 RRA


The connected device is reporting a remote alarm (all “1s”) on the E1 link.

Follow the circuit to the alarming device looking for an open E1 and/or an RRA output alarm on the connected device.

E1 Slot 0 Link X Exceeded Bit Error Rate

ALARM No. 36 and 47 EBER


No Signal from the E1 port. LOS would be accompanied by a NOS alarm.

See NOS alarm.

High loss on the E1 circuit. Check E1 connections between the Acom Console Unit and connected equipment using the system map.


Use E1 tester to measure signal strength.



371

E1 Slot 0 Link X Frame Slips

ALARM No. 37 and 48 SLIP

This alarm is raised for each slip except the first slip after restart. It is cleared by disabling the channel, or replacing the card (at either end). It is cleared automatically only after a slip free period of 60 minutes or less (programmable in IMS


Clocking sources for E1 devices are not in sync causing intermittent slips.

Allow the Acom device to accept clocking from the E1/T1 link using IMS.

1. From the IMS menu select Configure, System Clocking.

2. Add all of the Available Clocking Sources to the Clocking list.

Repeat these two steps for the other Acom devices on the E1 ring.

E1 Slot 0 Link X Loss of Multiframe Alignment

ALARM No. 38 and 49 MFA

Multiframe synchronization is lost when the framer chip does not detect the multiframe sync bit. If this occurs, the MFA alarms are raised. The MFA alarms are cleared when the first correct multiframe alignment signal is detected.



TS16 can be used as a data channel, CAS signaling bits, or as a clear voice channel. The expected signaling was not detected on TS16; check E1 configuration on both ends (see “Dual E1 Module” in Acom Software Configuration, P/N 025-9529).

E1 Slot 0 Link X

ALARM No. 39 and 50 CRC4

This alarm is raised when a CRC error is reported by the framer chip and cleared when it has received two correct CRC multiframes.

Appendix A: Alarms

372 025-9619A



TS16 can be used as a data channel, CAS signaling bits, or as a clear voice channel. The expected signaling was not detected on TS16, check E1 configuration on both ends.

Noise or poor signal strength. Check E1 connections between the Acom Console Unit and connected equipment using the system map.


Use an E1 tester to measure signal strength.


E1 Slot 0 Link X Multiframe Remote Alarm

ALARM No. 40 and 51 MFR

The MFR alarm is raised when the Framer detects a Multiframe Receive Remote Alarm. The Acom Console Unit is capable of both sending and receiving this alarm. An E1 bit is set on the transmitted multiframe to signal a MFR.


Remote device has detected loss of incoming 2Mbps signal.

Follow MFA and RRA alarms to the source.

Remote device has detected loss of multiframe alignment signal.

Follow MFA and RRA alarms to the source.

E1 Slot 0 Link X RA1

ALARM No. 41 and 52


The connected DS3 is reporting a remote alarm because of a failed DS3 link.

Check for a broken DS3 link on the connected DS3 Switch port 1.

E1 Slot 0 Link X RA2

ALARM No. 42 and 53


The connected DS3 is reporting a remote alarm because of a failed DS3 link.

Check for a broken DS3 link on the connected DS3 Switch port 1.

Supervisor Alarms in IMS

373

Supervisor Alarms in IMS

Supervisor alarms are designed to alert a supervisor that there is a problem with the console system.

Supervisor Console Alarms

Output alarms will cause the on-screen ALARM button to flash red and an audible sound to be played to the supervisor. This functionality was designed to alert supervisors that there is an alarm condition within the system so that he/she may take appropriate action in a timely fashion. Note that some alarms are easily resolved by the supervisor without calling in the system maintenance technician. In order to see alarm indications at an operator console position you must use the login type “SUPERVISOR” and you must have the desired alarm strings defined in the “AcomConsole.ini” file. Alarm strings are defined in the “AcomConsole.ini” file under the [ALARMS] section. Note that if an alarm is not defined then it will not be displayed on the supervisor’s console. There are four types of alarms that can be defined and displayed at the supervisor position. These alarm types include NAME, ACU, CONSOLE, and DEVICE alarms (ACU is Acom Console Unit). These alarms are generated by various system components and are passed around the system via time slot 16 of the E1 console loops.

If the Alarm button exists on the Acom Console Software screen, the device alarms will be reported regardless if you are logged in as Supervisor or any other operator type.

Any position can be a Supervisor position using one of the two methods.

• AcomConsole.ini has Operator Types set with “,S” after the name.

Example: Type1=SUPERVISOR,3,3,S

• The Acom Console Unit supervisor checkbox is enabled in the Acom Console Unit settings in IMS. This means that this position will be a Supervisor Position regardless of the login type set in the AcomConsole.ini file.

Name Alarms

NAME alarms are generated by an ALS within a system whenever one of its Output Alarms goes active. NAME alarms are assigned a unique identifier number (0-115) within the ALS programming and can be viewed or configured via IMS (see “Alarm Menu” in Acom Software Configuration, P/N 025-9529). To define NAME alarms within your “AcomConsole.ini” file use the following format, (where: n = 0 – 115 from Table 18):

NAMEn=description

Appendix A: Alarms

374 025-9619A

Table 18. Name Alarm Cross-Reference

N Value ALS (IMS) Value Alarm Reference

0 0 Urgent Alarm LED

1 1 Non-Urgent Alarm LED

2 2 Information Alarm LED

3 3 Not used with Acom

4 4 Standby Fault

5 5 MSU Out3 (A012)

6 6 MSU Out4 (A022)

7 7 Standby Fault (watchdog)

8 8 MSU Out6 (A023)


10 10 MCU Slot 0 Port1 RRA

11 11 MCU Slot 0 Port1 MRRA

12 12 MCU Slot 0 Port1 RA1


14 14 MCU Slot 0 Port2 RRA

15 15 MCU Slot 0 Port2 MRRA



18-113 18-113 Not used with Acom

114 114 Primary MCU LED B7

115 115 ACK All

Acom Console Alarms (ACU) in IMS

ACU alarms are generated by an Acom Console Unit within a system whenever one of its Output Alarms goes active. ACU alarms are assigned a unique identifier number (1-96) within the Acom Console Unit programming and can be viewed/changed via IMS (see “Alarm Menu” in Acom Software Configuration, P/N 025-9529). To define ACU alarms within your “AcomConsole.ini” file use the following format (where: n = 0 – 96 based on Table 19):

ACUn=description


375

Note that the ACU alarms as viewed by IMS are zero based but the alarms seen by the supervisor console will be 1’s based. Therefore, to customize ACU alarm 0 your string would start with “ACU1= urgent alarm”.

Table 19. ACU Alarm Cross-Reference

N Value ACU (IMS) Value Alarm Reference

1 0 Urgent Alarm LED

2 1 Non-Urgent Alarm LED

3 2 Information Alarm LED

4 3 Digital Output 1







11 10 ACK All


29 28 E1 Slot0 Link1 RRA

30 29 E1 Slot0 Link1 MRRA

31 30 E1 Slot0 Link1 RR1


33 32 E1 Slot0 Link2 RRA

34 33 E1 Slot0 Link2 MRRA




Console Alarms

CONSOLE alarms are generated by an Acom Console Unit anytime the Acom Console Unit fails to receive responses to polling from its associated ACS. CONSOLE alarms are assigned a unique identifier number (1-128) which represents the number of the alarming console position (refer to Table 3). To define CONSOLE alarms within your “AcomConsole.ini” file use the following format (where: n = 0 – 128 based on Table 20):

CONSOLEn=description

Appendix A: Alarms

376 025-9619A

Table 20. Console Alarm Cross-Reference

N Value Alarm Reference

1 Console Position 1

.

.

.

.

.

.

128 Console Position 128

Device Alarms

DEVICE alarms are generated by the Acom Console Unit (ACU) whenever a device fails to respond to polling. DEVICE alarms are assigned a unique identifier number (1-255) which represents the network address of the alarming equipment. Acom Console Unit addresses are typically 1-99 and subracks are typically 100-255 (see Table 19). DEVICE alarms do not need to be defined unless you want to customize the text associated with the alarms. In other words, DEVICE alarms will always be displayed at the supervisor console position regardless of your alarm definitions within your “AcomConsole.ini” file. To define DEVICE alarms within your “AcomConsole.ini” file use the following format (where: n = 0 – 255 based on Table 19):

DEVICEn=description

Table 21. Device Alarm Cross-Reference

N Value Alarm Reference

1 ACU1

.

.

.

.

.

.

99 ACU99

100 ALS100

.

.

.

.

.

.

255 ALS255


377

Sample “AcomConsole.ini” file

Here is a sample [ALARMS] section of an “AcomConsole.ini” file. Note that in this particular example there are four specific console positions that are being monitored by this supervisor. The NAME and ACU alarms have been defined and will output a message to contact technical support. Note that the Urgent alarms tell the supervisor to call immediately and the non-urgent alarms specify normal business hours. The alarm strings also allow us to tell the supervisor which area of the system is experiencing problems (CCE room vs. console room). The CONSOLE and DEVICE alarms have been defined to give meaningful names to each console position. Note that a CONSOLE alarm alerts the supervisor that a console has been shut down and a DEVICE alarm indicates that a console is actually experiencing a failure.

[Alarms] ;NAME Alarms (ALS Generated Output Alarms) NAME0=Urgent Alarm Active in CCE Room- Call 24/7 Support Immediately NAME1=Non-Urgent Alarm Active in CCE Room - Call helpdesk during normal business hours ;OCU Alarms (ACU Generated Output Alarms) OCU1=Urgent Alarm Active in Console Room - Call 24/7 Support Immediately OCU2=Non-Urgent Alarm Active in Console Room - Call helpdesk during normal business hours ;CONSOLE Alarms (ACU Generated Output Alarms) CONSOLE1=MTCE Console has been shut down CONSOLE4=FlightDispatch Console #1 has been shut down CONSOLE5=FlightDispatch Console #2 has been shut down CONSOLE22=De-Ice Console has been shut down ;DEVICE Alarms (IMS Terminal Generated Output Alarms) DEVICE1=MTCE Console is out of service DEVICE4=FlightDispatch Console #1 is out of service DEVICE5=FlightDispatch Console #2 is out of service DEVICE100=Backroom Equipment Failure (ALS1A is out of service)

Appendix A: Alarms

378 025-9619A

Purpose

379

Appendix B: System Failure Worksheet

Purpose

To provide a worksheet to be filled out in case of an Acom system with a severe failure such as an inactive or unstable system. Capturing the state of the LEDs captures information required to help determine the cause of failure. Fill out each section applicable to the failure, and report your findings to Zetron. See http://www.zetron.com for contact information.

Note Make as many copies of these worksheet pages as needed to

capture the LED information from all ACUs, DCUs, MSUs, and MCUs in the system.

Worksheets are available for:

• DCU LEDs on page 380

• MCU3/4 LEDs (in ALS) on page 382

• MCU4 LEDs (in ADS) on page 384

• MSU LEDs on page 386

• Acom Console Unit (ACU) LEDs on page 388


380 025-9619A

DCU LEDs

Go to each Acom DCU in the system and record the name (example: DCU1) and the status of the LEDs on the front edge of the card. Record the LED status by filling in the LED indicators in the DCU front edge picture. Record any notes of color or flashing LEDs by checking the appropriate boxes. If you need to record more than seven DCU cards, make copies of the following pages as needed to record all DCU front edge LEDs.

Cycle MasterPort 2 DS3 Link StatePort 2 Wrap StateSpare

Name___________________________________________________________

A BCard Operational State

Port 1 DS3 Link StatePort 1 Wrap State

Status of ADS

DCU LEDs

381


382 025-9619A

MCU3/4 LEDs (in ALS)

Go to each MCU in the Acom Line Subracks and record the name (example: ALS1A, MCU slot 0) and the status of the LEDs on the MCU front edge. Record the LED status by filling in the LED indicators in the MCU front edge picture. If you need to record more than seven MCU cards, make copies of following page as needed to record all MCUs in the ALS Subracks.

MCU3/4 LEDs (in ALS)

383


384 025-9619A

MCU4 LEDs (in ADS)

Go to each MCU4 in the Acom DS3 Switches and record the name (example: ADS1A, MCU slot 2) and the status of the LEDs on the MCU4 front edge. Record the LED status by filling in the LED indicators in the MCU4 front edge picture. If you need to record more than seven MCU4 cards, make copies of following page as needed to record all MCU4 cards in the Acom DS3 Switches.

MCU4 LEDs (in ADS)

385


386 025-9619A

MSU LEDs

Go to each MSU in the system and record the name (example: ALS1A, MSU slot 12) and the status of the LEDs on the MSU front edge. Record the LED status by filling in the LED indicators in the MSU front edge picture. If you need to record more than 10 MSU cards, make copies of the following page as needed to record all MSUs in the system.

MSU LEDs

387


388 025-9619A

Acom Console Unit (ACU) LEDs

Go to each Acom Console Unit in the system and record the name (example: DS1) and the status of the LEDs on the Acom Console Unit rear panel. Record the LED status by filling in the LED indicators in the Acom Console Unit rear panel picture. Record any notes of color or flashing LEDs by checking the appropriate boxes. If you need to record more Acom Console Unit rear panels, make copies of the following page as needed to record all Acom Console Unit rear panel LEDs.

Note The following LED work sheets represent the rear view of an

Acom Console Unit. These diagrams are represented in a manner that is truncated and not to scale.


389


390 025-9619A


391

Index

2 2-wire interface, 307

4 4-wire leased lines, 42

A about this document, 13 ACD, 307 Acom system overview, 15 ACS, 307 ACS backup, 26 ACU, 307 ADS, 307 ADS changeover wiring example, 247 AFD, 307 AIS, 307 A-Law, 307 ALI, 307 ALS, 307 AMUX, 307 ANI, 307 answer next button

console screen changes, 208 file settings AcomConsole.ini, 209

audience, 13

B backbone switch signaling, 245 backbone time slots for local resources, 21 backplane, 307 bearer, 307 bearer time slots for intersite resources, 22

BER, 307 bit error rate, 307 branching connection, 308 broadcast connection, 308

C CAD, 308 call history panel

console screen changes, 206 editing AcomConsole.ini file, 207

call queue button console screen changes, 211 file settings AcomConsole.ini, 211

capacity, 22 CAS, 308 CCC, 308 CCC-E, 308 CCE, 308 CCU, 308 CDS, 308 changeover hardware, 242 changeover subrack, 244 channel associated signaling, 308 channel set funciton button, 179 CLI, 308 clipping, 308 clock signal, clock source, 308 clocking sources

daylight saving time, 236 external, 235 intersite considerations, 238

cloning an ALS, 252 CMOS, 308 CND, 308 COC, 308 CODEC, 308

Index

392 025-9619A

codirectional interface, 308 common control equipment (CCE), 19 companding, 309 configuring analog radio function and resource buttons, 179 connectors and pinouts, 18 console hardware, 16 console hardware requirements, 18 console phone line transfer button


console screen changes answer next button, 208 call queue button, 211 console phone line transfer button, 213 hold button, 216 hunt group dialpad, 220 ring enable/disable, 223 selected phone line dialpad, 226 speed dial function button, 229

COR, 309 COS, 309 COV-R, 309 COV-T, 309 COV-V, 309 CRC, 309 crosspoint switch, 309 CSR, 309 CTCSS, 309 CTS, 309 cyclic redundancy check, 309

D daylight saving time, 236 DCD, 309 DCE, 309 DCU, 309 decadic signaling, 309 device and system shutdown and restart, 241 device real-time clocks, 233 dial types database programming

MDC-1200 signaling, 150 DID, 309 differential data, 309 digital multiplex hierarchy, 310 DIU, 310 documentation, 14 DPLL, 310 DS3, 310 DS3 switches, 19

DSR, 310 DTE, 310 DTMF, 310 DTR, 310 dynamic allocation, 21

E E&M, 310 earth recall signal, 310 EBER, 310 edit console screen file

MDC-1200 signaling, 151 EIE, 310 electrical requirements, 18 EMC, 310 EMI, 310 EMU, 310 enable caller ID incoming

file settings AcomConsole.ini, 204 line resource programming, 203 SMU programming, 202

EnRoute signaling line button setup, 167 radio line programming, 165 SMU configuration, 163

EPIC, 310 ESD, 310 ETSI, 310 external clocking sources, 235

F FAS, 311 fault log

input alarms, 319 output alarms, 324

Field Programmable Gate Array, 311 file settings AcomConsole.ini

console phone line transfer button, 214 enable caller ID incoming, 204 GE-Star signaling, 159 hunt group dialpad, 221 MDC-1200 signaling, 153

files settings AcomConsole.ini answer next button, 209 call queue button, 211 hold button, 216

footswitch set up, 231 FPGA, 311 frame, 311


393

frame alignment, 311 frame alignment signal, 311 framer, 311 full backup, 25

G gain, 311 GE-Star signaling

call history panel setup, 159 file settings AcomConsole.ini, 159 GE-Star definitions programming, 157 line button, 161 radio line programming, 158 SMU configuration, 156

H handshaking, 311 HDB3, 311 HDLC, 311 hold button


hot plugging, 311 how to force a change-over, 249 hunt group dialpad


I IDF, 311 IMS, 312 IMS backup, 25 IMS Terminal, 311 in-band signaling, 312 instant monitor funciton button, 183 instant TX funciton button, 186 intersite bearers, 20 intersite considerations, clocking, 238 IOM-2, 312 IPAT, 312 IRR, 312 ISB, 312 ISDN, 312

L LCB, 312 level setting

terms, 32

theory, 31 line break, 312 line card, 312 line resource programming

enable caller ID incoming, 203 link, 312 LIT, 312 LLCB, 312 LMFA, 312 local BCD radio control, 132 local PTT radio control, 129 loop detect, 313 loop out, 313 LOS, 313

M maintaining backups of config files

ACS backup, 26 full backup, 25 IMS backup, 25 standby backup, 26

maintenance computer, about, 23 marker tone funciton button, 192 master clock, 313 MCU, 313 MDC-1200 signaling

dial types database, 150 edit console screen file, 151 file settings AcomConsole.ini, 153 radio line programming, 150 SMU configuration, 148

MDF, 313 microwave and T1 links, 42 monitoring system faults, 26 MSU, 313 multiframe, 313 MUSAC, 313 muting received TRC tones

radio line programming, 146 radio tone database programming, 145 SMU configuration, 143

MUX, 313

N Non Urgent Alarm, 313 NOS, 313 NRZ, 313 NTP, 313

Index

394 025-9619A

O OAM, 314 OLCB, 314 omnibus connection, 314 onboard tab, clocking, 233 optimizing system levels, 31 order wire, 314

P P25, 314 PABX, 314 paging levels for transmit audio, 43 partial time slot allocation, 314 PCM, 314 PCM-30, 314 PE, 314 permanent allocation, 21 PLL, 314 power-up sequence, 251 primary MCU, 314 primary rate, 315 protective earth, 315 PSTN, 315 PTT, 315

R radio line programming

EnRoute signaling, 165 GE-Star signaling, 158 MDC-1200 signaling, 150 muting received TRC tones, 146 tone remote control, 140 two-tone paging, 174

radio lines, 126 radio resources

local BCD radio control, 132 local PTT, 129 radio lines, 126 tone remote control, 136

radio tone database programming muting received TRC tones, 145

receive audio alignment basics, 33 console desk mic, 40 console mic alignment, 39 EIE & TIE cards, 35 radio base station alignment, 34 RIU card, 34 telephone hybrid adjustment, 36

telephone Rx level, 37 VU meter calibration, 33

receive audio adjustments, 33 recovered clock, 315 redundant bearer, 315 replacing hardware modules, 253 resource audio volume funciton button, 188 restarting the system, 250 RF, 315 RGU, 315 ring cadence, 315 ring enable/disable

console screen changes, 223 ring out signaling, 315 ring signal, 315 RMS, 315 RRA, 315 RTC, 315 RTS, 315 RVA, 315 RX, 315 RXD, 315

S Safety Extra Low Voltage, 315 safety summary, 3 SCC, 315 SDI, 315 selected phone line dialpad

console screen changes, 226 SELV, 315 service word, 315 setting up funciton buttons

channel set, 179 instant monitor, 183 instant TX, 186 marker tone, 192 resource audio volume, 188 squelch disable, 196

shuttung down the system, 250 signaling, 315 slave clock, 316 slip, 316 slot, 316 SMB, 316 SMU, 316 SMU configuration

EnRoute signaling, 163 GE-Star signaling, 156 MDC-1200 signaling, 148


395

muting received TRC tones, 143 tone remote control, 137 two-tone paging, 172

SMU programming enable caller ID incoming, 202

speed dial function button console screen changes, 229

squelch disable funciton button, 196 standby backup, 26 submultiframe, 316 subrack, 316 subrack change-over, 241 subrate communication, 316 synchronous communication, 316 system clocking, 233 system conceptual diagrams, 15 system level setting

terms, 32 theory, 31

T TDM, 316 telephone line resources, 201 theory of system level setting, 31 TIE, 316 time slot, 316 time slots, 21 TNV, 316 tone remote control, 136

radio line programming, 140 radio tone database configuration, 138 SMU configuration, 137

tone remote control adjustments, 41 transceiver, 316 transmit audio

4-wire leased lines, 42 EMU/RIU card alignment, 43 microwave and T1 links, 42

paging levels, 43 radio base station alignment, 43 telephone levels, 44 tone remote control, 41

transmit audio alignment, 41 TRC, 317 TSI, 317 TTL, 317 two-tone paging

radio line programming, 174 setting a page stack, 176 setting up an instant page, 175 setting up paging database, 175 SMU configuration, 172

TX, 317 TXD, 317

U UIO, 317 UMS, 317 urgent alarm, 317 using IMS terminal, 26

diagnostics, 28 general configuration, 27 IMS ALS module, 26 monitoring, 27

V VF, 317 VoIP, 317

W watchdog timer, 317 what is in this manual, 13 where to find more help, 14

acom system maintenance 025-9619.pdf

Documents

zetron products

zetron software

zetron accessories

zetron warrants

limitation of liability

zetron price book

zetron factory labor

current zetron hourly