@charlesrchance - the core2 is generated when sending a KDMQ request, the core1 is generated during cleanup at shut down.

The first thing to sort out with core2 is why sending KDMQ it is done in main process -- either it is a kamailio with fork=no or some procedure done at startup. Sending happens when dialog hash table is still null.

I pushed a safety patch, but overall, dealing with sip traffic should be avoided in main process -- not sure if it is related to dmq in general or the dmq extension for dialog.

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