< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index  

Re: [reSIProcate] relation resiprocate and sipx/vocal


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On Jun 29, 2004, at 03:43, martin.van.den.berg@xxxxxxxxxxx wrote:


Just curious: how are sipX and Vovida's VOCAL related to resiprocate?


I'll take a stab and answering this. :-) Corrections welcome.

Around 2 years ago, some people got together to write a C++ SIP stack
that was supposed to be a clean slate 3261-based design. This lead to
vocal2 (or was it sip2), hosted within the VOCAL project.

One thing led to another and the project left the VOVIDA SCM umbrella
and was reborn (exported?) at www.resiprocate.org using sourceforge's
project tools, but independent SCM (CVS).

Time passed and PingTel announced their Open Source initiative, inviting
other VoIP (and specifically SIP) related projects to participate.
The reSIProcate team decided that we were keen to increase our visibility and are happy to be a part of the SipFoundry -- as a separate project under
the SipFoundry umbrella.

In short -- SipX is completely separate from reSIProcate. But we are part
of the same code management and project infrastructure at SipFoundry.

Once upon a time -- reSIProcate was hosted within the VOCAL project, but
it has never shared any core design with the VOCAL code-base.


Alan Hawrylyshen
reSIProcate Project Administrator
http://sipfoundry.org/reSIProcate/
a l a n a t j a s o m i d o t c o m
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iD8DBQFA4aB92t1B785xGCgRAjZaAJ97IIbenpEVriOrv/SVRhyxfnt+JACfQVNg
3s9382kn82lCj8fXBoVqqL4=
=+LJr
-----END PGP SIGNATURE-----