Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
Thanks for the tip to delete the failing module directory when building.
I found the DMQ log lines appear to start with commit 80beb29. This hinted me to the fact that perhaps insert_dlg_timer was being called twice, and the problem might be due to my config self-referencing the local server in dmq.notification_address. For example:
modparam("dmq", "server_address", "sip:LOCAL_ADDRESS")
modparam("dmq", "notification_address", "sip:LOCAL_ADDRESS")
modparam("dmq", "notification_address", "sip:REMOTE_ADDRESS_1")
modparam("dmq", "notification_address", "sip:REMOTE_ADDRESS_2")
I did this as my config file is dynamically generated based on shared metadata and it was easier to script. Just a note that the output of kamcmd dmq.list_nodes is the same with or without the self-referenced notification_address, so I assumed the self-reference was OK/ignored. My bad!
I've removed the self-reference in my config and the errors have disappeared. I'd put the DMQ errors down to user error.
The DB persistence problem remains with the above fix to my config, so I'll continue exploring and update here.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.