Sony Ericsson LBI-38965 installation manual CDR File Topics

Page 42

LBI-38965

7. CDR FILE TOPICS

CDR files are located in the 1.2/cdr directory. All closed CDR files are named tdddhhmm.CDR, where

ddd

= Day of the year the record was created (001 to 366).

hh

=

Hour of the day the record was created (00 to 23).

mm

=

Minute of the hour the record was created (00 to 59).

The maximum number of call records which will be written to a single CDR file is controlled by the “bcs” utility. Refer to LBI-38967 for further discussion of CDR file control parameters.

A log file (1.2/log/cdr.log) is maintained which contains information regarding when and why a CDR file has been closed. The contents of this file can be useful in customer tuning and diagnostics of the CDR file generation process.

A file with a .CTM extension will exist in the 1.2/cdr directory when the BCU is actively generating CDRs. This is a temporary file which will grow to the user specified size, then be renamed as a .CDR file. Users should never attempt to modify (edit, delete, etc.) the .CTM file.

If the BCU is logging CDR files to an optional DAT tape drive, files with a .CDP will be present in the 1.2/cdr directory. A .CDP is a backup copy of a CDR file which has successfully been archived to tape. The number of days that a .cdp will remain on the disk is also controlled using the “bcs” command.

A-8

Image 42
Contents System and Installation Manual Table of Contents LBI-38965Table of Contents Introduction BCU/CAL ArchitectureBCU Functional Description CAL Functional DescriptionCall Types Supported 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 CallsFile Name Contents Database 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 Installation Contents DisketteFile Name Usage Parameter MeaningEXPORTS.DAT Configuration File ParameterCAL.DAT Configuration File Directory Clientip EXPORTS.DAT File ParametersCAL.DAT File Parameters SITE01Initial Installation PrerequisitesInstallation Return First-Time Configuration Default System AccountsLogin Password Access Level Prerequisite User Information Entering bcs invokes the BCS programSystem Disk Booting Proper System Shutdown User Information Invoke the BCS programCAL Terminal Server Configuration Software UpgradesExample Configuration Tips Page Appendix a Edacs Billing CDR Format Billing for Multiple Sites OverviewBilling by Conversation Record EncodingMULTIPLE-SITE Calls Record LayoutSINGLE-SITE Calls MOBILE-TO-LAND Telephone Interconnect CallsTable A.1 Call Detail Record Field Descriptions Name Size Format Range/Values DescriptionCall Type Definitions Table A.2 Call TypesCall Type Description Valid with Hex Decimal Rec. Type A0-FF Call Type Bit Fields Table A.3 Call Type Bit Field DefinitionsCDR 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 Table B.1 WANServer Port DB-25F Signal Name Function ConnectorCable Pinouts Table B.2 WANServer PortTable B.3 WANServer Port Table B.4 WANServer PortTable B.5 BCU/CAL Hdlc Loopback Cable Specification DB-25M Connector Signal Name Function BCU/CAL PortFigure B.9 CAL Terminal Server to Distribution Panel Cable A14 INM AC H106 Computer Terminal Appendix C Fault Tolerance Figure C.1 Edacs Billing Fault Tolerant Architecture Redundant Operation