Best posts made by tm1000

Not to "toot" our own horn or anything but some others might find this interesting/useful.

https://www.freepbx.org/what-happened-to-elastix/

@JaredBusch said in 2600hz.org - Open Source VoIP:

@coliver said in 2600hz.org - Open Source VoIP:

@agarcia.wier said in 2600hz.org - Open Source VoIP:

I think now is the time to invest in true open source alternative to Asterisk engine

How is the Asterisk engine not open source? It's released under the GPL meaning you can do whatever you want with the code base. FreePBX remains one of the, if not the, very best implementations of an Asterisk distribution that is also 100% open source. I'm just not sure where you're going with the last few threads about this.

Asterisk and FreePBX are open source, but Schmooze made changes regarding things such as third party module signing and requirements related to commercial modules that soured the mood with some in the FOSS telephony community.

The referenced article is old. As of this year you can sign your own modules without asking for anything from Sangoma. We've even written unit tests around this functionality so it can never break. We do listen to the community and have made changes over the last two years to how GPG functions. One of the biggest things we did was allowing users to sign any module locally without having to sign a CLA or a CSA with Sangoma, putting the power of open source (with GPG benefits) back into the hands of users.

@scottalanmiller said in True Open Source PBX:

@JaredBusch said in True Open Source PBX:

I am interested in Xivo (whatever their new name is).

It is not production ready like FreepBX yet, but their goal of making everything accessible via REST API will make it a very flexible thing.

Me too, certainly lots of potential and I hate the FreePBX interface, so am hopeful there.

Let me know what you don't like if you have time!

Also the Wazo(XiVO) developers are great guys. A few of the FreePBX team (Rob Thomas ( @xrobau ) and I) talk to them ( @quintana ) weekly on IRC/Twitter and we've conversed over a hangout session and at Astricon.

Hi all!

Hi guys,

I work for Sangoma so I wanted to try to clear some things up here...

Some comments here. We have to (By law) call this Sangoma 7. If you redistribute CentOS (commercially... which we do) you can not use their trademarks. Therefore we have to call it something else. See here for more information: https://www.centos.org/legal/trademarks/ and http://nerdvittles.com/?p=8888 and http://community.redhat.com/centos-faq/#_centos_trademark

Specifically

A Linux distribution can only be called CentOS if it is built on code in git.centos.org, is signed with the appropriate keys, and released by the CentOS Project. If you were to rebuild CentOS source code on your own, you could not call the result CentOS.

We've actually had to repackage our own distro for a while now. Since at least CentOS 6.5 (Not sure of the exact timing). You'll notice it's called shmzOS

We will update the CentOS 7 guides. Sorry about that we've been slacking.

PHP 5.6 is still supported by PHP so yes. It's modern. We can't (at this time) jump to PHP 7 because it does not support Zend which we use for our commercial modules BUT that said it should work perfectly fine on PHP 7.

@scottalanmiller We are starting to use it to build more robust Daemons. Hey, it's better than trying to do it in PHP!!

@jaredbusch said in FreePBX 14 Module Update Errors:

@tm1000 I was not complaining. I was actually stating that I have never seen as many issues at once before, ever. You guys do a great job.

Thanks Jared. Just explaining what went wrong for those curious. I'll push the firewall issue to Rob later today

@bigbear said in FreePBX 14 Release Candidate is out:

How long before they rename it Sangoma FreePBX?

Never. It's still FreePBX. In the last year we've actually done more open source work than the year before.

@bigbear said in FreePBX 14 Release Candidate is out:

Something I was discussing with someone the other day. If you don't purchase their System Admin module how do you update?

Through module admin. Nothing has changed there. All we did was change the ability to update the system from system admin to module admin. So you update the system there now. Automated system updates have always required a purchase to System Admin, so again nothing has changed here except for where it's at and how it works (slightly).

For modules you still upgrade them through Module admin.

@bigbear said in FreePBX 14 Release Candidate is out:

Is this Zulu now or is it Zulu "Private Interal Beta Edition"

This is Zulu now and customers are using the chat functionality. It's not internal. Not sure why it would matter if it was an internal Beta Edition anyways.

At this time that feature does not exist in 14.

https://issues.freepbx.org/browse/FREEPBX-15598

@bigbear said in FreePBX 14 Release Candidate is out:

Matters because I want to know if Zulu is worth checking out today.

Ah yes it's out right now. Most of our internal "betas" are actually alphas which end users can download. We rarely ever have an internal beta these days since we have version tracks.

@bigbear said in FreePBX 14 Release Candidate is out:

BTW @tm1000 I signed up for an RMS beta and its turned out to be pretty cool. Havent seen any pricing other than the beta in the portal though. Is it currently for sale?

RMS should be for sale. I think it's $5/month/server

@netprimates said in FreePBX 14 Module Update Errors:

I assume you are referring to repo bug [17585] - https://issues.freepbx.org/projects/FREEPBX/issues/FREEPBX-17585?filter=allissues which seems to have been closed

Closed with a resolution. Not just closed.

@jaredbusch said in FreePBX 14 Module Update Errors:

Core and framework updated again.

Which fixed a codec read issue with Asterisk 13.9 and lower

@jaredbusch said in FreePBX 14 Module Update Errors:

It must be the week of bad updates or something.
I cannot remember the last time they had a string of bad updates like this.
I update systems monthly-ish and have not had a problem since sometime last year.

We did not upgrade or release any firewall versions this release. The last firewall version published to the STABLE track is 19 days old.

The only one in edge is:

• There are 198 systems using version 13.0.55.3 of firewall (94051). It is 2 days old
• There are 1 systems using version 13.0.55.2 of firewall (94041). It is 2 days old

I wouldn't say it was a week...It was one day of pushing moving EDGE modules to STABLE that required other modules that weren't released (core required a version of framework that was in edge, ivr required core that wasn't released at the same time as core was, it was release about an hour later).

Rob just got back to me and swears the trust code hasn't changed in a long time but he'll look at it later today

Our QA team has confirmed that firewall has no issues:

https://community.freepbx.org/t/bug-in-latest-firewall-adding-ip-to-firewall-trusted-zone-no-longer-updates-iptables-firewall-rules-on-firewall-restart/50181/9?u=tm1000