/
1.4.6 Callback routes

1.4.6 Callback routes

Owned by Piotr Mrozek
Last updated: Nov 13, 2024

The Callback routes section enables defining different routes which can handle the callback trigger calls.

Callback scenarios can be setup in many ways using the settings below, giving flexibility to the callback operation. 

General

  • Name
    a name of the Callback route, used to distinguish routes in the Dialing Plan setup
  • Dest. leg prefix
    the Dialing Plan prefix (number) a customer (source leg) is connected with after the callback call has been triggered.
    Usually this prefix points to the Dialing Plan, VoipBox route type with the "PIN" scenario.
  • Authorized client desttination  prefix
    the Dialing Plan prefix (number) a customer (source leg) is connected with after the callback call had been triggered and the ANI (caller id) has been authorized by Voipswitch.
    Usually this prefix points to the Dialing Plan, VoipBox route type with the "Ask for number" scenario.
  • Triggering delay
    time in seconds between the callback trigger and the callback call to the source leg
  • Do not ask for number after dest. leg has ended
    when the destination leg ends a callback connection, the source leg is asked again for a new destination number, so it can make many calls. If this option is ticked the call will be disconnected. - this applies only to callback route if the destination prefix is not routing the call to an IVR scenario but to certain route directly (e.g. a retail client or specified external number). When the prefix routes the B leg to an IVR scenario  first please use the "...+only once" scenario to get the same effect.

Charging

For recognized users only - CallBack can be triggered only by users recognized by CallerID

this option disables the PIN callback so only clients with their Caller ID registered in the system are able to trigger callback calls:

    • Retail clients using the "ANI numbers" list or the "Recognize when ANI=login" feature
    • IVR clients using only the "ANI numbers" list
  • Client who will be charged for unauthenticated calls
    the client selected from CallBack or Retail clients which will be charged for the PIN callback calls where the PIN has not been authorized
  • Charge calls only when both legs were connected

    if ticked, the failed callback calls will not be charged at all. When the VoipSwitch owner has to pay for such callback calls it may lead to financial loss and so has to be used with care


Use Charge calls only when both legs were connected carefully! It can cause financial loss in situations, when the src. leg is already connected and dest. leg is not answering the call.


Wav files

file paths to the audio (.wav) files which can be played during the callback scenario:

  • the first file is played while calling to the callback trigger number; it can be ringback or busy tone.

  • the second file is played while the customer (source leg) is waiting for the connection to the destination number (destination leg)

Wav files must be stored in a directory defined as storage. The file name cannot contain any spaces. The file name MUST also include the codec name at the end, separated from the rest of the file name by an underscore.

Example file name: example_file_g711a.wav 


Callback type

  • Dial src. and dest. leg number at the same time
    when the callback call has been triggered VoipSwitch calls back to the customer (source leg) and the destination number (destination leg) at the same time
  • Connect src. leg and dial dest. leg number
    when the callback call has been triggered VoipSwitch first calls back the customer (source leg) and only when the call is connected, dials the destination number (destination leg)