Ericsson LBI-38965B installation manual Software Installation, Distribution Media

Page 21

INSTALLATION

LBI-38965

If the BCU/CAL is being connected to a network, plug a MAU (either coaxial or twisted pair) into the 15-pin female connector labeled "ETHERNET" on the TVME-712/M transition module on the rear of the BCU/CAL enclosure and attach the MAU to the network. If the BCU/CAL is being connected to a 10BASE-15 (Thick Ethernet) network, no MAU is required. Attach the transceiver cable directly to the 15-pin connector on the transition module.

If CAL is to be enabled for this installation, then connect the Emulex P2516 terminal server(s) to the same network segment to which the BCU/CAL is connected and switch on the power. Be sure to wait 5 minutes after applying power to the P2516 before continuing on to the next step. Even though it is a separate unit, the terminal server is an integral part of the CAL. The terminal server must be situated near the VAX System Manger's terminal server (DECServer). The ports on the P2516 connect to the ports on the DECServer with RS-232 cables. The port connections will be different for each installation, depending on which sites will be monitored by CAL.

Turn on all power switches and wait for approximately 2 minutes. The following indications signify that the BCU/CAL is functioning properly:

∙The red LEDs on the BCU/CAL are not illuminated.

∙The amber "STATUS" LED on the TVME-147 is lit dimly or is flashing.

∙The green "RUN" LED on the fv5310 is illuminated.

∙The console terminal displays the message Login:

If any of these conditions are not met, then double-check the connections and try to restart the BCU/CAL by switching the power off, waiting 15 seconds, and switching on the power again. If normal operation is not achieved, then leave the power switched on and the network connected. It may be possible to diagnose the BCU/CAL remotely over the network.

The personality of the BCU/CAL unit is set during manufacture, but can be changed by using the product utility, which can be run from the BCU/CAL command line after logging in. For details on this utility, see the User Interface Manual (LBI-38967).

For BCU/CAL operation via the console terminal, refer to the User Interface Manual (LBI-38967).

4.2. SOFTWARE INSTALLATION

The following section describes the software distribution, installation, and configuration of the BCU/CAL application(s).

4.2.1. Distribution Media

The BCU/CAL software is distributed on four 1.44Mb MS-DOS compatible floppy diskettes. The first three disks contain Ericsson PRS executable code, supplied in ASCII S-Record format. The head (first few lines) of the files on these disks identifies the software revision of the distribution.

The fourth disk (Installation Disk 4) contains template ASCII configuration files which are intended to be modified by the end user.

21

Page 20 Page 22
Image 21
Page 20 Page 22
Contents Ericssonz LBI-38965 Table of Contents Table of Contents BCU/CAL Architecture IntroductionBCU Functional Description CAL Functional DescriptionCall Types Supported Introduction Physical Description and Compatibility Physical SpecificationsTVME147 CPU BCU/CAL ArchitectureCPU Backwards Compatibility CompatibilitySpecifications Common BCU and CAL Operational SpecificationsBCU Operational Specifications Billing Architecture BCU Operation Overview Billing ArchitectureRF Channel Usage Air Time Group Billing ModeConversations Grouping CallsFile Name ContentsOperator Functions Default DataDatabase Elements Unit DataCall Processing CDR Processing ErrorsCDR Processing Call Processing CDR OutputCAL Operational Specifications System Manager InterfaceProtocol Supported CAL Operation Overview Additional Product Features Network File SystemHardware Installation InstallationDistribution Media Software InstallationUsage Installation DisketteParameter ROUTES.DAT Configuration FileIP.DAT File Parameters MeaningDirectory clientip EXPORTS.DAT File Parameters EXPORTS.DAT Configuration FileCAL.DAT File Parameters CAL.DAT Configuration FilePrerequisites Initial InstallationInstallation Installation User Information Login Default System AccountsPassword Access LevelUser Information Entering bcs invokes the BCS program PrerequisiteSystem Disk Booting Software Upgrades Proper System ShutdownUser Information Invoke the BCS program # access CAL Terminal Server ConfigurationExample Configuration TipsThis page intentionally left blank Appendix a Edacs Billing CDR Format Billing by Conversation OverviewBilling for Multiple Sites Record EncodingSINGLE-SITE Calls Record LayoutMULTIPLE-SITE Calls CDR Radix-64 DigitTable A.1 Call Detail Record Field Descriptions MOBILE-TO-LAND Telephone Interconnect CallsCall Type Hex Decimal Call Type DefinitionsTable A.2 Call Types DescriptionDescription Valid with Rec. Type A0-FF Table A.3 Call Type Bit Field Definitions Call Type Bit FieldsCDR File Topics Page Appendix B Physical Configuration Details Jumper Settings Figure B.1 Tvme 147SA1 Single-Board Computer Figure B.2 Tvme 712/M Transition Module Figure B.4 fv5310 Main Board Figure B.5 fv5310 Mezzanine Card Scsi Connector Pwr Cable Pinouts Connector DB-25F Signal NameTable B.1 WANServer Port FunctionTable B.2 WANServer Port Table B.3 WANServer Port Table B.4 WANServer Port DB-25M Connector M/W BCU/CAL Port Signal Name Table B.5 BCU/CAL Hdlc Loopback Cable SpecificationFigure B.9 CAL Terminal Server to Distribution Panel Cable Figure B.10 CAL 32-Port Configuration Computer Terminal Appendix C Fault Tolerance Redundant Operation Figure C.1 Edacs Billing Fault Tolerant Architecture
Top Page Image Contents