| < Previous by Date | Date Index | Next by Date > |
| < Previous in Thread | Thread Index | Next in Thread > |
hI,
How much expense would it be or setting up of 10 line IP PBX using SIPpbx application.
How we can calculate the details.
Best regards,
From: Scott Lawrence <slawrence@xxxxxxxxxxx>
To: sipX users <sipx-users@xxxxxxxxxxxxxxxxxxx>, sipX developers <sipx-dev@xxxxxxxxxxxxxxxxxxx>
CC: announce@xxxxxxxxxxxxxxxxxxx
Subject: [sipX-dev] New sipXecs Project Launched,Major Upgrade to the sipXpbx Project
Date: Sat, 14 Apr 2007 11:09:18 -0400
MIME-Version: 1.0
Received: from lambda.sipfoundry.org ([72.232.205.74]) by bay0-mc10-f17.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2668); Sat, 14 Apr 2007 08:15:56 -0700
Received: from lambda.sipfoundry.org (localhost.layeredtech.com [127.0.0.1])by lambda.sipfoundry.org (8.13.8/8.13.8) with ESMTP id l3EF9Ojt034876;Sat, 14 Apr 2007 10:09:37 -0500 (CDT)(envelope-from sipx-dev-bounces@xxxxxxxxxxxxxxxxxxx)
Received: from mail.pingtel.com (hide.pingtel.com [65.220.123.2])by lambda.sipfoundry.org (8.13.8/8.13.8) with ESMTP id l3EF9IQr034865; Sat, 14 Apr 2007 10:09:22 -0500 (CDT)(envelope-from slawrence@xxxxxxxxxxx)
Received: from [127.0.0.1] (pi.pingtel.com [10.1.1.12])by mail.pingtel.com (Postfix) with ESMTP id A83356C017;Sat, 14 Apr 2007 11:08:52 -0400 (EDT)
Effective today, the maintainers of the sipXpbx project and Pingtel Corp. have launched sipXecs, a successor to the sipXpbx project, which represents a major upgrade to the sipX family and includes features and functionality not previously available in sipXpbx. 'ecs' stands for "Enterprise Communication System", which reflects the fact that sipX is now much more than just a phone system (pronounce the new name 'sip-eks-ee-see-es' or 'sip-eks-eks').
The launch of the sipXecs project continues and expands our commitment to providing the best possible open source SIP standard communications solution to the industry community. First, with sipXecs, Pingtel Corp. is releasing into open source important new features not available in sipXpbx, including the SIPxchange ACD call center solution, a new unified presence server, an improved authorization proxy, and extensive bug fixes.
Secondly, sipXecs consolidates all the underlying project components (sipXtacklib, sipXportlib, etc.) into one cohesive project making the software easier to use, and eliminating the chance for individual components to diverge.
Finally, the sipXecs project fully clarifies the relationship between the client side projects at SIPfoundry (namely the sipXtapi project), and the server side components (namely sipXpbx). Given increasingly different needs for the respective applications, the maintainers decided to create two independent and easy to use projects from the "ground up".
sipXecs project communications will remain on the sipx-users and sipx-dev mailing list, and Jira will be used for project issue tracking. sipXecs appears as a new project in Jira. Anyone with a current account can access sipXecs. The maintainers will copy all outstanding issues from sipXpbx into the new sipXecs project. If something is missed please post to the list.
The launch of sipXecs represents a major milestone for the sipX projects that reflects both the maturity and the growing use of the software by enterprises and institutions worldwide. We hope that you find sipXecs to be useful. For more information please see the FAQ below and SIPfoundry, or post questions and comments to this list.
What happens to the sipXpbx binaries and source code that I have been using?
Nothing. sipXpbx will remain available to users and developers. However, the maintainers and Pingtel Corp. will concentrate on sipXecs, so users should consider moving to sipXecs to stay current with the project.
How difficult will it be to migrate a system to sipXecs from sipXpbx?
It will be no more difficult to migrate to sipXecs than to upgrade to a new version of sipXpbx. As practical matter, users will see no real changes to system operation, but users will have access to new features and sipXecs is a more stable and robust than sipXpbx. For a list of current and planned sipXecs features see the project roadmap.
Will the mailing list change?
The sipx-users and sip-dev mailing list are not changing. There is a new list (sipxecs-commit@xxxxxxxxxxxxxxxxxxx) for the commit messages and issue updates; all subscriptions to sipx-commit have been copied to the new commit list.
Will the bug tracker change?
A sipXecs project has been added to Jira. Anyone with a current Jira account can access the sipXecs project. The sipXecs tracker consolidates all of the separate Jira components into one, except for sipXconfig, which remains in its existing project. The project maintainers are copying all outstanding issues from sipXpbx into the sipXecs project. If something is missed please post to the list.
Where do I find the most recent binaries and builds?
For stable releases see http://sipxecs.sipfoundry.org/pub
For development builds see http://sipxecs.sipfoundry.org/temp
Note that it may take a few days for builds to start appearing as the build systems change over to the new repository and upload to the new server. If you have any problems, post to the list.
This change also means that we will stop building binaries for the old sipXpbx project (both nightly builds as well as new stable releases).
Where is the source and how do I upgrade my working copy?
The sipXecs subversion repository is at:If you have questions or comments please post!
http://sipxecs.sipfoundry.org/rep/sipXecs
We recommend doing a fresh checkout of sipXecs. It is straightforward to use 'svn diff' and 'patch -p0' to move any changes from an existing sipX working copy to the new working copy (ask on the sipx-dev list if you need help).
Commit access requires approval from the project maintainers and a signed Contributor Agreement. The sipXecs project uses a new Contributor Agreement that adds assignment of a joint copyright to Pingtel. There are many other open source projects that operate this way; some call this model 'shared copyright', some use 'joint copyright', but it's the same thing.
All contributors retain the full copyright of their contributions.
All contributions accepted under the Contributor Agreement become part of the sipXecs open source project.
Scott Lawrence Chief Technology Officer
Pingtel Corporation
Enterprise-Grade, Real Time Communications Solutions
www.Pingtel.com
sip:slawrence@xxxxxxxxxxx
tel:+1.781.938.5306;ext=162
sipXecs Project Coordinator
www.SIPfoundry.org
<< sipfoundry.gif >> << pingtel.jpg >>_______________________________________________
sipx-dev mailing list
sipx-dev@xxxxxxxxxxxxxxxxxxx
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev