Sony Ericsson LBI-38965 installation manual File Name Contents

Page 13

LBI-38965

Channel assignment and channel drop messages contain the following information:

∙Date and time of event to the nearest tenth of a second

∙Type of event (i.e., assignment or drop)

∙Call type (individual clear voice, group clear voice, individual digital voice, group digital voice, data, etc.)

∙Site number or console number

∙Channel number

∙Caller ID

∙Callee ID

3.2.3.5.Time Synchronization

The time of channel event value is derived from the IMC's internal clock. This is slaved to the MOM-PC clock, which can be synchronized externally from a WWVB signal, via a Spectracom clock unit. This unit is available as an option to the MOM-PC. The Spectracom unit includes an internal high-stability reference clock, which maintains synchronization even in the event of loss of the WWVB signal for an extended period. This configuration ensures that RAR timestamps are accurate at all times.

3.2.3.6. Output Records

The BCU creates CDRs by processing the input messages due to channel assignments and channel drops. The format of a CDR record entry is discussed in detail in Appendix A. Each CDR records the following information about each conversation:

∙The Logical Identification (LID) of the caller

∙The identity of the callee (either LID or GID)

∙The location (node, site, and channel number) of each RF channel involved in the conversation

∙The call type (individual clear voice, group clear voice, individual digital voice, group digital voice, data, etc.)

∙A flag indicating which party to bill (caller or callee)

∙The start time of the first call

∙The elapsed time from the start time until the end of the final call

∙The number of channel assignments included in the conversation

∙The total accumulated air time (Note that this is not the same as the elapsed time because of the pseudo hang time, and the effect of multiple channels per call.)

3.2.3.7.BCU Configuration Files

The BCU uses binary configuration files to store various configuration values. The file names and their contents are as follows:

File Name

Contents

SYSTEM.BIN

Specifies system parameters, default pseudo hang times, and billing modes.

UNIT.BIN

Specifies the pseudo hang time associated with each LID.

GROUP.BIN

Specifies the pseudo hang time and the group billing mode associated with each GID.

 

 

These files are located in the 1.2/cnfg directory.

Since they are stored in binary form, these configuration files can be modified only by using the BCU/CAL Configuration Service (BCS) program, which is described in the User Interface Manual (LBI-38967). The BCU is able to operate with no terminal input by using all default values for configuration parameters.

Pending development by Ericsson GE of a system-wide database management strategy, there is a method by which the BCU configuration "database" can be maintained without using BCS to configure each unit manually.

13

Page 12 Page 14
Image 13
Page 12 Page 14
Contents System and Installation Manual LBI-38965 Table of ContentsTable of Contents BCU/CAL Architecture IntroductionCAL Functional Description BCU Functional DescriptionCall Types Supported Physical Description and Compatibility Physical SpecificationsTVME147 CPU BCU/CAL ArchitectureCPU Backwards Compatibility CompatibilityCommon BCU and CAL Operational Specifications SpecificationsBCU Operational Specifications Billing Architecture BCU Operation Overview Billing ArchitectureRF Channel Usage Air Time Group Billing ModeConversations Grouping CallsFile Name Contents Operator Functions Default DataDatabase Elements Unit DataCall Processing CDR Processing ErrorsCDR Processing Call Processing CDR OutputSystem Manager Interface CAL Operational SpecificationsProtocol Supported CAL Operation Overview Additional Product Features Network File SystemHardware Installation InstallationInstallation Contents Diskette Software InstallationParameter Meaning File Name UsageParameter EXPORTS.DAT Configuration FileDirectory Clientip EXPORTS.DAT File Parameters CAL.DAT Configuration FileSITE01 CAL.DAT File ParametersPrerequisites Initial InstallationInstallation Return Default System Accounts First-Time ConfigurationLogin Password Access Level User Information Entering bcs invokes the BCS program PrerequisiteSystem Disk Booting User Information Invoke the BCS program Proper System ShutdownSoftware Upgrades CAL Terminal Server ConfigurationExample Configuration Tips Page Appendix a Edacs Billing CDR Format Billing by Conversation OverviewBilling for Multiple Sites Record EncodingSINGLE-SITE Calls Record LayoutMULTIPLE-SITE Calls MOBILE-TO-LAND Telephone Interconnect CallsName Size Format Range/Values Description Table A.1 Call Detail Record Field DescriptionsTable A.2 Call Types Call Type DefinitionsCall Type Description Valid with Hex Decimal Rec. Type A0-FF Table A.3 Call Type Bit Field Definitions Call Type Bit FieldsCDR File Topics 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 DB-25F Signal Name Function ConnectorTable B.1 WANServer Port Table B.2 WANServer PortTable B.4 WANServer Port Table B.3 WANServer PortDB-25M Connector Signal Name Function BCU/CAL Port Table B.5 BCU/CAL Hdlc Loopback Cable SpecificationFigure B.9 CAL Terminal Server to Distribution Panel Cable A14 INM AC H106 Computer Terminal Appendix C Fault Tolerance Redundant Operation Figure C.1 Edacs Billing Fault Tolerant Architecture
Top Page Image Contents