To be honest, I rather stay with the upstream Kamailio from Xenial and accept this bug for now.

The burden of having to maintain a custom Kamailio build and package does not outweigh the complications caused by this issue, in our case.

I can understand that fixing Xenial bugs are not your priority... if there's no plan to fix this in Kamailio, we should just close this with "won't fix".

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