ARI v0.1.2 ARI.HTTP.Endpoints View Source
HTTP Interface for CRUD operations on Endpoint objects
REST Reference: https://wiki.asterisk.org/wiki/display/AST/Asterisk+16+Endpoints+REST+API
Endpoint Object: https://wiki.asterisk.org/wiki/display/AST/Asterisk+16+REST+Data+Models#Asterisk16RESTDataModels-Endpoint
Link to this section Summary
Functions
Returns a specification to start this module under a supervisor.
Invoked when the server is started. start_link/3 or start/3 will
block until it returns.
Link to this section Functions
Returns a specification to start this module under a supervisor.
See Supervisor.
get(tech, id)
View Sourceget(String.t(), String.t()) :: ARI.HTTPClient.Response.t()
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
GenServeris 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 callingSupervisor.restart_child/2after 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.
list_by_tech(tech)
View Sourcelist_by_tech(String.t()) :: ARI.HTTPClient.Response.t()
request(method, path, from, state, body \\ nil)
View Sourcerequest( String.t(), String.t(), GenServer.from(), ARI.HTTPClient.State.t(), map() | String.t() | nil ) :: ARI.HTTPClient.State.t()
send_message(to, from, body \\ "", variables \\ %{variables: %{}})
View Sourcesend_message(String.t(), String.t(), String.t(), %{variables: %{}}) :: ARI.HTTPClient.Response.t()
send_message_to_endpoint(tech, id, from, body \\ "", variables \\ %{variables: %{}})
View Sourcesend_message_to_endpoint(String.t(), String.t(), String.t(), String.t(), %{ variables: %{} }) :: ARI.HTTPClient.Response.t()