[Voip-select] A question of distros for delivery of prepacked solutions

Kilian Krause kilian at debian.org
Tue Jan 3 00:06:18 UTC 2006


Hi David,

> Perhaps very late this year I plan to deliver some complete prepacked 
> solutions, and I am curious what kinds of solutions and which distro 
> people would suggest to see such solutions delivered under.  I 
> particularly like the idea of supporting a instant "voice application 
> service provider out of a box" type solution with a future BayonneXML 
> server bundled with ser (or maybe partysip), as well as very specific 
> service provider solutions built around a traditional Bayonne server and 
> ser, or that uses Bayonne with traditional CTI hardware, or bundled with 
> a preconfigured gnugk for H.323 deployments.  Another possibility is a 
> complete bundled appserver/callserver/gateway telephone system.
> 
>  From an organizational point of view, it would make sense to use Debian
> (3.1) for these things and setup an appropriate Debian repository for
> Bayonne and other components.  I prefer to setup and use Debian in part
> because it has an intelligent deployment model, unlike the typical
> multi-cd rpm distro.  However my own experience is far more complete
> with packaging...

sorry for not have answered to this before, but I just happened to come
across this posting while looking up your email. The idea to ship
bayonne with Debian is probably a very good idea which should be
supported as good as can. However, with the latest stable release of
Bayonne 1.2.15 we do encounter *a lot* of problems on archs !i386 at the
moment. You can check
http://buildd.debian.org/build.php?arch=&pkg=bayonne where all the
buildlogs are archived. A brief insight has brought me to believe this
is due to the integral overlapping of server daemon and server library
code. Probably this needs to be cleaned up to comply with libtool in a
sane way and build libs as library code (through libtool) and the server
as application code like now. 

Are you aware of any patches that do this cleanup already or is there a
1.2.16 release in the pipeline which would address this?

Thanks for your answer and happy new year!

-- 
Best regards,
 Kilian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
Url : http://lists.alioth.debian.org/pipermail/pkg-voip-maintainers/attachments/20060103/c72777d8/attachment.pgp


More information about the Pkg-voip-maintainers mailing list