Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Organization: SipXecs Forum In-Reply-To: <CAAHujP6yyGWXFCF7q+FK9r+9G0gri=4_yinac_2tjezsecv...@mail.gmail.com> X-FUDforum: 08063afcdd00a6e76393c5b9527381e8 <66153> Message-ID: <10269.4f3df...@forum.sipfoundry.org>
Mike, I would like to see a list of what documentation eZuce has, what cost would be associated with getting access to that documentation, and what the differences between OpenUC and sipXecs community are. Should I contact you off-list for that information? The problem with paying upfront for documentation and OpenUC is we would need to be sure it's going to work for us. If we want to test some scenarios in a lab to make sure it will work for our situation without paying for support, we're stuck with the community documentation. Depending on what that cost is, it may not even be an issue. My point about the Zenoss reference (which people not familiar with Zenoss would probably not get) was that the administration guide for Zenoss Core is available to the community but created/updated by Zenoss. I just think it's difficult for the community documentation to stay current without some commercial backing. People are usually crunched for time and when they solve a problem, they put off documenting it and eventually forget about it. Thanks, Nate _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
