Sipper

Sipper captures its server's SIP traffic, so a call that went wrong can be looked at afterwards.

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 sipper
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 sipper

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

Taking it off

sudo xema node role remove sipper
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 sipper

Restarting it

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

Restarting drops the calls it is carrying.

Capturing

xema node interfaces                                   # what can be captured on
sudo xema node capture start --record Failed           # start, on this server
sudo xema node capture start --node <server> --device <interface>
xema node capture                                      # whether it is capturing, and what
sudo xema node capture stop
xema node captures --search <number>                   # the captured calls, from every server

Name the interface with --device on a server reached over wifi.