A tour of the 3CX Admin Console
A guided tour of the 3CX Admin Console — where to find extensions, trunks, rules, reporting and backups.
The 3CX Admin Console is the single place where your phone system is configured: who has an extension, how calls come in and go out, what happens after hours, and how your data is backed up. If you have ever opened it and felt lost, you are not alone — but once you know where each thing lives, day-to-day changes take minutes rather than a support ticket.
This is a guided tour, not a click-by-click manual. We will walk through the main areas and flag the few spots where a wrong setting can cost you calls or money — so you know where to find extensions, trunks, routing, reporting and backups.
What the Admin Console actually is
The Admin Console (sometimes called the management console) is the browser-based control panel for your 3CX phone system, separate from the Web Client your staff use to make and receive calls. As the administrator you sign in to change how the system behaves; everyone else just uses the phones and apps.
It is organised by function — extensions, trunks, routing, and so on — usually down a left-hand menu, and most changes apply immediately with no reboot. You do not need to touch most of it: a typical business lives in three or four areas and leaves the rest alone. The console looks the same whether 3CX is cloud, self-hosted or on-premise; if you are still deciding, see our guide on hosting options.
People and lines: Extensions and SIP Trunks
An Extension represents a person, desk or reception point, tying together their number, voicemail, apps and permissions — the area you will visit most. Here you create users, set voicemail-to-email, handle IP phone provisioning for handsets such as Yealink, Fanvil and Snom, and decide what each person can do across the Web Client and the Windows, Mac, iOS and Android apps. For more, see managing extensions and provisioning desk phones.
Extensions let your team call each other; to reach the phone network you need a SIP trunk — the connection to your provider that carries calls in and out, along with your numbers (DIDs). Two things matter most: the trunk must show a connected registration status or no outside calls work, and its capacity (simultaneous calls) affects busy-hour performance.
Trunk setup is one of the trickier parts of 3CX, especially around firewalls and audio. If you would rather not wrestle with it, this is exactly what we set up and support — call SIP Connect on 1300 747 266, or read SIP trunks explained and our walkthrough on connecting a SIP trunk.
Routing: where calls go and when
Routing decides what happens to a call once it arrives or leaves — the heart of how your business sounds to a caller. It is built from a few pieces:
Inbound Rules
DID routing that sends each incoming number to the right place.
Outbound Rules
which trunk a call uses based on the number dialled.
Digital Receptionist (IVR)
the auto-attendant that says "press 1 for sales".
Ring Groups
ring several people at once or in sequence.
Call Queues
hold and distribute callers using a polling strategy: Hunt/Ring all, Round robin, Least talk time or Longest waiting.
Office Hours
business hours and holidays that switch between day and after-hours routing.
For more complex logic — surveys, conditional routing, callbacks — the Call Flow Designer (CFD) is a visual builder for custom call handling. We cover each of these in our guides on inbound and outbound rules, the digital receptionist, call queues and after-hours routing.
Reporting, recording and integrations
The reporting area covers call logs and statistics — volumes, missed calls, queue performance and agent activity — useful for staffing and spotting problems. Call Recording settings sit nearby; it is easy to switch on, but in Australia it carries legal obligations around consent, so read our guide on call recording and your obligations first.
This is also where you connect 3CX to tools you already use — Microsoft 365 for contacts and presence, Microsoft Teams for calling, and CRM integration so calls log against customer records. If your team lives in Teams, see 3CX with Microsoft Teams.
Security and backups: the part not to skip
Two areas quietly protect your system, and both are worth a few minutes:
- Security and anti-fraud limits — controls that cap unusual activity and block toll fraud, where someone hijacks your system to make expensive international calls. Sensible limits can save you thousands; see securing 3CX against toll fraud.
- Backup & Restore — schedule regular backups so a failure or a fat-fingered change never means rebuilding from scratch. See our backup and restore guide.
You may also see network components such as the Session Border Controller (SBC) and STUN settings, which help calls pass through firewalls and NAT. These are easy to get wrong and a common cause of one-way audio, so they are best left to whoever installed the system. None of this needs doing at once — get extensions and routing right first, then switch on backups and security.
What we see installing this in Melbourne
Most Melbourne SMEs we hand the Admin Console over to only ever touch four screens: Users, Inbound Rules, Office Hours and the holiday list. Everything else — trunks, SBC, anti-fraud limits — we set once during the cutover and lock down. The mess usually starts when someone reads a forum post and changes an outbound rule at 4pm on a Friday.
The other recurring pattern is the office NBN. A 40/20 FTTC service looks fine on a speed test and then chokes on six concurrent calls because the upload is shared with Teams video and a Dropbox sync. We test with the trunk provider's live audio loop on the actual office connection before go-live, not from our workshop, and we leave SIP ALG off on the router — almost every consumer-grade gateway ships with it on.
Post-cutover we sit with reception for the first morning, fix the inevitable IVR wording, and turn call recording on only after the consent message has been signed off — Australian state laws on recording vary and getting that wrong is the expensive mistake.
Frequently asked questions
Do I need to be technical to use the Admin Console?
For everyday changes — adding a person, updating after-hours routing, changing a voicemail greeting — no, those are point-and-click jobs. The deeper plumbing, like SIP trunks and the SBC, is where technical knowledge pays off, and it is fine to leave that to your provider.
What is the difference between the Admin Console and the Web Client?
The Admin Console is where you configure the system: extensions, trunks, rules and security. The Web Client is what staff use to make and take calls, check voicemail and see who is available. Admins use both; everyone else only needs the Web Client and the apps.
Can SIP Connect manage the console for us?
Yes. We are a Melbourne-based team that installs and supports 3CX for Australian businesses, so we can set it up, lock it down and handle changes for you, or just be on call when you need a hand. Start with a free bill review or visit our contact page.
Get a free bill analysis — and stop overpaying
Send us a recent phone or internet bill. We’ll show you exactly where the waste is — our bill reviews have identified savings of up to 65%.