...
In the spring of 2007, we decided to change the project structure and licensing to reduce complexity and potential usage conflicts. Pingtel made a new contribution of code to SIPfoundry based on its previous commercial version to create the sipXecs project (see the change announcement).
Many of the developers who were focused on User Agents continued with those parts of the original code base as the sipXtapi project, and that project is very much alive and well.Anchor
...
| title | The name of the project |
|---|
Note that nowhere in any of the above did the project name sipX appear. The name sipX has been used as a sort of shorthand since the beginning, but is actually ambiguous (since there are two independent projects that both use that name prefix).
...
project
...
.
Commercial sponsor history
| Section | |||||||||
|---|---|---|---|---|---|---|---|---|---|
|
In July of 2007, Pingtel was acquired by Bluesocket, which in turn sold all the assets of Pingtel to Nortel in August of 2008. Nortel had already been selling a product (Software Communications System - SCS) based on code from the sipXecs project for some time. When Nortel bought the assets of Pingtel, they also hired all of the developers from Bluesocket.
...
In March 0f 2010, Avaya stopped contributing to the source code to the community. Members of the community came together (including several of the original Pingtel employees under the company name eZuce, Inc.) and until the beginning of February 2015 maintained the sipXecs project.
Citing differences with SIPfoundry ownership, eZuce decided in February 2015 to fork sipXecs to form sipXcom. eZuce continues to improve and expand the code base.