[asterisk-users] Upgrade to Asterisk 1.4 - it's one year's old!

Tilghman Lesher tilghman at mail.jeffandtilghman.com
Sun Dec 16 22:40:06 CST 2007


On Saturday 15 December 2007 15:48:01 Philipp Kempgen wrote:
> Tilghman Lesher wrote:
> > If anything broke from the transition from 1.2 to 1.4, it is because you
> > were using something that was deprecated in 1.2.
>
> After thinking about it for a while this is not true.
> Well, it's true for the dialplan.
> Changing CALLERIDNUM to CALLERID(num) is easy.
>
> But i guess people use a lot of custom applications built
> around Asterisk 1.2. If any of the interfaces (AGI, AMI,
> CDRs, queue log, ...) change that might break the app.
> Fixing these apps might not be trivial and probably requires
> a lot of fine-tuning.

While that's true, the incompatible changes to AMI, AGI, and other
non-C interfaces should all be documented in UPGRADE.txt, which
users have been asked to read.

Internal C APIs are quite a different matter, of course.  Sometimes the
interface simply must change, even in minor upgrades, in order to fix
bugs.  That is unavoidable.  The best way about this is that if you've written
an app in C, you should genericize it to be useful to others and contribute it
back upstream.  Once it's in Asterisk, you no longer need to worry about
keeping the interfaces in sync -- the developers will do that for you, as an
integral part of the changeset.

-- 
Tilghman



More information about the asterisk-users mailing list