Section 7.11. DPS Interface DataINCDR DPS interface

7.11. DPS Interface Data

The call data recording software complex offers the OpenScape 4000 system operator a feature for retrieving call charge data or transmitting call charge data to a DPS application using a partner computer (DPS) application.

The message traffic and output of the call charge data to the DPS are processed via the Communication Management System (CMS).

Connection process for retrieving data from the DPS: For this connection process, the DPS must send a job that specifies how much data should be transmitted.
The DPS only sends the "Send call charge data" job at the beginning. Call data recording then responds with "Call charge data block on request" and waits for the answer "Call charge data processed" from the DPS. If this acknowledgement is not sent within a specified time, the logical connection is cleared down and the charge transmission is cancelled. If the DPS sends the acknowledge message, the next block of data is transmitted with "Call charge data processed" and a new call request. A "End of call charge data" message is sent when there is no more call charge data available.

Requirement for processing the call charge data call:

The AMO GEZAB's "ADD" action must be used to define a dialog field for the DPS retrieval of the CDRC1 or CDRC2 file.

Example for multiple output = NO:

ADD-
GEZAB:TYPE=L,DIAFNO=<number>,FILE=CDRC1|CDRC2,FILESTA=<string
>

           
,FILEND=<string>,DEV=DP,CALLUP=Y,DEL=<Y\N>,FORM=<string>

           
,FORM=<string>,BLKSIZE=<number>,FOUT=<Y\N>,MULTOUT=N

           ,PERIOD=<string>,SELSTOP=<Y\N>;

For each dialog field that is assigned to the DPS call, a "short dialog" must be defined for the AMO GEZAB. In the "short dialog", it must be possible to change the two parameters FILESTA (start of file) and FILEND (end of file). If a scheduled job is activated for the dialog field that is assigned to the DPS call, the dialog field can only be rewritten by stopping the active scheduled job (STOP-GEZAB). This changes the status of the dialog field from TIMEORDER ACTIVE to BUSY. With the CHANGE-GEZAB action, the two parameters FILESTA and FILEND can be rewritten in the "short dialog".

A plausibility check is run on the data sent by the DPS application (file name, file start, file end), which means only the value CDRC1 or CDRC2 is allowed.

Call data recording for CDRC output on call must be configured:

ADD-FEACG:CM=CDRCDIS;

Furthermore, each of the eight dialog fields is searched to see if it contains the following parameters.

DEV	=	DPS
FILE	=	CDRC1 or CDRC
ORDER_ID	=	CALL

If a dialog field contains the above parameters, the dialog field on the database (DB) is blocked.

Connection process for output from the OpenScape 4000: In the event of a file overflow (mandatory output) or output by scheduled jobs, the call charge detail output is initiated by the OpenScape 4000 when the output device is specified (DPS in this case). This is done by sending the message "Call charge data blockon request". If the "Call charge data processed" acknowledge is sent, the process is continued in the same way as for DPS-based file retrieval.

If there is no acknowledgement from the DPS within a specific time, the call charge detail output is cancelled.

In contrast to call charge detail retrieval via DPS, the initiative for call charge detail output to the DPS lies with the OpenScape 4000.

All eight dialog fields are searched for the following parameters.

DEV	=	DPS
FILE	=	CDRC1 or CDRC
ORDER_ID	=	TO or FORCE

File processing starts if there is a dialog that contains these parameters. If no such dialog field is found (for example, if the job was cancelled with the AMO GEZAB before the DPS connection was set up), a report is sent to the exception handler and the system waits for the next job.

Meaning of the ORDER_ID variables:

ORDER_ID = CALL There is a call from the DPS.
ORDER_ID = TO Output to the DPS.
ORDER_ID = FORCE Mandatory output to the DPS (for example, in the event of file overflow)

${DocTitle}, ID: ${DocID}

© 03/2026 Mitel Networks Corporation. All rights reserved. Mitel and the Mitel logo are trademark(s) of Mitel Networks Corporation. Unify and associated marks are trademarks of Unify Software and Solutions GmbH & Co. KG. All other trademarks herein are the property of their respective owners.