Custom asterisk dialplan

With this module an Asterisk developer can route calls to your custom dialplan.

OMniLeads run Asterisk like a PBX engine, then any developer who know about Asterisk syntax can write your own dialplan in order to customized the call flow.

  • Inbound routes
  • Inbound campaigns
  • Failover destination
  • Outbound routes
  • Etc.

Therefore, it is allowed to generate an invokable node within a call flow, this node being Asterisk programming syntax, customized according to any specific need that is outside the scope of the typical OMniLeads modules.

For example, a developer can write a dialplan to integrate different business processes and numerous data sources to your IVR using API integrations with CRM or ERP.

Custom destination settings

The custom destination module simply involves a form indicating the name of the custom dialplan node and also the Asterisk dialplan triad:

  • Context
  • Extension
  • Priority

Where to route the call affected by this node (Custom destination field). We also have the need to indicate a destination in case of failure.

_images/telephony_custom_dst.png

figure 1: custom dst view

Asterisk developer can generate your own dialplan on the oml_extensions_custom.conf file.

Example

We will implement the dialplan

[omnileads_custom]
exten => s,1,Verbose(2, omnileads custom dialplan)
same => n,Answer()
same => n,Playback(demo-congrats)
same => n,Hangup()

Then, we will write the code on oml_extensions_custom.conf the file is on “/opt/omnileads/asterisk/etc/asterisk” dir.

Then, we must to create a custom destination node.

_images/telephony_custom_dst_example.png

figure 2: custom dst example

Finally we can invoke our node, from an IVR option, conditional on time or incoming route.

_images/telephony_custom_dst_example_2.png

figure 3: custom dst example