For the technical buyer

What a hosted PBX is, and what you actually administer.

If you have run an on-premise PBX, you know the parts: trunks, extensions, dial plans, registration, failover. A hosted PBX keeps the concepts and moves the box. This page describes how those parts look on 3CTel.

  • Standard SIP endpoints: desk phones, softphones, adapters
  • Extensions, groups, queues and dial plan rules in a portal
  • Failover rules per number, site and user

A hosted PBX is a private branch exchange run as a service by the provider rather than on hardware in your building. Your desk phones, softphones and adapters register to it over the internet as SIP endpoints; extensions, ring groups, queues, menus and dial plan rules are configured in a web portal. 3CTel operates the platform, provisions the endpoints, connects Canadian numbers and builds failover rules with you.

The PBX without the chassis

An on-premise PBX does three things: it registers your phones, applies routing logic to calls, and connects to the public network through trunks. A hosted PBX does the same three things from the provider's platform. Your phones register outbound over the internet, so no inbound ports need to be opened on your firewall. Routing logic lives in the portal. The trunk side is handled by 3CTel and simply appears as numbers on your account.

The practical result is that the skills transfer. If you have built a dial plan, you can read one in the portal. What disappears is the hardware lifecycle, the software patching and the trunk contract.

Endpoints and registration

  • Desk phones: standard SIP phones from the common manufacturers register to the platform with credentials pushed by provisioning. Configuration is central, so a replacement phone picks up the same settings.
  • Softphones: the 3CTel desktop and mobile apps register as endpoints for the user's extension, alongside or instead of a desk phone. Multiple endpoints per extension ring together or in sequence.
  • Analogue adapters: an ATA connects a fax machine, an older door phone or an overhead paging amplifier as a SIP endpoint.
  • Registration over the internet: endpoints register outbound, typically with transport encryption, so remote and on-site phones behave the same and no VPN is required.
  • NAT and firewalls: because registration is outbound, most routers need no special rules. The specialist reviews SIP handling on your firewall for the few that interfere.

Extensions and dial plan

Extensions are the addressable units: users, groups, queues, menus, voicemail boxes and conference rooms. The dial plan decides what happens when a number is dialled, inbound or outbound. On a hosted PBX both are configured in the portal, and a typical inbound plan looks like the example below.

Illustrative; the plan for your organization is built with the specialist.
StepRuleExample
Inbound numberWhich number was dialledMain line, sales line, a direct-dial number for a user
Time conditionOpen, closed or holidayWeekdays 8 to 6; provincial holiday calendar
First destinationMenu, group, queue or extensionMain menu with three options; sales line straight to the sales queue
Ring strategyHow a group or queue ringsRing all for a small group; longest idle for a queue
Timeout and overflowWhat happens when nobody answersEscalate to a second group, then voicemail or AI receptionist
Outbound rulesCaller ID and permissions per userMain number shown by default; direct-dial for account managers; international restricted

Failover and continuity

Platform side

The platform side is operated by 3CTel, not by you. Ask the specialist for the continuity details that apply to your account; they are set out in your agreement.

Site connectivity

If a site loses internet, its endpoints drop registration. Numbers for that site can be configured to route automatically to mobile apps, to another site or to an external number.

User level

An extension with a desk phone and a mobile app keeps ringing on the app when the desk phone is unreachable. No manual forwarding is needed.

Number level

Each inbound number can have an unreachable-destination rule distinct from its busy or no-answer rules, so an outage is treated differently from a missed call.

Administration

The portal exposes users, endpoints, numbers, time conditions, menus, groups, queues, recording, voicemail and reporting. Administrator roles can be scoped to a site or to a subset of settings. Changes apply immediately, and the change history shows who altered what.

For organizations that prefer to delegate, 3CTel support makes changes on request. Most technical customers do routine changes themselves and involve support for larger restructures or number moves.

Technical questions, answered

Can we bring our own SIP phones?

In most cases, yes, provided they are standard SIP devices rather than models locked to a specific PBX vendor. The specialist checks the models and firmware, and provisioning templates exist for the common manufacturers. Phones that cannot be provisioned centrally can sometimes be configured manually, but a supported model is easier to manage across a fleet.

How do direct-dial numbers map to extensions?

Each user or destination can have its own DID, a public number that bypasses the main menu, or share the main number and be reached through the menu or by transfer. DIDs are ported or provisioned per user, and the dial plan sends each one straight to its extension while still applying time conditions and overflow rules where you want them.

Is a hosted PBX the same as UCaaS?

They overlap. Hosted PBX describes the telephony core: registration, routing and numbers as a service. UCaaS describes a broader bundle that adds messaging, video meetings and presence on the same platform. 3CTel's service includes both: the hosted PBX described here plus business SMS, video meetings and the desktop and mobile apps.

Migrating from an on-premise PBX

  1. Export the current dial plan

    Extensions, groups, time conditions and numbers are documented from the existing system so nothing is rebuilt from memory.

  2. Rebuild and test on temporary numbers

    The plan is recreated in the portal and tested end to end with real endpoints, while the old PBX keeps carrying live calls.

  3. Port numbers, in stages if needed

    Numbers can move in groups, for example one site or one department at a time, with the old PBX forwarding in the interim.

  4. Decommission

    Once every number has moved and the last endpoint is registered, the old PBX and its trunks are retired.

Frequently asked questions.

Usually not. Endpoints register outbound to the platform, so no inbound ports are opened. The specialist reviews your firewall's SIP handling during setup.

Bring your dial plan. We will rebuild it.

Share how your current PBX is set up and a specialist maps it onto 3CTel, tests it on temporary numbers and quotes the migration.

Call 3CTelBuild My System