Please enable JavaScript to view this site.

IP Office Basic Edition - Web Manager R11.1

> » No topics above this. «

SMDR Call Logging

Scroll Prev Up Next More

The control unit is able to send SMDR (Station Message Detail Reporting) records to an IP address and port. Each SMDR record contains call information in a comma-separated format (CSV) format, that is variable-width fields with each field separated by commas. The 3rd party call logging software running at the specified address collects the records and uses the data to provide call information.

Normally an SMDR record is output for each call between two parties when the call has been completed. In some scenarios, for example transfers and conferences, separate SMDR records may be output for each part of the call. See SMDR Examples.  

Configuring the SMDR Destination

1.Click System in the menu bar and then click Auxiliary Equipment.

2.The SMDR Setup panel is used to set the destination for any SMDR records output by the system.

SMDR output: Default = Off
This control can be used to switch the output of SMDR on or off.

IP Address: Default = 0.0.0.0 (Listen).
The destination IP address for SMDR records.

TCP Port: Default = 0.
The destination IP port for SMDR records.

Record to Buffer: Default = 500. Range = 10 to 3000.
The phone system can buffer up to 3000 SMDR records if it detects a communications failure with destination address. When the buffer is full, each new record overwrites the oldest record.

Call Splitting for Diverts: Default = Off.
When enabled, for calls forwarded off-switch using an external trunk, the SMDR produces separate initial call and forwarded call records. This applies for calls forwarded by forward unconditional, forward on no answer or forward on busy. The two sets of records will have the same Call ID. The call time fields of the forward call record are reset from the moment of forwarding on the external trunk.

3.Click Save.

SMDR Records

An SMDR record is generated for each call between two devices on the IP Office system. Devices include extensions, trunk lines (or channels on a trunk), voicemail channels, conference channels and IP Office tones.

Calls that are not presented to another device do not generate an SMDR record. For example internal users dialing short code that simply changes a configuration setting.

The SMDR record is generated when the call ends. Therefore the order of the SMDR records output does not match the call start times.

Each record contains a call ID which is increased by 1 for each subsequent call.  

When a call moves from one device to another, an SMDR record is output for the first part of the call and an additional SMDR record will be generated for the subsequent part of the call.

Each of these records will have the same Call ID.

Each record for a call indicates in the Continuation field if there will be further records for the same call.

Wake up calls produce an SMDR record even if the intended extension was busy at the time of the call. Party1 is shown as Wakeup Call.

Call Times

Each SMDR record can include values for ringing time, connected time, held time and parked time. The total duration of an SMDR record is the sum of those values.

The time when a call is not in any one of the states above, for example when one party to the call has disconnected, is not measured and included in SMDR records.

Where announcements are being used, the connected time for a call begins either when the call is answered or the first announcement begins.

All times are rounded up to the nearest second.

Each SMDR record has a Call Start time taken from the system clock time. For calls being transferred or subject to call splitting, each of the multiple SMDR records will have the same Call Start time as the original call.

 

 

Performance figures, data and operation quoted in this document are typical and must be specifically confirmed in writing by Avaya before they become applicable to any particular order or contract. The company reserves the right to make alterations or amendments at its own discretion. The publication of information in this document does not imply freedom from patent or any other protective rights of Avaya or others. All trademarks identified by ™, ® or © are registered trademarks or trademarks respectively are the property of their respective owners.

Use of this site indicates acceptance of its cookies and analytics, and acceptance of the Avaya privacy policy.

© 2020 AVAYA
Issue 05.a.–
Thursday, July 23, 2020