[asterisk-dev] [Code Review] app_swift - streaming text-to-speech interface for the Cepstral Swift engine

[Darren Sessions]

> On 2010-06-03 13:44:39, pabelanger wrote:
> > /trunk/apps/app_swift.c, lines 318-321
> > <https://reviewboard.asterisk.org/r/691/diff/1/?file=10562#file10562line318>
> >
> >     It seems you are defaulting to ulaw, is there a reason?  What if the user had gsm, or alaw? Does the engine support SLN?

I just tried using GSM with xlite (forcing it on the sip peer in Asterisk and making it the sole codec in xlite) and it worked just fine.

I'll check into the sln.


- Darren


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviewboard.asterisk.org/r/691/#review2141
-----------------------------------------------------------


On 2010-06-03 12:34:47, Darren Sessions wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviewboard.asterisk.org/r/691/
> -----------------------------------------------------------
> 
> (Updated 2010-06-03 12:34:47)
> 
> 
> Review request for Asterisk Developers.
> 
> 
> Summary
> -------
> 
> app_swift uses the Cepstral text-to-speech engine and copies audio frames straight from the Cepstral libs to the call channel which avoids the need to write the generated audio to a file first and then read it. Additionally, DTMF recognition code was integrated into the module to prevent delays in previous usage scenarios where the app was called and dtmf listened for afterward.
> 
> 
> Diffs
> -----
> 
>   /trunk/apps/app_swift.c PRE-CREATION 
>   /trunk/autoconf/ast_ext_lib.m4 266734 
>   /trunk/build_tools/menuselect-deps.in 266734 
>   /trunk/configs/swift.conf.sample PRE-CREATION 
>   /trunk/configure.ac 266828 
>   /trunk/include/asterisk/autoconfig.h.in 266828 
>   /trunk/makeopts.in 266734 
> 
> Diff: https://reviewboard.asterisk.org/r/691/diff
> 
> 
> Testing
> -------
> 
> I've built against trunk successfully now (thanks to Tilghman for getting the build tweaks squared away) without any errors and made dozens of test calls using different usage scenarios.
> 
> 
> Thanks,
> 
> Darren
> 
>