ombutel.com



  • @stuartjordan said in ombutel.com:

    I do agree with your comment about it being closed source, the interface looks nice though and it seems to have all the features available without any limitations.

    Right, and closed source is just too risky when open source options exists. If there was no open source solution available, a free closed source solution can be a very good solution. This is just not the case in the PBX market.

    We have no way to know how secure this code is from various known vulnerabilities or anything else.



  • @jaredbusch are you planning to stay with Freepbx for the foreseeable future, or are you looking at other options?



  • @stuartjordan said in ombutel.com:

    @jaredbusch are you planning to stay with Freepbx for the foreseeable future, or are you looking at other options?

    For the current time yes.

    FusionPBX is nice, but not something I would be comfortable turning up for a client and walking away from, the work would be nice, but I do not try to force a client to be dependent on us.

    Issabel is just not ready for production yet.

    Wazo is in the same state as FusionPBX. Not something I would turn a client loose on, but great for someone like us that knows PBX systems.



  • I do like FusionPBX, I didn't have any major issues with it just that the hardware phone was playing up, it looked like to be a NAT issue. although I didn't have any issues with the phone using 3CX.



  • I'm with Jared, I'm willing to look at things, but moving away from solid, dependable FreePBX is hard to do until some of these other products mature a bit.



  • What Linux distro is ombutel using?
    FreePBX is using CentOS.
    FusionPBX is using Debian.



  • @black3dynamite said in ombutel.com:

    What Linux distro is ombutel using?
    FreePBX is using CentOS.
    FusionPBX is using Debian.

    They use CentOS 7.

    0_1506705948031_ombutel.png



  • Hi,

    Ombutel is completely free without limitations, already has more than two years in production environments with excellent results, currently working on version 2.0 which will bring many surprises.



  • I took a look at the site to see if this was something I might want to poke around with but it doesn't inspire a lot of confidence when half the links on the site are dead. The website template still contains some of the "Lorem ipsum" text from the original template designer.



  • I did try it, but I’ve stayed with fusion pbx for now.



  • Hi NashBrydges:

    We agree with you, since Telesoft took full control of the Ombutel project, we have been making important improvements, one of which is the website and also the name of the project. We invite you to visit our new website (not yet finished), where you can see that the new version 2.0 of Ombutel (VitalPBX 2.0), this version will be available in December this year. vitalpbx.org



  • @rcuadra will you be incorporating different templates for various phone manufacturers like snom? I did not see these when I tried the pbx



  • @rcuadra never came back, but the project was recently rediscovered under its new name and there is a thread about it.



  • @scottalanmiller said in ombutel.com:

    I'm with Jared, I'm willing to look at things, but moving away from solid, dependable FreePBX is hard to do until some of these other products mature a bit.

    So are you saying that this is now so mature with so many features that being closed source is no longer a concern?

    Even tough it has only existed for a year and a half as a full package?



  • @JaredBusch said in ombutel.com:

    @stuartjordan said in ombutel.com:

    @jaredbusch are you planning to stay with Freepbx for the foreseeable future, or are you looking at other options?

    For the current time yes.

    FusionPBX is nice, but not something I would be comfortable turning up for a client and walking away from, the work would be nice, but I do not try to force a client to be dependent on us.

    Issabel is just not ready for production yet.

    Wazo is in the same state as FusionPBX. Not something I would turn a client loose on, but great for someone like us that knows PBX systems.

    These things all seem to be about the same as before. FreePBX doesn't seem to be moving forward in any serious way and has always been "good enough, but not impressive" and Issabel seems to have Petered out, Wazo is to nascent, FusionPBX better for a different use case. These factors seem to rule out the alternatives.



  • @JaredBusch said in ombutel.com:

    @scottalanmiller said in ombutel.com:

    I'm with Jared, I'm willing to look at things, but moving away from solid, dependable FreePBX is hard to do until some of these other products mature a bit.

    So are you saying that this is now so mature with so many features that being closed source is no longer a concern?

    Even tough it has only existed for a year and a half as a full package?

    From what we've seen of it so far, it feels so much more mature than FreePBX. FreePBX has the massive benefit of being open source, but the massive negative of having been really poorly built and not having strong refactoring changing it.

    Because of the almost stateless nature of a PBX, especially an Asterisk PBX, my concerns about maturity and longevity are pretty minor. Our ability to replace a VitalPBX instance with a FreePBX one is insanely rapid. But it seems to have enough benefits around maturity and momentum, that I am feeling pretty confident in putting it into some new production roles to really kick the tires. Not switching over anyone pre-existing except internally, but for new builds, it seems like VitalPBX is really marching forward and FreePBX is potentially mired in old code that is hard to maintain.



  • @scottalanmiller said in ombutel.com:

    @JaredBusch said in ombutel.com:

    @stuartjordan said in ombutel.com:

    @jaredbusch are you planning to stay with Freepbx for the foreseeable future, or are you looking at other options?

    For the current time yes.

    FusionPBX is nice, but not something I would be comfortable turning up for a client and walking away from, the work would be nice, but I do not try to force a client to be dependent on us.

    Issabel is just not ready for production yet.

    Wazo is in the same state as FusionPBX. Not something I would turn a client loose on, but great for someone like us that knows PBX systems.

    These things all seem to be about the same as before. FreePBX doesn't seem to be moving forward in any serious way and has always been "good enough, but not impressive" and Issabel seems to have Petered out, Wazo is to nascent, FusionPBX better for a different use case. These factors seem to rule out the alternatives.

    They certainly are. Thus the only remaining discussion is VitalPBX really that much better that you will give up Open Source for Closed Source?



  • Correct me if I'm wrong, but I believe VitalPBX is Ombutel:
    https://vitalpbx.org/en/ombutel-change-name/



  • @Skyetel said in ombutel.com:

    Correct me if I'm wrong, but I believe VitalPBX is Ombutel:
    https://vitalpbx.org/en/ombutel-change-name/

    Yes.



  • Duh - You said that above. Sorry I missed it @JaredBusch



  • @Skyetel said in ombutel.com:

    Duh - You said that above. Sorry I missed it @JaredBusch

    I"m circle the horses back to comments made almost 2 years ago. We know they are the same project. So no reason to make a new thread.

    Also @scottalanmiller you might as well add the vitalpbx tag to this thread.
    Edit: Nevermind I see it is already there.



  • @JaredBusch said in ombutel.com:

    @scottalanmiller said in ombutel.com:

    @JaredBusch said in ombutel.com:

    @stuartjordan said in ombutel.com:

    @jaredbusch are you planning to stay with Freepbx for the foreseeable future, or are you looking at other options?

    For the current time yes.

    FusionPBX is nice, but not something I would be comfortable turning up for a client and walking away from, the work would be nice, but I do not try to force a client to be dependent on us.

    Issabel is just not ready for production yet.

    Wazo is in the same state as FusionPBX. Not something I would turn a client loose on, but great for someone like us that knows PBX systems.

    These things all seem to be about the same as before. FreePBX doesn't seem to be moving forward in any serious way and has always been "good enough, but not impressive" and Issabel seems to have Petered out, Wazo is to nascent, FusionPBX better for a different use case. These factors seem to rule out the alternatives.

    They certainly are. Thus the only remaining discussion is VitalPBX really that much better that you will give up Open Source for Closed Source?

    That's how I'm feeling, yes. Open source > Closed source for sure. But good product > poor product as well. FreePBX led the pack only after all the competitors fell away. I'd love to see a quality open source alternative arise and I'd switch no question. But I don't feel that the source license in an essentially stateless product that can be trivially swapped out carries enough weight to warrant using FreePBX over VitalPBX.



  • @scottalanmiller said in ombutel.com:

    @JaredBusch said in ombutel.com:

    @scottalanmiller said in ombutel.com:

    @JaredBusch said in ombutel.com:

    @stuartjordan said in ombutel.com:

    @jaredbusch are you planning to stay with Freepbx for the foreseeable future, or are you looking at other options?

    For the current time yes.

    FusionPBX is nice, but not something I would be comfortable turning up for a client and walking away from, the work would be nice, but I do not try to force a client to be dependent on us.

    Issabel is just not ready for production yet.

    Wazo is in the same state as FusionPBX. Not something I would turn a client loose on, but great for someone like us that knows PBX systems.

    These things all seem to be about the same as before. FreePBX doesn't seem to be moving forward in any serious way and has always been "good enough, but not impressive" and Issabel seems to have Petered out, Wazo is to nascent, FusionPBX better for a different use case. These factors seem to rule out the alternatives.

    They certainly are. Thus the only remaining discussion is VitalPBX really that much better that you will give up Open Source for Closed Source?

    That's how I'm feeling, yes. Open source > Closed source for sure. But good product > poor product as well. FreePBX led the pack only after all the competitors fell away. I'd love to see a quality open source alternative arise and I'd switch no question. But I don't feel that the source license in an essentially stateless product that can be trivially swapped out carries enough weight to warrant using FreePBX over VitalPBX.

    I am surprised that there isn't more support for FusionPBX on ML. We've found it to be rock solid once you get over the learning curve.



  • @Skyetel said in ombutel.com:

    @scottalanmiller said in ombutel.com:

    @JaredBusch said in ombutel.com:

    @scottalanmiller said in ombutel.com:

    @JaredBusch said in ombutel.com:

    @stuartjordan said in ombutel.com:

    @jaredbusch are you planning to stay with Freepbx for the foreseeable future, or are you looking at other options?

    For the current time yes.

    FusionPBX is nice, but not something I would be comfortable turning up for a client and walking away from, the work would be nice, but I do not try to force a client to be dependent on us.

    Issabel is just not ready for production yet.

    Wazo is in the same state as FusionPBX. Not something I would turn a client loose on, but great for someone like us that knows PBX systems.

    These things all seem to be about the same as before. FreePBX doesn't seem to be moving forward in any serious way and has always been "good enough, but not impressive" and Issabel seems to have Petered out, Wazo is to nascent, FusionPBX better for a different use case. These factors seem to rule out the alternatives.

    They certainly are. Thus the only remaining discussion is VitalPBX really that much better that you will give up Open Source for Closed Source?

    That's how I'm feeling, yes. Open source > Closed source for sure. But good product > poor product as well. FreePBX led the pack only after all the competitors fell away. I'd love to see a quality open source alternative arise and I'd switch no question. But I don't feel that the source license in an essentially stateless product that can be trivially swapped out carries enough weight to warrant using FreePBX over VitalPBX.

    I am surprised that there isn't more support for FusionPBX. We've found it to be rock solid once you get over the learning curve.

    It is rock solid IMO. But it is better for MSP/Resellers.

    The learning curve is why I will never deploy it stand alone. I don't sell PBX service. I turn things up and hand them over most of the time.



  • @Skyetel said in ombutel.com:

    @scottalanmiller said in ombutel.com:

    @JaredBusch said in ombutel.com:

    @scottalanmiller said in ombutel.com:

    @JaredBusch said in ombutel.com:

    @stuartjordan said in ombutel.com:

    @jaredbusch are you planning to stay with Freepbx for the foreseeable future, or are you looking at other options?

    For the current time yes.

    FusionPBX is nice, but not something I would be comfortable turning up for a client and walking away from, the work would be nice, but I do not try to force a client to be dependent on us.

    Issabel is just not ready for production yet.

    Wazo is in the same state as FusionPBX. Not something I would turn a client loose on, but great for someone like us that knows PBX systems.

    These things all seem to be about the same as before. FreePBX doesn't seem to be moving forward in any serious way and has always been "good enough, but not impressive" and Issabel seems to have Petered out, Wazo is to nascent, FusionPBX better for a different use case. These factors seem to rule out the alternatives.

    They certainly are. Thus the only remaining discussion is VitalPBX really that much better that you will give up Open Source for Closed Source?

    That's how I'm feeling, yes. Open source > Closed source for sure. But good product > poor product as well. FreePBX led the pack only after all the competitors fell away. I'd love to see a quality open source alternative arise and I'd switch no question. But I don't feel that the source license in an essentially stateless product that can be trivially swapped out carries enough weight to warrant using FreePBX over VitalPBX.

    I am surprised that there isn't more support for FusionPBX on ML. We've found it to be rock solid once you get over the learning curve.

    Solidity isn't really a concern. Learning curve is. When we create these systems for customers to use, learning curve is a killer.



  • I shouldn't say that solidity isn't a concern. I meant that it is not a reason anyone here is avoiding FusionPBX. It's not that we don't assume that it is solid, we do. It's that it doesn't fit a need in the SMB space, it's not tuned for the job at hand.



  • Gotcha - thanks for the feedback 🙂


Log in to reply