🇬🇧
Omnileads Docs
ComunidadForo
English
English
  • 👶Introduction to OMniLeads
    • OMniLeads General Specs
    • Architecture and components
  • 🚀OMniLeads installation methods
    • Deploy using Docker
      • Deploy with Docker-Destkop
      • Deploy with Docker for VPS Cloud or VM
      • Deploy with Docker for VPS Cloud or VM with External Bucket
    • Deploy with Ansible
      • AIO (All-In-One) Deploy
      • AIT (All-In-Three) Deploy
      • HA (High Availability) Deploy
      • Backups, Restores, Upgrades and Rollbacks
      • Migration from CentOS7
    • OMniLeads Enterprise
    • Development Enviroment Deploy
    • First Login
    • TLS/SSL Certificates
    • Monitoring and observability
    • Security considerations
  • ⚙️Initial Configuration
    • External Authentication
    • Text To Speech (TTS)
  • 🎯CX Survey (Pro)
    • Reports
  • 📈Premium Reports (Pro)
    • Activity Reports
    • Analyzing Results
  • 🎞️Video Calls (Pro)
    • Wordpress Plugin
    • Initial Configuration
    • Webphone Demo
    • Embedding the Webphone
  • ☎️Voice Channel Configuration
    • General SIP trunk parameters
  • 🆗Whatsapp Channel Settings (Pro)
    • OMniLeads & GupShup
    • Register WhatsApp Business in GupShup
    • Message Templates and Time Groups
    • Providers
    • Lines
  • 🚧Wallboard for Business (Pro)
    • Creating a Wallboard
    • Adding Widgets and Realtime Pages
    • Exploring Widgets and Metrics
  • 📤Whatsapp Bulk Messaging (Pro)
  • 💬Contact Campaigns
    • Inbound Campaign
      • Incoming Call Routing
      • Forwarding incoming calls from the PBX
      • Time range conditioned routing
      • IVR - Interactive Voice Response
      • Incoming Caller ID
      • Ejecución de dialplan personalizado
    • Manual Campaign
    • Preview Campaign
    • Dialer Campaing
    • Whatsapp Campaign (Beta)
  • 🎧Agent handbook
    • Login Logout
    • Manual calls from contact list
    • Preview Calls
    • Dialer inbound calls
    • Inbound calls
    • Calls between agents
    • Contact List
    • Whatsapp Messages
  • 🛑Reports, recordings and monitoring
    • Recordings
    • Incoming Campaign Reports
    • Outbound Campaign Reports
    • General call report
    • Agent reports
    • Whatsapp reports (Beta)
    • Conversation Reports
    • Supervision
  • 📊Backoffice - Management audit
  • ☎️Integration between OMniLeads and PBXs
  • 🛠️IT administrator's tasks
  • 🧩CRM Integration
    • Interaction from OMniLeads to CRM
    • Interaction from CRM to OMniLeads
  • 🔐Security considerations
  • 📌OMniLeads RESTful API
    • Agent Session API in Asterisk
  • 🗒️Release Notes
  • ❤️Community
  • 🎇About us
Con tecnología de GitBook
En esta página
  1. Contact Campaigns
  2. Inbound Campaign

Forwarding incoming calls from the PBX

AnteriorIncoming Call RoutingSiguienteTime range conditioned routing

Última actualización hace 12 meses

Forwarding incoming calls from the PBX to OMniLeads

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

Figure 1: Call forwarding from PBX We start from the fact that there is a SIP trunk that links OMniLeads with the PBX. The first thing that must be defined is the number assigned to the incoming route that will process the call from the PBX to an OMniLeads destination, since this number (route DID) must be dialed by the PBX to send calls from any module (extensions, IVRs, incoming routes, follow me, etc.) of said PBX, to the destination configured in the OMniLeads route:

The idea of creating an extension pointing towards OMniLeads is illustrated in figures 3 and 4: If our Asterisk PBX has a web configuration interface, we can simply generate a New custom extension and make it point to SIP/trunkomnileads/123456, where "trunkomnileads" is the name configured in the PBX to designate the SIP trunk with OMniLeads.

Using the route with the DID 123456 as shown in the previous figure, the Asterisk PBX should generate calls through the SIP trunk to the mentioned number whenever any PBX resource needs to reach the 123456 destination of OMniLeads. _Figure 2: Incoming route parameters

Figure 3: Custom extension for OMniLeads Although the extension in the PBX can have any number (2222 was used as an example), the important thing is to send 123456 (in our example) to OMniLeads, as highlighted in the following figure:

Figure 4: Custom extension for OMniLeads Once the extension is available in the PBX, it is only a matter of invoking it from any module of the PBX, such as an IVR:

Figure 5: Forwarding to OMniLeads from IVR Although the figure above exemplifies the forwarding of calls to incoming OMniLeads campaigns from a PBX IVR, we can conclude that PBX extensions can also dial or transfer calls to OMniLeads, and that PBX modules such as time conditions, follow me, incoming routes, etc. can invoke a custom PBX extension that forwards calls to OMniLeads.

💬