OpenPKG Specs: comparison asterisk/asterisk.txt

-:c2a83a20fc7d
+:3da5d5ce2332
 ;nofork            = no
 ;console           = no
 ;dontwarn          = no
 </file>
+<file name="amd.conf">
+;;
+;;  amd.conf -- Answering Machine Detection configuration
+;;
+[general]
+initial_silence        = 2500 ; Maximum silence duration before the greeting.
+; If exceeded then MACHINE.
+greeting               = 1500 ; Maximum length of a greeting.
+;If exceeded then MACHINE.
+after_greeting_silence = 800  ; Silence after detecting a greeting.
+; If exceeded then HUMAN.
+total_analysis_time    = 5000 ; Maximum time allowed for the algorithm to
+; decide on a HUMAN or MACHINE.
+min_word_length        = 100  ; Minimum duration of Voice to considered a word.
+between_words_silence  = 50   ; Minimum duration of silence after a word to
+; consider the audio what follows as a new word.
+maximum_number_of_words = 3   ; Maximum number of words in the greeting.
+; If exceeded then MACHINE.
+silence_threshold       = 256
+</file>
 <file name="modules.conf">
 ;;
 ;;  modules.conf -- Asterisk functionality module configuration
 ;;
 [modules]
 autoload           = yes
-noload             = chan_iax2.so
-noload             = chan_mgcp.so
-noload             = chan_skinny.so
-noload             = chan_gtalk.so
-noload             = chan_ooh323.so
 [global]
 </file>
 <file name="logger.conf">
 write              = system,call,agent,user,config,command,reporting
 </file>
 <file name="http.conf">
 ;;
-;;  http.conf -- Asterisk HTTP Server Interface
+;;  http.conf -- Asterisk HTTP server interface
 ;;
 [general]
 enabled            = no
 bindaddr           = 127.0.0.1
 ;bindaddr=127.0.0.1  ; more than once to bind to multiple
 ;                    ; addresses, but the first will be the
 ;                    ; default
 </file>
+<file name="iaxprov.conf">
+;;
+;;  iaxprov.conf -- IAX2 provisioning information
+;;
+; Contains provisioning information for templates and for specific service
+; entries.
+;
+; Templates provide a group of settings from which provisioning takes place.
+; A template may be based upon any template that has been specified before
+; it.  If the template that an entry is based on is not specified then it is
+; presumed to be 'default' (unless it is the first of course).
+;
+; Templates which begin with 'si-' are used for provisioning units with
+; specific service identifiers.  For example the entry "si-000364000126"
+; would be used when the device with the corresponding service identifier of
+; "000364000126" attempts to register or make a call.
+;
+[default]
+port=4569  ; the port number the device should bind to (default 4569)
+server=127.0.0.1  ; our PRIMARY server for registration and placing calls
+; altserver is the BACKUP server for registration and placing calls in the
+; event the primary server is unavailable.
+;
+altserver=127.0.0.2
+; port is the port number to use for IAX2 outbound.  The connections to the
+; server and altserver (default 4569)
+;
+serverport=4569
+language=es  ; the preferred language for the device
+codec=ulaw  ; requested codec, the iaxy supports ulaw and adpcm
+; flags is a comma separated list of flags which the device should
+; use and may contain any of the following keywords:
+;
+;  "register"  - Register with server
+;  "secure"    - Do not accept calls / provisioning not originated by server
+;  "heartbeat" - Generate status packets on port 9999 sent to 255.255.255.255
+;  "debug"     - Output extra debugging to port 9999
+;
+;  Note that use can use += and -= to adjust parameters
+;
+flags=register
+tos=ef  ; see doc/ip-tos.txt
+; Example iaxy provisioning
+;
+;[si-000364000126]
+;user=iaxy
+;pass=bitsy
+;flags += debug
+;[si-000364000127]
+;user=iaxy2
+;pass=bitsy2
+;template=si-000364000126
+;flags += debug
+;  If specified, the '*' provisioning is used for all devices which do not
+;  have another provisioning entry within the file.  If unspecified, no
+;  provisioning will take place for devices which have no entry.  DO NOT
+;  USE A '*' PROVISIONING ENTRY UNLESS YOU KNOW WHAT YOU'RE DOING.
+;
+;[*]
+;template=default
+</file>
 <file name="rtp.conf">
 ;;
 ;;  rtp.conf -- Asterisk RTP configuration
 ;;
 Event=>reboot
 ; Cisco
 [cisco-check-cfg]
 Event=>check-sync
