Call Routing from 3CX

Routes 3CX calls into a skill either directly through a dedicated extension or by tagging a DID and matching it with a Call Routing Rule.

A 3CX call reaches CCaaS by pointing its destination at a SIP extension registered to CCaaS. Which method fits depends on whether each skill has its own dedicated extension, or a smaller number of extensions need to serve multiple skills.


Routing Directly to an Extension

When a skill has its own dedicated CCaaS-registered extension, any 3CX entry point can be pointed straight at it — no additional CCaaS-side configuration is needed.

  • A DID's Inbound Rule can set Route Calls to directly to the extension
  • A Digital Receptionist menu option can use Connect to Extension to reach it
📘

Prerequisite — SIP Extensions

The extension must already be registered to CCaaS — see SIP Extensions.


Routing via a Call Routing Rule

When multiple DIDs need to fan into skills without a dedicated extension for each, a tag applied in 3CX is matched against a CCaaS Call Routing Rule instead.

Tagging the DID in 3CX

  1. In the 3CX portal, navigate to Inbound Rules

    237
  2. Select the DID to route to a skill

  3. In the Name field, enter a tag identifying the destination skill (for example, Support)

  4. Under Route Calls to, confirm the DID is routed to the extension registered as the CCaaS virtual handset

    571
  5. Select OK

📘

Prerequisite — SIP Extensions

The extension selected under Route Calls to must already be registered to CCaaS — see SIP Extensions.

Configuring the Matching Routing Rule in CCaaS

  1. Navigate to Routing Configuration > Call Routing
  2. Select + to add a new rule
  3. Complete the following fields:
FieldDescription
Routing Rule NameA descriptive name for the rule
SIP HeaderFrom
MatchingContains is recommended
ValueThe tag entered in the Inbound Rule's Name field
DestinationThe skill the call should route to
  1. Select Done, then Make Live to activate the rule
⚠️

Confirm with a Test Call

3CX populates the Inbound Rule's Name tag into the From header's display name. Place a test call to the DID and confirm it routes to the intended skill before relying on the rule in production.

🛑

Configure a Default Skill

A call that matches no routing rule disconnects immediately. A default routing rule or skill group should be configured to catch calls that don't match a specific tag.