Hi Guys,

Any updates regarding this Ticket #2790 ?
Recording DISA calls

It is a very useful function in PBX.

I was really hoping that it would be in the upcoming release of 2.7

Looks like it's pretty important to at least a few of you.

You can always engage the paid support department on such requests, if one of you has not already done so...

netphreak,

the support folks used to do what you requested.

The problem became that so many requests come in that if no filter is provided, the team ends up spending 30-60 minutes to work out what it will take to do x, y or z feature request. Well when 1 of 10 people are willing to pay what things really cost, that results in 5-10 hours of time spent just assessing costs for each request that they are engaged into doing.

That is why they now charge to "assess" the costs of doing a feature. And don't mi-understand what that means. When a developer "assesses" what it is going to take to do something, it means they are starting to do the work. There is no overhead in that.

If you are looking for ball park figures, that's a hard call to provide. A typical feature can take anywhere from a couple hours to dozens of hours depending on how complex it is.

Not to belabor this but here's another perspective if you don't like that one. I've got a leak in my hot tub. It's going to cost me $100 for the guy to come out and then tell me what is wrong and how much it might cost to fix (if he can figure it out in 30 minutes). Oh - and he didn't give me the hot tub for free to begin with, otherwise, maybe I should expect him to come out for free :-).

Given how important you indicate this feature is in your blog post, spending $150 to get something started given the cost you paid for the software (also developed by those same folks) is not exactly "stiff" when you take all that into consideration.

I hope this helps you understand the reasons and maybe a different perspective.

netphreak,

there are plenty of tickets that are 2+ years old. Features get worked on for various reasons that all translate to some developer is interested in doing it for one reason or another.

Sometimes its something they want, sometimes it is pure academic interest, sometimes it is money.

There are also tickets that don't get done because they get "lossed" in the bug tracker. Adding MoH to conferences is a perfect example. I just stumbled across the ticket in the 11th hour before closing the 2.7 release, complete with a patch that applied perfectly to test it out. (granted I ended up having to make some minor fixes to what the contributor had applied but...).

The other consideration of putting any feature into the product, and is considered in the "cost" of doing it, is long term support of the feature. (Cost being effort, $, etc.). Because often there is more backend work to maintain a feature then implementing it initially. (That's one of a couple reasons why modules like Custom Contexts has never been put in as a Core Team supported module - which is about to seriously break in 2.8 for example.)

So I can't honestly tell you what Recording in DISA is going to entail. My gut expectation is it probably is not that much work (Add a GUI field, add the required dialplan to trigger the recording). On the other hand, maybe there is more to it given how DISA let's you re-initiate new calls, etc. - and all of that needs to be examined as well as tested with various scenarios once implemented...