Nortel DMS-100 Hunt Group Table (HUNTGRP)

Table Name

Hunt Group Table

Functional Description of Table HUNTGRP

Table HUNTGRP contains the data for each hunt group assigned in the switching unit.

If a switching unit has feature BR0750 (Hunt Group Size Expansion), then a Distributed Line Hunt (DLH) group, Directory Number Hunt (DNH) group, or Multiline Hunt (MLH) group can be assigned up to 1,024 members.

For switching units without feature BR0750, a DLH, DNH, or MLH group can be assigned up to 256 members.

The maximum number of members for a Bridged Night Number (BNN) hunt group is 210.

The Terminating Fault Option (TFO) specifies the type of search that is made of a hunt group's members for an incoming call.

If field TFO is set to "Y" (yes), then an incoming call attempts to terminate to the first member that appears idle, regardless of whether that member has passed line diagnostics.  A DLH group must have field TFO is set to "Y" because DLH overrides the fault flag.

If field TFO is set to "N" (no), then an incoming call searches the hunt group for an idle line, but skips over any members that have failed line diagnostics.  If no idle member is found, then a second search for an idle line is made through the members that have failed line diagnostics.  Members that have failed line diagnostics are put last in the search order for an idle line.  Incoming calls have a better chance of completing if field TFO is set to "N".

The following information is applicable to switching units with software package NTX806AA (Enhanced Call Forwarding - POTS) and Plain Ordinary Telephone Service (POTS) hunt groups.  Software package NTX806AA is required for the feature Call Forward Group Don't Answer (CFGDA).

Feature CFGDA can be assigned to MLH, DLH, BNN, and DNH groups on a hunt group basis.

Either feature Call Forward Don't Answer (CFDA) or feature CFGDA can be assigned to the pilots of only MLH and DLH groups.  Features CFDA and CFGDA are mutually exclusive in function on MLH and DLH groups.

Call Forward Don't Answer can be assigned as CFDA to individual lines within a DNH group, and as CFGDA to the DNH group on a group basis.  The line CFDA takes precedence over the group CFGDA, on a directly dialed DN.

The number of lines within a DNH group that can be assigned individual CFDA is restricted by the real-time considerations based on the number of features that can be assigned to a DNH group.

The forward Directory Number (DN) of a CFGDA group must never be a member of the same hunt group.  This looping unnecessarily exhausts the simultaneous call limit and has a cost of real-time efficiency.

Field LINETYPE allows for the distinction between POTS and Meridian Digital Centrex (MDC) lines.  If MDC is selected, then calls can be forwarded within or outside an Integrated Business Network (IBN) hunt group.

Call Forward Group Don't Answer can be assigned so that calls to an idle hunt group station ring for a predetermined amount of time before being forwarded either to the next station in the hunt sequence or to a DN outside the hunt group, but inside the customer group.  This feature can be assigned only by the operating company; subscribers must contact the operating company to assign or deassign CFDA or to change the forward DN.  The DN can be of any size up to 30 digits.  No translation verification is performed when CFDA is entered into the database whether through the Service Order System (SERVORD) or table control, except to ensure that the station does not forward to itself.

The data for the CFDA and CFGDA features is stored in table CFW (Call Forwarding).  Adding the CFGDA feature to table HUNTGRP automatically updates table CFW; similarly, updating table CFW updates table HUNTGRP.

The Terminating Billing Option (TBO) is incompatible with features CFGDA and CFDA.

Feature ISDN Packet single DN (AF6872) allows DLH, DNH, MLH, or PRH hunt groups to be assigned on the Voice Interface (VI) Circuit Mode Data (CMD) appearance of a shared DN.  Only DLH and DNH type hunt groups can be assigned to the Packet Mode Data (PMD) appearance of a DN.  A DN can only be datafilled as shared if SOC option NI000051 is on.

The following table control rules for shared ISDN terminals apply to table HUNTGRP:

If the Line Overlflow to DN (LOD) is a 1 + 10 digit inter-LATA call, the Primary Inter-LATA Carrier (PIC) assigned to the phone will not be used for the call.  LOD is an overflow feature and does not reference line options for call routing.  The Equal Access (EA) option for selector NET GEN in table IBNXLA (IBN Translation) can be used to specify a PIC in this situation.

The LODDN field in table HUNTGRP allows the capability to store DNs from 1 to 30 digits for the overflow option LOD.

Enhanced 911 Emergency Services

The following two options support E911:

