The displayed information will not show agents in Make Busy or in Do Not Disturb.
If the group is in Do Not Disturb or all agents have DND enabled separately, the display shows no call waiting and group in DND.
To activate the attendant overflow feature, you need one dedicated RAD and one ONS port.
If a 'Do Not Disturb' is set on a hunt group pilot number, the group is in 'Do Not Disturb'. Any calls directed to that group will now route to the Night RAD.
If a hunt group is placed in DND, the status of individual members is not affected.
If a stand-alone message is used with no follow-up call handling, the system can clear down the call at the end of the message.
One RAD and one ONS or OPS port is required for each front end message.
One ONS port is required for the trunk answer point.
To activate Front End Messaging, the following equipment is required:
One dedicated RAD and one ONS or OPS port is required for each separate front-end message
One ONS port is required for the trunk answer point.
For each night RAD message, you require one RAD and one ONS port.
The 'Always Rerouting' destination of a phantom group must be another phantom group or a voice group with a RAD assigned.
MCD phantom groups cannot be used as 'Call Forward Busy', 'Call Forward No Answer', Call Reroute' first, or 'Call Reroute Second' destinations of other devices and still retain their MCD rerouting features.
Remote groups or sets accessed across MSDN/DPNSS from phantom groups do not retain originally called number display features.
Call rerouting for MCD calls, which initially route through phantom hunt groups, is based on the first voice group that the call is presented to.
Phantom groups are only used as alternate destinations for front end messaging, attendant overflow, automatic attendant, and MCD voice groups.
The original dialed destination must reside on the same system as the phantom group to be displayed.
To activate Trunk Group Busy RAD, you require one dedicated RAD and one ONS port.
