Home

lbi-38965 - The Repeater Builder`s Technical Information Page

Contents

1. ADDRESS 147 117 37 226 5 bcuO1 SUBNET MASK FFFFFOOO Table 3 IP DAT File Parameters Paramter _ O Z IP ADDRESS IP address of the BCU CAL in Internet dotted decimal notation HOST NAME Host name of the BCU CAL up to 32 characters long SUBNET MASK IP subnet mask for the BCU CAL Specified as 8 hexadecimal digits in upper case 4 2 1 1 2 ROUTES DAT Configuration File The ROUTES DAT configuration file specifies network routing paths to be established at system boot Typically this file will only be required if the BCU CAL 15 connected to a wide area network where routers exist between the unit and other customer host facilities The template file contains a few example routes which are commented out i e preceded with a character If no network routing is required this file may be omitted or left unaltered A log file 1 2 log routes log is generated on each system boot This file contains a summary of successful routing additions as well as any errors detected during processing of the ROUTES DAT file 20 LBI 38965 Network routes are specified the following form type destination_ip gateway gateway_ip Table 4 ROUTES DAT File Parameters Parameter type Keyword for the type of route being added either host or netw
2. 11 92 2815 Channel Usage IH uyu ones yau avon 12 9 2 ed O ISI ONS Quan ned cen 12 312 3 9 7 GIEOUD B HD Nie yanasa dur d 12 S Foe EUIS uu 23 s 12 2229595 HME S vri c DEOR ZO OTI a abans bau u end Paus doe E Doct edu as 13 2 3 ONE OUE RECO SENE or 13 3 2 Te DC U C ntieurattoD Qt 13 32 958 Operor Pune ONS m a stas a T techo uto Ds 14 Database Vc MICAS sas tet ua tod Or N Rod Ra 14 I2 al ane e sI ayu 15 32 Call etal Weed us yuta ccn 15 This manual is published by Ericsson Mobile Communications Inc without any warranty Improvements and changes to this manual necessitated by typographical errors inaccuracies of current information or improvements to programs and or equipment may be made by Ericsson GE Mobile Communications Inc at any time and without notice Such changes will be incorporated into new editions of this manual No part of this manual may be reproduced or transmitted in any form or by any means electronic or mechanical including photocopying
3. 569 Feb 01 1994 10 47 SYSTEM BIN rwxrwxrwx 1 131072 Feb 01 1994 10 47 UNII BIN 33 CINXIWXIWX le 16384 Feb 01 1994 10 47 GROUP BIN USER ACTION Two system parameters may need to be set If the BCU CAL is operating in a Multi Node StarGate configuration the IMC NIM slot number needs to be defined If the BCU CAL service area IMC has a Jessica interconnect system installed the IMC PIM slot number needs to be defined These parameters must be set appropriately for the BCU to correctly provide billing for calls involving these sites i e StarGate or Jessica They are required by the CAL to simulate secondary drops from the site s it is providing service for If the parameter NIM or PIM slot does not apply it should be set to zero default value These parameters are defined using the BCU CAL Configuration Service BCS program BCS is discussed in detail in LBI 38967 The following example is provided for reference to get the BCU set up and running as quickly as possible PREREQUISITE 1 Obtain the IMC slot number of the NIM and PIM modules if any 2 If not already logged into the BCU CAL log in under the root account as previously discussed Enter the following commands at the indicated prompts USER INFORMATION Entering bcs invokes the BCS program DoHt gt bes Welcome to the BCU CAL Configuration Service BCS System Administrator privilege acknowledged USER INFORMATION Enter
4. B 8 5 Archive Maynard 4324NP DA ukla Suka B 8 LBI 38965 Serial Port 4 J5 98 J9 Factory u System Controller Set Pus 2 AM27C040 J6 oo Factory oo Set U22 U30 G 9 00 0 G 0 G 0 G4 0 0 G 0 0 J1 J2 Figure B 1 TVME 147SA1 Single Board Computer B 3 LBI 38965 B 4 T 2 J26 1 J21 5 VIT 114 2 17 J9 ED 2 14 2 14 ul JI 142 4 2 142 14 RG CE oy R8 8 R9 B RIB 9 Figure 2 TVME 712 M Transition Module Terminators Installed Figure B 3 TVME 147P2 Adapter Board LBI 38965 311115435 N 211915 ago ooo aca 0220 ocooogooo coooococ 51452 55 153 feb 2 S 8 5100 ooo ooo goo ood oon
5. MN Port 1 MW MENU s Port 0 i i _ j ___ R TSTN 2 _ O 196 REN 2 __ 2 8 59 4 DCEReay ___ _____22 23 X DCEREADYN O _ 2 06 bDTEREADYP DTEReay aa 23 DIEREADYN 0 LBI 38965 WIRING TABLE FROM ITEM 1 TO ITEM 2 SIGNAL WIRE WIRE COLOR RJ12 1 DB25 6 DTR ITEM 5 WHITE RJ12 2 DB25 3 TXD ITEM 5 BLACK RJ12 3 DB25 7 GND ITEM 5 RED RJ12 3 DB25 7 GND ITEM 5 GREEN RJ12 4 DB25 2 RXD ITEM 5 YELLOW RJ12 5 DB25 20 DSR ITEM 5 BLUE DB25 6 DB25 8 DCD ITEM 4 WHITE DB25 4 DB25 5 RTS CTS ITEM 4 WHITE lt TBD 75 2 PIN 1 NOTES 1 FABRICATE CABLE TO LENGTH INDICATED NOTE CONNECTOR ORIENTATION CAREFULLY B 12 9X PIN 1 PIN 13 Figure B 9 CAL Terminal Server to Distribution Panel Cable Ov OC N 14 25 LBI 38965
6. ReceiveData C0 16 C08 12 X TSETN y __ A 06 0 RSETN AB 19 TU M RSN A05 13 CIEN C06 06 X DCEREADYP DCEReady O AO 292 DCEREADYN CoU 23 Table B 2 WANServer Port 1 Lm umm omm pL connector _ ____ 09 116 1 TSETN o Als O REN o A6 19 J O AB 13 06 X DCEREADYP __ A15 22 X DCEREAD TN Ci 23 DTEREADYN B 9 LBI 38965 Table B 3 WANServer Port 2 ee mm omm L Connect _ 1 Oo C7 16 RNN C24 12 TSETN 002 A22 0 REN A24 19 RSN OO An 13 C C2 J 06 DCEREADYP DCEReajy ARB 22 DCEREAD N 2 C23 j 235 Table B 4 WANServer Port mm WC MG Connector _ C25 16 C3 1 J TSTN REN A32 19 RIEN A29 13 CIEN C C30 06 DCEREADYP DCERead ___ A31 22 DCEREADYN y C31 23 DTEEADYN LBI 38965 Table 5 BCU CAL HDLC Loopback Cable Specification oo
7. 14 INMAC H1060 1 14 INMAC 1060 1 14 INMAC 1060 1 gt a lt 91 1HOd 1 4 150 CLV 100186000 V 1908 1904 100186000 CLV 190185000 71304 0 10 gc 100186000 100186000 CLV el LYOd 621804 100186000 190188065 CLV 211909 82 1904 s 5 150 CLV 100186000 V E 5 1 8084 12 1808 2 2 100186000 CLV 90 86022 21V 5 011804 921804 gt 190186000 CIV 100186000 21V 2 N 61304 901804 Em 100186000 100186060 CLV _ gt _ 81804 1804 z 5 i 190186000 CLV 100186000 CLV 2 CO lt S o 5 5 2 eo i 5 5 7 ox L1uOd 861404 2 s 2 LOOL8E0cc 100186000 2 91808 22 1 04 190186006 CLV 190186000 CLV 8 1404 iz 1804 190186060 100186000 O 04 021804 100186002 21V 190186000 CIV 1HOd 611304 9013 0 ZLY 190186000 CLV 21804 81 1HOd LOOL8E0cc 90182022 ZLY 1808 ZL 1808 100185000 V z 5
8. Redundant MIM processors are added to each RF System interface within the IMC A duplicate CAM is added which connects to the redundant BCU CAL and tape drive REDUNDANT OPERATION The primary and redundant MIM processors operate in a hot standby configuration 1 once primary unit failure 15 detected the backup becomes the active processor with minimal disruption to calls in progress The redundant CAM BCU CAL and tape drive are operated as on line mirror duplicates This eliminates any changeover operation in the event of failure of one BCU CAL or its associated components the remaining unit continues to operate and process call activity
9. ago obo og og aoopoocogo og goanoooogoo gooo 75300 WARN Server Figure fv5310 Main Board B 5 LBI 38965 PORT 0 DTE WITH DCE PROVIDING RX AND TX 5 IMC CAM INTERFACE DCE WITH DCE CLOCKING DTE MEZZANINE CARD Figure B 5 fv5310 Mezzanine Card LBI 38965 SCSI Connector 1 RN2 RN1 J6 Motor Terminators Removed oo Parity SCSI ID 2 Factory Set Figure B 6 Maxtor MXT 1240S Hard Disk B 7 LBI 38965 TEAC FD235HS 711 Factory Set Jumpers Terminators RA2 Removed SCSI ID 1 SCSI Conn Figure B 7 Teac FD235HS 711 Floppy Disk SCSI Connector HOC Reserved Self Test mium DDS Pass Through Compression Off Parity On SCSI Mode SCSI 1 OFF Terminators Removed SW 8 765 4 3 2 1 a SCSI ID 3 Figure B 8 Archive Maynard 4324NP DAT B 8 LBI 38965 2 CABLE PINOUTS BCU CAL Internal Wiring VME P2 Backplane connector of WANServer card to DB 25 connectors on backplate Table B 1 WANServer Port 0 ae po Connector Connect AON 02 XMTP TransmitData _ _ __ _ xr _ AOL B
10. BCU CAL Input Data Each raw activity record RAR contains the following information Day and time of event accurate to 0 1 second Type of event 1 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 to match assignments with drops Caller ID Callee ID Digitally dialed PSTN digits for outgoing interconnect calls perc a Pos em Note The dialed digits correspond to the digits sent by a radio to the interconnect system to initiate interconnect call dual tone multi frequency overdial digits sent by the radio once an interconnect call is In progress are not registered by the BCU 3 1 2 Throughput The BCU CAL s interface to the IMC is capable of receiving a peak data rate of 192 raw activity records RARs per second A buffer stores incoming at the peak rate of 192 per second for a minimum of 300 seconds 5 minutes 3 1 3 Hard Disk Interface The BCU CAL provides nonvolatile storage of the BCU CAL operating software CDRs system configuration data system defaults and subscriber attributes The hard disk provides concurrent support of call record processing and the operator interface 3 1 4 Operator Interface Most BCU CAL operator functions are capable of being performed without impacting or reducing the capacity of the call processing functions below specifie
11. oerver su Password system system is the default privileged account password This can be changed later Set the terminal type used to configure the server Server change port 1 type VT100 Define the IP address and subnet mask of the terminal server The IP address terminal server ip must reflect the associated address defined in the CAL DAT file The subnet mask subnet mask should be the same as defined for the BCU CAL in the IP DAT configuration file Server set server ip terminal server ip Server set server subnet mask subnet mask 31 LBI 38965 For each site defined in the CAL DAT file configure the associated port on the terminal server as follows Server gt gt change port port_no access remote Server gt gt change port port no type softcopy Server change port port no autobaud disabled Server change port port no speed 19200 Server change service PORT port no TCP port no port port no telnet disabled Server change port port no queuing disabled Server change port port no flow control disabled TCP port no is the value defined in CAL DAT for a particular site EXAMPLE Assume that the file CAL DAT has the following two site entries System Manger site 2 is connected to port 3 on the distribution panel and System Manager site 10 is connected to port 6 on the distribution panel SITE 02 PASSWD SJ TREO SITBSUAZIP Jub kas usc oap Terminal server IP address SITEO02Z
12. 1736 bytes copied 4427 bytes copied lt LOADER gt Floppy disk has been unmounted lt LOADER gt USER ATTENTION REQUIRED Remove the current installation floppy diskette Insert the next installation disk if any Strike lt to continue USER ACTION Remove Installation Diskette 4 Press the Enter key lt LOADER gt Processing file 01 02 cnfg IP DAT Setting IP address 37 220 Assigning host name bcu01 Setting subnet mask OxFFFFFOOO0 LOADER LOADER LOADER LOADER LOADER Loading file 01 02 108dsS BC A SX from the hard dusk First load complete 393126 bytes loaded Loading Tirte from the hard Second load complete Application load complete 55692 bytes loaded 448818 bytes loaded LOADER Hard disk has been unmounted LOADER Transferring program control to BCU CAL lt BCU CAL gt System startup Wed May 4 13 54 47 1994 lt BCU CAL gt Beginning boot WanServer board lt BCU CAL gt WanServer boot complete lt BCU CAL gt Initializing memory and global objects lt BCUY BeGimnind applica clon uwnmustsltatrotn lt BCU CAL gt Checking system directories lt BCU CAL gt Created default LOG directory path 012027164 SBCUZCAL Created default CDR directory paths O1 02 c0r lt BCU CAL gt Created default RAR directory path 01 02 rar lt BCU CAL gt Checking s
13. Call MSGTrunked ____ 00 ____ 5254 8284 Invalid Call 9 5 85 Group Digital Voice System Call MSG Trunked 0 ____ 5658 8688 Invalid Call Type 98 5 89 Group Clear Voice Update System All MSG Trunked 00 ___5 5 9092 Invalid Call Type 88 SD 93 Group Digital Voice Update System Call MSG Trunked 00 Invalid Call o 60 9 Individual Clear Voice Jessica Bill Caer or 61 63 9799 Invalid Call Type 9 656F 101111 Invalid Call e ____ _____ 72773 114115 InvalidCallType Po 7678 118420 Invalid Call Type e Group Clear Voice Emergency Jessica Bill Callee 7A IC 122 124 Po 125 Group Digital Voice Emergency Jessica Bill Callee a Invalid Call 128 individual Clear Voice Jessica Special Call Bill Caller 8183 129131 Invalid Call Type e 858F 133 143 Invalid Call 90 144 Individual Clear Voice Jessica Special Call Bill Calle 0 Invalid Call Type p 94 148 Individual Digital Voice Jessica Special Call Bill Calle 03 E 95 9F 149 159 Invalid Call Type 0 160 255 Reserved Types LBI 38965 Call Type Bit Fields The call type values have b
14. LBI 38965 Mobile Communications EDACS BCU CAL Billing Correlation Unit Centralized Activity Logger System and Installation Manual LBI 38965 TABLE OF CONTENTS c 4 II BCU FUNCHONAL DESCRIPTION uuu u aaa 5 12 CAL FUNCTIONAL DESCRIPTION uuu u u etes ette gt ___ _ asas 5 2 PHYSICAL DESCRIPTION AND COMPATIBILITY UU uu 6 2515 PH YSICADSPEOCIPICA IIONS RUNE 6 2 2 Ala ARCHIVE CUR E mee MD qn od qo basu cdi as duds 7 COMPATIBILITY oa esate 9 GI LO TID Su ET 10 3 1 COMMON BCU AND CAL OPERATIONAL SPECIFICATIONS 10 DAC S Stem MING tus esu 10 351522 TROU DUE Santu 10 M Di ML Tm 10 SM OME u astra aa 10 32 SPECIFICATIONS aaa a 10 32 45 SUDDETTA De Database ie uuu m busana 10 Ar t ee pi uo u la 11 der yasa
15. pim NIM slot 32 PIM Sot EG USER ACTION Exit BCS which returns the operator the pSH gt prompt BCS gt exit pSH t 4 2 2 2 System Disk Booting After software has been installed on the BCU CAL system disk the BCU CAL will use these files for any subsequent re boot The following example shows the typical console output observed when the BCU CAL boots from its hard disk No user action is required for this process The BCU CAL will immediately begin normal application processing when the boot cycle is complete OS Beginning bootstrap loader DATE May 4 1994 TIME 1 56 23 pm 0o Scanning herd disk for LOADER OX pts OS Loading file LOADER SX from the hard disk OS Load complete 97762 bytes loaded OS Hard disk has been unmounted OS Transferring program control to LOADER module LOADER Installing BCU CAL DATE May 4 1994 TIME 1 56 58 pm LOADER Processing file 01 02 cnfg IP DAT Setting IP address Les LOIS POZO Assigning host name bcu01 Setting subnet mask OxFFFFFOOO 29 LBI 38965 lt LOADER gt Loading file 01 02 loads BC_A SX from the hard disk lt LOADER gt First load complete 393126 bytes loaded lt LOADER gt Loading file 01 02 loads BC_B SX from the hard disk lt LOADER gt Second load complete 55692 bytes loaded lt LOADER gt Application load complete 448818 bytes loaded lt LOADER gt Hard disk has been unmounted lt TOADE
16. server software feature File contents specify NFS client IP address es and the BCU CAL directory s they are privileged to mount Syntax is similar to the UNIX etc exports file CAL DAT Defines the site interfaces from CAL to the EDACS System Manager Contents of this file are directly related to configuration parameters which must be set on the Emulex Terminal Server s 4 2 1 1 User Configuration Files This section discusses the contents of the user configuration files contained on Installation Diskette 4 These files should be modified according to customer requirements When changes are made to the file contents the BCU CAL should be rebooted with the diskette installed in the floppy drive 4 2 1 1 1 IP DAT Configuration File The IP DAT configuration file is provided in template form on Installation Diskette 4 This file is common to both the BCU and CAL feature licenses It defines the unit s Internet parameters on the end user s local or wide area network The following three lines show the default contents of the IP DAT file The values shown in bold print should be modified by the end user Only space characters should be used between the parameter keywords and the end user assigned values Any errors detected in the file will be displayed on the local console during system boot at
17. 1042 9 Invalid Call Type 88 OD B Group Digital Voice or Data Emergency Bill Caller OEIO 1416 InvaidCallType 1214 1820 Invalid Call Type o 1618 2224 InvaidCallType Group Clear Voice Emergency Bill Callee lA IC 2628 InvaidCallType 2 Group Digital Voice or Data Emergency Bill Callee Invalid Call Type i 2 33 Group Clear Voice Special Call Bill Caller 00 2223 3435 99 Invalid Call Type 2 3 Group Digital Voice Special Call Bill Caller 00 262F 3847 999 Invalid Call Type 3233 5051 Invalid Call Type 8 3698 5456 Invalid Call Type Group Clear Voice Emergency Special Call Bill Callee 022000 Invalid Call La Group Digital Voice Emergency Special Call Bill Callee O ___ 40 6264 9 Invalid Call Type 41 65 Group Clear Voice System Call TX Trunked 00 424 6668 Invalid Call Type 8 LBI 38965 Table A 2 Call Types Cont Hex Decimal Rec EC GN s 49 73 Group Clear Voice Update System Call Trunked 0 x 4A 4C 7476 9 Invalid Call Type 40 7 Group Digital Voice Update System Call TX Trunked 0 Invalid Call O __8 51 81 Group Clear Voice System
18. 3 10 Call Processing This section contains specifications on the BCU s call processing capability CDR Processing A record of each conversation is maintained by the system A conversation is a collection of calls detailed by RARs that have been correlated based upon call participants and caller pseudo hang time Each CDR contains the following information Caller billing ID BID Callee BID or GID group ID Call type individual group Digital Voice data interconnect etc Bill flag caller or callee Identification of each RF channel node site and channel Start time of the first call Number of channel assignments included in the conversation Total elapsed time from start time to end of final call Total accumulated node air time to within 0 5 seconds 0 PSTN number dialed on outgoing interconnect calls 1 PSTN line number on incoming interconnect calls a Call Processing CDR Output The call processing software redirects file output to a new file when the current file being written to exceeds a maximum size The system administrator can set this maximum size CDR Storage Requirements The BCU is capable of storing all CDRs from the previous 30 days on its internal hard drive CDR files are maintained on the system for a programmable time period CDR Processing Errors The call processing software recovers automatically from the following error conditions 1 Link time out exceeded
19. communicate between the BCU CAL and the associated port on the terminal server Note that each terminal server port is associated with the site number specified by ss The value port number must be unique for every site defined The following example shows how sites 1 and 2 might be defined in the CAL DAT file SITE 01 PASSWD SITEO1 System Manager Password for the site OLIEOIl IP 147 117 37 10 IP address of the terminal server SITE 01 PORT 5001 TCP port number SITE 02 PASSWD SITEO2 SITE 02 IP 147 117 37 10 SIIBOZ POREI 5002 Configuration Tips The TCP port number selection can be of significance if the BCU CAL is attached to a large or TCP protocol intensive network If you are unsure of TCP port usage on your network consult you network administrator prior to assigning these values In general beginning TCP port definition at 5000 is safe for most applications A convenient rule of thumb is to start at 5000 with the lower digits of the port reflecting the associated site number For example use TCP port number 5010 for site 10 The parameters defined in CAL DAT must be known when the Emulex terminal servers are to be configured Have a hard copy of this file available wh
20. 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 Call Types Supported All EDACS call types except for the following are supported by the CAL Console calls Conventional site calls Local interconnect calls Non EDG data calls LBI 38965 2 PHYSICAL DESCRIPTION AND COMPATIBILITY This section outlines the specifications depicts the physical architecture and provides compatibility information for the BCU CAL Software for the BCU and the CAL are merged into one software package Feature encryption allows or disallows BCU or CAL functionality The two products can also run on the same hardware platform with minor additions for CAL 2 1 PHYSICAL SPECIFICATIONS General Specifications BCU CAL ELMA VME System 12 7 slot enclosure with PSU and integral cooling fan TVME 147 single board computer with TVME 712 M Transition Module Formation WANServer fv5310 Maxtor MXT 1240S 1 2 GB 3 half height 8 5ms hard disk drive internal Teac FD235HS 711 1 44 MB 312 half height floppy disk drive internal Tape Drive Optional with BCU only Archive Maynard 4324
21. which party to bill The choice is determined by a billing mode associated with each group ID or by the default billing mode Individual calls are always charged to the caller except for land to mobile interconnect calls and incoming data calls In each of these cases the ID of the caller or sender of the data 1s unknown thus the call must be billed to the callee 3 2 3 4 Input Messages Input to the BCU consists of a stream of activity messages As a minimum the messages include all channel assignment events and channel drop events generated on EDACS This includes channel assignment and drop from the Jessica Private Branch Exchange PBX Gateway and StarGate interfaces 12 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 1 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 be synchronized externally from WW VB signal via a Spectracom clock unit This unit is available as an option to MOM PC The Spectracom unit includes an internal high stability reference clock which maintains synchronization even i
22. 1 2 indicates that the entire volume may be mounted by the host specified by client_ip client_ip Internet address of the NFS client permitted to mount directory specified in dotted decimal notation If no address is specified it indicates that any client may mount the directory The examples below show several valid export entries in the EXPORTS DAT file HHH Ht EE HH HH EE EH EE HH EE OH HE OO ES EO EEE EO EEE EOE EEE In the following example hosts fallwell and hagee may NFS mount the entire BCU CAL system disk volume 1 2 Host robertson may only mount the BCU CAL cdr directory Any host may mount the log directory tit HH HH Ht HHH HH HH EE EH HE EE EO EEE EO EEE Leay AT DEW 91 2455 host name fallwell Leay 147 11737 248 host name hagee Vay 20249 host name robertson 14274009 any client may mount 4 2 1 1 4 CAL DAT Configuration File The CAL DAT is a mandatory file for execution of the CAL software feature It defines the interface parameters between the BCU CAL and the System Manager The template file defines 32 example sites which are commented out 1 preceded with a character and thus have no effect when the file is processed Entries must be provided for each site interface the CAL will be supporting The informat
23. 190185022 ZLY A L 090LH OVINNI FLV A14 INMAC H1060 1 NOTES ETHERNET THIN WIRE COAX CONNECTOR FOR NETWORK CONNECTION Figure B 10 CAL 32 Port Configuration B 13 LBI 38965 EGE PT NO 19685232701 CONTROL INTERFACE BOARD TO TERMINAL SERVER 1 B 14 14 15 A6P2 46220371001 J2 J3 BCU CAL REAR PANEL IO PANEL TRANSITION MODULE J5 J1 PORTO v J6 Aom DB25F o mO m JJ 29 J2 PORT 1 M gt DB25F D o r UR ATP J3 PORT2 s DB25F Cc m m x Computer gt m O gt m lt Terminal E r r J4 PORT 3 202 22 DB25F 2 m i O E sss m m P E lt 2 7 ASCII Keyboard m JJ m JJ Figure B 11 BCU CAL Rear Panel I O LBI 38965 APPENDIX C FAULT TOLERANCE C 1 LBI 38965 Figure C 1 shows the architecture for a fault tolerant EDACS billing system Primary Backup Console Downlink Downlink Terminal Primar Backup BCU Terminal a To StarGate Figure C 1 EDACS Billing Fault Tolerant Architecture
24. 2 Unmatched channel drops 3 Unmatched channel assignments 4 CAM hardware reset 5 WANServer reset RAR Storage Options The system administrator can choose either to store all RARs to the hard drive or to discard RARs after use by the CAL and or BCU processing software RAR Storage Requirements The BCU CAL can store all raw activity records for the previous 24 hours 3 2 3 11 Call Detail Records A CDR is a series of ASCII characters terminated by a newline NL character The records are variable length but they contain a fixed length segment which is always present followed by zero or more suffix segments There are two types of suffix segments The first is an additional site segment which identifies the sites and channels used in a multisite call The second type of suffix 15 a PSTN phone number field which is appended to a mobile originated interconnect call record and contains the digits dialed by the caller 15 LBI 38965 3 3 CAL OPERATIONAL SPECIFICATIONS This section outlines the specifications that are unique to the CAL personality Refer to Figure 4 for the CAL architecture 3 3 1 System Manager Interface The CAL interfaces to the System Manager s DECServer s via one or two terminal servers capable of supporting up to 32 independent asynchronous RS 232 serial connections The ports on the CAL s terminal servers are connected to the ports on the System Manager s DECServers via RS 232 cables 3 3 2 Protoco
25. 4 Specifically if new changes are made to either the IP DAT or CAL DAT files the BCU CAL should be rebooted with the modified diskette inserted in the floppy drive Note that previous software loads and user configuration files are not destroyed when an upgrade or configuration change is installed The BCU CAL archives up to 3 of the last installations in the 1 2 backup directory These can be retrieved by the operator in the event of problems with a new software installation or errors in the end user modified configuration files 4 3 CAL TERMINAL SERVER CONFIGURATION The CAL feature of the BCU CAL supports up to 2 Emulex P2516 Terminal servers Each terminal server provides 16 serial ports Of these 15 are readily accessible for System Manager site controller interfaces with one port port 1 being used for initial terminal server configuration Temporarily disconnect the Ethernet LAN connection from the terminal server Connect a dumb VT100 compatible terminal to port of the terminal server to be configured This corresponds to port 1 on the BCU CAL distribution panel for the first terminal server and port 17 for the second terminal server The terminal should be configured for 9600 baud start bit 1 stop bit and no parity Log in to the first terminal server under the privileged account If you are greeted with a prompt first execute the following command access If the server requests a password enter CTRL Z
26. COMPATIBILITY The BCU CAL software is compatible with the following IMC and System Manager versions IMC Software V4 01 and later IMC CAM Controller Board P N 19D903299P3 Networks Data VME Controller ROM V1 03 MicroVax System Manager Software V3 01 and later CAL only The System Manager Software version requirement applies only to the CAL feature The BCU feature operates independent of the System Manager Thus the BCU is compatible with any System Manager software version Backwards Compatibility The BCU CAL will function with IMC software versions down to V3 04 with minor performance degradation The following features are not available with IMC software versions older than V4 01 BCU CAL The User Interface stats command will not provide information regarding queued denied system busy and convert to callee channel events CAL Specific e Activity records and site monitoring will not reflect queued denied system busy and convert to callee channel events e The site monitor will not provide current control channel indication LBI 38965 3 SPECIFICATIONS 3 1 COMMON BCU AND CAL OPERATIONAL SPECIFICATIONS 3 1 1 EDACS System Interface The BCU CAL interfaces to EDACS via a full duplex port supporting high level data link control HDLC protocol The BCU CAL will adapt to the data transmission rate to which the Central Activity Module CAM is set to operate 64K or 360K selectable via CAM dip switches
27. IPOPRT S002 ICP port_no used for site 2 SITE l0 PASSWD SITELO S TTE T O TPE yo Job sus SITE 10 SOTO TCP port_no used for site 10 Inserting the information below would configure the terminal server for the values shown above Server gt gt change port 3 access remote Server gt gt change port 3 type softcopy Server gt gt change port 3 autobaud disabled Server gt gt change port 3 speed 19200 Server gt gt change service PORT_3 5002 port 3 telnet disabled Server gt gt change port 3 queuing disabled Server gt gt change port 3 flow control disabled Server gt gt change port access remote Server gt gt change port type softcopy Server gt gt change port autobaud disabled Server gt gt change port 6 speed 19200 Server gt gt change service PORT_6 5010 port 6 telnet disabled Server gt gt change port 6 queuing disabled Server gt gt change port 6 flow control disabled OY OY OY After completing the configuration reconnect the Ethernet LAN connection to the terminal server If a second terminal server is installed repeat the procedure above 32 LBI 38965 Configuration Tips If all 16 ports of a terminal server are needed for System Manager interface first configure 15 of them using a dumb terminal connected to port 1 Port 1 configuration port may then be re assigned to a remote port accessible via a telnet connection Telnet into the terminal server on the OVERRIDE port number an
28. NP 4 8 GB 312 half height 4mm digital audio tape DAT drive internal Console Terminal DEC VT100 or compatible console terminal Terminal Servers CAL only Emulex Performance Series P2516 SLTL 16 ports per terminal server Power Supply BCU CAL 115 230 VAC 47 63 Hz 500W Physical EGE Standard Cabinet BCU CAL 6 rack units 26 67 cm 10 5 in high x 48 26 cm 19 in wide x 49 99 cm 19 68 in deep Environmental Storage Temperature 40 to 85 C Operating Temperature 0 to 40 C ambient Operating Altitude lt 15 000 feet Shipping Altitude lt 50 000 feet Relative Humidity lt 90 non condensing LBI 38965 2 2 BCU CAL ARCHITECTURE The BCU CAL s internal architecture is shown in Figure 2 The individual components and their primary functions are outlined below VMEbus Backplane P2 Adapter Board RS 232 HDLC Common From CAM VME Platform Ethernet SCSI LAN TVME712 M Transition TVME147 CPU Formation WANServer Module 5 Communications m Module Er Tape Drive Floppy P Administrative Terminal Disk TTTTTTTTTTTTTTTT 7 Hard Disk To System Manager NEN Terminal Servers CAL Only Figure 2 BCU CAL Architecture LBI 38965 The BCU CAL is based on a VMEbus computing platform with the following components CPU Technico TVME 147 single board computer based
29. R gt Transferring program control to lt BCU CAL gt System startup Wed May 4 13 58 32 1994 lt BCU CAL gt Beginning boot of 1 5310 WanServer board lt BCU CAL gt WanServer boot complete lt BCU CAL gt Initializing memory and global objects SBCU CAL Beginning application installation lt BCU CAL gt Checking system directories lt BCU CAL gt Checking system configuration files lt BCU CAL gt Checking product feature license lt BCU CAL gt Application installation complete lt K lt x lt K lt x x lt K lt x k lt K lt x lt k lt x k lt lt x lt lt lt x lt k lt lt k lt KK x k ck x k x kok x kok lt x x x lt x x lt Welcome to the EDACS BCU CAL 5 Copyright Ericsson Mobile Communications x Mountain View Road Lynchburg Virginia 24502 p di di di di dir dir dir dir dir dir dir dir dir dir dir dir dis dis dir dir dio di dis di di dir dir dir di di dii dir dir dir dir div di dir dir dir dir dir dir dios dir dis dios dir dir dir di di x x x x lt x x lt System boot complete Wed May 4 13 58 50 lio mmn 4 2 2 3 Proper System Shutdown The BCU CAL must be shut down in an orderly fashion prior to a system reboot This procedure essentially disconnects the link to the IMC CAM gracefully closes any open files especially significant for the BCU and secures the hard driv
30. RIAL PORT on TVME 712 M transition module located in the rear of the BCU CAL enclosure For reference the BCU CAL is delivered preconfigured from the factory in a 19 inch rack Connect the other end of this cable to the console terminal s host port or equivalent If a PC is used as the console terminal then a DB 9 adapter may be needed In either case the serial cable for the console is wired straight through Configure the console terminal for the communications parameters below 9600 Baud No Parity 8 Data Bits Stop Bit 18 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 15 being connected to IOBASE 15 Thick Ethernet network no MAU is required Attach the transceiver cable directly to the 15 pin connector on the transition module If CAL 15 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 DEC
31. SITE CALLS The following diagram shows the layout of the fields in a basic CDR for a single site call The top row shows the field name and number the middle row shows the subfield name and letter if applicable and the bottom row shows the byte offset within the record 2 Node ID No 3 Record ID No 4 Start Date 5 Start Time Lee _ NIE 6 7 Caller ID 8 Callee ID No Type HEN _________ _ _ ___ _______ ____ ____ ____ 9 Elapsed Time 10 Accumulated Air Time 11 No of Channel 12 No of 13 Site of Origin c IKE SEIEN IEEE HE HEC MORE CH Figure 1 Call Detail Record Single Site Call 5 2 MULTIPLE SITE CALLS A CDR may have 0 to n additional fields added beginning at byte offset 70 where n No of Sites 1 The format of the additional fields is identical to the Site of Origin field field 13 and is shown in the diagram below The offset x of the first byte in each additional field is calculated as x 62 13 n Additional Site n Figure A 2 Call Detail Record Additional Site Field 5 3 MOBILE TO LAND TELEPHONE INTERCONNECT CALLS A CDR for mobile to land telephone interconnect call will have an additional field beginning at byte offset 70 This field contains the digits dialed by the caller A mobile to land call never involves multiple sites so the PSTN Telephone Number field is never combined with the Additional Site fi
32. Server 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 15 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 di
33. a network connection the file IP DAT may be left unmodified from that supplied with the release distribution If initial routing entries are desired edit the file ROUTES DAT If the NFS feature is purchased edit EXPORTS DAT It is a template file for configuring NFS clients of the BCU CAL Client entries are specified as a BCU CAL system disk directory followed by the IP address of the client permitted to mount it A log file 1 2 log nfs log 15 generated on each system boot The log summarizes processing of this file indicating what has been exported who received the export and any errors encountered in this file This file 15 processed during the application loading boot phase only Modifications made after the unit is up and running will take effect during the next system boot If the BCU CAL has been purchased with the CAL software feature the file CAL DAT on Installation Diskette 4 must be modified This modification should define each site interface to the System Manager for which the CAL feature is to provide service If the unit is only licensed for the BCU feature the file CAL DAT may be left unmodified from that supplied with the release distribution Reboot the BCU CAL LBI 38965 INSTALLATION 1 Insert Installation Diskette 1 into the BCU CAL floppy disk drive 2 Apply unit power and observe the user console The remainder of the installation is provided by way of example Actual observed output may be slightly di
34. a varying level of system access security The following table defines the initial accounts and their passwords arranged in decreasing levels of access The login name and password are case sensitive These passwords can be changed from their default values and new accounts installed using the passwd command Any new accounts added will have the same level of access as the user account Table 7 Default System Accounts Login Password Access Level Anything This account is the Can access any BCS commands for system configuration Most restricted particularly for the BCS commands Log onto the BCU CAL under the root account The console display will be similar to the following Login YOOL Password Copyright c Integrated Systems Inc 1992 Welcome to pSOSystem pSH t 27 LBI 38965 USER INFORMATION Enter 45 to observe the root level directory files and subdirectories which were created during the software installation process pSH gt 15 BITMAP 2 5 backup etc mnt var EIOSI9X5 bin export rar LOADER SX cdr loads tmp activity ontg log usr USER INFORMATION The following example shows the configuration files for the unit The BIN files were created during the software installation process pSHt cnig pSH gt 18 15 Al 2 L BOOT 622 Feb 1994 10 45 CAL DAT 2 YOOL 892 Feb 01 1994 10 45 IP DAT 2
35. ains up to 32 digits dialed by No the caller The digits are left justified and padded with ASCII SP decimal 32 on the right Accumulated Air 5 Hex 00000 FFFFF The number of seconds of actual air time used on all sites on the Time local node for this call Does not include air time on site 32 which is a remote node 1 12 13 Information on the site of Origin field 13 and any additional sites indicates at least one channel assignment on the indicated 4 LBI 38965 6 CALL TYPE DEFINITIONS Table A 2 contains the typical values of the call type CDR field 6 Note that many call types are invalid and most call types are valid only in conjunction with particular record types CDR field 1 An invalid call type simply indicates that these values are not generated with this version of BCU CAL software They may be used by other EDACS components such as ELI Local Interconnect In developing a billing system to process CDRs the call type bit fields in Table A 3 should be used to identify a particular call type Table A 2 Call Types Hex Decimal Rec Type 00 O Individual Clear Voice Bill Caller 00 01 0 Group Clear Voice 1 00 __02 2 Clear Voice 00 0 0 00 01 04 0 5 ____ Group Digital Voice Data Bill Caller 00 04 6 Digital Voice Bill Caller 07 08 9 Group Clear Voice Emergency Bill Caller OA 0C
36. ances efficient storage with comprehensive resource utilization data 2 BILLING BY CONVERSATION EDACS uses transmission trunking to allocate RF channels Unlike a landline telephone conversation where a single circuit is established at the beginning of the call and disconnected at the end EDACS establishes a new circuit assigns an RF channel each time a conversation participant presses the PTT switch on a radio and disconnects drops the channel as soon as the PTT switch is released Thus a single conversation may result in several RF channel assignments Rather than designate each of these brief transmissions as a call requiring its own CDR the EDACS CDR format permits all of the transmissions making up a single conversation to be recorded in a single CDR The CDR records the elapsed time of the conversation the actual accumulated air time time that an RF channel was in use and the number of transmissions involved A list of the channels used in the call is also part of the record 3 BILLING FOR MULTIPLE SITES EDACS allows calls which originate on one radio site and use RF channels on one or more additional sites The EDACS CDR format accommodates these calls by recording the site number and a list of the RF channels used for each site participating in the call In addition the accumulated air time field in the CDR contains the total air time used on all sites In this case the accumulated air time value will usually be greater than t
37. and recording for any purpose without the express written permission of Ericsson GE Mobile Communications Inc Copyright August 1994 Ericsson GE Mobile Communications Inc LBI 38965 TABLE OF CONTENTS Cont 3 3 CAL OPERATIONAL SPECIFICATIONS 3 3 1 System Manager Interface 3 3 2 Protocol Supported 3 3 3 CAL Operation Overview 3 3 4 Additional Product Features 4 INSTALLATION 4 1 HARDWARE INSTALLATION 4 2 SOFTWARE INSTALLATION 4 2 1 Distribution Media 4 2 1 1 User Configuration Files 4 2 2 Initial Installation 4 2 2 1 First Time Configuration 4 2 2 2 System Disk Booting 4 2 2 3 Proper System Shutdown 4 2 3 Software Upgrades 4 3 CAL TERMINAL SERVER CONFIGURATION APPENDIX A EDACS BILLING CDR FORMAT APPENDIX B PHYSICAL CONFIGURATION DETAILS APPENDIX C FAULT TOLERANCE LBI 38965 1 INTRODUCTION This manual contains installation instructions physical and functional descriptions specifications and usage information for the Enhanced Digital Access Communications System EDACS Billing Correlation Unit and the Centralized Activity Logger BCU CAL A block diagram of the BCU CAL is shown below The BCU CAL works as a subsystem attached to an Ericsson GE Integrated Multisite and Console Controller and can be set to operate as a BCU a CAL or both Each IMC node must have its own BCU CAL BCU and CAL are two separate capabilities which can run independently of each other on the same machine yet
38. d rates Refer to the User Interface Manual LBI 38967 for further information 3 2 BCU OPERATIONAL SPECIFICATIONS This section outlines the specifications that are unique to the BCU personality 3 2 1 Subscriber Attribute Database Each system subscriber and each group defined on the system is assigned a record in the subscriber attribute database This database supports a maximum of 16 383 individual subscribers and a maximum of 2048 groups 10 LBI 38965 3 2 2 Billing Architecture The EDACS billing system architecture is shown in Figure 3 Each IMC is connected to a BCU CAL via a high speed serial communications link using HDLC protocol Downlink Terminal DAT Optional MIM MIM DAT Optional MIM MIM High Speed HDLC Link Pd Ethernet WAN StarGate Customer Billing Mainframe To other IMCs The dotted lines enclose one optional setup for a StarGate multi node billing architecture Figure 3 Billing Architecture 3 2 3 BCU Operation Overview Each RF system sends all call information to the IMC via the downlink This is true for single channel autonomous trunking SCAT Conventional Network Interface CNI basic EDACS and RF systems operating in failsoft mode All call activity information messages received by the IMC are collected by the Central Activity Module CAM where each call message is time stamped These messages calle
39. d raw activity records RARs are then passed via the high speed serial link to the BCU CAL If activity logging is enabled the BCU first archives a copy of each RAR received The BCU then examines each RAR and uses the time stamp values to determine the length of each call The actual billing algorithm is quite complex and depends on the BCU s keeping a memory of outstanding calls The output of the billing algorithm is stored to a regular disk file as a series of call detail records CDR Activity logging of RARs is a diagnostic capability not required for normal BCU functionality RAR activity logging consumes disk space and can result in degraded system throughput Although the feature is provided its use is strongly discouraged for most users The CDR format is compatible with Cincinnati Bell Information System s CBIS Cellware billing software 11 LBI 38965 3 2 3 1 RF Channel Usage Air Time The basic unit of RF channel usage for billing purposes is a channel assignment One or more working RF channels is assigned in response to a request from a subscriber unit mobile radio data terminal etc Each channel assignment event results in air time which is defined as the period of time during which the RF channel or group of channels is in use repeating the signal from a subscriber unit If the system is operating in transmission trunked mode one channel assignment occurs each time the unit is keyed and unkeyed In a multisite
40. d reconfigure port 1 as required Refer to the Emulex Terminal Server user s manual for additional information on server configuration via a telnet connection The up arrow on a VT100 can be used to recall commands to the terminal server allowing the user to reissue the same command to each port on the server by only changing port_no NOTE The push button switch marked default on the front of the Emulex P2516 terminal server will erase all configuration information in the terminal server and return it to the factory default state Do not use this switch to reset the terminal server Cycle power or issue the Initialize server command from the server configuration port to restart the terminal server Ericsson GE Mobile Communications Inc Mountain View Road Lynchburg Virginia 24502 Printed in U S A 33 LBI 38965 APPENDIX A EDACS BILLING CDR FORMAT LBI 38965 This appendix defines the EDACS call detail record CDR format for the collection of system resource usage data in a multisite trunked radio system The document is intended for use primarily by air time billing software developers who use this record format as input as well as for developers of equipment and software to collect and archive call detail data from EDACS 1 OVERVIEW The EDACS CDR is designed to record call activity on an EDACS multisite trunked radio system The records are intended primarily for billing purposes The EDACS CDR format bal
41. e file system The proper way to shut down the BCU CAL can be executed from either the root or admin accounts This procedure is shown by way of example USER INFORMATION Invoke the BCS program DSH gt bes Welcome to the BCU CAL Configuration Service BCS System Administrator privilege acknowledged USER INFORMATION The BCS halt command performs the proper shutdown procedure BCS gt halt USER INFORMATION Wait at least 2 minutes from issuing command then exit BCS BCS exit pei At this point the BCU CAL may be powered down or rebooted without concern for disk data integrity Under extreme 1 panic circumstances the root user can force an immediate reboot by entering reboot h at the pSH gt prompt either at the user console or via a telnet connection 30 LBI 38965 4 2 3 Software Upgrades Software upgrades are similar to the initial installation procedure discussed above Each time the BCU CAL boots it will check to determine whether a floppy diskette is installed If a diskette is present it will be scanned to check whether any BCU CAL installation files are present If applicable files are detected they will be copied to the appropriate system disk directory As in the initial installation procedure the operator will be prompted to remove the current diskette and insert the next one This method also applies to customer modifications to the contents of Installation Diskette
42. eature for the CAL 17 LBI 38965 4 INSTALLATION 4 1 HARDWARE INSTALLATION CAUTION Turn off the power before removing or installing VMEbus boards Removing or reinstalling the boards while the power is on will damage the boards This section describes the physical installation of the BCU CAL Other configuration is performed during manufacture and the information necessary is provided in Appendix B Follow these steps to connect a BCU CAL to an IMC for the first time except where indicated otherwise these steps apply to all configurations BCU only CAL only or BCU and CAL Using LAPB cable provided connect the BCU CAL s CAM control port 0 a female DB 25 connector located on rear of the BCU enclosure to the lower connector on the IMC backplane which corresponds to the slot in which the CAM resides The cable is keyed so that it fits properly only when it is correctly oriented BCU CAL Equipment Rack IMC Equipment Rack 190903628 71 85232701 903531P1 P72 P2 P1 P73 BCU CAL lt Ji J1 lt p CAM Control c Mi J14 lt J9 This will be plugged into PA2XX on the backplane and will correspond with the slot in which the CAM Data Concentrator at Audio Concentrator control card is located BCU CAL Equipment Rack at IMC 19D903880P 120 129 Figure 5 BCU CAL to IMC Next connect the console terminal to the female DB 25 connector labeled SE
43. ed 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
44. een selected so that individual attributes of the call type may be associated with single or double bit fields within the call type byte The call type byte is the 8 bit value represented by the ASCII encoded 2 digit hexadecimal number in the CDR call type field Table A 3 shows these bit fields and their meaning Table A 3 Call Type Bit Field Definitions Bit Position Normal Call Special Call system All Call Modifies meaning of bits 3 and 4 Jessica Jessica Special Call Reserved Reserved Reserved Bill Caller Trunked Bill Callee MSG Trunked Normal Emergency Update Call Clear Voice Digital Voice or Data Individual Call Group Call ICall Il Reserved A 7 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 log 1 2 log cdr log is maintained which contains information regarding when and why a CDR has been closed The contents of this file can be useful in customer tuning and diagnostics of the CDR file generation process A file w
45. elds described in the preceding section 14 PSTN Telephone No Figure A 3 Call Detail Record PSTN Telephone Number Field A 3 LBI 38965 5 4 CALCULATING THE NUMBER OF BYTES IN A CDR Note that the final linefeed character which terminates the record is not shown in these diagrams The actual number of bytes in a CDR is calculated by adding 2 to the offset of the final byte For example a group call involving 4 sites contains 3 additional site fields beginning at offset 70 and ending at offset 93 from the formulae above The actual length of the record including the linefeed character is thus 95 bytes 5 5 CDR FIELD DESCRIPTIONS Table A 1 contains detailed descriptions of each of the CDR fields Table A 1 Call Detail Record Field Descriptions No Size Format Range Values 1 Record Type 2 Hex 00 FF Defines the type of record 00 Mobile to Mobile 01 Mobile to Land Interconnect 02 Illegal 03 Land to Mobile Interconnect 04 Data 05 FF Reserved 2 Node ID No 4 Unique identification number for the EDACS node where the call activity in this CDR occurred User configurable System 2 Hex 00 FF System ID Number Multiple nodes Node 2 Hex 00 FF Node ID Number Multiple sites b Record ID No Radix 64 Unique identifier for the Call Detail Record 4 8 Start Date The date when the call was initiated Year Decimal 1970 2038 Mont
46. en you are ready to set up the terminal servers The System Manager must be properly configured to recognize the sites that the BCU CAL is simulating Be sure that these sites have been defined and the passwords are correct prior to connection establishment attempts between the System Manager and the BCU CAL 23 LBI 38965 4 2 2 Initial Installation The following section discusses software installation on a new BCU CAL An example of the expected terminal display during this sequence is also provided This example is annotated with comments indicating user activity procedures during the installation as well as general information regarding the process PREREQUISITES 1 Verify that the BCU CAL unit does not have power currently applied 2 Verify that the BCU CAL is correctly connected to VT100 compatible terminal user console the IMC CAM and the local area network LAN if applicable 3 Verify that the user console is configured as follows 9600 baud start bit 1 stop bit no parity VT100 personality Terminal is DTE No translation of CR to CR LF Local echo off Tab stop at 8 characters DCE DTE handshaking off XON XOFF flow control is optional The BCU CAL does support flow control 4 Edit the user configuration files contained on Installation Diskette 4 a 24 Edit the text file IP DAT to define unit s Internet parameters on the local network If the unit will not have
47. fferent If the BCU CAL hard disk drive has never been formatted 1 system integrator installation or the field unit s hard drive has been replaced output similar to the following will be observed If this message is displayed the operator should answer yes lt gt or simply lt RET gt when prompted The hard disk drive could not be mounted Do you wish to perform a high level format Y N lt RET gt Beginning high level format High level format successfully completed lt OS gt Beginning bootstrap loader DATE May 4 1994 TIME lt OS gt Floppy disk has been mounted lt 05 gt Scanning tloppy disk for LOADER SX lt OS gt Copying LOADER SX to the herd disks lt OS gt Copy complete 299029 bytes copied lt OS gt Floppy disk has been unmounted lt 05 gt Scanning hard dusk for LOADER SX OS Loading file LOADER SX from the hard disk lt OS gt Load complete 97762 bytes loaded lt OS gt Hard disk has been unmounted lt OS gt Transferring program control to LOADER module 1 46 36 pm lt LOADER gt Installing BCU CAL DATE May 4 1994 TIME 1 48 00 pm lt LOADER gt Floppy disk has been mounted Scanning floppy disk for BCU CAL installation files lt LOADER gt Floppy disk has been unmounted lt LOADER gt USER ATTENTION REQUIRED Remove the current installation floppy diskette Insert the next installation disk if any Strike lt RETURN gt to cont
48. g functions locally or remotely using a terminal interface program running on the BCU CAL Input of default configuration database Default pseudo hang time Default group billing mode Input of configuration data for individual LIDs and or GIDs to override the default configuration database Configuration data may be input for an individual ID or range of IDs LID pseudo hang time GID pseudo hang time GID group billing mode e Creation of a magnetic tape archive of CDRs e Transfer CDR files from the hard drive to the floppy drive Refer to LBI 38967 for a detailed explanation of the available operator functions 3 2 3 9 Database Elements This section describes the elements of the BCU s configuration database Default Data A set of subscriber default attributes maintained on the system contains the following information 1 Default unit pseudo hang time seconds 2 Default group pseudo hang time seconds 3 Default group billing mode caller or group 4 Default data call pseudo hang time seconds Unit Data Each subscriber can be assigned a record in the subscriber attribute database This record contains the following information Pseudo_Hang Time seconds Group Data Each group defined on the system shall be assigned a record in the subscriber attribute database containing the following information 1 Group pseudo hang time seconds 2 Billing mode group or caller 14 LBI 38965 3 2
49. h Decimal 01 12 Day Decimal 01 31 Start Time The time of day when the call was initiated Hours are in military Hour Decimal 00 23 format Minute Decimal 00 59 Second 2 Decimal 00 59 00 FF See The type of call as defined in Table A 2 Indicates whether call is Table A 2 group or individual whether to bill the caller or the callee etc Caller ID 10 Decimal 0000000000 For Record Types 00 and 01 this field contains the Logical ID LID 9999999999 of the caller For Record Type 03 the field contains the Interconnect Line number Decimal 0000000000 For Record Types 00 and 03 this field contains the Logical ID LID 9999999999 of an individual callee or the Group ID GID of a call group The Call Type field indicates individual or group call For Record Type 01 the field contains the Interconnect Line number 10 ui Callee ID No Elapsed Time 0000 FFFF The duration of the call in seconds 5 2 8 2 6 32 Decimal 01 32 Site number site 32 represents a remote node ete Assignments the local node for this call Number of Sites __ 2 Decima 01 32 The number of sites the local node which participated in this call Site of Origin 13 n Additional Site n participating in the call a Site Number b Channel Map Hex 000000 FFFFFF A hexadecimal bitmap where bit 0 channel 1 bit value of 1 channel 14 PSTN Telephone Dialed Digits Occurs in Record Type 01 only Cont
50. he elapsed time 4 RECORD ENCODING An EDACS CDR is an ASCII text record terminated by a linefeed character LF decimal 10 The record consists of fixed length fields The total number of fields in the record is variable depending on whether the call involved multiple sites or was a radio originated telephone interconnect call Most of the fields are numeric data and are specified as either Decimal or Hex format Decimal format fields are radix 10 integers encoded using the ASCII characters from decimal 48 0 through decimal 57 9 Hex fields are radix 16 integers encoded using the ASCII characters from decimal 48 0 through decimal 57 9 and decimal 65 A through decimal 70 Two additional formats are used The radix 64 format is used to provide a sequence number for each record The last format used is the dialed digits format This format is used to record a telephone number dialed by the originator of mobile to land telephone interconnect call The standard digits on a telephone keypad are encoded using the ASCII characters decimal 35 4 decimal 42 gt and decimal 48 0 through decimal 57 9 The following table defines the ASCII characters used in the CDR radix 64 sequence number field and their associated decimal values CDR Radix 64 Digit 0123456789 ABCDEFGHIJ KLMNOPQRST UVWXYZabcd efghijklmn LBI 38965 5 RECORD LAYOUT 5 1 SINGLE
51. ing show system displays the default system parameters that were initialized during the initial software installation BCS gt show system Default unit pseudo hangtime 10 Default group pseudo hangtime 10 Default group billing mode Bill callee Data call pseudo hangtime 10 PILLING On Phone digits mandatory Off CDR maximum file records 1024 CDR sequence wrapping On 28 LBI 38965 Offload time 00 00 00 Tape logging Off CDR archive s lifetime 7 IMC time synchronization Off RAR activity logging Off RAR maximum file records 10000 System ID 0 Node ID 0 NIM slot 0 Sot USER ACTION To define the IMC NIM slot execute the following command This example assumes that the NIM occupies slot 32 The actual value should reflect the end user s IMC configuration If the IMC does not have a NIM disregard this command BCS gt set system nim 32 USER ACTION To define the IMC PIM slot for Jessica execute the following command This example assumes that the PIM occupies slot 16 The actual value should reflect the end user s IMC configuration If the IMC does not have a PIM skip this command BCS gt set system pim 16 USER ACTION If either of the previous commands were executed you can verify them by entering the following command The previous two steps may be repeated in case the values were incorrectly entered by the operator BCS gt show system nim
52. inue USER ACTION Remove Installation Diskette 1 Insert Installation Diskette 2 Press the Enter key lt LOADER gt Floppy disk has been mounted Scanning floppy disk tor BCU CAL installation files Copying 01 02 loadS BC A 9X 4 Done 1200330 bytes copied LOADER Floppy disk has been unmounted LOADER USER ATTENTION REQUIRED Remove the current installation floppy diskette Insert the next installation disk if any Strike RETURN to continue 25 LBI 38965 USER ACTION Remove Installation Diskette 2 Insert Installation Diskette 3 Press the Enter key lt LOADER gt Floppy disk has been mounted Scanning floppy disk for BCU CAL installation files Copying BG B SX 0102 loads BC Done 109977 bytes copied lt LOADER gt Floppy disk has been unmounted lt LOADER gt USER ATTENTION REQUIRED Remove the current installation floppy diskette Insert the next installation disk if any Strike REIURN to continue USER ACTION Remove Installation Diskette 3 Insert Installation Diskette 4 Press the Enter key lt LOADER gt Floppy disk has been mounted Scanning floppy disk for BCU CAL installation files Copying Do Done Copying ROUTES DAT to 01 02 cnfg ROUTES DAT Copying EXPORTS DAT to 01 02 cnfg EXPORTS DAT Copying to 01 02 entG DAT we Done 915 bytes copied Done 2237 bytes copied Done
53. ion contained in the CAL DAT file must also be used to properly configure the Emulex Terminal Server s Terminal server configuration is discussed in detail in a separate section of this document EDACS System Manager site entries are specified in the following form SITE ss PASSWD system manager password SITE ss IP terminal server ip SITE ss PORT tcp port number where ss designates the associated site number ranging from 01 to 32 inclusive The site number in CAL should correspond to the site number of the System Manager port to which it will be connected A log file 1 2 log cal ini log is generated on each system boot This log summarizes the processing of this file indicating which sites are supported the values assigned as PASSWD IP and PORT for each site and any errors encountered in processing CAL DAT 22 LBI 38965 Table 6 CAL DAT File Parameters Parameter SITE ss PASSWD Specifies the System Manager password to be used for logins to from this site system_manager_password must match the associated value programmed on the System Manager for the site specified by ss SITE ss IP Defines the Internet IP address in dotted decimal notation of the Emulex Terminal server for the site specified by ss Note that the address terminal_server_ip should be chosen to be on a directly connected network with the BCU CAL IP address as specified in IP DAT SITE ss PORT Defines the TCP IP port number used to
54. is of the same call type as all other calls in the set For group calls only calls made with the same Group Identification GID may be linked In this case the Logical Identification LID of the caller is irrelevant except for the LID of the first caller in a sequence this is explained in the next subsection For individual calls the caller s LID must be the same as either the caller s or the callee s LID in every other call in the set Broken Call Sequences A set of calls must occur in an unbroken sequence A sequence is broken when one of the call participants calls a non participant For individual calls this means that either the caller or the callee from the first call in the sequence calls some third party either a group or individual For group calls the sequence is broken if the caller from the first call in the sequence calls a different group or an individual Note that a subscriber unit may participate in multiple group conversations overlapping in time as long as that unit was not the first caller in at least one of the conversations A sequence of calls is also broken when the time interval separating the end of one call and the beginning of the subsequent call in the sequence exceeds an arbitrary value This value is called the pseudo hang time and 15 configurable on a unit or group basis in the BCU 3 2 3 3 Group Billing Mode A group call may be charged to the caller or to the group The CDR includes a flag which indicates
55. ith a CTM extension will exist in the 1 2 cdr directory when the BCU 15 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 15 also controlled using the bcs command LBI 38965 APPENDIX B PHYSICAL CONFIGURATION DETAILS B 1 LBI 38965 This appendix contains information about jumper settings and cable pinouts for the BCU CAL 1 JUMPER SETTINGS Jumper settings for the BCU CAL components are shown on the pages listed below Figure Page 1 1475 1 Single Board Computer B 3 2 TV ME Ul u sh autos B 4 B 3 TVME 147P2 Adapter Boatrd B 4 BA MOO Mam O 5 143340 Mezzanine B 6 6 Maxtor MXT 1240S Hard DISIe eit b aa RA CER Eh OD Ln aa usanta B 7 B 7 Teac FD235HS 711 Floppy Disk
56. l Supported The CAL is capable of communicating with the System Manager using the System Manager to Site Controller SM SC and Site Controller to System Manager SC SM protocol defined in EDACS Protocol Specification System Manager Site Controller Version 1 1 High Speed HDLC Link RS 422 5 232 Centralized Activity CAL Console Terminal Logger CAL TCP IP LAN Emulex DEC en Terminal Servers 16 RS 232 Terminal Servers anager DECNet LAN Emulex DEC Figure 4 CAL Architecture 16 LBI 38965 3 3 3 CAL Operation Overview As new enter the system they are dispatched to an appropriate site handler which reformats and queues the data When the number of activity records queued exceeds a threshold value obtained from the System Manager at startup a download request is sent to the System Manager At any point the System Manager may log in to the site object and request it to purge its queue of activity messages start stop download of activity messages or start stop the transmission of monitoring messages 3 3 4 Additional Product Features Network File System The BCU CAL can be licensed to function as a network File Server NFS This feature allows the BCU CAL system disk to be mounted by client hosts such as billing mainframe computer NFS feature is provided at no charge for units licensed for BCU operation It may be purchased as an additional f
57. lly determine the proper or most efficient parameters and then add these to the ROUTES DAT file Proper routing is intimately related to the IP address and subnet mask specified in the IP DAT configuration file Keep these parameters in mind when adjusting ROUTES DAT contents 4 2 1 1 3 EXPORTS DAT Configuration File The EXPORTS DAT file only applies to BCU CAL units which have been purchased with the NFS Server software feature The NFS feature 15 always provided with the BCU It is an option for the CAL feature BCU users may disable the NES by using the product command discussed in LBI 38967 EXPORTS DAT defines which network clients are privileged to mount the BCU CAL system disk Example exports provided on the template disk are commented out i e preceded with a character and thus have no effect when the file is processed A log file 1 2 log nfs log is generated on each system boot The log summarizes the processing of this file indicating what has been exported who received the export and any errors encountered in processing the EXPORTS DAT file 21 LBI 38965 Export entries are specified in the following form directory client ip Table 5 EXPORTS DAT File Parameters Parameter Meaning directory Directory structure s to be exported Must be a fully specified valid directory on the BCU CAL system disk volume 1 2 Note that directories are case sensitive Specifying the BCU CAL root directory
58. n the event of loss of the WW VB 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 FileName 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 pseud
59. network more than one channel assignment can occur in a single call since multiple sites can participate in a call and a channel is used on each participating site The air time for such a call is defined as the sum of the air time associated with all of the channel assignments occurring in that call In a multiple node network StarGate or MultiLink a single call may involve channel assignments on sites on more than one node In theory these channel assignments are part of the same call In practice the BCU deals with data at the node level and does not correlate channel assignment air time from remote nodes A multiple node call is identified by the StarGate interface ID as the site ID in the CDR this facilitates the correlation of records across nodes in the external billing system 3 2 3 2 Conversations If a CDR were created for each call the data storage requirements for the BCU CAL would be excessive For this reason a different unit of RF channel usage called a conversation has been defined A conversation includes one or more calls Calls are summed into conversations based on the subscriber radio units participating in the calls and the duration of the time interval between the end of one call and the beginning of the subsequent call The criteria for inclusion in a conversation are explained in detail below Grouping Calls A set of calls may be grouped into a conversation only if each call involves the same participants and
60. o 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 15 a method by which the BCU configuration database can be maintained without using BCS to configure each unit manually 13 LBI 38965 The three configuration files can be created by running BCS on a BCU CAL used as a master Then these files can be copied to the appropriate directory 1 2 cnfg on a target BCU and the target will assume the same configuration values Changes specific to the target must be made either by running BCS on the target or by making the changes on the master copying the configuration files to the target then reversing the changes to restore the master to its baseline configuration NOTE To copy or delete the configuration files from a BCU CAL you must NOT be running BCS on that system BCS keeps all the configuration files open while it is running thereby preventing them from being deleted or overwritten 3 2 3 8 Operator Functions An EDACS system operator is able to perform the followin
61. on a 68030 microprocessor e Supports BCU CAL application processing e Interfaces to hard disk floppy disk and tape drive via an on board small computer systems interface SCSI with a connector on the transition module e Interfaces to the console terminal via an RS 232 serial port with a connector on the transition module e Network physical connection is 802 3 Ethernet 10 BASE 15 Thick Wire A MAU may be used for connection to a Thin Wire coaxial network Internal Drives Hard Disk 32 1 2 GB e Provides configuration parameter storage e Provides call detail record CDR storage e Provides raw activity record RAR buffering storage Floppy Disk 32 1 44 MB e Used for application program updates Tape 342 4 8 GB 4mm DAT e Provides call detail record CDR file archival storage e Provides general purpose file interchange with UNIX e UNIX Tar format 512 byte tape block size no data compression Communications Module Formation WANServer fv5310 Interfaces the BCU CAL via high speed high level data link control HDLC link to the Central Activity Module CAM in the Integrated Multisite and Console Controller IMC System Manager Interface CAL only One or Two Emulex Performance Series P2516 SLTL Terminal Servers Communicates with the BCU CAL over the network and with the System Manager over RS 232 e Converts between transmission control protocol TCP sockets and asynchronous serial protocol LBI 38965 2 3
62. ork destination_ip IP address of the destination host or network in Internet dotted decimal notation gateway Keyword indicating that the next field is that of the gateway node gateway_ip IP address of the gateway to be used to communicate with the host address specified by destination_ip Parameter specification is not case sensitive and is parsed 1 net 15 equivalent to network White space and or tabs may separate the parameters Trailing comments are allowed The following are examples of routing entries in the file ROUTES DAT In this example packets destined for host 147 117 1 2 will be routed to gateway 147 117 37 245 for forwarding All packets destined for hosts on network 147 200 0 0 will be routed to gateway 147 117 32 2 for forwarding Similarly destinations on network 147 117 100 will be routed through 147 117 32 3 host 1 1412 Gateway L47 11752357 245 Example of host route network 147 200 0 0 gateway 147 117 32 2 Example of a network route net 127 100 0 0 gate RATIO SA V Example of parsing Configuration Tips Network routes should be entered in a logical order That is if there are multiple gateways between the BCU CAL and a destination the most direct route s should be specified first Network routes may be manually added and deleted using the route command discussed in the User Interface Manual LBI 38967 If you are unsure of proper routing use the route command to experimenta
63. still utilize resources and utilities common to both Additional information for BCU CAL can be found in the following publication LBI 38967 EDACS Billing Correlation Unit Centralized Activity Logger User Interface Manual Console Terminal Downlink DAT Optional MIM CAL A M High Speed HDLC Link RS 422 Ethernet TCP IP WAN Emulex Emulex Terminal Terminal Servers Servers 116 RS 232 Network Manager DEC DEC Terminal Terminal Servers Servers DECNet LAN System Manager The dotted lines enclose the CAL specific interfaces of the BCU CAL Figure 1 BCU CAL Architecture LBI 38965 1 1 BCU FUNCTIONAL DESCRIPTION The main function of the BCU 15 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 Console calls Conventional site calls Local interconnect calls Non EDG data calls cs 1 2 CAL FUNCTIONAL DESCRIPTION EDACS system administrators require both site monitor and activity download capabilities These functions are normally support
64. stributed on four 1 44Mb MS DOS compatible floppy diskettes The first three disks contain Ericsson GE 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 The table below summarizes the contents of the distribution disks Table 1 BCU CAL Installation Diskettes Installation Contents Diskette LOADER SX Bootstrap loader for the BCU CAL application 2 BC_A SX First segment of the BCU CAL executable image 3 BC_B SX Second segment of the BCU CAL executable image 4 Product configuration files to be modified by the BCU CAL end user LBI 38965 The following table summarizes the configuration files contained on Installation Diskette 4 These files are provided in template form and should be modified to suit customer specific requirements The files are in MS DOS format and may be edited with any ASCII text editor Table 2 BCU CAL Configuration Diskette IP DAT Defines the IP address subnet mask and host name of the BCU CAL ROUTES DAT Defines network routing paths between the BCU CAL and other hosts on the customer s network Syntax is similar to the UNIX etc gateways file EXPORTS DAT Defines BCU CAL NFS export list for units which have been purchased with the NFS file
65. ystem configuration files lt BCU CAL gt Creating default system Cibe SYSTEM BIN gt i lt BCU CAL gt Creating default mit parameters Triler lt BCU CAL gt Creating default group parameters file 01 02 cnfg GROUP BIN lt BCU CAL gt Checking product feature license lt BCU CAL gt Application installation complete 26 LBI 38965 ck KO KC Ck ck Kok Kok Kk KC KC Ck ok Kok Ck ok Ko KC Kk KK KKK k k x k k k k k x x x x lt x x lt x x KKK KKK lt x x x x x Welcome to the EDACS BCU CAL Copyright C Ericsson GE Mobile Communications 5 Mountain View Road Lynchburg Virginia 24502 T 1993 1 994 w lt K K k Kk Kk k k k Ck ok x x Kok k lt lt lt lt lt lt lt lt lt lt lt lt lt lt KK x lt lt lt lt lt lt lt lt lt lt K lt k lt lt KK KG X X X X X X X X lt System boot complete Wed May 4 13 55 09 1994 Login USER INFORMATION The Welcome banner and Login prompt indicate a successful software installation and system boot At this point the operator should log into the unit under the root account to perform some first time configuration operations 4 2 2 1 First Time Configuration The following section describes the minimal set of system initializations that a user must perform to set up a BCU CAL When the BCU CAL software is first installed three user accounts are initialized Each account has

Download Pdf Manuals

Related Search

Related Contents

DRN- DGN - GRN APN - MAN  Troubleshooting Wireless Networks  Baixar manual  CNC 8055 Educacional  Why D-Link Wireless    Jornal fev08    Bitdefender BITDEFENDER 9 Turntable User Manual  CRYSTAL CLEAR UPGRADE – URETHANE 4 CONCRETE  

Copyright © All rights reserved. Failed to retrieve file