+</file>
+<file name="extconfig.conf">
+;;
+;;  extconfig.conf -- Static and realtime external configuration engine
+;;
+[settings]
+;
+; Static configuration files:
+;
+; file.conf => driver,database[,table[,priority]]
+;
+; maps a particular configuration file to the given
+; database driver, database and table (or uses the
+; name of the file as the table if not specified)
+;
+;uncomment to load queues.conf via the odbc engine.
+;
+;queues.conf => odbc,asterisk,ast_config
+;extensions.conf => sqlite,asterisk,ast_config
+;
+; The following files CANNOT be loaded from Realtime storage:
+;	asterisk.conf
+;	extconfig.conf (this file)
+;	logger.conf
+;
+; Additionally, the following files cannot be loaded from
+; Realtime storage unless the storage driver is loaded
+; early using 'preload' statements in modules.conf:
+;	manager.conf
+;	cdr.conf
+;	rtp.conf
+;
+;
+; Realtime configuration engine
+;
+; maps a particular family of realtime
+; configuration to a given database driver,
+; database and table (or uses the name of
+; the family if the table is not specified
+;
+;example => odbc,asterisk,alttable,1
+;example => mysql,asterisk,alttable,2
+;example2 => ldap,"dc=oxymium,dc=net",example2
+;
+; Additionally, priorities are now supported for use as failover methods
+; for retrieving realtime data.  If one connection fails to retrieve any
+; information, the next sequential priority will be tried next.  This
+; especially works well with ODBC connections, since res_odbc now caches
+; when connection failures occur and prevents immediately retrying those
+; connections until after a specified timeout.  Note:  priorities must
+; start at 1 and be sequential (i.e. if you have only priorities 1, 2,
+; and 4, then 4 will be ignored, because there is no 3).
+;
+; "odbc" is shown in the examples below, but is not the only valid realtime
+; engine.  There is:
+;    odbc ... res_config_odbc
+;    sqlite ... res_config_sqlite
+;    pgsql ... res_config_pgsql
+;    curl ... res_config_curl
+;    ldap ... res_config_ldap
+;
+;iaxusers => odbc,asterisk
+;iaxpeers => odbc,asterisk
+;sippeers => odbc,asterisk
+;sipregs => odbc,asterisk ; (avoid sipregs if possible, e.g. by using a view)
+;voicemail => odbc,asterisk
+;extensions => odbc,asterisk
+;meetme => mysql,general
+;queues => odbc,asterisk
+;queue_members => odbc,asterisk
+;musiconhold => mysql,general
+;queue_log => mysql,general
+;
+;
+; While most dynamic realtime engines are automatically used when defined in
+; this file, 'extensions', distinctively, is not.  To activate dynamic realtime
+; extensions, you must turn them on in each respective context within
+; extensions.conf with a switch statement.  The syntax is:
+;      switch => Realtime/[[db_context@]tablename]/<opts>
+; The only option available currently is the 'p' option, which disallows
+; extension pattern queries to the database.  If you have no patterns defined
+; in a particular context, this will save quite a bit of CPU time.  However,
+; note that using dynamic realtime extensions is not recommended anymore as a
+; best practice; instead, you should consider writing a static dialplan with
+; proper data abstraction via a tool like func_odbc.
 </file>
 <file name="extensions.conf">
 ;;
 ;;  extensions.conf -- Asterisk inbound & outbound call configuration
 search             = e164.org
 </file>
 <file name="musiconhold.conf">
 ;;
-;;  musiconhold.conf -- Asterisk music-on-hold configuration
+;;  musiconhold.conf -- Asterisk music on hold configuration
 ;;
 [default]
 mode               = files
 directory          = @l_prefix@/share/asterisk/moh
 ;dtmf_generate     = yes
 </file>
 <file name="features.conf">
 ;;
-;;  features.conf -- Asterisk Call Features configuration
+;;  features.conf -- Asterisk call features configuration
 ;;
 [general]
 ;parkext           = 700
 ;parkpos           = 701-720
 ;context           = parkedcalls
+</file>
+<file name="festival.conf">
+;;
+;;  festival.conf -- Asterisk festival configuration
+;;
+[general]
+host      = localhost  ; default 'localhost'
+port      = 1314       ; default '1314'
+usecache  = no         ; default 'no'
+; If usecache=yes, a directory to store waveform cache files.
+; The cache is never cleared (yet), so you must take care of cleaning it
+; yourself (just delete any or all files from the cache).
+; THIS DIRECTORY *MUST* EXIST and must be writable from the asterisk process.
+; Defaults to /tmp/
+;
+;cachedir  = /opsw/var/asterisk/festivalcache/
+;
+; Festival command to send to the server.
+; Defaults to: (tts_textasterisk "%s" 'file)(quit)\n
+; %s is replaced by the desired text to say. The command MUST end with a
+; (quit) directive, or the cache handling mechanism will hang. Do not
+; forget the \n at the end.
+;
+festivalcommand = (tts_textasterisk "%s" 'file)(quit)\n
 </file>
 <file name="gtalk.conf">
 ;;
 ;;  gtalk.conf -- Asterisk GTalk configuration
 ;timeout           = 100
 </file>
 <file name="indications.conf">
 ;;
-;;  indications.conf -- Asterisk Tone Indications
+;;  indications.conf -- Asterisk tone indications
 ;;
 [general]
 country            = us

OpenPKG Specs / file comparison

comparison: asterisk/asterisk.txt

asterisk/asterisk.txt