Skip to content
Voxbi Cockpit APIs
API Guides

Twinnings

Twinning also rings an external number (mobile phone or Microsoft Teams) when a user's PBX extension is called, so they can be reached on another device.

Overview

Twinning is configured per user. A rule has an active status so you can pause it without deleting it.

What it does

The dial strategy sets how the external device is reached. Fixed-Mobile Convergence (FMC) extends PBX features like transfer and hold to the mobile device, and applies to mobile twinning that uses a GSM-capable strategy.

See also

  • Users - the parent entity for twinning configurations.
  • Queues - enable "ring twinnings" on a queue to reach twinned members on mobile.

Form fields

Fields available in the create and edit forms.

General

Enabled

Whether twinning is on. When off, incoming calls only ring the PBX extension.

Phone number

The external number to ring alongside the PBX extension.

Type

The destination type for twinning.

  • mobile Mobile Rings a cellular phone number.
  • teams Teams Rings a Microsoft Teams client.
Dial strategy

How the outbound leg to the external device is placed.

Shown when

Type is Mobile

  • gsm_only GSM only Traditional cellular call. Most reliable but uses mobile minutes.
  • voip_only VoIP only IP-based call to the mobile app. No mobile minutes but needs a data connection.
  • voip_and_gsm_fallback VoIP and GSM fallback Tries VoIP first. Falls back to GSM if the app does not answer in time.
Ring after

Seconds to wait before ringing the external device. Set to 0 for true simultaneous ring.

FMC

Enables Fixed-Mobile Convergence (FMC), allowing call transfer and hold to be performed directly from the mobile phone. Available only on a Voxbi SIM.

Backup phone number

Secondary number tried when FMC is on and the primary number is unreachable.

Shown when

FMC is on

Updated