I think a more global command would be nice to have.

As far as I am concerned dialog plugin implemented in DMQ module is perfectible and does not currently cover all the cases I am facing (and maybe will never be able to do so). So the ability to force a dialog state for handling some particular cases could be a solution.

I explained in the mailing-list that case "state 4 to state 5" seems to be the most important in my opinion because for the others we generally have shorter lifetime timeouts (for non-ACKed dialogs for instance). So they should not remain in memory for a long period of time, as opposed to active dialogs.

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