AutoRecall

Description (v2.0.0)

INFO This action redials the called party number when he/she becomes available.
INFO If the called party [Called party] is not available.
INFO the system checks every [Timeout] seconds if the called party is still not available. If it is not the case, the calling party is connected to the called party (Callback).
INFO The availability check is terminated after [Retries] tries.
INFO Callback type [Callback type].

Release notes

Show release notes
Version 2.0.0 - General deployment
  • Improvement: Compatibility with the Communication Server module
  • Dependency:
    • SOP API module

Version 1.90 - General deployment
  • Bugfix: Callback was not working on standalone SOP (M5126)
  • Dependency:
    • SOP API module

Version 1.80 - Deprecated
  • Bugfix: Extension was staying in busy state forever (M5094)
  • Bugfix: Callback was not working on standalone SOP (M5126)
  • Deprecated: Action does not install properly

Version 1.70 - Early deployment
  • Avoid the action to write unnecessary logs
  • Avoid characters which can cause problems

Version 1.60 - General deployment
  • Do not allow the calling party to autorecall himself

Version 1.50 - General deployment
  • MySQL initial request optimization for callback on phones which has never made any call
  • Improve logging
  • Improve action parameter label
  • Virtual phone support
  • Fix a bug (when the second phone is not defined)

Version 1.40 - General deployment
  • MySQL initial request optimization for callback on phones which has never made any call
  • Improve logging
  • Improve action parameter label

Version 1.30 - General deployment
  • Adds the following values: 240, 360, 480, 600, 720 in the 'retries' parameter dropdown parameter
  • Default value of 'retries' parameter dropdown parameter is 60 seconds
  • Multiple script callback bug solved
  • Removes the name in the callerid when callback is triggered

Version 1.20 - General deployment
  • add ccnr support
  • one version of the API module must exist.

Version 1.00 - General deployment

Version 0.4 - Deprecated
  • Implement primary and secondary devices for ccnr

Version 0.3 - Deprecated
  • Play Music on hold during inter sop callback

Version 0.2 - Deprecated
  • add the possibility to not play the 'thank-you' on success of callback initiation
  • add called secondary device supervision in case of callback
  • check also the remotechannel
  • If the call is intersop, checks the remote caller primary and secondary device. Does work only with consolidated management.

Version 0.1 - Deprecated
  • add the possibility to not play the 'thank-you' on success of callback initiation
  • add called secondary device supervision in case of callback
  • check also the remotechannel
  • If the call is intersop, checks the remote caller primary and secondary device. Does work only with consolidated management.

Version 0.0 - Deprecated
  • add the possibility to not play the 'thank-you' on success of callback initiation
  • add called secondary device supervision in case of callback
  • check also the remotechannel
  • If the call is intersop, checks the remote caller primary and secondary device. Does work only with consolidated management.

Action parameters

This action tries to recall automatically the called party when it has become available. This action can be triggered either when the called party is busy (CCBS) or when the called party does not reply (CCNR). In the CCBS case, the condition to decide the called party is available is when the primary and secondary devices of the called party are free. In the CCNR case, the condition to decide the called party is available is when the called party performs a call with any of his devices or the called party answers a call with any of his devices.

ALERT! Please note that this action only works when the called party is connected to an Escaux SOP.

  • Called party: this is the extension of the called party
  • Timeout: this is the period between subsequent checks. At every Timeout, the system performs a new check on the availability of the called extension. If the called party is available, the calling party is connected to the called party (Callback): First the calling party's phone rings and when picked up, the called party is called.
  • Retries: The availability check is terminated after a number of tries
  • Callback type: the possible values are:
    • on busy: the callback action is triggered when the called party is busy (CCBS)
    • on no reply: the callback action is triggered when the called party does not answer (CCNR)
  • Prompt:
    • 'Play confirmation prompt on success': Play the confirmation prompt 'thank-you' in case the callback is successfully activated.
    • 'Do not play confirmation prompt on success': Do not play the confirmation prompt. Implement the auditive success confirmation through subsequent call flow actions.
  • Check caller devices before callback:
    • Delay callback until primary and secondary caller devices are not busy.
    • Do not delay callback: This option can be activated for example, if the call waiting is activated in the user call flows.
  • If the 'loop' output is activated, when the calling request an autorecall to the called, the call ends in loop without activating the callback

Example of use

This action is typically used when an internal extension is busy (does not answer). In the case of an internal call , an IVR action can ask if the caller desire a callback on busy (no reply). If the caller wants a callback, the action AutoRecall is called with the proper Callback type.
Copyright © Escaux SA