# External SMDR

## Description

External SMDR collects data for outgoing and incoming trunk calls. You can use the data to determine the cost of external telephone calls. Typically, external SMDR is used for the following purposes:

- for billing external calls back to individuals, customers or departments

- for evaluating the system trunks (for example, number, type and traffic).

Both stations and trunks must have external SMDR enabled in their Class of Service Options form for an SMDR record to be generated for a call. Under these conditions, SMDR data collection is initiated every time an incoming or outgoing trunk is seized (if both incoming and outgoing recording are enabled). Call data is collected on a per-call basis, formatted into an SMDR record, and routed to an RS-232 output port for processing on an station message detail accounting (SMDA) machine or for storage. Alternately, call data can also be stored on the system hard disk and retrieved for processing at a later date.

The following external SMDR conditions are reported as follows when an attendant handles a call:

- When an attendant dials a trunk with no station or trunk involved, the calling party is the attendant.

- When an attendant answers a trunk call and does not transfer it to a station, the called party is the attendant.

- When the attendant dials a trunk while it has a station as its source, the calling party is reported as the station and an "?" appears in the Attendant field.

- When an attendant connects a previously-held station to a trunk, the calling party is the station and an "?" appears in the Attendant field.

- When the attendant has a trunk as Source, and then connects a station to the trunk, the calling party is the trunk, the called party is the station, and an "?" appears in the Attendant field.

- The attendant will appear as the called party when involved in a call transfer (two records are generated).

- When a hunt group with ONS ports as members is programmed as an ACD path unavailable answer point, and the ONS port answers the call, the SMDR record shows the ACD path reporting number (rather than the ONS directory number) in the Called Party field.

When external SMDR is enabled for incoming calls the following conditions are reported:

- Digits dialed on incoming DID, DISA or dial-in tie trunks are reported in the digits dialed on the Trunk field. When the dial-in trunk dials an illegal or vacant number, or hangs up before completing the number, the call is reported. The called party is the station dialed. The DISA security code is reported in the Account Code field.

- The called party is always the attendant, except when an attendant forwards a call to a station. The station then becomes the called party and an "?" is reported in the Attendant field.

- Direct-in trunks show the station number as the called party (for example, dial-in trunks). The digits dialed on the Trunk field displays the incoming digits. When the trunk is directed to a hunt group, the station that answered the call is reported.

- On incoming calls, an " E" is reported in the Call Completion field when the trunk hangs up while listening to reorder tone, or a "B" is reported when the trunk hangs up while listening to busy tone. A " T" is reported when the incoming call is answered with TAFAS.

- If the attendant forwards a call to a station, a second record is generated and the attendant remains as the called party for the first record.

## Standardized SMDR

### Network OLI

Standardized Network Originating Line Identity (OLI) provides a mechanism which allows for the correlation of all SMDR events associated with a call, irrespective of the specific call scenario and applicable SMDR options. When the Standardized Network OLI option is enabled in the SMDR Options form, all SMDR events associated with a single call through the network are associated using the Network OLI.

When a call is transferred between extensions, the OLI on each segment of the call is based on the transferring party. All segments of the call report the Network OLI in the ANI portion of the ANI/DNIS field, but they may not match as a result of the transfer.

NOTE: Network OLI is not preserved across analog or digital tie trunks.

The application of the following mechanisms can be used to sequence the SMDR events involved in a call; however, we recommend Call ID Format be used for these purposes:

- Network Originating Line Identity ( OLI) - all SMDR events associated with a call through the network share a common Network OLI based on the first party involved in the call (using the System ID and either the extension number of the caller, or the trunk number of the incoming trunk).

- Common Calling Party and Called Party - the SMDR event associated with the incoming trunk is associated with the SMDR event on the outgoing trunk, based on the common Calling Party and Called Party fields in both events.

- Transfer Indication - SMDR events associated with segments of a call across DPNSS trunks are associated based on the Third-Party and Called Party fields.

- Call Pickup or TAFAS Answered - The Calling Party and Called Party fields in the two SMDR events associated with a call are opposites, the Calling Party in one event is the Called Party in the other event. This is indicated by a " T" in the Call Completion Status field. This occurs in the case of Incoming CO-trunk calls, which are transferred to an extension upon which call pickup is exercised by a third-party extension.

- Uniform Trunk Numbering Plan - In the case of analog tie trunks there is no signaling of OLI across the span; therefore, SMDR events at either end of the tie trunk are generated independently. By assigning the same trunk number to both ends of the analog tie trunks, SMDR events associated with a call across the tie trunk can be correlated based on the common trunk number. As a result, correlation of these events is based on the Calling Party and Called Party being the same. The Digits Dialed on the Trunk field in both SMDR events also match (subject to digit modification).

### Call ID Format

Standardized Call ID Format facilitates the sequencing of SMDR events within a call and distinguishes SMDR events between calls, when the calls are made by the same caller. When the Standardized Call ID Format option is enabled in the SMDR Options form, the following identifier fields are added to the SMDR record (the Standardized Network OLI option must also be enabled):

- Call Identifier - an 8-digit field in the SMDR record, which uniquely identifies all SMDR events associated with a single call through the network (subject to roll over - calls with the same identifier can be differentiated by elapsed time between calls).

- Call Sequence Identifier - a single field in the SMDR record starting at "A" on the first SMDR event associated with a particular call, and incrementing for each SMDR event progressing through the call.

- Associated Call Identifier - an 8-digit field in the SMDR record, which is the call identifier of a previous call associated with the current call (for example, transfer, conference, call pickup, etc.). This field is used to correlate all SMDR events associated with a series of related calls.

## SMDR File Transfer

When the SMDR File Transfer option is enabled in the SMDR Options form, the following additions are introduced to regular SMDR logging:

- A duplicate SMDR log facility is created, at system restart.

- The *. ops catalog is created.

- SMDR logs are generated to both the SMDR file and the duplicate SMDR file ( ftsmdr).

The duplicate SMDR log facility continually captures SMDR events to the ftsmdr file. This file is identical to the regular SMDR file, but is created on the non-redundant partition and is provided only for the support of SMDR File Transfer. No action is performed on the duplicate SMDR file unless requested through the use of authorized maintenance commands.