asterisk 1.8 compatible with Redux 3.0.5/4.0.3

[phil_discount]

Hello,

we are using Redux 3.0.5 and 4.0.3 with asterisk 1.4 and vicidial 2.2.1-237.
the system is stable and at the moment i wont upgrade to a newer version of vicidial.

can i install redux 5.0.2 with asterisk 1.8 and use the old extensions.conf and agi-files from asterisk 1.4 / vicidial 2.2.1?

regards
philip

[geoff3dmg]

No asterisk 1.4 configuration files are not directly compatible with asterisk 1.8. I'm puzzled why you don't want to upgrade. It's fairly straight forward to backup your database, install Vicibox 5.03 then restore your database back onto the new system. Could you not at least try it on your test/development server?

[phil_discount]

we did a lot of customization and the moment i've got no time to do this with a newer vicidial version.
i think at the end of year i want to upgrade, but at the moment we have many other projects to do.

is it possible to manually update the extensions.conf and the agi files .. i think at DEADagi to AGI and so on?
perhaps anyone has written a howto? (-:

regards
philip

[geoff3dmg]

You have to change a lot of the formatting in the configuration files, you also have to re-write all the dialplan macros.

[williamconley]

You may be able to get away with Vicibox 4.0.3 which installs asterisk 1.4 (and still the latest vicidial code!).

But your challenge is that the ".conf" files (the static ones, that should NEVER be modified) are modified with some new features/additions to Vicidial. Also some are modified during bug fixes. So you would do best to stick with what you have or begin porting your changes to the newer version of Vicidial in a virtual system. Not using the "stock" .conf files will undoubtedly lead to hair pulling as some of the changes almost seem stupid and unnecessary ... until a strange problem crops up that you cannot explain (failing transfers, but only under certain circumstances?LOL).

Note that there are multiple places to put "custom dialplan" and "custom sip settings" into the system now. So you can have them all embedded and never need to customize the conf files again upon completion.

Another method is to put the customizations into an external ".conf" file and just include them in the base ... then your only change to the base is a single include statement. Easily managed after each upgrade.

In the meantime, the best advice I can give you is to fire up a Virtual Vicidial development box and begin your "port" process.

We've upgraded many client boxes over the years, with customizations built by us and also by the client and I've found that some modifications are no longer necessary (as the feature is already in Vicidial!). Recognizing that can save quite a bit of effort. Which you can do after you have a functional virtual system to play with.

Happy Hunting!

[phil_discount]

thanks a lot, i understand (-: