Mlx Displays: Private Network Call Display Problems - Lucent Technologies MERLIN LEGEND Release 6.1 Maintenance And Troubleshooting Manual

MERLIN LEGEND Communications System Release 6.1
Maintenance and Troubleshooting 555-661-140

MLX Displays: Private Network Call Display Problems

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: Private 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 private 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 display telephone extension may not be programmed as you expect. The
factory setting displays the caller's extension number. Check System Planning
Form, MLX Telephones, for the recipient extension or see "Display Preferences
for Intersystem Calls" in Chapter 5 of Network Reference to check the setting
.
Issue 1
August 1998
Page 5-69