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
Feature Interactions
Page 3-21
Remote Access
3
Remote Access
3
“Remote Access” on page 8
provides details about setting up and using remote
access in private networks. The scenarios in Chapter 2 provide examples of
remote access setup and use in private networks. In addition, Chapter 4,
“Security,” provides information about how remote access is used in private
networks.
remote access setup and use in private networks. In addition, Chapter 4,
“Security,” provides information about how remote access is used in private
networks.
Remote access allows tandem and UDP calls and non-local private network ARS
users to call out on local trunks connected to the PSTN, permitting cost savings.
Default COR permissions and restrictions must be assigned to all tie or all non-tie
trunks, depending on whether private network trunks are tie trunks (analog, T1-
emulated tie) or non-tie (PRI) facilities. Toll and outward restrictions should be
removed from the COR for these facilities. When a tandem UDP or ARS call is
routed across the private network on tandem trunks, the local COR FRL at the
receiving system is compared to the FRL for the local ARS or UDP route. For the
call to go through, the default COR FRL must be equal to or greater than the route
FRL. UDP and ARS at a remote system can route calls to yet another system on
the private network.
users to call out on local trunks connected to the PSTN, permitting cost savings.
Default COR permissions and restrictions must be assigned to all tie or all non-tie
trunks, depending on whether private network trunks are tie trunks (analog, T1-
emulated tie) or non-tie (PRI) facilities. Toll and outward restrictions should be
removed from the COR for these facilities. When a tandem UDP or ARS call is
routed across the private network on tandem trunks, the local COR FRL at the
receiving system is compared to the FRL for the local ARS or UDP route. For the
call to go through, the default COR FRL must be equal to or greater than the route
FRL. UDP and ARS at a remote system can route calls to yet another system on
the private network.
A Remote Access code can be programmed into the non-local dial plan to allow
toll savings for remote access calls across the private network. Barrier codes and
associated barrier code Disallowed Lists and FRLs should be applied.
toll savings for remote access calls across the private network. Barrier codes and
associated barrier code Disallowed Lists and FRLs should be applied.
A caller can also reach remote access on a networked system by calling in on DID
or dial-plan routed trunks or by calling in on a line/trunk programmed for shared or
dedicated remote access. During Night Service operation, a user can call into a
trunk programmed for shared remote access and use remote access to reach
non-local extensions. As in non-network operation, the local system applies any
required restrictions. Barrier codes and other remote access restrictions should be
assigned for this type of calling.
or dial-plan routed trunks or by calling in on a line/trunk programmed for shared or
dedicated remote access. During Night Service operation, a user can call into a
trunk programmed for shared remote access and use remote access to reach
non-local extensions. As in non-network operation, the local system applies any
required restrictions. Barrier codes and other remote access restrictions should be
assigned for this type of calling.