The article below describes the concept on how RingLogix partners can setup extension dialing between a RingLogix Hosted PBX and an external PBX (like a 3CX, Avaya, Asterisk, etc.) connected to a RingLogix SIP trunk.

It is a design concept with steps to prepare for the function to work. It is not a step-by-step how-to. For more help with this function please contact our support team.

Design Concepts

Extension Numbering: The simplest way to implement this function is with unique extension numbers on each system. For example, 1XX extensions on the hosted PBX and 2XX extensions on the external PBX.

If this is not possible then prefixes can be used for dialing extensions on the other system. For example, 01101 to reach extension 101 on the hosted PBX and 02101 reach extension 101 on the external PBX.

How your extensions are numbered will affect the outbound routing configuration for each system.

Extension Mapping: To properly route calls between the two systems (and from an external source to an internal extension) you will need to map inbound routes to extension numbers. For this process virtual IDs or real phone numbers will be used.

When routing calls from a hosted PBX to an external PBX extension, a virtual ID will be assigned for each extension on the external PBX. The format for these virtual IDs are usually the [siptrunkID]+[ext#]. For example, “02041234567+101” for extension 101 on the external PBX connected to SIP trunk ID 02041234567.

When routing calls from an external PBX to a hosted PBX extension, a dedicated DID will be required and assigned to each hosted extension. For this step a DID is required.

Outbound Routing and Translations: By default, most PBX systems will try route 3 to 5-digit extension calls internally. Meaning extension calls will NOT be routed externally through a SIP trunk the same way a call to a 10 or 11-digit destination would.

To make this work an outbound route matching the [ext#] or [prefix+ext#] will be needed for each target extension on the other system.

Outbound routes on the hosted PBX will be created by a RingLogix support technician and will route external extension calls to the SIP trunk used by the external PBX.

Outbound routes on the external PBX will need to be setup by the PBX admin and will route matching calls to the SIP trunk.

Inbound Extension Routing: Inbound routes will need to be setup on each system for each extension. This way each system knows… “when I get a call for ### destination, route it to ### extension”.

On the Hosted PBX you simply create an inbound route for each DID to each extension.

On the external PBX you will create an inbound route for each virtual ID to its respective extension. For example, inbound calls to DID/Pattern “02011234567+101” route to extension “101”.



How to Prepare

1. You will need to activate and setup both a SIP trunk and a hosted PBX within the same customer record.

2. You will need to create a list of the external PBX extension numbers and provide it to RingLogix.

3. A RingLogix technician will use your list to create the virtual IDs, outbound rules and translations needed so that calls to those extension numbers are routed out of the hosted PBX and to the SIP trunk connected to your external PBX. The technician will provide you with the list of mapped virtual IDs when ready.

4. On the external PBX, you will need to create inbound routes for each virtual ID to each extension.

5. You will need to activate and assign a DID/Phone number to each hosted PBX extension.

6. You will need to create outbound routes and translations on the external PBX for each hosted PBX extension, so that calls to the hosted extensions are taken out of the external PBX and sent to the SIP trunk. These rules must translate the dialed extension number to the assigned DID for the hosted extension.



Sample Inbound and Outbound Routes for a Yeastar PBX