Bug#837754: mpath doesn't have sensible default

[Daniel Pocock]

Package: kamailio
Severity: important
Version: 4.4.2-3

If the mpath value is not set in kamailio.cfg, it defaults to
/usr/lib/kamailio/modules and the log contains errors like these:


DEBUG: <core> [sr_module.c:510]: load_module(): module file not found
</usr/lib/kamailio/modules/pv.so>
DEBUG: <core> [sr_module.c:533]: load_module(): module file not found
</usr/lib/kamailio/modules/pv/pv.so>
ERROR: <core> [sr_module.c:571]: load_module(): could not find module
<pv> in </usr/lib/kamailio/modules>



The value is set in the official kamailio.cfg sample by the install-cfg
target in Makefile

However, if a user is trying to use a kamailio.cfg from another source
then they will encounter the error and they have to manually set mpath

Could the default mpath value be set to the appropriate value at package
compile time?

One reason this fix is desirable is that the homer-api package also
provides a kamailio.cfg file.  If a default mpath was valid, the package
could provide a single cfg file for all Debian architectures.  Without a
valid default, the homer-api package needs to be rebuilt for each
architecture, with a sed command in debian/rules to add mpath to the
sample config.