For the moment, it's impossible to apply changes to Kamailio config file (not using KEMI, for sure) without restarting Kamailio.
Here is a small trick that you can use to enable/disable some parts of a script in a realtime, that is very useful for debugging. Not the whole script, but something.
kamailio.cfg
#!KAMAILIO
# REALTIME changable parameters
...
# Enable or disable test numbers function. Done as realtime not to use group (SQL) functions every call
realtime.test_destination=0
...
route[TEST_DESTINATION_DETECT] {
if ($(sel(cfg_get.realtime.test_destination){s.int}) != 1) {
return;
}
if (is_user_in("To", "test-dst-to")) {
xlog("$var(debug_level)", "[TEST_DESTINATION_DETECT] $rU as a test destination TO number\n");
setflag(FLT_TESTNUMBER);
return;
}
if (is_user_in("From", "test-dst-from")) {
xlog("$var(debug_level)", "[TEST_DESTINATION_DETECT] $fU as a test destination FROM number\n");
setflag(FLT_TESTNUMBER);
}
}
In this example the whole route execution is based on a value of realtime.test_destination parameter. By default it's 0 (means false), but can be easily changed with
# kamcmd cfg.set realtime test_destination 1
And no need to restart script. Small, but useful trick for me. Only thing to keep in mind, that unlike KEMI this trick is not taking into accout transaction states, etc. Just change and that's it.
P.S: Got some feedback, that $(set(cfg_get...)) might lead to a crashes on a high load. Htable might be a good alternative for this as well.
