Bridge

Bridge holds a call once it is answered: who is in it, transfers, conferences, coaching and what is recorded. A server that runs Queue needs Bridge beside it, or nothing puts a caller and an agent together.

Given automatically to a server that carries a trunk. When a trunk is assigned to a server (sudo xema trunk assign <trunk> --node <server>), that server is given every service a phone system's server runs, this one among them. It is given once and kept: unassigning the server's last trunk does not take it away again. xema node role remove does.

Putting it on a server

sudo xema node role add bridge
sudo xema node apply

node role add records that this server should run it, and node apply starts it. If xema component list shows it is not installed here, install it between the two:

sudo xema component install bridge

A server can also be given it as it joins: sudo xema join ... --roles bridge,....

Taking it off

sudo xema node role remove bridge
sudo xema node apply

Checking it

xema node roles          # what this server should run, beside what it runs
xema status              # every service on this server, running or not
xema logs bridge

Restarting it

sudo xema restart bridge                       # on this server
sudo xema node restart bridge --node <server>  # on another one

Restarting drops the calls it is carrying.