When both internal and external SMDR are enabled, external SMDR takes precedence over internal SMDR. As a result, if system programming allows for both an external SMDR record and an internal SMDR record to be made for a call, only the external SMDR record will be generated.
When SMDR real time reporting is enabled, you cannot use the Logsys Read SMDR maintenance command.
SMDR is not used in the following situations:
An attendant or station user receives busy tone when dialing an external number (because all trunks in the group are busy). If ANSWER PLUS - MITEL Call Distribution (MCD) has been installed, SMDR will record a busy condition.
The calling or called party has a class of service which disables SMDR
A station user receives reorder tone due to dialing an invalid number
An attendant intercepts a station attempting to access a trunk group.
Note: SMDR file size and buffer size parameters must be reset after a software upgrade.
The network format option in the SMDR Options form may only be enabled if the MSDN/DPNSS Voice V feature has been installed on the system. This option provides for the recording of the calling party's node ID and extension number in the Digits Dialed on the Trunk field, as well as the actual digits dialed (called party's node ID and extension number).
For external SMDR, if a station involved in a trunk call invokes a transfer to another station, only one record is generated; however, the number of the second station appears in the SMDR call record.
External SMDR records are not created under the following circumstances:
calls which encounter busy trunks
internal calls between stations or between a station and an attendant
calls made from stations or going to trunks whose COS has SMDR disabled
When two or more trunks are involved in a call, separate SMDR records are generated for each trunk, providing that the appropriate options have been enabled in the SMDR Options form. For example, in the case of tandem trunk calls, the SMDR feature of the central node in a tandem call would generate a record for the incoming trunk call to the central node of the system network and one for the outgoing trunk. In such instances, individual trunks can be analyzed for costing purposes.
If the SMDR Record Transfer option is enabled in the SMDR Options form, an SMDR record is generated for each station involved in an outgoing trunk call stating the duration and number of meter pulses for that station's portion of the call.
If SMDR meter units per station is enabled in the SMDR Options form, meter pulses may be accumulated on a device and account code basis up to an assigned buffer size. The meter pulses can be read, printed and cleared from the operator's console. The options 'Report Outgoing Calls' and 'Report Meter Pulses' must also be set to 'Yes' for Station Message Detailed Accounting (SMDA) to be functional. Each device or account code may accumulate up to a maximum of 65535 meter units against it. When that total is exceeded, the number remains at 65535 until cleared by the operator.
If the extended digit length option is enabled in the SMDR Options form, then the line length of each SMDR record will be increased from 88 to 99 columns, to allow 7-digit extension numbers and 4-digit trunk numbers in the Calling, Called and Third Party fields, and to allow 10 columns in the Duration of Call field.
The SMDR real time reporting option, when enabled in the SMDR Options form, allows you to obtain real time SMDR records. This is accomplished by routing the SMDR records directly to a previously defined printer instead of storing the records on disk and then sending them to print. Once the real time option is enabled or disabled, you must perform a system restart.
Internal SMDR records are not generated for calls that involve trunks.
If two stations are involved in a call, and either or both of the stations have Internal SMDR enabled in their class of service, the system generates an Internal SMDR record.
Only one internal SMDR record is generated per internal call, unsupervised call transfer, or conference call. A separate record is not produced for each member of an internal call, conference call or call transfer. For example, if Station A calls Station B, the internal SMDR feature generates a record that shows Station A called Station B. A second record showing that Station B conversed with Station A is not generated.
An internal SMDR record is only generated for completed internal calls. Note that successful Directed Pages and Group Pages are completed internal calls.
Internal SMDR records allow you to identify each member of an internal conference. At least one station in the conference must have internal SMDR enabled in its class of service.
If a station transfers (unsupervised) an internal call to another station, a record is generated showing the numbers of all three stations involved in the transfer. At least one station involved in the call transfer must have Internal SMDR enabled in its class of service. Another record is generated for the 2-party call that results from the call transfer, if either of the stations has Internal SMDR enabled.
If the extended digit length option is enabled in the SMDR Options form, then the line length of each SMDR record is increased from 88 to 99 columns, to allow 7-digit extension numbers in the Calling, Called and Third Party fields, and to allow 10 columns in the Duration of Call field.
Internal SMDR does not interact with the MITEL Call Distribution feature, SMDA Meter Pulse Recording, or the ANI/DNIS/ISDN/CLASS Number Delivery feature.
