6.2.3. Message Sequences for Transmitting Individual Call
Data 
There are different message sequences for transmitting data over the
data channel:
- Immediate output after the end of a connection initiated by OpenScape 4000
- (NOT RECOMMENDED ANY MORE). Data retrieval initiated by the DPS. If CDR records are stored in GEZSFILE1 and GEZSFILE2 then it is possible for the application to initiate the output. If no realtime processing is necessary the Collecting Agent provides much more flexibility in CDR data processing.
A separate logical connection must be set up between OpenScape 4000 and
the DPS receiver application.
The DPS receiver application must always be ready to accept a connection
setup from OpenScape 4000 (if there is not already a connection). Although
normally the application initiates the connection and then receives and
processes the CDR records, if the connection is lost OpenScape 4000 will
create a new connection to the DPS system, so the DPS system must be
able to handle connect requests.
If you have configured immediate output, once a connection is made,
that connection is sustained. If it has been cleared down for any reason
it is set up again as soon as the next data record is ready.
The DPS receiver application sets up and clears down the connection
to the OpenScape 4000. During the connection, the following messages
are exchanged:
- OpenScape 4000 → DPS
OpenScape 4000 sends a data block with call data records to the DPS. This record is EBCDIC encoded and the length must not exceed 1020 bytes.
- DPS → OpenScape 4000
The DPS receiver application acknowledges the receipt of the CDR information, and simultaneously indicates ready for next retrieval with the Data Indication message "A1011" (for description of the available messages see "Appendices C Example Coding for DPS output" under "OpenScape 4000, Call Detail Recording, Service Documentation").If OpenScape 4000 does not receive the confirmation within 30sec the actual CDR record is sent again.