Configure a remote PBX as part of the extension list

This example is written for the Canistracci OIL tenant. Create the objects with a Docs Demo prefix, test them on non-production numbers, and then adapt the same structure for the production tenant.

The case was more common than I initially though. The client you are going to move on the MiRTA PBX has several offices and not all of them will be immediately configured on the MiRTA PBX. So you'll have some extensions directly on the tenant and some other behind a remote PBX, like a FreePBX.

Let's make an example with a tenant named "TOWER"

Ext 4401 is on MiRTA PBX

Ext 4402 is on MiRTA PBX

Ext 4701 is on a remote FreePBX

Ext 4702 is on a remote FreePBX

Let's see how you can configure the tenant to allow any extension to call any other extension, as they are all on the MiRTA PBX

You need to start by creating a new extension, like 2000 and use that to register the FreePBX on MiRTA PBX. It is best to set it as "Trunk" extension, so the callerid will be correct for the calls. The FreePBX will be behind the extension 2000-TOWER.

Create a provider not using realtime account and assign the Peer Name as the extension used to register the FreePBX. In this case, 2000-TOWER. Set to be allowed to Allow custom extensions:

400px

Define a "custom prefix" for routing calls to the remote PBX. I used #100##, but you can use anything that will never be dialed directly. Create a routing profile rule going to the provider created above

400px

Now it is time to create a Custom Extension for each one of the extensions registered on the remote PBX. In the security section, you'll set the Security section as following:

400px

Validation

• Confirm the tenant selected in the top bar is Canistracci OIL before creating the example.
• Verify the created objects appear in the expected Configuration menu page.
• Place a controlled test call or run the related status check.
• Remove or disable temporary test numbers when the example is no longer needed.