Issabel ISO (Latest): Download Here
Cloud Services: User Portal - Quick Guide
News: Telegram channel
Become a Patron!
  • Dev
  • Github Mirror of Elastix SVN

It should be better build the source code and the dialplan from scratch, the elastix code belongs to FPBX , so It has the same issues as Freepbx

    If there is an issue with freepbx please file a bug report http://issues.freepbx.org keep in mind the latest version of Elastix is using code that is almost 3 major versions behind. That is thousands of commits. Issues that may have been resolved years ago. There are at least 2 freepbx developers here and happy to help. One of them posted this topic.

      The first is Asterisk 13 / Lo primero es Asterisk 13!
      Elastix 4 con Asterisk 11 realmente ya no va para el nivel competitivo que despliega la industria de Appliances con Grandstream, Yeastar, Zycoo.

        15 days later

        Does source code for Elastix 4 exist somewhere? Elastix 2.5 cannot be used with any recent version of FreePBX due to PHP version conflicts. Elastix 2.5 needs PHP 5.1.*

          5 days later

          What is the username and password to get in as admin?

            During netinstall, you should be prompted to enter passwords for different services, including the one for the web admin.

              Well, it didn't. I think I'll run it again...

                asternic Ya está listo lo siguiente:

                (Github page con links de lo que hay)
                https://issabelfoundation.github.io/issabel/

                La idea es usar GIT como control de versiones del código y utilizar su herramienta de issues para el tracking.

                Lo ideal sería que compartieran su usuario de GitHub para agregar a los miembros a la organización y tengan acceso para subir código.

                Mientras tanto puedo subir el código al master branch.

                E ir redactando un README.md

                Con las instrucciones para montarlo ya sea desde los repos linux o desde git

                Pasé a saludar a HipChat para ver este tema, estoy al tanto vale?

                asternic Pls help me
                I'm install with minimal centos 7
                centos-release-7-3.1611.el7.centos.x86_64
                after install, login to Issabel, CDR report
                ==> (internal) Failed to count CDRs - Error de conexion a la base de datos - could not find driver

                i think it's error when install bash at
                Installing : elastix-framework-4.0.0-19.noarch [################################################################################### ] 34/52
                Installing : elastix-framework-4.0.0-19.noarch [#################################################################################### ] 34/52
                Installing : elastix-framework-4.0.0-19.noarch [##################################################################################### ] 34/52
                Installing : elastix-framework-4.0.0-19.noarch 34/52
                warning: /etc/yum.repos.d/Issabel.repo created as /etc/yum.repos.d/Issabel.repo.rpmnew
                Note: Forwarding request to 'systemctl enable ntpd.service'.
                Created symlink from /etc/systemd/system/multi-user.target.wants/ntpd.service to /usr/lib/systemd/system/ntpd.service.
                error reading information on service mysqld: No such file or directory
                and
                Installing : elastix-reports-4.0.0-6.noarch [######################################################################################## ] 41/52
                Installing : elastix-reports-4.0.0-6.noarch 41/52
                ERROR 1049 (42000) at line 1: Unknown database 'asteriskcdrdb'
                ERR: action install failed for database asteriskcdrdb.
                ERR: status 1 from command: mysql -uroot '-peLaStIx.2oo7' '' < '/usr/share/elastix/module_installer/elastix-reports-4.0.0-6/setup/db/1_sqlFile.sql'.

                danardf Thanks for your reply
                ERR: status 1 from command: mysql -uroot '-peLaStIx.2oo7' '' < '/usr/share/elastix/module_installer/elastix-reports-4.0.0-6/setup/db/1_sqlFile.sql --> file doesn't exist

                Here is mysql
                Welcome to the MariaDB monitor. Commands end with ; or \g.
                Your MariaDB connection id is 21
                Server version: 5.5.52-MariaDB MariaDB Server

                Copyright (c) 2000, 2016, Oracle, MariaDB Corporation Ab and others.

                Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

                MariaDB [(none)]> show databases;
                +--------------------+
                | Database |
                +--------------------+
                | information_schema |
                | asterisk |
                | asteriskcdrdb |
                | endpointconfig |
                | meetme |
                | mya2billing |
                | mysql |
                | performance_schema |
                | roundcubedb |
                | test |
                +--------------------+

                Database changed
                MariaDB [asteriskcdrdb]> show tables;
                +-------------------------+
                | Tables_in_asteriskcdrdb |
                +-------------------------+
                | cdr |
                +-------------------------+
                1 row in set (0.00 sec)

                  netsinstall script was updated, and I think it will fix the issues you are reporting.

                  Original elastix rpm packages do 'odd' things, like resetting mysql password to eLaStIx.2oo7 in /etc/elastix.conf while mariadb has "no password" for root at installation time. So now the script installs mariadb, sets the root password to that old elastix default, then install elastix packages (with no auth errors on db). After installing elastix packages it resets the password back to blank, and finally executes elastix-firstboot so you can set the mysql root password and elastix admin passwords.

                    juliorfa No es mejor que partiendo del repo inicial usuarios hagan fork y creen pull requests para subir/modificar/eliminar código y designar a varios desarrolladores como admins quienes puedan aceptar estos pull requests después de haber sido revisadas y discutidas en GitHub ?.

                    Pienso en esto para evitar que se suba código al master branch con bugs o que no sean directamente discutidos o revisados al menos por otra persona de la comunidad.

                    Saludos,