@dustinb3403 said in Virtualizing Your Cudatel Appliance: @scottalanmiller said in Virtualizing Your Cudatel Appliance: Go ahead, download FreePBX and start playing with it. You could have installed it while reading this article! Any good installation guides here on ML? @JaredBusch has a great series of posts for FreePBX here. https://mangolassi.it/topic/11805/freepbx-13-setup-guide

@wls-itguy said in FreePBX - No Incoming/Outgoing Calls: @scottalanmiller said in FreePBX - No Incoming/Outgoing Calls: @wls-itguy said in FreePBX - No Incoming/Outgoing Calls: I have a PRI and it is through Time Warner/Spectrum. That all checks out on their end. Oh. Ewww At the time we didn't have a SIP option. Now that they are trying to make us pay a $7000 bill for their F-up we'll be looking for a new SIP provider. VoIP.ms and Flowroute I use and are good. Twilio, I have not used yet, but it has good recommendations.

@dustinb3403 said in VoIP over Wifi: You should set traffic shaping on wireless the same as you would on your LAN. Doesn't work the same. It's a bus, not a switch.

@JaredBusch said in FreePBX 14 Release Candidate is out: @tm1000 said in FreePBX 14 Release Candidate is out: @JaredBusch that is correct I am interested in Zulu but never set it up because a 2 users license for only a year is useless. Or does that auto renew so I always have 2 users for free? If that is the case I will set it up on my company PBX for myself and another user. None of my clients have had an interest sadly. Same here, time out free licenses I generally avoid.

Now log into your new FreePBX system and it will show the Apply Config warning. Do so. At this point you can go through the new system one piece at a time and make sure you are good. Change a couple extensions to point to your new PBX and make sure they register and can call each other. Once you are sure that the basics are working, disable the trunks on the old system, enable on the new system, and verify outside connectivity works. Finally, you can change the rest of the extensions.

3CX's behaviour as a company on the Spiceworks forums is additionally reason to not deal with the product.

It is a sales tactic...

@JaredBusch said: No, you are missing the entire point. There is a reason that Elastix dropped FreePBX in 3.0. There is a reason the the PBXiaF team has spent the time and effort to come up with the Asterisk GUI distribution. Both teams obviously hope that nothing changes as they are also continuing efforts with their products that use FreePBX. FreePBX is a horrible interface. It is dated and sad. It works, mostly, but leaves a lot to be desired. Ever since FreePBX switched from being an interface to being a full on competitor to Elastix and PIAF they have had a huge incentive, really a need, to develop their own thing. If anything, my guess is that they hope that FreePBX does do something drastic and force them to either take over or abandon FreePBX, not that they fear that. I felt for years that they needed to do this, having nothing to do with source worries with FreePBX. Simple business pressures would make them do what they are doing. Nothing more is needed.

@Reid-Cooper said: Hopefully this means even more commercial development in FreePBX. It's a good product but could use polishing. The new version that "just" became stable is fairly good. I'm going to deploy it to replace an old Trixbox server at our NC site. Not flashy by any stretch but very functional.