IVR Menu

From FreeSWITCH Wiki
Jump to: navigation, search


General Concept

You may also want to reference this;


The IVR Menu feature allows you to easily create IVR menus by describing them in XML. (See also phrase macros)

Menus are defined in the autoload_configs/ivr.conf.xml file configuration as below.

<configuration name="ivr.conf" description="IVR menus">
    <!-- demo IVR setup -->
    <!-- demo IVR, Main Menu -->
    <menu name="demo_ivr"
          timeout ="10000"
      <entry action="menu-exec-app" digits="1" param="bridge sofia/$${domain}/888@conference.freeswitch.org"/>
      <entry action="menu-exec-app" digits="2" param="transfer 9996 XML default"/>    <!-- FS echo -->
      <entry action="menu-exec-app" digits="3" param="transfer 9999 XML default"/>    <!-- MOH -->
      <entry action="menu-sub" digits="4" param="demo_ivr_submenu"/>  <!-- demo sub menu -->
      <entry action="menu-exec-app" digits="5" param="transfer 1234*256 enum"/>    <!-- Screaming monkeys -->
      <entry action="menu-exec-app" digits="/^(10[01][0-9])$/" param="transfer $1 XML default"/> <!-- dial ext & x-fer -->
      <entry action="menu-top" digits="9"/>    <!-- Repeat this menu -->
    <!-- Demo IVR, Sub Menu -->
    <menu name="demo_ivr_submenu"
      <entry action="menu-top" digits="*"/>

The IVR Menu supports prompts using the phrase macro. To speak a phrase macro preface your macro name with "phrase:". Be sure to specify the tts-engine, tts-voice, and phrase-lang parameters. See the following menu example.

     <menu name="main"
        timeout ="10000"
           <entry action="menu-exit" digits="*"/>
           <entry action="menu-sub" digits="2" param="menu2"/>
                       <entry action="menu-say-phrase" digits="4" param="enteraccount"/>
           <entry action="menu-back" digits="5"/>
           <entry action="menu-exec-app" digits="7" param="transfer 888 XML default"/>
           <entry action="menu-sub" digits="8" param="menu8"/>


ivr <menu_name>


<action application="ivr" data="main"/>

Note it is sometime necessary to have the following before the call to the ivr application so it won't pick up in early media:

<action application="answer"/>


Menu tag options

  • name - the name of the ivr menu
  • greet-long - the menu prompt played the first time the menu is played. May be a filename (starting with \ or /) or "say:Text to speak" for TTS, or "phrase:phrase_macro_name" to speak a phrase macro.
    • When using a "phrase:my_phrase" you can specify the string to pass along for input pattern matching like so: "phrase:my_phrase:options|option2"
  • greet-short - the shorter version of the menu prompt played when the menu loops. May be filename, say, or phrase.
  • invalid-sound - played when no entry or an invalid entry is made. May be filename, say, or phrase.
  • exit-sound - played when the menu is terminated, May be filename, say, or phrase.
  • inter-digit-timeout - number of milliseconds to wait for a selection
  • timeout - number of milliseconds to wait for a after playing confirm-macro to conform entered digits
  • confirm-macro -
  • confirm-key - the key that tells the IVR that digit-entry is finished. Defaults to #, even if blank.
    • to override the # as a built-in terminator and change it to * enter in the dialplan before you run the ivr this would disable
 <action application="set" data="ivr_menu_terminator=*"/>
  • confirm-attempts -
  • max-failures - maximum wrong digits entry(ies) before ending the menu (default 3 if not specified or invalid (less than 1) values are specified)
  • max-timeouts - maximum timeout retry(ies) before ending the menu (default will use the max_failures value or 3 if both are left blank or invalid (less than 1) values are specified)
  • tts-engine - name of TTS engine to speak text (ie. cepstral). (optional)
  • tts-voice - name of TTS voice to use to speak text (ie. david). (Necessary if tts-engine is specified)
  • digit-len - maximum number of digits to collect before searching for a matching menu entry

Each menu can support a number of actions bound to a key as follows:

  • menu-exit - Exit the IVR menues
  • menu-sub - Load a sub-menu
  • menu-exec-app - Execute a FreeSWITCH dialplan application
  • menu-play-sound - Play a sound file or speak text
 <entry action="menu-play-sound" digits="3" param="say: You pressed 3"/>
 <entry action="menu-play-sound" digits="6" param="voicemail/vm-goodbye.wav"/>
  • menu-back - Return to the calling menu level
  • menu-top - Return to the top level menu
  • menu-exec-api was previously documented on this page and is documented in the FreeSWITCH book - it is however not currently supported.

