1.5 Administrator's Guide

  1. Home
  2. Docs
  3. 1.5 Administrator’s Guide
  4. Commissioning the unit
  5. FlexPaths
  6. FlexPath use Cases
  7. Partitioning / multi-tenant

Partitioning / multi-tenant

Scenario:

Company A and Company B share a PBX. Each company has reserved a set of BRI channels for their exclusive use.

Company A: 4 BRI channels on BRI ports d1 and d2

Company B: 4 BRI channels on BRI ports d3 and d4

Extensions 8xxx belong to Company A with reception at 8000.

Extensions 9xxx belong to Company B with reception at 9000

Outgoing calls must be routed to the companies’ BRI channels.

Incoming calls on the companies’ BRI lines must be routed to their reception.

Configuration:

Extensions:

  • Extensions ports (both FXS and SIP) are assigned the appropriate extension numbers for each company.

Two outbound routes:

  • companyAout routes over Company A’s BRI channels

  • companyBout routes over Company B’s BRI channels

Two Inbound routes:

  • Fixed incoming DID 8000 is routed to Company A’s reception. This DID will be assigned to BRI calls originating from Company A’s BRI channels in a FlexPath

  • Fixed incoming DID 9000 is routed to Company B’s reception. This DID will be assigned to BRI calls originating from Company B’s BRI channels in a FlexPath

FlexPaths:

  • companyA-in: Add a Start route that transforms incoming BRI calls without DIDs to the reception extension and forward these to the Inbound routes.

  • companyA-in: Add a Match route that transforms incoming BRI calls with any DID to the reception extension and forward these to the Inbound routes.

  • Assign Company A’s BRI trunk groups to the companyA-in FlexPath

  • companyA-out: Include an internal route that facilitates dialing internal extensions

  • companyA-out: Add a rule that matches outgoing numbers other than extensions and routes them to the companyAout outbound route.

  • Assign Company A’s extension ports to the companyA-out FlexPath

  • companyB-in: Add a Start route that transforms incoming BRI calls without DIDs to the reception extension and forward these to the Inbound routes.

  • companyB-in: Add a Match route that transforms incoming BRI calls with any DID to the reception extension and forward these to the Inbound routes.

  • Assign Company B’s BRI trunk groups to the companyB-in FlexPath

  • companyB-out: Include an internal route that facilitates dialing internal extensions

  • companyB-out: Add a rule that matches outgoing numbers other than extensions and routes them to the companyBout outbound route.

  • Assign Company B’s extension ports to the companyB-out FlexPath

Note: Inter-company calls are facilitated by default and can be accessed by directly dialing a company’s extensions (e.g. the receptionist for Company B could dial 8000 to reach the receptionist for Company A.) To disable this, create empty FlexPaths that terminate service for cross-company numbers:

Company A: Create an empty FlexPath that Matches dial pattern 9XXX

Company B: Create an empty FlexPath that Matches dial pattern 8XXX

Note: This is a simplified example. FlexPath could also be used to match incoming DID ranges and route these to separate inbound routes for different partitions.

Note: The incoming CID can also be prefixed with a custom name for inbound routes. To configure this, access the FreePBX Inbound Route configuration (please see section 6.5) and configure the ‘CID name prefix’ field.