> So... the two areas where code changes in Asterisk affect these systems are<br>
> API changes and CLI/dialplan syntax changes. An example of an API change<br>
> would be the ast_config_load function which, I am told, now requires that an<br>
> additional parameter be passed.<br>
<br>>> What was this change? When? What was the rationale for doing it?<br><br>What: The change was to add an additional parameter presumably with additional functionality. <br>When: Asterisk 1.6-beta<br>Why: I've assumed that the improvement was for the best of reasons. That doesn't change what I've suggested.<br>
<br>>> Arguing that something is bad because "I was told so" makes it pretty difficult for anybody to give you sensible answers.<br><br>You're certainly proving that. I didn't say it was bad. I said it was different. I was told it was different by Jared Smith. I assumed he knew what he was talking about since he offered a patch to un-break Cepstral.<br>
<br>>>
What prevents you from fixing it? Or paying someone to fix it?<br>
<br>Knowing how prevents me from fixing it. Not sure why it would be my responsibility to pay someone to fix something that someone else broke. I'm not making a nickel off of this stuff. Digium (and others like you) are.<br>
<br>>> where can I find the latest versions of:
phpagi (homepage lists latest version as released on 2005)<br>
<br>
Any current version of FreePBX or PBX in a Flash will have the latest supported version of phpagi.<br><br>>>
Generally if some software is left unchanged for two years, with not even bug fixes, I start suspecting no one uses it.<br><br>That kinda says it all and explains the problem better than I ever could have. <br><br><br>