Skip to main content

Thirdlane PBX and Thirdlane PBX MTE CentOS 5.6 based ISOs with Asterisk 1.6.2.18 and Asterisk 1.8.4.2 are available

Posted by thirdlane on Wed, 07/06/2011

OS updated to CentOS 5.6
PBX Manager GUI updated to 6.1.1.11.
Asterisk 1.6 updated to 1.6.2.18
Asterisk 1.4 is replaced with Asterisk 1.8.4.2
PBX is now HA (high-availability) ready


Submitted by bfsworks on Thu, 07/07/2011 Permalink

Would like to try this out any chance on a 64 bit version?

Submitted by ftl001 on Sat, 07/09/2011 Permalink

First error I encountered...Running Asterisk 1.
PBX Tools ->PBX Information


PBX Version

Asterisk 1.8.4.4 built by root
.
.
.
ZAP Channels

No such command 'zap show channels' (type 'core show help zap show' for other possible commands)

Conferences

Voicemail Users

Unable to connect to remote asterisk (does /var/run/asterisk/asterisk.ctl exist?)

Then asterisk segfaults, and restarts itself.

Submitted by thirdlane on Sat, 07/09/2011 Permalink

Strange

Why is Asterisk version 1.8.4.4? The one on the ISO is 1.8.4.2.

Also - something is really not right - if dahdi is installed the section is called DAHDI Channels not ZAP Channels so I don't understand what you are running. How did you install everything - was that an ISO install or you did something afterwards?

Does the segfault happen every time you run this? What happens if you run the same command at CLI?

Submitted by rfrantik on Sun, 07/10/2011 Permalink

Alex:

You generally do a really good job of listing fixes and changes for each release? Do you have a list you can post for 6.1.1.11?

Also wondering if you have thought about using the PAE kernel on the ISO's? Especially the MTE... all of our boxes have at least 8Gig and we are trying to get most up to 16. There seem to be folks on the forum that favor using PAE versus going to 64 bit.

Thanks.

Submitted by thirdlane on Wed, 07/13/2011 Permalink

6.1.1.11
2011-07-02 Fixed a bug where in pickupgroups channels separator was incorrect Thanks Bill
2011-06-12 Added sample provisioning templates for Yealink phones. Thanks Erik
2011-06-09 Fixed a bug in HA cluster configuration where an unexpected DRBD status was not reported correctly.
2011-06-03 Fixed a bug in tl-page where (in Asterisk 1.6.x) phone availability was not determined correctly. Thanks Erik

We are working on a 64 bit ISO. Those favoring PAE can build it - all the sources are available.

Submitted by George on Thu, 07/14/2011 Permalink

any new updates / enhancements coming out for non ISO customers..? seems like a very long time since anything other then bug fixes have been released.?

Submitted by thirdlane on Fri, 07/22/2011 Permalink

Download link is on the Download page :)

You have to be registered and logged in to be able to download.

Submitted by syncro11 on Mon, 07/25/2011 Permalink

1.)
When upgrading from previous versions of MTE. If we do a full backup, format and reinstall 2.2 with 1.8 (previous was asterisk 1.6), will all new features be available, as well as all past configurations including tftp, sip ... be retained from backup?

Is that the practice, or just full backup and load to secondary server with licence?

Or is it only used for new tenants going forward?

2.)
Is there no call parking or equivalent available in asterisk 1.8 MTE? Or is there another workaround method?

Submitted by eeman on Mon, 07/25/2011 Permalink

no, in fact after the restore from backup you will have re-installed all the old scripts. As to what is retained from backup depends on what you chose to backup. If you are talking about just the backup tool in thirdlane then none of the other items or content (such as ftp site, firmware etc) will be restored, they are not part of the backups. The backups from the thirdlane module include the configuration files of asterisk, the license files and ACL lists for the users, the license file, the astdb, the greetings, and if selected the voicemail recordings and recorded calls. If this statement alarms you it's probably because your understanding of how all the different systems and services tie together is limited. This is not an insult, not everyone is expected to understand. It does, however, indicate that the potential to have a crisis when attempting your method of restoration is much higher. You may consider getting some assistance in coordinating a big task like that.

To just upgrade MTE, without a fresh-install-transfer method, one really would just compile/install the new version of asterisk, upgrade the thirdlane webmin module, and republish the routes and huntlists that require new syntax. To implement new features, it's a matter of just enabling those other daemons and getting their configurations correct etc.

as to your question about parking, its officially broken with no Digium effort or even concern to work the problem, first reported 10 months ago. I have a working patch and work-around, however, I can tell by your posting that your level of skill at this appears limited and would highly suggest getting professional help with that task.

Submitted by syncro11 on Mon, 07/25/2011 Permalink

Thank you for the prompt reply Erik-

After your comments, I would rather stay away from upgrading the legacy (PBX Manager 6.0.1.81) on asterisk 1.6

Which leads me to the next alternative, is if we cluster a new 2.2 with asterisk 1.8 with the original legacy and provision all new tenants and phones on the new system, would that cause problems, or leave the 2 system separate a better practice?

As for call parking, I would definitely be interested in professional assistance for a patch / workaround.

Thank you,

Submitted by eeman on Mon, 07/25/2011 Permalink

can you clarify by what you mean to imply with the word "cluster" ? There are several meanings to that word and dont want to assume the wrong one and give you an answer not at all related to what you are intending.

Submitted by eeman on Mon, 07/25/2011 Permalink

well there is a HA cluster for thirdlane, but I am guessing by 'cluster management' we're talking about the mere proxy connection to the other server which essentially is stand-alone. Yes you should be ok with having a separate stand-alone PBX that you bring on new clients and perhaps migrate older ones one at a time.

Submitted by whheesen on Tue, 11/15/2011 Permalink

Hi Alex

Any news on the 64 bit iso?

thanks
Heinrich

Submitted by bfsworks on Mon, 11/28/2011 Permalink

Seriously we have been running 64 bit for the last 4 years stable as could be. We have been using the webmin module due to this but as things evolve future a x86_64 ISO release will be required.