| Now you can update your old Elastix box to the new 0.9 version! |
|
|
|
| Escrito por Administrator |
| Sábado 17 de Noviembre de 2007 06:27 |
|
This is available to all the 0.8 versions and 0.9-betas. Here are some instructions: If you have 0.9-beta* just run a "yum update" For 0.8.4 and 0.8.5 run the following commands: #rpm -e --nodeps freePBX #rpm -e --nodeps spandsp #yum updateFor 0.8.1 to 0.8.3 run the following commands: #wget http://mirror.centos.org/centos/5/os/i386/CentOS/kernel-xen-2.6.18-8.el5.i686.rpm #rpm -ivh kernel-xen-2.6.18-8.el5.i686.rpm #rpm -e --nodeps freePBX #rpm -e --nodeps spandsp #yum update The 0.7 branch (and any other branch before it) wont be upgradeable to 0.9 because this is an old branch with radical changes. It was based in CentOS 4 and asterisk 1.2. Finally, if you would want to make this process a little bit safer using RPM rollbacks please see this post in our forums. Last minute news: One user has reported that his freePBX database was gone after the update process so backup your files under the /var/lib/mysql/asterisk/ folder until We can confirm or discard this issue. |
| Última actualización el Sábado 17 de Noviembre de 2007 19:47 |
Testimonios
"El nivel de soporte técnico, el costo razonable de sus servicios, la capacidad para implementar soluciones complejas para nuestros clientes más exigentes, y la rapidez en el desarrollo de estas soluciones comparado con el resto de la industria, han hecho de PaloSanto un aliado importante en el crecimiento de nuestra cartera de productos y de ventas" |



Buscar
478 usuarios en línea










Comentarios
Downloading Packages:
Running Transaction Test
Finished Transaction Test
Transaction Check Error:
file /var/www/html/modules/pbxadmin/index.php conflicts between attempted installs of elastix-0.9.0-18 and freePBX-2.3.1-13
Error Summary
-------------
Any ideas?
DB is in place all data ok, however /etc/asterisk/. overwritten and has excluded a2billing entries. :(
Any advise ?
Also I'd be very insterested in the turn for you guys to make RPM rollbacks standard in all future versions of Elastix especially with all the changes that continue to make this product so great.
Thanks for your post.
At this time there are not errors with the zaptel hardware. It was just that some users forgot to edit the zapata.conf. Note that the hardware detector tool does not edit the zapata.conf file.
Sugar vx. vTiger. Good point. Which do you think is better to leave in Elastix?
Please note, that this update process will erase any FreePBX data you have, so per the post above please backup your files under the /var/lib/mysql/asterisk/ folder.
And for those of you with Zaptel Hardware there are reports of zaptel drivers not writing to the configuration files, causing issues.
Next on the list of things to add, any reason we have both vTiger CRM and SugarCRM? I just think it's a little redundant, don't you?
Suscripción de noticias RSS para comentarios de esta entrada.