If field E911PSAP is set to "Y", then two sets of subfields are possible, depending on the option (LDTPSAP or LINEPSAP), and the corresponding subfields are prompted for.  If neither option LDTPSAP nor LINEPSAP has been assigned to a hunt group, then field E911PSAP for that hunt group entry has a default value of "N".

Option LDTPSAP can be added to a MLH group only with Line Class Code (LCC) IBN.  Option LINEPSAP can be added to a MLH, DLH, or DNH group with LCC IBN.

Note:  When adding option LDTPSAP or LINEPSAP, do not manually update table HUNTGRP through the table editor.  Table HUNTGRP is automatically updated when either of these options is added to an IBN hunt group, using SERVORD.

The LDTPSAP or LINEPSAP data is added to table HUNTGRP through field E911PSAP.  When adding to or changing a hunt group tuple, the field name is E911PSAP.  When positioning or listing on a hunt group tuple, the field name is LDTLNOPT.

Table HUNTGRP has a new field named NATLXLA.  Entry to this field is prompted when assigning or modifying options LINEPSAP and LDTPSAP.  If the entry to this field is "Y" (yes), call translations to the PSAP are based on 10 digits (with NPA) and the PSAPDN field in table E911PSAP is datafilled with 10 digits.  If the entry is "N" (no), call translations to the PSAP are based on 7 digits (without NPA) and the PSAPDN field in table E911PSAP is datafilled with 7 digits.  This affects 911 call routing.

Release NA012 adds fields SNGLSANI and WANITYPE to table HUNTGRP.  The SNGLSANI prompt occurs when the LDTPSAP option ENHDISP is equal to "Y".  Field SNGLSANI defines the ANI spill as either single or double.  The WANITYPE prompt occurs when SNGLSANI is equal to "Y" or when ENHDISP is equal to "N" and NUMIDIGS is equal to one or three.  Subfield WANITYPE defines the source for the ANI spill.  The WANITYPE field also exists as a subfield to ENHDISP when ENHDISP is equal to "N".  The following represent the wireless ANI types:

Release NA016 adds field OVFLFLSH to table HUNTGRP.  The OVFLFLSH prompt occurs when LDTPSAP option ANISPILL is equal to "Y".  Field OVFLFLSH enhances the current FLASHING ANI feature, activated in table E911ESN, to include calls that get overflowed from one PSAP to another when all members are busy.  If the OVFLFLSH option is activated for the terminating PSAP and Call Processing recognizes the call as being overflowed, then the flash bit is set.

Assignable Hunt Group Types

The following types of hunt groups can be assigned in the switching unit.

Directory Number Hunting

Each line in the hunt group has a unique DN.  The hunt group can be accessed by dialing the main number (called the pilot DN) or by dialing the DN of one of the hunt group members.  Hunting starts at the number dialed.  The number of lines hunted to find an idle line is dependent on the hunting option assigned to the DNH group.

If option Circular Hunting (CIR) is assigned to the group, then all lines in the hunt group are hunted, regardless of the start point.

The following types of hunt groups can be assigned in the switching unit.

Directory Number Hunting

Each line in the hunt group has a unique DN.  The hunt group can be accessed by dialing the main number (called the pilot DN) or by dialing the DN of one of the hunt group members.  Hunting starts at the number dialed.  The number of lines hunted to find an idle line is dependent on the hunting option assigned to the DNH group.

If option Circular Hunting (CIR) is assigned to the group, then all lines in the hunt group are hunted, regardless of the start point.  If CIR is not assigned, then the default is sequential hunting (sometimes called linear hunting).  Sequential hunting starts at the number dialed and ends at the last number in the hunt group.  Therefore, if the pilot DN is not dialed, not all lines are hunted.

For optimum performance, no more than 70 lines within a given group should have any combination of features CFDA, CFW/CFX, MSB, RMB, SHU, DTM, or CDIV (Call Diversion), regardless of whether they are activated or not.

CDIV features can only be provided in a switching unit (international) with universal translations.

The above option limitations are not enforced by table control.

Multiline Hunting

Only a pilot DN is associated with the hunt group.  To access the group, the pilot must be dialed.  Hunting starts with the pilot and ends at the last line, in a sequential fashion.

For optimum performance, no more than 140 lines within a given group should have any combination of features MSB, RMB, SHU, DTM, or CDIV.

CDIV features can only be provided in a switching unit (international) with universal translations.

The above option limitations are not enforced by table control.

Multiple Position Hunting

