Lucent Technologies 555-661-150 User Manual
MERLIN LEGEND Communications System Release 6.1
Network Reference
Network Reference
555-661-150
Issue 1
August 1998
Network Management
Page 5-4
General Programming in Private Networks
5
used for emergency or other N11 calls, it should be assigned to the
main pool. In this case, IXC calls determine the number of loop-starts
required. Refer to Feature Reference guide for details on the PFT
feature.
main pool. In this case, IXC calls determine the number of loop-starts
required. Refer to Feature Reference guide for details on the PFT
feature.
At the system where calls are delivered to the PSTN, digit manipulation
may also be required. In the example above where calls are routed from
the 908 area code to the 617 area code, the system in the 617 area code
absorbs
may also be required. In the example above where calls are routed from
the 908 area code to the 617 area code, the system in the 617 area code
absorbs
. ARS tables can be used, under some circumstances, to
send calls to yet another private network system. It may be necessary to
add or absorb digits for further routing.
add or absorb digits for further routing.
3.
Subpatterns. At the system where calls originate, set up the subpatterns
for the table. In doing so, you may wish to check with the non-local system
manager to ensure that the local system routes associated with the primary
time period (sub-pattern A) take advantage of non-local system routes
associated with the secondary time period (sub-pattern B). If the non-local
system is in a different time zone from your own, you may need to take this
into consideration as well.
for the table. In doing so, you may wish to check with the non-local system
manager to ensure that the local system routes associated with the primary
time period (sub-pattern A) take advantage of non-local system routes
associated with the secondary time period (sub-pattern B). If the non-local
system is in a different time zone from your own, you may need to take this
into consideration as well.
4.
Facility Restriction Levels. At the system where calls originate, assign
appropriate FRLs to the routes and to the extensions that will use the
private network lines. Factory settings do not restrict toll calls. At the
system where calls reach the PSTN, assign an FRL to the default class-of-
restriction (COR) for the type of tandem trunk (non-tie for PRI and tie for all
others).
appropriate FRLs to the routes and to the extensions that will use the
private network lines. Factory settings do not restrict toll calls. At the
system where calls reach the PSTN, assign an FRL to the default class-of-
restriction (COR) for the type of tandem trunk (non-tie for PRI and tie for all
others).
discusses this in detail.
Facility Restriction Levels for Extensions
5
FRLs are assigned to extensions. These FRLs apply not only to ARS but to non-
local UDP routing as well. Plan UDP, ARS, and extension FRLs carefully so that
extension users can reach non-local extensions as needed and still be subject to
required limitations on toll calling.
local UDP routing as well. Plan UDP, ARS, and extension FRLs carefully so that
extension users can reach non-local extensions as needed and still be subject to
required limitations on toll calling.
When local system users employ ARS in order to call out over PSTN facilities
connected to a non-local system, the user’s local system applies necessary
restrictions using the ARS or UDP route FRL and the extension FRL. If the caller
has dialed a Remote Access code included in the non-local dial plan on the calling
system, the barrier code FRL on the called system is used instead of the
extension FRL (barrier codes must be required for the default COR setting applied
to the type of tandem trunk used). For the call to leave the local system, the
extension or barrier code FRL must be equal to or higher than the route FRL. The
extension FRL has no effect after the call leaves the local system. At the remote
system, the route FRL is compared to the remote access default COR FRL, which
acts in place of an extension FRL on a local system. For the call to go through, the
remote access default COR FRL must be equal to or higher than the route FRL.
connected to a non-local system, the user’s local system applies necessary
restrictions using the ARS or UDP route FRL and the extension FRL. If the caller
has dialed a Remote Access code included in the non-local dial plan on the calling
system, the barrier code FRL on the called system is used instead of the
extension FRL (barrier codes must be required for the default COR setting applied
to the type of tandem trunk used). For the call to leave the local system, the
extension or barrier code FRL must be equal to or higher than the route FRL. The
extension FRL has no effect after the call leaves the local system. At the remote
system, the route FRL is compared to the remote access default COR FRL, which
acts in place of an extension FRL on a local system. For the call to go through, the
remote access default COR FRL must be equal to or higher than the route FRL.