Incoming calls from the PBX

This section illustrates how to configure OMniLeads and an Asterisk-based PBX, to derive calls from the PBX to OMniLeads.

Figure 1: Inbound route parameters

We start from the fact that there is a SIP trunk that links OMniLeads with the PBX.

The first thing to define is the DID number assigned to the incoming route that will process calls from the PBX to an OMniLeads destination, since this number (DID of the route) must be dialed by the PBX to send calls from any module (extensions, IVRs, inbound routes, followme, time conditions), towards the destination configured in the OMniLeads route.

Figure 2: Inbound route parameters

From the example (123456 used in Figure 2), the Asteisk PBX should dial calls through the SIP trunk to the number 123456 every time a PBX extensiones or module (IVR, time conditions, inbound routes, etc.) needs to reach the incoming OMniLeads route.

If our Asterisk PBX has a configuration web interface, a new custom extension whose dial field contains the string must simply be generated; SIP/trunkomnileads/123456. The value trunkomnileads is the name of the SIP trunk declared in the PBX.

The custom extension generated to dial to OMniLeads is exemplified in Figures 3 and 4.

Figure 3: OMniLeads PBX custom extension

While the extension in the PBX can have any numbering (exemplified with 2222), the important thing is to send 123456 (in our example) to OMniLeads as highlighted in Figure 4.

Figure 4: OMniLeads PBX custom extension

Once the custom extension is available on the PBX, it is only a matter of dialing 2222 from any module of the PBX, such as an IVR.

Figure 5: from IVR to OMniLeads

Although the derivation of calls to incoming OMniLeads campaigns from an IVR of the PBX is exemplified in Figure 5. We can conclude that PBX extensions can also dial or transfer calls to OMniLeads, as well as PBX modules such as time conditions, followme, inbound routes, etc. they can invoke a custom extension of the PBX that derives calls to OMniLeads.