Starting this issue to collect suggestions about what should be adjusted in the default config or options (global or module parameters) in preparation for Kamailio 5.4.0. The goal is not to recreate a completely new config, the current one being a good starting point for new deployments, but to tune its parameters with what people consider useful to have based on experiences encountered lately.

Compared with 5.3, there are already:

• replaced XMLRPC with JSONRPC
• option to use RTPEngine instead of RTPProxy

Other proposals I would do:

• enable path support by default in registrar/usrloc modules - it is disabled by default, a modparam needs to be set, but if set and no PATH header, then there is no effect. I met couple of cases when a Kamailio proxy was added in front of other Kamailio (usually coming as part of a PBX) and Path is not enabled there.
• set timer_procs for usrloc - as deployments grow with the population of registered endpoints, core time can be affected by scanning expired registrations
• load textopsx module and try to provide an example of using msg_apply_changes() probably within some ifdef - aiming to help new comers spot that changes as are immediately visible

Listing now, but to have in mind for other future releases, because the code is young in 5.4:

• keepalive to be done with usrloc module to get round trip timer, etc
  *dlgs module loaded to see the basic stats about active calls - useful to help deciding when to do a restart or a maintenance shut down, even if it may not be 100% accurate if done after another restart (because there is no persistence, at least now), currently the stats being more or less in the fashion of active transaction stats

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.