MPH with queue allows the distribution of calls evenly across multiple non-data-link attendant consoles.  Calls are presented to the consoles in the order they arrive at the DMS-100 family switch.  Calls that cannot be presented to any console are enqueued in the DMS-100 switch until a console is available to serve that call.

A call is directed to a multiple hunting arrangement by associating a DN with each call type in the console group.  A maximum of 32 call types are supported.  To establish a multiple position arrangement, primary tables requiring datafill include SCGRP, SDGRP, MPHGRP, MPHCON, HUNTGRP, and HUNTMEM.

Night Service is activated by the operation of a Service Control Point (SCP) from the master console in a console group.  If Night Service is activated, arriving calls are redirected to a predefined DN.  The Night Service DNs are assigned separately for each call type.

Many hunt group options are either not assigned to MPH groups, or have no effect on MPH hunting patterns.  These options are CIR, TFO, LOR, LOD, CFGD, OFR, OFS, and TRMBOPT.

Options that are incompatible with MPH groups are ACD, AUL, BC, CFB, CFD, CFGD, CIR, CWI, CWX, DNH, DSCWID, DTM, LOD, LOR, MDN, OFR, OFS, RAG, RMB, SCMP, SCWID, SETMODEL, SHU, SLQ, SMDICND, SOR, SORC, TFO, TRMBOPT, and UCD.

To forward all calls directed to a MPH group (not all calls to a console group), Call Forwarding can be assigned to the pilot of that hunt group.  Activation of Call Forwarding by the pilot redirects all calls destined for the hunt group to the forwarded-to number.

Other restrictions that apply are as follows:

Call Request Retrieval (CRR) calls can be made to consoles but queuing of this type of call is not supported.

Distributed Line Hunting

Only a pilot DN is associated with the hunt group.  To access the group, the pilot must be dialed.  Hunting always starts on the subsequent line in the group.

If the line where hunting starts is not idle due to an origination, the next line is checked.  This continues until the hunting start point is reached.  At this point, busy tone is returned unless options Line Overflow to DN (LOD) or Line Overflow to Route (LOR) are assigned to the hunt group.

DLH is assigned to large hunt groups that require equal distribution of calls.

For optimum performance, no more than 170 lines within a given group should have any combination of features MSB, RMB, DTM, or CDI, regardless of whether they are activated or not.

CDIV features can only be provided in a switching unit (international) with universal translations.

The above option limitations are not enforced by table control.

Bridged Night Number

This type of hunt group has several BNNs that can be formed into a BNN hunt group.  Hunting is sequential unless option CIR is assigned to the hunt group.


The following options can be assigned to DNH, MLH, and DLH groups:

If the hunt group belongs to an IBN customer group, the pilot DN and the hunt group members must belong to the same customer group.  The LOD number can be outside the customer group.

If the hunt group has option LOD, the following applies for a Ring Again (RAG) request.

If a party calls the hunt group only to find it busy as well as the overflow DN busy, then the RAG request is activated against the LOD line and not against the hunt group.  RAG Recall is activated against the REQUESTOR only if the LOD line becomes idle.

If any member of the hunt group becomes idle, the RAG Recall is not activated against the REQUESTOR.  When the REQUESTOR answers the RAG Recall, the LOD DN is rung back.

The operation of the LOD option for translation and billing is as follows:

For assignment of members to a hunt group, see table HUNTMEM.

Datafill Sequence

The following tables must be datafilled before table HUNTGRP:

To create a hunt group using table control, add hunt group datafill in the following order:

  1. Table HUNTGRP
  2. Table LENLINES, or IBNLINES, or KSETLINE
  3. Table HUNTMEM

To delete hunt group datafill, remove data in the reverse order.

Deletion of a MPH, MLH, or DLH hunt group from table HUNTGRP can cause line data corruption.  The line data corruption is from partially datafilled hunt members, members that are datafilled in the lines table but not in table HUNTMEM (Hunt Member).

To avoid line data corruption, do not delete a MPH, MLH, or DLH hunt group from table HUNTGRP if line data exists for members in tables LENLINES, IBNLINES, or KSETLINE.

The table size 0 to 8,192 tuples.

Datafill

The following table describes datafill for table HUNTGRP:

----------------------------------------------------------------------------------------------
Table HUNTGRP Field Descriptions

