Enter the members, pick a distribution algorithm, set the timers — get the Line Group, Hunt List, Hunt Pilot, and Pickup Group config you actually have to enter into CUCM Admin.
A CUCM hunt group is three CUCM objects — a Line Group that contains the member DNs and the distribution algorithm, a Hunt List that orders one or more Line Groups, and a Hunt Pilot that is the actual number users dial. Pickup Groups are separate but almost always provisioned in the same breath. This tool takes the information you'd enter by hand on four different CUCM Admin screens and puts it on one form. Output is field-level config ready to paste into CUCM Admin → Call Routing, plus the Pickup Group config.
Enter members + pilot, click Generate config.
The ordered list of DNs + distribution algorithm + RNA timer. Create first.
Points at one or more Line Groups. Route List routing happens here.
The DN users dial. References the Hunt List. Goes in a Partition, uses a CSS.
Top-Down always starts at member #1 and walks down. Use this when you have a ranked escalation path — a senior agent handles every call first, overflow goes to junior agents. The cost is that member #1 gets every call; members #4 and #5 rarely ring. Good for on-call rotations where one person is the designated primary.
Circular rotates the starting position by one each call. This is the correct default for most general sales/support lines because it distributes load evenly across members. CUCM remembers the last-tried member and starts at the next one. If member #3 answered the last call, the next call starts at member #4.
Longest Idle Time picks whichever member has been off-hook the longest. This sounds ideal but has a subtle failure mode: members who are on calls constantly get skipped, and members who park the phone and go to lunch get every call until they come back. Use for small teams (3–6 members) where you want to force fairness; avoid for contact-center workloads (use UCCX instead).
Broadcast rings all members simultaneously. Use only for small groups (≤ 8) and for functions where anyone answering is acceptable (front desk, operator console backup). At larger sizes it creates a phone-tornado that annoys users.
For the RNA timer, 15 seconds is the usual default — long enough for a user to notice but short enough that the next member gets a try before the caller hangs up. Don't use longer than 20 seconds; total wait before hitting final forward is timer × members, and a 10-member group at 20s is 3+ minutes of ringing before voicemail. If you need longer wait, add more members, not more seconds.
Hunt Group for ad-hoc teams under ~10 members with no reporting need. UCCX the moment you need agent states, wrap-up codes, skills-based routing, or call reporting.
Line Group is the members + algorithm. Hunt List is a failover chain of Line Groups. Small hunt groups have a Hunt List with exactly one Line Group — the Hunt List still has to exist.
Pickup Group when calls ring at one phone and you want others to optionally grab them. Shared Line when you always want the call to ring at multiple phones simultaneously.
Yes — each Line Group in the Hunt List has its own algorithm. A common pattern is Circular primary Line Group, Broadcast secondary Line Group for escalation.
It skips members already on a call and rings only idle members. If all members are busy, it falls to the next Line Group in the Hunt List.
Pilot 2000, members 2001–2004, Circular, RNA 15s, final → voicemail
Pilot 3000, L1 agents Top-Down in Line Group A, L2 agents Broadcast in Line Group B as overflow
Pilot 0, 3 receptionist phones Broadcast, RNA 20s, final → night attendant mailbox
The Network & UC Health Assessment includes a Hunt Group / Pickup Group / UCCX decision review — which teams belong where, what should be consolidated, and what should move off CUCM to a proper contact center.