Installation and Commissioning Manual 1026209 – 0001 Revision B February 24, 2000 11717 Exploration Lane, Germantown, MD 20876 Tel: (301) 428–5500 Fax: (301) 428–1868/2830
Copyright E1999–2000 Hughes Network Systems, a Hughes Electronics Corporation company All rights reserved. This publication and its contents are proprietary to Hughes Network Systems, a Hughes Electronics Corporation company. No part of this publication may be reproduced in any form or by any means without the written permission of Hughes Network Systems, 11717 Exploration Lane, Germantown, Maryland 20876.
Revision record Revision Date of issue A November 8, 1999 Initial release B February 24, 2000 Added instructions for several additional procedures; minor revisions throughout.
iv 1026209– 0001 Revision B
Contents About this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Important safety information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi xv 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1 1.1 System components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2 System Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3 Installing the Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1 3.2 3.3 3.4 3.5 vi 3–1 Rack–mount configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mounting the Controller chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . Controller cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking System Controller operation . . . . . . . . . . . . . . . . . . . . . . . System cabling . . . . . . . . .
NAM status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Initializing settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–27 6–28 7 Installing picocells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–1 7.1 Preparing for picocell installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.2 Mounting the picocells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–1 13.1 Controller problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.2 Picocell problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the IP addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding picocell IP addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.
Figures 1-1 1-2 1-3 1-4 1-5 System Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AIReach OS block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example of full rack mount . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Controller front panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Flow chart: AIReach OS major installation and test tasks . . . . . . . . .
7-9 Power terminal block connections . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10 Picocell connections at the telco closet . . . . . . . . . . . . . . . . . . . . . . 7-11 T568B–compliant wiring flip at patch panel . . . . . . . . . . . . . . . . . . 7-12 T568B–compliant wiring flip using modular jack . . . . . . . . . . . . . . 7–14 7–15 7–16 7–17 8-1 Example of a signed SSL certificate . . . . . . . . . . . . . . . . . . . . . . . . . 8–6 13-1 LEDs on front of picocell . . . . . . . .
About this manual Scope Audience Organization This manual provides instructions for installing and commissioning the AIReach Office System (AIReach OS). This manual is written for installers responsible for installating and commissioning the AIReach OS.
AIReach Office documentation set The AIReach Office documentation set for each user is listed below with the documentation number and description of the manual. All audiences AIReach Office CD–ROM (1026207–0001) Contains PDF files of all documents for online viewing. Phone user audience AIReach Office Mobile Phone Network Features Quick Guide (1027893–0001) Describes how to use each of the features of the AIReach Office System phone.
Printing PDF files Conventions for software instructions This manual is provided in Adobe Systems’ Portable Document Format (PDF) for online viewing and searching. To successfully print the entire manual from the PDF file, and ensure optimum print quality, you should use a Postscript printer and a computer with ample free hard disk space or a network print queue. On non–Postscript printers, print a relatively small number of pages at a time.
xiv About this manual 1026209– 0001 Revision B
Important safety information For your safety and protection, read this entire manual before you attempt to prepare the site for installation of the AIReach Office System Controller and picocells. In particular, read this safety section carefully. Keep this safety information where you can refer to it if necessary. Types of warnings used in this manual This section introduces the various types of warnings used in this manual to alert you to possible safety hazards.
Warnings used in this manual This manual includes the following safety warnings: WARNING When installing the picocell on the mounting plate, use care to avoid falling and injuring yourself. WARNING The AIReach Office System Controller can weigh in excess of 50 pounds. To avoid personal injury or damage to equipment, follow these precautions: • Do not attempt to move or install the System Controller by yourself. Two people are required for these tasks.
WARNING To reduce the risk of fire, use only No. 24 AWG or larger line cord to connect to the picocell, and replace the fuse only with a fuse of the type and rating identified on the fuse label. Failure to heed these warnings could result in personal injury or death.
Chapter 1 Introduction This chapter includes the following topics: • • • • • • System components – page 1–1 System Controller – page 1–3 Picocell components – page 1–7 Procedural flow chart – page 1–8 Tools and materials – page 1–11 Configuration options – page 1–12 1.1 System components The AIReach Office System (AIReach OS) is a wireless communications system designed to provide in–building voice communications. The System is integrated with an existing hard wired PBX phone system.
The AIReach OS features: • A Windows NT based System Controller with a graphical • • • • user interface (GUI) for configuration, operation, and troubleshooting Up to 64 picocells (line powered) A Primary Rate T1 connection from the Controller to the PBX An IS–41 TCP/IP connection from the Controller to the macro cellular system An optional LAN connection to a remote computer.
1.2 System Controller The System Controller consists of the following components: • A Windows NT computer with an internal floppy disk drive, a read/write CD–ROM drive, a 20–slot backplane, and system software • Telephony cards to support the AIReach OS. (For a complete description, see Chapter 5.
Monitor Keyboard with integrated touchpad Controller G-14758 F 11/04/99 Figure 1-3 Example of full rack mount Both the CD–ROM R/W (read/write) drive and a 3.5 inch floppy drive are accessible through a drop down panel on the front of the unit. Status indicators are provided on the front for fan, temperature, drive, and power. See Figure 1-4.
Filter door Release handles Status indicators FAN STATUS TEMP STATUS DRIVE ACTIVITY -12 +12 - 5 + 5 POWER SUPPLY POWER ON FAN STATUS Drive door TEMP STATUS DRIVE ACTIVITY -12 +12 - 5 + 5 POWER SUPPLY POWER ON Door lock Release handles Closed and locked CD-ROM R/W drive G-17022 F 08/04/99 3 1/2” floppy drive Drive door open Figure 1-4 System Controller front panel 1026209– 0001 Revision B Introduction 1–5
The System Controller is configured with a subset of the following hardware: • Hardware (cards): The cards that are installed in the System Controller are standard plug–in type CPU cards that are ISA or PCI compatible. The System Controller has eight ISA slots and nine PCI slots.
1.3 Picocell components The picocell consists of a backplane covered by an external housing and contains the following internal components: • Master oscillator: Provides a reference frequency for picocell signal timing. • Power supply: Converts the –48 Vdc input power to –6.5 Vdc for internal picocell operation. • Transceivers: Each traffic picocell includes up to four transceivers, with each transceiver providing three full–rate TDMA channels.
1.4 Procedural flow chart The following flow chart (Figure 1-5 on page 1–9) shows the sequence of major tasks required for site preparation, installation, and commissioning of the AIReach OS. Test picocells at the System Controller site. Complete picocell cabling before you install the System Controller and test picocells.
Start Provide Installation Package to Implementation Team Ship AIReach OS Equipment to Implementation Team Verify Contents of Installation Package Verify Contents of Shipment(s) MRC Ships Damaged Equipment to AIReach OS Vendor Discrepancies Ship Replacement or Missing Equipment to Implementation Team Missing Items Deploy to Site with Equipment No No Yes Obtain Missing Items No Additional Cards Yes Ship Damaged Equipment to Material Return Center (MRC) Conduct Pre-Installation Walk-Through w
A From previous page From previous page Receive Replacement Picocell from MRC Test Picocell Performance Picocell Failure B Yes Ship Failed Picocell to MRC No Permanently Install Scanning Picocell Verify RF Coverage Permanently Install Traffic Picocells Discrepancies Correct Identified Discrepancies Yes No Initiate Frequency Band Scan (24 Hour Minimum) Conduct Performance Test Connect Controller to PBX and Dial-up Modem Perform Installation QA Inspection Install SSL Certificate Discrepan
1.5 Tools and materials Required tools To install and service the AIReach OS, you need the tools and materials listed below.
Required materials The following materials are required: • Drywall screws • E–Z Anchor self–drilling drywall anchors (plastic), light duty • • • • • • Wood screws RJ–45 connectors RJ–11 connectors Pull string CAT 5 T1 cable CAT 5 T1 test cable (minimum 2 each, 6 feet, flipped and terminated with an RJ–45 connector on each end) • Cross–connect blocks (i.e. BIX, 66, 110 block) • Cable ties Other requirements A –48 Vdc power supply is required for testing picocells. 1.
Chapter 2 Adding cards to the System Controller This chapter includes the following topics: • • • • Unpacking the System Controller – page 2–2 Unpacking the picocells – page 2–4 System Controller card configurations – page 2–8 Adding cards to the System Controller (first steps) – page 2–11 • Jumper and DIP switch settings – page 2–13 • Attaching the bus cables – page 2–23 • Adding cards to the System Controller (final steps) – page 2–24 • Configuring System Controller cards – page 2–25 • Verifying the
2.1 Unpacking the System Controller The System Controller is delivered in three boxes containing: • System Controller (chassis) • Monitor • Keyboard The optional rack, if ordered, is shipped in a separate container. Rack mounting the System Controller is recommended, but table mounting is acceptable. Unpack the Controller as follows: 1. 2. 3. 2–2 Adding cards to the System Controller Remove the System Controller and accessory packages from the packing container as shown in Figure 2-1.
1. Remove cardboard tray and accessories 2. Remove packing Controller 3.
2.2 Unpacking the picocells After unpacking the Controller, unpack the picocells so you can record their serial numbers. Picocells are not installed until later (as explained in Chapter 7), but you need to record their serial numbers so you can enter them when you verify the Controller configuration (Chapter 4). Each picocell is packaged in a cardboard box. Unpack the picocells using the following steps. See Figure 2-2. 1. 2. 3. 2–4 Adding cards to the System Controller Open the box at the top.
2. Remove packing Picocell with attached mounting plate 1.
4. 5. Remove the lock key that is taped to the outside of the picocell mounting plate. Use the key to unlock the picocell from the mounting plate. Insert the key and turn it clockwise to a vertical position to unlock the mounting plate, as shown in Figure 2-3. 1 3 2 G-17891 F 08/25/99 Figure 2-3 Unlocking the mounting plate from the picocell 6. 2–6 Adding cards to the System Controller Remove the mounting plate from the picocell.
7. Record the serial numbers of all the picocells, from the label on the back of each picocell. Later you enter the picocell serial number as part of the base transceiver station (BTS) configuration information for the Controller. For proper picocell operation, you must enter the serial number exactly as it appears on the label—as indicated in figure 2-4. Picocell revision letter Include 1 dash before the revision letter. Serial number Include 2 dashes after the revision letter.
2.3 System Controller card configurations This section shows: • How to identify the backplane slots of the System Controller • The standard and fully loaded Controller configurations Backplane slot identification As shown in Figures 2-5 and 2-6, each slot is identified in two ways: • By slot number: Slots are labeled 1 through 20 on the rear S LO T M 56 20 O K D E M of the System Controller. • By ISA or PCI number (slot type ID): PCI 1–9, ISA 1–8.
Standard (factory) configuration The following cards are installed in the System Controller at the factory (one each): • • • • • TX2000 IP card Quad T1 card Conference card LAN card 56K modem card For backplane slot assignments for each card, see Figure 2-6. See also Figure 2-7.
Fully loaded configuration A fully loaded System Controller has the backplane loaded as shown in Figure 2-7. In this configuration, four card slots are unused and available for future functions.
2.4 Adding cards to the System Controller (first steps) In addition to the factory–installed cards listed in Section 2.3, the Site Configuration Report may specify additional cards: • Additional Quad T1 cards (up to 5 additional, for a total of 6) • A TX2000 SS7 card • A second conference card • A second LAN card If you need to replace, move, or remove a Quad T1 card see Chapter 14 for important instructions. To install a card in the System Controller, follow these steps: 1. 2.
3. Unpack the card. CAUTION Before removing or installing electronic components, make sure static electricity has been discharged from yourself and any object that may contact the component. Wear a new or recently tested anti–static wrist strap and use an anti–static pad while handling components. Failure to follow these instructions could result in damage to components. 4. 2–12 Adding cards to the System Controller Check all dual inline package (DIP) switch and jumper settings.
2.5 Jumper and DIP switch settings This section specifies all jumper and DIP switch settings for all System Controller cards. Before adding or replacing any card in the System Controller, make sure all jumper switches and DIP switches on the new card are set correctly. You may need to change some settings, and should check all jumpers and switches to make sure they are set correctly.
A Quad T1 card is factory installed in slot 9. When only one Quad T1 card is installed (or if the card is replaced), set all S1 switches to ON (terminated). This is the default setting. If you add a Quad T1 card (in slots 4 through 8), the setting for switch S1 depends on where the card is on the H.100 bus: • If the Quad T1 card is the first or last Quad T1 card on the H.100 bus, set all S1 switches to ON (H.100 bus terminated). • For cards that are not first or last on the H.
TX2000 IP and TX2000 SS7 cards This section applies to both the TX2000 IP card (factory installed in slot 16) and the TX2000 SS7 (optional, slot 15). Most settings are the same for both cards; those that are different are clearly pointed out. The key settings to check on the TX2000 cards are the IRQ and I/O address. All jumpers other than JP7 (IRQ selection) should be left in their factory default positions. Jumpers Make sure the IRQ selection jumper is in position 7, as shown in Figure 2-11.
Figure 2-11 illustrates all the TX2000 jumpers. Table 2-1 identifies the function of each jumper and summarizes the correct settings: Table 2-1 Jumper settings for TX2000 IP and TX2000 SS7 cards Use these settings. Jumper Function TX2000 IP TX2000 SS7 IRQ 7 IRQ 7 Both jumpers in vertical position (for dual port RAM); see Figure 2-11. Both jumpers in vertical position (for dual port RAM); see Figure 2-11.
Table 2-2 TX2000 card I/O address settings (switch S1) Address Setting Address Setting 8000 8200 8400 8600 8800 13 14 15 16 17 18 __ 14 15 16 17 18 13 __ 15 16 17 18 __ __ 15 16 17 18 13 14 __ 16 17 18 C000 C200 C400 C600 C800 13 14 15 16 17 __ __ 14 15 16 17 __ 13 __ 15 16 17 __ __ __ 15 16 17 __ 13 14 __ 16 17 __ 8A00 8C00 8E00 __ 14 __ 16 17 18 13 __ __ 16 17 18 __ __ __ 16 17 18 CA00 CC00 CE00 __ 14 __ 16 17 __ 13 __ __ 16 17 __ __ __ __ 16 17 __ 9000 9200 9400 9600 9800 13 14 15 __ 17 18 _
Conference card I/O address I/O address 0x2140 is used for the first conference card (in slot 13). If you install a second conference card (in slot 14), use DIP switch S1 to select address 0x2160, as shown in Figure 2-12. 1 4 ON Address for first conference card (slot 13): 0x2140 (all OFF) 1 4 ON Address for second conference card (slot 14): 0x2160 (OFF, OFF, OFF, ON) 1 4 ON JP3 JP4 S1 Leave JP3 and JP4 unconnected (no jumpers).
Table 2-3 Conference card I/O address settings (switch S1) Base addr S1–1 S1–2 S1–3 0640 ON ON ON ON 0620 ON ON ON OFF 0560 ON ON OFF ON 0540 ON ON OFF OFF 0240 ON OFF ON ON 0220 ON OFF ON OFF 0160 ON OFF OFF ON 0140 ON OFF OFF OFF 2640 OFF ON ON ON 2620 OFF ON ON OFF 2560 OFF ON OFF ON 2540 OFF ON OFF OFF 2240 OFF OFF ON ON OFF 2220 OFF OFF ON 1 OFF OFF OFF ON 2140 2 OFF OFF OFF OFF 2160 1 2 S1–4 Use for second conference
Single board computer (SBC) In the event of a problem with the SBC (slot 12), make sure DIP switch SW1 is set correctly, depending on the installed CPU, and check all jumpers. Processor configuration The standard CPU shipped with the AIReach OS System Controller is an Intel Pentium II, 450 MHz processor. Normally, the system BIOS autodetects the CPU and sets the system bus frequency accordingly.
To determine the proper FSB and multiplier for a particular processor, first read the clock speed from the label on top of the processor casing. Look at the last six numbers in the first row of numbers and/or letters. For example, 450512 indicates a processor clock speed (first three numbers) of 450 MHz, with 512K of Level–2 (L2) cache (last three numbers). In general, any Pentium II processor 333 MHz or slower uses a 66–MHz FSB, while any processor 350 MHz or faster uses a 100–MHz FSB.
Connect JP2 pins 2 and 3 for normal CMOS operation. In the event that CMOS settings prevent the AIReach OS Controller from booting, you can clear the CMOS settings by placing a jumper over JP2 pins 1 and 2. Do this only in an emergency. Clearing the CMOS helps correct only certain hardware problems. Operating system or software problems cannot be remedied through clearing the CMOS. If it is necessary to clear CMOS settings, see HNS document 1027630 for the proper settings.
2.6 Attaching the bus cables After all cards are installed, make sure the MVIP and H.100 bus ribbon cables are connected to the cards as shown in Figure 2-14. If you added any cards, connect the bus cables to the added card(s), as shown. The MVIP bus ribbon cable connects to: • The small bus adapter card attached to the top of the first Quad T1 card (in slot 9) • Any TX2000 cards • Any conference cards The H.100 bus cable connects to all Quad T1 cards.
2.7 Adding cards to the System Controller (final steps) After making sure all jumpers and DIP switches on the card are set correctly: 1. 2. 3. 4. 5. 6. 2–24 Adding cards to the System Controller Use a Phillips screwdriver to remove the screw from the card slot cover (blank panel), and then remove the card slot cover from the Controller chassis. Slide the card into place. Fully insert the card’s edge connector(s) into the sockets on the System Controller backplane.
2.8 Configuring System Controller cards Use the System Controller installation software to: • Configure a new System Controller • Configure a replacement card • Reconfigure a card after moving it to a different slot For a new System Controller, follow the configuration steps below after all cards are installed. If an installed card is replaced or moved, you must follow the steps in this section to configure or reconfigure it.
2–26 Adding cards to the System Controller 4. For newly installed cards only, click Add to display the Hardware Details window: 5. For each newly installed card, enter the following information: a. Select the Card Type for the new card from the dropdown list. b. Enter the PC Slot, PCI Bus, and PCI Slot or Address values specified in the Configuration Report.
2.9 Verifying the card configuration After entering information for new cards (Section 2.8), verify the card configuration as follows: 1. As the System Controller becomes operational (after rebooting), several background processes appear on the Windows taskbar. Verify that the AIReach OS software applications are present, as indicated on the Windows taskbar: The taskbar may show other applications in addition to those shown here. (The taskbar is shown vertically here, so the labels can be read.
2. Launch the AIReach Office application by double–clicking on the desktop icon labeled AROS Configuration (shown below). The software displays the AIReach Office banner window shown below and a Login dialog box that shows AROSC: Localhost. “Localhost,” the default Controller selection, indicates that you are logging onto the local Controller. 3. In the Login dialog box, enter: - The name of the Controller you want to connect to (after AROSC) - User name (No entry is needed if this field is grayed out.
6. 7. 8. 9. 10. 1026209– 0001 Revision B From the AIReach banner window main menu, select Configure → BSC Configuration. Click the HW Config tab to display the AROSC Configuration window shown below. If any installed cards are not listed, click Add to add the card(s). The AIReach OS software prompts you to enter the type of card you want to add. After you enter the appropriate information, the software displays a configuration window for the type of card you indicated.
Adding a Quad T1 card If you specified a Quad T1 card (in step 9), the software displays this window, which shows parameters for configuring the Quad T1 card: 11. For each T1 line (Line 1, Line 2 . . . ), verify or select the following values: - PC Slot: Slot where the card is installed. - Connection Type: BTS or PBX. Set according to whether a BTS or PBX will be connected to the line. If initially there will be no connection to a line, select BTS. - Desired State: INS (in service). - Line Code: B8ZS.
Adding a TX2000 or conference card If you specified a TX2000 card or conference card (in step 9), the software displays this window, which shows parameters for configuring the TX2000 card or conference card: 14. 15. 16. 17. 18. 1026209– 0001 Revision B Select the TX2000 or conference card from the Card Type dropdown list. Verify the displayed values. Select INS from the Desired State menu. Click Accept to save the information.
Chapter 3 Installing the Controller This chapter includes the following topics: • • • • • Rack–mount configuration – page 3–2 Mounting the Controller chassis – page 3–4 Controller cabling – page 3–5 Checking System Controller operation – page 3–6 System cabling – page 3–7 The AIReach OS System Controller, monitor, and associated components are typically installed in a rack. All cards must be installed in the System Controller before the Controller is installed in the rack.
3.1 Rack–mount configuration Mount the System Controller, monitor, and keyboard (with touchpad) on an available 19–inch rack, as shown in Figure 3-1 . Optionally, a UPS, power distribution tray, patch panel, and CSU tray can be mounted on the same rack. (These components are also shown in Figure 3-1.) WARNING The AIReach Office System Controller can weigh in excess of 50 pounds.
Power distribution Monitor Keyboard and mouse Controller Patch panel CSU tray UPS G-17207 F 07/01/99 Figure 3-1 System Controller and associated components in a 19–inch rack (typical installation) 1026209– 0001 Revision B Installing the Controller 3–3
3.2 Mounting the Controller chassis Mount the System Controller chassis to the rack as follows: 1. Choose a location in the rack that allows easy access to the monitor, keyboard and rear of the Controller. 2. Position the Controller on the vertical side rails of the rack. 3. Secure the Controller to the front of the rack using the eight provided mounting screws. See Figure 3-2, which shows the screw holes on each side of the chassis (front). G-17420 F 10/04/99 Figure 3-2 Installing the chassis 4.
3.3 Controller cabling After mounting the components in the rack, connect the keyboard, monitor, touchpad cables, and printer (if used) to the ports shown in Figure 3-3: 1. Connect the monitor video cable to the video port on the rear of the single board computer (SBC) (slot 12). Connect the touchpad to the mouse port on the rear of the SBC card. The touchpad and keyboard cables split off from a single cable.
5. 6. Provide power to the monitor and System Controller (110 Vac, 60 Hz). Figure 3-3 shows the Controller power connector. Verify that the System Controller power indicators are lit. The power indicators on the front and rear of the Controller are on only if power is connected to the Controller and the front panel power switch is on. 3.4 Checking System Controller operation To check System Controller operation: 1. 2. 3. 4. Power on the System Controller.
3.5 System cabling 1026209– 0001 Revision B For information on system cabling, see the Site Preparation Manual (1026208–0001).
Chapter 4 Verifying the System Controller configuration After the System Controller has been unpacked, configured with hardware (cards), and installed, verify the configuration as explained in the following sections: • Data required – page 4–2 • Verifying the System Controller configuration – page 4–1 4.
4.2 Verifying the System Controller configuration To verify the System Controller configuration, you use the AIReach Office Operation and Maintenance Center (OMC) software, as explained below. The OMC software runs on the System Controller, under Microsoft Windows NT. Important: For configuration values to enter in the AIReach OS software windows, see the site–specific AIReach Office Configuration Report.
5. Select Configure → BSC Configuration from the AIReach Office banner to display the main AROSC Configuration window, shown below. 6. Verify the following information: - AROSC Name Verify that the AROSC Name matches the name assigned to the Controller by clicking Start → Settings → Control Panel → Network → Network ID. Do not change the AROSC Name unless the TAC instructs you to do so. - Operating Mode: Normal - Companding Type: Mu–Law 7.
Verifying the card information Verify the card information for each card that is installed in the System Controller. 1. Click the HW Config tab to see information for the installed cards: 2. Verify that the cards installed in the Controller are configured for the specific site. At least one Quad T1 card, one TX2000 card, and one conference card must be listed.
3. Select (highlight) the first Quad T1 card and double–click on the card name to display the Hardware Configuration window. 4. Select the Line 1, Line 2, Line 3, and Line 4 tabs, in order, and verify the displayed information. Select SLAVE clock reference for all line numbers except those connected to the PBX. For the Quad T1 port connected (or to be connected) to the PBX, set the Clock Reference to MASTER_EXTERNAL. A second PBX connection can be set to BACKUP.
8. 9. 10. 11. 4–6 Verifying the System Controller configuration Highlight the TX2000 card and double–click to display the Hardware Configuration window. Verify the Desired State—INS (in service); then click Accept. Highlight the conference card and double–click to display the Hardware Configuration window. Verify the Desired State—INS (in service); then click Accept.
1026209– 0001 Revision B 12. In the AROSC Configuration window, click the Clusters tab. 13. If the specified clusters are not listed, click Add to display the Cell Configuration – New window: 14. 15. Enter the specified cluster name. Select the band to use from the Band dropdown list, and click Accept.
16. Select the Frequency Assignment tab. 17. If no channels are listed in the Cluster Frequencies column (values are channels, not frequencies): a. For the specified band, enter the start channel in the left box and the end channel in the right box below “Specify a frequency or range . . . “ b. Click Enable. c. Enter AROSC pool size: 30 d. Click Accept. Click the Scanner Parameters tab. (The screen for this tab is not shown.) Verify or enter the specified values, and click Accept.
Verifying the Network data information 1026209– 0001 Revision B Configure or verify the information for the network data. For all configuration windows shown or referred to through the end of this chapter, do not change default information unless you are instructed to do so in this manual or by the RF engineer. 1. In the AROSC Configuration window, click the Network tab to display the window shown below. 2.
4. 5. 6. If the PSID (public system identification) is not displayed for the cluster, click Add P/RSID. Make sure all AIReach Office clusters are assigned the same PSID value. Enter the specified PSID information for each cluster and click Accept. Click Close to return the AROSC Configuration window. 7. Click the Frequency/DVCC tab; then click the tab for the specified band (800–A in the example below) to display the window illustrated below: 8.
9. 10. 11. 1026209– 0001 Revision B Click the IS136 tab (not shown) to display the AROSC configuration window. Click the Network Parameters tab. Verify the Service Operator (SOC) and Mobile country information; then click Accept. 12. 13. Click the Mobile Call Control tab. Verify the information displayed; then click Accept. 14. 15. Click the AROSC Services tab. Verify the information displayed; then click Accept. 16. 17. Click the Call Control tab.
Verifying the Cell information Cell information is configured to provide the Controller with data for each picocell’s DCCH, handoff, physical layers, RRM, and the dedicated scanning picocell. To configure the picocell information: 1. 2. 3. 4. 5. Click the Cells tab. (The window displayed—not shown here—may or may not contain data.) Click Add to display the Cell Configuration – New window. Enter the data for the scanning picocell. Make sure there is a check mark in the Dedicated Scanning Cell box.
6. Click Close to return to the AROSC Configuration window. The scanning picocell you added should now be listed. 7. 8. Click Add to display the Cell Configuration – New window. Enter the required data for a traffic picocell. 9. Click the Cell DCCH tab. Verify the information displayed. 10. Click the Cell Handoff tab. Verify the information displayed. 11. Click the Cell Physical Layer tab. Verify the information displayed. 12. Click the Cell RRM tab. Verify the information displayed. 13.
Verifying the BTS information To provide the System Controller with the BTS information, follow these directions: 1. 2. 3. Click the BTSs tab. (The BTSs window may or may not contain data.) Click Add to display the BTS Configuration – New window. Enter or verify the information for the scanning picocell.
When you enter the serial number (from the label on the back of each picocell), you must enter the serial number exactly as it appears on the label—as indicated in figure 4-1. If the serial number is entered incorrectly, the picocell may not operate correctly. Picocell revision letter Include 1 dash before the revision letter. Serial number Include 2 dashes after the revision letter. AVPU-D--02025234 T0001001 Enter all 8 digits, including leading zeros, as on the label.
5. 6. 7. 8. 9. 10. Click the BTS Components tab. Enter or verify the information for the BTS components. The Desired State for all slots should be set to AUTO. Click Accept. Click Close to return to the AROSC Configuration window. Repeat steps 1 through 5 until all traffic picocells are listed in the AROSC Configuration window (BTSs tab). Minimize the AROSC Configuration window to return to the AIReach Office window.
Verifying the systemwide configuration To verify the systemwide configuration: 1. 2. 3. 4. 5. From the AIReach Office banner menu, select Configure → NSS → Systemwide to display the System Wide Configuration window. Click the System Capability tab. Select the specified AROSC Name from the dropdown list. Enter or verify the system capability information. The default selection for IS41 Interface is GW (gateway).
6. 7. Click the Service Code tab. The Service ID should display Emergency. The customer may provide updated information during the time of installation. Enter or verify the information; then click Save. 8. 9. Click the IS–41 Timer tab. Enter or verify the information; then click Save. 10. 11. Click the Transport tab. Enter or verify the information for the WOS to Gateway Server Address and Server Port values; then click Save. 12. 13. 14. Click the Line Range tab. Verify the Line Range values.
Verifying the MSC configuration Verify the MSC Configuration as follows: 1. 2. 3. 4. 1026209– 0001 Revision B From the AIReach Office banner menu, select Configure → NSS → MSC → MSC Configuration. Click the MSC configuration tab. The parameters that appear in the MSC Configuration window depend on whether you selected GW (for gateway) or SS7 from the IS41 Interface dropdown list in the System Wide Configuration window. The screen shown below is for a gateway (GW) configuration.
5. 6. 7. 8. 9. 10. 11. 12. 13. Click the BSC Configuration tab. Enter or verify the information. Make sure all traffic picocells to be installed are assigned a BSC. Verify that all enabled BSC RNUM values are greater than zero and match the Registration Number entered in the Cell Configuration – New window (shown on page 4–12). Click Save. Click the MSC Timer tab. Enter or verify the information. Use the scrollbar to view all fields. Click Save. Click the TLDN Range tab.
Configuring the HLR Configure the HLR (Home Location Register) as follows: 1. From the AIReach Office window, select Configure → NSS → HLR to display the HLR Configuration window. (This window initially contains no data.) Note You only need to configure the HLR once (not once for each picocell). 2. 4. Select the AROSC Name from the dropdown menu and enter the specific values. Then click the Save button. Select the NPA–Nxx tab.
7. 8. 9. 10. Select the MIN Range tab. Enter the following values for the first test mobile: a. Begin MIN: Enter the test mobile MIN (mobile identification number). b. Allocation Type: Select Individually allocated from the dropdown list. c. MIN Type: Select AROS only subscriber from the dropdown list. Click Save. Repeat steps 8 and 9 for the second test mobile phone. Provision at least two test subscribers in the System Controller to verify proper traffic picocell operation. 11. 12. 13. 14. 15.
Chapter 5 Configuring the router This chapter includes the following topics: • Installing the router – page 5–2 • Configuring the router – page 5–2 • Configuring the Controller for gateway access – page 5–7 The AIReach OS supports the Cisco 1602–R router. The information in this chapter applies to the Cisco 1602–R router. If you use a different router, you may be able to apply some of this information, but you will have to configure your router according to the manufacturer’s instructions.
5.1 Installing the router When you install the router: • Install the router in the location specified in the Configuration Report. • Install the router according to the manufacturer’s instructions. • Use CAT 5 T1 cable to connect the router to the Controller and to the service provider’s gateway. 5.2 Configuring the router To configure the router, you need to obtain the gateway IP address and circuit identification values from the customer.
4. Edit the renamed router configuration file, listed below, with the appropriate IP addresses, masks, and passwords (if used): service udp–small–servers service tcp–small–servers ! hostname ! ip subnet–zero no ip domain–lookup ! interface Ethernet0 ip address ! interface Serial0 description Leased Line to AT&T (–>) ip address encapsulation frame–relay bandwidth 56 frame–relay interface–dlci ! no router rip ! ip route Z.Z.Z.0 255.
8. If a router HyperTerminal was previously configured: a. Click the desired HyperTerminal icon. b. Select Connect from the dropdown list. 9. If a router HyperTerminal was not configured: a. Click the HyperTerminal icon. b. Select Connect from the dropdown list. c. Enter the name for the HyperTerminal (Cisco) and select an icon. d. Select Direct to com 1. e. Click OK. f. Select 9600 (bits per second) from the dropdown list. g. Click OK to display an active HyperTerminal window. 10.
18. 19. Router configuration example To exit router privileged mode, enter exit at the Router > prompt. Connect the router to the service provider frame relay service. Figure 5-2 and the file that follows are examples of a typical router configuration. RELIATEL INC frame relay 142.148.254.102 255.255.255.252 DLCI = 500 DLCI = 300 142.146.254.101 255.255.255.252 S0 E0 Acme Corporation Cisco 1602-R router S1 RELIATEL INC router 142.146.254.97 255.255.255.252 E1 142.146.254.17 255.255.255.
The file below is an example of a typical router configuration. It is the configuration file for the network shown in Figure 5-2. service udp–small–servers service tcp–small–servers ! hostname acme64 ! ip subnet–zero no ip domain–lookup ! interface Ethernet0 ip address 142.146.254.97 255.255.255.252 ! interface Serial0 description Leased Line to RELIATEL ip address 142.146.254.102 255.255.255.252 encapsulation frame–relay bandwidth 56 frame–relay interface–dlci 300 ! no router rip ! ip route 142.146.254.
5.3 Gateway access To set up the AIReach OS System Controller to access the IS–41 gateway: 1. Using Notepad, edit the file C:\gwroutes.bat to remove REM from the line route ADD –p yyy.yyy.yyy.0 mask 255.255.255.0 xxx.xxx.xxx.xxx 1026209– 0001 Revision B 2. Enter the first three digits of the IS–41 gateway IP address in place of yyy.yyy.yyy . For example, if the IS–41 gateway IP address is 198.225.8.1, enter 198.225.8, so the address (after –p) would be 198.225.8.0. 3. In the xxx.xxx.xxx.
15. After the Controller reboots, verify connectivity to the IS–41 gateway by pinging the gateway IP address: a. b. Select Start → Programs → Command Prompt to open a DOS window. At the DOS prompt (C:>\), enter ping c.
Chapter 6 Testing picocells This chapter includes the following topics: • • • • • • • • • • Connecting a picocell for testing – page 6–2 Verifying software load – page 6–5 Checking scanning picocell operation – page 6–6 Performing a test frequency band scan – page 6–10 Checking traffic picocell operation – page 6–17 Provisioning test mobile phones – page 6–20 Programming test mobile phones – page 6–22 Registering test mobile phones – page 6–23 Placing test calls – page 6–24 Additional phone programming p
6.1 Connecting a picocell for testing This section explains how to connect a picocell (scanning picocell or traffic picocell) at the staging area for testing (not for actual installation). Test cable: The test cable referred to below is a CAT 5 T1 cable terminated with RJ–45 connectors at both ends. The cable is “flipped” so the TX pinouts at one end connect to the RX pinouts at the other end. (For pinout details, see page 7-12.
Power switch Line power LINE I OFF Local power o LOCAL I Picocell LOCAL POWER + Local power connector (not used) VOICE/ DATA OUT Connect test cable here. (TX and RX pinouts must be flipped).
LEDs PBX connection (typically first port of first Quad T1 card, in slot 9) 1 For all other Quad T1 cards: picocell connection 2 All ports: RJ-45 3 Picocell connections 4 T0001007 Figure 6-2 Ports on Quad T1 card Providing power to the picocell Provide power to the picocell: 1. 2. Connect a –48 Vdc power supply to the test cable. Plug the power supply into a 120 Vac, 60 Hz ac outlet.
6.2 Verifying software load Power on the picocell, and observe the picocell LEDs as the System Controller automatically downloads software to the picocell: 1. 2. Press the picocell power switch to the LINE (line power) position. Observe the LEDs for normal operation: a. During software loading, the Temp LED on the front of the picocell is orange. See Figure 6-3. b. When the picocell is fully loaded and operational, the Power and Temp LEDs display green, and the Alarm LED is off.
6.3 Checking scanning picocell operation At the System Controller, verify scanning picocell operation first, as explained in this section. Then verify traffic picocell operation, as explained in Section 6.5. Check the scanning picocell operability, as follows: 1. 2. 3. 6–6 Testing picocells Verify that the scanning picocell is connected with the test cable as explained in Section 6.1. Make sure the picocell is powered on (power switch in the LINE position).
f. If the red or yellow LED remains lit, repeat steps c through e. Yellow Green Red LED indications Green = Operational LEDs Red = Not operational; error condition Yellow = Not operational; error condition. Controller problem. 1 2 Ports LED positions top to bottom match port positions.
4. 6–8 Testing picocells Click WOS BSC Application to display the WOS BSC Application window.
5. 6. Select Btsm → State to display the Select BTS window. Select the scanning picocell from the dropdown menu. 7. Verify that the scanning picocell self–test and software download are successful: a. BTC: Select each BTC (using the dropdown menu) and verify that 0 appears in the chan window. b. WBSU State: Verify that the state is Active. c. Close the window and return to the WOS BSC Application window. 8. Minimize the WOS BSC Application window to return to the AIReach Office window.
6.4 Performing a test frequency band scan Perform an initial (test) 6–minute frequency band scan at the System Controller location. The initial band scan is used to quickly find a frequency that can be used to test all the picocells at the Controller location. Later, you perform a 24–hour (or longer) band scan to set up the system for normal operation. Note The system is not available for traffic during a band scan.
Setting up the frequency band scan 1026209– 0001 Revision B Set up the band scan as follows: 1. From the AIReach Office banner, select Installation → Auto Setup. The software displays the Welcome to AROSC Band Scan Setup Wizard window: 2. Enter the following entries in the Setup Wizard window: a. Perform Band Scan to Discover Usable Frequencies: Check (Click the box so a check mark is displayed.) b. Perform DCCH Scan to Configure PSPs: Check c. Number of Reports required: 1. d.
3. Click Next to display the Band Scan Parameters window. 4. Set Critical RSSI bin Uplink and Downlink to 0 for the 6–minute band scan (For the subsequent 24–hour band scan, set Critical RSSI bin Uplink and Downlink to 3.) In the remaining boxes, use the default parameters unless otherwise instructed (for example, by the macro provider, or in release notes). Click Next to display the Select Cells for the Test window. 5. 6.
7. 8. 9. Starting the scan and observing the results Check the box associated with the scanning picocell name and select the Uplink / Downlink Scan in the Scan Mode column when necessary. Click Next to display the Start Scan Frequency Band Scan window.
Approximately 6 minutes after the band scan was started, the Frequency Band Scanning in Progress window automatically closes and the DCCH Scanning in Progress window is automatically displayed (not shown here). When the DCCH band scan is finished, the DCCH Scanning in Progress window automatically closes, and the Band Scanning Results window is automatically displayed: The Band Scanning Results window indicates if frequencies are usable or not, based on user–specified limits.
3. Click Next to see the DCCH Scanning Results window (not shown here). 4. Click Next to access the Select Measurements Reports window. 5. For the scanning picocell used to perform the frequency and DCCH band scan: a. Check: - Use to Assign Frequencies - Use to Assign POFs (private operating frequencies) - Use to Assign PSPs (public service profiles) b. 6. 1026209– 0001 Revision B Do not check “Use results of previous tests if any.” Click Next in succession to display these windows: a.
7. Click Next again and the Setup Complete window is displayed. 8. Click Finish and the AIReach Office banner window is displayed. The POFs and cluster pool are now automatically assigned. Returning to normal operation 1. From the AIReach Office banner, select Configure → BSC Configuration → AROSC. 2. Select Normal from the Operating Mode dropdown list, then click Accept.
6.5 Checking traffic picocell operation Perform this test sequence for each traffic picocell. Temporarily connect the traffic picocell to the System Controller to verify that the picocell is operating properly. 1. 2. 3. 1026209– 0001 Revision B Verify that the traffic picocell is connected with the test cable, as explained in Section 6.1. Make sure the picocell is powered on (power switch in the LINE position).
4. 6–18 Testing picocells Click WOS BSC Application to display the WOS BSC Application window.
5. 6. Select Btsm → State. Select the traffic picocell using the dropdown menu below “WBSU.” 7. Verify that the traffic picocell self–test and software download are successful: a. b. c. d. 8. BTC: Verify that one of the channels identified as usable from the test frequency band scan appears for BTC 1. WBSU State: Verify that the state is Active. BTC State: Verify that the state is Active. DCCH State: Verify that the state is Active.
6.6 Provisioning test mobile phones Subscriber provisioning This section explains how to provision test mobile phones so they can be used to check traffic picocells. Multiple users can access and use subscriber configuration windows at the same time. Enter and verify the subscriber provisioning information. 1. From the AIReach Office window: a. Select the Configure → Subscribers. b. Click the Identification tab. Initially, this window does not contain data. 2. 3. 4. 5. 6.
7. 8. 1026209– 0001 Revision B Click the Basic Services tab. Enter the information; then click Save. 9. 10. Select the Supplementary Services tab. Enter the information; then click Save. 11. 12. Select the Service Profile tab. Enter the information; then click Save. 13. 14. 15. Select the PSID/RSID tab. Enter the PSID value. When you enter a value, press the Enter or Tab key afterward. The Save button is “grayed” (not available) until you press the Enter or Tab key.
18. 19. Click the Operational Status tab. Verify that the specified HLR Flags and VLR Flags are displayed. 6.7 Programming test mobile phones The next step (detailed in Section 6.9) is to place test calls to test the picocells. However, before phones can be used for testing, they must be programmed for the customer system, as explained below, and then registered (as explained in Section 6.8). Installers use Nokia 6120, 6160, or 6161 mobile phones to test the AIReach OS.
6.8 Registering test mobile phones To register the test mobile phones on the AIReach OS, follow the steps below. Prerequisites: • The test phone must be provisioned, with the correct MIN and ESN (Section 6.6). • The phone must be in field test mode (Section 6.7). Registration procedure: These instructions are for Nokia 6120 and 6160 mobile phones. 1. 2. 3. 4. 5. 6. 7. 1026209– 0001 Revision B Power the phone off, then on.
6.9 Placing test calls The procedures below explain how to test all transceivers in each installed traffic picocell. 1. Determine which picocell slots contain transceivers (BTCs). A label attached to the picocell tells you which slots contain BTCs. The slot arrangement and numbering scheme are shown in Figure 6-5. CPU 0 1 Depending on the picocell configuration, slots 0 - 4 may contain 2 to 4 BTCs, a scanning receiver – or some slots may be empty. The CPU slot is not numbered.
4. 5. Testing the remaining transceivers The test is successful if the transceiver processes the call and the displayed power level reading varies no more than 5 units from all other picocells. Notify the MRC and request an RMA if: - The transceiver fails to process a test call. - The power level reading varies by more than 5 units compared with readings from all other picocells. Test the remaining transceivers as follows: 1. Bring another traffic picocell transceiver into service: a. b. c. d. 2. 3.
6.10 Additional phone programming procedures Home system ID The following programming procedures for Nokia Series 6000 mobile phones are provided for the installer’s convenience. However, normally, these procedures are not required to complete and test the installation. To program the home system ID number for a Nokia 6000 series mobile phone: 1. Enter *3001#12345#. 2. Press until Field Test displays, then press 3. Press until Enabled is highlighted and press 4.
Operator Code (SOC) To program the Operator Code (SOC): 1. until the Operator Code (SOC) displays and Press press . 2. Verify that the Operator Code displays 4. 3. If the Operator Code is incorrect, press . press NAM status , enter 4, and To program the NAM Status for a Nokia series 6000 phone: 1. Press or (right button) until NAM1 displays and press . until Change Defaults displays and press . 2. Press 3. Verify that the NAM Status displays enabled. 4.
Initializing settings To initialize changed settings for a Nokia series 6000 phone: (You do not need to do these steps after putting the phone into field test mode and entering the MIN.) 1. Power off the cellular phone and then turn the power on. 2. Press (Menu) to display the menu. 3. Press or 4. Press until Network Services displays. 5. Verify that digital & analog displays. 6.
Chapter 7 Installing picocells This chapter describes how to install a picocell at the permanent site. It includes the following sections: • • • • Preparing for picocell installation – page 7–1 Mounting the picocells – page 7–2 Installing and connecting picocells – page 7–7 Performing the frequency band scan – page 7–18 Install the scanning picocell first, and then the traffic picocells.
7.2 Mounting the picocells The picocell is designed to be attached to different wall surfaces: wallboard, concrete, wood, or metal or wood studs. Installing the mounting plate The mounting plate must have at least 4.5 to 5. inches of clearance on all sides (from ceiling, floor, and walls) so the picocell will have proper clearance (3 inches minimum) for mounting and ventilation. See Figure 7-1. Ceiling 4.5" 4.5" 5" 4.
Figure 7-2 shows the position of the mounting plate relative to the picocell. 1.375” 1.5” 2.0” 1 2 4 Picocell 3 2.75” G-17371 F 08/24/99 Notice that clearance for the mounting plate is not the same on each side. Figure 7-2 Position of the picocell on the mounting plate Note This note applies only to pre–production picocells: Mounting plate revisions are not upward compatible.
Table 7-1 Surface Approved mounting plate fasteners Fastener Fastener part number Hole locations 1 Drywall (hollow) E–Z Anchor self–drilling drywall anchor and screw 9010193–0001 1, 2, 3, 4 Concrete block or concrete t Lead anchor for 10–24 screw 9004929–0001 1, 2, 3, 4 Phillips head machine screw, 10–24 x 3/4” 9003333–0074 Metal wall or metal studs Sheet metal screw, self–drilling, self–tapping, 10 x 3/4” 1028868–0018 1, 3 Wood wall or wood studs Wood screw, 10 x 1–1/4” 1028228–0021 1,
Note If you use option 1 to mount the picocell near a door, remember to maintain the proper clearance between the top edge of the picocell and the ceiling.
Mounting plate Th is 1 eu p sid 4 2 3 Four fasteners G-17414 F 10/04/99 Figure 7-4 Attaching the picocell mounting plate to concrete, block, or wallboard To attach the mounting plate (for all wall types): 7–6 Installing picocell 1. Position the mounting plate on the wall: a. Make sure the part labeled “This side up” is on top. b. Allow at least the minimum clearance, as shown in Figure 7-1. c. Make sure the mounting plate is level. 2. 3. Mark on the wall the position of each mounting screw.
7.3 Installing and connecting picocells This procedure applies to both the scanning picocell and traffic picocells. Install the scanning picocell in its permanent location prior to completing the 24–hour (minimum) frequency band scan (section 7.4). To save time, initiate the 24–hour frequency band scan (Section 7.4) and then install the traffic picocells at their permanent locations while the band scan is running.
Picocell connections Connect the T1/power cable as follows: 1. Terminate the T1 cable(s) with RJ–45 connectors on each end using the pinout plan shown in Table 7-2 . T0002001 Plastic clip Pin 1 RJ–45 connector, showing pin 1 position Table 7-2 Pin 2.
3. Route the T1/power cable through the opening in the wall mounting plate (as shown in Figure 7-5). An acceptable alternative is to run the cable down from the ceiling, along the wall to the picocell.
4. Connect the T1 cable (with RJ–45 connector) to the appropriate picocell port, as shown in Figure 7-6. Power switch Line power LINE I OFF Local power o LOCAL I Picocell LOCAL POWER + Connect CAT 5 T1 cable here for daisy-chained picocell. Local power (not used) VOICE/ DATA OUT VOICE/ DATA IN Connect CAT 5 T1/power cable here for both standalone and daisychained picocells.
Picocells Telco blocks VOICE/ DATA OUT Power switch VOICE/DATA IN VOICE/ DATA OUT To Controller VOICE/ DATA OUT VOICE/DATA IN VOICE/ DATA IN VOICE/ DATA OUT VOICE/DATA IN CAT 5 T1 cabling (single run) Standalone picocells Picocells Telco blocks VOICE/ DATA OUT Power switch To Controller VOICE/DATA IN VOICE/ DATA OUT VOICE/ DATA OUT VOICE/DATA IN VOICE/ DATA IN VOICE/ DATA OUT VOICE/DATA IN CAT 5 T1 cabling (double run) Daisy-chained picocells T0001009 Figure 7-7 T1 cabling for standalo
Mounting the picocell Mount the picocell as follows: 1. 2. Power on the picocell by pressing the power switch to the LINE position. Mount the picocell to the mounting plate by aligning the lock on the picocell housing with the positioning tab on the mounting plate, as shown in Figure 7-8. WARNING When installing the picocell on the mounting plate, use care to avoid falling and injuring yourself. 3. 4.
Align picocell with mounting plate, push in, pull down, and push right to secure 1 2 Mounting plate Th is 3 1 eu p sid 4 2 3 Align locking tab with alignment dots on picocell G-14764 F 08/24/99 Figure 7-8 Mounting the picocell 5. 1026209– 0001 Revision B Punch down and label the T1 cables on the telco room termination block.
6. Set up the power connection: a. Mount the power supply in the telco room. Typically, the power supply is mounted to plywood. b. Remove the DIN connector from the power wire. c. Strip the end of the wire. d. Clip the green wire (not used), fold it back, and heat shrink it. e. Connect the wires from the power supply to the terminal block, as shown in Figure 7-9 and Table 7-3 . f. Plug the power cable into a 110 Vac outlet.
WIRING CLOSET Telco blocks can be: - 66 block - 110 block or - Bix block Terminal block (see detail) CAT 5 cable Building riser telco block for T1 cross-connect to Controller Telco block for picocell T1 connections Picocell AC outlet Power supply T1 bundle to/from Controller Terminal block detail Heat shrink Two pairs of CAT 5 to merge with cable to picocell G-17890 F 10/04/99 To power supply Figure 7-10 Picocell connections at the telco closet 1026209– 0001 Revision B Installing picocell 7–1
T1 wiring and flip Important: All T1 wiring must comply with TIA/EIA–568A and TIA/EIA–606. (In Canada, T1 wiring must comply with CSA Standards T528 and T529.) These standards are listed in Appendix B, Section B.5. A T568B–compliant wiring flip must be used between: • The Controller and picocell • Daisy–chained picocells (that is, between each picocell–to–picocell connection) The flip is accomplished at the patch panel (as shown in Figure 7-11) or using a modular jack (Figure 7-12).
Pair 3 Pair 2 Pair 1 Pair 4 RJ-45 connector pinout for T568B-compliant flip Flipped end T568B BR O W -G B W L -B L W G -B R W -O 1 2 3 4 5 6 7 8 Pin and color code Pin Signal Color code Pin Signal 1 TX Ring White-orange 5 RX Ring Color code White-blue 2 TX Tip Orange-white 4 RX Tip Blue-white 3 Pos DC White-green 3 Pos DC White-green 4 RX Tip Blue-white 1 TX Ring White-orange 5 RX Ring White-blue 2 TX Tip Orange-white 6 Neg DC Green-white 6 Neg DC Green-white
7.4 Performing the frequency band scan Section 6.3 explains how to initiate a test (6–minute) frequency band scan (starting on page 6–10). Now that the system is installed, you perform a band scan to set up the system for normal operation—specifically, to determine what frequencies the AIReach OS can use. The post–installation scan takes a minimum of 24 hours. The AIReach Office Configuration Report states the actual time requirement. Initiate the 24–hour band scan as explained in Section 6.
Chapter 8 Connecting to external equipment This chapter includes: • • • • • Connecting the Controller to the PBX – page 8–2 Installing the SSL certificate – page 8–4 Repointing the HLR – page 8–8 Installing a second LAN card (optional) – page 8–9 Enabling alarm paging – page 8–11 As shown in Figure 1-2 (page 1–2), the AIReach OS Controller connects to: • The customer’s PBX • The macro cellular system • The customer’s corporate LAN (optional) The procedures explained in this chapter are related to these
8.1 Connecting the Controller to the PBX To establish final System Controller connectivity, connect the Controller to the PBX and connect the analog line as follows: 1. 2. 3. 4. Terminate the PBX T1 trunk CAT 5 cable with a RJ–45 connector. Connect the PBX T1 trunk to port 1 of the assigned Quad T1 card. Verify that the Controller configuration values indicated below are set to the values specified in the (customer site–specific) AIReach OS Configuration Report.
d. In the System Variables listing, search for SRM_USER_SIDE and SRM_OPERATOR: SRM_USER_SIDE 0 (default) – Set this variable to 0 if the Controller is on the network side of the ISDN interface. 1 – Set the variable to 1 if the Controller is on the user side of the ISDN interface. SRM_OPERATOR Protocol used on the ISDN link to the PBX: 4ESS (default) Other possible values: DMS100, N12, and 5E10 If the variable is not present, the default value is applied.
8.2 Installing the SSL certificate Creating the request file Follow the instructions in this section to obtain and install a Secure Socket Layer (SSL) certificate: (SSL provides data encryption between the Controller and the IS–41 gateway.) First you create a file you will use to request an SSL certificate: 1. Open a DOS window by selecting Start → Programs → Command Prompt. 2. At the DOS prompt (C:\>) enter cd C:\Program Files\spst 3. At the DOS prompt (C:\Program Files\spst\>), create the files csr.
1. Copy the block of information, starting with (and including) the header ––––BEGIN CERTIFICATE–––– and ending with (and including) the footer ––––END CERTIFICATE–––– 2. 3. 4. 5. 6. Paste the block just copied at the beginning of the spst.key file created in step 3 on page 8–4. Save the modified spst.key file created in steps 1 and 2 above as spst_c.pem. Open the file spstca.pem.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ======================================= WOS Certificate follows: –––––BEGIN CERTIFICATE––––– MIICozCCAgygAwIBAgIBQTANBgkqhkiG9w0BAQQFADBoMQswCQYDVQQGEwJVUzEf MB0GA1UEChQWQVQmVCBXaXJlbGVzcyBTZXJ2aWNlczEQMA4GA1UECxMHVERHIExh YjEmMCQGA1UEAxMdVERHIExhYiBDZXJ0aWZpY2F0ZSBBdXRob3JpdHkwHhcNOTkx MTA4MTkzMjI0WhcNMDQxMTA2MTkzMjI0WjCBjjELMAkGA1UEBhMCVVMxETAPBgNV BAgTCE1hcnlsYW5kMRMwEQYDVQQHEwpHZXJtYW50b3duMR8w
Installing the certificate Install the SSL certificate: 1. 2. 3. 4. 5. 6. 7. Open the AIReach Office Application if it is not already open. Select Configure → NSS → Systemwide to open the System Configuration window. Click the Transport tab. In the WOS to Gateway Server Address line, enter the gateway address and port number. (Obtain these from the gateway provider.) Click Save. By default, the IS–41 link is configured to operate in secure mode.
8.3 Repointing the HLR Once the SSL link has been established and heartbeats are received from the gateway, repoint the AIReach OS HLR to the macro HLR, as follows: 1. 2. 3. 4. 5. 6. From the AIReach Office banner menu, select Configure → NSS → SystemWide. Select the Line Range tab. Select the AROSC Name. Change the HLR Point Code to an invalid but non–zero number, such as 1.1.1. Restart the Router application by closing the Router window.
8.4 Installing a second LAN card and driver (optional) Installing the LAN card If a second LAN card is required for an administrative LAN, follow the instructions below to install the second card and LAN card driver: Install the second LAN card in chassis slot 3, according to the manufacturer’s instructions. Note The second LAN card must be the same brand and model as the LAN card shipped from the factory. Any exceptions must be approved through the TAC.
Entering the IP address 1. Enter an IP address for the LAN card: a. For the IP address, enter the administrative IP address provided by the customer network administrator. b. Use a subnet mask value of 255.255.255.0 unless otherwise instructed by the network administrator. c. Do not enter a value for the default gateway. 2. 3. 4. 5. 8–10 Connecting to external equipment Click the DNS tab and enter the IP address provided by the customer network administrator for the DNS server.
8.5 Enabling alarm paging The AIReach OS can be configured to page the system operator when a critical or major alarm occurs. To enable alarm paging, you must: • Install an external modem. • Configure the operator’s pager information in the AIReach OS. Alarm paging also requires HipLink Lite software, which is factory–installed on the System Controller. Instructions for installing the external modem and configuring the pager information are given below.
Configuring the AIReach OS for alarm paging Configure the AIReach OS with the operator’s pager, mobile phone, or beeper information, as explained below. (The HipLink software must already be installed.) Notes If the AIReach OS is configured to direct alarm pages to a mobile phone on the AIReach OS, the mobile phone may not receive an alarm page in the event of an outage. If you need assistance using HipLink, call the Cross Communi– cations support hotline at (630) 964–4282.
4. Uncomment (remove “ # ” from) the appropriate lines in ArosPageInfo.
Table 8-1 Supported alphanumeric service providers Provider/service name MobileMedia 800 B MM800B MobileMedia 804 MM_804 MobileMedia 817 MM_817 Nextel 312 NXT312 Nextel 415 NXT415 Nextel 510 NXT510 Nextel 630 NXT630 Nextel 708 NXT708 Nextel 847 NXT847 Nextel 847–344 NEXTEL PacBell 415 PAC415 PageBridge 407 PBR407 PageMart 800 PMR800 PageNet Nationwide 800 PAGENE Page New England 800 PNE800 Page New York 716 PNY716 PageNet 404 PNT404 PageNet 408 PNT408 PageNet 415 PNT415
Table 8-1 Supported alphanumeric service providers Provider/service name Provider ID TNI Paging 800 TNI800 Touch Tel Paging 510 TTP510 US West 520 USW520 Westlink Paging 602 WLP602 Westlink Paging 801 WLP801 1 For SKYTEL alphanumeric users who have a pin number instead of an 800 number, the dialup number will be 1–800–679–2778. (See Creating a new provider ID below.
Sample entries for numeric pager with phone number 888–886–3647 and PIN number 348593: pagingEnabled yes pagerType numeric serviceNumber 18888863647 pin 348593 Sample entries for beeper with beeper number 703–580–2077: pagingEnabled yes pagerType beeper beeperNumber 17035802077 Creating a new provider ID If the customer’s paging provider or service is not listed in Table 8-1 , follow the procedure illustrated below to create a new provider ID.
Chapter 9 System testing This chapter addresses the following tasks: • Testing RF coverage – page 9–1 • Conducting performance tests – page 9–2 Verify operational performance by completing the Performance Test Checklist referred to in Section 9.2. This verification is the final step in commissioning the AIReach OS. 9.1 Testing RF coverage 1026209– 0001 Revision B Using a test cell phone, perform a walk–through of the entire customer site to confirm AIReach OS RF coverage and record signal strengths: 1.
9.2 Performance testing To complete installation of the AIReach OS, conduct performance tests as follows: 1. 2. Obtain the Performance Test Checklist from your AIReach OS Program Manager. Complete this checklist by performing each listed test and checking the associated box after each test is successfully completed. Note A customer representative should witness the performance tests. 3. 4. 5. 6. 7. 8. Sign the completed checklist. Obtain the customer’s representative’s signature.
Chapter 10 Installation inspection This chapter briefly discusses the installation quality inspection. When all the initial AIReach Office subscribers have been entered into the Controller, complete the Installation Quality Assurance (QA) Inspection Checklist. Obtain this checklist from your AIReach OS Program Manager. Invite a customer representative to accompany the person performing the QA inspection.
Chapter 11 Provisioning This chapter explains the procedure for provisioning permanent subscribers. To provision temporary subscribers (visitors, for example), see page 4–20. 11.1 Provisioning permanent subscribers After the system has been installed and verified, provision the subscribers as follows: 1. 2. 3. 4. 5. 6. If not already connected to the system, click the Connect button in the Connect window to display the main AROSC Configuration window. Select Configure → NSS → HLR.
13. 14. Select the specified AROSC Name from the dropdown list. Enter each subscriber’s information, including LDN extension, MIN, and ESN. Then click Save. Note Observe the status bar above the option windows. If the status bar is red, a subscriber information error exists. Use the vertical scroll bar to display the error message. Before proceeding, review the message and correct the error. The software shows a Successful Load message when the subscriber information is entered correctly.
Chapter 12 Remote Client This chapter includes: • Overview of the AIReach OS Remote Client – page 12–1 • Explains how to install the Remote Client – page 12–2 • Explains how to test the installation – page 12–3 12.1 AIReach OS Remote Client The Remote Client can be installed on a Windows 95, Windows 98, or Windows NT computer to provide access from a remote location to the AIReach OS.
12.2 Installing the Remote Client Windows 95 or Windows 98 12–2 Remote Client Follow these steps to install the Remote Client on a remote computer: 1. Load the AIReach OS software CD into the computer’s CD drive. 2. Using the Windows Explorer, find the folder called GUIInst, and double–click to open it. 3. Double–click on the setup.exe file. This starts the InstallShield. 4. Read the instruction file displayed by the InstallShield; follow the on–screen instructions; and respond to the questions.
3. 4. Change the Initial Environment value from the default setting to 2048. Click OK. 12.3 Testing the Remote Client Make sure the Remote Client connects to the Controller: The instructions below are for Windows 95, Windows 98, or Windows NT . 1. At the remote computer, double–click the AROS Configuration icon: The software displays the AIReach Office banner and a Login dialog box. 2.
Chapter 13 Troubleshooting 13.1 This chapter includes information for troubleshooting a newly installed AIReach OS; it does not address troubleshooting for routine (post–installation) operation. It addresses: • Controller problems – page 13–1 • Picocell problems – page 13–2 • General operational problems – page 13–6 • Picocell alarms – page 13–8 Controller problems Problems with System Controller cards Make sure the card is properly seated in the Controller backplane socket.
Indications that a T1 trunk is good are: Alarms: NONE Frame sync: OK 2. 3. Press F3 or Esc to exit. At the DOS prompt, enter Exit to close the Command Prompt window. 13.2 Picocell problems (See also Section 13.4, Picocell alarms.
3. In the “Ethernet adapter TXn0002” section of the configuration screen, make sure the correct IP addresses are displayed for the picocells to be installed in the system. An IP address must be listed for each picocell, in sequential order, as illustrated below: Picocell 1 2 3 4 . . IP Address 69.1.1.254 69.1.2.254 69.1.3.254 69.1.4.254 . . Notes When a picocell boots up, it is assigned the next available IP address. Only picocell IP addresses are assigned to the TX2000 IP card.
Adding picocell IP addresses You need to add picocell IP addresses only if the number of picocell addresses is incorrect, as explained in the previous section (Checking the IP addresses). Skip this section if the picocell IP addresses are configured correctly. If you need to add picocell IP addresses: 13–4 Troubleshooting 1. Select Start → Settings → Control Panel → Network → Protocols. This opens the Network window: 2. 3. Select TCP/IP → Properties → IP Address.
This opens the Microsoft TCP/IP Properties window: 4. 5. 1026209– 0001 Revision B The initial TXn000 IP address must be 69.1.1.254 with a Subnet Mask of 255.255.255.0. Leave the Default Gateway field blank. Click Advanced. This opens the Advanced IP Addressing window: Click Add under IP Addresses.
This opens the TCP/IP Address window: 6. Enter the appropriate picocell IP Address and Subnet Mask; then click Add. Picocell IP addresses are in the form: 69.1.X.254, where X is the next available number in sequence, that is, 2, 3, 4, 5 ... The Subnet Mask is always 255.255.255.0. Note The Add button is not activated until an IP Address is entered. 7. Repeat step 6 until a picocell IP address and subnet mask is entered for all the picocells installed in the system. 13.
Phones do not lock or register If the phones do not lock or register, check: • The phone programming • The subscriber entries on the provisioning screens • The DCCH configuration Mobile phones cannot contact each other If two mobile phones cannot call each other, check: • The PBX connection LED on the rear of the System Controller. • That the PBX administrator has activated the T1 and entered the phantom numbers correctly. • That all cells are listed under MSC Configuration, BSC Configuration.
13.4 Picocell alarms Table 13-1 describes the alarm codes from the picocell. There are four categories of picocell alarms: • • • • Critical – BTS requires service immediately Major – Major performance or capacity loss Minor – Minor performance or capacity loss Info – Informational alarm When critical or major alarms occur, the Alarm LED on the picocell front panel is red. When a minor alarm occurs, the Alarm LED is orange.
Table 13-1 Picocell alarms Name Alarm Severity Meaning WBSU Rebooting 2180 Info WBSU has been rebooted Perform WBSU startup procedures WBSU Restart 2181 Info WBSU has been warm booted Perform WBSU startup procedures Get Time–of–day Failed 2185 Minor WBSU could not contact WOSC time server to get time–of–day Check IP address of time server CPU Busy 2188 Info CPU idle time < 5% CPU Available 2189 Info CPU idle time > 5% Master Oscillator Failed 218A Critical Master oscillator f
Chapter 14 Maintaining Quad T1 cards This chapter includes the following topics: • Replacing a Quad T1 card – page 14–2 • Moving a Quad T1 card – page 14–5 • Removing (deleting) a Quad T1 card – page 14–9 To add a Quad T1 card, see Sections 2.4 through 2.8. The instructions in this chapter are not part of the initial installation procedure. They are provided in case you need to replace, move, or remove a Quad T1 card.
14.1 Replacing a Quad T1 card in the same slot To replace a Quad T1 card in the same slot, follow these steps: Note When you replace a Quad T1 card in the same slot, do not make any software configuration changes. Shut down the Controller: Click Start → Shutdown, select Shut down the computer?, and click Yes. After you see the message indicating that it’s OK to turn off power to the computer, turn off the Controller power switch. Remove the Controller cover (as explained on page 2–11).
11. If the removed card was the first in a chain of Quad T1 cards, an MVIP–to–H.100 bus adapter card is attached at the top of the Quad T1 card (Figure 14-1): Unscrew the bus adapter card (or use a new bus adapter card) and connect it to the new Quad T1 card, as shown in Figure 14-2. The bus adapter card must be secure and in full contact with the Quad T1 card. 2. Secure adapter card with No. 4 screw into Quad T1 card MVIP bus connector 1. Insert bus adapter connection into Quad T1 card H.
18. 19. 20. Turn the power switch on and wait for the Controller to boot up. After you log in, make sure all AIReach OS software application buttons are displayed on the Windows NT desktop (taskbar buttons here are shown vertically stacked): The taskbar may show other applications in addition to those shown here. If any applications are missing, contact your HNS Installation Manager.
14.2 Moving or replacing a Quad T1 card to a different slot If you are moving a Quad T1 card to a different slot or replacing a Quad T1 card to a different slot (original card removed from slot x, but replacement installed in slot y), follow the steps below (Physical steps and Configuring the card): Moving a Quad T1 card is not recommended, because it may result in a configuration mismatch. However, if a chassis slot is malfunctioning or is suspected of malfunctioning, you might want to move a card.
13. 14. 15. 16. 17. 18. 19. Configuring the card If the removed card was the first in a chain of Quad T1 cards, an MVIP–to–H.100 bus adapter card is attached at the top of the card (Figure 14-1): If the card will no longer be the first one in the chain or the card is being replaced, unscrew the bus adapter card (or use a new bus adapter card) and connect it to the Quad T1 card that will be the first in the chain. See Figure 14-2.
5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 1026209– 0001 Revision B Click on the BTSs tab of the BTS Configuration window. This window lists all configured BTSs. Move any BTSs configured on the Card Number of the old card (original card or original card location) to a different card number. At this point, the BTSs may be configured on the same card and port as another BTS. To move a BTS: a. Click on the BTS and then click Modify. b.
Configuring the T1 Quad card 1. Launch the AROSHWCfg utility by double–clicking on the AROSHWCf . . . (hardware configuration) icon: 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 14–8 Maintaining Quad T1 card Stop all AROS processes: Click Shutdown AROS and then click Yes when prompted, “Do you really want to quit?” The AROSHWCfg window lists the Quad T1 boards. In the AROSHWCfg window, select the card that has been moved by clicking on the PC slot number; then click Delete to remove the card.
14.3 Removing (deleting) a Quad T1 card If you are removing—and not replacing—a Quad T1 card (deleting the card), follow the instructions in this section. When you remove and do not replace a Quad T1 card, remove the last card added. If you need to delete a different card (not the last added), you must: 1. Delete the last card added. 2. Move the card to be deleted to the position where the last card was located. For example, a system has Quad T1 cards in slots 4, 6, and 8.
7. 8. 9. 10. 11. Physically removing the card To remove the card from the chassis: 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14–10 Maintaining Quad T1 card The AROSHWCfg window lists the Quad T1 boards. In the AROSHWCfg window, select the card with the same PC slot number as the card previously deleted; then click Delete to remove the card. Click OK to exit the AROSHWCfg utility. Shut down the Controller: Click Start → Shutdown, select Shut down the computer?, and click Yes.
Appendix A Equipment specifications This appendix lists preliminary specifications for the AIReach OS equipment: • System Controller specifications – page A–1 • Picocell specifications – page A–4 • Picocell power supply specifications – page A–6 All specifications in this appendix are preliminary and are subject to change. A.1 System Controller specifications Security Mechanical The AIReach OS System Controller provides the mobile switching functionality.
Electrical The System Controller requires a standard electrical outlet (NEMA 15P) located within 6 feet. The power supply provides power only to the System Controller. When battery backup is required, a UPS (uninterruptable power source) unit is necessary. The ac input connects to a single phase, two–wire service. This interface occurs through a standard IEC 320 style connector. The power cord is of a double reinforced insulation design as required by safety agencies.
Environmental Table A-1 The environmental specifications for the System Controller are consistent with indoor commercial electronic communication products.
Table A-1 System Controller environmental specifications Preliminary specifications – subject to change Operational Seismic Vibration 0.3 0.6 2.0 5.0 15.0 50.0 Altitude Non–operational (packaged) (per NEBS, Zone 4 upper floors requirement) Frequency (Hz) Shock Non–operational (unpackaged) Accel (g) 0.2 2.0 5.0 5.0 1.6 1.
Shipping size • Height: • Width: • Depth: Electrical The picocell is line powered using the T1 cable. The picocell operates over an input dc voltage range of –24 to –54 volts. For dc power, the maximum power draw of the picocell does not exceed 50 watts. Environmental specifications Table A-2 The environmental specifications for the picocell are consistent with indoor commercial electronic communication products.
RF levels A.3 Picocell power supply Maximum RF power output (Equivalent Radiated Power) for the 100 mW radio option of the Pico BTS is ±20 dBm with +1/–3 dB accuracy. The BTS has a nominal dynamic range of at least 26 dB (from ±20 dBm to –6 dBm), adjustable in steps of 1 dB. For the 10 mW radio option, maximum RF power output (Equivalent Radiated Power) of the Pico BTS is +10 dBm with +1/–3 dB accuracy.
Appendix B Standards compliance information This appendix lists standards compliance information for the AIReach OS components: • • • • • FCC compliance – page B–1 Picocell regulatory compliance – page B–2 System Controller regulatory compliance – page B–3 Picocell power supply compliance – page B–4 Other compliance – page B–4 B.
B.2 Picocell regulatory compliance Type acceptance FCC Part 22 and 24, Personal Communications Services, October 1, 1997. Part 22 – Cellular band. Part 24 – PCS band.
B.3 System Controller regulatory compliance CSA C22.2 No.
B.4 Picocell power supply compliance CE compliant CSA950 Complies with EMC Directives In Case IEC320 with ground TUV/IEC950 UL1950 B.5 Other compliance AWS Wireless Office Service System Specification, Document WOS–97–01, Rev 1.0 The BTS complies with the latest revision of TIA/EIA/IS–136.1A and TIA/EIA/IS–136.2A.
Appendix C Equipment part numbers This appendix lists part numbers for major components of the AIReach OS: • Customer documentation – page C–1 • Component part numbers – page C–1 C.1 Customer documentation For document numbers for AIReach OS customer documents, see the About section of this manual. C.2 Component part numbers Table C-1 lists the major components of the AIReach OS, field replaceable units (FRUs), parts needed for installation, and their part numbers.
Table C-1 Major AIReach OS components, FRUs, and installation parts HNS part number Component Picocells and picocell components Picocell base transceiver station (BTS) 1026426–00xx Multiple types: 800 or 1900 MHz; 100 mW or 10 mW; T1 or E1. 1 scanner no radios; 2 radios with vocoder no scanner; 2 radios (no vocoder) no scanner; Controller (no radios or scanners); radio spares with vocoder.
Table C-1 Major AIReach OS components, FRUs, and installation parts Component HNS part number Other options Contact your AIReach OS Program Manager for information on the following additional options: Monitor enclosure options UPS and power distribution options Rack frame and frame mounting components options Rack cable routing options Rack frame bracing options (for ceiling or cable ladder) Rack extenders (7–inch) Router options CSU options 1026209– 0001 Revision B Equipment part numbers C–3
Appendix D Updating software; backing up databases This chapter includes the following topics: • Updating software – page D–1 • Backing up and restoring databases – page D–2 D.1 Updating software with a new release A new software release could be a release of the AIReach Office application software, an OMC release, or both. Install the new release during non–business hours. AIReach Office functions are not available during this time. To install a new release of AIReach software: 1. 2. 3. 4.
D.2 Backing up and restoring databases To safeguard system data, create regular backups of all databases created and maintained by the AIReach Office software. Databases may be restored to the Controller hard disk, if necessary. All AROS software applications are stopped during backup or restore operations. Any calls in progress are dropped, and no new calls can be made until the Controller restarts.
Restoring To restore the databases from a CD to the Controller hard disk: 1. Enter these commands from a DOS prompt: cd %omc_root_dir%\tools cleanupdb 2. The cleanupdb script closes all AROS processes and cleans the databases. After some time, the Controller reboots itself, but no AROS services start. After the Controller reboots, enter: cd %omc_root_dir%\tools restore 3. 1026209– 0001 Revision B The Controller reboots again.
Index A AIReach Office application banner window, 2–28 launching, 2–28, 4–2 T1, picocells, 7–11, 7–16 wiring flip, 7–16 Applications (list of AIReach OS applications), 2–27 Cards (Controller) adding, 2–11 configuring, 2–25 DIP switch settings, 2–13 fully loaded configuration, 2–10 jumper settings, 2–13 slot assignments, 2–9 standard configuration, 2–1, 2–9 types, 1–6 verifying configuration, 2–27, 4–4 AROS Configuration icon, 2–28 Cell Configuration window, 4–12 AROSC Configuration window, 2–29, 4–3
checking operation, 3–6 compliance information, B–3 components, 1–3, 1–6 part numbers, C–1 configuring cards, 2–25 gateway access, 5–7 description, 1–1, 1–6 dimensions, A–1 front panel illustration, 1–5 installing, 3–2 mounting options, 1–3 operating mode, 6–16 operating system, 1–2 PBX connections, 8–2 power indicator, 3–6 power requirements, 3–6 rack mounting, 3–4 setup mode, 6–10 slots card assigned to each slot, 2–9 identification, 2–8 numbering, 2–8 types, 2–8 troubleshooting, 13–1 unpacking, 2–2 verif
J Jumper settings, Controller cards, 2–13 O OMC software, description, 4–2 Operating mode, 6–16 L Optional equipment, C–3 Organization of this manual, xi LAN cards, 2–19 driver, 8–9 installing a second LAN card, 8–9 IP address, 8–10 P Pagers, configuration to receive alarms, 8–12 Launching the AIReach Office application, 2–28, 4–2 Part numbers, C–1 LDN (local directory number), 4–22, 11–2 PBX connections, 8–2 checking, 14–4 LEDs picocells, 6–5, 7–17 illustrated, 13–8 Quad T1 cards, 6–6 illustrated
serial numbers, 2–7, 4–15 slots, numbering, 6–24 specifications, A–4 electrical, A–5 environmental, A–5 RF levels, A–6 weight, A–4 T1 wiring, 7–16 testing, 6–1, 6–17, 6–24 transceivers, 1–7 troubleshooting, 13–2 unpacking, 2–4 wiring flip, 7–16 pinouts, 7–17 Pin assignments T1 cable for picocells, 7–8 wiring flip, 7–17 Pinging the gateway, 5–8 Quality inspection of installation, 10–1 R Rack mounting Controller, 3–4 illustrated, 1–4, 3–3 Registering test mobile phones, 6–23 Remote access.
Standards compliance, FCC, B–1 Tools required for installation, 1–11 Standards compliance information, B–1 Traffic picocells. See Picocells Subscriber Provisioning window, 6–20 Transceivers (picocell), 1–7 testing, 6–24 Subscribers, provisioning, 11–1 System block diagram, 1–2 configuration options, 1–12 testing, 9–1 System Controller.
