Ctrl K
ring2all.com

Ring Groups Module Documentation

Table of Contents

  1. Module Overview (Technical)
  2. Module Overview (Commercial/Business)
  3. Module Overview (End User/Administrator)
  4. Configuration Fields Reference
  5. Ring Strategies
  6. Member Configuration
  7. Common Scenarios & Examples
  8. Limitations & Important Notes
  9. Troubleshooting Tips
  10. Glossary

---

1. Module Overview (Technical)

What Are Ring Groups?

Ring Groups distribute incoming calls to multiple destinations based on configurable strategies. When a call reaches a ring group extension, the system rings members simultaneously, sequentially, or in other patterns until someone answers or timeout occurs.

Architecture

Plaintext
┌─────────────────────────────────────────────────────────────────┐
│                   Ring Group System                             │
├─────────────────────────────────────────────────────────────────┤
│                                                                 │
│  Caller dials Ring Group extension (e.g., 2000)                 │
│       │                                                         │
│       ▼                                                         │
│  ┌──────────────────────────────────────────────────────────┐   │
│  │              Load Ring Group                             │   │
│  │  SELECT * FROM public.ring_groups                        │   │
│  │  WHERE extension = '2000' AND enabled = TRUE             │   │
│  └──────────────────────────────────────────────────────────┘   │
│       │                                                         │
│       ▼                                                         │
│  ┌──────────────────────────────────────────────────────────┐   │
│  │              Load Members                                │   │
│  │  SELECT extension, delay, timeout                        │   │
│  │  FROM public.ring_group_members                          │   │
│  │  ORDER BY order_index                                    │   │
│  └──────────────────────────────────────────────────────────┘   │
│       │                                                         │
│       ▼                                                         │
│  ┌──────────────────────────────────────────────────────────┐   │
│  │              Apply Strategy                              │   │
│  │                                                          │   │
│  │  Simultaneous: Ring all at once                          │   │
│  │  Sequence: Ring one by one                               │   │
│  │  Enterprise: Cascade with delays                         │   │
│  │  Random: Random order                                    │   │
│  │  Rollover: First available                               │   │
│  └──────────────────────────────────────────────────────────┘   │
│       │                                                         │
│       ▼                                                         │
│  Member answers OR Timeout → Fallback Destination               │
│                                                                 │
└─────────────────────────────────────────────────────────────────┘

Key Tables

TablePurpose
public.ring_groupsRing group definitions
public.ring_group_membersMember extensions and settings
public.ring_group_settingsAdditional configuration

Key Files

FileDescription
admin/apps/web/src/modules/ringGroups/Frontend module
admin/apps/web/src/i18n/en/ringGroups.jsonTranslations
telephony/freeswitch/lua/main/xml_handlers/ring_group/ring_group.luaMain handler
telephony/freeswitch/lua/main/xml_handlers/routing/ring_group.luaRouting handler
---

2. Module Overview (Commercial/Business)

Business Value

Ring Groups enable team-based call handling:

Without Ring GroupsWith Ring Groups
Single-line per personTeam shares one number
Missed calls frequentMultiple coverage
No routing controlFlexible strategies
Manual call forwardingAutomatic distribution

Use Cases

  1. Sales Teams
- All sales reps ring simultaneously

- First available takes the call

  1. Support Departments
- Sequential ringing by priority

- Escalation through tiers

  1. After-Hours Coverage
- Ring primary, then backup

- Fallback to voicemail

  1. Reception Backup
- Reception rings first

- After 15 sec, add backup staff

Feature Highlights

FeatureBenefit
5 StrategiesSimultaneous, Sequence, Enterprise, Random, Rollover
Skip BusyAvoid disrupting calls in progress
Caller ID PrefixIdentify call source
Per-Member Delay/TimeoutGranular timing control
Call ScreeningRequire confirmation
RecordingRecord all group calls
Follow-MeRespect member forwarding
Fallback DestinationRoute unanswered calls
---

3. Module Overview (End User/Administrator)

What Can You Do?

  • Create ring groups with extensions
  • Add members with individual timing
  • Configure ring strategies
  • Set caller ID prefixes
  • Enable call recording
  • Configure timeout destinations

Administrator Workflow

Plaintext
┌─────────────────────────────────────────────────────────────────┐
│              Creating a Ring Group                              │
├─────────────────────────────────────────────────────────────────┤
│                                                                 │
│  Step 1: Basic Information                                      │
│  ├─ Group Name: "Sales Team"                                   │
│  ├─ Extension: 2000                                            │
│  └─ Strategy: Simultaneous                                     │
│                                                                 │
│  Step 2: Caller Experience                                      │
│  ├─ Greeting: sales_greeting.wav                               │
│  ├─ Ringback: Music on Hold                                    │
│  └─ Caller ID Prefix: "Sales:"                                 │
│                                                                 │
│  Step 3: Members                                                │
│  ┌───────────────────────────────────────────────────────────┐  │
│  │ Member 1: 101 (Alice) | Delay: 0s | Timeout: 20s          │  │
│  │ Member 2: 102 (Bob)   | Delay: 0s | Timeout: 20s          │  │
│  │ Member 3: 103 (Carol) | Delay: 0s | Timeout: 20s          │  │
│  └───────────────────────────────────────────────────────────┘  │
│                                                                 │
│  Step 4: Timeout Destination                                    │
│  └─ Module: Voicemail | Destination: 101                       │
│                                                                 │
│  Step 5: Save                                                   │
│                                                                 │
└─────────────────────────────────────────────────────────────────┘

Quick Tips

TIP
Strategy Choice: Use Simultaneous for small teams, Sequence for escalation.
TIP
Caller ID Prefix: Add "Sales:" so members know call origin.
CAUTION
No Members = Fast Busy: Always have at least one member.