Playing remote audio files

There are two ways to play remote audio;

  • mod_shout
  • mod_http_cache

Generally speaking, mod_http_cache is the preferred method, and this is explained below.

using mod_http_cache

Here is an example using mod_http_cache;


By using the above, you can avoid hitting the remote server every time the audio needs to be played.

However, it introduces some issues that you need to be aware of;

  • A suitable caching period needs to be used. If it's too high, then changes to the audio file won't happen in a timely fashion. Too low, and you risk having the same problems explained in mod_shout.
  • The initial caching of the audio file directly impacts the IVR. If it takes 2 seconds for the audio file to cache initially, then the IVR will 'freeze' for 2 seconds. You can potentially look at using http_prefetch to get around this.

You will notice that audio files will start playing much quicker than mod_shout, and the first few milliseconds of audio might get cut off. To get around this, just introduce a 500ms sleep, like so;

<action application="answer"/>
<action application="sleep" data="500"/>
<action application="ivr" data="my_ivr"/>

using mod_shout

Here is an example of using mod_shout;


However, you should be aware of the following problems;

  • Every time an audio file needs to be played, a new HTTP request is made to the remote server. This could result in accidental DDoS.
  • Any latency/slowness on the HTTP request will directly impact your IVR (if it takes 2 seconds to download the audio file, the IVR will 'freeze' for 2 seconds).
  • There is noticeable delay between play events, even if your remote HTTP server is on the same machine!
  • For the above reasons, this is not an advisable approach for production systems.


How to route the call if no DTMF is pressed

First, define the IVR main menu like this:

    <menu name="ivr-test"
      <entry action="menu-exec-app" digits="1" param="bridge sofia/internal/1001%"/>
      <entry action="menu-exec-app" digits="2" param="bridge sofia/internal/1002%"/>
      <entry action="menu-exec-app" digits="3" param="bridge sofia/internal/1003%"/>

and then in your dialplan, you need:

   <extension name="from_carrier_to_ivr-test">
      <condition field="destination_number" expression="^15559876543$">
	<action application="set" data="hangup_after_bridge=true"/>
        <action application="ivr" data="ivr-test"/>
        <action application="bridge" data="sofia/internal/1000%"/>

With this config, if the IVR manages to bridge the call, it will hang up when the bridge ends.

But if no DTMF is sent, twice in a row (max-timeouts control that), FreeSWITCH will exit the IVR menu and process the next dialplan line, which bridges to 1000.

How to run several apps with one digit

You need to use the execute_extension app, with the inline parameter.

For example:

  <menu name="ivr-test"
      <entry action="menu-exec-app" digits="1" param="execute_extension limit:'hash ivr in',
bridge:sofia/internal/1001%,playback:ivr/ivr-busy.wav,hangup inline"/>
      <entry action="menu-exec-app" digits="2" param="execute_extension limit:'hash ivr in',
bridge:sofia/internal/1002%,playback:ivr/ivr-busy.wav,hangup inline"/>

With execute_extension, you can add in sequence any apps you need, as in a regular XML extension, but the string containing the apps must not contain whitespaces.

So you need to replace them by \s, or as above, to put the substring with the spaces between ' ':

limit:'hash ivr in'

Also, see the playback and hangup apps after the bridge app.

In an IVR (to be confirmed formally), continue_on_fail=true is the default.

This means that if the bridge is not successful in my example, the file will be played back to the caller and the call will be hung up.

If you don't hang up the call there, the IVR will playback the greetings file again.

To end the call after a successful bridge, you just need to set:

<action application="set" data="hangup_after_bridge=true"/>

from the dialplan before calling the iVR, or in each execute_extension string, as in the previous example above.

Another way to run several apps with one digit

Simply list the same digit multiple times in the IVR menu definition. For instance if you have multiple entries for "1" then each entry for 1 will be executed in sequence if 1 is pressed. Note: if they are executed in reverse order you are using a version of Freeswitch that was built prior to September 2010 - to fix this you can either get a newer version or put the entries in reverse order so that they will be executed in the correct order!

Path for Sound Files

Use an absolute path value for the greeting sounds. When you use a relative path (i.e. you don't start with a forward slash) then it will assume that you want to use a sound file somewhere in the sounds directory structure.

Relative: greet-short="ivr/ivr-menu.wav"

Absolute: greet-short="/full/path/to/file/ivr-menu.wav"


ivr_menu statues

Channel Variable with options of success, failure or timeout

variable_ivr_menu_status: [success]
variable_ivr_menu_status: [failure]
variable_ivr_menu_status: [timeout]

See Also

Variable_ivr_menu_status Channel_Variables