You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Flite and PocketSphinx are the only TTS and ASR engines available at zero cost for use with Asterisk via MRCP. They are supported via plugins to UniMRCP server and are installed on Telephony Dev Box.
Unfortunately Flite does not support SSML (plain text only) and PocketSphinx supports only JSGF grammars, not SRGS.
Changes required
Plain text content of an SSML document must be extracted here
Since Punchblock nor the UniMRCP client do not know what formats an engine supports prior to submitting a request to them, it would seem sensible for these manipulations to be implemented in the UniMRCP Server plugins such that they are transparent to the client side. These manipulations could be implemented using cspeech once it's ready.
Application impact
None.
The text was updated successfully, but these errors were encountered:
Sounds entirely reasonable to me. I don't know how much work the JSGF->SRGS conversion would be, or how perfectly the capabilities overlap. Stripping SSML seems easy enough. I do like that we'll have an entry-level ASR+TTS option on Asterisk.
Motivation
Flite and PocketSphinx are the only TTS and ASR engines available at zero cost for use with Asterisk via MRCP. They are supported via plugins to UniMRCP server and are installed on Telephony Dev Box.
Unfortunately Flite does not support SSML (plain text only) and PocketSphinx supports only JSGF grammars, not SRGS.
Changes required
Since Punchblock nor the UniMRCP client do not know what formats an engine supports prior to submitting a request to them, it would seem sensible for these manipulations to be implemented in the UniMRCP Server plugins such that they are transparent to the client side. These manipulations could be implemented using cspeech once it's ready.
Application impact
None.
The text was updated successfully, but these errors were encountered: