wardmundy
Nerd Uno
- Joined
- Oct 12, 2007
- Messages
- 20,217
- Reaction score
- 5,974
Ethan,
I raised the initial concern so let me be the first to apologize if it was offensive. Those of us who develop software often get "too close" to our projects to be objective, and I'm as guilty of this as anyone. For the model you have described, i.e. the 40-person office, you're absolutely right. The rent model makes perfect sense. And it would be a tremendous addition.
For the five-person office or the two-person office, they also like bells and whistles, and that was the concern with the rental approach that I was raising. Perhaps there's another licensing model that will be a better fit for these folks.
Funny thing is that I'm wrestling with the same issues with a new fault-tolerant Asterisk setup with heartbeat. Server #1 fails and Server #2 automatically takes over. Once Server #1 is repaired, just run a little script and everything is back to being fault tolerant. Should I give it away? Should it be provided to PBX in a Flash development partners only for use with their customers? Should it work on "other" Asterisk implementations? These are tough questions... particularly when you've grown accustomed to eating.
Bottom Line: We're all working through the difficult pricing and licensing model that's at the heart of the Asterisk community. Don't be offended by questions and confusion. It's part of the territory.
I raised the initial concern so let me be the first to apologize if it was offensive. Those of us who develop software often get "too close" to our projects to be objective, and I'm as guilty of this as anyone. For the model you have described, i.e. the 40-person office, you're absolutely right. The rent model makes perfect sense. And it would be a tremendous addition.
For the five-person office or the two-person office, they also like bells and whistles, and that was the concern with the rental approach that I was raising. Perhaps there's another licensing model that will be a better fit for these folks.
Funny thing is that I'm wrestling with the same issues with a new fault-tolerant Asterisk setup with heartbeat. Server #1 fails and Server #2 automatically takes over. Once Server #1 is repaired, just run a little script and everything is back to being fault tolerant. Should I give it away? Should it be provided to PBX in a Flash development partners only for use with their customers? Should it work on "other" Asterisk implementations? These are tough questions... particularly when you've grown accustomed to eating.
Bottom Line: We're all working through the difficult pricing and licensing model that's at the heart of the Asterisk community. Don't be offended by questions and confusion. It's part of the territory.

The only reason the product has taken off at all is because they've offered $50 licenses to anyone and everyone in the Asterisk community. That's about what a license is worth in the scheme of things. They're charging FIVE TIMES that much. So the only folks that buy them are companies that want to annoy the hell out of you by not ever answering your calls. I can count them on one hand: banks, cell phone companies, insurance companies when you want to file a claim, doctors' offices, customer "service" hotlines... You get the idea.