ARI v0.1.2 ARI.Transfer View Source

A Stasis application to handle transferring calls to phone numbers outside of our system.

Example

  Channels.originate(UUID.uuid4(), %{
    endpoint: "PJSIP/+15555550101@ivr",
    app: "transfer",
    appArgs: state.channel,
    callerId: "Citybase, Inc",
    originator: state.channel,
    context: "ivr"
  })

This would be initiated in an event handler for your current call. The state.channel should be the ID of the incoming call.

This will create a Bridge and dial +15555550101 connecting the original call with the dialed number. This example assumes you have registered the ARI.Transfer Stasis application with the name transfer like this.

  {ARI.Stasis, [sup, %{name: "transfer", module: ARI.Transfer}, ws_host, un, pw]}

Link to this section Summary

Types

t()

Functions

child_spec(init_arg)

Returns a specification to start this module under a supervisor.

init(state)

Invoked when the server is started. start_link/3 or start/3 will block until it returns.

start_link(list)

state(channel, caller, list, start_event, app_state)

Called when an incoming call is received. Arguments are Channel ID, Caller ID, Args, StasisStart Event and App Config

Link to this section Types

t()

t() :: %ARI.Transfer{
  caller: term(),
  channel: term(),
  incoming_channel: term(),
  start_event: term()
}

Link to this section Functions

child_spec(init_arg)

Returns a specification to start this module under a supervisor.

See Supervisor.

init(state)

Invoked when the server is started. start_link/3 or start/3 will block until it returns.

init_arg is the argument term (second argument) passed to start_link/3.

Returning {:ok, state} will cause start_link/3 to return {:ok, pid} and the process to enter its loop.

Returning {:ok, state, timeout} is similar to {:ok, state}, except that it also sets a timeout. See the "Timeouts" section in the module documentation for more information.

Returning {:ok, state, :hibernate} is similar to {:ok, state} except the process is hibernated before entering the loop. See c:handle_call/3 for more information on hibernation.

Returning {:ok, state, {:continue, continue}} is similar to {:ok, state} except that immediately after entering the loop the c:handle_continue/2 callback will be invoked with the value continue as first argument.

Returning :ignore will cause start_link/3 to return :ignore and the process will exit normally without entering the loop or calling c:terminate/2. If used when part of a supervision tree the parent supervisor will not fail to start nor immediately try to restart the GenServer. The remainder of the supervision tree will be started and so the GenServer should not be required by other processes. It can be started later with Supervisor.restart_child/2 as the child specification is saved in the parent supervisor. The main use cases for this are:

The GenServer is disabled by configuration but might be enabled later.
An error occurred and it will be handled by a different mechanism than the Supervisor. Likely this approach involves calling Supervisor.restart_child/2 after a delay to attempt a restart.

Returning {:stop, reason} will cause start_link/3 to return {:error, reason} and the process to exit with reason reason without entering the loop or calling c:terminate/2.

Callback implementation for GenServer.init/1.

start_link(list)

state(channel, caller, list, start_event, app_state)

state(String.t(), String.t(), list(), map(), map()) ::
  ARI.Stasis.channel_state()

Called when an incoming call is received. Arguments are Channel ID, Caller ID, Args, StasisStart Event and App Config

Callback implementation for ARI.Stasis.state/5.