Hi
What are different ways to reload Kamailio configuration file without restart? I need to make configuration file changes on production server without bringing down kamailio service.
*Thanks & Regards,* Amit Patkar
Hello,
if you need to change the routing logic, then you have to restart. If you use UDP, it is not noticed at all by the clients and active calls are not affected at all.
Restart is very fast. Also, the content of the config should be only logic, the values (like IP addresses), should be inside the database -- for example lcr, dispatcher, ... can reload the records from database without a need to restart, but by issuing a MI/RPC command.
Changing values for parameters can be done for many of them using command line.
Cheers, Daniel
On 07/01/16 08:11, Amit Patkar wrote:
Thanks Daniel. Since there are WebRTC clients connected, restart should be avoided in my case
Is there any plan to add configuration file reload in future?
*Thanks & Regards,* Amit Patkar
On 1/8/2016 2:07 PM, Daniel-Constantin Mierla wrote:
Connections can be dropped from other reasons, not only restarts (like congested routers on the path), so if your client is not able to reconnect, then it will get in troubles anyhow.
You can also build a topology with an edge proxy (referred by many as sbc), which sits in between the client and the main sip server, with a very basic configuration that you don't need to change. This is actually something recommended, in the edge proxy you can filter bad traffic (scanning attacks, malformed sip packets) and behind it you can have many sip servers (for redundancy/high availability), routing traffic to them using dispatcher module (load balancer).
Edge proxy and main proxy can be even on the same system, but using different ports.
Cheers, Daniel
On 11/01/16 10:32, Amit Patkar wrote:
-
Amit Patkar -
Daniel-Constantin Mierla