I would think that there are many eZuce resellers that are jumping on the opportunity to show the difference between the open source solution and the eZuce solution after these questions. It's a great sales opportunity for eZuce resellers, to show how they differentiate that product from other products, include sipXecs.
And I would suspect they have a resource for showing that difference. If you aren't being contacted by someone, I'd reach out on the list and ask who is a reseller so they can contact you. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Burleigh, Matt Sent: Friday, February 17, 2012 11:30 AM To: Discussion list for users of sipXecs software Subject: Re: [sipx-users] sipXecs Commercial Feasibility I too would like to see a side by side comparison of the current OpenUC offering versus SipXECS 4.4. We migrated from an old ShoreTel v6 system to a SipXECS 4.2-4.4 system about 8 months ago. We're small with about 30 users, do lots of conferencing and only a dozen hard phones, a mix of Polycom phones, IP 500(actually branded ShoreLine and were MGCP), IP 6000s, IP 335s and also a dozen Bria 3 softphones. Using a dedicated FreeSwitch server with a Digium PRI card as our primary gateway(I hope to integrate this PRI card directly into sipx server at some point). I agree that diagnosing anything is more than painful but overall were pretty happy with the results so far. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Nate Sent: Friday, February 17, 2012 1:36 AM To: [email protected] Subject: Re: [sipx-users] sipXecs Commercial Feasibility 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: <[email protected]> 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 [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/ _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/ _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