Field       Subfield       Entry                       Explanation and Action
---------------------------------------------------------------------------------------------
HTGRP                      0 to 32,767                 Hunt Group Number
                                                       Enter the hunt group number assigned 
						       to the hunt group.  Any entry outside
						       the range of indicated values for this
						       field is invalid.
----------------------------------------------------------------------------------------------
SNPA                       Numeric                     Serving Numbering Plan Area
                                                       Enter the Serving Numbering Plan Area 
						       (SNPA) to which the hunt group belongs.
----------------------------------------------------------------------------------------------
DN                         Numeric                     Directory Number
                           (up to 15 digits)           Enter the listed DN of the hunt group.
----------------------------------------------------------------------------------------------
GRPTYP                     See Subfield                Group Type
                                                       This field consists of subfield GRPTYPE
						       and refinements. 

            GRPTYPE        BNN, CPU, DLH, DNH,         Hunt Group Type
	                   MLH, MPH, PRH,              Enter the type of hunt group:
			   or UA  
			                               BNN: Bridged Night Number
						       CPU: Call Pickup
						       DLH: Distributed
						       DNH: Directory Number
						       MLH: Multiline
						       MPH: Multiple Position
						       PRH: Preferential Hunt
						       UA:  Universal Access
						       
						       Any entry outside the range indicated
						       for this field is invalid.
----------------------------------------------------------------------------------------------
-End-












GRPTYPE = BNN, DLH, DNH, MLH, or PRH

Datafill CIR, TFO, TRMBOPT, TRMBILL, LOROPT, LODOPT, CFGADAOPT, OFROPT, OFSOPT, LDTLNOPT, SIZE, and OPTIONS, subfields as follows.

----------------------------------------------------------------------------------------------
Subfield       Entry                       Explanation and Action
---------------------------------------------------------------------------------------------   
CIR            Y or N                      Circular Hunt
                                           If the hunt group type is DNH and it is arranged for
					   circular hunt, enter "Y" (yes).  
					   Otherwise, enter "N" (no).
----------------------------------------------------------------------------------------------
TFO            Y or N                      Terminating Fault Option
                                           If an attempt is made to terminate to the first idle
					   member of a hunt group, regardless of whether or not
					   the member has passed line diagnostics, enter "Y".
					   If GRPTYPE is DLH, then TFO must be "Y".  If an 
					   attempt is made to search for an idle member of a 
					   hunt group that has passed line diagnostics, before
					   searching for an idle member that has not passed line
					   diagnostics, enter "N".  Incoming calls have a better
					   chance of completing if TFO is "N".
----------------------------------------------------------------------------------------------
TRMBOPT        Y or N                      Terminating Billing Option
                                           If the optional terminator software package is 
					   provided, and if a record is generated for each call
					   to a member of the hunt group, enter "Y". 
					   Otherwise, enter "N".
----------------------------------------------------------------------------------------------
TRMBILL        PILOT, RCVD, or TERM        Type of Terminator Billing
                                           If service is billed to the pilot DN of the hunt 
					   group, enter PILOT.  If service is billed to the
					   number that the terminating office receives, enter
					   RCVD.  If service is billed to the DN that was
					   actually terminated on, enter TERM.
----------------------------------------------------------------------------------------------
LOROPT                                     Line Overflow to Route Option
                                           Datafill the LOR subfield.
----------------------------------------------------------------------------------------------
LOR            Y or N                      Line Overflow to Route
                                           If the hunt group is arranged to overflow to a route
					   if all lines are busy, enter "Y" and datafill the 
					   following subfields.  Otherwise, enter "N".
----------------------------------------------------------------------------------------------
TABID          AOSS, AOSSAMA, IBNRT2,      Table Name
               IBNRT3, IBNRT4, IBNRTE,     Enter the routing table that calls are routed to if
	       OFR2, OFR3, OFR4, OFRT,     all lines are busy.
	       RRTE, TOPS, TOPSAMA, 
	       or TTL4
----------------------------------------------------------------------------------------------
KEY            0 to 1,023                  Index
               or Alphanumeric             Enter the index (route reference number) within the 
	                                   routing table that all calls route to if all lines 
					   are busy.  If the TABID field iis set to AOSS, 
					   AOSSAMA, TOPS, or TOPSAMA, then enter the call 
					   origination.
----------------------------------------------------------------------------------------------
LODOPT                                     Line Overflow to Directory Number Option
                                           Datafill the subfield LOD.
----------------------------------------------------------------------------------------------


