On Fri, Mar 5, 2021 at 4:41 AM Lewis Bergman <lewis.bergman@gmail.com> wrote:
That was exactly it for the record. #which text2wave # <-- before apt-get install festival #which text2wave /usr/bin/text2wave # echo 'This is an example of using tts_commandline' | text2wave -f 8000 > test.wav # file test.wav test.wav: RIFF (little-endian) data, WAVE audio, Microsoft PCM, 16 bit, mono 8000 Hz # ls -l test.wav -rw-r--r-- 1 root root 60208 Mar 4 06:44 test.wav And the freeswitch debug log that shows it works: EXECUTE [depth=0] sofia/internal/102@66.151.243.45 speak(tts_commandline|text2wave|This is an example of using tts_commandline) 2021-03-04 06:59:14.305216 [DEBUG] switch_ivr_play_say.c:3023 OPEN TTS tts_commandline 2021-03-04 06:59:14.305216 [DEBUG] switch_ivr_play_say.c:3033 Raw Codec Activated 2021-03-04 06:59:14.305216 [DEBUG] mod_tts_commandline.c:160 Executing: echo 'This is an example of using tts_commandline' | text2wave -f 8000 > '/tmp/05e71313-2a4d-48ce-a1e9-84600859112f.tmp.wav' 2021-03-04 06:59:15.545212 [DEBUG] switch_ivr_play_say.c:2741 Speaking text: This is an example of using tts_commandline 2021-03-04 06:59:15.545212 [DEBUG] sofia.c:7326 Channel sofia/internal/102@66.151.243.45 entering state [ready][200] 2021-03-04 06:59:15.565210 [DEBUG] switch_rtp.c:7759 Correct audio ip/port confirmed. 2021-03-04 06:59:19.305225 [DEBUG] switch_ivr_play_say.c:2905 done speaking text
Thanks for the help. The reason I tried to start with tts_commandine is I have been struggling for a couple of weeks to get MRCP to produce something useful so I thought I would try something simpler and I could swear mod_tts_commandline was listed as a requirement.
Working with mod_unimrcp should be simple. But maybe this can be of help: https://github.com/MayamaTakeshi/mrcp_client It is a node.js app that I wrote to test mrcp servers. I don't know which MRCP server you are using (maybe unimrcp?). But you could make requests directly to it and check if it's working as expected without having to deal with FS. Then once things are cleared up you can work on the FS configuration. Also, if you want to get down checking SIP/MRCP messages, you could use this sngrep fork: https://github.com/MayamaTakeshi/sngrep/tree/mrcp_support (this is a patch that I wrote to support MRCP on sngrep, but this will not be merged to upstream as sngrep main branch is only accepting bug fixes right now: https://github.com/irontec/sngrep/pull/346) so you would need to build it yourself.