Calls Across The Private Network - Lucent Technologies MERLIN LEGEND Release 6.1 Maintenance And Troubleshooting Manual

MERLIN LEGEND Communications System Release 6.1
Maintenance and Troubleshooting 555-661-140
Station Message Detail Recording (SMDR) Reports Do Not Include Calls
Chapter 5 of Network Reference . To program clock synchronization, see
Chapter 3 of System Programming .
If the clock source is correct, ensure that the specified port is functioning
properly and has an in-service facility connected to it.
If this does not solve or explain the problem, call the Lucent Technologies
Helpline at 1 800 628-2888; consultation charges may apply.
Station Message Detail Recording
(SMDR) Reports Do Not Include

Calls across the Private Network

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 private network tandem trunks. To log private network calls, SMDR
should be programmed to report both incoming and outgoing calls.
System A
PSTN
IN OUT
555-1234 555-1234
The diagram above shows how a single call, routed across a private network, is
both an incoming and an outgoing call in the same system. For private network
calls, outgoing call records report the incoming tandem trunk number in the
STN. field (see System B above). Dialed digits shown on the report do not
reflect any digit manipulation (addition or absorption) performed by the local
system.
Calls across the private 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.
If the system date and time are not synchronized across the private network, it
may be hard to recognize the records for a single call, even when the systems
System B
IN OUT
1234 4+1234
System C
Ext. 41234
IN
41234
Issue 1
August 1998
Page 5-73