Foreign language asterisk sounds

[Kilian Krause]

Lionel,

On Wed, Jun 13, 2007 at 11:02:31AM +0200, Lionel Elie Mamane wrote:
> On Wed, Jun 13, 2007 at 10:00:11AM +0200, Kilian Krause wrote:
> > On Wed, Jun 13, 2007 at 08:32:55AM +0200, Lionel Elie Mamane wrote:
> 
> >> Is there a reason (beyond nobody did it yet) we do not ship the Digium
> >> asterisk French/Spanish sounds?
> 
> > there's just nobody pushing it.
> 
> Well, now there is. There is me :)

Yes, great! ;)


> >>  - Can we presume the same license as Asterisk (or the English core
> >>    sounds), or do we want an explicit OK from Digium? In the latter
> >>    case, has anybody contacted Digium about that?
> 
> > These sounds don't technically "link" with asterisk. So their
> > license is what that speaker/upstream says it is. At least in my
> > understanding, yet IANAL.
> 
> Well, the current situation is that upstream doesn't say anything
> explicit. I mainly wanted to check nobody from Debian had already
> contacted Digium about this.


Not that I'm aware of lately. But querying for a current status won't
hurt I guess.


> >>  - Shall we include them in the repackaged upstream tarball or as
> >>    separate source packages?
> 
> > Seperate source makes more sense as the release cycles differ
> > largely.
> 
> I was speaking about the ones on
> http://ftp.digium.com/pub/telephony/sounds/; their release cycle is,
> as far as I understand, synchronised with Asterisk; there is a tarball
> for each Asterisk release in
> http://ftp.digium.com/pub/telephony/sounds/releases/ .
> 
> (Possibly the sounds haven't changed between releases, but still: same
>  release cycle, they are considered part of asterisk.)

Yes, we could put those in one large source. With repacking happening
anyway that should be ok.


> >>  - Do we want to ship all coding variants or just GSM?
> 
> > That's a bit tricky. We can ship everything except iLBC, as we
> > exclude iLBC from asterisk source and therefore wouldn't be able to
> > read it.
> 
> It wouldn't? I would have thought it could read it and stream it on
> an iLBC call, but not transcode it. Anyway, upstream doesn't
> distribute iLBC prompts, but gsm, g729, alaw, ulaw, g722, wav (RIFF
> (little-endian) data, WAVE audio, Microsoft PCM, 16 bit, mono 8000
> Hz).

I'm not sure how hard asterisk will remove iLBC, it may be possible that
reading is still fine, but I'd rather assume that I will plain forget
about this codec existing as a safe bet (at least until we have a
package-time-verification for the opposite). This would then ensure that
any subsequent release will be able to use these sounds just as the one
before.

For the recording in postinst, I don't really know what the quality
would be. If it's gonna be significantly less than what upstream
provides, having the larger packs (in a modular language per one package
approach) sounds saner to me.

-- 
Best regards,
Kilian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-voip-maintainers/attachments/20070613/25bcc856/attachment.pgp