New production installations of Issabel

This site is best viewed in a modern browser with JavaScript enabled.

New production installations of Issabel

randallrw

This really a request to the leaders of the project. I think it is the moment to have a formal recommendation from you of what to do in new installations. As an example, the next week I have a production VoIP PBX to install and it is not clear at least to me which is the best way to do that right now. I know that the very good functional add ons that we were used to will be back soon enough to Issabel.

The general idea is to say, ok if you cannot wait for the stable release of Issabel the best way is to install XX.iso and change the repos and later yyy and later zzz.
This will be a serious responsibility from you I know, it is not written in stone, but will bring peace at least to my mind.
Thanks people from all your efforts.
Randall

RiveraPer

Acabo de terminar una instalación. Para ello he usado una ISO de elastix 2.5, después cambie los repos y actualice.
El funcionamiento es correcto.
No use la ISO de Issabel 2.5 porque le faltan algunas cosas, por ejemplo el system-config-network.
No aconsejo hacerlo con la versión 4 hasta tener una ISO de Issabel 4 estable.

rodolfoed

RiveraPer Hola, Issabel 2.5 es estable, es elastix 2.5, solo que se le cambia algunas cosas, en general es el mismo elastix, se le da continuidad, ese es el objetivo darle continuidad, algunos detalles aún faltan según leí, pero muy bien se podían hacer desde cli, el caso que mencionas sobre la interfaz para configurar la red se puede hacer editando archivo con vi, la forma tradicional de hacer eso y eso ya no es tan necesario ya que en la documentación RHEL 5 dice que parámetros poner en las rutas respectivas, eso ya es pura CentOS. La distribución es CentOS 5.11, cosa que elastix no lo tiene, se quedó en la version 5.9 si no mas recuerdo, creo que se le debe dar la oportunidad a issabel para ambientes en producción, se esta mejorando para dar continuidad a servidores en producción que usan 2.5, uno que otro detalle aún supongo que falta, pero no es grave, algo asi entendí cuando un developer respondía algunas dudas aquí mismo en el foro, saludos.

randallrw

Thanks Rivera for your reply, the 2.5 I imagine is working great as you said, but I guess is still over Centos 5.x

If that is the case is not suitable for servers with hardware too new that will not work without the proper raid drivers as for example Proliants Gen9. For other hardware less complcated 2.5 will be greate.

The Issabel 4 is in alpha state yet. I have tested but it is not ready for production environments. I know there is a lot of people working on that.

For v4 the scenario will be I guess to install Elastix 4, update if possible and change the repos to Issabel as soon they will be available.

I can help hosting a repo.

thanks again for your suggestions.

RiveraPer

Hola randallrw, He realizado una instalación virtualizada de Elastix 4, he cambiado el repo a Issabel y he actualizado. El funcionamiento es perfecto.
Pero hay que tener dos cosas en cuenta, la ISO de Elastix 4, para mi gusto estaba aún sin terminar, y por otra parte aun no tengo claro como sera la versión final de Issabel 4 y por lo tanto futuras actualizaciones de Issabel 4 pueden no ser compatibles.

RiveraPer

Amigo Rodolfoed, claro que le doy oportunidades a Issabel, tengo instaladas las versiones i386 y 64 de Issabel en maquinas virtuales (de prueba). El funcionamiento en general es bueno, como lo era Elastix 2.5.
He encontrado algunos fallos que en ningún caso afectan a su funcionamiento en producción, pero que fallan en pruebas, no solo el system-config-network que es lo de menos como tu dices, también me falla el modulo DUNDI entre dos servidores instalados con la ISO de Issabel lo cual tampoco es ningún problema ya que se pude hacer editando ficheros. Ademas raras veces se va utilizar el DUNDI en producción.
Lo unico que digo es que hace 5 días monte una PBX para producción con la ISO de Issabel
y me fallo, lo hice con Elastix y funciono. No fue un fallo de Issabel, probablemente me dieron mal la IP, es decir una IP ya usada o algo similar, por prisas intente cambiarla con system-config y vi que no estaba. Como en ese momento no sabia que fallaba y por no investigar mas instale la ISO de Elastix y funciono. Ahora me doy cuenta de que posiblemente el único problema era esa IP.
Agradezco tu información sobre la versión de Centos y en futuras instalaciones usare Issabel. Pero hay un refrán en España que dice que mas vale malo conocido que bueno por conocer, y ante las dudas, uno tira por lo que conoce.

