[Olympus developers 448]: Re: how to integrate olympus/ravenclaw with asterisk - multi user

[Aasish Pappu]

For a telephone interface, you could use a softswitch like freeswitch that
supports multiple sessions (default is 1000) and protocols to communicate
with an application.

We have tried to provide a preliminary interface between the audioserver
component and the freeswitch server. There's a tarball that you can start
from. The freeswitch application writes incoming audio data to a named-pipe
for every new session. This audio data is read by an instance of
audioserver component and forwarded to the recognizer (pocketsphinx).

http://www.speech.cs.cmu.edu/apappu/pubdl/fs-dialog-interface.tar.gz

There is an example application (with example configuration) in the
tarball. It also includes customized audioserver and the pocketsphinx
engine. If you want to rest of the olympus components, you have to figure
out how they will interact with the freeswitch application.


On Sat, Feb 8, 2014 at 1:53 PM, Nitin Dhawan
<nitin at imarketingadvantage.com>wrote:

> We want to make the system available on the pstn phone system. We have
> setup asterisk and can route the calls on extensions. The question is
>
> a.       How to integrate this with the dialog system. This is regularly
> done with systems like Roomline, but the instructions are not very clear.
> Here is someone talking about it
> http://www.cs.cmu.edu/~jsherwan/research/asterisk.ppt  but its not quite
> clear
>
> b.      How to enable multiple people to connect simultaneously over
> telephony. I already asked how to enable multiple simultaneous sessions,
> but the answer looks quite complicated and non-standard. It's hard to
> believe how any commercial systems would be implemented on Ravenclaw
> without multi session support being a standard feature.
>
>
>
> Please help .
>
>
>
> We are investing serious efforts in integrating Ravenclaw architecture in
> our system with the belief that this is one of the best systems around.
>
>
>
> Regards
>



-- 
Aasish Pappu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.srv.cs.cmu.edu/pipermail/olympus-developers/attachments/20140208/ba73950a/attachment.html>