I think the problem is in other part -- the build parameters must be adjusted to set
internally the proper path to modules. Explicitly setting the path in config proved to be
a bit more dangerous when having more than one installation, but also because there are
parts of code relying on those paths, especially for default config path -- if the build
system is not setting those defines properly, there can be other side effects in long
term.
If one runs:
```
kamailio -I
```
it should print the right path to modules and kamailio tries to load from there. If there
is a mismatch from what `kamailio -I` prints and where the modules were installed, then it
has to be fixed.
As a side note for the future, prefix the commit message with the component that is
affected, in this case being kamailio.cfg, so it should look like:
```
kamailio.cfg: short commit description here
```
I am closing this one and further discussions should be on the issue you opened (#1096).
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/1095#issuecomment-297666899