Lucent Technologies 555-661-150 manual Station Message Detail Recording, Smdr

MERLIN LEGEND Communications System Release 6.1			Issue 1
Network Reference 555-661-150			August 1998
3 Feature Interactions
	Station Message Detail Recording (SMDR)		Page 3-23
	Station Message Detail Recording	3
	(SMDR)

For 6.0 systems, all private network calls are reported according to SMDR Call Report programming for reporting non-UDP incoming and outgoing calls. To log network calls, SMDR should be programmed to report both incoming and outgoing calls.

In Release 6.1 and later systems, SMDR can be programmed to record incoming/outgoing UDP calls or no UDP calls. When a system is programmed to record no UDP calls, only calls received on a PSTN trunk and/or routed over the private network to a PSTN trunk on a remote system using ARS or DID/PRI dial plan routing are included on SMDR reports. The default value programming is to record incoming UDP calls. This programming is local to each system, and is not network wide.

For Release 6.0 and later systems, calls across the network are not recorded, even at a tandem switch, if the call is not answered unless the outgoing facility is a loop-start or ground-start trunk. Then calls are logged, even unanswered calls.

Ensure that the system date and time are set accurately on each system that carries private network calls. If the system date and time are not synchronized across the network, it may be hard to recognize the records for a single call, even when the systems are in the same time zone. When reviewing reports, consider When UDP calls are recorded on SMDR reports, a single call routed across a private network, is recorded as both an incoming and an outgoing call in the same system. For network calls, outgoing call records report the incoming tandem trunk number in the STN. field (see System B in Figure 3-1 below). Dialed digits shown on the report do not reflect any digit manipulation (addition or absorption) performed by the local system. Uncompleted calls do not generate a SMDR report, except for calls over loop-start or ground-start trunks, which generate SMDR reports whether completed or not. SMDR reports may report calls using more than one call record on more than one system. Depending upon how SMDR is programmed and how calls are routed, you may need to consult several SMDR records to trace a call that is routed over network trunks.

Figure 3–1 shows examples of different call types an how they are recorded on SMDR reports when the SMDR call report option is set to log incoming and outgoing calls and for Release 6.1 and later systems, the SMDR UDP option is set to log all UDP calls at each systems in the private network.