[OpenSER-Users] "noisy_ctimer" parameter in TM module

Hi, I want to get some feedback from the users regarding one of the TM parameters: "noisy_ctimer" . This parameter, is disabled, would try to let a call to ring for ever (openser will never give internal timeout). But, the parameter is automatically turned on (disregarding the script setting) in certain conditions: - parallel forking is done - a failure route is set - a failure callback is set by other module (like acc, cpl, dialog, etc) - a fr_invite timeout was configured via AVP - some reply was already received - no other module explicitly asked for this (like siptrace, acc,osp) Following some discussion on the tracker, there is large support for removing this parameter as: 1) it is difficult to anticipate the final behaviour due complicated logic 2) due all dependencies, in 99% of the case, the param will be automatically turned on 3)it breaks the RFC3261, which make mandatory to have a final reply form a stateful proxy My question is: Is anybody having a good point in not removing this parameter (and having noisy_ctimer behaviour all the time)? I'm pushing this question only on users list, as between the developers, there is an consent in removing it ;) Regards, Bogdan