6.2.1. Requirements for Call Detail Transmission to the
DPS 
Depending on the administration of the OpenScape 4000 system, data
can be recorded over all outgoing, incoming, and tie trunk connections,
and also over internal connections, and then prepared for call detail
tracing. This makes it possible to output connection and call detail
data. A data processing system (DPS) coupled over the data channel reachable
over customer LAN is available as the output device. The Layer 4 protocol
is ISO8073 Class 0 (RFC1006).
INFO:
ATOS DOES NOT SUPPLY ANY APPLICATION WHICH CAN HANDLE DPS OUTPUT!!
This section describes configuration details for the transmission
of data concerning the individual connections (individual call data)
over the data channel to the DPS.
The following general possibilities for transmitting this data to
the DPS exist:
- Immediately after each connection ends (immediate output) initiated by OpenScape 4000,
- After temporary storage of the data in OpenScape 4000
INFO:
THIS USE CASE IS NOT RECOMMENDED ANY MORE! IF NO REALTIME PROCESSING IS NECESSARY FTFILE AND COLLECTING AGENT MUST BE USED. THESE MECHANISMS PROVIDE MUCH MORE FLEXIBILITY AND FURTHER PROCESSING CAPABILITIES.- On demand, initiated by the DPS,
- Upon the expiration of a (periodic) scheduled batch job in OpenScape 4000 initiated by OpenScape 4000,
- Upon overflow of the call detail file in OpenScape 4000 (forced output) initiated by OpenScape 4000.
A configuration example for OpenScape 4000 is given in Section 59.3.1, "Example configuration of an immediate DPS output over customer LAN".The DPS receiver application parameters have to fit with the OpenScape 4000 configuration according to ISO8073 specification.