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-6
Camp-On
3
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.
number of loop-starts required. Refer to Feature Reference guide for details
on the PFT feature.
NOTE:
VMI ports default to FRL=0. To allow the VMS/AA to transfer calls across
the private network, the VMI ports’ FRL should be set to 3.
the private network, the VMI ports’ FRL should be set to 3.
Camp-On
3
Camp-On does not work for calls to non-local dial plan extensions.
Centralized Voice Messaging
(Release 6.1 and Later Systems)
(Release 6.1 and Later Systems)
3
The following features work differently for centralized VMS/AA than for local
VMS/AA systems:
VMS/AA systems:
■
Only MERLIN LEGEND systems can share a centralized VMS. A
DEFINITY ECS or DEFINITY ProLogix system cannot share the MERLIN
LEGEND centralized VMS/AA and MERLIN LEGEND systems cannot
share a DEFINITY system VMS. However, automated attendant systems
can transfer to non-local extensions on any system.
DEFINITY ECS or DEFINITY ProLogix system cannot share the MERLIN
LEGEND centralized VMS/AA and MERLIN LEGEND systems cannot
share a DEFINITY system VMS. However, automated attendant systems
can transfer to non-local extensions on any system.
■
Only the MERLIN LEGEND Mail, Messaging 2000, Intuity AUDIX, and IS-
III AUDIX Voice Power voice mail systems can be used as the centralized
VMS/AA. Other voice mail systems are not supported for Centralized Voice
Mail, even though they may work as local voice mail systems.
III AUDIX Voice Power voice mail systems can be used as the centralized
VMS/AA. Other voice mail systems are not supported for Centralized Voice
Mail, even though they may work as local voice mail systems.
■
For Release 6. and later systems, when a centralized automated attendant
transfers a call to a non-local extension, the transferring system monitors
the call to ensure that it is answered. If the non-local extension is not
available or the call is not answered within the fixed redirect interval (32
seconds), the call stops ringing at the remote destination and is redirected
to an extension on the transferring system (the system with the centralized
VMS/AA) that is programmed to receive redirected calls. This extension
can be the first QCC queue, another extension, or a calling group (the call
is directed to an available member and not sent to calling group coverage).
transfers a call to a non-local extension, the transferring system monitors
the call to ensure that it is answered. If the non-local extension is not
available or the call is not answered within the fixed redirect interval (32
seconds), the call stops ringing at the remote destination and is redirected
to an extension on the transferring system (the system with the centralized
VMS/AA) that is programmed to receive redirected calls. This extension
can be the first QCC queue, another extension, or a calling group (the call
is directed to an available member and not sent to calling group coverage).
NOTE:
Calls transferred by the VMS/AA to a calling group with a non-local
member, and all UDP routes are busy, will go to the redirect
destination upon transfer completion. If a transferred call travels over
a loop-start or ground-start line to the PSTN, it will not return for
redirection.
member, and all UDP routes are busy, will go to the redirect
destination upon transfer completion. If a transferred call travels over
a loop-start or ground-start line to the PSTN, it will not return for
redirection.