Requires a version of ASterisk higher than supported by PIAF.
This is a situation that is only going to get worse.... As we know piaf is based on ASterisk 1.4.21.2. The Mainline 1.4 is now at 1.4.26.2 - That's five relatively major releases... While 1.4.21.2 is stable, I would be surprise if all or most of the subsequent revisions aren't.
Equally with the 1.6 stuff (where PIAF pretty much is a "here it is" there are several versions between 1.6.1.1 (PIAF) and current 1.6.1.6 (Asterisk)
When are we likely to see PIAF resynch with something more current (and yet stable).
I suppose a few comments are in order
Yes our Gold standard is Frozen at 1.4.21.2. This is the last version that worked with Zaptel. I also think it is the last truly stable version of asterisk 1.4 tree. It comes down to why monkey with what works?
While this may seem like a philisophical question I believe it indicates a good set of business values which lead to better stability in the long run. I know when I install a commercial version of PIAF my clients do not want me to view them as lab rats to experiment with using bleeding edge software. Rather they want stable proven software that "Just Works" (C)
The current version of the 1.4 tree (1.4.26.2) What I refer to as a silver choice does work but uses Dahdi. Dahdi has improved to the point where it can be used but there are other issues now in the current 1.4 tree which makes it more unstable (my opinion) that the "gold standard". There are a number of issues that need to be resolved before I would "unleash" this version on any of my clients.
For those who wish to use it you can simply use the update-source and install the very latest. Have at it! This will be changing in the future with the addition of a new payload package. Indeed the next 1.5 beta of the ISO will contain an updated installer which will give you the ability after the ISO is installed to choose 1 of 5 choices.
For the 1.4 Asterisk Tree
1. PIAFXtras menu
2. Install our Gold Standard (asterisk/zaptel 1.4 FROZEN)
3. Install our Silver Standard (Asterisk/dahdi 1.4 current)
4. Install the latest Beta
5. Quit
For the 1.6 Asterisk Tree
1. PIAFXtras menu
2. Install our Bronze Standard (Asterisk/Dahdi 1.6 current)
3. Install the latest Beta
4. Quit
Thus you will be able to "Go to hell in your own way" as it should be.
Also update-source 1.6 will be making a re-appearance shortly so please be patient.
As for 1.6 version being out of sync. Yep we keep breaking the current version of 1.6 so I have not updated it in the load files. Would you like me to simply put in the current version without testing it? I am quite happy to simply do this and NOT test every version that comes out. This way the users of PIAF can have the joy of discovering problems and figuring out ways to fix them..... :beta1b:
Our testing matrix is as follows
both 32/64 bit OS's
1.4 frozen
1.4 current
1.6 current
Thus every time a new version or update comes out we install it on both 32/64 bit versions of centos. Generally each load file contains asterisk/dahdi/libpri/addons. Thus if just one component of the mix is updated everything has to be tested again. I have found that because of the way the asterisk group of products is written you can change a single component and everything stops working. I generally install piaf a couple of times a day with updates etc.... Guess this is not enough huh......
This all means that there is a definite delay in updating the load files with the very latest (unstable at times) source from digium. The update-source protocol is in place for the 1.4 tree to allow you to "do it your way"
Hopefully this helps clarify things...... If not :nukeb:
Regards
Tom
Phone System 