Links hidden for unregistered users. Login or register Here. This release is for testing only, it is not for production use.

The main changes on this releases is that it is base on CentOS 5.2 with kernel 2.6.18-92.1.17.el5 and it also update new packages such as freepbx, misdn among other improvements.

Changelog:

- New avantfax module in extra repositories
- New text to speech module (Early stage)
- New report by trunks
- New report by queue
- Web Interface so that users can administrate their voice mail
- Kernel update to CentOS 5.2 version (2.6.18-92.1.17.el5)
- Hardware detector supports for misdn
- Free PBX updated to 2.5.1
- Enable wake extension in dialplan
- Asterisk log: include filter by string
- Dialer now supports sip trunks
- Endpoint configuration: update atcom.cfg.php
- Misdn updated to 1.1.8


Help is needed testing updates, at the moment we have problems with freepbx after an update. So enable the beta repos and help us test the upgrade process


Regards,

Rafael

Wow Rafael!! Great news!!!

I was hoping news about the next version of Elastix!

I see many features interesting for me and for many people in Spain, where ISDN is used. I see mISDN hardware detector, mISDN updated to 1.1.8 and kernel update.

Thanks Rafel for this great news, and thanks to the all developers from Elastix Team.

Ciao.

It's a good news.

I try it.

Rafael,

Have installed 1.4-1 Beta on a machine with TDM400. Installation ok with no errors
Comment: Like the clean interface of the hardware detection. Detected TDM400 ok.

Looked at Freepbx 2.5.1.0
Freepbx changed my php setting immediately to 100Mb from 16Mb (automatic)
Comment: Good .... having seen this issue before where 16Mb was not enough.

Performed Module upgrade
Comment: All looked good - no errors reported by upgrade process
Performed Module Install (for modules not installed by default)
Comment: No errors reported by install process

Checked Freepbx System Status - All clear...no errors to report

Will continue testing, but everything works as per 1.3-2 Elastix
Except Checked FOP - aghast!!! - FOP is showing up ZAPTEL trunks....

Performed YUM update - looks good - no errors

Comment: Good - Elastix now using Zaptel 1.4.12.1 (should correct a few recent wctdm24xxp detection issues)

All system config was rebuilt by hand via unembedded Freepbx, however, as a test also added one extension via Embedded Freepbx. Extension added successfully with no errors and extension working, confirmed it was visible via Unembedded Freepbx without any errors.

Only one minor comment on the Embedded Freepbx, the small icons are not showing up next to Delete Extension and Add Follow Me which are elastixsystem/images/user_add.png & elastixsystem/images/user_delete.png. Note this is extremely minor.

On the whole, so far, one of the best and smoothest installs, and thats not bad for a beta. If the only error to report is a couple of icons missing, then there is not too much to worry about. Based on this install I have moved this PBX into production use for the time being to put under further test.

Regards

Bob

Using 1.4-1 Beta
As part of the process of moving completely away from the command line to complete Elastix systems,
Decided to use the packages update interface to enable the Elastix-Extras repository and then install AvantFax.

Enabled the repository, then found Avantfax to install.
Commenced install, and got the hour glass. However it sat there for over 15 mins, and I finally decided that it had failed. Could not access Elastix GUI again, and also freepbx GUI also was unresponsive.

Had to reboot Elastix, and on checking packages, it said it was loaded.

Just reporting this, in case others come across it as well. The message is not about avantfax, but the packages update system.

Regards

Bob

Hi Bob,

The small icons, you can copy it from /var/www/html/admin/modules/core/images
# cp /var/www/html/admin/modules/core/images/* /var/www/html/images

Hi Saleh,

Thanks for the tips. If I can add something about this images:







Also I want to confirm issue with installing package from GUI described by Bob.

STOP THE PRESS!!! (Unconfirmed)

There is a major issue with the 1.4.1 Beta. After performing more tests, it appears that there is a problem with the TDM400 card. Now fair enough, these cards are becoming End of Life, but there are literally thousands and thousands of them out there. Add that to the number of clones out there which will also suffer the same issue.

Issue: The TDM400 shows up as configured, Zap show channels and Dahdi show channels shows the channels configured. Everything looks normal. Incoming calls work perfectly, but outgoing calls fail with the following message:
app_dial.c: Unable to create channel of type 'ZAP' (cause 0 - Unknown)

Resolution: None known yet

Further Info: It appears that this is not an Elastix issue with PIAF also showing similar problems
www.pbxinaflash.com/forum/showthread.php?t=2417&page=5. They submitted a Bug to Digium, but basically they blew it off, not supporting A400 cards. The fault is exactly identical to my issue, yet I have a Genuine Digium TDM400 card.

If anyone has a digium TDM400 and can test with 1.4.1Beta, it would be appreciated to turn this report into a confirmed report. If you have found that your TDM400 works, likewise love to hear from you.

The TDM400 that I am using is a working card, as is the machine that it is in. It was previously running 1.3-2 only several hours before, so we are not talking about hardware failure.

The most likely causes are
1) Elastix has introduced a bug in the Asterisk build. Note that since all the Zaptel stuff works, it is more than likely to be in the Asterisk application, not the zaptel.

2) Digium have not tested the Asterisk code with TDM400 cards.

3) Digium choosing to not support the TDM400 due to end-of-life.

4) The only other think I can think off is that I note that the Asterisk version being reported in the 1.4.1beta is 1.4.22rc5. I note that there is a later release in the Elastix repository and that there may be a missing link between Asterisk 1.422rc5 and the latest Zaptel. It is possible PIAF has done the same thing.

Anyhow running more tests, and possible fixes, but wanted to make sure that 1.4.1beta does not get released until this report is confirmed or debunked.

Regards

Bob

Bob

I noticed the same issue after doing a clean install of 1.4 and TDM400 card
Calls would come in but not allow out going, so called my pstn line and sure enough call came in

Now this time calling back out from zaptel the call would proceed with no issue, it was like the zaptel driver was going to sleep.

But for the last 4 hours I have not had the issue
Also I did the clean install but didn't do the yum update, only updated freepbx modules

Dave,

I have been doing some hunting this morning and believe that it is Zaptel related. Also noticing some bug reports been reported in the last couple of days for the TDM400 on the Digium Bug Trac. In particular one relating to the channel being unavailable. Only skimming at moment, will try running back to 1.4.11 Zaptel just to confirm issue.

Shame, the release was looking absolutely solid until I noticed that my outbound calls were going out via IAX....

Regards

Bob