--- Scott Lawrence <[EMAIL PROTECTED]> wrote:
...
> 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".
>
Lets be perfectly clear here. The maintainers of sipXportLib,
sipXtackLib, sipXsdpLib, sipXmediaLib, sipXmediaAdapterLib, sipXcallLib
(including sipXtapi and the user agent functionality) had nothing to do
with this yet another fork of the sipX project. Nor did these
maintainers encourage the fork between the main and sipXtapi. This is
a Pingtel spondored fork of the sipX project for Pingtel business
reasons. In fact SIPez has spend considerable time and money in trying
to put the main and sipXtapi fork back together.
The main and sipXtapi branch of the sipX project is an open branch
willing to take contributions under a LGPL license with a fair and
equal basis without the contributor yielding copyright.
SIPez LLC
SIP VoIP, IM and Presence Consulting
http://www.sipez.com
tel: +1 (617) 273-4000
_______________________________________________
sipxtapi-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
