trixbox 2.8.0.4 released

That is a great Job indeed... Thanks for all...

I've asked this before a couple of times but did not get an answer: Will 2.6 ever get a new CentOS?? CentOS 5.4 and above have much better timing under VMware.

That brings me to the 2nd question, why did you stop offering a VMware image as a download option?

With the recent introduction of PCI pass-through, there is now a chance to even use Hardware FXO and FXS Cards with a trixbox VM.

2.6 is not being maintained, it was EOL several months ago.

The new CentOS is great however we need to move to a later FreePBX and Asterisk as soon as possible.

The new 2.8.0.4 image has been added to the tribox.leadmon.net archive

You can access the images vi rSync, FTP, or HTTP.

Info on how to rSync is in this thread:

http://www.trixbox.org/forums/trixbox-forums/open-discussion/trix...

You can FTP the images from:

ftp://trixbox.leadmon.net/trixbox

You can HTTP/WEB the images from:

http://trixbox.leadmon.net/ftp/trixbox/

As always locally generated MD5 checksums are available, as well as the enhanced SHA256 checksums for all files in the archive.

Are you aware of a bug in queue with ring strategy not at ringall. Do you know if is fixed with this version of asterisk.

Thanks

Excuse the possibly stupid question, but I can't get to the two systems to test at this moment. If I take a 2.8.0 CD and install then do a yum update do we end up with 2.8.0.4? or do we have to install as that from the start?

I see the comment that 2.6 is eol - is there every going to be an upgrade path or is it a manual rebuild from scratch?

Thanks

Gavin

You can update any 2.8 system to 2.8.0.4 with yum. You may need to run dahdi_fix.sh if it's a really only 2.8 system.

There is no upgrade path for a 2.6 system you need a clean install.

Hi All,
I updated to new version and my CDR has a bunch of big red boxes all over it.
Also, call recordings have stopped showing up in the call monitor in my extension.
Any ideas ???

The CDR Report boxes are all along the lines of ....

Appcelerator Processing Error:
Element [div] with ID: app_11 has an error:
message: '1' is null or not an object, location: undefined
in
compiling "on" attribute for element app_11

Cheers ...

use IE in compatibility mode or firefox it worked for me

Hi!
I'am sorry. But where is located 'dahdi_fix.sh" ?
Thx.

i've read a few posts saying NOT to do "yum -y update" as breaks things... is this correct? if so, what's the best way to update then from 2.8?

andrew wrote:

You can update any 2.8 system to 2.8.0.4 with yum. You may need to run dahdi_fix.sh if it's a really only 2.8 system.
There is no upgrade path for a 2.6 system you need a clean install.

What and where is dahdi_fix.sh and how do you know if you need it - I searched the forum with no mention and Google came up with 2 responses in German, a search of a 2.8 system produced no results either.

Thanks

Gavin

Just letting you know that IE in compatability mode worked a treat, but firefox 3.6.3 doesn;t work :(

Also have noticed that the CDR itself has not recorded a call since the update was installed.

Also user's recordings are not showing up in recordings.

Hi,

I've been running 2.8.0.3 and just upgraded to 2.8.0.4 and have a couple of issues with both versions.

1) I have call recording set to always on all extensions, but calls picked up from the parking lot don't get recorded. I understand this is an issue with asterisk, but I didn't know if there was a workaround.

2) We have grandstream phones and use the transfer button on the phone vs using feature codes, which works just fine except that we loose the beep indicating the transfer is complete. Any way to fix this?

3) We have 3 sip trunks configured and they seem to work just fine. However, if the internet goes down and the trunks can't register, all of my phones lose connection with trixbox. I have to disable the trunks and restart the server for them to provision. Is this a bug?

Thanks for your help - keep up the good work!

How to use fix-dahdi was posted in my dev blog a few posts below this one. I'll repost it here.

wget http://yum.trixbox.org/fix/fix-dahdi.sh
sh ./fix-dahdi.sh
yum clean all
yum update

yum update is always the best way to get the latest code.

Were did setup-sangoma go?

And where is the wanpipe that that matches the kernel?

Hi all today i get a message on the dash board that there is a new update so I go into the module do and upgrade and it installs a freepbx upgrade tool which i Follow is instructions. well know it wont let me apply changes. I am using the 2.6 version but I'm confused because it seems i tried to upgrade to 2.8 . here is the link of the post . please help me out to figure this out.
http://www.trixbox.org/forums/trixbox-forums/open-discussion/core...

thank you
rrichiez

OK, the repo didn't have the right wanpipe, they had to come from Sangoma's FTP.

