Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Organization: SipXecs Forum In-Reply-To: <[email protected]> X-FUDforum: 08063afcdd00a6e76393c5b9527381e8 <66184> Message-ID: <[email protected]>
Tim Ingalls wrote on Fri, 17 February 2012 14:05 > -Training and docs as well as support are available very > similar to e.g. Cisco as mentioned below, but as part of > the commercial edition > > OK. But consider the fact that organic growth can be > fueled by the open-source version. You will never get > certain customers, because they don't need you. But in > great numbers, they can provide market assurance that your > solution rocks. The closer you get to mass adoption, the > greater the perception that your commercial offerings > rock. But you won't get to mass adoption (like Asterisk > and it's variants have achieved) if > nerdy-but-not-that-nerdy people like me can't understand > quickly how to deploy sipXecs with ITSP SIP trunking. So > it furthers your goals to make all of that documentation > public. Great documentation = great mindshare. I tend to agree with Tim, and was going to post almost the same thing, but he said it better than I would have. Would eZuce be losing customers by making their BASIC documentation available to the community? If yes, then is there a way for SMBs or startups to purchase access to their documentation? Tony Graziano wrote on Fri, 17 February 2012 14:15 > I don't think any of the responses to you have been > unprofessional, > that was uncalled for. > > I'll encourage anyone reading this thread to ignore the > poster until > (if) he musters up some civility. I'm sorry but I was also thinking the comment was offensive and unprofessional. Although I'm very impressed that the CEO is active on a discussion such as this, I would not expect to hear a comment like that. _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
