asterisk and mysql_cdr

[Tzafrir Cohen]

On Sat, Feb 26, 2005 at 04:31:40PM +0100, Kilian Krause wrote:

> thanks for the pointer. Yet it's to be said that H323 support was
> *completely* removed from asterisk recently and replaced by the new
> source asterisk-oh323. 

That still depends on libopenh323

> Thus the asterisk source and its debs do not link
> with OpenH323 at all, the entire H323 support is derived from installing
> asterisk-oh323 (which unfortunatelly is still stuck in NEW). 

But if you install asterisk-oh323 and load that module to asterisk you
link asterisk with libopenh323.

> Moreover
> the source of asterisk-addons will bring their own packages which again
> reside all within the GPL domain as far as i have checked. I am still
> wondering if this is better to be shipped within the asterisk source as
> patch or as extra source.

So it is basically illegal to load both res_perl (from addons) and
asterisk-oh323 . Even today it is possible to add a conflict between
asterisk-h323 (had it not been dumped) and any such problematic package.

I don't see why te fact that the h323 module came from a different
source package matters.

> 
> Now the only problem (if any) is the fact that the asterisk source does
> technically offer linking with OpenH323 (yet another version than is in
> the archive). If a user does do that from a debian source to my
> understanding that is no problem of Debian providing that source in the
> first place. However that's nothing Debian-specific, but that's by the
> upstream source. If this poses a problem, we can just force the source
> to ship without chan_h323 easily, like we now do with the Music-on-Hold
> files.
>

-- 
Tzafrir Cohen     icq#16849755  +972-50-7952406
tzafrir.cohen@xorcom.com  http://www.xorcom.com