Call Forward by Call Type (Hunting Option)
This enhancement to the Hunting feature provides the capability for the system to send an internal call to a Directory Number (DN) different from the DN used for an external call when the telephone is busy.
A common way to use this capability is when the dialed telephone is already busy with a call, internal calls can be redirected to Voice Mail messaging while external calls can be redirected to a person.
To enable the Call Forward by Call Type (Hunting Option) capability, you must allow the Hunting (HTA) feature in addition to the Call Forward by Call Type (CFTA) feature in the Class of Service (CLS) of the telephone.
Additional CLS CFTA prompts:
- HUNT xxxx - internal, busy DN
- FDN xxxx - internal, no answer DN
- EHT xxxx - external, busy DN
- EFD xxxx - external, no answer DN
Short hunting takes place along the key strip and any Meridian propriety telephone. The hunt chain begins on a DN on the key strip. The call hunts up the keys until it reaches a feature key, an unassigned key, or the Last Hunt key (LHK), defined in LD11). If the call cannot reach an available DN, the caller hears busy tone. when the call hunts to a Multiple Appearance DN, all appearances with ringing are allowed. For a TN with Hunting Control enabled, Short Hunt takes precedence over normal Hunting
On a busy condition, ext 4378 is supposed to short hunt to 3378, then on RNA at 3378 hunt to 5555 (Meridian Voice Mail).
On a RNA condition, ext 4378 is supposed to forward to 5555 (Meridian Voice Mail).
FDN = xxxx (internal call forwarding), HUNT = xxxx
(external call forwarding) - may both be set to Meridian Voice Mail's DN.
CLS features enabled are FNA HTA MWA (Message Waiting Allowed).
LHK is 1 (The system will hunt until the first appearance of a DN, feature key or LHK. If LHK is 0, there will be no hunting)
PROBLEM: Hunting and Forwarding do not work!
If hunting/forwarding does not work for a particular set, check KEY 00
to see if MARP is enabled.
Using hyper-terminal, print the TNB of the set in question: in the keys section, check MARP is shown next to key 00.
To do this in MAT or Optivity, double click the KEY 00 button, and check that MARP is "yes".
MARP indicates that this set 'owns' the DN. If it doesn't 'own' the DN, it cannot control the hunting/forwarding conditions. In other words, if not MARP'd, hunting/forwarding will not work as expected!
To change MARP in hyperterminal:
LD 11 REQ: chg TYPE 2616 TN 4 1 12 1 ECHG yes ITEM key oo scr 4378 HNT FNA MARP on TN 004 0 11 01 MARP yes
MARP on TN showns you the TN of the set that currently 'owns' this number (and thus controls the call forwarding features). This will always default to the lowest physical TN unless you manually change it.
MARP prompt, if you input YES (the default is NO), a message prints out to indicate that a MARP has changed:
SCH5524 DN X..X NEW MARP L S C U
X..X represents the new DN
L S C U represents the Loop number, Shelf number, Card number, Unit number of this telephone.