Options
All
  • Public
  • Public/Protected
  • All
Menu

Verto Orchestrator can be seen as the core component of our Verto implemented Its role is to read all incoming message and act appropriately:

  • broadcast important messages as ZiwoEvent (incoming call, call set on hold, call answered, ...)
  • run appropriate commands if required by verto protocol (bind stream on verto.mediaRequest, clear call if verto.callDestroyed, ...)

Hierarchy

  • VertoOrchestrator

Index

Constructors

constructor

Properties

Private Readonly debug

debug: boolean

Private Readonly verto

verto: Verto

Methods

Private ensureCallIsExisting

  • ensureCallIsExisting(call: Call | undefined): boolean
  • ensureCallIsExisting makes sure the call is not undefined. If it is undefined, throw a meaningful error message

    Parameters

    • call: Call | undefined

    Returns boolean

Private handleMessage

Private handleNotification

Private onAnswer

Private onAttach

Private onClientReady

Private onHold

  • onHold(call: Call): void

onInput

  • onInput(message: any, call: Call | undefined): void
  • We can identify 2 types of inputs:

    • message (or request): contains a method and usually requires further actions
    • notication: does not contain a method and does not require further actions. Provide call's update (hold, unhold, ...)

    Parameters

    • message: any
    • call: Call | undefined

    Returns void

Private onInvite

Private onMedia

Private onUnhold

  • onUnhold(call: Call): void

Private pickup

Private pushState

Legend

  • Constructor
  • Property
  • Method
  • Private property
  • Private method
  • Static property
  • Static method
  • Property
  • Protected method

Generated using TypeDoc