<br><div class="gmail_quote">Hello!<br><br>In light of my recent lay-off from Digium, I find myself looking for a job and any consulting<br>work I can get until I find one. If anyone has any ideas or propositions, call me at 307-899-5535,<br>
or email me at murf at parsetree dot com...<br><br>One area where I might be able to help: <br><br>The state of CDR processing in Asterisk is somewhat in limbo. On the one hand, <br>somewhere near 16 CDR bugs have been recently unassigned in the issue tracker, <br>
and on the other hand, my work to provide a next-generation CDR generator<br>has only a rough start; the CEL work is still needing another review, and someone <br>to take care of the issues found in that review; perhaps someone will step into that role.<br>
<br>Since there's bills to pay, kids to feed, etc., I can't justify pushing any of these issues<br>for free. However, there exists a window of opportunity for the community!<br><br>Between now, and the time I get a "real job", I might have time to work on completing<br>
the CEL->CDR converter I've proposed.<br><br>The cost of the project is a function of the deliverables, milestones, and etc. Depending<br>on what is wanted, it seems to me a 2-8 week project (to be realistic). The RFCs <br>
document I published earlier would end up as the documentation, of course, and one<br>of the deliverables.<br><br>The catch: Before I start, one or a set of the community must guarantee that they'll support this<br>work. . As to what you get in return, I'm pretty flexible; I can develop in a public branch, and<br>
supply a patch, or if my client(s) would prefer, I could keep the results private for some amount<br>of time, and then release them. I'd assume that it'd be nice to not have to patch this in forever.<br><br>Again, what you would get: CDRs generated that are dependable, easy to <br>
maintain (for me or anyone else), and easier to manipulate via the dialplan<br>via a much simpler interface (IMHO). No spending weeks with the current<br>interface trying to find the magic combination of commands that will give you<br>
what you need.<br><br>This is perhaps the best deal you could ever hope for with CDR's. I'd wager I<br>
could do the job quicker and better than anyone else. I've been playing with<br>the ideas for over 2 years, and I have over 30 years of development experience.<br>I know pretty much what is wanted, and how to get there. If there's not <br>
enough interest, I'm sure someone (perhaps Digium) will either fix the current <br>interface, or finish where I started, or submit something new; it's just a <br>matter of time. Or you could allow me to speed things up a bit!<br>
<br>I will not fix the bugs in the current CDR implementation. It's not worth it to you or me.<br>You might find some sharp unsuspecting kid willing to try, but even if he <br>
succeeded, you'd still be left with problem code, hard to fix and maintain, and it<br>will break horribly whenever somebody made even small changes to the PBX <br>engine, masquerade code, etc. (Well, I *say* I won't do it, but for the right price,<br>
I can do whatever is wanted!)<br><br>And I suspect that he/she would not succeed. I have a patch supplied that solves<br>
maybe 1/2 of the open bugs, but breaks CDRs for assisted transfers even worse<br>than how it is broken now, and estimated that it would take 2 more weeks to *try*<br>to repair that damage and make them work right, or at least prove that the approach<br>
was wrong. No, that is *not* the right way to handle this situation. But, of course,<br>individuals, the community, and Digium are always free to do as they wish!<br><br>Respond in private if you are interested in this or any other effort. Again, my phone is<br>
307-899-5535, and my email is murf at parsetree dot com.<font color="#888888"><br> (ParseTree is my own little consulting corp).<br></font></div><br>-- <br>Steve Murphy<br>ParseTree Corp<br><br>