Common Setups
Common Setup Examples¶
These ready-made configuration recipes cover the most common NexusUC deployment scenarios. Each one walks you through which features to configure and in what order, with links to the detailed setup instructions.
Small Office (2–10 Users)¶
Scenario: A small business with a handful of staff who each need their own phone extension, a shared voicemail for after-hours calls, and basic inbound call routing.
What you'll need:
- 2–10 extensions (one per user)
- 1 inbound DID number
- Business hours time condition
- A shared voicemail inbox for after-hours
Setup steps:
-
Create extensions for each user
-
Attach devices (desk phones or softphones) to each extension
-
Create a Business Hours Time Condition under Applications → Time Conditions
- Set your office hours (e.g., Mon–Fri, 8:30 AM – 5:00 PM)
- Destinations, Time Conditions, and Call Flows
-
Create a shared voicemail inbox for after-hours calls
- Set a greeting like "Thank you for calling [Business Name]. We're currently closed..."
- Enable email delivery so staff receive voicemail notifications
- Set up Voicemail & Shared Voicemail Inbox
-
Configure the inbound destination:
- During business hours → Ring a specific extension or a small Ring Group
- After hours → Route to the shared voicemail inbox
- Set up Inbound Destinations
-
(Optional) Set up a Manual Diversion Call Flow for emergency forwarding to a mobile number
Recommended extension ranges:
| Item | Extension |
|---|---|
| User extensions | 100–109 |
| Shared voicemail | 999 |
| Time Condition | 8000 |
| Call Flow | 9000 |
Medium Business with Departments (10–50 Users)¶
Scenario: A business with multiple departments (e.g., Sales, Support, Accounts). Callers should hear an IVR menu and be directed to the right team. Each department has its own ring group.
What you'll need:
- 10–50 extensions
- 1 or more inbound DID numbers
- An IVR menu (auto attendant)
- Ring groups per department
- Business hours and holiday time conditions
- Voicemail per department or per user
Setup steps:
-
Create extensions for all users
-
Attach devices to each extension
-
Create Ring Groups for each department (e.g., Sales = 6001, Support = 6002)
- Choose a strategy like Simultaneous for small teams or Round Robin for larger ones
- Set a timeout destination (e.g., department voicemail)
- Set up Ring Groups
-
Create an IVR Menu (e.g., "Press 1 for Sales, Press 2 for Support, Press 3 for Accounts")
- Upload a professional greeting recording
- Map each option to the corresponding Ring Group
- Set up IVR Menus
-
Create Business Hours and Holiday Time Conditions
-
Create a Manual Diversion Call Flow for emergency forwarding
-
Wire it all together:
- Inbound DID → Call Flow → Holiday TC → Business Hours TC → IVR Menu → Ring Groups
- After hours → Shared voicemail or diversion mobile
-
(Optional) Import contacts for the company phonebook
Recommended extension ranges:
| Item | Extension |
|---|---|
| User extensions | 100–149 |
| IVR Menu | 5000 |
| Ring Groups | 6001–6005 |
| Time Conditions | 8001–8002 |
| Call Flows | 9001 |
Call Centre (Queue-Based Routing)¶
Scenario: A business that handles high inbound call volumes with dedicated agents. Calls should be queued with hold music and distributed to agents based on a strategy (e.g., longest idle, round robin).
What you'll need:
- Agent extensions
- Call center agents and queues
- Hold music
- Wallboard for live monitoring
- CDR and queue statistics for reporting
Setup steps:
-
Create extensions for each agent
-
Create call center agents linked to each extension
- Set appropriate call timeouts, wrap-up times, and max no-answer counts
- Creating Call Center Agents
-
Create one or more call center queues
- Choose a strategy (e.g., Longest Idle Agent or Round Robin)
- Assign agents with appropriate tier levels
- Set max wait times and timeout destinations
- Creating a Call Center Queue
-
Upload custom hold music for the queue
-
Configure the inbound destination to point to the queue
- Add a Caller ID Name Prefix if handling calls from multiple sites
- Set up Inbound Destinations
-
Enable call recording on the queue for quality assurance
-
Use the Wallboard for real-time monitoring of queue activity
-
Review queue and agent performance via statistics
Recommended extension ranges:
| Item | Extension |
|---|---|
| Agent extensions | 200–249 |
| Call Center Queues | 7001–7005 |
| Time Conditions | 8001–8002 |
| Call Flows | 9001 |
Multi-Site Business¶
Scenario: A business with multiple physical locations (e.g., Sydney, Melbourne, Brisbane) that share a single NexusUC instance. Each site has its own inbound numbers, but the PBX is managed centrally.
What you'll need:
- Separate extension ranges per site
- Multiple inbound DID numbers
- Caller ID Name Prefix to identify call origin
- Site-specific time conditions (if operating hours differ)
- Shared or per-site IVR menus
Setup steps:
-
Plan your extension numbering by site:
Site Extension Range Sydney 100–199 Melbourne 200–299 Brisbane 300–399 -
Create extensions and devices for each site
-
Create per-site inbound destinations with a Caller ID Name Prefix so staff know which site the call is for (e.g., SYD#, MEL#, BNE#)
-
Create site-specific time conditions if office hours differ between locations
-
Create per-site Ring Groups or IVR Menus if each location handles calls differently
-
Create per-site Call Flows for emergency diversion at each location
-
Set up call forwarding between sites for overflow or after-hours coverage
Remote Workers with Softphones¶
Scenario: Staff work from home or on the road and need to use their NexusUC extension from a mobile phone or laptop using the Ringotel softphone app.
What you'll need:
- User extensions with attached users
- Ringotel softphone licenses
- VPS-hosted or remote NexusUC instance (with proxy port or custom FQDN)
Setup steps:
-
Create extensions for remote users (if not already created)
-
Create and attach user accounts to each extension
- Ensure each user has a valid email address for credential delivery
- Ringotel Setup Steps 1–7
-
Activate Ringotel licenses
- Add the organization, activate users, and credentials will be sent automatically
- Activating Ringotel
-
Configure SIP registration for remote access
- Use the Proxy Port method for VPS deployments, or Custom FQDN for partners with their own domain
- SIP Endpoint Registration Options
-
(Optional) Set up call forwarding so unanswered softphone calls fall back to the user's mobile