bcmike
New Member
- Joined
- Aug 15, 2008
- Messages
- 17
- Reaction score
- 8
Hi Ward,
I've been around since the Asterisk Management Portal days. We then found Asterisk@home, moved to Trixbox, and finally have been happy users of PBIAF for a lot of years.
It looks like PBIAF is now entering its Trixbox phase. Oh well it was a good run...
Unfortunately you're basically doing away with every reason we moved to PBIAF, here's the list:
I do have one final request, and its humbly on bended knee; can you maintain the old PBIAF repositories or make them downloadable for offline use. PBIAF even in its older incarnations is still one of the strongest, most reliable offerings ever made available to the world of telecom and it'd be a shame if we couldn't still use it.
Your biggest fan,
Mike
I've been around since the Asterisk Management Portal days. We then found Asterisk@home, moved to Trixbox, and finally have been happy users of PBIAF for a lot of years.
It looks like PBIAF is now entering its Trixbox phase. Oh well it was a good run...
Unfortunately you're basically doing away with every reason we moved to PBIAF, here's the list:
- Based on open source products with a healthy and vibrant community. You can say what you want about the 3CX community it doesn't come close to Asterisk/FreePBX/PBIAF. With such a wide base of support it wasn't hard to find someone having the same problem you were. I don't even know what runs 3CX, or what its evolution has been, and frankly a native Windows telecom product seems suspect.
- The Centos/RHEL environment. It's what we have become accustom too and has preformed like a rock for many years. Again Debian may be a great platform but if its not broke why are we fixing it? Are we simply accommodating 3CX? Whats the track record with 3CX in Linux? As long as Asterisk? Probably not..
- Compile from source scripts and version continuity. I always loved all the hardwork you guys put into the install and upgrade scripts that allowed us to compile from source. We could keep all the versioning straight and still add run time options, etc. It made for a super stable asterisk environment and kept us safe from RPM hell. I guess those days are gone and we will mourn them.
- Flexibility. We could always add our own scripts, get ideas from other people, make small improvements and in short do really creative things with PBIAF. Entering the 3CX walled garden essentially ends that. Giving 3CX credit they have a lot of great shiny polished stuff that's exciting, but at the end of the day its their stuff, branded with their logos, with them adding value as opposed to us.
- Lean mean PBX machine. The differentiator between incredible PBX and PBIAF was that it was a core engine without the bells and whistles, which made it super stable and an awesome platform. Again 3CX is not that. Its all things to all people and in my opinion that's not PBIAF
- Sacalability. Can you scale 3CX to a 1000 concurrent calls? I'm not sure. Can you set up a geo redundant 3CX cluster? I don't know. If it is possible do I need to license windows to run it all in those modes?
I do have one final request, and its humbly on bended knee; can you maintain the old PBIAF repositories or make them downloadable for offline use. PBIAF even in its older incarnations is still one of the strongest, most reliable offerings ever made available to the world of telecom and it'd be a shame if we couldn't still use it.
Your biggest fan,
Mike
Last edited:

Maybe a picture will help clarify where things stand since you seem to have considerable difficulty reading.