Not only that, but the fix is not trivial. Contrary to how it may appear to a non-developer, this problem cannot be solved by just making a little patch.
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.
-- This message was painstakingly thumbed out on my mobile, so apologies for brevity, errors, and general sloppiness.
Alex Balashov - Principal Evariste Systems LLC 260 Peachtree Street NW Suite 2200 Atlanta, GA 30303 Tel: +1-678-954-0670 Fax: +1-404-961-1892 Web: http://www.evaristesys.com/
On Oct 10, 2011, at 1:00 PM, Jim Lucas lists@cmsws.com wrote:
On 10/10/2011 9:20 AM, Iñaki Baz Castillo wrote:
2011/10/10 Jim Lucas lists@cmsws.com:
On 10/8/2011 6:03 PM, Timo Reimann wrote:
As explained by myself in Flyspray issue #146[1], a fix to this problem is quite feasible. Overall, I believe that dialog module usage should be more robust and work out of the box; that is, it shouldn't matter where you place dlg_manage(), things should just work and handle the tricky cases intelligently.
I'm sure the developers would welcome you to submit a patch.
Humm, Time *is* the developer here ;)
My apologies to Timo.
The way he said it, I read that as he was suggesting that someone else should develop it.
-- Jim Lucas
http://www.cmsws.com/ http://www.cmsws.com/examples/ http://www.bendsource.com/
C - (541) 408-5189 O - (541) 323-9113 H - (541) 323-4219
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users