Route a test DID to an in-group

01 / 05

1. Create the in-group

These steps target VICIdial Admin 2.14-969a, SVN 4037 / database schema 1748. Substitute unused IDs for LAB01, LABTEAM, learner1, 8001, 90001, SALESDEMO and DEMOIVR if any already exist. Labels and options may differ on other builds. The configuration checks below do not establish that a call, audio, or carrier route has been tested.

1. Open Inbound → In-Groups → Add New In-Group.
2. Enter Group ID SALESDEMO and Group Name Sales Demo, choose the appropriate Admin User Group, and set Active to Y for the isolated test. Submit, then reopen SALESDEMO.
3. Review its call-time, queue, no-agent and after-hours actions with the owner before directing a DID to it.

Group ID / Group Name

SALESDEMO / Sales Demo (or unused substitutes)

Admin User Group

Select the group permitted to administer this lab

Active

Y only when ready for the isolated test

View a still screenshot

Enter an inbound group

Open to enlarge

You should seeReopen the group and check Group ID, Group Name and Active. If the ID already exists, stop and choose an unused ID; do not overwrite an existing group. The form image is not proof of a saved group.

02 / 05

2. Route the test DID

Obtain from the carrier or trunk administrator the exact DID digits delivered to the system. Do not assume they match the public display format.

1. Open Inbound → DIDs → Add A New DID, or open the dedicated test DID.
2. For a new DID, enter the exact delivered digits in DID Extension, enter DID Description Test line and choose the Admin User Group permitted to administer it, then submit. Reopen the DID, set DID Route to IN_GROUP and select SALESDEMO in In-Group ID.
3. Save and reopen the DID to verify the pattern, route, target and Active state.

DID Extension

Use the exact delivered test digits from the carrier or trunk administrator, without spaces or dashes. The unsaved demonstration uses 18005550101 as a fictional example; it is not an assigned or callable DID.

DID Description

Test line

Admin User Group

The group permitted to administer this test DID

DID Route

IN_GROUP

In-Group ID

SALESDEMOSALESDEMO is the course target only if it already exists on your system; the unsaved lab illustration uses the distinct existing KPIDEMOQ option.

View still screenshots

Enter a DID identity

Open to enlarge

Select the DID in-group routing controls

Open to enlarge

You should seeReopen the DID: its delivered-digit pattern, Active state, IN_GROUP route and SALESDEMO target must match your change record. If the target is absent, verify the group exists and is accessible before saving again. This does not establish carrier delivery.

03 / 05

3. Allow and select the in-group

For the inbound DID exercise, the companion LAB01 starts as MANUAL. On the captured SVN4037 build, MANUAL excludes the inbound group chooser. For this exercise use INBOUND_MAN: agents may place manual calls and receive inbound calls between them; it does not enable predictive outbound dialing. The native form stores Auto Dial Level 1.0 in this method.

An in-group and a DID alone do not make an agent available.

1. Keep the agent paused/logged out and record LAB01’s current Dial Method, Auto Dial Level, Active, Allow Inbound and Blended and allowed groups. This method change belongs to the isolated lab only.
2. Open Campaigns → Show Campaigns → LAB01. Set Dial Method to INBOUND_MAN; save and reopen. Accept the native 1.0 level for this method; do not force a database0 or change to RATIO to expose inbound controls.
3. Set Allow Inbound and Blended to Y; save/reopen and select only SALESDEMO under Allowed Inbound Groups. Save and reopen again to check both the method and group. Allow Closers is a separate transfer permission.
4. After the DID/in-group, station and user permissions are ready and the test window is approved, set this isolated campaign Active Y only for the exercise; save/reopen before Agent login. Keep the agent paused until the intended SALESDEMO membership and phone connection are verified. If the campaign remains inactive or login/group selection is unavailable, stop before testing.
5. Open Inbound → In-Groups → SALESDEMO. Under Agent Ranks For This Inbound Group, check SELECTED for learner1 and submit; leave Rank and Grade unchanged for this first test.
6. Open Users → Show Users → learner1 and inspect Agent Choose Ingroups; this setting affects whether the agent can choose groups at login. Have the agent log in to LAB01, select SALESDEMO if prompted and reach READY for an authorized test.

Dial Method

INBOUND_MAN for this manual + inbound exercise

Auto Dial Level

1.0 native value in INBOUND_MANThis method excludes automated outbound dialing; it is not a predictive rate.

Allow Inbound and Blended / Allowed Inbound Groups

Y / SALESDEMO only, then save and reopen

LAB01 baseline after the call lab was restored

Open to enlarge

The restored inbound permission baseline

Open to enlarge

You should seeThe reopened campaign is INBOUND_MAN with inbound Y and SALESDEMO selected. If the group chooser remains absent, stop at this configuration gate; do not change queue exits or use predictive dialing as a workaround. At agent login, verify SALESDEMO is actually selected before an authorized READY test.

04 / 05

4. Plan the controlled call

A test call requires an authorized originating phone, working trunk and available agent; none was exercised for this guide.

1. Agree on the test window and record the existing DID route for rollback.
2. During the approved test, follow the call through DID, queue and agent; compare each observation with the configuration.
3. Restore the original DID route and verify it after the test.
4. After the supervised exercise, pause and log out the test agent. Restore the recorded Dial Method, Auto Dial Level, inbound flag, allowed groups and Active state through Admin; save/reopen. Confirm the intended idle state and retain the test record.

You should seeIf the call never enters the system, involve the carrier/trunk operator. If it queues without an agent, inspect agent selection and readiness; if it reaches the wrong destination, recheck the DID’s saved route.

05 / 05

Recorded lab terminal checks

Recorded lab checks were run against the synthetic demo on November 4, 2026. These read-only observations supplement the configuration steps above; they do not establish that a call, route, recording or report workflow succeeded.

Recorded lab observation: Four configured inbound groups; no routing or call outcome tested.

Recorded lab observation: Two configured DID records; no carrier delivery or routing tested.

Recorded lab observation: No current inbound auto-call rows at capture; not an inbound routing test.

Recorded lab observation: The inbound queue columns result describes the installed schema, not a completed workflow.

Recorded lab observation: The did columns result describes the installed schema, not a completed workflow.

mysql --defaults-extra-file=/etc/vicidial-readonly.cnf --batch vicidb -e "SELECT COUNT(*) AS inbound_group_count FROM vicidial_inbound_groups;"mysql --defaults-extra-file=/etc/vicidial-readonly.cnf --batch vicidb -e "SELECT COUNT(*) AS did_count FROM vicidial_inbound_dids;"mysql --defaults-extra-file=/etc/vicidial-readonly.cnf --batch vicidb -e "SELECT COUNT(*) AS active_inbound_rows FROM vicidial_auto_calls WHERE call_type='IN';"mysql --defaults-extra-file=/etc/vicidial-readonly.cnf --batch vicidb -e "SHOW COLUMNS FROM vicidial_auto_calls WHERE Field IN ('campaign_id','status','call_type');"mysql --defaults-extra-file=/etc/vicidial-readonly.cnf --batch vicidb -e "SHOW COLUMNS FROM vicidial_inbound_dids WHERE Field IN ('did_id','did_active','group_id');"

View still screenshots

Recorded lab terminal: inbound aggregate

Open to enlarge

Recorded lab terminal: did aggregate

Open to enlarge

You should seeThe recorded lab command and output show exactly what the demo returned. Use the original workflow’s separate end-to-end acceptance checks before declaring success.