[asterisk-dev] Is externalivr really ready for "real" usage?

Steve Murphy murf at parsetree.com
Fri Feb 10 19:19:43 CST 2012


On Fri, Feb 10, 2012 at 8:15 AM, Chris Tooley <chris at tooley.com> wrote:

> I have quite a few very high volume applications using it
>

So, let me ask: you don't need to do any "say_number" or like things, or...
you have a slick way to do it...?

murf


> On Feb 10, 2012 12:14 AM, "Steve Murphy" <murf at parsetree.com> wrote:
>
>> I've been investigating turning an app I wrote into an externalIVR...
>>
>> and hitting some major roadblocks...
>>
>> For one, there is no stopstream action, for when you just want to cut off
>> the playing without
>> starting a new soundfile.... unless I guess, we start playing a silence
>> file... is that the "approved tactic"?
>>
>> Nextly, I need to use ast_say_number, ast_say_digit_str,
>> ast_say_character_str, and ast_say_phonetic_str,
>> but this is not provided at all by app_externalivr.
>>
>> I'm looking to see if such capability could be added, but... not very
>> easily, it appears...
>> The ast_say_ functions pretty much use directly ast_streamfile and
>> ast_waitstream directly to play the sounds
>> as the algorithms determine the files.... they don't merely generate a
>> list of files.
>>
>> To do that, it appears that every say routine in every language would
>> have to have a "get a list of files" version.
>> That strikes me as impractical.
>>
>> Might there be a way to turn off the play mech and use the say routines
>> instead for this kind of request? Is that
>> a possible alternative?
>>
>> Am I the only guy on earth to be trying out app_externalivr? You know,
>> the mechanisms required to write a
>> full-featured external app are not trivial. You need to create a thread
>> to collect the events from asterisk,
>> and then consume those in your main line. Some signalling from the input
>> thread to the main thread
>> is required. The simple examples provided by the literature are a far cry
>> from what the specification says is needed.
>> Anybody else working on this sort of thing?
>>
>>
>>
>> murf
>>
>>
>> --
>>
>> Steve Murphy
>>
>> ParseTree Corporation
>>
>> 57 Lane 17
>>
>> Cody, WY 82414
>>
>>murf at parsetree.com
>>
>> ☎ 307-899-5535
>>
>>
>>
>> --
>> _____________________________________________________________________
>> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>>
>> asterisk-dev mailing list
>> To UNSUBSCRIBE or update options visit:
>>   http://lists.digium.com/mailman/listinfo/asterisk-dev
>>
>
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-dev
>



-- 

Steve Murphy

ParseTree Corporation

57 Lane 17

Cody, WY 82414

✉  murf at parsetree.com

☎ 307-899-5535
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20120210/8cef2f0c/attachment.htm>


More information about the asterisk-dev mailing list