This patch gives the optional ability to keep queue rules in RealTime. It is important to note that with this patch: (a) Queue rules in RealTime are only examined on module load/reload (b) Queue rules are loaded both from the queuerules.conf file as well as the RealTime backend To inform app_queue to examine RealTime for queue rules, a new setting has been added to queuerules.conf's general section "realtime_rules". RealTime queue rules will only be used when this setting is set to "yes". The schema for the database table supports a rule_name, time, min_penalty, and max_penalty columns. min_penalty and max_penalty can be relative, if a '-' or '+' literal is provided. Otherwise, the penalties are treated as constants. For example: rule_name, time, min_penalty, max_penalty 'default', '10', '20', '30' 'test2', '20', '30', '55' 'test2', '25', '-11', '+1111' 'test2', '400', '112', '333' 'test3', '0', '4564', '46546' 'test_rule', '40', '15', '50' which would result in : Rule: default - After 10 seconds, adjust QUEUE_MAX_PENALTY to 30 and adjust QUEUE_MIN_PENALTY to 20 Rule: test2 - After 20 seconds, adjust QUEUE_MAX_PENALTY to 55 and adjust QUEUE_MIN_PENALTY to 30 - After 25 seconds, adjust QUEUE_MAX_PENALTY by 1111 and adjust QUEUE_MIN_PENALTY by -11 - After 400 seconds, adjust QUEUE_MAX_PENALTY to 333 and adjust QUEUE_MIN_PENALTY to 112 Rule: test3 - After 0 seconds, adjust QUEUE_MAX_PENALTY to 46546 and adjust QUEUE_MIN_PENALTY to 4564 Rule: test_rule - After 40 seconds, adjust QUEUE_MAX_PENALTY to 50 and adjust QUEUE_MIN_PENALTY to 15 If you use RealTime, the queue rules will be always reloaded on a module reload, even if the underlying file did not change. With the option disabled, the rules will only be reloaded if the file was modified. Review: https://reviewboard.asterisk.org/r/3607/ ASTERISK-23823 #close Reported by: Michael K patches: app_queue.c_realtime_trunk.patch uploaded by Michael K (License 6621) ........ Merged revisions 420624 from http://svn.asterisk.org/svn/asterisk/branches/13 git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@420625 65c4cc65-6c06-0410-ace0-fbb531ad65f3 |
||
---|---|---|
.. | ||
ast-db-manage | ||
editors | ||
init.d | ||
scripts | ||
thirdparty | ||
unistimLang | ||
upstart | ||
utils | ||
asterisk-doxygen-header | ||
asterisk-ices.xml | ||
asterisk-ng-doxygen | ||
dictionary.digium | ||
festival-1.4.1-diff | ||
festival-1.4.2.diff | ||
festival-1.4.3.diff | ||
festival-1.95.diff | ||
i18n.testsuite.conf | ||
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 &