Instruction manual

Group Hunt Page 1607 of 3156
Features and Services
If a MADN multiple call arrangement must be used, a supervisor set must be
assigned to the hunt group. This supervisor set must be given the one and only
prime appearance of the MADN. Any other appearance must have the
MADN programmed as a secondary DN (any DN key other than 0). In this
way, the supervisor set controls the status of the MADN and thus the group
hunt treatment. If the supervisor set is busy, the hunt does not terminate on
the MADN.
Multi-Party Operations
As per the existing Multi-Party Operations (MPO) feature, recovery of
misoperation of call transfer will not be applied to incoming calls which are
transferred on ringing to a Pilot DN by transferring parties who are waiting in
GPHT queues for service.
Night Answer by Time of Day
If a Pilot DN is defined as one of the NITE DNs in LD 15, then incoming calls
directed to the Pilot DN will be presented to the next idle DN in the group. At
the instant of changeover (change from one night DN to another), Group
Hunting, if still active, will keep on hunting for the next idle DN in the group.
Night Service
If a Pilot DN is defined as a NITE DN or trunk NITE DN, then incoming calls
directed to the NITE DN or trunk NITE DN will be presented to the next idle
station in the hunt group.
On Hold on Loudspeaker
Group Hunt to a loudspeaker DN can be programmed, but will be ignored if
configured as Make Set Busy (MSB) by call processing.
Override
Ring Again
Override and Ring Again will not be supported.