After 15 years of development, it is time for Kamailio v5.0.

• define and implement an export interface from modules to embedded interpreters to automatically add new functions to embedded interpreters, in a similar fashion as for adding functions to configuration file

• writing the routing logic only in a scripting language supported via embedded interpreters
• eventually setting core parameters, loading modules and setting modules' parameters are still done using the kamailio configuration file but all routing blocks should be possible to be written in an embedded language
• routing logic in an embedded language should allow reloading at runtime without kamailio restart

It was discussed in the past:

• source code files should be relocated to have a better structure for include headers, core files, modules and internal libraries as well as utilities

Revising the build system based on Makefiles.

Alternatives to analyze:

• configure
• cmake

Reviving the exiting unit testing or selecting another framework.

Defining a minimum set of automatic tests that needs to be provided by each module:

• a minimal config for loading the module, to be sure it doesn't have missing linking symbols
• can be done with a config as simple as:

loadmodule "foo.so"

request_route {
  ;
}

• or can require setting some module parameters or even loading other modules