MERLIN LEGEND Communications System Release 6.1 | Issue 1 |
Network Reference | August 1998 |
6 Troubleshooting |
|
DID Calls Not Completed | Page |
|
|
■If not enough trunks are available, consider adding more to the system.
■If there are sufficient trunks assigned and the problem persists, the cause of the problem may be at an intervening system between the one where the calls are received from the PSTN and the destination. Go to Possible Cause 2.
■If there are sufficient trunks and routes and there are no intervening systems between the one where the calls are received from the PSTN and the destination, contact the provider of the DID service. If this does not solve the problem, call the Lucent Technologies Helpline at
1 800
Possible Cause 2: The FRL for the default COR for all tie
What to Do: Check with the coordinating system manager so that he or she can determine where the problem exists. This may involve more than one system, depending upon how your private network is set up. For example, a call might be routed across the private network in a fashion such as this:
Origin System A→System B→System C→Destination System D
In this configuration, the coordinating system manager must check routes and default COR attributes for Systems B and C.
■Check to make sure the calling restriction of the default COR is set to unrestricted. The factory setting is outward restricted, which blocks calls across the private network.
■Check that the routes voice/data capability is correct for the type of call being made. The factory setting is Both, which will support both voice and data calls.
■In each intervening system, compare the FRLs assigned to routes for the call with the default COR FRL. The route FRL must be equal to or lower than the default COR value or the call is blocked. The factory setting is 3.
■If FRL settings are not the cause, call the Lucent Technologies Helpline at 1 800