RiveraPer

Por cierto Rodolfoed, acabo de arrancar una maquina virtual que tenia de Elastix 2.5 i386 tiene la versión CentOS release 5.11 (Final).

randallrw

Thanks both for your replies. The situation is other really because Centos 5.11 is better than 5.9, yes, that is for sure, but Centos 5 has 10 years of support and those 10 years will end the next month:

https://wiki.centos.org/FAQ/General#head-fe8a0be91ee3e7dea812e8694491e1dde5b75e6d

The next dates for end of life for the available CentOS releases are:

CentOS-5 updates until March 31, 2017
CentOS-6 updates until November 30, 2020
CentOS-7 updates until June 30, 2024

Then Elastix or Issabel 2.5 over CentOS 5.x should be seen in general as a last resource for the community. Mantaining it with all the effort that it involves is a honorable and respected work specially in this transitional moments where a lot of people are struggling to keep alive production environments that are important and hard to migrate due to complexity, hardware issues, etc., but for new production installations it is not the best environment. It is very important to remember that the security in a PBX is as important as any other server in production, and some of you have seen IP PBXs tried to be hacked hundreds of times in a few hours specially if those are reachable from outside of a LAN.

If there is a way to try to modify the Issabel 2.5 to work over Centos 6 for example it will be great. I had not tested yet and I guess it should not work partially, but it is not my place to say what is not possible, I think as a community we should try to reach the best we can.

As always I am here to help in anyway I can.

Thanks

randallrw

and Riveraper is right, I had done several Elastix 4 production installations that never behaved the same for different and odd things, for example, transferring calls from one IP PBX to another sometimes will be ok just to create and extension with no one using it in the target PBX, making a follow me and just redirecting the call to a queue.

but sometimes that simple things simply not worked and had to find a workaround.

In other installation, Where I imported the extensions from an csv, I had in internal phone calls 6-7 seconds with no ringing in the destination extension. Until I just erased the extensions, and created manually one by one the situation resolved. yes Elastix 4 was not a very mature project, but at least was in a Linux distro with 7 more years of support.

I am posting about this because I care about your future installations and security and that is the heart of an opensource community, people watching the backs from other people.

;-)

Those odd things

RiveraPer

Amigos, yo no soy programador y mi negocio no es la venta de PBX, pero es un tema que me gusta y algunas veces instalo alguna.
No me cabe ninguna duda de que Issabel 4 será lo mejor, mejor incluso que Elastix 4. Pero si hoy me piden una centralita no puedo pensar en Issabel 4 (alpha1), aunque la tengo funcionando en maquina virtual y usando el FreePBX embebido, funciona bastante bien.
Tampoco montaría un Elastix 4, sin ningún futuro.
Por eso he montado un Elastix/Issabel 2.5, tampoco le veo ningún futuro, pero funciona.

randallrw

Then maybe we can say that if the decision is to go for Issabel 2.5 it works ok and if the decision is to install alpha 1 of Issabel install it, use embedded freepbx and wait for new versions to update?

In that scenario maybe it can be developed a migration importer that take the 2.5 backup and will import it later in a Issabel 4.0 stable release. I know not even Palo Santo developed never something like that but they where really a company that answered very slowly to the new versions of Linux and Asterisk and really didn't care much about if you have to start from scratch each new version, and I don't feel at all that Issabel will have that behaviour.

best regards

randallrw

danarf, if FreePBX on Elastix 4 Alpha 1 is working and after that we can just run a yum update to migrate to a beta and son on, it would be marvelous because FreePBX just works but it is not the old Elastix we just loved (water over the bridge I know and we move on)

To have Freepbx in the background will support the new Issabel meantime it will be stable again over Centos 7 and will let us be alpha and beta testers in a lot of production environments.

best regards

randallrw

maybe freepbx 13 it is a little too ambitious, but the developers will tell

;-)

randallrw

You are right, that's why I said that freepbx could be the "bridge" to support Issabel 4 until it reaches the stable status.

redes

danardf Tiene usted razón,