This answering machine can be connected to a Fritz!Box or other VOIP
router as IP phone.

The PhoneBlock-AB cloud answering machine is implemented as external
VOIP device that registers at the customers router. To find the router's
IP address PhoneBlock-AB provides a built-in DynDNS service. This can be
used, if the has no domain name registered and no otherwise configured
DynDNS service.

Extracted PhoneBlock API to separate module phoneblock-shared. Only
accept calls that have sufficient PhoneBlock votes. Added service
configuration file to add PhoneBlock as Linux systemd service.

Added version information to startup.

The answering machine must support different audio formats depending on
the remote receiver.

The Java default implementation for audio resampling is good enough.

Those options are necessary, when accessing a Fritz!Box from a cloud
instance (not in the local network).

This allows to detect, whether the caller is known in the local address
book of the router.

The pom properties of the main artifact get not included, when building
a jar with all dependencies.

When using host names for RTP connection information, no audio
connection is established - at least when communicating with Fritz!Box
VOIP routers.

Without this setting, no POST requests can be issued from the Flutter UI
to the PhoneBlock service, even if the UI is served from the same
origin.

Save call list per user to a separate database table.

Alternative to JNDI for running PhoneBlock locally.

Alternative to JNDI configuration for running PhoneBlock locally.

JSPs no longer require Maven resource filtering, which is not available,
when starting PhoneBlock locally.

The UI is served from the same origin.