Bayonne 0.5.23, final of the 0.5.x releases
(2001-04-22) In putting out 0.5.23 tonight, I am distributing what I hope will be the final of the 0.5.x releases of Bayonne. This release introduces both support for streaming audio thru a URL resource, and the functionality required for parsing an XML script language from a Web server thru a plugin. Plugins can now be created for multiple XML dialects, such as CallXML, XTML, VoiceXML, CPL, or whatever. The underlying mechanisms for executing an XML dialect will be thru the structure of the Bayonne script runtime engine itself.
Some changes are needed in Common C++, ccRTP, and ccAudio, before Bayonne 0.6.0 is released, and those will be started shortly after this release. Those changes include some better control of URLStream options, and ideally a put method, FTP support, and making some info available from ccAudio private members, as well as sufficient RTCP session functionality for a pure Bayonne RTP IVR driver skeleton. There may be a few aaScript XML dialect matching functions added as well.
This release also includes the brand new Bayonne manual that was created by Anders Dahnielson of the core Bayonne development team. This manual replaces all the arbitrary text files that used to be distributed with Bayonne. The manual is found in the doc subdirectory and has been partially revised for this new release.
Other changes in this release include the addition of extensive new commands for digit manipulation. This should allow one to code proper call routing tables and operations in Bayonne without having to resort to plugins. Other changes were made both to enable mapping of XML dialects into the ccScript runtime engine, and to condense the number of script steps needed for some operations.
For those looking to help with or contribute to Bayonne development, one area we need an additional contributors is in helping with the Common C++ URLStream and XMLStream classes, and to produce a valid XML parser for at least a demonstratable subset of CallXML using the XMLStream parser in a Bayonne XML plugin. We are also looking for a someone who might be brave enough to volunteer to operate, or that would be willing to contribute to support deployment of, a public access Bayonne driven XML telephony voice portal.
As usual, Bayonne and all related tarballs are distributed thru the feeder mirror, at ftp://www.voxilla.org/pub/bayonne/tarball. The latest copy of Bayonne and all related files may be found there.
From Singapore - Best New Enterprise Application - Infrastructure - Open Source Telecom - Bayonne
Based in the US, Open Source Telecom (OST) is the first and only provider of entirely free software based enterprise class telephony applications and services in the market today, including turnkey and customized solutions for enterprise messaging, voice response, customer relations management, and v-commerce solutions, based on Bayonne, the telephony server of the GNU Project, and telephony hardware running under GNU/Linux. OST believes in the vision that involves the displacement of proprietary solutions with open ones based on free software to provide telephony services and solutions, such that one is neither locked into working with specific vendors' equipment nor restricted from using and deploying telephony applications in new and creative ways.
Other information about Singapore Linux Conference may be found at http://www.slc.org.sg.
Savannah CVS and GNU Enterprise
Yes, Bayonne is now up on Savannah, the new central site for developing and distributing GNU packages. Bayonne can be found directly under http://savannah.gnu.org/projects/bayonne. We have always held primary Bayonne CVS on subversions.gnu.org, and these CVS archives can now be accessed from Savannah.
All current Bayonne contributors should register at and start using Savannah for primary CVS access. We will also start using their project management and bug tracking facilities over time. At some time in the near future BayonneDB will be split from Bayonne and maintained as a fully separate package, perhaps on Sourceforge.
Bayonne has also been selected to provide telephony infrastructure for GNU Enterprise. Bayonne, and some other parts of GNUCOMM, such as TOSI, will be used to help bring full telephony integration to GNU Enterprise as a whole. Bayonne and TOSI essentially replace the proposed EWOKS system originally started by the GNU Enterprise project. See gnue.org for more details.
We have recently distributed an initial release of "bayonnedb" along with Bayonne 0.5.16. "bayonnedb" is a new and very compact plugin driven threaded database transaction monitor that will ultimately be usable in several telephony projects, including Bayonne, and pre-viking.
While this initial release covers proof of architecture and a simple CDR example, bayonnedb will grow to cover a vast range of database services to support multiple Bayonne and pre-viking servers. BayonneDB will also offer centralized coordination for clusters of Bayonne servers such as to implement "Agent Queue Service" for distributed ACD functionality. BayonneDB will also offer centralized collection point for call statistics and reporting.
BayonneDB, like Bayonne, uses C++ base classes held in the server and plugins which implement these classes. Plugins include a "service" interface which provides generic logic for a service, and a backend "database" driver which implements a given service for a particular database backend. This initial public release offers an example CDR service with an example PostgreSQL backend.
By using plugin architecture, one can select and deploy only those specific BayonneDB services one wishes to run rather than loading a massive monolithic image. By using threading, BayonneDB is able to execute parallel queries and provide optimized performance when hosted on SMP servers.
BayonneDB is available for immediate download from ftp://www.voxilla.org/pub/bayonnedb. Like Bayonne, BayonneDB is based on Common C++. RPM's are also available.
BayonneDB is the second of three components that have been identified for implementing enterprise and carrier level GNU telephony services as part of GNUCOMM. The third is Babylon, which will be a plugin based PBX monitor/protocol integration platform. Babylon will be introduced a little later this year.