SOLVED IncrediblePBX13.2.iso problems take 2
- Thread starter qtlnx
- Start date
- Status
In a software distribution business it is significantly more reliable to use appropriate platform tools, like rpmbuild with its slew of helpful build macros, instead of make && make install.... When I start using a custom program I almost always build an rpm and then just rebuild rpm with next version when required. If you really prefer debian then you can always make .deb package such a way that it is automatically converted to rpm by alien tool.
wardmundy
Nerd Uno
- Joined
- Oct 12, 2007
- Messages
- 20,219
- Reaction score
- 5,974
@qtlnx: We provide a platform for a variety of users with a variety of skill sets: hobbyists and tinkerers, small businesses, large businesses, home users, telephony engineers and managers, network administrators, Linux whiz kids, and other assorted techies that want to try out new things before introducing them into their "day jobs." As such, RPMs are much less flexible for those of us that want to tweak things and experiment with solutions to meet individual or corporate requirements. There are plenty of RPM solutions floating around if that's your thing.
When you raised your complaints about the Incredible PBX ISO, I was tempted to tell you to learn something about the Asterisk menuselect application, but something told me that probably would not have been well received. In any case, under the Compiler Flags section in the Asterisk module builder, there is a flag for BUILD_NATIVE. We typically leave this turned on, but it would have been the first thing I turned off if Asterisk wasn't building properly on a particular platform (which you never quite disclosed). That gives you a more generic/vanilla compile similar to what you would get with an RPM solution. You might want to try that on your platform and see what you get. I suspect it will work just fine.
While your approach also seems to work (for you), it required delving into the Asterisk weeds big time. Your compiler failure was the first one reported in at least the last five years, and our installed base runs to hundreds of thousands of users. The fact that it happened on a Fedora VM and not on Enterprise Linux derivatives should tell you all you need to know about using Bleeding Edge platforms.
As I said, we will take a look at incorporating your change into future installers, but that requires considerably more testing on a variety of production-level platforms. You of all people should appreciate why we can't merely adopt your conclusion that "it worked for me." That's especially true with Fedora solutions.
When you raised your complaints about the Incredible PBX ISO, I was tempted to tell you to learn something about the Asterisk menuselect application, but something told me that probably would not have been well received. In any case, under the Compiler Flags section in the Asterisk module builder, there is a flag for BUILD_NATIVE. We typically leave this turned on, but it would have been the first thing I turned off if Asterisk wasn't building properly on a particular platform (which you never quite disclosed). That gives you a more generic/vanilla compile similar to what you would get with an RPM solution. You might want to try that on your platform and see what you get. I suspect it will work just fine.
While your approach also seems to work (for you), it required delving into the Asterisk weeds big time. Your compiler failure was the first one reported in at least the last five years, and our installed base runs to hundreds of thousands of users. The fact that it happened on a Fedora VM and not on Enterprise Linux derivatives should tell you all you need to know about using Bleeding Edge platforms.
As I said, we will take a look at incorporating your change into future installers, but that requires considerably more testing on a variety of production-level platforms. You of all people should appreciate why we can't merely adopt your conclusion that "it worked for me." That's especially true with Fedora solutions.
Last edited:
is positioned as simple out of the box unattended installation with no questions asked except for google voice authentication method.
wardmundy
Nerd Uno
- Joined
- Oct 12, 2007
- Messages
- 20,219
- Reaction score
- 5,974
Yep. And, as I said, it's worked that way for all but one individual out of 100,000+ users. And it worked that way for you as well when you deployed it on VirtualBox. You elected to move to a non-standard, Bleeding Edge platform for deployment. With that choice, the monkey shifted to your back to address anomalies caused by your platform which we neither support nor recommend. You learned (the hard way) that your platform turned out not to be quite as identical to VirtualBox as you originally suggested. Contrary to your assertion, most cloud providers don't host their virtual machines on the Fedora platform for one very good reason that you, too, have now discovered. As also mentioned, if you prefer RPM solutions, there are plenty of them available including Incredible PBX for XiVO. Finally, there are some terrific commercial solutions including our corporate sponsor 3CX if you find the price tag and/or aggravation of an Incredible PBX deployment unacceptable. Best of luck finding your perfect software platform. It may take you a little longer than a couple of days.
Last edited:
I think you a missing the point. My Fedora does not really differ from RHEL 7 from all intends and purposes.
I've been using Red Hat products from v3.0.3 and know what is "Bleeding Edge" and what is not.
This problem solved, I am not the first who encountered asterisk "invalid instruction" and this is the end of the discussion.
I need to actually accomplish something so may ask real usage questions later. Thank you.
- Status
Forum statistics
Get 3CX - Absolutely Free!
Link up your team and customers 
Phone System Live Chat Video Conferencing
Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.
Verify your Email
Check your inbox!
We’ve sent you an email. Click on the button in the email body to verify your email address – (if you can not find it, check your spam folder).
Upon verification you will be directed to the 3CX setup wizard.