Hi List
I wanted to take one of our cores down gracefully by not destroy running dialogues to be able to implement a config change on Kamailio 5.5
For this I did:
kamctl dispatcher.remove ID SIP-URI, for every IC
This worked fine, Kamailio is instructed to reply 503 on out of dialogue traffic from unknown endpoints causing the endpoints to re-route traffic to the other core, eventually making it possible to stop and restart Kamailio without harm.
dialog count was steadily decreasing, until after about 10 minutes after removing the dispatcher URI's it started to increase again.
kamctl dispatcher.list shows me, all dispatcher URI I removed are back!
There is no ds_reload() being executed by calls.
In the module description, I find no hint, that the dispatcher config is being reloaded from file in some interval or so.
What could be the cause of my removed dispatcher suddenly being back?
Hello,
On 10.11.23 15:25, Benoît Panizzon via sr-users wrote:
Hi List
I wanted to take one of our cores down gracefully by not destroy running dialogues to be able to implement a config change on Kamailio 5.5
For this I did:
kamctl dispatcher.remove ID SIP-URI, for every IC
This worked fine, Kamailio is instructed to reply 503 on out of dialogue traffic from unknown endpoints causing the endpoints to re-route traffic to the other core, eventually making it possible to stop and restart Kamailio without harm.
dialog count was steadily decreasing, until after about 10 minutes after removing the dispatcher URI's it started to increase again.
kamctl dispatcher.list shows me, all dispatcher URI I removed are back!
There is no ds_reload() being executed by calls.
In the module description, I find no hint, that the dispatcher config is being reloaded from file in some interval or so.
What could be the cause of my removed dispatcher suddenly being back?
there is no automatic reload, be sure you do not have some timer routine (inside kamailio.cfg or cron.d) that does it, or an external application (e.g., management application).
To double-check, once you run the remove command, do a dump of in-memory records to be sure it was removed, maybe the command fails and there should be error messages about that.
Cheers, Daniel
Hi Daniel
there is no automatic reload, be sure you do not have some timer routine (inside kamailio.cfg or cron.d) that does it, or an external application (e.g., management application).
Thank you, that was the cause. We have a cronjob which downloads rules from a spit call blocklist supplier, puts them in various textdb htables and mtrees and reloads them.
That script also preformed dispatcher.reload.
Mit freundlichen Grüssen
-Benoît Panizzon-
-
Benoît Panizzon -
Daniel-Constantin Mierla