Filter
Top Products
MERLIN LEGEND Communications System Release 6.1
Network Reference
555-661-150
Issue 1
August 1998
Troubleshooting
Page 6-14Call to Non-Local Extension Reaches Wrong Extension
6
Call to Non-Local Extension Reaches
Wrong Extension 6
Possible Cause: If a call to a non-local extension connects to the wrong
extension, one or more non-local dial plan extension ranges and/or routes may be
incorrectly programmed. Non-local dial plan numbers must be unique and
unambiguous or calls can be misrouted. Furthermore, digit absorption and
prepending for the routes must be programmed correctly.
What to Do:
First, review the local routing for the call (see “Reviewing the
Non-Local Dial Plan and Routing” on page 3). Then follow the steps below.
1. At your local system, ensure that routing for the destination extension
specifies pools of trunks connecting to the correct adjacent system (if there
is more than one). If digit prepending or absorption is needed, make sure
that it is correctly programmed. If you find an error, you have solved the
problem. If not, proceed to Step 2.
2. If you are directly connected to the system where the destination extension
is located, go to Step 3. Otherwise, the coordinating system manager
should repeat Step 1 for each system through which the call is routed until
you reach the system where the destination extension is located.
3. Check with the system manager at the destination system or with the
coordinating system manager to ensure that the extension number is in the
local dial plan for that system.
NOTE:
The system does not permit programming of non-local extension ranges
that conflict with extension numbers included in the local or non-local dial
plan. However, conflicts can still arise due to digit prepending or absorption
as a call is routed across the private network.
If this is not the problem, call the Lucent Technologies Helpline at 1 800 628-2888;
consultation charges may apply.