Looking at the analog gateways, DEC/SIP, and now possibly some wifi phones (suddenly technology is appealing... go figure).
Thanks for everyone's input! On Fri, Apr 1, 2011 at 8:24 AM, Michael Picher <mpic...@gmail.com> wrote: > this all is a little off topic... > > this guy has 2 phone lines and just needs a couple of cheap analog phones > on them... > > get a couple gateways and be done with it... in an environment like he's > putting it in, keep it simple stu.... > > > > > On Wed, Mar 30, 2011 at 8:36 PM, Josh M. Patten > <jpat...@co.brazos.tx.us>wrote: > >> You know I used to be a very active member of the trixbox community and >> when I finally decided to leave it (about 3 months ago) I hadn't seen a >> developer post in a really long time. >> >> It really is up to your preference what kind of open source PBX you decide >> to start with. If you're familiar with Asterisk and would like a GUI on top >> of it that can manage most of the operations of the system and you don't >> need a redundant system or complete phone provisioning, then a FreePBX >> system such as trixbox or Elastix is probably what you should use. >> >> If you want a system that has seamless integration of all components in a >> clean UI and need some level of redundancy then sipX is more logical. >> >> If you want a system where the documentation is maintained by 1 or more >> paid professional technical writers and if you find it all "too hard to >> learn" contact a VAR to install a Cisco CallManager system. >> >> NO system is without gotchas and bugs. sipX moves at a very fast pace and >> is a very complex piece of software so there will always be bugs or >> workarounds and the documentation doesn't always keep up with changes to the >> system. The fortunate thing about this project is that the developers are >> almost always watching this list and if you've done your due diligence to >> craft a mailing list post that details the problem you're having with >> information that can help the developers, such as a snapshot, then there is >> usually a fix available or something that can be done to work around your >> problem, and if not you can file a bug report in the tracker that details >> the problem so the developers can work on it. >> >> Or, if you're feeling adventurous you could help straighten out the >> documentation by requesting rights to modify the wiki or even help with the >> development of the project to help it suit your needs. Get involved in the >> project and contribute what you can, when you can and you'll find that >> you'll become a lot more familiar with sipX and understand why the system is >> designed the way it is. >> >> In the world of open source software that costs nothing to download and >> use, filing complaints gets nothing accomplished and serves no other purpose >> than to discourage and enrage those that do contribute. Making constructive >> suggestions and feature requests (which you did do to a small degree) goes a >> lot further. Actually helping make those suggestions and feature requests a >> reality by contributing to the project is what open source is all about. >> >> >> ------------------------------ >> *From:* sipx-users-boun...@list.sipfoundry.org [ >> sipx-users-boun...@list.sipfoundry.org] on behalf of Tim Ingalls [ >> t...@sharedcom.net] >> *Sent:* Wednesday, March 30, 2011 4:27 PM >> *To:* Discussion list for users of sipXecs software >> *Subject:* Re: [sipx-users] Suggestions? sipX or not, and if not... >> >> >> Michael Scheidell wrote: >> >> On 3/30/11 11:27 AM, Tim Ingalls wrote: >> >> Bluebox would be an improvement over Trixbox since its not using Asterisk >> as the back-end. >> >> except BB is not freepbx+ >> >> I'm not sure what you mean. FreePBX is a front-end for Asterisk. When >> they started to make FreePBX 4.0, they did it only for FreeSwitch, and they >> renamed that project to Bluebox. So it's pretty much FreePBX for Freeswitch. >> >> instead of a user friendly gui (BB) for a phone system/pbx, its a GUI to >> help you edit freeswitch xml files .. >> there is a difference. >> >> I'm not really seeing what the difference is. I found FreePBX an easier >> GUI than sipXconfig. The Bluebox GUI doesn't look that different. I had >> Trixbox set up in a week, but I'm still finding inconsistencies and glitches >> with sipX that cause me problems 4 months into it. The sipX project has poor >> documentation on the wiki that conflicts with itself in several places, is >> out of date, or is incomplete. Supposedly the sipX book is the best way to >> learn the system, but from my reading, it seems out of date and limited in >> the details of how to set things up. The Web site has false statements about >> the features sipX has (i.e., how redundant is HA mode, the fact that media >> does in fact use the server in sipXbridge, etc.) >> >> I'm not trying to be a sipX hater, but it's definitely not an easy system >> to learn and install if you are a newbie to the project. There seem to be >> surprises around every corner. There is so much you don't understand if >> you're new to sipXecs that you won't find out until you wade through 6+ >> months of sipx-user discussion list posts for the most common issues. >> >> I don't really see sipXecs as the best server for a small business to use. >> It's too hard to learn and get right. Maybe if the learning curve were less >> steep and the main bugs and limitations were communicated up front better, >> someone getting involved in the project wouldn't get so frustrated. Some >> instructional videos and tutorials would go a long way. Having a real user >> forum (instead of a mailing list that also gets posted to the Web) that is >> monitored by a commercial entity (like Trixbox is) would also have a big >> impact, because it would be easier for newbies to ask questions and search >> for answers. >> >> >> support is only via IRC (if the single developer is on) >> >> good support when you get him, but unless you are a freeswitch expert, >> don't try it. >> >> >> I haven't actually installed Bluebox (I'm doing it today), so I'll have >> to trust you on the support issues. >> >> >> -- >> Michael Scheidell, CTO >> o: 561-999-5000 >> d: 561-948-2259 >> ISN: 1259*1300 >> > *| *SECNAP Network Security Corporation >> >> - Best Intrusion Prevention Product, Networks Product Guide >> - Certified SNORT Integrator >> - Hot Company Award, World Executive Alliance >> - Best in Email Security, 2010 Network Products Guide >> - King of Spam Filters, SC Magazine >> >> >> ------------------------------ >> >> This email has been scanned and certified safe by SpammerTrap®. >> For Information please see http://www.secnap.com/products/spammertrap/ >> ------------------------------ >> >> ------------------------------ >> >> _______________________________________________ >> sipx-users mailing listsipx-us...@list.sipfoundry.org >> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >> >> >> _______________________________________________ >> sipx-users mailing list >> sipx-users@list.sipfoundry.org >> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >> > > > > -- > There are 10 kinds of people in this world, those who understand binary and > those who don't. > > mpic...@gmail.com > blog: http://www.sipxecs.info > call: sip:mpic...@sipxecs.info > > _______________________________________________ > sipx-users mailing list > sipx-users@list.sipfoundry.org > List Archive: http://list.sipfoundry.org/archive/sipx-users/ >
_______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
