Hughes Network Systems PICO-1900 1900 MHz Indoor Cellular Base Station User Manual

Hughes Network Systems 1900 MHz Indoor Cellular Base Station

EXB 10

11717 Exploration Lane, Germantown, MD 20876Tel: (301) 428–5500 Fax: (301) 428–1868/2830 1026209–0001Revision BFebruary 24, 2000Installation and Commissioning Manual
1026209–0001 Revision BiiCopyright E1999–2000 Hughes Network Systems, a Hughes Electronics Corporation companyAll rights reserved. This publication and its contents are proprietary to Hughes NetworkSystems, a Hughes Electronics Corporation company. No part of this publication may bereproduced in any form or by any means without the written permission of Hughes NetworkSystems, 11717 Exploration Lane, Germantown, Maryland 20876.Hughes Network Systems has made every effort to ensure the correctness and completenessof the material in this document. Hughes Network Systems shall not be liable for errorscontained herein. The information in this document is subject to change without notice.Hughes Network Systems makes no warranty of any kind with regard to this material,including, but not limited to, the implied warranties of merchantability and fitness for aparticular purpose.TrademarksAIReach is a trademark of Hughes Network Systems. Other trademarks, marks, names, orproduct names referenced in this publication are the property of their respective owners, andHughes Network Systems neither endorses nor otherwise sponsors any such products orservices referred to herein.
1026209–0001 Revision B iiiRevision recordRevision Date of issue ScopeANovember 8, 1999 Initial releaseBFebruary 24, 2000 Added instructions for several additionalprocedures; minor revisions throughout.
1026209–0001 Revision Biv
1026209–0001 Revision B vContentsAbout this manual xi. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Important safety information xv. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Introduction 1–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1 System components 1–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2 System Controller 1–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware 1–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software 1–6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3 Picocell components 1–7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4 Procedural flow chart 1–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.5 Tools and materials 1–11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Required tools 1–11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended tools 1–11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Required materials 1–12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Other requirements 1–12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.6 Configuration options 1–12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Adding cards to the System Controller 2–1. . . . . . . . . . . . . . . . . . . . . 2.1 Unpacking the picocells 2–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2 System Controller card configurations 2–8. . . . . . . . . . . . . . . . . . . . . . . Backplane slot identification 2–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . Standard (factory) configuration 2–9. . . . . . . . . . . . . . . . . . . . . . . . . Fully loaded configuration 2–10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3 Adding cards to the System Controller (first steps) 2–11. . . . . . . . . . . . . 2.4 Jumper and DIP switch settings 2–13. . . . . . . . . . . . . . . . . . . . . . . . . . . . Quad T1 card 2–13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TX2000 IP and TX2000 SS7 cards 2–15. . . . . . . . . . . . . . . . . . . . . . . Conference card 2–18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LAN cards 2–19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modem card 2–19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Single board computer (SBC) 2–20. . . . . . . . . . . . . . . . . . . . . . . . . . . 2.5 Attaching the bus cables 2–23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.6 Adding cards to the System Controller (final steps) 2–24. . . . . . . . . . . . . 2.7 Configuring System Controller cards 2–25. . . . . . . . . . . . . . . . . . . . . . . . Specifying basic card information 2–25. . . . . . . . . . . . . . . . . . . . . . . . 2.8 Verifying the card configuration 2–27. . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding a Quad T1 card 2–30. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding a TX2000 or conference card 2–31. . . . . . . . . . . . . . . . . . . . .
1026209–0001 Revision Bvi3 Installing the Controller 3–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1 Rack–mount configuration 3–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2 Mounting the Controller chassis 3–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3 Controller cabling 3–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4 Checking System Controller operation 3–6. . . . . . . . . . . . . . . . . . . . . . . 3.5 System cabling 3–7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Verifying the System Controller configuration 4–1. . . . . . . . . . . . . . . 4.1 Data required 4–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2 Verifying the System Controller configuration 4–2. . . . . . . . . . . . . . . . . Verifying the site information 4–2. . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying the card information 4–4. . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying the Network data information 4–9. . . . . . . . . . . . . . . . . . . Verifying the Cell information 4–12. . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying the BTS information 4–14. . . . . . . . . . . . . . . . . . . . . . . . . . Verifying the systemwide configuration 4–17. . . . . . . . . . . . . . . . . . . Verifying the MSC configuration 4–19. . . . . . . . . . . . . . . . . . . . . . . . . Configuring the HLR 4–21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Configuring the router 5–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1 Installing the router 5–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.2 Configuring the router 5–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Router configuration example 5–5. . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3 Gateway access 5–7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Testing picocells 6–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.1 Connecting a picocell for testing 6–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . Providing power to the picocell 6–4. . . . . . . . . . . . . . . . . . . . . . . . . . 6.2 Verifying software load 6–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.3 Checking scanning picocell operation 6–6. . . . . . . . . . . . . . . . . . . . . . . . 6.4 Performing a test frequency band scan 6–10. . . . . . . . . . . . . . . . . . . . . . . Switching to Setup mode 6–10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up the frequency band scan 6–11. . . . . . . . . . . . . . . . . . . . . . . Starting the scan and observing the results 6–13. . . . . . . . . . . . . . . . . 6.5 Checking traffic picocell operation 6–17. . . . . . . . . . . . . . . . . . . . . . . . . . 6.6 Provisioning test mobile phones 6–20. . . . . . . . . . . . . . . . . . . . . . . . . . . . Subscriber provisioning 6–20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.7 Programming test mobile phones 6–22. . . . . . . . . . . . . . . . . . . . . . . . . . . 6.8 Registering test mobile phones 6–23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.9 Placing test calls 6–24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . First transceiver test 6–24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Testing the remaining transceivers 6–25. . . . . . . . . . . . . . . . . . . . . . . . 6.10 Additional phone programming procedures 6–26. . . . . . . . . . . . . . . . . . . Home system ID 6–26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Home SOC 6–26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PSID/RSID number 6–26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System ID number 6–26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operator Code (SOC) 6–27. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1026209–0001 Revision B viiNAM status 6–27. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Initializing settings 6–28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Installing picocells 7–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1 Preparing for picocell installation 7–1. . . . . . . . . . . . . . . . . . . . . . . . . . . 7.2 Mounting the picocells 7–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the mounting plate 7–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.3 Installing and connecting picocells 7–7. . . . . . . . . . . . . . . . . . . . . . . . . . Warnings and cautions 7–7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Picocell connections 7–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mounting the picocell 7–12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . T1 wiring and flip 7–16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Check for proper operation 7–17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.4 Performing the frequency band scan 7–18. . . . . . . . . . . . . . . . . . . . . . . . . 8 Connecting to external equipment 8–1. . . . . . . . . . . . . . . . . . . . . . . . 8.1 Connecting the Controller to the PBX 8–2. . . . . . . . . . . . . . . . . . . . . . . 8.2 Installing the SSL certificate 8–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating the request file 8–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Requesting the certificate 8–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Completing the certificate 8–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the certificate 8–7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.3 Repointing the HLR 8–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.4 Installing a second LAN card and driver (optional) 8–9. . . . . . . . . . . . . Installing the LAN card 8–9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the LAN card driver 8–9. . . . . . . . . . . . . . . . . . . . . . . . . . . 8.5 Enabling alarm paging 8–11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the external modem 8–11. . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the AIReach OS for alarm paging 8–12. . . . . . . . . . . . . . 9 System testing 9–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.1 Testing RF coverage 9–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.2 Performance testing 9–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Installation inspection 10–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Provisioning 11–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1 Provisioning permanent subscribers 11–1. . . . . . . . . . . . . . . . . . . . . . . . . 12 Remote Client 12–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1 AIReach OS Remote Client 12–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Requirements 12–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2 Installing the Remote Client 12–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Windows 95 or Windows 98 12–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.3 Testing the Remote Client 12–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1026209–0001 Revision Bviii13 Troubleshooting 13–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.1 Controller problems 13–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.2 Picocell problems 13–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the IP addresses 13–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding picocell IP addresses 13–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.3 General operational problems 13–6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.4 Picocell alarms 13–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Maintaining Quad T1 cards 14–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.1 Replacing a Quad T1 card in the same slot 14–2. . . . . . . . . . . . . . . . . . . . 14.2 Moving or replacing a Quad T1 card to a different slot 14–5. . . . . . . . . . Physical steps 14–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the card 14–6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.3 Removing (deleting) a Quad T1 card 14–9. . . . . . . . . . . . . . . . . . . . . . . . Deleting the card from the configuration 14–9. . . . . . . . . . . . . . . . . . . Physically removing the card 14–10. . . . . . . . . . . . . . . . . . . . . . . . . . . . A Equipment specifications A–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.4 System Controller specifications A–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . Security A–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mechanical A–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Electrical A–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Environmental A–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Acoustics A–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.1 Picocell specifications A–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Security A–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mechanical A–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Electrical A–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Environmental specifications A–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . RF levels A–6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.2 Picocell power supply A–6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B Standards compliance information B–1. . . . . . . . . . . . . . . . . . . . . . . . B.1 FCC compliance B–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.2 Picocell regulatory compliance B–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.3 System Controller regulatory compliance B–3. . . . . . . . . . . . . . . . . . . . . B.4 Picocell power supply compliance B–4. . . . . . . . . . . . . . . . . . . . . . . . . . B.5 Other compliance B–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C Equipment part numbers C–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C.1 Customer documentation C–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C.2 Component part numbers C–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D Updating software; backing up databases D–1. . . . . . . . . . . . . . . . . . . D.1 Updating software with a new release D–1. . . . . . . . . . . . . . . . . . . . . . . . D.2 Backing up and restoring databases D–2. . . . . . . . . . . . . . . . . . . . . . . . . Backing up D–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restoring D–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index Follows Appendix D. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1026209–0001 Revision B ixFigures1-1 System Controller 1–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 AIReach OS block diagram 1–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 Example of full rack mount 1–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4 System Controller front panel 1–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5 Flow chart: AIReach OS major installation and test tasks 1–9. . . . . . . . . 2-1 Unpacking the System Controller 2–3. . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 Unpacking the picocell 2–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3 Unlocking the mounting plate from the picocell 2–6. . . . . . . . . . . . . . . . 2-4 Recording and entering serial number from each picocell 2–7. . . . . . . . . 2-5 Slot label on rear of System Controller 2–8. . . . . . . . . . . . . . . . . . . . . . . 2-6 Slot assignments: System Controller standard configuration 2–9. . . . . . . 2-7 Slot assignments: System Controller fully loaded configuration 2–10. . . . 2-8 Removing the System Controller cover 2–11. . . . . . . . . . . . . . . . . . . . . . . 2-9 DIP switches on Quad T1 card 2–13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10 H.100 bus termination 2–14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11 Jumpers and address switch on TX2000 cards 2–15. . . . . . . . . . . . . . . . . 2-12 Conference card jumpers and address switch 2–18. . . . . . . . . . . . . . . . . . 2-15 SBC jumper and DIP switch locations 2–20. . . . . . . . . . . . . . . . . . . . . . . 2-16 H.100 and MVIP bus cables 2–23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 System Controller and associated components in a 19–inch rack 3–3. . . 3-2 Installing the chassis 3–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3 System Controller connectors 3–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 Recording and entering serial number from the picocell 4–15. . . . . . . . . . 5-1 AIReach OS IS–41 gateway network diagram 5–2. . . . . . . . . . . . . . . . . . 5-2 Typical AIReach OS IS–41 gateway network diagram 5–5. . . . . . . . . . . 6-1 Picocell connection for testing 6–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2 Ports on Quad T1 card 6–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3 LEDs on front of picocell 6–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4 LEDs on Quad T1 card 6–7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5 Picocell slot numbers 6–24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1 Placing the mounting plate to allow proper clearance 7–2. . . . . . . . . . . . 7-2 Position of the picocell on the mounting plate 7–3. . . . . . . . . . . . . . . . . . 7-3 Attaching the picocell mounting plate to wood or metal studs 7–5. . . . . 7-4 Attaching the picocell mounting plate – concrete, block, wallboard 7–6. 7-5 Cabling the picocell 7–9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6 T1 cable and power connections at the picocell 7–10. . . . . . . . . . . . . . . . . 7-7 T1 cabling for standalone and daisy–chained picocells 7–11. . . . . . . . . . . 7-8 Mounting the picocell 7–13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1026209–0001 Revision Bx7-9 Power terminal block connections 7–14. . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10 Picocell connections at the telco closet 7–15. . . . . . . . . . . . . . . . . . . . . . 7-11 T568B–compliant wiring flip at patch panel 7–16. . . . . . . . . . . . . . . . . . 7-12 T568B–compliant wiring flip using modular jack 7–17. . . . . . . . . . . . . . 8-1 Example of a signed SSL certificate 8–6. . . . . . . . . . . . . . . . . . . . . . . . . 13-1 LEDs on front of picocell 13–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1 H.100 and MVIP bus cables 14–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-2 MVIP bus adapter card 14–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tables2-1 Jumper settings for TX2000 IP and TX2000 SS7 cards 2–16. . . . . . . . . . 2-2 TX2000 card I/O address settings (switch S1) 2–17. . . . . . . . . . . . . . . . . 2-3 Conference card I/O address settings (switch S1) 2–19. . . . . . . . . . . . . . 2-5 SBC processor settings (switch SW1) 2–21. . . . . . . . . . . . . . . . . . . . . . . . 2-6 SBC card jumper settings 2–22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1 Approved mounting plate fasteners 7–4. . . . . . . . . . . . . . . . . . . . . . . . . 7-2 T1 (RJ–45) connector pinouts 7–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3 Power supply and CAT 5 wire colors 7–14. . . . . . . . . . . . . . . . . . . . . . . . 13-1 Picocell alarms 13–9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1 System Controller environmental specifications A–3. . . . . . . . . . . . . . . A-2 Picocell environmental specifications A–5. . . . . . . . . . . . . . . . . . . . . . . A-3 Power supply environmental specifications A–6. . . . . . . . . . . . . . . . . . . C-1 Major AIReach OS components, FRUs, and installation parts C–1. . . .
1026209–0001 Revision B About this manual xiAbout this manualThis manual provides instructions for installing andcommissioning the AIReach Office System (AIReach OS).This manual is written for installers responsible for installatingand commissioning the AIReach OS.This manual is divided into the following chapters and appendices:Chapter 1 – IntroductionChapter 2 – Adding cards to the System ControllerChapter 3 – Installing the ControllerChapter 4 –Verifying the System Controller configurationChapter 5 – Installing and Configuring the RouterChapter 6 – Testing picocellsChapter 7 – Installing picocellsChapter 8 – Connecting to external equipmentChapter 9 – System testingChapter 10 – Installation inspectionChapter 11 – ProvisioningChapter 12 – Remote accessChapter 13 – TroubleshootingChapter 14 – Maintaining Quad T1 cardsAppendix A – Equipment specificationsAppendix B – Standards compliance informationAppendix C – Equipment part numbersAppendix D – Updating software; backing up databasesThe instructions in this manual are organized according to tasks.The instructions are intended to be followed in the order in whichthey appear in the manual.ScopeAudienceOrganization
1026209–0001 Revision B xii About this manualThe AIReach Office documentation set for each user is listedbelow with the documentation number and description of themanual.All audiencesAIReach Office CD–ROM (1026207–0001)Contains PDF files of all documents for online viewing.Phone user audienceAIReach Office Mobile Phone Network Features Quick Guide(1027893–0001)Describes how to use each of the features of the AIReach OfficeSystem phone.Network administrator audienceSite Preparation Manual (1026208–0001)Describes the tasks required to prepare the site for the AIReachOffice System, including the System Controller and picocellspecifications.Getting Started (1027677–0001)Provides an introduction for using the system and its userinterface. Describes logging on and off, manipulating screens andmenus, navigating through the user interface and using Help areincluded in this manual. (Also applicable for the provideraudience).Network Administrator’s Guide (1027680–0001)Describes the regular scheduled and non–scheduled tasks thenetwork administrator performs. This manual includes directionsfor subscriber provisioning, software upgrade, backup, andoperator management and security. It also includes first–leveltroubleshooting instructions.Provider audienceInstallation and Commissioning Manual (1026209–0001)Describes how to install and commission the AIReach Officesystem, including: picocell installation, System Controllerhardware and software configuration, System Controllerinstallation, cabling the system, commissioning the system, andinstallation troubleshooting.Configuring the System (1027678–0001)Describes how to configure all of the elements that are a part ofthe system, including the system, System Controller, picocells,NSS/MSC, and BSCs.Monitoring System Performance, Troubleshooting, andAlarms (1027679–0001)Describes how to monitor the status of the system and itscomponents, and how to troubleshoot the system when problemsoccur. Also includes instructions for disaster recovery.AIReach Officedocumentation set
1026209–0001 Revision B About this manual xiiiThis manual is provided in Adobe Systems’ Portable DocumentFormat (PDF) for online viewing and searching. To successfullyprint the entire manual from the PDF file, and ensure optimumprint quality, you should use a Postscript printer and a computerwith ample free hard disk space or a network print queue. Onnon–Postscript printers, print a relatively small number of pages ata time. Try 30 pages—results will vary depending on printermemory, hard disk space, printer drivers, and other factors.The following conventions are used in the software instructionsincluded in this manual:Select means to click the mouse to make a choice, such as a menuselection. For example: Select Configure. Items you can select ona software screen are shown in bold type.To click or double–click, use the left mouse button unless the rightmouse button is specified.Select Configure → NSS → HLR means to make three selectionsconsecutively, as shown here:Click (3)Click (1)Click (2)T0001002Printing PDF filesConventions forsoftware instructions
1026209–0001 Revision B xiv About this manual
1026209–0001 Revision B Important safety information xvImportant safety informationFor your safety and protection, read this entire manual before youattempt to prepare the site for installation of the AIReach OfficeSystem Controller and picocells. In particular, read this safetysection carefully. Keep this safety information where you can referto it if necessary.This section introduces the various types of warnings used in thismanual to alert you to possible safety hazards.WARNINGWhere you see this alert symbol andWARNING heading, strictly follow thewarning instructions to avoid personalinjury.WARNINGFall hazard: Where you see this symbol andWARNING heading, strictly follow thewarning instructions to prevent personalinjury.WARNINGHeavy equipment hazard: Where you seethis symbol and WARNING heading, strictlyfollow the warning instructions to preventpersonal injury due to lifting heavyequipment.WARNINGPotential fire hazard: Where you see thissymbol and WARNING heading, strictlyfollow the warning instructions to preventpersonal injury or death due to fire.Types of warnings usedin this manual
1026209–0001 Revision B xvi Important safety informationThis manual includes the following safety warnings:WARNINGWhen installing the picocell on the mountingplate, use care to avoid falling and injuringyourself.WARNINGThe AIReach Office System Controller canweigh in excess of 50 pounds. To avoidpersonal injury or damage to equipment,follow these precautions:•Do not attempt to move or install theSystem Controller by yourself. Twopeople are required for these tasks.•If the System Controller will be rackmounted, secure the rack to the flooror wall so the rack cannot fall.WARNINGThe AIReach Office System Controller canweigh in excess of 50 pounds. To avoidpersonal injury or damage to equipment,follow these precautions:•Do not attempt to move or install theSystem Controller by yourself. Twopeople are required for these tasks.•Do not stack more than three SystemController boxes.Warnings used in thismanual
1026209–0001 Revision B Important safety information xviiWARNINGTo reduce the risk of fire, use only No. 24AWG or larger line cord to connect to thepicocell, and replace the fuse only with afuse of the type and rating identified on thefuse label.Failure to heed these warnings could resultin personal injury or death.
1026209–0001 Revision B Introduction 1–1 Chapter 1IntroductionThis 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–12The AIReach Office System (AIReach OS) is a wirelesscommunications system designed to provide in–building voicecommunications. The System is integrated with an existing hardwired PBX phone system.The AIReach OS is driven by an industrial computer thatprocesses cellular telephone calls. Operators use this computer, theSystem Controller, to configure, control, monitor, and troubleshootthe system.The System Controller has most of the functionality of largermacro cell Operation and Maintenance Centers (OMCs), includingBase Station Controllers (BSCs) and Mobile Switching Centers(MSCs). These functions run as applications under MicrosoftWindows NT on the System Controller, which is equipped withspecial cards to enable telephony support.Figure 1-1 System Controller1.1System components
1026209–0001 Revision B 1–2 IntroductionThe AIReach OS features:•A Windows NT based System Controller with a graphicaluser interface (GUI) for configuration, operation, andtroubleshooting•Up to 64 picocells (line powered)•A Primary Rate T1 connection from the Controller to thePBX•An IS–41 TCP/IP connection from the Controller to themacro cellular system•An optional LAN connection to a remote computer.ControllerAlarmprinterRemoteworkstationCorporateLAN56K leased linePatchpanelRouterDSUPBXPSTNIS-4IgatewayMACROPicocellPicocellPicocellCAT-5T1CAT-5T1CAT-5T1PicocellPicocellPicocell T1T1G-17007 F11/05/99Daisy-chainedpicocells10BaseTTCP/IP IS-41CAT-5 T1ISDN PRIFigure 1-2 AIReach OS block diagramThe System Controller is rack or table mounted in close proximityto the PBX.The picocells are small Base Transceiver Stations (BTSs) designedto be mounted on office walls throughout a building. They are linepowered and connected to the System Controller using CAT 5 T1cables.The OMC functions of the AIReach OS can be performed at aspecially configured (customer provided) remote computer. Thiscomputer can be located on an internal corporate LAN andprovide the network administrator with the ability to monitor andcontrol the system without having to be physically at the SystemController location.
1026209–0001 Revision B Introduction 1–3The System Controller consists of the following components:•A Windows NT computer with an internal floppy diskdrive, a read/write CD–ROM drive, a 20–slot backplane,and system software•Telephony cards to support the AIReach OS. (For acomplete description, see Chapter 5.)•A rack mounted 17–inch color monitor•A rack mounted keyboard with integrated touchpadThe standard (factory) configuration includes the SystemController with monitor and keyboard with integrated touchpad. Atelco rack is optional.There are three options for mounting the System Controller:•Desktop mount•Chassis slide mount•Full rack mount (illustrated in Figure 1-3)The Controller front panel has a power switch and indicators fordisk activity, CD–ROM read and write activity, and power supplystatus. The Controller keyboard connects to the rear panel orbehind the locking front access door.A remote computer, if used, connects to the System Controllerthrough a LAN or dial–up modem connection, using Windows NTRemote Access Server (RAS).1.2System ControllerHardware
1026209–0001 Revision B 1–4 IntroductionKeyboard withintegrated touchpadControllerG-14758 F11/04/99MonitorFigure 1-3 Example of full rack mountBoth the CD–ROM R/W (read/write) drive and a 3.5 inch floppydrive are accessible through a drop down panel on the front of theunit. Status indicators are provided on the front for fan,temperature, drive, and power. See Figure 1-4.
1026209–0001 Revision B Introduction 1–5Figure 1-4 System Controller front panelG-17022 F08/04/99Drive door openClosed and lockedDoorlockDrivedoor ReleasehandlesFANSTATUS TEMPSTATUS DRIVEACTIVITY -12 +12 -5 +5POWER SUPPLYPOWER ONStatus indicatorsFANSTATUS TEMPSTATUS DRIVEACTIVITY -12 +12 -5 +5POWER SUPPLYPOWER ONRelease handlesFilterdoorCD-ROMR/W drive3 1/2”floppydrive
1026209–0001 Revision B 1–6 IntroductionThe System Controller is configured with a subset of the followinghardware:•Hardware (cards): The cards that are installed in theSystem Controller are standard plug–in type CPU cards thatare ISA or PCI compatible. The System Controller has eightISA slots and nine PCI slots. The following cards areinstalled in the System Controller:- Quad T1 cards (1 minimum, 6 maximum) with four T1ports per card- TX2000 IP card (1)- Conference card (0, 1, or 2)- CD–ROM SCSI card (1)- 56K modem card (1)- Ethernet cards (1 or 2)-Optional: TX2000 SS7 card (1)•Hardware (System Controller components)- Keyboard with integrated touchpad- Passive backplane supporting 8 ISA, 9 PCI, andPICMG single board computers- 512 MB PC100 error correcting synchronous DRAM- 10/100BaseT PCI ethernet card- 56K V.90 X2 modem, ISA bus- 8.4 GB Ultra ATA hard drive (minimum, connected toIDE interface number 1)- 1.44 MB floppy drive- CD–RW drive with SCSI interface (2X write mode, 6Xread mode minimum, installed in ISA slot 7)- VGA monitor allowing a minimum of 640x480resolution (optional)- standard EIA 19 inch equipment chassisThe System Controller includes the following software:- Windows NT computer- Oracle database software- System Controller and OMC software on CD–ROM- Computer–based Training (CBT – available as aseparate CD–ROM)- Online PDF documentation (available as a separateCD–ROM)Software
1026209–0001 Revision B Introduction 1–7The picocell consists of a backplane covered by an externalhousing and contains the following internal components:•Master oscillator: Provides a reference frequency forpicocell signal timing.•Power supply: Converts the –48 Vdc input power to –6.5Vdc for internal picocell operation.•Transceivers: Each traffic picocell includes up to fourtransceivers, with each transceiver providing three full–rateTDMA channels. One channel is used as the digital controlchannel (DCCH) to provide access information to themobiles. The remaining full–rate channels are used asdigital traffic channels (DTC). Each picocell can handle 11mobile voice channels simultaneously, when fully loaded.Each mobile phone requires one voice channel.Transceivers are used only in traffic picocells.•Scanning receiver: This module is used in scanning ortraffic picocells to monitor the transmitter signal strength ofthe neighboring base stations. One scanner (maximum) isused per scanning picocell.•Picocell Controller: This module is the processor of thepicocell. It configures and controls the transceiversoperation using a proprietary protocol via the ST–BUS. ThePicocell controller uses one T1 slot to communicate withthe System Controller. The remaining slots are used toprovide bearer services.•Antenna and branching module: The transmit anddiversity receivers of the installed transceivers arecombined and split in this module. The picocell has a 360°omnidirectional radiation pattern in azimuth.•Locking tab, lock, and key: The lock and key secure thepicocell to the locking tab on the mounting plate.•Mounting plate: To ensure secure mounting, the installerattaches a mounting plate to the wall, and then mounts thepicocell to the mounting plate.1.3Picocellcomponents
1026209–0001 Revision B 1–8 IntroductionThe following flow chart (Figure 1-5 on page 1–9) shows thesequence of major tasks required for site preparation, installation,and commissioning of the AIReach OS.Test picocells at the System Controller site. Complete picocellcabling before you install the System Controller and test picocells.1.4Procedural flowchart
1026209–0001 Revision B Introduction 1–9Figure 1-5 Flow chart: AIReach OS major installation and test tasksShip DamagedEquipment to MaterialReturn Center (MRC)RescheduleInstallationSee next pageStartProvide Installation Packageto Implementation TeamVerify Contents ofInstallation PackageObtain MissingItemsShip AIReach OSEquipment toImplementation TeamVerify Contentsof Shipment(s)MissingItemsShip Replacement orMissing Equipment toImplementation TeamMRC Ships DamagedEquipment toAIReach OS VendorDeploy to Sitewith EquipmentConduct Pre-InstallationWalk-Through withCustomerDiscrepanciesSiteReadyAdditionalCardsInstall AdditionalCircuit CardsInstall ControllerEnter / VerifyControllerConfigurationTest ControllerPerformanceInstall andConfigure RouterConfigure Controllerfor Gateway AccessTemporarily ConnectScanning Picocellto ControllerInitiate 6 MinuteTest FrequencyBand ScanTemporarily ConnectEach Picocellto ControllerYesNoYesNoYes NoYesNoShip Failed ControllerComponent to MRCReceive ReplacementController Componentfrom MRCInstall ReplacementComponent intoControllerFailuresYesNoAB2/17/00T0001030
1026209–0001 Revision B 1–10 IntroductionLeave SiteNoVerify RF CoverageYesYesNoFinishSend QA Inspection &Operational PerformanceChecklists to AIReach OSInstallation ManagerNoShip Failed Picocellto MRCReceive ReplacementPicocell from MRCPermanently InstallScanning PicocellConnectController to PBXand Dial-up ModemInstall SSLCertificateDiscrepanciesCorrect IdentifiedDiscrepanciesPerform InstallationQA InspectionCorrect IdentifiedDiscrepanciesSend "As-Built"System ConfigurationReport toNetwork PlanningEnter Subscriber DataInto Controller(Provisioning)Provide On-SiteCustomer Trainingand SupportCustomer AcceptAIReach OSDiscrepanciesYesTest PicocellPerformancePicocellFailureBFrom previous page From previous page2/17/00T0001031AConductPerformance TestPermanently InstallTraffic PicocellsInitiate Frequency(24 Hour Minimum)Band ScanFigure 1-5 Flow chart: AIReach OS major installation and test tasks (Continued)
1026209–0001 Revision B Introduction 1–11To install and service the AIReach OS, you need the tools andmaterials listed below.The following tools are required to complete the AIReach OSinstallation:•Cell phones (2 – Nokia 6160 or 6161 for PCS and 800MHz; Nokia 6120 for 800 MHz only)•Punchdown block tool with BIX, 66 block, and 110 die•Step ladder (6 foot minimum, per team)•Level•Stud finder•Tone chaser/generator•Tape measure (10–foot minimum)•Crimp tool with RJ–45 die•Crimp tool with RJ–11 die•Multimeter•Hole saw•Wire stripper/cutter•Fish tape•Flashlight•Scissors•Flushcuts•Anti–static wrist strap•Power strip (multi–socket extension cord)•Common hand tools (screwdrivers, pliers, hammer)•Tool case/bagIn addition, the following tools are recommended:•Two–way radio (2 each)•Mini–Champ (or equivalent) signal strength measurement tool•Label maker (P–touch or equivalent)•Cordless drill (with bits)•Cable tester•Staple gun1.5Tools and materialsRequired toolsRecommended tools
1026209–0001 Revision B 1–12 IntroductionThe following materials are required:•Drywall screws•E–Z Anchor self–drilling drywall anchors (plastic), lightduty•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 andterminated with an RJ–45 connector on each end)•Cross–connect blocks (i.e. BIX, 66, 110 block)•Cable tiesA –48 Vdc power supply is required for testing picocells.Several options are available for system installation:•The picocells are line powered and use an ac–to–dc powersupply providing –48 Vdc.•The System Controller can be configured with up to six T1cards, each supporting four T1 lines to picocells.•A traffic picocell can be configured with one to fourtransceiver cards.•Picocells can be daisy–chained to one System Controller T1port or individually connected to a System Controller T1port.•The System Controller can be installed as:- Desktop mount- Chassis slide mount- Full rack mountRequired materialsOther requirements1.6Configurationoptions
1026209–0001 Revision B Adding cards to the System Controller 2–1 Chapter 2Adding cards to the System ControllerThis 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 card configuration – page 2–27The System Controller is shipped in a standard configuration withall software and the following standard cards installed (one ofeach):•Quad T1 card•TX2000 IP card•Conference card•LAN card•56K modem cardIf additional cards are required (typically to expand service), theyare installed and configured at the customer site.NoteThe System Controller’s hardware configuration is site–specificand is specified in the AIReach Office Configuration Report. Thisreport is prepared by the HNS Network Planning Department.
1026209–0001 Revision B 2–2 Adding cards to the System ControllerThe System Controller is delivered in three boxes containing:•System Controller (chassis)•Monitor•KeyboardThe optional rack, if ordered, is shipped in a separate container.Rack mounting the System Controller is recommended, but tablemounting is acceptable.Unpack the Controller as follows:1. Remove the System Controller and accessory packagesfrom the packing container as shown in Figure 2-1.Also refer to the unpacking instructions shipped with theController.2. Remove the monitor and keyboard from their respectiveboxes.3. Verify all parts against the enclosed packing lists. Visuallyinspect the components for damage.2.1Unpacking theSystem Controller
1026209–0001 Revision B Adding cards to the System Controller 2–3G-17197 F01/28/003. Lift unit out ofshipping containerController2. Remove packing1. Remove cardboard tray and accessoriesFigure 2-1 Unpacking the System Controller
1026209–0001 Revision B 2–4 Adding cards to the System ControllerAfter unpacking the Controller, unpack the picocells so you canrecord their serial numbers. Picocells are not installed until later(as explained in Chapter 7), but you need to record their serialnumbers so you can enter them when you verify the Controllerconfiguration (Chapter 4).Each picocell is packaged in a cardboard box. Unpack thepicocells using the following steps. See Figure 2-2.1. Open the box at the top. Note that the picocell is supportedin the box by two end caps made of form–fitted foampacking material.2. Remove the picocell and packing from the box as one piece.3. Remove both end caps from the picocell. Remove theplastic bag covering the picocell.Note that the mounting plate is mounted and locked tothe picocell.2.2Unpacking thepicocells
1026209–0001 Revision B Adding cards to the System Controller 2–5G-14759 F08/23/99Picocell withattached mounting plate1. Lift unit out ofshipping container2. Remove packingFigure 2-2 Unpacking the picocell
1026209–0001 Revision B 2–6 Adding cards to the System Controller4. Remove the lock key that is taped to the outside of thepicocell mounting plate.5. Use the key to unlock the picocell from the mounting plate.Insert the key and turn it clockwise to a vertical position tounlock the mounting plate, as shown in Figure 2-3.G-17891 F08/25/99123Figure 2-3 Unlocking the mounting plate from the picocell6. Remove the mounting plate from the picocell.
1026209–0001 Revision B Adding cards to the System Controller 2–77. Record the serial numbers of all the picocells, from the labelon the back of each picocell.Later you enter the picocell serial number as part of the basetransceiver station (BTS) configuration information for theController. For proper picocell operation, you must enterthe serial number exactly as it appears on the label—asindicated in figure 2-4.AVPU-D--02025234T0001001Include 1 dashthe revision letter.beforeInclude 2 dashesthe revision letter.afterPicocellrevision letterEnter all 8digits, includingleading zeros,as on the label.Serial numberFigure 2-4 Recording and entering the serialnumber from the back of each picocell8. Visually inspect all contents for damage.9. Save the boxes and packing material until the systemoperation is verified and the system is released to thecustomer. When packing materials are disposed of, recyclethe materials.
1026209–0001 Revision B 2–8 Adding cards to the System ControllerThis section shows:•How to identify the backplane slots of the SystemController•The standard and fully loaded Controller configurationsAs shown in Figures 2-5 and 2-6, each slot is identified in twoways:•By slot number: Slots are labeled 1 through 20 on the rearof the System Controller.•By ISA or PCI number (slot type ID): PCI 1–9, ISA 1–8.The slot type IDs are labeled on the inside of the Controller,on the backplane.Figure 2-5 Slot label on rear of System ControllerG-17011 F10/04/99 MODEM 56KSLOT 20Cards are installed in PCI or ISA slots, as listed below:PCI slots: Ethernet and T1 cardsISA slots: TX2000, conference, and modem cards2.3System Controllercard configurationsBackplane slotidentification
1026209–0001 Revision B Adding cards to the System Controller 2–9The following cards are installed in the System Controller at thefactory (one each):•TX2000 IP card•Quad T1 card•Conference card•LAN card•56K modem cardFor backplane slot assignments for each card, see Figure 2-6. Seealso Figure 2-7.PCI9PCI8PCI7PCI6PCI5PCI4PCI3PCI2PCI1ISA1ISA2ISA3ISA4ISA5ISA6ISA7ISA856K modemSpareSpareSpareTX2000 IPSpareSpareConf card 1SBCLAN 11Spares23456Quad T1Slot type IDG-17192 F 02/24/00PCI slotsISA slotsParallelport7(Not used)SpareSlotnumber 123 45 67891011121314 15 16 17 18 19 20Figure 2-6 Backplane slot assignments: System Controller standard configurationStandard (factory)configuration
1026209–0001 Revision B 2–10 Adding cards to the System ControllerA fully loaded System Controller has the backplane loaded asshown in Figure 2-7. In this configuration, four card slots areunused and available for future functions.Figure 2-7 Backplane slot assignments: System Controller fully loaded configurationPCI9PCI8PCI7PCI6PCI5PCI4PCI3PCI2PCI1ISA1ISA2ISA3ISA4ISA5ISA6ISA7ISA856K ModemSpareSpareSpareTX2000 IPTX2000 SS7Conf card 2Conf card 1ParallelportLAN 11LAN 2Notused 23456Quad T1 CardsG-17009 F 02/24/00PCI Slots ISA SlotsSlotnumber1234567891011121314 15 16 17 18 19 20Slottype IDSBCSpareFully loadedconfiguration
1026209–0001 Revision B Adding cards to the System Controller 2–11In addition to the factory–installed cards listed in Section 2.3, theSite 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 cardIf you need to replace, move, or remove a Quad T1 card seeChapter 14 for important instructions.To install a card in the System Controller, follow these steps:1. Make sure the Controller is powered off.2. Remove the Controller chassis cover, as follows:a. Loosen the five spring–loaded Phillips head screws atthe rear (top) of the chassis (Figure 2-8).b. Remove the chassis top cover by lifting the back edgeof the cover (approximately 1 inch) and then slidingthe cover toward the rear of the chassis.Use care to avoid damaging the copper finger stock underthe front of the cover.G-17193 F06/30/99Copper finger stock1. Loosen screws3. Slide cover back2. Lift cover upSpring loadedscrews (5)Figure 2-8 Removing the System Controller cover2.4Adding cards to theSystem Controller(first steps)
1026209–0001 Revision B 2–12 Adding cards to the System Controller3. Unpack the card.CAUTIONBefore removing or installing electroniccomponents, make sure static electricityhas been discharged from yourself and anyobject that may contact the component.Wear a new or recently tested anti–staticwrist strap and use an anti–static pad whilehandling components.Failure to follow these instructions couldresult in damage to components.4. Check all dual inline package (DIP) switch and jumpersettings. You may need to change some settings. SeeSection 2.5, Jumper and DIP switch settings.
1026209–0001 Revision B Adding cards to the System Controller 2–13This section specifies all jumper and DIP switch settings for allSystem Controller cards.Before adding or replacing any card in the System Controller,make sure all jumper switches and DIP switches on the newcard are set correctly. You may need to change some settings,and should check all jumpers and switches to make sure they areset correctly.Note that for Quad T1, TX2000, and conference cards, settings aredifferent depending on whether the card is the first of its typeinstalled, or is a subsequently installed card of the same type.The instructions below tell you which jumpers and DIP switchesyou need to change, and they specify the correct settings for alljumpers and switches (including those that do not need to bechanged). This is so you can check all settings and correct them ifnecessary.If you experience a problem with a card, make sure all jumpersand DIP switches are set as specified here before contacting HNSfor customer support.The jumper and switch settings indicated in the following sectionshave been established for the combination of cards used theAIReach System Controller. Do not use other settings.DIP switchesThe only option on the Quad T1 card is to set DIP switch S1(Figure 2-9) to enable or disable H.100 bus termination.1S2 ONOFF1S4 ONOFF1S5 ONOFF1S3 ONOFF1S1 OFFONDo not changethese switches.All S1 switches ON to terminate H.100 bus.All OFF for unterminated.T00010131S1 OFFONDetail, S1Figure 2-9 DIP switches on Quad T1 card2.5Jumper and DIPswitch settingsQuad T1 card
1026209–0001 Revision B 2–14 Adding cards to the System ControllerA Quad T1 card is factory installed in slot 9. When only one QuadT1 card is installed (or if the card is replaced), set all S1 switchesto ON (terminated). This is the default setting.If you add a Quad T1 card (in slots 4 through 8), the setting forswitch 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 theH.100 bus, set all S1 switches to ON (H.100 busterminated).•For cards that are not first or last on the H.100 bus, set allS1 switches to OFF (unterminated). See Figure 2-10.Termination reduces line noise caused by signal reflection off thetwo ends of the bus, and is critical for correct transmission ofreferenced T1 clock signals.Switches S2 through S5 are factory configured with the followingdefault settings: Sx–1 and Sx–5 ON, and all others OFF. Do notchange these settings. Switches S2 through S5 may be coveredwith an adhesive label.MVIP busIf the System Controller has two or more Quad T1 cards, theends of the MVIP bus should not be terminated. Remove jumpersJP14 and JP16 from the TX2000 IP card in slot 16 (the last cardon the MVIP bus).16H.100 bus cableMVIP bus cableEnabletermination(S1 ON)Disable termination(S1 OFF)T0001014TX2000 IPcardQuad T1 cards456789SlotEnabletermination(S1 ON)Figure 2-10 H.100 bus terminationSee alsoFigure 2-14.For additional explanation of the H.100 and MVIP buses, seeSection 2.6.IRQ and addressThe Quad T1 card interrupt request (IRQ) and address areautomatically configured through the BIOS. They are not userselectable.
1026209–0001 Revision B Adding cards to the System Controller 2–15This section applies to both the TX2000 IP card (factory installedin slot 16) and the TX2000 SS7 (optional, slot 15). Most settingsare the same for both cards; those that are different are clearlypointed out.The key settings to check on the TX2000 cards are the IRQ andI/O address. All jumpers other than JP7 (IRQ selection) should beleft in their factory default positions.JumpersMake sure the IRQ selection jumper is in position 7, as shown inFigure 2-11. (The factory default is IRQ 10. “NO” disables theISA bus.) Use IRQ 7 only.Figure 2-11 Jumpers and address switch on TX2000 IP and TX2000 SS7 cardsJP1JP9JP2JP16JP14S1IRQON131415161718Address for 0xD4000(ON, OFF, ON, OFF, ON, OFF, as shown)TX2000 IP:ON131415161718Address for TX2000 SS7: 0xD6000(OFF, OFF, ON, OFF, ON, OFF, as shown)TX2000 IP:TX2000 SS7:Connect JP14 pins and connect JP16 pins, as shown.connect these jumpers.DO NOTJP1: Connect twojumpers vertically.>832JP2: Connecttop pins.NO151412111097543Set to IRQ 7.JP9: Connectupper pins.T0001015 TX2000 IP andTX2000 SS7 cards
1026209–0001 Revision B 2–16 Adding cards to the System ControllerFigure 2-11 illustrates all the TX2000 jumpers. Table2-1 identifies the function of each jumper and summarizes thecorrect settings:Table 2-1 Jumper settings for TX2000 IP and TX2000 SS7 cards Use these settings.Jumper Function TX2000 IP TX2000 SS7IRQ Interrupt request(IRQ) signal IRQ 7 IRQ 7JP1 Boot type Both jumpers invertical position (fordual port RAM); seeFigure 2-11.Both jumpers invertical position (fordual port RAM); seeFigure 2-11.JP2 Boot device size >8 >8JP9 Shared interruptsbetween multipleTX2000 cards(enable/disable)Upper 2 pins (1–2)connected (enabled) Upper 2 pins (1–2)connected (enabled)JP14 MVIP bus terminator(enable/disable) Connected (jumperON) (terminated) 1Not connected (no jumper)JP16 MVIP bus terminator(enable/disable) Connected (jumperON) (terminated) 1Not connected(no jumper)1If multiple Quad T1 cards are used, remove this jumper. See MVIP bus onpage 2–14.As shown in Table 2-1 , all jumper settings are the same for bothcard types, except the MVIP bus termination jumpers, JP14 andJP16. For the TX2000 SS7 card, jumpers JP14 and JP16should not be connected under any circumstances. (Notconnected is the default setting for the TX2000 SS7 card.)I/O addressFor the TX2000 IP card, the I/O address selection (DIP switch S1)is factory set to 0xD4000. If you add a TX2000 SS7 card, set theTX2000 SS7 card address to OxD6000, as shown in Figure 2-11.To set DIP switch 1, set all switches up, to ON, then push theswitches down (OFF) for the positions marked with an underscore( __ ) in Table 2-2 . The addresses in Table 2-2 are provided fortroubleshooting purposes only. When installing a card, use onlythe address specified above.
1026209–0001 Revision B Adding cards to the System Controller 2–17Table 2-2 TX2000 card I/O address settings (switch S1) Address Setting Address Setting8000 13 14 15 16 17 18 C000 13 14 15 16 17 __8200 __ 14 15 16 17 18 C200 __ 14 15 16 17 __8400 13 __ 15 16 17 18 C400 13 __ 15 16 17 __8600 __ __ 15 16 17 18 C600 __ __ 15 16 17 __8800 13 14 __ 16 17 18 C800 13 14 __ 16 17 __8A00 __ 14 __ 16 17 18 CA00 __ 14 __ 16 17 __8C00 13 __ __ 16 17 18 CC00 13 __ __ 16 17 __8E00 __ __ __ 16 17 18 CE00 __ __ __ 16 17 __9000 13 14 15 __ 17 18 D000 13 14 15 __ 17 __9200 __ 14 15 __ 17 18 D200 __ 14 15 __ 17 __9400 13 __ 15 __ 17 18 D400 113 __ 15 __ 17 __9600 __ __ 15 __ 17 18 D600 2__ __ 15 __ 17 __9800 13 14 __ __ 17 18 D800 13 14 __ __ 17 __9A00 __ 14 __ __ 17 18 DA00 __ 14 __ __ 17 __9C00 13 __ __ __ 17 18 DC00 13 __ __ __ 17 __9E00 __ __ __ __ 17 18 DE00 __ __ __ __ 17 __A000 13 14 15 16 __ 18 E000 13 14 15 16 __ __A200 __ 14 15 16 __ 18 E200 __ 14 15 16 __ __A400 13 __ 15 16 __ 18 E400 13 __ 15 16 __ __A600 __ __ 15 16 __ 18 E600 __ __ 15 16 __ __A800 13 14 __ 16 __ 18 E800 13 14 __ 16 __ __AA00 __ 14 __ 16 __ 18 EA00 __ 14 __ 16 __ __AC00 13 __ __ 16 __ 18 EC00 13 __ __ 16 __ __AE00 __ __ __ 16 __ 18 EE00 __ __ __ 16 __ __B000 13 14 15 __ __ 18 F000 13 14 15 __ __ __B200 __ 14 15 __ __ 18 F200 __ 14 15 __ __ __B400 13 __ 15 __ __ 18 F400 13 __ 15 __ __ __B600 __ __ 15 __ __ 18 F600 __ __ 15 __ __ __B800 13 14 __ __ __ 18 F800 13 14 __ __ __ __BA00 __ 14 __ __ __ 18 FA00 __ 14 __ __ __ __BC00 13 __ __ __ __ 18 FC00 13 __ __ __ __ __BE00 __ __ __ __ __ 18 FE00 __ __ __ __ __ __1Default for TX2000 IP (slot 16). 2Use for TX2000 SS7 (slot 15).Note: Underline ( __ ) indicates switch in OFF position.
1026209–0001 Revision B 2–18 Adding cards to the System ControllerI/O addressI/O address 0x2140 is used for the first conference card (in slot13). If you install a second conference card (in slot 14), use DIPswitch S1 to select address 0x2160, as shown in Figure 2-12.T0001016JP3JP41S14ON14ON14ONLeave JP3and JP4unconnected(no jumpers).Address for :0x2140 all OFF)first conference card((slot 13)Address for (slot 14)second conference card :0x2160 (OFF, OFF, OFF, ON)Figure 2-12 Conference card jumpers and address switchFor troubleshooting purposes only, Table 2-3 shows all addressesthat can be assigned to a conference card. When installing a card,use only the address specified above.Jumpers (MVIP bus termination)For either conference card (in slot 13 or 14), leave jumpers JP3and JP4 unconnected. This disables MVIP bus termination for thecard.IRQThe conference card does not need an IRQ.Conference card
1026209–0001 Revision B Adding cards to the System Controller 2–19Table 2-3 Conference card I/O address settings (switch S1) Base addr S1–1 S1–2 S1–3 S1–40640 ON ON ON ON0620 ON ON ON OFF0560 ON ON OFF ON0540 ON ON OFF OFF0240 ON OFF ON ON0220 ON OFF ON OFF0160 ON OFF OFF ON0140 ON OFF OFF OFF2640 OFF ON ON ON2620 OFF ON ON OFF2560 OFF ON OFF ON2540 OFF ON OFF OFF2240 OFF OFF ON ON2220 OFF OFF ON OFF 2160 1OFF OFF OFF ON 2140 2OFF OFF OFF OFF1Use for second conference card (slot 14).2Default for first conference card (slot 13).The Ethernet LAN cards (slot 10, and slot 3 if a second LAN cardis used) are configured automatically through BIOS Plug and Play(PnP); they have no user selectable jumpers.The modem card (slot 20) is configured automatically throughBIOS Plug and Play (PnP); it has no user selectable jumpers. (Themodem uses COM2 and IRQ3.)LAN cardsModem card
1026209–0001 Revision B 2–20 Adding cards to the System ControllerIn the event of a problem with the SBC (slot 12), make sure DIPswitch SW1 is set correctly, depending on the installed CPU, andcheck all jumpers.Processor configurationThe standard CPU shipped with the AIReach OS SystemController is an Intel Pentium II, 450 MHz processor. Normally,the system BIOS autodetects the CPU and sets the system busfrequency accordingly. If the BIOS does not do this, or if you electto use a different processor, you must set DIP switch SW1 to thecorrect bus frequency and processor multiplier for the CPU, asspecified in table 2-4 . The location of switch SW1 is shown inFigure 2-13.Figure 2-13 SBC jumper and DIP switch locationsT0001019RearbracketDIMM memoryPentium II processor BatteryJP2 - CMOSoperationJP3 - Watchdogtimeout interruptJP4 - PnPand flashBIOSupgradeJ17 -WatchdogtimerDIP switch SW1As shown in Table 2-4 , switch SW1–1 selects the processor frontside bus frequency (FSB), more commonly known as the bus ormemory frequency. Switches SW1–2 to SW1–5 select theprocessor multiplier.Single board computer(SBC)
1026209–0001 Revision B Adding cards to the System Controller 2–21To determine the proper FSB and multiplier for a particularprocessor, first read the clock speed from the label on top of theprocessor casing. Look at the last six numbers in the first row ofnumbers and/or letters. For example, 450512 indicates a processorclock speed (first three numbers) of 450 MHz, with 512K ofLevel–2 (L2) cache (last three numbers). In general, any PentiumII processor 333 MHz or slower uses a 66–MHz FSB, while anyprocessor 350 MHz or faster uses a 100–MHz FSB.To determine the processor multiplier, divide the processor clockspeed by the FSB. For the 450–MHz processor, set the FSB to 100MHz (SW1–1 OFF) and the multiplier at 4.5 (SW1–2 OFF,SW1–2 ON, SW1–3 ON, and SW1–5 OFF). See the followingchart for other processor combinations and settings.Table 2-4 SBC processor settings (switch SW1) FSB SW1–1 X SW1–2 SW1–3 SW1–4 SW1–5Processor (MHz) SelectsFSB Multiplier These switches select the multiplier.Pentium II 233 MHz 66 ON 3.5 OFF ON OFF ONPentium II 266 MHz 66 ON 4 ON ON ON OFFPentium II 300 MHz 66 ON 4.5 OFF ON ON OFFPentium II 333 MHz 66 ON 5 ON ON OFF OFFPentium II 350 MHz 100 OFF 3.5 OFF ON OFF ONPentium II 400 MHz 100 OFF 4 ON ON ON OFFPentium II/III 450 MHz 100 OFF 4.5 OFF ON ON OFFPentium III 500 MHz 100 OFF 5 ON ON OFF OFFSW1–6 to SW1–8 are reserved and should be left in the OFF position.Highlighted (gray): Standard processor for AIReach OS ControllerJumpersSet all jumpers as specified in Table 2-5 . The location of eachjumper is shown in Figure 2-13.The SBC uses the watchdog timer (jumper J17). Even though thepre–timeout interrupt option (JP3) of the watchdog timer is notused, leave a jumper across pins 2–3. A jumper over JP4 pins 2and 3 enables PnP capabilities and the ability to upgrade the flashBIOS.
1026209–0001 Revision B 2–22 Adding cards to the System ControllerConnect JP2 pins 2 and 3 for normal CMOS operation. In theevent that CMOS settings prevent the AIReach OS Controllerfrom booting, you can clear the CMOS settings by placing ajumper 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 remediedthrough clearing the CMOS. If it is necessary to clear CMOSsettings, see HNS document 1027630 for the proper settings.Table 2-5 SBC card jumper settings Use these settings.Jumper Function SettingJ17 Watchdog timer Enabled ONJP2 Normal CMOSoperation Normal operation Connect pins2–3JP3 Watchdog timerpre–timeoutinterrupt optionDisabled Connect pins2–3JP4 PnP and BIOSflash upgrade Enabled Connect pins2–3
1026209–0001 Revision B Adding cards to the System Controller 2–23After all cards are installed, make sure the MVIP and H.100 busribbon cables are connected to the cards as shown in Figure 2-14.If you added any cards, connect the bus cables to the addedcard(s), as shown.The MVIP bus ribbon cable connects to:•The small bus adapter card attached to the top of the firstQuad T1 card (in slot 9)•Any TX2000 cards•Any conference cardsThe H.100 bus cable connects to all Quad T1 cards.Make sure the bus adapter card is secure and in full contactwith the (slot 9) Quad T1 card.Figure 2-14 H.100 and MVIP bus cables (2 views)LAN 1cardSBCcardConfcard 1Confcard 2TX2000SS7cardTX2000IPcardSLOT 4(PCI 7) SLOT 5(PCI 6) SLOT 6(PCI 5) SLOT 7(PCI 4) SLOT 8(PCI 3) SLOT 9(PCI 2) SLOT 12 SLOT 13(ISA 1) SLOT 14(ISA 2) SLOT 15(ISA 3) SLOT 16(ISA 4)SLOT10SLOTQuad T1 cardsBackplaneTop viewParallelportH.100 bus cableMVIP bus cableFirstQuadT1cardEach rectanglerepresents a connector.H.100 bus cableMVIP bus cable(Connects all Quad T1 cards)(Connects all Tx2000and conference cards)Bus adaptercard (slot 9)T00010292.6Attaching the buscables
1026209–0001 Revision B 2–24 Adding cards to the System ControllerAfter making sure all jumpers and DIP switches on the card are setcorrectly:1. Use a Phillips screwdriver to remove the screw from thecard slot cover (blank panel), and then remove the card slotcover from the Controller chassis.2. Slide the card into place. Fully insert the card’s edgeconnector(s) into the sockets on the System Controllerbackplane.Install the card according to the manufacturer’s directions.3. Replace and tighten the slot cover screw (now into the cardbracket) to secure the card to the Controller chassis.4. When all cards are installed, replace the System Controllertop cover.5. Connect power to the Controller.6. Boot the Controller. (Power it on.)2.7Adding cards to theSystem Controller(final steps)
1026209–0001 Revision B Adding cards to the System Controller 2–25Use the System Controller installation software to:•Configure a new System Controller•Configure a replacement card•Reconfigure a card after moving it to a different slotFor a new System Controller, follow the configuration steps belowafter all cards are installed.If an installed card is replaced or moved, you must follow thesteps in this section to configure or reconfigure it.Important: For values needed to configure the picocell, see thesite–specific AIReach Office Configuration Report. References tospecified values or parameters in this manual refer to values andparameters specified in the Configuration Report. For values notlisted in the Configuration Report, use the default values shown inthe software or specified in these instructions.Follow the steps below to enter basic configuration informationfor newly installed cards.If you are using the standard Controller configuration, with noadditional cards, verify that the standard cards are installed, andverify the configuration information.1. At the System Controller, start Windows NT.2. From the Windows NT desktop, double–click theAROSHWCf . . . (hardware configuration) icon:The AIReach OS software displays the AROS SystemManagement window, shown below:3. If any AIReach OS applications are running, close them byclicking Shutdown AROS.2.8Configuring SystemController cardsSpecifying basic cardinformation
1026209–0001 Revision B 2–26 Adding cards to the System Controller4. For newly installed cards only, click Add to display theHardware Details window:5. For each newly installed card, enter the followinginformation:a. Select the Card Type for the new card from thedropdown list.b. Enter the PC Slot, PCI Bus, and PCI Slot or Addressvalues specified in the Configuration Report.If you click Find Next T1 Card, the software locatesthe next Quad T1 card (not TX2000 or conferencecards) and automatically display detectedconfiguration data.c. Click Accept.6. Reboot the Controller: Click Start → Shut Down, selectRestart the computer?, and click Yes.
1026209–0001 Revision B Adding cards to the System Controller 2–27After entering information for new cards (Section 2.8), verify thecard configuration as follows:1. As the System Controller becomes operational (afterrebooting), several background processes appear on theWindows taskbar. Verify that the AIReach OS softwareapplications are present, as indicated on the Windowstaskbar:The taskbar may show other applications in addition tothose shown here.(The taskbar is shown vertically here, so the labels can beread. Typically, it appears horizontally across the bottom ofthe screen.)If any applications are missing, contact your HNSInstallation Manager.2.9Verifying the cardconfiguration
1026209–0001 Revision B 2–28 Adding cards to the System Controller2. Launch the AIReach Office application by double–clickingon the desktop icon labeled AROS Configuration (shownbelow).The software displays the AIReach Office banner windowshown below and a Login dialog box that shows AROSC: Localhost. “Localhost,” the default Controllerselection, indicates that you are logging onto the localController.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.)- PasswordThe default administrator password is “abc123.”4. Click Connect.The Login dialog box disappears.5. After you successfully log in, change the administratorpassword: Click File → Change Password, and enter apassword.
1026209–0001 Revision B Adding cards to the System Controller 2–296. From the AIReach banner window main menu, selectConfigure → BSC Configuration.7. Click the HW Config tab to display the AROSCConfiguration window shown below.8. If any installed cards are not listed, click Add to add thecard(s).9. The AIReach OS software prompts you to enter the type ofcard you want to add.After you enter the appropriate information, the softwaredisplays a configuration window for the type of card youindicated.10. To add:- A Quad T1 card, go to step 11.- A TX2000 or conference card, go to step 14.
1026209–0001 Revision B 2–30 Adding cards to the System ControllerIf you specified a Quad T1 card (in step 9), the software displaysthis window, which shows parameters for configuring the Quad T1card:11. For each T1 line (Line 1, Line 2 . . . ), verify or select thefollowing values:- PC Slot: Slot where the card is installed.- Connection Type: BTS or PBX. Set according towhether 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.- Frame Type: ESF.- Clock Reference: SLAVE, MASTER_EXTERNAL,or BACKUP.Set all lines configured as BTS Connection Type toSLAVE. Set one (and only one) PBX connection onthe Controller to MASTER_EXTERNAL. If a secondPBX connection is present, set it to BACKUP. Set another PBX connections to SLAVE.- T1 Time Slot: All T1 slots should be set to Free.12. Click Accept to save the information.13. After adding cards or modifying any settings under the HWConfig tab, click Start → Shut Down to reboot theController.Adding a Quad T1 card
1026209–0001 Revision B Adding cards to the System Controller 2–31If you specified a TX2000 card or conference card (in step 9), thesoftware displays this window, which shows parameters forconfiguring the TX2000 card or conference card:14. Select the TX2000 or conference card from the Card Typedropdown list.15. Verify the displayed values.16. Select INS from the Desired State menu.17. Click Accept to save the information.18. After adding cards or modifying any settings under the HWConfig tab, click Start → Shut Down to reboot theController.Adding a TX2000 orconference card
1026209–0001 Revision B Installing the Controller 3–1 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–7The AIReach OS System Controller, monitor, and associatedcomponents are typically installed in a rack. All cards must beinstalled in the System Controller before the Controller is installedin the rack.To install cards in the Controller, see Chapter 2.For verification information and procedures, see Chapter 4.
1026209–0001 Revision B 3–2 Installing the Controller Mount the System Controller, monitor, and keyboard (withtouchpad) on an available 19–inch rack, as shown in Figure 3-1 .Optionally, a UPS, power distribution tray, patch panel, and CSUtray can be mounted on the same rack. (These components are alsoshown in Figure 3-1.)WARNINGThe AIReach Office System Controller canweigh in excess of 50 pounds. To avoidpersonal injury or damage to equipment,follow these precautions:•Do not attempt to move or install theSystem Controller by yourself. Twopeople are required for these tasks.•If the System Controller will be rackmounted, secure the rack to the flooror wall so the rack cannot fall.3.1Rack–mountconfiguration
1026209–0001 Revision B Installing the Controller 3–3Keyboard and mouseUPSG-17207 F07/01/99MonitorPower distributionCSU trayPatch panelControllerFigure 3-1 System Controller and associated components in a 19–inch rack (typical installation)
1026209–0001 Revision B 3–4 Installing the Controller Mount the System Controller chassis to the rack as follows:1. Choose a location in the rack that allows easy access to themonitor, 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 eightprovided mounting screws. See Figure 3-2, which shows thescrew holes on each side of the chassis (front).Figure 3-2 Installing the chassisG-17420 F10/04/994. Tighten the mounting screws.3.2Mounting theController chassis
1026209–0001 Revision B Installing the Controller 3–5After mounting the components in the rack, connect the keyboard,monitor, touchpad cables, and printer (if used) to the ports shownin Figure 3-3:1. Connect the monitor video cable to the video port on therear of the single board computer (SBC) (slot 12).2. Connect the touchpad to the mouse port on the rear of theSBC card.The touchpad and keyboard cables split off from a singlecable. The connectors on these cables are identified bysymbols that look like a computer mouse and a keyboard.3. Connect the keyboard cable to the port on the left rear of theSystem Controller.4. If your configuration includes a printer (optional), connectthe printer to the parallel port (slot 11).PCI9PCI8PCI7PCI6PCI5PCI4PCI3PCI2PCI1ISA1ISA2ISA3ISA4ISA5ISA6ISA7ISA8G-17206 F 02/14/00COM1 portCOM1Monitor port Mouse portPowerconnectorKeyboardportPowerParallel port(LPT1)for optional printerPowerindicatorSlotnumber12345 67891011121314 15 16 17 18 19 20Slottype IDSystem Controller, rear viewFigure 3-3 System Controller connectors for monitor, keyboard, touchpad, and power3.3Controller cabling
1026209–0001 Revision B 3–6 Installing the Controller 5. Provide power to the monitor and System Controller (110Vac, 60 Hz). Figure 3-3 shows the Controller powerconnector.6. Verify that the System Controller power indicators are lit.The power indicators on the front and rear of the Controllerare on only if power is connected to the Controller and thefront panel power switch is on.To check System Controller operation:1. Power on the System Controller.2. Verify that the Controller successfully boots up. You shouldsee the Windows NT desktop on the monitor, with no errormessages.If the Controller does not boot, make sure all cards in theController are properly seated.3. Verify that the keyboard, touchpad, and monitor areoperational.4. As the System Controller becomes operational, severalbackground processes appear on the Windows taskbar.Verify that the AIReach OS software applications arepresent, as indicated on the Windows taskbar:The taskbar may show other applications in addition tothose shown here.(The taskbar is shown vertically here; typically, it appearshorizontally across the bottom of the screen.)3.4Checking SystemController operation
1026209–0001 Revision B Installing the Controller 3–7For information on system cabling, see the Site PreparationManual (1026208–0001).3.5System cabling
1026209–0001 Revision B Verifying the System Controller configuration 4–1 Chapter 4Verifying the System ControllerconfigurationAfter the System Controller has been unpacked, configured withhardware (cards), and installed, verify the configuration asexplained in the following sections:•Data required – page 4–2•Verifying the System Controller configuration – page 4–1To verify the System Controller configuration, the following datamust be available before you begin:•Password (administrator level password used to access thecomputer)•IP address for:- System Controller (or whether DHCP server assigns it)- IS–41 gateway- optional second LAN card, if used•IS–41 gateway socket number•DNS (domain name servers) IP addresses•Subnet mask•Gateway for the subnet on which the System Controllerresides•System identification (SID)•Public system identification (PSID)•System operator console (SOC)4.1Data required
1026209–0001 Revision B 4–2 Verifying the System Controller configurationTo verify the System Controller configuration, you use theAIReach Office Operation and Maintenance Center (OMC)software, as explained below. The OMC software runs on theSystem Controller, under Microsoft Windows NT.Important: For configuration values to enter in the AIReach OSsoftware windows, see the site–specific AIReach OfficeConfiguration Report. References to specified values orparameters in this manual refer to values and parameters specifiedin the Configuration Report. For values not listed in theConfiguration Report, use the default values shown in thesoftware or specified in these instructions.Controller (BSC) configuration windows are available to onlyone user (local or remote) at a time.Starting from the Windows NT desktop, verify the site informationas follows:1. Launch the AIReach Office application by double–clickingon the traffic light icon labeled AROS Configuration,shown below.The software displays the AIReach Office banner windowand a Login dialog box.If the application is already running, click its button on theWindows taskbar (and skip step 2).2. In the Login dialog box, enter:- System to log intoTo use the local Controller, leave the default,Localhost, after AROSC.- User name(No entry is needed if this field is grayed out.)- PasswordThe default administrator password is “abc123.”3. Click Connect.4. After you successfully log in, change the administratorpassword if you have not already done so: Click File →Change Password, and enter a password.4.2Verifying theSystem ControllerconfigurationVerifying the siteinformation
1026209–0001 Revision B Verifying the System Controller configuration 4–35. Select Configure → BSC Configuration from theAIReach Office banner to display the main AROSCConfiguration window, shown below.6. Verify the following information:- AROSC NameVerify that the AROSC Name matches the nameassigned to the Controller by clicking Start →Settings → Control Panel → Network → NetworkID.Do not change the AROSC Name unless the TACinstructs you to do so.- Operating Mode: Normal- Companding Type: Mu–Law7. Enter the Geographic Location information; then clickAccept.
1026209–0001 Revision B 4–4 Verifying the System Controller configurationVerify the card information for each card that is installed in theSystem Controller.1. Click the HW Config tab to see information for theinstalled cards:2. Verify that the cards installed in the Controller are configuredfor the specific site.At least one Quad T1 card, one TX2000 card, and oneconference card must be listed.Verifying the cardinformation
1026209–0001 Revision B Verifying the System Controller configuration 4–53. Select (highlight) the first Quad T1 card and double–clickon the card name to display the Hardware Configurationwindow.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 exceptthose connected to the PBX.For the Quad T1 port connected (or to be connected) to thePBX, set the Clock Reference to MASTER_EXTERNAL.A second PBX connection can be set to BACKUP. Set anyadditional PBX connections to SLAVE.5. Click Accept.6. For each additional Quad T1 card, repeat steps 3 through 5to verify the information for all T1 lines.7. Click Close to return to the AROSC Configuration window.
1026209–0001 Revision B 4–6 Verifying the System Controller configuration8. Highlight the TX2000 card and double–click to display theHardware Configuration window.9. Verify the Desired State—INS (in service); then clickAccept.10. Highlight the conference card and double–click to displaythe Hardware Configuration window.11. Verify the Desired State—INS (in service); then clickAccept.
1026209–0001 Revision B Verifying the System Controller configuration 4–712. In the AROSC Configuration window, click the Clusterstab.13. If the specified clusters are not listed, click Add to displaythe Cell Configuration – New window:14. Enter the specified cluster name.15. Select the band to use from the Band dropdown list, andclick Accept.
1026209–0001 Revision B 4–8 Verifying the System Controller configuration16. 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 theleft box and the end channel in the right box below“Specify a frequency or range . . . “b. Click Enable.c. Enter AROSC pool size: 30d. Click Accept.18. Click the Scanner Parameters tab.(The screen for this tab is not shown.)19. Verify or enter the specified values, and click Accept.20. Close the Cell Configuration – New window.
1026209–0001 Revision B Verifying the System Controller configuration 4–9Configure or verify the information for the network data.For all configuration windows shown or referred to throughthe end of this chapter, do not change default informationunless you are instructed to do so in this manual or by the RFengineer.1. In the AROSC Configuration window, click the Networktab to display the window shown below.2. If the SID (system identification) is not displayed, clickAdd SID to display the SID Configuration – New window.3. Enter the SID and alphanumeric SID for the macro–cellularprovider in the region; then click Accept.Verifying the Networkdata information
1026209–0001 Revision B 4–10 Verifying the System Controller configuration4. If the PSID (public system identification) is not displayedfor the cluster, click Add P/RSID.Make sure all AIReach Office clusters are assigned thesame PSID value.5. Enter the specified PSID information for each cluster andclick Accept.6. Click Close to return the AROSC Configuration window.7. Click the Frequency/DVCC tab; then click the tab for thespecified band (800–A in the example below) to display thewindow illustrated below:8. Verify that all Frequency values (channels) are enabled (boxchecked).If the Frequency values are not enabled:a. Enter the start channel value in the left Frequencywindow and the end channel value in the rightFrequency window.b. Click Enabled.NoteIn the PCS bands (1900 MHz), channels 1000 andabove are not available and must be disabled.
1026209–0001 Revision B Verifying the System Controller configuration 4–119. Click the IS136 tab (not shown) to display the AROSCconfiguration window.10. Click the Network Parameters tab.11. Verify the Service Operator (SOC) and Mobile countryinformation; then click Accept.12. Click the Mobile Call Control tab.13. Verify the information displayed; then click Accept.14. Click the AROSC Services tab.15. Verify the information displayed; then click Accept.16. Click the Call Control tab.17. Verify the information displayed; then click Accept.18. Click the Registration Control tab.19. Verify the information displayed; then click Accept.20. Click the Timers tab.21. Verify the information displayed; then click Accept.Use the scroll bar to view all timers.
1026209–0001 Revision B 4–12 Verifying the System Controller configurationCell information is configured to provide the Controller with datafor each picocell’s DCCH, handoff, physical layers, RRM, and thededicated scanning picocell.To configure the picocell information:1. Click the Cells tab.(The window displayed—not shown here—may or may notcontain data.)2. Click Add to display the Cell Configuration – Newwindow.3. Enter the data for the scanning picocell.4. Make sure there is a check mark in the Dedicated ScanningCell box.5. Click Accept.Verifying the Cellinformation
1026209–0001 Revision B Verifying the System Controller configuration 4–136. Click Close to return to the AROSC Configuration window.The scanning picocell you added should now be listed.7. Click Add to display the Cell Configuration – Newwindow.8. 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 informationdisplayed.11. Click the Cell Physical Layer tab. Verify the informationdisplayed.12. Click the Cell RRM tab. Verify the information displayed.13. Click Close to return to the AROSC Configuration window.If you made changes, the software prompts you to acceptthem.14. Repeat steps 7 through 13 until all traffic picocells arelisted in the AROSC Configuration window (Cell tab).
1026209–0001 Revision B 4–14 Verifying the System Controller configurationTo provide the System Controller with the BTS information,follow these directions:1. Click the BTSs tab.(The BTSs window may or may not contain data.)2. Click Add to display the BTS Configuration – Newwindow.3. Enter or verify the information for the scanning picocell.Verifying the BTSinformation
1026209–0001 Revision B Verifying the System Controller configuration 4–15When you enter the serial number (from the label on theback of each picocell), you must enter the serial numberexactly as it appears on the label—as indicated in figure4-1. If the serial number is entered incorrectly, the picocellmay not operate correctly.AVPU-D--02025234T0001001Include 1 dashthe revision letter.beforeInclude 2 dashesthe revision letter.afterPicocellrevision letterEnter all 8digits, includingleading zeros,as on the label.Serial numberFigure 4-1 Recording and entering the serialnumber from the back of the picocell4. When you have verified all data in the BTS Configuration –New window. click Accept.
1026209–0001 Revision B 4–16 Verifying the System Controller configuration5. Click the BTS Components tab.6. Enter or verify the information for the BTS components.The Desired State for all slots should be set to AUTO.7. Click Accept.8. Click Close to return to the AROSC Configuration window.9. Repeat steps 1 through 5 until all traffic picocells are listedin the AROSC Configuration window (BTSs tab).10. Minimize the AROSC Configuration window to return tothe AIReach Office window.
1026209–0001 Revision B Verifying the System Controller configuration 4–17To verify the systemwide configuration:1. From the AIReach Office banner menu, select Configure → NSS → Systemwide to display the System Wide Configuration window.2. Click the System Capability tab.3. Select the specified AROSC Name from the dropdown list.4. Enter or verify the system capability information.The default selection for IS41 Interface is GW (gateway). Ifyou change IS41 Interface to SS7, check all parameters tomake sure they are set correctly for an SS7 interface.5. Click Save.NotesThe customer may provide updated information at the timeof installation.In the following steps, if you have not entered or changedany information, you do not need to save; you can go on tothe next tab.Verifying thesystemwideconfiguration
1026209–0001 Revision B 4–18 Verifying the System Controller configuration6. Click the Service Code tab.The Service ID should display Emergency. The customermay provide updated information during the time ofinstallation.7. Enter or verify the information; then click Save.8. Click the IS–41 Timer tab.9. Enter or verify the information; then click Save.10. Click the Transport tab.11. Enter or verify the information for the WOS to GatewayServer Address and Server Port values; then click Save.12. Click the Line Range tab.13. Verify the Line Range values.14. If you need to modify the Line Range values:a. Click ADD.b. Check the Enabled box so you can enter values forHLR Point Code, mobile phone Begin NpaNxx, andmobile phone End NpaNxx.If the AIReach OS is a standalone system, the localHLR point code is 55 55 229.If the AIReach OS is connected to a macro systemgateway, enter an invalid but non–zero point codesuch as 1 1 1.c. After entering the correct values, click Save.15. Click Close to return to the AIReach Office window.
1026209–0001 Revision B Verifying the System Controller configuration 4–19Verify the MSC Configuration as follows:1. From the AIReach Office banner menu, select Configure→ NSS → MSC → MSC Configuration.2. Click the MSC configuration tab.The parameters that appear in the MSC Configurationwindow depend on whether you selected GW (for gateway)or SS7 from the IS41 Interface dropdown list in the SystemWide Configuration window.The screen shown below is for a gateway (GW)configuration. If you selected SS7 as the IS41 Interface, theMSC Configuration screen will be different.3. Select the specified AROSC Name from the dropdown list.4. Enter or verify the MSC configuration information; thenclick Save.Verifying the MSCconfiguration
1026209–0001 Revision B 4–20 Verifying the System Controller configuration5. Click the BSC Configuration tab.6. Enter or verify the information.Make sure all traffic picocells to be installed are assigned aBSC.Verify that all enabled BSC RNUM values are greater thanzero and match the Registration Number entered in the CellConfiguration – New window (shown on page 4–12).7. Click Save.8. Click the MSC Timer tab.9. Enter or verify the information.Use the scrollbar to view all fields.10. Click Save.11. Click the TLDN Range tab.A temporary local directory number (TLDN) enables amacro user to communicate with a mobile registered on theController.The TLDN maximum range is 100 numbers.The TLDN cannot be a duplicate of an LDN.12. Enter or verify the information; then click Save.13. Click Close to return to the AIReach Office window.
1026209–0001 Revision B Verifying the System Controller configuration 4–21Configure 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.)NoteYou only need to configure the HLR once (not once for eachpicocell).2. Select the AROSC Name from the dropdown menu andenter the specific values. Then click the Save button.3. Select the NPA–Nxx tab.You must configure the NPA–Nxx before you can enter thepremises dialing plan.4. Enter the appropriate values, then click Save.5. Select the Premises Dialing Plan tab.6. Enter the appropriate values, then click Save.Configuring the HLR
1026209–0001 Revision B 4–22 Verifying the System Controller configuration7. Select the MIN Range tab.8. Enter the following values for the first test mobile:a. Begin MIN: Enter the test mobile MIN (mobileidentification number).b. Allocation Type: Select Individually allocated fromthe dropdown list.c. MIN Type: Select AROS only subscriber from thedropdown list.9. Click Save.10. Repeat steps 8 and 9 for the second test mobile phone.Provision at least two test subscribers in the SystemController to verify proper traffic picocell operation.11. Select the LDN Range tab.12. Enter the following for the first test mobile:a. Begin Ldn Block: Enter the temporary LDN (localdirectory number) assigned to the test mobile.b. Allocation Type: Select Allocated Individuallyfrom the dropdown list.c. Ldn Type: Select Local Directory Number from thedropdown list.13. Click Save.14. Repeat steps 12 and 13 for the second test mobile phone.15. Click Close.
1026209–0001 Revision B Configuring the router 5–1 Chapter 5Configuring the routerThis 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–7The AIReach OS supports the Cisco 1602–R router. Theinformation in this chapter applies to the Cisco 1602–R router. Ifyou use a different router, you may be able to apply some of thisinformation, but you will have to configure your router accordingto the manufacturer’s instructions.
1026209–0001 Revision B 5–2 Configuring the routerWhen you install the router:•Install the router in the location specified in theConfiguration Report.•Install the router according to the manufacturer’sinstructions. •Use CAT 5 T1 cable to connect the router to the Controllerand to the service provider’s gateway.To configure the router, you need to obtain the gateway IP addressand circuit identification values from the customer.To configure the Cisco 1602–R router for use in the AIReach OS:1. Refer to the network diagram in Figure 5-1 and verify theIS–41 gateway configuration and IP addresses.AIReach OfficeSystem ControllerService providermacro system networkS1E0S0E1Service providerframe relayDLCI = A DLCI = BT0001027Service providerrouterIP address Zmask ZIP address Ymask YIP address Xmask XIS-41gatewayController IPaddressCustomer router(Cisco 1602-R)Figure 5-1 AIReach OS IS–41 gateway network diagram2. Use Notepad to open the standard router configuration textfile, which is loaded on the Controller.The name of the router configuration file is site–specific.Examples: router.txt, RELIATEL_bldg2.txt3. Save the configuration file using a new file name (topreserve the original file).5.1Installing the router5.2Configuring therouter
1026209–0001 Revision B Configuring the router 5–34. Edit the renamed router configuration file, listed below,with the appropriate IP addresses, masks, and passwords (if used):service udp–small–serversservice tcp–small–servers!hostname <CUSTOMER NAME>!ip subnet–zerono ip domain–lookup!interface Ethernet0 ip address <IP Address X> <Mask X>!interface Serial0 description Leased Line to AT&T (<A>–><B>) ip address <IP Address Y> <Mask Y> encapsulation frame–relay bandwidth 56 frame–relay interface–dlci <B>!no router rip!ip route Z.Z.Z.0 255.255.255.224 <IP Address Z>!no ip http serverno ip classless!line con 0line vty 0 password <customer determined> loginline vty 1 password <customer determined> login length 0line vty 2 4 password <customer determined> login!endFor an example of a typical configuration file, see page 5–6.5. Save the edited configuration file.6. Connect an 8–conductor phone cable from the routerconsole port to the Controller, via the DB–9 adapter.7. From the Windows desktop on the Controller (or a separatePC), select Start → Programs → Accessories →HyperTerminal.
1026209–0001 Revision B 5–4 Configuring the router8. 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) andselect 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 HyperTerminalwindow.10. Connect power to the router and turn the power switch on.The router displays a series of boot–up messages.After bootup is complete, the router displays the userprompt: Router > .11. Enter the router privileged mode (Router #) by enteringenable at the Router > prompt.You cannot modify the configuration file unless therouter is in router privileged mode.12. Enter the router configuration mode (Router (config)#) by entering config term at the Router > prompt.You cannot enter the configuration file unless the routeris in configuration mode.13. Copy and paste the router configuration text file created instep 4 into the router. (Place the cursor after theRouter(config)# prompt; then paste.)14. Save the router configuration file you entered by typingwrite at the Router(config)# prompt.15. Verify that the router configuration file is running byentering sho run (show running program) at the Router(config)# prompt.You should see the contents of the file you edited and saved.16. Verify that the router configuration file is also the startupprogram by entering sho startup at the Router(config)# prompt.17. To exit configuration mode, enter exit at the Router(config)# prompt.NoteTo see the router help screen, enter ? at the Router > prompt.
1026209–0001 Revision B Configuring the router 5–518. To exit router privileged mode, enter exit at the Router> prompt.19. Connect the router to the service provider frame relayservice.Figure 5-2 and the file that follows are examples of a typicalrouter configuration.Figure 5-2 Typical AIReach OS IS–41 gateway network diagramAIReach OfficeSystem ControllerRELIATEL INCmacro system networkS1E0S0E1RELIATEL INCframe relayDLCI = 500 DLCI = 300T0001028RELIATEL INCrouter142.148.254.102255.255.255.252142.146.254.17255.255.255.252142.146.254.101255.255.255.252142.146.254.97255.255.255.252IS-41gateway142.146.254.98Acme CorporationCisco 1602-R routerRouter configurationexample
1026209–0001 Revision B 5–6 Configuring the routerThe file below is an example of a typical router configuration. It isthe configuration file for the network shown in Figure 5-2.service udp–small–serversservice tcp–small–servers!hostname acme64!ip subnet–zerono 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.0 255.255.255.224 142.146.254.101!no ip http serverno ip classless!line con 0line vty 0 password mercury&4 loginline vty 1 password mercury&4 login length 0line vty 2 4 password mercury&4 login!end
1026209–0001 Revision B Configuring the router 5–7To set up the AIReach OS System Controller to access the IS–41gateway:1. Using Notepad, edit the file C:\gwroutes.bat toremove REM from the lineroute ADD –p yyy.yyy.yyy.0 mask 255.255.255.0 xxx.xxx.xxx.xxx2. Enter the first three digits of the IS–41 gateway IP addressin place of yyy.yyy.yyy .For example, if the IS–41 gateway IP address is198.225.8.1, enter 198.225.8, so the address (after –p)would be 198.225.8.0.3. In the xxx.xxx.xxx.xxx position, enter the IP addressof the router on the Controller side of the frame relayconnection to the IS–41 gateway.4. Save the file and close Notepad.5. Click Start → Settings → Control Panel.6. Double–click the Network icon.7. Click the Protocols tab.8. Double–click TCP/IP Protocol.9. In the Adapter dropdown list, select the first adapter card ifit is not selected by default.10. In the IP Address window, enter the IP address designatedby the customer network administrator for the Controller’sconnection to the IS–41 gateway.11. Enter 255.255.255.0 in the Subnet Mask window.12. For the gateway address, enter the IP address of the routeron the Controller side of the frame relay.13. Close all network windows.You should be prompted to reboot the Controller when youclose the last network window.14. Click OK to reboot the Controller.5.3Gateway access
1026209–0001 Revision B 5–8 Configuring the router15. After the Controller reboots, verify connectivity to theIS–41 gateway by pinging the gateway IP address:a. Select Start → Programs → Command Promptto open a DOS window.b. At the DOS prompt (C:>\), enterping <IS–41 gateway IP address>c. A successful ping from the device associated with theIS–41 gateway IP address results in Pinging andReply from messages similar to those shownbelow:
1026209–0001 Revision B Testing picocells 6–1 Chapter 6Testing picocellsThis 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 procedures – page 6–26Each picocell is tested at the System Controller location (stagingarea), so that if a unit fails, it can be replaced before installation.First you test the scanning picocell, then you test the trafficpicocells.Important: References to specified values or parameters in thismanual refer to values and parameters specified in the AIReach OSConfiguration Report. For values not listed in the ConfigurationReport, use the default values shown in the software or specifiedin these instructions.
1026209–0001 Revision B 6–2 Testing picocellsThis section explains how to connect a picocell (scanning picocellor traffic picocell) at the staging area for testing (not for actualinstallation).Test cable: The test cable referred to below is a CAT 5 T1 cableterminated with RJ–45 connectors at both ends. The cable is“flipped” so the TX pinouts at one end connect to the RX pinoutsat the other end. (For pinout details, see page 7-12.)For staging area testing, you connect power from a –48 Vdc powersupply to the test cable, which in turn connects to the picocell.Connect the scanning picocell first (since it is tested first). Followthese instructions to connect a scanning picocell or a trafficpicocell:1. Connect the test cable to the picocell VOICE/DATA IN(LINE POWER) port, as shown in Figure 6-1.2. Connect the other end of the test cable to the first Quad T1card (in slot 9) on the System Controller. See Figure 6-2:-For a scanning picocell, connect to the second port(from the top) of the first Quad T1 card.-For a traffic picocell, connect to the third port (fromthe top) of the first Quad T1 card.CAUTIONMake sure the picocell power switch is OFF(middle position) before connecting thepicocell to the Controller.6.1Connecting apicocell for testing
1026209–0001 Revision B Testing picocells 6–3LINE IOFFoLOCAL IVOICE/DATAOUTVOICE/DATAIN(LINE POWER)FUSELOCAL -POWER +T0001005PicocellLinepowerLocalpowerLocal powerconnector(not used)Connect test cable here.(TX and RX pinoutsmust be flipped).Power switchFigure 6-1 Picocell connection for testing (scanningor traffic) picocell at System Controller location
1026209–0001 Revision B 6–4 Testing picocells1234T0001007LEDsPicocellconnectionsAll ports:RJ-45PBX connection (typicallyfirst port of first Quad T1card, in slot 9)For all other Quad T1 cards:picocell connectionFigure 6-2 Ports on Quad T1 cardProvide power to the picocell:1. Connect a –48 Vdc power supply to the test cable.2. Plug the power supply into a 120 Vac, 60 Hz ac outlet.Power supplyThe following symbols appear on the picocell power supply:Symbols on power supplyT0001023The house symbol indicates that the power supply should be usedonly in a dry environment. The exclamation (!) symbol means toread the instructions in this manual concerning the power supply.As stated on the power supply, there are NO USERSERVICEABLE PARTS INSIDE. Do not attempt to open orrepair the power supply.For power supply specifications, see Appendix A, Section A.3.Providing power to thepicocell
1026209–0001 Revision B Testing picocells 6–5Power on the picocell, and observe the picocell LEDs as theSystem Controller automatically downloads software to thepicocell:1. Press the picocell power switch to the LINE (line power)position.2. Observe the LEDs for normal operation:a. During software loading, the Temp LED on the frontof the picocell is orange. See Figure 6-3.b. When the picocell is fully loaded and operational, thePower and Temp LEDs display green, and the AlarmLED is off.T0001003PowerGreen - Voltage normalOrange - Low voltageAlarm (Controller)Off - NormalOrange - Minor alarmRed - Major alarmTemperature (power supply)Green - NormalRed - Exceeds 75° CPowerTempAlarmAlarm LED is orange whilethe Controller boots.Figure 6-3 LEDs on front of picocellNoteThe LED information above is for production picocells. LEDcodes may be different for pre–production picocells.6.2Verifying softwareload
1026209–0001 Revision B 6–6 Testing picocellsAt 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. Verify that the scanning picocell is connected with the testcable as explained in Section 6.1.2. Make sure the picocell is powered on (power switch in theLINE position).3. Verify that scanning picocell–to–Controller connectivity isgood (green LED on the Quad T1 card, port where thepicocell is connected).(The Quad T1 LEDs are explained in Figure 6-4.)If a red or yellow LED is illuminated on the Quad T1 card:a. Check the T1 test cable. Use a cable tester to verifythat the cable is good and correctly flipped (TX toRX). Re–terminate the RJ–45 connectors ifnecessary.b. If the cable is good, reconnect the picocell to anotherQuad T1 card port.c. From the AIReach Office window, select Configure→ BTS Configuration. This opens the BTSConfiguration window.d. Select the scanning picocell from the BTS pulldownlist.e. Select the new Quad T1 card port from the T1 LineNumber dropdown list, and click Save.If the traffic picocell is connected to a new Quad T1card, select the new card number from the T1 CardNumber pulldown list before selecting the T1 LineNumber.It may take up to 3 minutes for the red LED to turnoff and the green LED to light up.6.3Checking scanningpicocell operation
1026209–0001 Revision B Testing picocells 6–7f. If the red or yellow LED remains lit, repeat steps cthrough e.Figure 6-4 LEDs on Quad T1 card1234T0001006LEDsGreenYellowRedLED indicationsGreen = OperationalRed = Not operational;error conditionYellow = Not operational;error condition.Controller problem.PortsLED positions topto bottom matchport positions.
1026209–0001 Revision B 6–8 Testing picocells4. Click WOS BSC Application to display the WOS BSCApplication window.
1026209–0001 Revision B Testing picocells 6–95. Select Btsm → State to display the Select BTS window.6. Select the scanning picocell from the dropdown menu.7. Verify that the scanning picocell self–test and softwaredownload 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 BSCApplication window.8. Minimize the WOS BSC Application window to return tothe AIReach Office window.Do not close the WOS BSC Application window. Thiswindow is required during normal operation. (If youinadvertently close this window, it will restartautomatically.)
1026209–0001 Revision B 6–10 Testing picocellsPerform an initial (test) 6–minute frequency band scan at theSystem Controller location. The initial band scan is used toquickly find a frequency that can be used to test all the picocells atthe Controller location. Later, you perform a 24–hour (or longer)band scan to set up the system for normal operation.NoteThe system is not available for traffic during a band scan.To initiate a frequency band scan, the Controller must be inSetup mode.Follow these steps to put the Controller in Setup mode:1. From the AIReach Office banner, select Configure → BSCConfiguration → AROSC.2. Select Setup from the Operating Mode dropdown list, thenclick Accept.Call processing is disabled while the Controller is in Setupmode.Clicking Accept disables all Controller T1 lines; therefore,wait (a few minutes) until the Controller T1 lineconnectivity is re–established before initiating thefrequency band scan.6.4Performing a testfrequency bandscan Switching toSetup mode
1026209–0001 Revision B Testing picocells 6–11Set up the band scan as follows:1. From the AIReach Office banner, select Installation →Auto Setup.The software displays the Welcome to AROSC Band ScanSetup 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: Checkc. Number of Reports required: 1.d. Time interval between Scan Reports: 1.e. Continue Previous Scan Test: Not checked.f. RSSI Threshold: –105.Setting up thefrequency band scan
1026209–0001 Revision B 6–12 Testing picocells3. Click Next to display the Band Scan Parameters window.4. Set Critical RSSI bin Uplink and Downlink to 0 for the6–minute band scan(For the subsequent 24–hour band scan, set Critical RSSIbin Uplink and Downlink to 3.)5. In the remaining boxes, use the default parameters unlessotherwise instructed (for example, by the macro provider, orin release notes).6. Click Next to display the Select Cells for the Test window.
1026209–0001 Revision B Testing picocells 6–137. Check the box associated with the scanning picocell nameand select the Uplink / Downlink Scan in the Scan Modecolumn when necessary.8. Click Next to display the Start Scan Frequency Band Scanwindow.9. In the Start Scan Frequency Band Scan window (not shownhere), check these items only:- View Band Scan results before generating PrivateOperating and Traffic Frequencies- View DCCH Scan results before generating PublicService Profile information for AROS cellFollow these steps to start the band scan and observe the results:1. In the Start Scan Frequency Band Scan window, click Nextto start the frequency band scan.When you click Next, the software displays a Measurementin Progress window, and then (automatically) the FrequencyBand Scanning in Progress window.2. Wait for the band scan to finish.No results are shown until the frequency scan is finished.The values shown in the Frequency Band Scanning inProgress window are explained below:The system continuously measures the received signalstrength indication (RSSI) for the whole band, and reportsthe percentages above the given threshold as a cumulativedistribution. Each value is the percentage of samples abovethe given RSSI, which is shown at the top of each column.For example, for channel 2 above, 14% of the samples weremeasured above –101 dBm (RSSI), and 33% were above–105 dbm.A “Time Started” message and value are shown in the lowerleft corner of the window when the band scan is beingsuccessfully performed.Starting the scan andobserving the results
1026209–0001 Revision B 6–14 Testing picocellsApproximately 6 minutes after the band scan was started,the Frequency Band Scanning in Progress windowautomatically closes and the DCCH Scanning in Progresswindow is automatically displayed (not shown here).When the DCCH band scan is finished, the DCCHScanning in Progress window automatically closes, and theBand Scanning Results window is automatically displayed:The Band Scanning Results window indicates if frequenciesare usable or not, based on user–specified limits. Note thatit shows channels, not frequencies.This data is used to generate an initial frequency list.(Subsequently, all frequency management is dynamic.) Thescore values indicate interference at the specified threshold.Some frequencies are marked non–usable because thesystem tries to avoid using adjacent channels.
1026209–0001 Revision B Testing picocells 6–153. Click Next to see the DCCH Scanning Results window(not shown here).4. Click Next to access the Select Measurements Reportswindow.5. For the scanning picocell used to perform the frequency andDCCH band scan:a. Check:- Use to Assign Frequencies- Use to Assign POFs (private operatingfrequencies)- Use to Assign PSPs (public service profiles)b. Do not check “Use results of previous tests if any.”6. Click Next in succession to display these windows:a. Initial PSP assignment windowb. Initial POF Assignment window (listing the availablechannels and POFs)
1026209–0001 Revision B 6–16 Testing picocells7. Click Next again and the Setup Complete window isdisplayed.8. Click Finish and the AIReach Office banner window isdisplayed.The POFs and cluster pool are now automatically assigned.Returning to normal operation1. From the AIReach Office banner, select Configure → BSCConfiguration → AROSC.2. Select Normal from the Operating Mode dropdown list,then click Accept.Clicking Accept disables the Controller T1 lines; therefore,wait (a few minutes) until the Controller T1 lineconnectivity is re–established before checking trafficpicocell operation (Section 6.5).
1026209–0001 Revision B Testing picocells 6–17Perform this test sequence for each traffic picocell.Temporarily connect the traffic picocell to the System Controllerto verify that the picocell is operating properly.1. Verify that the traffic picocell is connected with the testcable, as explained in Section 6.1.2. Make sure the picocell is powered on (power switch in theLINE position).3. Verify that the traffic–picocell–to–Controller connectivity isgood (LED green on the corresponding Quad T1 card port).(The Quad T1 LEDs are explained on page 6–7.) If a red LED is illuminated on the Quad T1 card:a. Check the T1 test cable. Use a cable tester to verifythat the cable is good and correctly flipped (TX toRX). Re–terminate the RJ–45 connectors ifnecessary.b. If the cable is good, reconnect the traffic picocell toanother port.c. From the AIReach Office window, select Configure→ BTS. This opens the BTS Configuration window.d. Select the new Quad T1 card port from the T1 LineNumber dropdown list, and click Save.If the traffic picocell is connected to a new Quad T1card, select the new card number from the T1 CardNumber pulldown list before selecting the T1 LineNumber.It may take up to 3 minutes for the red LED to turnoff and the green LED to light up.6.5Checking trafficpicocell operation
1026209–0001 Revision B 6–18 Testing picocells4. Click WOS BSC Application to display the WOS BSCApplication window.
1026209–0001 Revision B Testing picocells 6–195. Select Btsm → State.6. Select the traffic picocell using the dropdown menu below“WBSU.”7. Verify that the traffic picocell self–test and softwaredownload are successful:a. BTC: Verify that one of the channels identified asusable from the test frequency band scan appears forBTC 1.b. WBSU State: Verify that the state is Active.c. BTC State: Verify that the state is Active.d. DCCH State: Verify that the state is Active.8. Minimize the WOS BSC Application window to return tothe AIReach Office window.Do not close the WOS BSC Application window. Thiswindow is required during normal operation. (If youinadvertently close this window, it will restartautomatically.)
1026209–0001 Revision B 6–20 Testing picocellsThis section explains how to provision test mobile phones so theycan be used to check traffic picocells.Multiple users can access and use subscriber configurationwindows 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. Select the AROSC Name using the pulldown menu.3. Enter the first test mobile LDN, MIN, and ESN values, thenclick Save.4. Select Subscriber Type: Local.5. Select Premises Extension: No.6. Click Save.6.6Provisioning testmobile phonesSubscriberprovisioning
1026209–0001 Revision B Testing picocells 6–217. Click the Basic Services tab.8. Enter the information; then click Save.9. Select the Supplementary Services tab.10. Enter the information; then click Save.11. Select the Service Profile tab.12. Enter the information; then click Save.13. Select the PSID/RSID tab.14. Enter the PSID value.When you enter a value, press the Enter or Tab keyafterward. The Save button is “grayed” (not available) untilyou press the Enter or Tab key.15. After entering the information; click Save.16. Click the Operational Data tab.17. Enter or verify the specified values; then click Save.
1026209–0001 Revision B 6–22 Testing picocells18. Click the Operational Status tab.19. Verify that the specified HLR Flags and VLR Flags aredisplayed.The next step (detailed in Section 6.9) is to place test calls to testthe picocells. However, before phones can be used for testing, theymust 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 theAIReach OS. To program a Nokia series 6000 mobile phone fortesting, follow the steps below. All other necessary values areloaded when the phone is registered onto the AIReach OS.1. Enter *3001#12345#.2. Activate field test mode:a. Press until Field Test is highlighted.b. Press (OK).c. Press until Enabled is highlighted.d. Press .3. Enter the assigned MIN:a. Press until NAM1 is highlighted.b. Press .c. Press until Own Number is highlighted.d. Verify that the MIN displayed is the correct MIN.e. If the displayed MIN is not correct:i. Press .ii. Enter the correct MINiii. Press .6.7Programming testmobile phones
1026209–0001 Revision B Testing picocells 6–23To register the test mobile phones on the AIReach OS, follow thesteps below.Prerequisites:•The test phone must be provisioned, with the correct MINand 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. Power the phone off, then on.2. Make sure the phone is on the correct band:The phone must be on the correct band before you initiateregistration. When the phone is in field test mode, the bandis displayed on the third line of window 01. A lowercase aor b represent the two 850 MHz cellular bands, anduppercase A through F represents the 1900 MHz PCSbands. If the phone camps on an incorrect band, powercycle the phone while shielding the antenna. The phoneshould begin to search each band. Once it begins searchingthe correct band, proceed with step 3 before the phonemoves to the next band.3. Select Menu.4. Scroll down the options and select System.5. Select New Search and OK.The phone should display Searching and then New System – xxxxxx , where xxxxxx is the alphatag (alphanumeric SID) for the system.6. If the displayed alpha tag is the alpha tag assigned to theAIReach OS, select OK complete the registration.(If you don’t know the AIReach OS alphanumeric SID, youcan find it on the Controller: From the AIReach Officebanner menu, select Configure → BSC Configuration,and then click the Network tab.)When the phone is registered on the system, the alphatag is displayed in window 07 of the test phone.7. If the displayed alpha tag is not the alpha tag assigned tothe AIReach OS, select Next to continue searching.If the phone displays No New Systems, verify that thecorrect information is entered in the subscriber window(Section 6.6), paying special attention to the MIN, ESN,and PSID values. Then repeat steps 1 through 6 to registerthe phone on the system.6.8Registering testmobile phones
1026209–0001 Revision B 6–24 Testing picocellsThe procedures below explain how to test all transceivers in eachinstalled traffic picocell.1. Determine which picocell slots contain transceivers (BTCs).A label attached to the picocell tells you which slots containBTCs. The slot arrangement and numbering scheme areshown in Figure 6-5.10234CPUThe CPUslot is notnumbered.Depending on thepicocell configuration,slots 0 - 4 may contain2 to 4 BTCs, a scanningreceiver or some slotsmay be empty.–T0001032Figure 6-5 Picocell slot numbers2. From the AIReach Office Window, select Configure →BSC Configuration.3. Click the BTSs tab.4. Highlight and double–click on the traffic picocell to betested, and click the BTS Components tab.Test the first transceiver (any one) as follows:1. Leave the transceiver to be tested in service (INS). Take allother transceivers (BTCs) out of service (OOS).a. For each slot that contains a BTC:i. Select BTC from the Hardware Typedropdown list.ii. Select OOS from the Desired State dropdownlist.b. Click Accept.The software displays the AROSC Configurationwindow.2. Record the power level displayed on the test mobiles.3. Initiate a mobile–to–mobile test call. (Dial the 4–digit LDNassigned to the other test mobile.)6.9Placing test callsFirst transceiver test
1026209–0001 Revision B Testing picocells 6–254. The test is successful if the transceiver processes the calland the displayed power level reading varies no more than 5units from all other picocells.5. 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 unitscompared with readings from all other picocells.Test the remaining transceivers as follows:1. Bring another traffic picocell transceiver into service:a. Highlight the picocell to be tested and click the BTSComponents tab.b. For the transceiver just tested, select OOS from theDesired State dropdown list.c. For the BTC to be tested:i. Select BTC as the Hardware Type.ii. Select AUTO from the Desired Statedropdown list.d. Click Accept.The software displays the AROSC Configurationwindow.2. Repeat the test call procedure for all transceivers installed inthe traffic picocell being tested.(Record power level; initiate test call; observe powerlevel—steps 2 through 4 in the previous section.)3. After testing all transceivers, turn off and disconnect thetraffic picocell from the Controller.4. Repeat the test call procedure for each traffic picocell. (Testall transceivers.)5. In the event you find a failed transceiver, toe tag and shipthe picocell to the MRC, with assigned RMA number.Do not ship any components without an RMA number.Testing the remainingtransceivers
1026209–0001 Revision B 6–26 Testing picocellsThe following programming procedures for Nokia Series 6000mobile phones are provided for the installer’s convenience.However, normally, these procedures are not required to completeand test the installation.To program the home system ID number for a Nokia 6000 seriesmobile phone:1. Enter *3001#12345#.2. Press until Field Test displays, then press .3. Press until Enabled is highlighted and press (OK).4. Press until NAM1 is highlighted and press .Verify Home System ID displays 13.5. If 13 does not display, press , enter 13 and press .To program the Home SOC for a Nokia series 6000 phone:1. Press until Home SOC displays. Verify that the HomeSOC displays 4.2. If the Home SOC is not correct, press , enter 4, andpress .To program the PSID/RSID number:1. Press until PSID/RSID displays and press .2. Select P/RSID 1.3. Press until the PSID/RSID displays. Verify that 15099displays for the PSID.4. If the PSID is incorrect, press , enter the PSID 15099,and press .To program the system ID number for a Nokia series 6000 phone:1. Press until the System ID displays and press .2. Verify that the System ID displays 13.3. If the System ID is incorrect, press , enter 13, and press .6.10Additional phoneprogrammingproceduresHome system IDHome SOCPSID/RSID numberSystem ID number
1026209–0001 Revision B Testing picocells 6–27To program the Operator Code (SOC):1. Press until the Operator Code (SOC) displays andpress .2. Verify that the Operator Code displays 4.3. If the Operator Code is incorrect, press , enter 4, andpress .To program the NAM Status for a Nokia series 6000 phone:1. Press or (right button) until NAM1 displays and press.2. Press until Change Defaults displays and press .3. Verify that the NAM Status displays enabled.4. If the NAM Status is incorrect, highlight enabled and press.5. Press (right button) until NAM1 is highlighted.6. Press until NAM2 displays and press .7. Press until Change Defaults displays and press .8. Verify that the NAM Status displays disabled.9. If the NAM Status is incorrect, highlight disabled andpress .10. Press until NAM3 is highlighted and press .11. Press until Change Defaults displays and press .12. Verify that the NAM Status displays disabled.13. If the NAM Status is incorrect, highlight disabled andpress .Operator Code (SOC)NAM status
1026209–0001 Revision B 6–28 Testing picocellsTo initialize changed settings for a Nokia series 6000 phone:(You do not need to do these steps after putting the phone intofield 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 until Setting displays and press .4. Press until Network Services displays.5. Verify that digital & analog displays.6. If digital & analog does not display, press until digital& analog displays and press .7. Press until Public System displays and press .8. Press until Any System is highlighted and press .9. Press (right button) until the main screen displays.10. Press until System displays and press .11. Highlight New Search and press .12. Verify that Alpha Tag displays and press .Initializing settings
1026209–0001 Revision B Installing picocell 7–1Chapter 7Installing picocellsThis chapter describes how to install a picocell at the permanentsite. 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–18Install the scanning picocell first, and then the traffic picocells.Follow the instructions in the AIReach OS Configuration Reportfor specifications on picocell location, cable labeling and telcoblock assignments.Important: All T1 wiring must comply with TIA/EIA–568A andTIA/EIA–606. (In Canada, must comply with CSA StandardsT528 and 529.)CAUTIONBefore removing or installing electroniccomponents, make sure static electricityhas been discharged from yourself and anyobject that will contact the component.Wear a new or recently tested anti–staticwrist strap and use an anti–static pad whilehandling components.Failure to follow these instructions couldresult in damage to components.Before you begin installing picocells, ensure that . . .•The power supply for line power is mounted in the telcoroom and correctly connected to the telco block.•The T1 cables are punched down and correctly labeled onthe telco block.•The power supply voltage to the picocell is –48 Vdc.•The picocell location will not interfere with door clearances.•The picocell will not be located in an inappropriate room(for example: a room without air conditioning).7.1Preparing forpicocell installation
1026209–0001 Revision B 7–2 Installing picocellThe picocell is designed to be attached to different wall surfaces:wallboard, concrete, wood, or metal or wood studs.The mounting plate must have at least 4.5 to 5. inches of clearanceon all sides (from ceiling, floor, and walls) so the picocell willhave proper clearance (3 inches minimum) for mounting andventilation. See Figure 7-1.4.5"4.5" 4.5"5"The clearances shown above allow a 3-inch minimum clearanceon the sides and top of the picocell, when it is mounted.CeilingWallT0001025Mounting plateFigure 7-1 Placing the mounting plate to allow proper clearance around the picocell7.2Mounting thepicocellsInstalling the mountingplate
1026209–0001 Revision B Installing picocell 7–3Figure 7-2 shows the position of the mounting plate relative to thepicocell.1.5” 2.0”1.375”2.75”G-17371 F 08/24/991234Figure 7-2 Position of the picocell on the mounting plateNotice that clearance for the mountingplate is not the same on each side.PicocellNoteThis note applies only to pre–production picocells: Mounting platerevisions are not upward compatible. This means you cannot useRevision B plates on Revision C picocells, but you can useRevision C plates on Revision B picocells.FastenersTo mount the picocell mounting plate to the wall surface, use onlythe fasteners shown in Table 7-1 —these are the only approvedfasteners. See the AIReach Office Configuration Report for sitespecifications.For wood or metal studs, HNS recommends two fasteners. SeeTable 7-1 and Figure 7-3.For walls composed of concrete, block, or drywall, HNSrecommends four fasteners. See Table 7-1 and Figure 7-4.
1026209–0001 Revision B 7–4 Installing picocellTable 7-1 Approved mounting plate fasteners Surface Fastener Fastener partnumber Hole locations 1Drywall (hollow) E–Z Anchor self–drillingdrywall anchor and screw 9010193–0001 1, 2, 3, 4Concrete block ortLead anchor for 10–24 screw 9004929–0001 1, 2, 3, 4concrete Phillips head machine screw, 10–24 x 3/4” 9003333–0074Metal wall or metal studs Sheet metal screw,self–drilling, self–tapping, 10 x 3/4”1028868–0018 1, 3Wood wall or wood studs Wood screw, 10 x 1–1/4” 1028228–0021 1, 31As shown in figures 7-3 and 7-4.If the picocell is located near a door, make sure the door openswithout hitting the picocell:1. Mount the picocell so the bottom of the picocell is abovethe top of the door and door hardware, or2. Mount the picocell far enough from the door so the door canopen fully without hitting the picocell.
1026209–0001 Revision B Installing picocell 7–5NoteIf you use option 1 to mount the picocell near a door,remember to maintain the proper clearance between the topedge of the picocell and the ceiling.G-17212 F10/04/99Mounting plateWood ormetal studThis side up1234Two fastenersFigure 7-3 Attaching the picocell mounting plate to wood or metal studs
1026209–0001 Revision B 7–6 Installing picocellG-17414 F10/04/99Mounting plateFour fastenersThis side up1234Figure 7-4 Attaching the picocell mounting plate to concrete, block, or wallboardTo attach the mounting plate (for all wall types):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 inFigure 7-1.c. Make sure the mounting plate is level.2. Mark on the wall the position of each mounting screw.3. If the cable to the picocell will be installed through the walland mounting plate:a. Mark on the wall the outline of the rectangular holein the center of the mounting plate.b. Remove the plate so you can cut the hole.c. Cut the hole in the wall, inside the rectangular wallmarking.4. Mount the mounting plate on the wall using the fastenersspecified in Table 7-1 .
1026209–0001 Revision B Installing picocell 7–7This procedure applies to both the scanning picocell and trafficpicocells.Install the scanning picocell in its permanent location prior tocompleting the 24–hour (minimum) frequency band scan (section7.4).To save time, initiate the 24–hour frequency band scan (Section7.4) and then install the traffic picocells at their permanentlocations while the band scan is running.NoteThe site–specific AIReach Office Configuration Report containsthe information needed to install the picocells, including locationswhere picocells are to be installed, cable labeling, punchdownblock assignments, and required fasteners.The following labels appear on the picocell connector panel:Labels on picocellSWITCH POWER OFFBEFORE CONNECTINGOR DISCONNECTINGCABLESWARNINGCAUTIONTO REDUCE THE RISK OFFIRE, USE ONLY No. 24AWG OR LARGER LISTEDTELECOMMUNICATIONSLINE CORD.FOR CONTINUEDPROTECTION AGAINSTRISK OF FIRE, REPLACEONLY WITH SAME TYPEAND RATING OF FUSE.T0001022As indicated by the WARNING label, make sure the picocellpower switch is OFF (middle position) before connecting ordisconnecting cables. This is to protect the picocell connectorsfrom possible damage.As indicated by the CAUTION label, use only No. 24 AWG linecord to connect to the VOICE/DATA ports. If you replace thepicocell fuse, use only a fuse of the type and rating identified onthe fuse label.WARNINGTo reduce the risk of fire, use only No. 24AWG or larger line cord to connect to thepicocell, and replace the fuse only with afuse of the type and rating identified on thefuse label.Failure to heed these warnings could resultin personal injury or death.7.3Installing andconnectingpicocellsWarnings and cautions
1026209–0001 Revision B 7–8 Installing picocellConnect the T1/power cable as follows:1. Terminate the T1 cable(s) with RJ–45 connectors on eachend using the pinout plan shown in Table 7-2 .Plastic clip Pin 1T0002001RJ–45 connector, showing pin 1 positionTable 7-2 T1 (RJ–45) connector pinouts Pin T1 connector signal CAT 5 color coding1RX RING White–blue2RX TIP Blue–white3+VDC1 (GND) White–green4TX RING White–orange5TX TIP Orange–white6–VDC1 Green–white7+VDC2 (GND) White–brown8–VDC2 Brown–white2. Label the cable at the picocell end.Picocell connections
1026209–0001 Revision B Installing picocell 7–93. Route the T1/power cable through the opening in the wallmounting plate (as shown in Figure 7-5).An acceptable alternative is to run the cable down from theceiling, along the wall to the picocell.G-14762 F08/23/99Cables routedthrough wallCAT 5 T1/powercable to controllerMounting platePicocellFigure 7-5 Cabling the picocell
1026209–0001 Revision B 7–10 Installing picocell4. Connect the T1 cable (with RJ–45 connector) to theappropriate picocell port, as shown in Figure 7-6.LINE IOFFoLOCAL IVOICE/DATAOUTVOICE/DATAIN(LINE POWER)FUSELOCAL -POWER +T0001010PicocellLinepowerLocalpowerLocal power(not used)Connect CAT 5 T1 cablehere forpicocell.daisy-chainedConnect CAT 5 T1/powercable here for bothpicocells.standalone and daisy-chainedPower switchFigure 7-6 T1 cable and power connections at the picocell
1026209–0001 Revision B Installing picocell 7–11Figure 7-7 T1 cabling for standalone and daisy–chained picocellsT0001009VOICE/DATAOUTVOICE/DATAINPowerswitchVOICE/DATAOUTVOICE/DATAINPowerswitchVOICE/DATA OUTVOICE/DATA INVOICE/DATA OUTVOICE/DATA INVOICE/DATA OUTVOICE/DATA INTelco blocksPicocellsCAT 5 T1 cabling(single run)ToControllerCAT 5 T1 cabling(double run)VOICE/DATA OUTVOICE/DATA INVOICE/DATA OUTVOICE/DATA INVOICE/DATA OUTVOICE/DATA INTelco blocksPicocellsToControllerStandalone picocellsDaisy-chained picocells
1026209–0001 Revision B 7–12 Installing picocellMount the picocell as follows:1. Power on the picocell by pressing the power switch to theLINE position.2. Mount the picocell to the mounting plate by aligning thelock on the picocell housing with the positioning tab on themounting plate, as shown in Figure 7-8.WARNINGWhen installing the picocell on the mountingplate, use care to avoid falling and injuringyourself.3. Push the picocell into the mounting plate, and then slide itdown and to the right to the locking position.4. Turn the lock key to the horizontal position to lock the unitafter it is mounted.If the key is difficult or impossible to turn, the picocell maynot be properly mounted. If this is the case, reinstall thepicocell on the mounting plate.Mounting the picocell
1026209–0001 Revision B Installing picocell 7–13Figure 7-8 Mounting the picocellMounting plateThis side up1234G-14764 F08/24/99Align locking tabwith alignment dotson picocell123Align picocell with mounting plate,push in, pull down, and push rightto secure5. Punch down and label the T1 cables on the telco roomtermination block.
1026209–0001 Revision B 7–14 Installing picocell6. 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 heatshrink it.e. Connect the wires from the power supply to theterminal block, as shown in Figure 7-9 and Table7-3 .f. Plug the power cable into a 110 Vac outlet.Figure 7-9 Power terminal block connectionsCAT 5PowersupplyG-17404 F08/24/99To picocellTable 7-3 Power supply and CAT 5 wire colors Power supply wire Cat 5 wire48 Vdc loadWhite Green–white–48 Vdc load Black Brown–white48 Vdc returnRed White–green–48 Vdc return Brown White–brownAC ground(not used) Green Not applicable
1026209–0001 Revision B Installing picocell 7–15AC outletG-17890 F10/04/99PicocellPowersupplyTerminal block(see detail)Telco blockfor picocell T1connectionsTelco blocks can be:- 66 block- 110 block or- Bix blockBuilding riser telco block forT1 cross-connect to ControllerWIRING CLOSETT1 bundleto/fromControllerCAT 5cableTerminal block detailTwo pairs of CAT 5to merge withcable to picocellHeat shrinkTo power supplyFigure 7-10 Picocell connections at the telco closet
1026209–0001 Revision B 7–16 Installing picocellImportant: All T1 wiring must comply with TIA/EIA–568A andTIA/EIA–606. (In Canada, T1 wiring must comply with CSAStandards T528 and T529.) These standards are listed in AppendixB, Section B.5.A T568B–compliant wiring flip must be used between:•The Controller and picocell•Daisy–chained picocells (that is, between eachpicocell–to–picocell connection)The flip is accomplished at the patch panel (as shown in Figure7-11) or using a modular jack (Figure 7-12). The flip must beT568B compliant, as shown in these two illustrations.T0001021White/GreenGreen/WhiteWhite/BrownBrown/WhiteWhite/BlueBlue/WhiteWhite/OrangeOrange/WhiteSide view Rear view(flip detail, T568B)PatchpanelRJ-45connector,straight throughPatchpanelFlipTopicocellFigure 7-11 T568B–compliant wiring flip at patch panelT1 wiring and flip
1026209–0001 Revision B Installing picocell 7–17Figure 7-12 T568B–compliant wiring flip using modular jackRJ-45 connector pinout for T568B-compliant flipT568B Flipped endPin Signal Color code Pin Signal Color code1 TX Ring White-orange 5 RX Ring White-blue2 TX Tip Orange-white 4 RX Tip Blue-white3 Pos DC White-green 3 Pos DC White-green4 RX Tip Blue-white 1 TX Ring White-orange5 RX Ring White-blue 2 TX Tip Orange-white6 Neg DC Green-white 6 Neg DC Green-white7 Pos DC White-brown 7 Pos DC White-brown8 Neg DC Brown-white 8 Neg DC Brown-whiteView from frontopening, tab down12345678W-O OW-GBLW-BLGW-BRBRPin and color codePair 2 Pair 1 Pair 4Pair 3T00010201. Terminate and label the CAT 5 T1 cable on the specifiedterminal block, using the specified pin assignments.Label the cables in accordance with TIA/EIA–606.2. Terminate the T1 cable with an RJ–45 connector at theSystem Controller end.3. Plug the RJ–45 connector into the first Quad T1 card (inslot 9), second port from the top, at the back of the SystemController.NoteThe physical port assignment for the T1 cable must matchthe virtual port assignment made in the AIReach OSsoftware.Verify that the picocell successfully completes its self test and thatthe Power LED (top) and Temp LED (middle) are green afterapproximately 2 minutes. The Alarm LED (bottom) is orange,then turns off—this is normal cycling of the unit.Check for properoperation
1026209–0001 Revision B 7–18 Installing picocellSection 6.3 explains how to initiate a test (6–minute) frequencyband scan (starting on page 6–10). Now that the system isinstalled, you perform a band scan to set up the system for normaloperation—specifically, to determine what frequencies theAIReach OS can use. The post–installation scan takes aminimum of 24 hours. The AIReach Office Configuration Reportstates the actual time requirement.Initiate the 24–hour band scan as explained in Section 6.3(page 6–10), except:In the Band Scan Parameters window, set Critical RSSI binto 3 (Uplink and Downlink).Otherwise, follow the directions in Section 6.3 (but ignorereferences to a 6–minute band scan).7.4Performing thefrequency bandscan
1026209–0001 Revision B Connecting to external equipment 8–1Chapter 8Connecting 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–11As shown in Figure 1-2 (page 1–2), the AIReach OS Controllerconnects to:•The customer’s PBX•The macro cellular system•The customer’s corporate LAN (optional)The procedures explained in this chapter are related to theseconnections.
1026209–0001 Revision B 8–2 Connecting to external equipment To establish final System Controller connectivity, connect theController to the PBX and connect the analog line as follows:1. Terminate the PBX T1 trunk CAT 5 cable with a RJ–45connector.2. Connect the PBX T1 trunk to port 1 of the assigned QuadT1 card.3. Verify that the Controller configuration values indicatedbelow are set to the values specified in the (customersite–specific) AIReach OS Configuration Report. If anyvalues are not as specified, change them to the specifiedvalues.a. System Capability – For instructions concerningSystem Capability configuration, see page 4–17.b. Transport configuration – See page 4–18.c. MSC Configuration – See page 4–19.d. HLR Configuration – See page 4–21.4. Configure the link between the Controller and the PBX:a. On the Controller, click Start → Settings →Control Panel.b. Double–click the System icon.c. Click the Environment tab (shown below).8.1Connecting theController to thePBX
1026209–0001 Revision B Connecting to external equipment 8–3d. In the System Variables listing, search forSRM_USER_SIDE and SRM_OPERATOR:SRM_USER_SIDE0 (default) – Set this variable to 0 if the Controller ison the network side of the ISDN interface.1 – Set the variable to 1 if the Controller is on theuser side of the ISDN interface.SRM_OPERATORProtocol used on the ISDN link to the PBX:4ESS (default)Other possible values: DMS100, N12, and 5E10If the variable is not present, the default value isapplied.If the default value is acceptable, no action isrequired if:- The variable is not listed (because if thevariable is not listed, the default is effective) or- The variable is listed with the default valuee. If you need to change a value and the variable ispresent:i. In the list of System Variables, click thevariable name to select it.The variable and value appear in the boxes atthe bottom of the window.ii. Change the value to the correct setting.iii. Click Set to save the value.iv. Reboot the Controller so the change will takeeffect.f. If you need to change a value and the variable is notpresent:i. Click on any variable name in the list ofSystem Variables.The variable and value appear in the boxes atthe bottom of the window.ii. In the Variable box at the bottom of thewindow, delete the variable name and enter thenew variable name.iii. In the Value box immediately below theVariable box, delete the value and enter thecorrect value.iv. Click Set to save the value.v. Reboot the Controller so the changes will takeeffect.
1026209–0001 Revision B 8–4 Connecting to external equipment Follow the instructions in this section to obtain and install aSecure Socket Layer (SSL) certificate:(SSL provides data encryption between the Controller and theIS–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:\>) entercd C:\Program Files\spst3. At the DOS prompt (C:\Program Files\spst\>),create the files csr.pem and spst.key by entering:ssleay.exe req –new –nodes –out csr.pem –config install\ca\ssleay.cnf4. Enter the information indicated below when prompted.Substitute customer–specific information inside the brackets[ ] as appropriate.Country Name (2 letter code) [US]:State or Province Name (full name) [Maryland]:Locality Name (city, town, etc.) [Germantown]:Organization Name (company) [Hughes Network Systems]:Organizational Unit Name (division) [Wireless Office Service]:Common Name (webserver hostname) [209.84.215.36]:For Common Name (webserver hostname), enterthe IP address of the gateway’s hostname. Ask the gatewayprovider what to use for the common name.5. The program ssleay.exe generates the files csr.pemand spst.key in the spst folder.6. Use Notepad to open csr.pem and change the lineBEGIN CERTIFICATE REQUESTtoBEGIN NEW CERTIFICATE REQUEST7. At the end of the csr.pem file, change the lineEND CERTIFICATE REQUESTtoEND NEW CERTIFICATE REQUESTRequest a certificate via e–mail from the appropriate serviceprovider representative, with the csr.pem file edited in steps 6and 7 above attached.The service provider representative sends back the informationyou need to complete a certificate. (See Figure 8-1 for an exampleof a certificate.)To complete the certificate, refer to Figure 8-1 and follow theseinstructions:8.2Installing the SSLcertificateCreating the requestfileRequesting thecertificateCompleting thecertificate
1026209–0001 Revision B Connecting to external equipment 8–51. Copy the <WOSC Certificate Follows> block ofinformation, starting with (and including) the header––––BEGIN CERTIFICATE––––and ending with (and including) the footer––––END CERTIFICATE––––2. Paste the block just copied at the beginning of thespst.key file created in step 3 on page 8–4.3. Save the modified spst.key file created in steps 1 and 2above as spst_c.pem.4. Open the file spstca.pem.5. If the CA certificate has already been installed—that is, if<CA Certificate Follows> is already included inthe file, as shown in Figure 8-1, proceed to the next section,Installing the certificate.6. If the CA certificate has not been installed, follow thesesteps:a. Copy the <CA Certificate Follows> blockof information, starting with the header––––BEGIN CERTIFICATE––––and ending with the footer––––END CERTIFICATE––––b. Paste the block just copied at the end of thespstca.pem file.NoteThe CA certificate may already be included in thespstca.pem file.c. Save the modified file created in steps a and b asspstca.pem.
1026209–0001 Revision B 8–6 Connecting to external equipment Figure 8-1 Example of a signed SSL certificate> ===================<WOSC Certificate Follows>====================>> WOS Certificate follows:>> –––––BEGIN CERTIFICATE–––––> MIICozCCAgygAwIBAgIBQTANBgkqhkiG9w0BAQQFADBoMQswCQYDVQQGEwJVUzEf> MB0GA1UEChQWQVQmVCBXaXJlbGVzcyBTZXJ2aWNlczEQMA4GA1UECxMHVERHIExh> YjEmMCQGA1UEAxMdVERHIExhYiBDZXJ0aWZpY2F0ZSBBdXRob3JpdHkwHhcNOTkx> MTA4MTkzMjI0WhcNMDQxMTA2MTkzMjI0WjCBjjELMAkGA1UEBhMCVVMxETAPBgNV> BAgTCE1hcnlsYW5kMRMwEQYDVQQHEwpHZXJtYW50b3duMR8wHQYDVQQKExZIdWdo> ZXMgTmV0d29yayBTeXN0ZW1zMSAwHgYDVQQLExdXaXJlbGVzcyBPZmZpY2UgU2Vy> dmljZTEUMBIGA1UEAxMLR01UV01EQUJEMDEwgZ8wDQYJKoZIhvcNAQEBBQADgY0A> MIGJAoGBANFkiH/w8GNzFYX94D5amyPVuFH2kCVfF5SkS3oLyDlyoLtVuQifA+kf> KXFAfy7FK7XSrWSwWTUusHt3RpQeNecpVDZLWV+yXEw8zV/G07RbUCLzSC+DETsX> vSAfp48MkVXgMaSSiChuzKQxo2Rbzuwe9/t2ndI0UpLA8row18z9AgMBAAGjNjA0> MBEGCWCGSAGG+EIBAQQEAwIAgDAfBgNVHSMEGDAWgBST+NNwPh0m0K0ZheiYX9yL> buzkSTANBgkqhkiG9w0BAQQFAAOBgQADlh72BvdvtxnEueo7TbuOtbBwpmq8Uby3> 5ST+U7is6XpkaYJP7FucsEamoPJH/DeO9Z3z/slha/QKvjQMX3W/Vadqg2kHk8QE> XzR9HNHRss2xUs7F5c6ECbEwF3ciKpVZzzU1ACo9U7cp7qolWp1c782Jl1I31s8u> lmjJ7NJ7Ww==> –––––END CERTIFICATE–––––>>> ====================<CA Certificate Follows>=====================>> –––––BEGIN CERTIFICATE–––––> MIICiDCCAfGgAwIBAgIBATANBgkqhkiG9w0BAQQFADBoMQswCQYDVQQGEwJVUzEf> MB0GA1UEChQWQVQmVCBXaXJlbGVzcyBTZXJ2aWNlczEQMA4GA1UECxMHVERHIExh> YjEmMCQGA1UEAxMdVERHIExhYiBDZXJ0aWZpY2F0ZSBBdXRob3JpdHkwHhcNOTgw> NzMxMjI0MzEyWhcNMDAwNzMwMjI0MzEyWjBoMQswCQYDVQQGEwJVUzEfMB0GA1UE> ChQWQVQmVCBXaXJlbGVzcyBTZXJ2aWNlczEQMA4GA1UECxMHVERHIExhYjEmMCQG> A1UEAxMdVERHIExhYiBDZXJ0aWZpY2F0ZSBBdXRob3JpdHkwgZ8wDQYJKoZIhvcN> AQEBBQADgY0AMIGJAoGBAKKVRDrifhgJJYri2bJDEKebKu5L+1OzNVESS5DkgtGR> UOA7eAhodsPqe7+kYr1WRtc8hou8Baglc406IbdtKPxh3i+nkXeQ9gkKjhZhrrAM> sl2EkvzgmyAz9mtjdmFyGNWSXBgIWYy7mrQQn/S5Rx7NyrYwcB4aeH+W4tXJ1maH> AgMBAAGjQjBAMB0GA1UdDgQWBBST+NNwPh0m0K0ZheiYX9yLbuzkSTAfBgNVHSME> GDAWgBST+NNwPh0m0K0ZheiYX9yLbuzkSTANBgkqhkiG9w0BAQQFAAOBgQByb81c> yIa8tDY8L23gQXjVs+Mjsk9+WqyjQH/jMcoQusnH2dKXcJuj2LJiDZd0SHNvM8nz> NrsxvW+YWjNDwE9626o6vxroR7V9lrJIzWSYSgrySNZvLC7SdhIr41AxrlBI028R> MKH5M/KKr8PIre/JorP8rnn6hCjGynSnGkraEw==> –––––END CERTIFICATE–––––>
1026209–0001 Revision B Connecting to external equipment 8–7Install the SSL certificate:1. Open the AIReach Office Application if it is not alreadyopen.2. Select Configure → NSS → Systemwide to open theSystem Configuration window.3. Click the Transport tab.4. In the WOS to Gateway Server Address line, enter thegateway address and port number. (Obtain these from thegateway provider.)5. Click Save.6. By default, the IS–41 link is configured to operate in securemode. If the IS–41 interface is operating in clear mode,make these changes:a. Enter the clear mode address and port in theTransport window.b. Edit the startup.dat file in the bin directory ofthe current release: Change the router startup optionfrom –ATTSSL to –ATT (clear mode).7. Click the ROUTER application on the taskbar to verifyrouter connectivity (heartbeat received) to the IS–41gateway.If the gateway connection is active, the ROUTER windowdisplays messages indicating that heartbeat has beenreceived:If a heartbeat is not received, ping the gateway to try to determinewhere the problem is. If you cannot resolve the problem, notify theservice provider representative responsible for establishing IS–41connectivity.Installing the certificate
1026209–0001 Revision B 8–8 Connecting to external equipment Once the SSL link has been established and heartbeats arereceived from the gateway, repoint the AIReach OS HLR to themacro HLR, as follows:1. From the AIReach Office banner menu, select Configure→ NSS → SystemWide.2. Select the Line Range tab.3. Select the AROSC Name.4. Change the HLR Point Code to an invalid but non–zeronumber, such as 1.1.1.5. Restart the Router application by closing the Routerwindow.6. After the router restarts and heartbeats resume, update theBSC point code with the new remote point code:a. Open a Command Prompt window and entercd %aros_root_dir%\bin\mscb. To open the file containing the remote point code,enternotepad inst1.iniNote the value of the remotepc entry in this file.c. Close inst1.ini.d. In the Command Prompt window, entercd %aros_root_dir%\bine. Enternotepad inst1.inif. Change the value of the localpc entry to the valueof remotepc noted in step 6b.g. Save the file.h. Reboot the Controller.8.3Repointing the HLR
1026209–0001 Revision B Connecting to external equipment 8–9If a second LAN card is required for an administrative LAN,follow the instructions below to install the second card and LANcard driver:Install the second LAN card in chassis slot 3, according to themanufacturer’s instructions.NoteThe second LAN card must be the same brand and model as the LANcard shipped from the factory. Any exceptions must be approvedthrough the TAC.To install the driver for the second LAN card:Editing gwroutes.bat1. Power up the Controller.2. Use Notepad to open the file C:\gwroutes.bat.3. Remove the comments from the linesroute DELETE 0.0.0.0androute ADD –p 0.0.0.0 mask 0.0.0.0 xxx.xxx.xxx.xxx4. Replace xxx.xxx.xxx.xxx with the IP address for theadministrative (second) LAN card.Obtain the IP address from the customer’s networkadministrator.5. Save the changes.Install the driver1. Click Start → Settings → Control Panel.2. Double–click the Network icon to launch the networkingwindow.3. Click the Adapters tab.There should be two adapters listed.4. Click Add to open the new adapter card window.5. If a driver was provided with the new LAN card, click onHave Disk … to use the drivers provided with the LANcard.6. Place the floppy disk or CD containing the driver into theController and select the appropriate disk drive.7. If a driver was not provided with the LAN card, select theLAN card from the list of drivers shown.8. If a driver was not provided and is not listed, contact TACto obtain the correct driver.9. Follow the on–screen instructions to install the driver.10. Close the Network window.8.4Installing a secondLAN card and driver(optional)Installing the LAN cardInstalling the LAN carddriver
1026209–0001 Revision B 8–10 Connecting to external equipment Entering the IP address1. Enter an IP address for the LAN card:a. For the IP address, enter the administrative IP addressprovided by the customer network administrator.b. Use a subnet mask value of 255.255.255.0 unlessotherwise instructed by the network administrator.c. Do not enter a value for the default gateway.2. Click the DNS tab and enter the IP address provided by thecustomer network administrator for the DNS server. If noDNS server is available, leave this field blank.3. Close all remaining network windows.The software prompts you to reboot the Controller.4. Click OK.5. After the Controller reboots, verify that the IS–41 routerreconnects—if it was previously connected: Verify thatexternal IP addresses can be reached using a web browseror by pinging a remote address.
1026209–0001 Revision B Connecting to external equipment 8–11The AIReach OS can be configured to page the system operatorwhen 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 isfactory–installed on the System Controller.Instructions for installing the external modem and configuring thepager information are given below.If the customer does not want to use alarm paging, proceed toChapter 3.Alarm paging can be set up to use one or two analog lines. Theadvantage of using two lines is that alarm pages are delivered evenwhen someone is dialed into the Controller. The disadvantage ofusing two lines is the cost of the second line. The decision to useone or two lines should be made by the customer.Follow these instructions to install the external modem:If one analog line is used:1. Connect the line to the input jack on the internal modem.2. Daisy chain the analog line from the internal modem to theline–in jack on the external modem.3. Connect the external modem to the serial port (COM1) onthe back of the Controller.4. Attach the power cable to the modem and to an outlet, andmake sure the modem power switch (if present) is on.5. Provide the dial–up number to the TAC—that is the directinward dialing (DID) number of the line coming into theinternal modem.If two analog lines are used:1. Connect one line to the input jack of the internal modem.2. Connect the other line to the input jack on the externalmodem.3. Connect the external modem to the serial port (COM1) onthe back of the Controller.4. Attach the power cable to the modem and to an outlet, andmake sure the modem power switch (if present) is on.5. Provide the dial–up number to the TAC—that is the directinward dialing (DID) number of the line coming into theinternal modem.NoteIf two lines are used, the line used for alarm paging does nothave to be a DID line.8.5Enabling alarmpagingInstalling the externalmodem
1026209–0001 Revision B 8–12 Connecting to external equipment Configure the AIReach OS with the operator’s pager, mobilephone, or beeper information, as explained below. (The HipLinksoftware must already be installed.) NotesIf the AIReach OS is configured to direct alarm pages to a mobilephone on the AIReach OS, the mobile phone may not receive analarm page in the event of an outage.If you need assistance using HipLink, call the Cross Communi–cations support hotline at (630) 964–4282.Required informationObtain the following information from the customer:•Pager number•PIN (for pagers)•MIN (for mobile phones)•Maximum character lengthEditing the ArosPageInfo.dat fileYou must enter the operator and page information in the fileC:\HipLink\ArosPageInfo.datA sample file is located inC:\%OMC_ROOT_DIR%\config\ArosPageInfo.datTo configure an operator to receive critical and major alarm pages:1. Use Notepad to editC:\HipLink\ArosPageInfo.dat, as explained in thefollowing steps:2. Edit ArosPageInfo.dat to include: PagingEnabled yes(Entries in ArosPageInfo.dat are not case–sensitive.)3. Uncomment “UserData” (remove “ # ”) and change theinformation to the Controller name or number (10characters maximum), for example:UserData AROSC1In this example, AROSC1 is a text string that uniquelyidentifies the Controller.If alarms will be sent to a beeper ornon–alphanumeric pager, use numbers only.When an alarm occurs, the Controller name or number youenter is displayed on the pager.Configuring theAIReach OS for alarmpaging
1026209–0001 Revision B Connecting to external equipment 8–134. Uncomment (remove “ # ” from) the appropriate lines inArosPageInfo.dat, and add appropriate information toidentify the pager or beeper type, service provider, and (forpagers only) personal identification number (PIN):Required for alphanumeric pagers:pagerType alphaserviceProvider <provider ID>pin <operator PIN>Use the provider ID for the customer’s service provider,as listed in Table 8-1 :Table 8-1 Supported alphanumericservice providersProvider/service name Provider IDAirTouch 408 AIR408AirTouch 602 AIR602Alert 702 ALR702American Pager 210 AMP210American Pager 800 AMP800American Paging 512 AMP512Ameritech 314 AMT314AmeritechIL 708 AMT708AT&T Paging 801 ATT801AT&T Wireless 888 ATT888Bell Atlantic 800–1 BAL800Bell Mobility BELLMOCell One 888 CELL1ComTech 800 CTH800Cook Paging 206 CKP206Cook Paging 209 CKP209Cook Paging 415 CKP415DeTeMobil TD1FirstPage FSTPAGMapComm 800 MAP800Metro 200 407 M2_407MetroCall 800 MCL800MetroMedia 800 MTM800Minn Comm 612 MNC612MobileComm 410 MCM410MobileComm 800 MCM800MobileComm 910 MCM910MobileMedia 800 A MM800A
1026209–0001 Revision B 8–14 Connecting to external equipment Table 8-1 Supported alphanumericservice providersProvider/service name Provider IDMobileMedia 800 B MM800BMobileMedia 804 MM_804MobileMedia 817 MM_817Nextel 312 NXT312Nextel 415 NXT415Nextel 510 NXT510Nextel 630 NXT630Nextel 708 NXT708Nextel 847 NXT847Nextel 847–344 NEXTELPacBell 415 PAC415PageBridge 407 PBR407PageMart 800 PMR800PageNet Nationwide 800 PAGENEPage New England 800 PNE800Page New York 716 PNY716PageNet 404 PNT404PageNet 408 PNT408PageNet 415 PNT415PageNet 503 PNT503PageNet 510 PNT510PageNet 602 PNT602PageNet 617 PNT617PageNet 619 A PN619APageNet 619 B PN619BPageNet 714 PNT714PageNet 800 CA PN800CPageNet Nationwide PAGNETPageNet Nationwide 888 PNT888PageNet 818 PNT818PageNet 908 PNT908PagePlus 918 PPL918Pagesouth 910 PSO910ProNet 510 PRN510SkyTel 707 SKY707SkyTel 800 SKY800SkyTel 2–Way SKY2WYSkyTel Nationwide 800 1SKYTELSprint SPRINT
1026209–0001 Revision B Connecting to external equipment 8–15Table 8-1 Supported alphanumericservice providersProvider/service name Provider IDTNI Paging 800 TNI800Touch Tel Paging 510 TTP510US West 520 USW520Westlink Paging 602 WLP602Westlink Paging 801 WLP8011For SKYTEL alphanumeric users who have apin number instead of an 800 number, thedialup number will be 1–800–679–2778. (SeeCreating a new provider ID below.)Required for numeric pagers:PagerType numericServiceNumber <service provider phonenumber>PIN <operator PIN>Required for beepers:PagerType beeperBeeperNumber <beeper number>Required for alphanumeric mobile phones:pagerType alphaserviceProvider <provider ID>min <operator MIN>Required for numeric mobile phones:PagerType numericServiceNumber <service provider phonenumber>MIN <operator MIN>Sample entries for ArosPageInfo.dat:Sample entries for alphanumeric Skytel pager with PIN number 8863647:pagingEnabled yespagerType alphaperviceProvider SKYTELpin 8863647
1026209–0001 Revision B 8–16 Connecting to external equipment Sample entries for numeric pager with phone number888–886–3647 and PIN number 348593:pagingEnabled yespagerType numericserviceNumber 18888863647pin 348593Sample entries for beeper with beeper number 703–580–2077:pagingEnabled yespagerType beeperbeeperNumber 17035802077Creating a new provider IDIf the customer’s paging provider or service is not listed in Table8-1 , follow the procedure illustrated below to create a newprovider ID.The steps below illustrate how to add a new phone number for aservice provider and create a new provider ID. In this example, thenew provider is a TAC service provider with the phone number1–800–679–2778:1. Double–click the HipLink icon in the Windows systemtray.2. Select Modify → Network service.3. Click New.4. In the Network description field, enter a description toidentify the service (30 characters maximum):Tac New Service5. Click the Phone field.The Network Key field now shows TACNEW (in all capitalletters). This is the service provider name (6 charactersmaximum) to be entered in the ArosPageInfo.dat file.(See step 4 on page 8–13.)6. Enter the phone number (800–679–2778) in the phone field.7. Set the maximum message length to 200 characters.NoteIf the service supports a message length of less than 200characters, the message may be truncated.8. Leave all other (default) values as they are.9. Save the modified Network service definition.10. Enter TACNEW as the service provider name in theArosPageInfo.dat file, and save the file.
1026209–0001 Revision B System testing 9–1 Chapter 9System testingThis chapter addresses the following tasks:•Testing RF coverage – page 9–1•Conducting performance tests – page 9–2Verify operational performance by completing the PerformanceTest Checklist referred to in Section 9.2. This verification is thefinal step in commissioning the AIReach OS.Using a test cell phone, perform a walk–through of the entirecustomer site to confirm AIReach OS RF coverage and recordsignal strengths:1. Test interior coverage, with the customer representativepresent:Record signal strength readings at the test points outlined inthe (customer site–specific) AIReach OS RF EngineeringPlan.Immediately notify the HNS TAC if:•The RF coverage is not as specified in the RFEngineering Plan•Signal strength readings inside the facility are 5 dBmabove or below the specified values2. Test exterior RF coverage, with the service providerrepresentative present:a. Record signal strength readings at the test pointsoutlined in the RF Engineering Plan.b. Make sure coverage does not extend beyond 30 feet(9.1 meters) from the building: Make a call inside thebuilding, walk outside, and walk away from thebuilding.The call should drop from the AIReach OS (andreselect to the macro network) before you are 30 feet(9.1 meters) from the building.Immediately notify the HNS TAC if:•The RF coverage is not as specified in the RFEngineering Plan•Signal strength readings outside the facility arestronger than specified values9.1Testing RF coverage
1026209–0001 Revision B 9–2 System testingTo complete installation of the AIReach OS, conduct performancetests as follows:1. Obtain the Performance Test Checklist from your AIReachOS Program Manager.2. Complete this checklist by performing each listed test andchecking the associated box after each test is successfullycompleted.NoteA customer representative should witness the performancetests.3. Sign the completed checklist.4. Obtain the customer’s representative’s signature.5. Send the completed Performance Test Checklist to the HNSInstallation Manager.6. Correct the Configuration Report to reflect the “as–built”AIReach OS installation.7. Correct (red line) the Configuration Report to reflect the“as–built” installation.8. Copy the AIReach OS default.cfg file to a floppy disk.To find the AIReach OS current release directory, whichcontains default.cfg, enter: cd %AROS_Root_Dir%from the DOS prompt.9. Send the corrected Configuration Report and default.cfgfloppy disk to the HNS Installation Manager.9.2Performance testing
1026209–0001 Revision B Installation inspection 10–1 Chapter 10Installation inspectionThis chapter briefly discusses the installation quality inspection.When all the initial AIReach Office subscribers have been enteredinto the Controller, complete the Installation Quality Assurance(QA) Inspection Checklist. Obtain this checklist from yourAIReach OS Program Manager.Invite a customer representative to accompany the personperforming the QA inspection.Complete the Installation Quality Assurance (QA) InspectionChecklist as follows:1. Check the Y box when an item is complete or the N boxwhen an item is NOT complete (discrepancy).2. Correct any discrepancies and initial the associatedCLEARED box when the discrepancy is corrected.3. Sign the checklist when the inspection is complete.4. Obtain the customer’s representative’s signature.5. Send the completed Installation Quality Assurance (QA)Inspection Checklist to the HNS Installation Manager.
1026209–0001 Revision B Provisioning 11–1 Chapter 11ProvisioningThis chapter explains the procedure for provisioning permanentsubscribers. To provision temporary subscribers (visitors, forexample), see page 4–20.After the system has been installed and verified, provision thesubscribers as follows:1. If not already connected to the system, click the Connectbutton in the Connect window to display the main AROSCConfiguration window.2. Select Configure → NSS → HLR.3. Click the MIN Range tab to display the HLR Configurationwindow.4. Select the specified AROSC Name from the dropdown list.5. Enter the specified MIN range values, then click Save tosave them.6. Repeat step 5 until the information for all subscribers isentered.NoteWhen using Allocation Type, Individually Allocated,information must be entered for each subscriber.7. Click the LDN Range tab.8. Enter the LDN range values, and then click Save to savethem.9. Repeat step 8 until the information for all subscribers isentered.NoteWhen using Allocation Type, Individually Allocated,information must be entered for each subscriber.10. When the information for all subscribers is entered, clickClose to return to the main AIReach Office window.11. Select Configure → Subscriber.12. Click the Identification tab to display the SubscriberProvisioning window.(Initially, this window may contain no data.)11.1Provisioningpermanentsubscribers
1026209–0001 Revision B 11–2 Provisioning13. Select the specified AROSC Name from the dropdown list.14. Enter each subscriber’s information, including LDNextension, MIN, and ESN. Then click Save.NoteObserve the status bar above the option windows. If thestatus bar is red, a subscriber information error exists. Usethe vertical scroll bar to display the error message. Beforeproceeding, review the message and correct the error. Thesoftware shows a Successful Load message when thesubscriber information is entered correctly.
1026209–0001 Revision B Remote Client 12–1 Chapter 12Remote ClientThis 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–3The Remote Client can be installed on a Windows 95, Windows98, or Windows NT computer to provide access from a remotelocation to the AIReach OS. The Remote Client provides thegraphical user interface that allows you to access the SystemController and AIReach Office software application. Through theClient, you can execute Controller functions from the remotecomputer.The remote access service is typically provided by the MicrosoftWindows Remote Access Server (RAS). RAS answers incomingphone connections and provides a PPP connection. Once a PPPconnection is established, the remote computer (client) functionsas if it were on the same physical network as the Controller. ALAN intranet connection can be used as an alternative to RAS.Typically, the System Controller is placed in a secure, limitedaccess area with the PBX. A separate operations room is typicallyused for daily PBX and AIReach OS tasks, such as adding usersand deleting users. If desired, these operations can be performedon a remote computer.NoteMultiple users can access Subscriber configuration windows at thesame time, but only one user at a time can access Controllerconfiguration windows.To use the Remote Client, the remote computer must have either:•IP connectivity between the remote computer and theController•Dial–in access from the remote computer to the ControllerFor dial–in access, the Controller must have a modem andRAS configured and enabled.12.1AIReach OS RemoteClientRequirements
1026209–0001 Revision B 12–2 Remote ClientFollow these steps to install the Remote Client on a remotecomputer:1. Load the AIReach OS software CD into the computer’s CDdrive.2. Using the Windows Explorer, find the folder calledGUIInst, 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 thequestions.After you complete the installation, InstallShield reboots thecomputer, and the AROS Configuration icon (shown below)appears.If the remote computer is running Windows 95 or Windows 98, youmust change the GUI’s initial environment memory setting:1. Right–click the AROS Configuration icon (shown in step4), and select Properties.2. Click the Memory tab.12.2Installing theRemote ClientWindows 95 orWindows 98
1026209–0001 Revision B Remote Client 12–33. Change the Initial Environment value from the defaultsetting to 2048.4. Click OK.Make sure the Remote Client connects to the Controller:The instructions below are for Windows 95, Windows 98, orWindows NT .1. At the remote computer, double–click the AROSConfiguration icon:The software displays the AIReach Office banner and aLogin dialog box.2. In the Login dialog box, enter:- The name of the Controller you want to connect to(Replace the default entry, Localhost, afterAROSC, with the name of the Controller you want toconnect to.)- User name(No entry is needed if this field is grayed out.)- PasswordThe default administrator password is “abc123.”3. Click Connect.The login window disappears, and the Remote Clientconnects to the Controller you specified.If the Remote Client cannot connect, it displays a messagestating that the connection failed.12.3Testing the RemoteClient
1026209–0001 Revision B Troubleshooting 13–1 Chapter 13TroubleshootingThis chapter includes information for troubleshooting a newlyinstalled AIReach OS; it does not address troubleshooting forroutine (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–8Problems with System Controller cardsMake sure the card is properly seated in the Controller backplanesocket. Check cables and connections (if applicable). Make sureall DIP switches and jumpers on the card are set correctly—asexplained in Section 2.5 (page 2–13).Problems with a Quad T1 card or T1 lineTo diagnose problems with a Quad T1 card or T1 line, access theDigital Trunk Monitor utility on the Controller:1. At the DOS prompt, entertrunkmon –bXwhere X can be 0 to n–1, where n = the number of Quad T1 cards in the systemThe utility is shown in a Command Prompt window:13.1Controller problems
1026209–0001 Revision B 13–2 TroubleshootingIndications that a T1 trunk is good are:Alarms: NONEFrame sync: OK2. Press F3 or Esc to exit.3. At the DOS prompt, enter Exit to close the CommandPrompt window.(See also Section 13.4, Picocell alarms.)Picocell won’t bootIf a picocell or picocells won’t boot:•Verify that the correct picocell IP addresses are entered inthe Controller•Add picocell IP addresses if necessaryVerify that the correct picocell IP addresses are entered in theController:1. Select Start → Program Files → Command Prompt todisplay a Command Prompt window.2. At the DOS prompt (C:\>), enter ipconfig to displaythe system’s IP configuration:13.2Picocell problemsChecking the IPaddresses
1026209–0001 Revision B Troubleshooting 13–33. In the “Ethernet adapter TXn0002” section of theconfiguration screen, make sure the correct IP addresses aredisplayed for the picocells to be installed in the system.An IP address must be listed for each picocell, in sequentialorder, as illustrated below: Picocell IP Address1 69.1.1.2542 69.1.2.2543 69.1.3.2544 69.1.4.254 .. ..NotesWhen a picocell boots up, it is assigned the next available IPaddress. Only picocell IP addresses are assigned to theTX2000 IP card.You will need to add picocell IP addresses (as explained inthe next section) if:•The number of picocell IP addresses is less than the number of picocells to be installed in the system•The picocell IP addresses do not correspond insequence to the picocells installedNotesThe number of addresses configured can exceed the numberof picocells; this will not cause a problem. Up to eight addresses can be configured.4. At the DOS prompt (C:\>), enter exit to return to theWindows desktop.
1026209–0001 Revision B 13–4 TroubleshootingYou need to add picocell IP addresses only if the number ofpicocell addresses is incorrect, as explained in the previoussection (Checking the IP addresses). Skip this section if thepicocell IP addresses are configured correctly.If you need to add picocell IP addresses:1. Select Start → Settings → Control Panel → Network →Protocols.This opens the Network window:2. Select TCP/IP → Properties → IP Address.3. Highlight the NMS TXn000 LAN adapter <CP.1> fromthe Adapter pulldown list and click Specify an IP address.Adding picocell IPaddresses
1026209–0001 Revision B Troubleshooting 13–5This opens the Microsoft TCP/IP Properties window:The initial TXn000 IP address must be 69.1.1.254 with aSubnet Mask of 255.255.255.0.Leave the Default Gateway field blank.4. Click Advanced.This opens the Advanced IP Addressing window:5. Click Add under IP Addresses.
1026209–0001 Revision B 13–6 TroubleshootingThis 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 Xis the next available number in sequence, that is, 2, 3, 4, 5 ...The Subnet Mask is always 255.255.255.0.NoteThe Add button is not activated until an IP Address is entered.7. Repeat step 6 until a picocell IP address and subnet mask isentered for all the picocells installed in the system.Cells do not loadLEDs on the Quad T1 card should show green for each connectedport. If the LEDs do not show green, check the following:•The wiring for proper wire schedule, crimps, etc.•The power connections to the picocells.•The software loads under the BTS tab. It should be set todefault settings.•The serial numbers under the BTS tab. Make sure the serialnumbers are correct and that the correct cells are connectedto the correct port.If some cells have booted, but others have not, substitute anon–booting cell for a booting cell and change the serial numberunder the BTS tab. Replace any faulty cells with spare cells andcontact TAC.DCCHs are not availableCall TAC.13.3General operationalproblems
1026209–0001 Revision B Troubleshooting 13–7Phones do not lock or registerIf the phones do not lock or register, check:•The phone programming•The subscriber entries on the provisioning screens•The DCCH configurationMobile phones cannot contact each otherIf two mobile phones cannot call each other, check:•The PBX connection LED on the rear of the SystemController.•That the PBX administrator has activated the T1 andentered the phantom numbers correctly.•That all cells are listed under MSC Configuration, BSCConfiguration.•The dialing plan in the configuration information. Makesure the information has been entered correctly.Coverage and handoff problemsCall TAC in case of:•Bad signal strength•Dragging calls•Frequent handoffs•System Controller cutoffs•Signal strength outside the building
1026209–0001 Revision B 13–8 TroubleshootingTable 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 alarmWhen critical or major alarms occur, the Alarm LED on thepicocell front panel is red. When a minor alarm occurs, the AlarmLED is orange. When an information alarm occurs, the AlarmLED is not lit: the information is sent to the System Controller forinformation only.Figure 13-1 LEDs on front of picocellT0001003PowerGreen - Voltage normalOrange - Low voltageAlarm (Controller)Off - NormalOrange - Minor alarmRed - Major alarmTemperature (power supply)Green - NormalRed - Exceeds 75° CPowerTempAlarmAlarm LED is orange whilethe Controller boots.NoteThe LED information above is for production picocells. LEDcodes may be different for pre–production picocells.13.4Picocell alarms
1026209–0001 Revision B Troubleshooting 13–9Table 13-1 Picocell alarms Name Alarm Severity Meaning Suggested ActionWBSU Rebooting 2180 Info WBSU has been rebooted Perform WBSU startupproceduresWBSU Restart 2181 Info WBSU has been warmbooted Perform WBSU startupproceduresGet Time–of–dayFailed 2185 Minor WBSU could not contactWOSC time server to gettime–of–dayCheck IP address of timeserverCPU Busy 2188 Info CPU idle time < 5%CPU Available 2189 Info CPU idle time > 5%Master OscillatorFailed 218A Critical Master oscillator failed Replace master oscillatorPower SupplyVoltage Alarm 2281 Critical Power supply output isout of range Service requiredSoftware ImageFile Corrupt 2380 Major Download software imagehas CRC error Check software downloadimage on WOSCSoftwareDownloadStarted2381 Info Software download inprogressSoftwareDownloadCompleted2382 Info Software downloadfinishedAbis Queue Full 2383 Minor Abis receive buffersusage is 75% ofmaximum capacitySuspend forwardmessaging to WBSU untilAbis Queue AvailableAlarm receivedAbis QueueAvailable 2384 Minor Abis receive buffersusage is below 25% Resume forwardmessaging to WBSUCard Insertion 3280 Info Card has been inserted Setup cardCardReboot/Reset 3281 Minor Card has been rebootedor reset Setup cardCard Removed 3282 Minor Card has been removed Decommission card andassociated protocolstacksCard Failed 3283 Major Card does not respond Decommission card andassociated protocolstacksTraffic ChannelFailed 5280 Minor Fatal error in protocolstack Decommission and thenre–commission protocolstack
1026209–0001 Revision B Maintaining Quad T1 card 14–1 Chapter 14Maintaining Quad T1 cardsThis 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–9To add a Quad T1 card, see Sections 2.4 through 2.8.The instructions in this chapter are not part of the initialinstallation procedure. They are provided in case you need toreplace, move, or remove a Quad T1 card.If you need to replace, move, or permanently remove (delete) aQuad T1 card, you must exercise special care because specificinstructions for DIP switch settings, an adapter card, and buscables depend on the slot where the card is installed (or removedfrom).
1026209–0001 Revision B 14–2 Maintaining Quad T1 cardTo replace a Quad T1 card in the same slot, follow these steps:NoteWhen you replace a Quad T1 card in the same slot, do notmake any software configuration changes.1. Shut down the Controller: Click Start → Shutdown, selectShut down the computer?, and click Yes.2. After you see the message indicating that it’s OK to turn offpower to the computer, turn off the Controller powerswitch.3. Remove the Controller cover (as explained on page 2–11).4. Remove any PBX or BTS connections to the back of theQuad T1 card to be replaced.5. Disconnect the H.100 ribbon cable (shown in Figure 14-1)from the card to be replaced.Figure 14-1 H.100 and MVIP bus cablesT000102616H.100 bus cableMVIP bus cableQuad T1 cards456789SlotBus adapter card6. If there are Quad T1 cards in both slots adjacent to the cardto be replaced (on each side), remove the cable from allcards to the end of the cable in either direction (so you canremove the card).7. If the card to be replaced is the first one in a chain of QuadT1 cards (typically in slot 9), remove the MVIP cable also.See Figure 14-1.8. Unscrew the hold–down screw for the card to be removed.9. Remove the card by carefully lifting it up.10. Set the S1 (termination) DIP switches on the new card tomatch those on the removed card. (For the location of theseswitches, see Figure 2-9 on page 2–13.)14.1Replacing a QuadT1 card in the sameslot
1026209–0001 Revision B Maintaining Quad T1 card 14–311. If the removed card was the first in a chain of Quad T1cards, an MVIP–to–H.100 bus adapter card is attached atthe top of the Quad T1 card (Figure 14-1): Unscrew the busadapter card (or use a new bus adapter card) and connect itto the new Quad T1 card, as shown in Figure 14-2.The bus adapter card must be secure and in full contactwith the Quad T1 card.Figure 14-2 MVIP bus adapter card (on the first Quad T1 card)G-17195 F09/30/99Secure adapter card with No. 4screw into Quad T1 cardInsert bus adapterconnection intoQuad T1 cardMVIP bus connectorH.100 bus connector2.1.12. Insert the new Quad T1 card into the slot where the originalcard was removed.Press down carefully to seat the card in the motherboardconnector. Be especially careful if a bus adapter card isattached to the Quad T1 card.13. Insert and tighten the hold–down screw removed from theoriginal card.14. Reconnect the H.100 cable to all Quad T1 cards. Refer toFigure 14-1.15. If the card replaced is the first card in a chain of Quad T1cards, carefully reconnect the MVIP cable. See Figure 14-1.16. Reconnect any PBX or BTS cables to the back of the card.17. Replace the Controller cover.Be careful not to damage the copper finger stock under thefront edge of the cover.
1026209–0001 Revision B 14–4 Maintaining Quad T1 card18. Turn the power switch on and wait for the Controller toboot up.19. After you log in, make sure all AIReach OS softwareapplication buttons are displayed on the Windows NTdesktop (taskbar buttons here are shown vertically stacked):The taskbar may show other applications in addition tothose shown here.If any applications are missing, contact your HNSInstallation Manager.20. Verify that the new card is operational by checking the stateof any BTSs connected to the card and any PBXconnections to the card:Checking the BTS state:a. Open the WOS BSC Application window.b. Select Btsm → State.c. From the dropdown BTS name list, select each BTSlocated on the new card.d. Verify that each BTS has booted up and is Active.Checking a single PBX connection:Place a call from a mobile configured on the systemto a PBX extension or to an LDN, and answer thedesk phone.Checking multiple PBX connections:a. Disconnect all PBX connections except for theconnection on the card to be tested.b. Place a call from a mobile configured on the systemto a PBX extension or to an LDN, and answer thedesk phone.
1026209–0001 Revision B Maintaining Quad T1 card 14–5If you are moving a Quad T1 card to a different slot or replacing aQuad T1 card to a different slot (original card removed from slotx, 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 mayresult in a configuration mismatch. However, if a chassis slot ismalfunctioning or is suspected of malfunctioning, you might wantto move a card.1. Shut down the Controller: Click Start → Shutdown, selectShut down the computer?, and click Yes.2. After you see the message indicating that it’s OK to turn offpower to the computer, turn off the Controller powerswitch.3. Remove the Controller cover (as explained on page 2–11).4. Remove any PBX or BTS connections to the back of theQuad T1 card to be moved or replaced.5. Disconnect the H.100 ribbon cable (shown in Figure 14-1)from the card to be moved or replaced.6. If there are Quad T1 cards in both slots adjacent to the cardto be moved or replaced (that is, on each side), remove thecable from all cards to the end of the cable in eitherdirection (so you can remove the card).7. If the card to be moved or replaced is the first one in achain of Quad T1 cards (typically in slot 9), remove theMVIP cable also. See Figure 14-1.8. Remove the hold–down screw for the card to be removed.9. Remove the card by carefully lifting it up.10. Remove the hold–down screw and blank panel from the slotwhere the card is to be installed and insert the blank paneland screw into the slot the card was removed from.11. If the card is to be replaced, set the S1 DIP switches(termination) on the replacement card to match those on theremoved card.12. If you move a card from the end of a Quad T1 chain to aninside position, set the S1 DIP switches as follows:Card on the inside – Disable termination (S1 OFF)Card on the end – Enable termination (S1 ON)For further details, see Section 2.5.14.2Moving or replacinga Quad T1 card to adifferent slotPhysical steps
1026209–0001 Revision B 14–6 Maintaining Quad T1 card13. If the removed card was the first in a chain of Quad T1cards, an MVIP–to–H.100 bus adapter card is attached atthe top of the card (Figure 14-1): If the card will no longerbe the first one in the chain or the card is being replaced,unscrew the bus adapter card (or use a new bus adaptercard) and connect it to the Quad T1 card that will be thefirst in the chain. See Figure 14-2.The bus adapter card must be secure and in full contactwith the Quad T1 card.You may have to temporarily remove an additional card tomake room so you can install the bus adapter card.14. Insert the Quad T1 card being moved or the replacementQuad T1 card into the proper slot.Press down carefully to seat the card in the motherboardconnector. Be especially careful if a bus adapter card isattached to the Quad T1 card.15. Insert and tighten the hold–down screw.16. Reconnect the H.100 cable to all Quad T1 cards. Refer toFigure 14-1.17. If the card replaced is the first card in a chain of Quad T1cards, carefully reconnect the MVIP cable. See Figure 14-1.18. Reconnect any PBX or BTS cables to the back of the card.19. Replace the Controller cover.Be careful not to damage the copper finger stock under thefront edge of the cover.Follow these steps to configure the moved T1 Quad card or thereplacement card:1. Turn the power switch on and wait for the Controller toboot up.2. After all processes on the Controller have started (asexplained in step 1 on page 2–27), open the AIReach Officeapplication and launch the BSC Configuration/ HW Configwindow.For details, see Section 2.9, steps 1 through 7.Configuring the BTS1. Select the Quad T1 card configured in the PC Slot wherethe moved or replaced card was originally located.2. Click Modify to open the Hardware Configuration window.3. Write down the Card Number of the selected card and theconfiguration for each line.NoteThe Card Number is not the same field as the PC Slot, PCI Bus,or PCI Slot fields.4. Click Close to close the window.Configuring the card
1026209–0001 Revision B Maintaining Quad T1 card 14–75. Click on the BTSs tab of the BTS Configuration window.This window lists all configured BTSs.6. Move any BTSs configured on the Card Number of the oldcard (original card or original card location) to a differentcard number.At this point, the BTSs may be configured on the same cardand port as another BTS.7. To move a BTS:a. Click on the BTS and then click Modify.b. On the BTS Configuration window, change the cardnumber to a different card, then click Accept.Write down which BTSs have been moved so youwill know which ones to move to the new card. Ifthere are no other Quad T1 cards in the system, theBTSs must be deleted and then recreated after thenew card is added. Make sure all associated data,such as RF parameters, are recorded prior todeleting the BTS.8. Click on the HW Config tab to return to the AROSCConfiguration window.9. Click on the card in the old slot location; then click Deleteto remove the card.10. Click Add and enter the information for the new PC slotand the line configuration. Use the information you wrotedown from the old card configuration.For detailed instructions, see Section 2.9, steps 9, 11, and12.11. Click the BTSs tab of the BTS Configuration window.12. Click on any of the BTSs which were previously moved andthen click Modify.13. In the BTS Configuration window, change the card numberto the number of the moved card, then click Accept.The card number is the same as it was originally.14. If you had to delete any BTSs, re–create them now usingthe parameters you previously wrote down.15. Click File → Exit to close the BTS Configuration window.16. From the AIReach banner window, click File → Exit toexit the AIReach Office application.
1026209–0001 Revision B 14–8 Maintaining Quad T1 cardConfiguring the T1 Quad card1. Launch the AROSHWCfg utility by double–clicking on theAROSHWCf . . . (hardware configuration) icon:2. Stop all AROS processes: Click Shutdown AROS and thenclick Yes when prompted, “Do you really want to quit?”3. The AROSHWCfg window lists the Quad T1 boards.4. In the AROSHWCfg window, select the card that has beenmoved by clicking on the PC slot number; then click Deleteto remove the card.5. Click Add to add the moved card, in its new location, backinto the system.6. In the configuration box that appears, click Find Next T1Card.The system should automatically locate the new T1 card.7. If the new card is not found:a. Open a Command Prompt window by clickingStart → Programs → Command Promptb. Enter blocate <Enter>.The system displays a list of all cards. Locate the newboard by finding the PCI bus / PCI slot numbercombination that is not listed in the AROSHWCfgwindow.c. Enter the PCI bus and PCI slot numbers in the NewCard window.8. Enter the new PC slot number.The Find Next T1 Card function automatically enters thecard type (Quad T1) and the new PCI bus and PCI slotnumber.9. Exit the AROSHWCfg the utility: Click Accept and thenOK.10. Reboot the Controller: Click Start → Shut Down, selectRestart the computer?, and click Yes.11. After all processes on the Controller have started, verifythat the new card is operational by checking the state of anyBTSs connected to the card and any PBX connections to thecard.For details, see steps 19 and 20 on page 14–4.
1026209–0001 Revision B Maintaining Quad T1 card 14–9If 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, removethe last card added. If you need to delete a different card (not thelast added), you must:1. Delete the last card added.2. Move the card to be deleted to the position where the lastcard was located.For example, a system has Quad T1 cards in slots 4, 6, and8. The card in slot 6 was the last card added to the system,but the card in slot 4 is the card to be deleted. In thisexample, delete the card in slot 6, and then move the card inslot 4 to slot 6.Follow the steps in the two sections below to delete the last cardadded from the software configuration (Deleting the card from theconfiguration) and then physically remove the card (Physicallyremoving the card).Delete the last card added, as follows:1. Verify which card was the last card added:a. Open the BSC Configuration (HW Configuration)window.For detailed instructions, see Section 2.9, steps 1through 7.b. Select each Quad T1 card and then click Modify.c. Observe the Card Number listed for each Quad T1card.The card with the highest number is the last cardinstalled.d. Click Cancel to close each Quad T1 HardwareConfiguration window.2. Delete the Quad T1 card with the highest number:a. Select the Quad T1 card with the highest number.b. Write down the PC slot for the card you are about todelete.c. Click Delete.3. Click File → Exit to close the BTS Configuration window.4. From the AIReach Office banner window, click File → Exitto exit the AIReach Office application.5. Launch the AROSHWCfg utility by double–clicking on theAROSHWCf . . . (hardware configuration) icon:6. Stop all AROS processes: Click Shutdown AROS and thenclick Yes when prompted, “Do you really want to quit?”14.3Removing (deleting)a Quad T1 cardDeleting the card fromthe configuration
1026209–0001 Revision B 14–10 Maintaining Quad T1 card7. The AROSHWCfg window lists the Quad T1 boards.8. In the AROSHWCfg window, select the card with the samePC slot number as the card previously deleted; then clickDelete to remove the card.9. Click OK to exit the AROSHWCfg utility.10. Shut down the Controller: Click Start → Shutdown, selectShut down the computer?, and click Yes.11. After you see the message indicating that it’s OK to turn offpower to the computer, turn off the Controller powerswitch.To remove the card from the chassis:1. Remove the Controller cover (as explained on page 2–11).2. Remove any PBX or BTS connections to the back of theQuad T1 to be removed.3. Disconnect the H.100 ribbon cable (shown in Figure 14-1)from the card to be removed.4. If the card to be removed is the first one in a chain of QuadT1 cards (typically in slot 9), remove the MVIP cable also.(This cable is shown in Figure 14-1.)5. Unscrew the hold–down screw for the card to be removed.6. Remove the card by carefully lifting it up.7. Install a blank panel in the slot where the card was removedand attach it with the hold–down screw from the card thatwas removed.8. Reconnect the H.100 cable (as necessary) so it connects toall Quad T.1 cards (as shown in Figure 14-1).9. If the card removed had the MVIP–to–H.100 bus adaptercard attached to it (Figure 14-1 on page 14–2), remove thebus adapter card and install it on the card that is now at theend of the Quad T1 card chain. See Figure 14-2 onpage 14–3.10. If the card removed was at either end of the Quad T1 cardchain, set the S1 DIP switches on the card now at the end ofthe chain to ON to enable termination.11. Replace the Controller cover.Be careful not to damage the copper finger stock under thefront edge of the cover.12. Turn the power switch on and wait for the Controller toboot up.13. After all processes on the Controller have started, verifythat the new card is operational by checking the state of anyBTSs connected to the card and any PBX connections to thecard.For details, see steps 19 and 20 on page 14–4.Physically removingthe card
1026209–0001 Revision B Equipment specifications A–1 Appendix AEquipment specificationsThis appendix lists preliminary specifications for the AIReach OSequipment:•System Controller specifications – page A–1•Picocell specifications – page A–4•Picocell power supply specifications – page A–6All specifications in this appendix are preliminary and are subjectto change.The AIReach OS System Controller provides the mobile switchingfunctionality. The System Controller is connected to multiplepicocells to provide wireless coverage and to the internal PBX tointegrate with desktop phones and outside lines.The drive bays are protected with a door that can be latched andlocked.The mechanical requirements are:•Height: 10.47 inches (6 rack units)•Width: 19 inches•Depth: 19 inches•Weight: 50 pounds when all components are installedShipping size•Height: 20 inches•Width: 27.5 inches•Depth: 24.5 inchesWARNINGThe AIReach Office System Controller canweigh in excess of 50 pounds. To avoidpersonal injury or damage to equipment,follow these precautions:•Do not attempt to move or install theSystem Controller by yourself. Twopeople are required for these tasks.•Do not stack more than three SystemController boxes.A.1System ControllerspecificationsSecurityMechanical
1026209–0001 Revision B A–2 Equipment specificationsThe 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 powersource) unit is necessary.The ac input connects to a single phase, two–wire service. Thisinterface occurs through a standard IEC 320 style connector. Thepower cord is of a double reinforced insulation design as requiredby safety agencies.Voltage, frequency, and phaseThe input voltage, frequency, and phase are:•Input voltage:- Low range: 95 Vac to 132 Vac nominal 110–125 Vac- High range: 190 Vac to 263 Vac nominal 230–240 Vac•Input frequency: range 47 Hz to 63 Hz•Input phase: single, three–wire earthed interface•Consumption: < 700 wattsAC input protectionThe System Controller has an internal fuse. Limited protection isprovided from power surges or other transients on the dc input.This meets with the levels provided by IFC–801–4 andIEC–801–2.AC input connectionThe ac input connects to a single phase, three–wire servicethrough a standard IEC 320 connector. The power cord is adouble/reinforced insulation design as required by safety agencies.Surge protectionThe surge requirements on the ac power line meet therequirements of the IEC 61–000–4–5 standards:•±1 kV (DM)•±2 kV (CM)Power drawFor dc power, the maximum power draw of the System Controllerdoes not exceed 400 watts.Bus supportThe System Controller’s single–board computer is capable ofsinking up to 64 mA and source up to 32 mA for the ISA bus.Electrical
1026209–0001 Revision B Equipment specifications A–3The environmental specifications for the System Controller areconsistent with indoor commercial electronic communication products.Table A-1 System Controller environmental specificationsPreliminary specifications – subject to changeOperational Non–operational(unpackaged) Non–operational (packaged)Temperature +5_C to +50_CTemperature gradient of upto 20_C per hour within theoperational temperaturerange–40_C to +60_CHumidity 5% – 85% relative humidityover the operationaltemperature rangeUp to 95% relative humidityover the non–operationaltemperature rangeVibration 0.21 g rms of randomvibrationFrequency PSD(Hz) (g2/Hz)5–350 0.0001350–500*500 0.00005* Slope: –6 dB/Oct2.09 g rms of randomvibrationFrequency PSD(Hz) (g2/Hz)5–100 0.0150100–137*137–350 0.0080350–500*500 0.0039* Slope: –6 dB/OctThe vibration limits fortransport in a turbopropeller aircraft (3g peakacceleration from 50 to 500Hz) apply. The SystemController was tested on allthree axes, 10 minutes peraxis.Swept sine:Freq. g Force Sweep Rate(Hz) (g) octave/min5–50 0.5 0.150–500 3.0 0.25Resonant dwell: the SystemController will not be damagedas a result of a 0.5 g (0 topeak) resonant search, from 5Hz to 200 Hz at a sweep rateof 1 octave per minute,followed by a 5 minute dwellat package resonance.Random:Frequency PSD(Hz) (g2/Hz)5–100 0.0150100–200*200 0.0039* Slope: –6 dB/OctEnvironmental
A.21026209–0001 Revision B A–4 Equipment specificationsTable A-1 System Controller environmental specificationsPreliminary specifications – subject to changeNon–operational (packaged)Non–operational(unpackaged)OperationalSeismicVibration (per NEBS, Zone 4 upperfloors requirement)Frequency Accel(Hz) (g)0.3 0.20.6 2.02.0 5.05.0 5.015.0 1.650.0 1.6Shock 10g at 10 ms, 1/2 sine,three shocks per each ofthree axesNon–operational: 55g at 10ms, 1/2 sine, three axesnon–operational drop: 2 inchdrop complies with BellcoreNEBS–TR–NWT–000063test configurationNon–operational drop: 36inch drop complies withBellcoreNEBS–TR–NWT–000063test configurationAltitude 200 feet below sea level to10,000 feet above sea levelwhen the specificationsmeet temperature andhumidity limits specified55,000 feet above sea levelAcoustic noise does not exceed 50dBA when measured 1 meterfrom the System Controller’s midpoint.The picocells provide the air interface to the mobile subscribers.The picocells are wall–mounted inside customer buildings and areadjusted to provide radio coverage to a given area within thebuilding. The picocells are placed throughout the building toensure complete building coverage. The picocells are connected tothe System Controller.Each picocell is equipped with a locking tab on the mountingbracket and a lock on the picocell housing. The lock is opened andclosed with a key.The dimensions of the picocells are:•Height: 13.2 inches•Width: 12.5 inches•Depth: 5.5 inchesThe picocell weighs less than 20 pounds when all components areinstalled.AcousticsPicocellspecificationsSecurityMechanical
1026209–0001 Revision B Equipment specifications A–5Shipping size•Height:•Width:•Depth:The picocell is line powered using the T1 cable. The picocelloperates over an input dc voltage range of –24 to –54 volts.For dc power, the maximum power draw of the picocell does notexceed 50 watts.The environmental specifications for the picocell are consistentwith indoor commercial electronic communication products.Table A-2 Picocell environmental specificationsPreliminary specifications – subject to changeOperational Non–operational(unpackaged) Non–operational (packaged)Temperature 0_C to +50_CTemperature gradient of upto 8.3_C per hour within theoperational temperaturerange–40_C to +65_CHumidity 10% to 95% relativehumidity, non–condensing 10% to 95% relativehumidity non–condensing,not poweredVibration 0.5–g rms random, 5 to 500Hz, three axes, 10 minutesper axisFrequency PSD(Hz) (g2/Hz)5–350 0.00060350–500 0.000291.5 g peak accelerationfrom 10 to 50 Hz 3g peak acceleration from50 to 500 Hz (Exampletransport in turbo propelleraircraft).Shock 10g at 11 ms, 1/2 sine,three shocks applied toeach of the three axes.Non–operational: 60g at 11ms, 1/2 sine, three shocksapplied to each of the threeaxes.Non–operational drop: 12inch drop complies withBellcore GR–63–CORE,1995 test configurationNon–operational: 36 inchdrop complies with BellcoreGR–63–CORE, 1995 testconfigurationAltitude 200 feet below sea level to10,000 feet above sea levelwhen the specificationsmeet temperature andhumidity limitsElectricalEnvironmentalspecifications
A.31026209–0001 Revision B A–6 Equipment specificationsMaximum RF power output (Equivalent Radiated Power) for the100 mW radio option of the Pico BTS is ±20 dBm with +1/–3 dBaccuracy. 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. The BTS has a nominal dynamic range of atleast 16 dB (from +10 dBm to –6 dBm), adjustable in steps of 1dB. Power is measured at the antenna port.AntennaThe antenna connections are male “SMA” connectors with nominalimpedance of 50 ohms. The return loss is 12 dB minimum. Theconnections are labeled “Antenna A” and “Antenna B”.A power supply is used to power each picocell. The mechanicalspecifications of the power supply are:•Height: 6.58 inches•Width: 4.0 inches•Depth: 1.98 inches•Weight: 22 ounces (excludes cords)The input specifications are:•Input voltage: 100 Vac to 250 Vac –10%, +6%•Input frequency: range 47 Hz to 63 Hz•Current: 2.0 A max. at 100 VAC inputThe output specifications are:•1.875 amps at –48 volts (90 watts)•Combined line and local voltage regulation of ±1%•Transient response of 0.5 ms for 50% local change•Hold time of 18 msec minimum at 120 Vac and 120 msecminimum at 240 Vac.•±10% “square” output current limiting•Short circuit protection•Over voltage crowbarTable A-3 Power supply environmental specificationsPreliminary specifications – subject to changeOperational Non–operationalTemperature 0_C to +50_C –30_C to +85_CHumidity 5% to 95% relativehumidity, non–condensingAltitude 0 feet to 10,000 feetAn area must be available on the wall near the telco wiring blocksand electrical outlet to fasten the power supply to the wall.RF levelsPicocell powersupply
1026209–0001 Revision B Standards compliance information B–1 Appendix BStandards compliance informationThis appendix lists standards compliance information for theAIReach 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–4The AIReach Office System Controller and picocells have beentested and found to comply with the limits for a Class B digitaldevice, pursuant to part 15 of the FCC Rules. These limits aredesigned to provide reasonable protection against harmfulinterference in a residential installation.This equipment generates, uses and can radiate radio frequencyenergy and, if not installed and used in accordance with theinstructions, may cause harmful interference to radiocommunications. There is no guarantee that interference will notoccur in a particular installation. If this equipment does causeharmful interference to radio or television reception, which can bedetermined by turning the equipment off and on, the user isencouraged to try to correct the interference by one of more of thefollowing measures:•Reorient or relocate the receiving antenna•Increase the separation between the equipment and receiver•Connect the equipment to an outlet on a circuit differentfrom that to which the receiver is connected•Consult an experienced radio/TV technician for helpB.1FCC compliance
B.21026209–0001 Revision B B–2 Standards compliance informationType acceptanceFCC Part 22 and 24, Personal Communications Services, October1, 1997. Part 22 – Cellular band. Part 24 – PCS band.Spurious emissionsFCC Part 15, Class B Radio Frequency Devices – Subpart B,unintentional radiators, October 1, 1997 or April 16, 1999EN 55022 Class A, Limits and methods of measurement of radiodisturbance characteristics of information technology equipment,December 1, 1995TelecomFCC Part 68, February 1998SafetyUL 1950 (without D3 deviations), Safety of InformationTechnology Equipment, Including Electrical Business EquipmentEN 60950, Safety of Information Technology Equipment,Including Electrical Business Equipment, 1992CSA C22.2 No. 950, Safety of Information TechnologyEquipment, Including Electrical Business Equipment, March 1,1998ImmunityEN 50082–1, Electromagnetic compatibility – Generic immunitystandard Part 1, Residential, commercial, and light industry, 1997Picocell regulatorycompliance
B.31026209–0001 Revision B Standards compliance information B–3CSA C22.2 No. 950, Safety of Information TechnologyEquipment, Including Electrical Business Equipment, March 1,1998EIA/TIA–232–F, Interface between data terminal equipment anddata circuit terminating equipment employing serial binary datainterchange, October 1997EN 55022 Class A, conducted and radiatedEN 55022 Class A, Limits and methods of measurement of radiodisturbance characteristics of information technology equipment,December 1, 1995EN 60950 “Safety of Information Technology Equipment,Including Electrical Business Equipment” 1992MIL–HNDBK–217F Military Handbook, Reliability Predicationof Electronic EquipmentFCC Part 15, CFR47, Class B Radio Frequency Devices – SubpartB unintentional radiators, October 1, 1997 or April 16, 1999Type acceptanceFCC Part 68 February 1998EmissionsFCC Part 15 Class BEN 55022 Class B with 6 dB or margin on both radiated andconducted unitsPower TransientsIEEE 587 – System Controller power supplies adheres to thesepower transient standardsSafetyUL 1950 (without D3 deviations), Safety of InformationTechnology Equipment, Including Electrical Business Equipment,Third Edition, March 1, 1998ImmunityEN 50082–1, Electromagnetic compatibility – Generic immunitystandard Part 1, Residential, commercial, and light industry, 1997IEC 61000–4–2, electrostatic dischargeIEC 61000–4–3, radiated RFIEC 61000–4–4, electrically fast transientsIEC 61000–4–5, surgeIEC 61000–4–6, conducted RFSystem Controllerregulatorycompliance
B.4B.51026209–0001 Revision B B–4 Standards compliance informationCE compliantCSA950Complies with EMC DirectivesIn Case IEC320 with groundTUV/IEC950UL1950AWS Wireless Office Service System Specification, DocumentWOS–97–01, Rev 1.0The BTS complies with the latest revision of TIA/EIA/IS–136.1Aand TIA/EIA/IS–136.2A.EIA/TIA–232–F, Interface between data terminal equipment anddata circuit terminating equipment employing serial binary datainterchange, October 1997TIA/EIA–568A, Commercial Building TelecommunicationsCabling StandardTIA/EIA–606, Administration Standard for theTelecommunications Infrastructure of Commercial BuildingsCSA Standard T528, Design Guidelines for Administration ofTelecommunications Infrastructure in Commercial BuildingsCSA Standard 529, Design Guidelines for TelecommunicationsWiring Systems in Commercial BuildingsEN 50082–1, Electromagnetic compatibility – Generic immunitystandard part 1. Residential, commercial, and light industry, 1997IS130A, July 1997IS135, April 1995IS136A (updates provided per Terms of Conditions):•IS136.1A specifies the Digital Control Channel•IS–136.2A specifies the Digital Traffic Channel•RF performance complies with the latest revision ofIS–138A, with the exception of delay interval compliance,which is not required for this short–range base stationIS138A (updates provided per Terms of Conditions)IEEE–C62.41 class A and B. The PSS complies with therequirements of this standard.MIL–HDBK–217F Military Handbook, Reliability prediction ofElectronic Equipment, 1992National Electrical Code, Section 800 – latest codeWBSU–WOSC Interface Specification Avalcom document No.A9.20.0002Picocell powersupply complianceOther compliance
C.21026209–0001 Revision B Equipment part numbers C–1 Appendix CEquipment part numbers This appendix lists part numbers for major components of theAIReach OS:•Customer documentation – page C–1•Component part numbers – page C–1For document numbers for AIReach OS customer documents, seethe About section of this manual.Table C-1 lists the major components of the AIReach OS, fieldreplaceable units (FRUs), parts needed for installation, and theirpart numbers.Table C-1 Major AIReach OS components,FRUs, and installation partsComponent HNS part numberSystem Controller and major componentsAROSC System Controller with 1 Quad T1 card, 1 TX2000 IP card,1 LAN card, and 1 conference card1028007–0001CD ROM drive, read/write, internal 9010029–0001Hard drive, 8.4 Gb 9010025–0001Floppy disk drive, 3.5 inch, 1.44 Mb 9010028–0001TX2000 IP card 9010089–0002TX2000 SS7 card 9010089–0001Quad T1 card 9010087–0001Conference card 9010086–0001Ethernet 10/100 LAN card 9010111–0001Modem, V.90/56K voice/fax ISA 9010027–0001System Controller installation partsMVIP to H.100 adapter card 9010118–0001Short MVIP assembly for 1 Quad T1 cards 1028010–0002H.100 ribbon cable (For Quad T1 cards), with 68–position CHAMPconnector1028158–0001C.1CustomerdocumentationComponent partnumbers
1026209–0001 Revision B C–2 Equipment part numbers Table C-1 Major AIReach OS components,FRUs, and installation partsComponent HNS part numberPicocells and picocell componentsPicocell base transceiver station (BTS)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 (novocoder) no scanner; Controller (no radios or scanners); radiospares with vocoder.For specific picocell type and part numbers for your site, refer tothe site–specific AIReach OS Configuration Report.1026426–00xxTransceiver, 800 MHz, 100 mW 1026426–0033Transceiver, 800 MHz, 10 mW 1026426–0034Transceiver, 1900 MHz, 100 mW 1026426–0035Transceiver, 1900 MHz, 10 mW 1026426–0036Scanning receiver (scanner), 800 MHz 1026426–0041Scanning receiver (scanner), 1900 MHz 1026426–0042Picocell power supply with bracket and screws (90–264 Vac/48 Vdc 90 W)1028482–0001Picocell RF cable 1026426–0043Picocell antenna (FRU) { TBD }Picocell terminal block assembly (for connecting DC power supplyto picocell). Terminal block, rail, end bracket, and end cover.1028211–0001Cable, LAN CAT 5, 24 AWG, 4 pr. 9008537–0001RJ–45 connector, plug 9010236–0001Other components17” video, monitor 1600x1200 resolution 9010043–0001Keyboard, compact 104–key with touchpad 9009294–0002Router 9010254–0001Rack mounting items and optionsSlide assembly, steel, 24–inch (allows Controller and monitor to slide)9010132–0001Keyboard Frame 1028301–0001Lock, cordset connector 9007022–0003Junction box panel assembly, 12–port RJ–45 CAT5 9010215–0001Junction box panel assembly, 24–port RJ–45 CAT5 9010216–0001
1026209–0001 Revision B Equipment part numbers C–3Table C-1 Major AIReach OS components,FRUs, and installation partsComponent HNS part numberOther optionsContact your AIReach OS Program Manager for information on the following additionaloptions:Monitor enclosure optionsUPS and power distribution optionsRack frame and frame mounting components optionsRack cable routing optionsRack frame bracing options (for ceiling or cable ladder)Rack extenders (7–inch)Router optionsCSU options
D.11026209–0001 Revision B Updating software; backing up databases D–1 Appendix DUpdating software; backing updatabasesThis chapter includes the following topics:•Updating software – page D–1•Backing up and restoring databases – page D–2A new software release could be a release of the AIReach Officeapplication software, an OMC release, or both.Install the new release during non–business hours. AIReachOffice functions are not available during this time.To install a new release of AIReach software:1. Read and follow all instructions in the software releasenotes or Service Bulletin provided by the TAC.2. Back up the current subscriber database on a floppy diskfollowing the instructions in Section D.2.3. Close the AIReach Office application.4. Exit any other programs that may be running, including anyconnections to remote workstations.CAUTIONWhen prompted during a software reload:“Is the nss database, nss to be createdagain?,” reply N. If you reply Y, you willdestroy parts of the existing database.5. Insert the CD with the new software release into the driveand follow the interactive instructions to install thesoftware.6. Reboot the System Controller.7. Start the AIReach Office application, and make sure themain window (banner with AIReach logo) displays.Updating softwarewith a new release
D.21026209–0001 Revision B D–2 Updating software; backing up databasesTo safeguard system data, create regular backups of all databasescreated and maintained by the AIReach Office software.Databases may be restored to the Controller hard disk, ifnecessary.All AROS software applications are stopped during backup orrestore operations. Any calls in progress are dropped, and nonew calls can be made until the Controller restarts. Therefore,backup and restore operations should be done when there areno users on the network, and users should be informed thatthe system will be down.To backup the AIReach OS databases to a writable CD:1. Close the AIReach OS banner window.2. Load a formatted RW CD into the CD–ROM drive.(If the CD is unformatted, format it before loading it. )3. Enter these commands from a DOS prompt:cd %omc_root_dir%\toolsbackup <CD–ROM drive letter>A db_log.LOG file opens.4. When you see “Export terminated successfully withoutwarning” at the bottom of the log, close the file.If you do not see this message, contact HNS TAC forassistance.Starting the software after backupTo start the AROS software after backup, follow these steps:1. Select Start → Settings → Control Panel.2. Double–click on Services.3. Select WOS LOAD/Monitor and press Start.4. Wait for all processes to start.(For a list of the processes, see the taskbar illustration onpage 3–6, step 4.)5. After all processes have started, you can open the AIReachOS banner window. (Double–click on the AROSConfiguration icon and log in.)Backing up andrestoring databasesBacking up
1026209–0001 Revision B Updating software; backing up databases D–3To restore the databases from a CD to the Controller hard disk:1. Enter these commands from a DOS prompt:cd %omc_root_dir%\toolscleanupdbThe cleanupdb script closes all AROS processes andcleans the databases. After some time, the Controllerreboots itself, but no AROS services start.2. After the Controller reboots, enter:cd %omc_root_dir%\toolsrestore <CD–ROM drive letter>The Controller reboots again.3. Launch the AIReach Office application and verify that thedatabase has been restored. Check the NSS, HLR, MSC andsystemwide configurations.Restoring
1026209–0001 Revision B Index-1IndexAAIReach Office applicationbanner window, 2–28launching, 2–28, 4–2Alarm paging, 8–11Alarms, picocells, 13–8table, 13–9Antenna, picocell, A–6Applications (list of AIReach OS applications),2–27AROS Configuration icon, 2–28AROSC Configuration window, 2–29, 4–3AROSC Name, 4–3ArosPageInfo.dat file, 8–12BBacking up databases, D–2Backplane slots. See Controller, slots, andPicocell, slotsBand scan. See Frequency band scanBanner window for AIReach Office application,2–28Block diagram, 1–2BTCs. See Transceivers (picocells)BTS Configuration window, 4–14Bus adapter card, 2–23, 14–3CCablesH.100 bus, 2–23, 14–2MVIP bus, 2–23, 14–2picocells, 7–7router connections, 5–2test cable (picocell to Quad T1 card), 6–2Cabling, 3–7Controller, 3–5Controller to PBX, 8–2external modem, 8–11picocell, 7–9T1, picocells, 7–11, 7–16wiring flip, 7–16Cards (Controller)adding, 2–11configuring, 2–25DIP switch settings, 2–13fully loaded configuration, 2–10jumper settings, 2–13slot assignments, 2–9standard configuration, 2–1, 2–9types, 1–6verifying configuration, 2–27, 4–4Cell Configuration window, 4–12Conference cardsadding to Controller configuration, 2–31DIP switch settings, 2–18jumper settings, 2–18MVIP bus, 2–23Configuration options, 1–12Configuration Report, 2–1, 2–25, 4–2, 6–1, 7–7correcting to reflect installation, 9–2ConfiguringController cards, 2–25HLR, 4–21Quad T1 cards, 14–6router, 5–2Connectorspicocellsillustrated, 7–10T1 cable, 7–8picocells (illustrated), 6–3Quad T1 card, 6–4Controllercabling, 3–5card types, 1–6cardsadding, 2–11configuring, 2–25DIP switch settings, 2–13fully loaded configuration, 2–10jumper settings, 2–13slot assignments, 2–9standard configuration, 2–1, 2–9verifying configuration, 2–27, 4–4chassis cover, 2–11, 2–24
1026209–0001 Revision BIndex-2checking operation, 3–6compliance information, B–3components, 1–3, 1–6part numbers, C–1configuringcards, 2–25gateway access, 5–7description, 1–1, 1–6dimensions, A–1front panel illustration, 1–5installing, 3–2mounting options, 1–3operating mode, 6–16operating system, 1–2PBX connections, 8–2power indicator, 3–6power requirements, 3–6rack mounting, 3–4setup mode, 6–10slotscard assigned to each slot, 2–9identification, 2–8numbering, 2–8types, 2–8troubleshooting, 13–1unpacking, 2–2verifying configuration, 4–2specifications, A–1electrical, A–2environmental, A–3weight, A–1Cover, Controller chassis, 2–11, 2–24DDatabases, backing up and restoring, D–2Deleting a Quad T1 card, 14–9Description (AIReach OS), 1–1DIP switch settings, Controller cards, 2–13Documentation set for the AIReach OS, xiiEElectrical specificationsController, A–2picocells, A–5Electrostatic discharge precautions, 2–12Enabling alarm paging, 8–11Environmental specificationsController, A–3picocells, A–5External modem, 8–11FFasteners for picocell mounting plate, 7–3FCC compliance, B–1Field test mode (for mobile phones), 6–22Flow chart, installation tasks, 1–8Frequency, 4–10assignment, 4–8band scan24–hour, 7–7, 7–18initial (6–minute scan), 6–10GGatewayaccess, configuring, 5–7IP address, 5–2, 5–7pinging, 5–8HH.100 bus, 2–13cable, 2–23, 14–2Hardware Details window, 2–26Hazard warnings, xvHLRconfiguring, 4–21repointing, 8–8HLR Configuration window, 4–21II/O address. See Jumper settings and DIP switchsettingsIcon, AROS Configuration, 2–28Inspection, quality, 10–1Installation QA Inspection Checklist, 10–1Interference, B–1IP addresses, 5–3Controller, 4–1gateway, 5–2, 5–7LAN card, 8–10picocells, 13–2IRQ (interrupt). See Jumper settings and DIPswitch settings
1026209–0001 Revision B Index-3JJumper settings, Controller cards, 2–13LLAN cards, 2–19driver, 8–9installing a second LAN card, 8–9IP address, 8–10Launching the AIReach Office application, 2–28,4–2LDN (local directory number), 4–22, 11–2LEDspicocells, 6–5, 7–17illustrated, 13–8Quad T1 cards, 6–6illustrated, 6–7Login, 2–28, 4–2remote access, 12–3MMaterials required for installation, 1–12MIN (mobile identification number), 6–23range, 4–22, 11–1Mobile phones, configuration to receive alarms,8–12Modemexternal, 8–11internal, 2–19Mounting, options, Controller, 1–3Mounting – rack mount. See Rack mountingMounting, options, Controller, 2–2Mounting plate, picocell, 1–7fasteners, 7–3installing, 7–2locking, 7–12unlocking, 2–6Moving a Quad T1 card, 14–5MSC Configuration window, 4–19MVIP bus, 2–14cable, 2–23MVIP bus cable, 14–2OOMC software, description, 4–2Operating mode, 6–16Optional equipment, C–3Organization of this manual, xiPPagers, configuration to receive alarms, 8–12Part numbers, C–1Password, 2–28, 4–2, 12–3PBX connections, 8–2checking, 14–4Performance testing, 9–2checklist, 9–2Picocellsalarms, 13–8table, 13–9antenna, A–6cabling, T1, 7–11cell information, 4–12compliance information, B–2components, 1–7part numbers, C–2connecting for testing, 6–2connections at telco closet, 7–15connectors, 7–8illustrated, 6–3pinouts, 7–8controller, 1–7description, 1–2dimensions, A–4installing, 7–2, 7–7preparing for installation, 7–1IP addresses, 13–2LEDs, 6–5illustrated, 13–8line cord, 7–7mounting. See Picocells, installingmounting plate, 1–7fasteners, 7–3installing, 7–2locking, 7–12unlocking, 2–6power requirements, 6–4power supply, 1–7, 1–12, 6–2, 6–4, 7–1connecting, 7–14specifications, A–6power switch, 6–6, 7–12RF levels, A–6scanning receiver, 1–7
1026209–0001 Revision BIndex-4serial numbers, 2–7, 4–15slots, numbering, 6–24specifications, A–4electrical, A–5environmental, A–5RF levels, A–6weight, A–4T1 wiring, 7–16testing, 6–1, 6–17, 6–24transceivers, 1–7troubleshooting, 13–2unpacking, 2–4wiring flip, 7–16pinouts, 7–17Pin assignmentsT1 cable for picocells, 7–8wiring flip, 7–17Pinging the gateway, 5–8Ports. See ConnectorsPower requirementsController, 3–6, A–2picocell, 6–4Power supply, picocells, 1–7, 1–12, 6–2, 6–4, 7–1, B–4specifications, A–6Programming mobile phones, 6–26Programming test phones, 6–22Provisioningsubscribers, 11–1test mobile phones, 6–20QQuad T1 cardsadding to Controller configuration, 2–30bus adapter card, 2–23configuring, 14–6deleting, 14–9DIP switch settings, 2–13H.100 bus, 2–13, 2–23cable, 14–2jumper settings, 2–14LEDs, 6–6illustrated, 6–7MVIP bus, 2–14cable, 14–2ports, illustrated, 6–4removing, 14–9replacing, 14–2, 14–5T1 line settings, 2–30, 4–5Quality inspection of installation, 10–1RRack mountingController, 3–4illustrated, 1–4, 3–3Registering test mobile phones, 6–23Remote access. See Remote ClientRemote Client, 1–2, 12–1installing, 12–2requirements, 12–1testing, 12–3Removing a Quad T1 card, 14–9Replacing a Quad T1 card, 14–2, 14–5Repointing the HLR, 8–8Restoring databases, D–3RF coverage, testing, 9–1RF levels, A–6RJ–45 connectorspinouts for wiring flip, 7–17T1 cable for picocells, 7–8Routerconfiguration example, 5–5configuring, 5–2installing, 5–2supported model, 5–1SSafety information, xv, B–2, B–3SBC (single board computer)DIP switch settings, 2–20jumper settings, 2–20Scanning picocells, checking operation, 6–6Scanning receiver (picocells), 1–7Serial numbers, picocells, 2–7, 4–15Service provider ID list, 8–13Setup mode (Controller), 6–10SID/PSID/RSID (system identification), 4–9,6–21, 6–23, 6–26Slots. See Controller, slots, and Picocell, slotsSpecifications, A–1Controller, A–1picocells, A–4SSL certificate, 8–4example, 8–6
1026209–0001 Revision B Index-5Standards compliance, FCC, B–1Standards compliance information, B–1Subscriber Provisioning window, 6–20Subscribers, provisioning, 11–1Systemblock diagram, 1–2configuration options, 1–12testing, 9–1System Controller. See ControllerSystem description, 1–1System Wide Configuration window, 4–17TT1 line settings, 2–30, 4–5T1 wiring, 7–16Task flow chart, 1–8Test cable, 6–2Test mobile phonesfield test mode, 6–22programming, 6–22provisioning, 6–20registering, 6–23types used for installation, 6–22Testingpicocells, 6–1, 6–17, 6–24programming test phones, 6–22provisioning test mobile phones, 6–20registering test mobile phones, 6–23RF coverage, 9–1scanning picocells, 6–6system performance, 9–2transceivers (picocells), 6–24TLDN (temporary local directory number), 4–20Tools recommended for installation, 1–11Tools required for installation, 1–11Traffic picocells. See PicocellsTransceivers (picocell), 1–7testing, 6–24Troubleshooting, 13–1Controller problems, 13–1picocell problems, 13–2TX2000 cardsadding to Controller configuration, 2–31DIP switch settings, 2–16jumper settings, 2–15MVIP bus, 2–23UUnpackingController, 2–2picocells, 2–4Updating AIReach software, D–1VVerifyingBTS information, 4–14cell information, 4–12Controller card configuration, 2–27, 4–4Controller configuration, 4–2MSC configuration, 4–19network data, 4–9scanning picocell operation, 6–6software download to picocell, 6–5systemwide information, 4–17WWindows taskbar, 2–27Wiring flip, 7–16WOS BSC Application window, 6–8

Navigation menu