You might want to take a look at OpenSBC hosted in http://www.opensipstack.org as well.
Daniel Corbe wrote: > Greetings SIP Implementers, > > I and a small team of developers are working towards implementing an > Open Source SIP B2BUA. We're basically looking for a community of > fellow SIP implementors, telecom companies, network operators, > carriers and general VOIP enthusiasts to interact with and bounce > questions off of. > > The reasons we have taken on this project are as follows > > 1) While there's a wealth of Free and Open Source Software available > -- especially in the VOIP arena -- we feel that not nearly enough of > it is geared towards network operators and carriers. > > 2) Between us, we have a wealth of operational experience within the > carrier space and haven't been able to find an existing open source > project which is as comprehensive as we would like it to be. Our > goal as network operators will be to completely replace commercial > Session Border Controllers and routing engines. > > Our current project goals include > > 1) A ground-up re-implementation of SIP and various protocol > extensions and drafts. We chose this route because we had a > difficult time finding an OSS SIP stack which met our choice > language, scalability, speed and licensing requirements. > > 2) We want to be able to statefully process 1000 CPS on commodity > hardware without media anchoring > > 3) We are embedding a TCL interpreter and exposing most of the > project core and some database access to it. The goal is to provide > the network operator with a way to alter SIP messages as they pass > through the server and to do things which the core shouldn't be > attempting to do (like LNP DIPs and route selection). We will author > and release some useful TCL scripts to do some of this stuff. > > 4) We're designing OpenB2BUA to be used in conjunction with existing > open source projects to implement Class-5 feature sets, such as > Unified Messaging (asterisk), SIP Registrar & Presence (SER./ > OpenSER), and Media Anchoring (rtpproxy). > > 5) OpenB2BUA will use the RADIUS protocol to conduct all Digest > authorization and billing. We're also releasing an OSS billing > engine as a companion to OpenB2BUA. > > 6) Full stateful fail-over. If you lose an OpenB2BUA box another one > takes over and your calls stay on-line. > > If anyone is interested in more information, feel free to contact me > until we get our websites set up. > > Regards, > Daniel > > > > _______________________________________________ > Sip-implementors mailing list > [email protected] > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > > > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
