Station Message Detail Recording (Smdr) Reports Do Not Include Calls Across The Private Network; T1 To Pri Conversion Fails - Avaya MERLIN MAGIX Maintenance And Troubleshooting Manual

Integrated system release 2.0 and earlier
Hide thumbs Also See for MERLIN MAGIX:
Table of Contents

Advertisement

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 Technical Support Organization 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
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 are in the same time zone. When
they are not, time zone differences must also be considered.

T1 to PRI Conversion Fails

T1 to PRI conversion sometimes fails. Here is a typical scenario. The hub system in a private
network has two 100D modules configured as tandem PRI. The 100D module in Slot 5 used B-
channel group 80, and the 100D module in Slot 10 used B-channel group 79. Then the 100D
module in Slot 5 was reconfigured for T1, and the translations were backed up.
Whenever the 100D module in Slot 5 needs to be converted back to PRI, follow these steps to
populate a B-channel group:
1. Move a B-channel from group 79 to 80.
2. Select PRI for Slot 5.
3. Change the switch type to something other than MAGIX-PBX or MAGIX-Ntwk.
4. Change the switch type back to MAGIX-PBX or MAGIX-Ntwk.
The B-channel group 78 will be occupied.
System B
IN
OUT
OUT
555-1234
1234
4+1234
Central Office and Private Network Problems
5
System C
Ext. 41234
IN
41234
5
Troubleshooting Guidelines and Preparation
5-29

Advertisement

Table of Contents
loading

Table of Contents