Skip to main content

Call Flows

Call flows define the way that the system handles the calls.

Normally, you can choose between the following main call flows when creating a meeting room:

  • The open call flow enables callers to enter a conference room with an access code associated with the meeting room. Alternatively, the open call flow also enables creating a meeting on the fly by entering a random access code.

  • The secured call flow only accepts access codes associated with the meeting room.

  • The direct_host call flow puts user directly into a conference with no access code prompt. Everyone becomes a host upon entering the meeting.

  • The direct_participant call flow puts user directly into a conference with no access code prompt. Everyone becomes a participant upon entering the meeting.

note

There can be variations of the call flows, but the main call flows used by CarrierX are those enumerated above.

The system automatically associates a call flow with the partner account at the creation of a Conference endpoint. The properties values of the Call Flow object serve as default settings. These settings can be overridden at various levels:

  • You can choose the call flow for your conference at the account, DID group, and DID levels.
  • You can additionally adjust the properties of the selected call flow at the account, DID group, DID, and meeting room levels.

Refer to the Conference v2 Call Flow Properties section for more information on this.

The typical call flow routing looks like this:

Call Flow Routing

  1. First, the system will check if the call flow is set at the phone number level.

  2. If it is not the case, the next step for the system is to check if the call flow is set at the DID group level.

  3. If it is also not true, finally, the system will look for the call flow settings at the account level.

The account associated with the conference should have a call flow set. If it is not so and the system fails to find the call flow settings at the DID or DID group level, the call will be dropped and the Meeting object will not be created.