Mlx Displays: Network Call Display Problems - Lucent Technologies MERLIN LEGEND Release 6.0 Network Reference Manual

MERLIN LEGEND Communications System Release 6.0
Network Reference 555-660-150
6 Troubleshooting

MLX Displays: Network Call Display Problems

5. Make some test calls across the network. If calls are at the proper levels,
the problem is solved. If transmission levels are still incorrect, proceed to
Step 6.
6. If the identifiers appear correct but the distance between systems is
between 180 and 220 miles, you may need to experiment with switch
identifiers in order to achieve the correct transmission levels. Return to
Step 4.
If changing one or more switch identifiers do not solve the problem,
Possible Cause 2: More than three analog spans are involved in the call.
What to Do: This may occur when calls are transferred or forwarded multiple
times across analog facilities. Consider changing to digital facilities if this situation
occurs frequently. Contact your Lucent Technologies representative or Local
Authorized Dealer for instructions.
If the problem is not solved with the above instructions, call the Lucent
Technologies Helpline at 1 800 628-2888; consultation charges may apply.
MLX Displays: Network
Call Display Problems
There are several possible causes for this problem, all of them easy to check:
Possible Cause 1: Non-local extension calls and outside calls routed on tandem
tie trunks display at recipient MLX display telephones as outside calls, for
example,
What to Do: Check the call routing and find out whether any tandem tie trunks are
included in the route. You may need to contact the coordinating system manager.
If the call originated from the PSTN on a PRI or BRI facility with Automatic
Number Identification (ANI), the original calling party information displays when
network routing is over tandem PRI trunks only. Check the call routing and see
whether any tandem tie trunks are included in the route.
Possible Cause 2: Call transferred to the extension.
What to Do: If the call was transferred to the extension, only the transfer
originator information displays, not the name and/or number of the original caller,
even if PRI ANI was available for the original call.
Possible Cause 3: Display Preference setting for MLX incorrect
What to Do: If the call route for an intersystem call includes only tandem PRI
trunks and the call was not transferred, the Display Preference setting for the MLX
.
6
Issue 1
February 1998
Page 6-20