[sr-dev] rfc: event route when kamailio starts

Daniel-Constantin Mierla miconda at gmail.com
Wed Oct 7 20:11:43 CEST 2015


Hello,

based on a recent discussion with Alex Balashov (at Kazoocon this week),
I pushed a patch that enables the execution of
event_route[core:worker-one-init] when kamailio is started. It would be
more like an alternative for event_route[htable:mod-init], for the cases
when htable is not used, but also should ensure that all the modules are
initialized. Moreover, because most of the modules close connection in
mod init, I though of doing it when child one (udp receiver)
initialization for all modules is finished, which means that all is
ready for runtime, still this is before receiving any packet.

On the other hand, forking is done by main process, so other children
can start listening for sip.

More or less what I want to ask here is whether the forking of the other
children should wait until the event_route[core:worker-one-init] is
finished (e.g., what is done in this event route is important before any
sip packet is routed) or just leave it like it is.

Worth to say that some modules do special processing in child init of
worker one, like usrloc module loads the records from database to
memory, which means that overall start of kamailio could be slower.
Also, if there are time consuming actions in the
event_route[core:worker-one-init], getting to the stage of routing sip
packets will take longer.

What would you find important, fork the other processes so routing sip
will happen as soon as possible, or block until execution
ofevent_route[core:worker-one-init] is finished.

I guess that making it cusomizable in some way would be a solution, but
knowing what use cases would be important may help in reducing the
complexity to get it enabled.

Cheers,
Daniel

-- 
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.com




More information about the sr-dev mailing list