what to do then? wait?
rrichiez

Hi Andrew,

This longtime bug still exists for us. When we restart trixbox, all of the queue's are broken and not working. In order to fix, we must use the web interface to update/save the queue and then they start working.

Something about the restart of trixbox is not starting the queues properly.

Any ideas?

norlab, that thing was fixed a long time ago in The Real FreePBX, I guess that andrew did not "fork" that.

If you upgrade or do a clean install 2.8.0.4 has a dahdi fail through lack of timing. 2.8.0.3 works so it must be a change somewhere as opposed to a hardware issue.

Andrew - I've put additional info in the Help section of the forum please check this out and let me know if you need additional info or if there is a simple fix for this.

Thanks

Gavin

Hi, Andrew!

There was a problem with WebMeetMe with Asterisk 1.6.0.22.

Error loading module 'app_cbmysql.so': /usr/lib/asterisk/modules/app_cbmysql.so: undefined symbol: __ast_malloc

Does it work now?

Thanks mickecarls...Is there a link to a patch or bug report that we can bring into this post?

I'd like to help get this patched because its a really scary bug for us, if the system reboots overnight we might not know that we're loosing a bunch of business.

Thanks for the comment!!

Hi,

The error not loading queues upon reboot is detailed in these two bug issues.

http://www.freepbx.org/v2/ticket/3118

https://issues.asterisk.org/view.php?id=14179

They stated to add:

>>> Try also adding "preload => chan_local.so" to modules.conf.

I'm going to give this a try, after hours, and I'll report back after testing.

We have a few extensions with "follow me" that has the original extension in the follow me list along with other extensions. If one of these extensions that has follow me is in the queue, then no one in the queue can answer calls. When they pick up the phone they hear "Answering...." and they wait. Sometimes they can wait for 30 to 60 seconds and the call will finally go to them.

This didn't happen in our previous 2.6 build. Can anyone explain why or what should be done?

The follow was added to modules.conf to fix the queues not starting on reboot. I added the two preload commands and now the queue's start as expected !!!!!

Thanks mickecarls for pointing me in the right direction.

[modules]
autoload=yes
;
; If you want, load the GTK console right away.
; Don't load the KDE console since
; it's not as sophisticated right now.
;
; added to fix queue starting issue
preload => chan_local.so
preload => pbx_config.so

http://trixbox.org/forums/trixbox-forums/help/trixbox-2804-cdr-ph...

Figure would post it here in case someone who can help fix see's it and also to let others know not to use 2.8.0.4.

The issue was noticed with CDR reports but now stems far beyond that...

All,

I have produced a fix for the CDR issue.

Andrew memcached is not set to auto start in the 2.8.0.4 iso

the following lines fix it for me and one other user who has tested so far

/etc/init.d/memcached start
chkconfig --add memcached
chkconfig memcached on

It seems the old bug of extension 666 not working is still there. In order to fix this I added an entry to extensions_override_freepbx.conf as follows. Note the problem is that rxfax should be ReceiveFax on line#3.

[macro-faxreceive]
exten => s,1,Set(FAXFILE=${ASTSPOOLDIR}/fax/${UNIQUEID}.tif)
exten => s,2,Set(EMAILADDR=${FAX_RX_EMAIL})
exten => s,3,ReceiveFax(${FAXFILE})
exten => s,103,Set(EMAILADDR=${FAX_RX_EMAIL})
exten => s,104,Goto(3)

This is not a bug related to this release but just a helpful tip for anyone trying to get faxing working on dedicated inbound routes. After fixing the 666 bug mentioned above I added a custom context to extensions_custom.conf as follows:

[custom-dest_fax]
exten => s,1,StopPlayTones
exten => s,n,Noop(${CALLERID(number)})
exten => s,n,Goto(ext-fax,in_fax,3)

and then defined a "custom destination" via the freepbx GUI as follows:

custom-dest_fax,s,1

I was then able to add it to the appropriate in-bound route as a custom destination. This allowed me to route all calls matching the inbound route to a "fax machine" (actually using system virtual fax)

Hope this helps anyone else with a similar situation.

I will be trying the above fix if it's going to work.

hello:
there is no opvxa1200.ko in kernel, so openvox a1200/a800p will not work with this version,please recompile that if you want to use.
Regards!
James.zhu
OpenVox cards, asterisk/zaptel/dahdi. Email: james.zhu@openvox.cn

I'm using 2.8.0.4 and have found a couple of books available through Amazon.com related to the 2.6 version. Are there significant differences between the minor point releases? Can you suggest a book?

Thanks in advance.

http://www.penguincomputel.com