Configuring the CDR format for Avaya Aura

Avaya Aura has a CDR format that is configurable both by the list of fields and by their order. To understand which CDR fields should be used in Avaya Aura to process them in the Tariscope billing system, here is the relevant information. For the correct processing of CDR data in Tariscope, almost all the fields listed below should be in the Avaya Aura CDR format setting.

acct-code. (Account Code). This CDR field can contain either a project code or an account code. If you use the project code when calling, then in Tariscope the field will go to ProjectCode. This field is not mandatory.

auth-code. (Authorization Code).If your telephone system allows you to use an authorization code when making calls, then this field should be added when configuring the CDR format in the PBX. In Tariscope, this field falls into a field with the corresponding name. If an authorization code calls are not used, this field is not required.

calling-num. (Calling Number). Depending on the call type in Tariscope, this field corresponds to one of the following fields: Originator, CLID, or DialNumber. This is a required field.

code-dial. (Code Dial). This field contains the access code that the subscriber dials when making outgoing calls. This field is optional.

code-used. (Access Code Used). This field is used only for outgoing calls when the system uses a trunk group that is different from the access code the subscriber dials. If you have such cases, then this field is mandatory. It is used when forming the Terminator field in Tariscope.

cond-code. (Condition Code).(Condition Code). Used in Tariscope to determine the call type.

date. This field contains the end date of the call. You can use the ‘start-date’ field instead. One of these fields is mandatory for Tariscope call processing.

dialed-num. (Dialed Number). Depending on the type of call in Tariscope, this field corresponds to one of the following fields: Terminator or DialNumber.

duration.This field contains the duration of the call in the format: hours (from 0 to 9), minutes (from 00 to 59), tenths of minutes (from 0 to 9). Thus, when using this field, the accuracy of determining the call duration is 6 seconds. The ‘sec-dur’ field can be used instead of this field. The use of one of these fields is required to determine the duration of a conversation in Tariscope.

in-crt-id. (Incoming Circuit Identification). This field contains the number of the trunk in the trunk group used for the incoming call. For outgoing calls, this field is empty. This is a required field, in Tariscope it is used to form the Originator field for incoming calls.

in-trk-code. (Incoming TAC). This field contains the access code for the incoming connection group. This field is mandatory for forming the Originator field in Tariscope for incoming or transit calls.

out-crt-id. (Outgoing Circuit Identification). For outgoing calls, this field contains the number of the outside line in the outside line group used during the call. This field is empty for incoming calls. This is a required field, in Tariscope it is used to form the Terminator field for outgoing calls.

sec-dur. This field contains the duration of calls in seconds with an accuracy of 1 second. It can be used instead of the ‘duration’ field. The use of one of these fields is required to determine the duration of a conversation in Tariscope.

start-date. This field contains the start date of the call. It can be used instead of the ‘date’ field. The use of one of these fields is mandatory to determine the start date of the call in Tariscope.

start-time. This field contains the start time of the call. It can be used instead of the ‘time’ field. The use of one of these fields is required to determine the start time of the call in Tariscope.

time. This field contains the end time of the call. It can be used instead of the ‘start-time’ field. The use of one of these fields is required to determine the start time of the call in Tariscope

ucid. ЭThis field contains the unique identifier of the call. It is necessary for linking in Tariscope individual CDR records formed during transfer calls.

All other CDR fields that are available in the Avaya Aura CDR format are not used in the Tariscope system.

Avaya Aura's CDR processing settings in Tariscope are described in the Tariscope document. Administrator's Guide.