Alex Balashov writes:
Stateless replies have that name for a reason; they
lack state. They
don't trigger any TM callbacks that the dialog module can latch onto.
So, figuring out how to remove a dialog to which a stateless final
failure reply has been sent is actually quite difficult, and requires
significant architectural changes.
one can always use sems to limit number of simultaneous calls (see
cc_pcalls sbc module).
lets face it: if you want to be dialog aware, it is better to do it with
right tool (= sbc) than to try to twist sip proxy to do something that
it is not by definition good for.
once you have bitten the bullet, you can easily handle rtp proxying,
topology hiding, reliable accounting, anonymity, etc. with one single
tool.
-- juha