Queued Call Console (Qcc); Reminder Service; Remote Access - Lucent Technologies MERLIN LEGEND Release 6.0 Network Reference Manual

MERLIN LEGEND Communications System Release 6.0
Network Reference 555-660-150
3 Feature Interactions

Queued Call Console (QCC)

Queued Call Console (QCC)
An extension may not have its calls covered by a QCC on another system.
A QCC operator can manually extend a non-local dial plan extension call to a local
extension, non-local dial plan extension, or a destination outside the private
network. If the destination is a non-local extension and the call extending is
completed to a busy or invalid number, the transfer can be returned only if the
transfer took place over tandem PRI trunks. If the transfer took place over tandem
tie trunks, it is not returned in the event that the destination is busy or invalid.
A QCC Pool Status button shows activity on private network trunk pools as well
as other trunk pools on the local system.
A call from a non-local dial plan extension over tandem trunks can be prioritized
as an LDN or Dial 0 call to the QCC. A call from the QCC to a non-local dial plan
extension is treated as an outside call for the purpose of the Conference Join
function.

Reminder Service

Reminder Service does not function across a private network.

Remote Access

"Remote Access" on page 2–6
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 networks.
Remote access allows tandem and UDP calls and non-local 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
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 network.
A Remote Access code can be programmed into the non-local dial plan to allow
toll savings for remote access calls across the network. Barrier codes and
associated barrier code Disallowed Lists and FRLs should be applied.
3
3
3
provides details about setting up and using remote
Issue 1
February 1998
Page 3-14