26c98bc68b
Instead of searching for the asterisk binary and the modules in the filesystem, we now get their locations, along with libdir, from the coredump itself... For the binary, we can use `gdb -c <coredump> ... "info proc exe"`. gdb can print this even without having the executable and symbols. Once we have the binary, we can get the location of the modules with `gdb ... "print ast_config_AST_MODULE_DIR` If there was no result then either it's not an asterisk coredump or there were no symbols loaded. Either way, it's not usable. For libdir, we now run "strings" on the note0 section of the coredump (which has the shared library -> memory address xref) and search for "libasteriskssl|libasteriskpj", then take the dirname. Since we're now getting everything from the coredump, it has to be correct as long as we're not crossing namespace boundaries like running asterisk in a docker container but trying to run ast_coredumper from the host using a shared file system (which you shouldn't be doing). There is still a case for using --asterisk-bin and/or --libdir: If you've updated asterisk since the coredump was taken, the binary, libraries and modules won't match the coredump which will render it useless. If you can restore or rebuild the original files that match the coredump and place them in a temporary directory, you can use --asterisk-bin, --libdir, and a new --moddir option to point to them and they'll be correctly captured in a tarball created with --tarball-coredumps. If you also use --tarball-config, you can use a new --etcdir option to point to what normally would be the /etc/asterisk directory. Also addressed many "shellcheck" findings. Resolves: #445 |
||
---|---|---|
.. | ||
ast-db-manage | ||
docker | ||
editors | ||
init.d | ||
scripts | ||
systemd | ||
thirdparty | ||
unistimLang | ||
upstart | ||
utils | ||
Makefile | ||
README.festival | ||
asterisk-ices.xml | ||
dictionary.digium | ||
festival-1.4.1-diff | ||
festival-1.4.2.diff | ||
festival-1.4.3.diff | ||
festival-1.95.diff | ||
i18n.testsuite.conf | ||
valgrind-RedHat-8.0.supp | ||
valgrind.supp |
README.festival
app_festival is an application that allows one to send text-to-speech commands to a background festival server, and to obtain the resulting waveform which gets sent down to the respective channel. app_festival also employs a waveform cache, so invariant text-to-speech strings ("Please press 1 for instructions") do not need to be dynamically generated all the time. You need : 1) festival, patched to produce 8khz waveforms on output. Patch for Festival 1.4.2 RELEASE are included. The patch adds a new command to festival (asterisk_tts). It is possible to run Festival without patches in the source-code. Just add this to your /etc/festival.scm or /usr/share/festival/festival/scm: (define (tts_textasterisk string mode) "(tts_textasterisk STRING MODE) Apply tts to STRING. This function is specifically designed for use in server mode so a single function call may synthesize the string. This function name may be added to the server safe functions." (let ((wholeutt (utt.synth (eval (list 'Utterance 'Text string))))) (utt.wave.resample wholeutt 8000) (utt.wave.rescale wholeutt 5) (utt.send.wave.client wholeutt))) [See the comment with subject "Using Debian festival >= 1.4.3-15 (no recompiling needed!)" on http://www.voip-info.org/wiki-Asterisk+festival+installation for the original mentioning of it] 2) You may wish to obtain and install the asterisk-perl module by James Golovich <james@gnuinter.net>, from either CPAN, or his site: http://asterisk.gnuinter.net, as this contains a good example of how variable text can be tts'd via asterisk, namely the examples/tts-*.agi files there. It has been noted that the current expression evaluation capabilities of asterisk are not best suited for the generation and manipulation of text. AGI scripting can be ideal for these sorts of needs. For simpler usage, fixed, pre-recorded messages may be more amenable for your purposes. 3) Before running asterisk, you have to run festival-server with a command like : /usr/local/festival/bin/festival --server > /dev/null 2>&1 &