442b597929
cdr, config and voicemail are all separate alembic trees. Because alembic's default is to use a table named 'alembic_version' to store the current tree revision, the 3 trees can't exist in the same schema without stepping on each other. Now each tree uses 'alembic_version_<tree_name>' as the version table. Each tree's env.py script now first checks for 'alembic_version'. If it finds it AND its revision is in the tree's history, the script renames it to 'alembic_version_<tree_name>'. Regardless, the script then continues with the migration using 'alembic_version_<tree_name>' and creates that table if it's not found. The result is that if an existing 'alembic_version' table was found but it didn't belong to this tree, it's left alone and 'alembic_version_<tree_name>' is used or created. WARNING: If multiple trees are using the same schema, they MUST NOT CRU or D any objects with names that might exist in the other trees. An example would be 'yesno_values' type. If two trees perform operations on it, one tree could pull it out from under the other. Thankfully we currently don't share any names among cdr, config and voicemail. NOTE: Since the env.py scripts in each tree were identical, a common env.py has been placed in the ast-db-manage directory and a symlink to it has been placed in each tree directory. ASTERISK-24311 #close Reported-by: Dafi Ni Change-Id: I4d593f000350deb5d21a14fa1e9bc3896844d898 |
||
---|---|---|
.. | ||
ast-db-manage | ||
docker | ||
editors | ||
init.d | ||
scripts | ||
thirdparty | ||
unistimLang | ||
upstart | ||
utils | ||
asterisk-doxygen-header | ||
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 | ||
Makefile | ||
README.festival | ||
valgrind-RedHat-8.0.supp | ||
valgrind.supp |
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 &