Перейти к основному содержимому

Branch survival nodes

A branch survival node is a small MonoPbx node installed at a branch office, next to the office's phones. While the office's internet or WAN link to your main PBX works, calls go through the main PBX as usual. When the link is lost, the node keeps the office working on its own:

  • Internal calls between the phones registered at the office keep working.
  • Emergency calls go out through the office's local gateway to the public telephone network, with the caller ID and location set for the emergency number.
  • Other calls are refused until the link returns. A call to an extension of another site plays an announcement.

When the link returns, the node sends the main PBX what happened in the meantime (call records, voicemail).

To send the office's calls to people's mobiles while its link is down, see Internet-down survival.

примечание

The node software that runs at the office is not part of this release yet. You can already register your branch nodes, their site and their scope on this page, and connect webhooks to the branch events below; the node uses them as soon as it is available.

Open People and devices, Sites, Branch survival (/admin/branch-nodes). You need settings:read to see the page and settings:write to change it.

Add a node​

Choose New node and fill in:

  • Name: letters, digits, dots, underscores or dashes. The node uses this name to fetch its configuration, so it cannot be changed later.
  • Site: a label for the office.
  • Local gateway: the office's own gateway to the telephone network for emergency calls, as a sip: address, for example sip:gw@192.0.2.5. Required when your company has emergency numbers.
  • Extension ranges and Departments: the extensions the office serves, for example 200-299. Leave both empty to serve the whole company. Extensions of other sites are kept by number only (no names leave the main PBX).

Watch the nodes​

The table shows for each node:

  • Link: Up, Up, replaying (the link is back and the node is still sending what it recorded), or Down.
  • Snapshot: the version of the configuration the node last fetched. It changes every time the node fetches it.
  • Last sync and Waiting to replay: when the node last reported in, and how many records it still has to send.

Choose Refresh to read the latest state.

Notifications​

A node going down or coming back raises the events branch.link_down and branch.link_up, and a finished replay raises branch.resynced. Subscribe a webhook to them (topic branch) to be told at once, for example in your chat tool. The events carry the node's id, name and site only.

An assistant connected through the PBX's AI tools can also list the nodes and their state (read-only).

For the node​

The node fetches its configuration with POST /api/v1/branch-nodes/{id}/snapshot and reports its link with POST /api/v1/branch-nodes/{id}/link-report, using an API key of your company that has settings:write. The configuration holds no passwords.