CallService

Description (v1.3)

INFO Apply intra-cluster routing and call an extension. Call parameters are also transfered to the remote SOP and can be read via InitService
INFO The destination extension [Extension].
INFO The primary SOP on which the extension is located [Sop1].
INFO The secondary SOP on which the extension is located [Sop2].
INFO The call parameter 1 [Parameter1].
INFO The call parameter 2 [Parameter2].
INFO The call parameter 3 [Parameter3].
INFO The call parameter 4 [Parameter4].

Release notes

Show release notes
Version 1.3 - General deployment
  • Improvement: Compatibility with the Communication Server module

Version 1.02 - General deployment
  • Bugfix: Output connectors does not work
  • Bugfix: Loop when primary sop is not available

Version 1.01 - General deployment
  • Improvement: CallService works in identical way if service is located on a remote SOP or a local SOP

Version 1.00 - General deployment
  • Feature: Initial release

Version 0.01 - Deprecated
  • Deprecated: Significant improvements have been done in a higher version

Version 0.00 - Deprecated
  • Deprecated: Significant improvements have been done in a higher version

Action parameters

This action enables to apply the intra-cluster routing to the current call taking into account the extension, the primary SOP and the secondary SOP provided in input.

Call parameters can also be sent to the remote SOP. Nevertheless only SIP is currently supported for the transport of such call parameters.

  • Extension: the extension where the call is to be sent
  • Sop1: the first SOP where to try to send the call
  • Sop2: the second SOP where to try to send the call
  • Parameter 1: the first call parameter to be sent to remote SOP
  • Parameter 2: the second call parameter to be sent to remote SOP
  • Parameter 3: the third call parameter to be sent to remote SOP
  • Parameter 4: the fourth call parameter to be sent to remote SOP

Example of use

It is possible to develop a service which enables to check personal voicemail from any phone of a cluster.

This service prompts the user for its language and its mailbox extension. Via the action GetExtensionInfo, the primary and secondary SOP of this one can be discovered. It is then possible to route the call to this SOP via the action CallService. The extension and language provided by the user can be sent to the remote SOP in order to prevent to prompt twice the request to get them. The action InitCall needs to be inserted at the beginning of the callflow in order to extract the call parameter provided in the CallService. Finaly the action VoicemailMenu is used to provide access to the right mailbox in the right language on the right SOP.

ALERT! Note: If the service is known as local, a Redirect to the service can also be done, this will prevent the creation of a new call and extra Local channels.
Copyright © Escaux SA