Ericsson LBI-38965B BCU Functional Description, CAL Functional Description, Call Types Supported

Page 6

LBI-38965

INTRODUCTION

1.1. BCU FUNCTIONAL DESCRIPTION

The main function of the BCU is to generate call detail records (CDRs) to be transferred to an external billing system for invoice generation. To accomplish this, the BCU scans an input stream of activity messages supplied by the IMC, archives these messages in their raw form, uses those messages which indicate channel assignment and channel drop events to calculate air time, and then generates the CDR.

Call Types Supported

All EDACS call types except for the following are supported by the BCU:

1.Console calls.

2.Conventional site calls.

3.Local interconnect calls.

4.System all calls.

NOTE

Non-EDG data calls are only supported if radios are “wide-area enabled” on the site .

1.2. CAL FUNCTIONAL DESCRIPTION

EDACS system administrators require both site monitor and activity download capabilities. These functions are normally supported by the System Manager in conjunction with the Site Controller at each Radio Frequency (RF) System. The CAL provides this capability for EDACS not equipped with a Site Controller.

1.Site Monitor

Provides the system operator at a System Manager terminal with a real-time display of the calls in progress on the RF channels at the selected trunked system.

2.Activity Download

Call activity and system status information are collected by the CAL and buffered in internal memory. Once an operator-defined buffer content threshold is exceeded, the CAL initiates a download of buffer contents to the System Manager. The downloaded information is used to prepare traffic reports on system usage.

In existing EDACS networks, the System Manager communicates with Site Controllers at RF systems using modems and dial-up or leased line connections, routed through a DECServer terminal server. A communications session is set up via a DECServer port between the System Manager and the Site Controller. The System Manager associates the DECServer physical port number with the Site Controller's identity.

Since the IMC is already connected to all the sites, it has centrally available much of the data that individual Site Controllers normally output to the System Manager⎯for all the sites. The CAL connects to the IMC and demultiplexes incoming call activity information messages⎯the same messages that the BCU uses for billing⎯into activity download data and site monitor data to send to a System Manager using Site Controller protocol.

The CAL uses two Internet Protocol (IP) terminal servers on the local area network (LAN) to communicate with the System Manager's DECServer(s). Up to 32 RS-232 asynchronous serial connections are available, 16 per terminal server. One System Manager DECServer port and one IP terminal server port are required per EDACS system being monitored by CAL.

6

Page 5 Page 7
Image 6
Page 5 Page 7
Contents Ericssonz LBI-38965 Table of Contents Table of Contents Introduction BCU/CAL ArchitectureBCU Functional Description CAL Functional DescriptionCall Types Supported Introduction Physical Specifications Physical Description and CompatibilityBCU/CAL Architecture TVME147 CPUCPU Compatibility Backwards CompatibilitySpecifications Common BCU and CAL Operational SpecificationsBCU Operational Specifications Billing Architecture Billing Architecture BCU Operation OverviewConversations Group Billing ModeRF Channel Usage Air Time Grouping CallsContents File NameDatabase Elements Default DataOperator Functions Unit DataCDR Processing CDR Processing ErrorsCall Processing Call Processing CDR OutputCAL Operational Specifications System Manager InterfaceProtocol Supported Additional Product Features Network File System CAL Operation OverviewInstallation Hardware InstallationSoftware Installation Distribution MediaInstallation Diskette UsageIP.DAT File Parameters ROUTES.DAT Configuration FileParameter MeaningEXPORTS.DAT Configuration File Directory clientip EXPORTS.DAT File ParametersCAL.DAT Configuration File CAL.DAT File ParametersInitial Installation PrerequisitesInstallation Installation User Information Password Default System AccountsLogin Access LevelPrerequisite User Information Entering bcs invokes the BCS programSystem Disk Booting Software Upgrades Proper System ShutdownUser Information Invoke the BCS program CAL Terminal Server Configuration # accessConfiguration Tips ExampleThis page intentionally left blank Appendix a Edacs Billing CDR Format Billing for Multiple Sites OverviewBilling by Conversation Record EncodingMULTIPLE-SITE Calls Record LayoutSINGLE-SITE Calls CDR Radix-64 DigitMOBILE-TO-LAND Telephone Interconnect Calls Table A.1 Call Detail Record Field DescriptionsTable A.2 Call Types Call Type DefinitionsCall Type Hex Decimal DescriptionDescription Valid with Rec. Type A0-FF Call Type Bit Fields Table A.3 Call Type Bit Field DefinitionsCDR 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 Table B.1 WANServer Port Connector DB-25F Signal NameCable Pinouts FunctionTable B.2 WANServer Port Table B.3 WANServer Port Table B.4 WANServer Port Table B.5 BCU/CAL Hdlc Loopback Cable Specification DB-25M Connector M/W BCU/CAL Port Signal NameFigure B.9 CAL Terminal Server to Distribution Panel Cable Figure B.10 CAL 32-Port Configuration Computer Terminal Appendix C Fault Tolerance Figure C.1 Edacs Billing Fault Tolerant Architecture Redundant Operation
Top Page Image Contents