----------------------------------------------------------------------------------------------
LOD           Y or N                       Line Overflow to Directory Number
                                           If the hunt group is arranged to overflow to a DN if
					   all lines are busy, enter "Y" and datafill the 
					   following subfields.  Otherwise, enter "N".
----------------------------------------------------------------------------------------------
LODDN          Numeric                     Line Overflow Directory Number
               (up to 30 digits)           Enter the DN to which all overflow calls route.
	                                   Note: Alphabetic characters are not allowed.
----------------------------------------------------------------------------------------------
CFGDAOPT                                   Call Forward Group Don't Answer Option
                                           Datafill the CFGDA subfield.
----------------------------------------------------------------------------------------------
CFGDA          Y or N                      Call Forwarding Group Don't Answer
                                           Enter "Y" if the switching unit has software package
					   NTX806AA (Enhanced Call Forwarding - POTS) and the 
					   hunt group has the CFGDA feature and datafill the 
					   following subfield.  Enter "N" if the switching unit
					   has software package NTX806AA and the hunt group does
					   not have the CFGDA feature or if software package
					   NTX806AA is not in the load.
----------------------------------------------------------------------------------------------
LINETYPE       MDC or POTS                 Line Type
                                           Enter MDC if CFGDA applies to a MDC hunt group.
					   Enter POTS if CFGDA applies to a POTS hunt group.
----------------------------------------------------------------------------------------------
-End-

Datafill Example

The following example MAP display shows sample datafill for table HUNTGRP:

All the lines in the examples are located in SNPA 613.

Hunt Group 0

This hunt group is a non-circular (field CIR) multiline hunt group (fields GRPTYP and GRPTYPE) with a listed DN of 725-2865.  The TFO and TRMBOPT fields are set to "N", and the service is billed to the number that the terminating office receives (RCVD).  If all lines in the group are busy, calls overflow to the OFRT table, index (IDX) 6 (fields LOR, TABID, and KEY).  Service is billed to the number received by the terminating office, as set in the TRMBILL field.  This group has the CFGDA feature with line type POTS.

The screening class for a forwarded call is ABCD (field SCRNCL).

The maximum number of calls forwarded is 10.

If a call is not answered within 20 seconds (field TIME), the call is forwarded.  The unanswered calls are forwarded to DN 725-2870.

The calls that overflow to the OFRT table are registered on a remote hardware register (field OFR).  The SD card is mounted on MTM 0, circuit 14.  The SD point is 3, and the normal state of the SD point is open.  No software register is incremented (field OFS).

There are no PSAP options.

The hunt group can have a maximum size of 25 members.

Hunt Group 1

This hunt group is a non-circular (field CIR) bridged night number (fields GRPTYP and GRPTYPE) with a listed DN of 621-8080.  Field TFO is set to Y.

The TRMBOPT field is set to "N", and the service is billed to the number that the terminating office receives (RCVD).  The hunt group does not overflow to a route if all lines are busy (field LOR).  If all lines in the group are busy, calls overflow to DN 621-8025.  This hunt group is not provided with feature CFGDA.

Neither a remote hardware registered, nor a software register is incremented (fields OFR and OFS).  There are no PSAP options.

The SMDI option is selected using message desk 63 and data link SMDI64.

The hunt group can have a maximum size of 35 members.

Hunt Group 2

This hunt group, which can have a maximum size of 35 members, is a circular directory hunt (DNH) group (fields GRPTYP and GRPTYPE) with a listed DN of 725-2856.  This group is not arranged to overflow to a DN or to a route, and does not increment a software or hardware register when all lines in the group are busy.  The TFO field is set to N.

Service is billed to the number that the terminating office receives (the TRMBILL field).  A record is generated for each call to a member of the hunt group.  This hunt group is provided with the Call Forwarding Group Don't Answer feature (the CFGDA field).  The MDC call is forwarded to the DN 725-6756.

The base station is rung for 15 seconds before the call is forwarded.  Incoming intragroup calls are denied forwarding.

There are no PSAP options.


HTGRP   SNPA   DN       GRPTYP   GRPDATA
___________________________________________________________________________________________
0       613    7252865  MLH      N N N RCVD Y OFRT 6 N Y POTS ABCD 10 20 7252870 Y MTM 0 14
                                 3 0 N N 25 $
1       613    6218080  BNN      N Y N RCVD N Y 6218025 N N SMDI 63 SMDI 64 35 $
2       613    7252856  DNH      Y N Y RCVD N N Y MDC Y 7256756 Y 15 CFGDI N N N 35 $