---

4. Configuration Fields Reference

Ring Group Fields

FieldDescriptionExample
Group NameUnique identifierSales Team
ExtensionDialable number2000
StrategyCall distribution methodSimultaneous
Ring TimeoutSeconds per round30
Skip BusySkip busy membersOn/Off
Timeout DestinationWhere to route unans callsVoicemail/IVR
EnabledGroup active statusOn/Off

Caller Experience Fields

FieldDescription
GreetingAudio played before ringing
RingbackWhat caller hears while waiting
Caller ID Name PrefixPrefix for caller ID name
Caller ID Number PrefixPrefix for caller ID number
Distinctive RingCustom ring pattern

Behavior Fields

FieldDescription
Call ScreenRequire member key press
Call ForwardRespect user's CF settings
Follow MeRespect Follow-Me configs
Missed Call ActionEmail/SMS on missed
RecordRecord group calls
---

5. Ring Strategies

Strategy Comparison

StrategyBehaviorBest For
SimultaneousRing all members at onceSmall teams, fast answer
SequenceRing one at a time, in orderEscalation, priority
EnterpriseCascade with configurable delaysMixed availability
RandomRandom member selectionLoad balancing
RolloverFirst available memberSimple backup

Visual Comparison

Plaintext
Simultaneous:
─────────────────────────────
  101 ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓
  102 ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓
  103 ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓
       0────────────────────→ time

Sequence:
─────────────────────────────
  101 ▓▓▓▓▓▓▓░░░░░░░░░░░░░░
  102 ░░░░░░░▓▓▓▓▓▓▓░░░░░░░
  103 ░░░░░░░░░░░░░░▓▓▓▓▓▓▓
       0────────────────────→ time

Enterprise (with delays):
─────────────────────────────
  101 ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓
  102 ░░░░▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓
  103 ░░░░░░░░▓▓▓▓▓▓▓▓▓▓▓▓▓
       0────────────────────→ time

---

6. Member Configuration

Member Fields

FieldDescriptionExample
DestinationExtension or dial string101
OrderSequence priority1, 2, 3...
Delay (sec)Wait before ringing0, 5, 10
Timeout (sec)Per-member ring time20
Confirm PromptRequire key pressNone/Confirm
EnabledMember active statusOn/Off

Delay Examples

Immediate Ring All:
MemberDelayEffect
1010Rings immediately
1020Rings immediately
1030Rings immediately
Cascading Ring:
MemberDelayEffect
1010Rings immediately
1025Joins after 5 sec
10310Joins after 10 sec
---

7. Common Scenarios & Examples

Scenario 1: Sales Team (Simultaneous)

Configuration:
  • Extension: 5000
  • Strategy: Simultaneous
  • Timeout: 20 sec

Members:
OrderExtensionDelayTimeout
1201020
2202020
3203020
Result: All 3 ring at once. First answer wins.

Scenario 2: Tiered Support (Sequence)

Configuration:
  • Extension: 5001
  • Strategy: Sequence
  • Timeout: 60 sec

Members:
OrderExtensionDelayTimeoutDescription
1301015Tier 1
2302015Tier 2
3303015Supervisor
Result: Rings 301 for 15s, then 302 for 15s, then 303.

Scenario 3: Cascading Reception (Enterprise)

Configuration:
  • Extension: 5002
  • Strategy: Enterprise

Members:
OrderExtensionDelayTimeoutDescription
1100030Primary Receptionist
21011020Backup 1
31021515Backup 2
Result: 100 rings immediately. After 10s, 101 joins. After 15s, 102 joins.

---

8. Limitations & Important Notes

Technical Limitations

WARNING
Member Limit: Performance may degrade with 20+ simultaneous members.
WARNING
External Destinations: External numbers may have carrier delays.

Best Practices

  1. Reasonable Timeouts: 15-30 sec per member
  2. Skip Busy: Enable to avoid disruption
  3. Fallback Required: Always set timeout destination
  4. Test Strategies: Verify behavior before production
  5. Monitor Usage: Check CDR for answer rates

---

9. Troubleshooting Tips

Common Issues

SymptomPossible CauseSolution
No ringingNo membersAdd members
Fast busyGroup disabledEnable group
Wrong orderOrder not setReorder members
Caller hears silenceRingback not setConfigure ringback
Calls not answeredTimeout too shortIncrease timeout

Diagnostic SQL

List ring groups:

Sql
SELECT id, extension, name, strategy, ring_timeout, enabled
FROM public.ring_groups
WHERE domain_id = [domain_id];

Check members:

Sql
SELECT m.extension, m.order_index, m.delay, m.timeout, m.enabled
FROM public.ring_group_members m
WHERE m.ring_group_id = [ring_group_id]
ORDER BY m.order_index;

---

10. Glossary

TermDefinition
Ring GroupCollection of extensions sharing calls
StrategyAlgorithm for distributing calls
DelayWait time before member starts ringing
TimeoutMax ring time per member
FallbackDestination for unanswered calls
Skip BusyIgnore members on other calls
Call ScreenRequire member confirmation
CascadeGradually add ringing members
---

Lua Script Status ✅

Fixed Issues

IssueBeforeAfter
Schemacore.ring_groupspublic.ring_groups
Domain lookupcore.tenantspublic.domains
Members tablecore.ring_group_memberspublic.ring_group_members
Settings tablecore.ring_group_settingspublic.ring_group_settings
Variable namingtenant_iddomain_id
--- Documentation last updated: January 2026
AI Assistant

👋 Hello! I'm your Ring2All documentation assistant. I can help you find information about configuring and using the Ring2All PBX platform.

How can I help you today?