Hunt group configuration

Hunt groups are intended to organize a waiting queue, monitor resource states, and connect waiting objects with resources based on configured strategies. Calls can be placed in the queue. Call placement in the queue is managed by the IVR role via feature codes (featurecode) of type 'hunt' and 'queue'.

The article describes examples with minimal settings for hunt groups to work.

Hunt group configuration

The required number of sipuser entities must be configured beforehand. The vector — default — created by default in the system is used; settings of the other entities are given below.

vectorrules entity settings
  • Name (title) — to 9*

  • Vector (vector) — default

  • Destination number (tonumber) — 9*

  • Action (action) — To service (featurecode)

  • Source number modifier (modfromnumber) — T

  • Destination number modifier (modtonumber) — T

Other parameters at defaults.

featurecodes entity settings
  • Prefix (prefix) — 912

  • Type (type) — Queue (hunt)

Other parameters at defaults.

hunt entity settings
  • Code (code) — test_hunt

  • Phone number (phonenumber) — 11

  • Operators — add the required number of rows to the table and select the previously created sipuser entities; priority can be set to 1.

After performing these settings, make a call to number 91211 and make sure the call reached the devices of the hunt group participants.

Template configuration

An object can be a template on the basis of which queue descriptors are dynamically built when a call arrives at the subscriber feature code "queue". One hunt entity instance can define a single format of different queues for several (or all) objects — users or groups. The entity is treated as a template if the 'opts.template_type' field value is 'personal' or 'group'.

A sipuser entity must be configured beforehand (for the example with number 101) for the 'personal' template, or a group number for 'group'. The vector — default — created by default in the system is used; entity settings for the 'personal' template are given below.

vectorrules entity settings
  • Name (title) — to 9*

  • Vector (vector) — default

  • Destination number (tonumber) — 9*

  • Action (action) — To service (featurecode)

  • Source number modifier (modfromnumber) — T

  • Destination number modifier (modtonumber) — T

Other parameters at defaults.

featurecodes entity settings
  • Prefix (prefix) — 913

  • Type (type) — Personal queue (queue)

Other parameters at defaults.

hunt entity settings
  • Code (code) — test_template_hunt

  • Phone number (phonenumber) — 12

  • Template mode (opts.template_type) — Personal queue (personal)

  • Number filter mask (opts.filter_number) — XXX (the XXX mask corresponds to 3-digit sipuser numbers)

After performing these settings, make a call to number 913101 (101 is the sipuser number) and make sure the call reached the device.