We've been testing it in our office for a little while now - phone systems is our core business.

Love 3CX. The licensing is slightly annoying - having to get yearly licenses etc. But it's how everything is going anyway. If you can get away with just the standard features and 4 simultaneous calls there is no licensing cost.

The Pro features are super cool though. For us specifically, the CRM linking is a key feature. Otherwise, standard is very powerful.

Auto-provisioning works perfectly for phones, mobile apps, and softphones. 

The set up we are testing is an Amazon EC2 instance (in Sydney), along with a Raspberry Pi SBC in the office. I was worried about latency, but so far haven't seen any real issues.

Used it in big and small cases on Linux and Windows. It's a great platform.

sfrasernz: I tested it before deciding to go down FreePBX route. I wanted more control over my IVRs and time based routing of calls which I couldn’t do in the free version of 3CX.

The configuration of 3CX was pretty straight forward and the phone provisioning was pretty slick. That said there is a provisioning module for free PBX which would do the same.

If you need more advanced features I’d suggest considering FreePBX otherwise for basic functionality you can’t go wrong with 3CX.

Yep that's fair.

I would say if you want the ability to do ANYTHING, FreePBX.

If you want a enterprise grade phone system, with all the expected features of a phone system, mobile apps, PC softphones, web conferencing, and CTI then 3CX is the obvious choice. I don't think "basic functionality" is a fair way to describe 3CX though. The call flow stuff in 3CX is enough to suit 90% of businesses out there.

Came free with our phone systems and the staff hated it. Had serious issues with outside calls and a 3cx system call then causing issues over the top (apparently this has now been fixed sort of). As the decision to move was based on the fixed voip end and we saw this as a freebie taking it off the phones was no biggie.

If most or all users are 3cx only then will work well (once sort if doing over wifi or mobile). But if a mix of desk phones, forwarded calls and 3cx calls then expect the non IT people to bitch something major. We removed it from most phones, in the end, to shut them up. Myself and Director still use and like it.

Anyone got it working with Spark Voice Connect?

chevrolux:

 

We've been testing it in our office for a little while now - phone systems is our core business.

 

Love 3CX. The licensing is slightly annoying - having to get yearly licenses etc. But it's how everything is going anyway. If you can get away with just the standard features and 4 simultaneous calls there is no licensing cost.

 

The Pro features are super cool though. For us specifically, the CRM linking is a key feature. Otherwise, standard is very powerful.

 

Auto-provisioning works perfectly for phones, mobile apps, and softphones. 

 

The set up we are testing is an Amazon EC2 instance (in Sydney), along with a Raspberry Pi SBC in the office. I was worried about latency, but so far haven't seen any real issues.