Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
Hey Henning!
sorry, will wait more in the future. For IMS modules, the interest seemed to be low and the state kind of experimental, so I pulled the trigger on the last day before going 1 week in vacation, reasoning that at least it has no breaking changes.
I fully agree with you. But also this module breaks away and there is further work required to make it really good and worthy of replacing the older module and dropping ims_dialog. I would rather surface WIP, than come-up with a huge PR after a long time.
For context: we're working at Neat Path Networks on a slightly different approach, where the IPsec part is external to a Kamailio P-CSCF. Hence some modules need less functionality, or we're trying to upgrade some to rather use the routing script and better-maintained/generic modules, instead of IMS-specific modules and opaque functions. We still hope though to share efforts with the bigger Kamailio IMS community, hence we'd rather avoid keeping our modules on a fork.
P.S. the IMS modules have no tests that I'm aware of, so trying to merge into the ims_qos module was way harder. If anyone is using Kamailio IMS into production, let's bundle up and write some, so that we can merge&deploy with confidence.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.