Collapse AllExpand All

6.2.2. Transmission of Individual Call Data Previous topic Parent topic Child topic Next topic

The transmission of individual call data is a part of the OpenScape 4000 system feature "Call detail recording, central (CDRC)".
You must use AMO GEZU (device allocation) to configure the name of the DP application that is to receive the data. You may configure only one DP application name.
The content of the CDR record is freely configurable by AMO FTBL. The records are encoded in EBCDIC and the length of a single record must not exceed 1020 bytes.
IMPORTANT:
If the DPS system fails, the output to other selection groups is also stopped and the CDR data is buffered as long as the output to DPS system is defective! A workaround would be the configuration of a reserve output device (e.g. FTFILE, see Section 59.3.1, "Example configuration of an immediate DPS output over customer LAN", step 4) to avoid this blockage.
The transmission of the data to the DPS can occur either immediately after a connection ends (immediate output) or after temporary storage in OpenScape 4000 (output on demand, this feature is deprecated. FTFILE and Collecting Agent should be used instead). For output on demand a dialog field has to be configured by AMO GEZAB (configuration of the central call detail data extraction). It is also important that you suitably coordinate the DP application and the OpenScape 4000 behaviour with one another according to ISO8073.
Regarding the CDRC1 and CDRC2 files (which due to poor performance compared to FTFILE usage is not recommended any more). These two hard disk files :CGD:GEZSFILE1 and :CGD:GEZSFILE2 are SAM files and are available for the temporary storage of the data in OpenScape 4000. Together they can currently accept a maximum of 130,000 data records. Each separate CDR file can store a maximum of 65,000 data records. The standard value of the file size for the CDR files (AMO DAGR controls administration of the CDR file parameters) is between 30,000 and 40,000 CDR records. Taking these boundary conditions into account, you can define the size of the CDR files with AMO DAGR as needed.