-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
52230eb
commit 99c12f2
Showing
153 changed files
with
20,010 additions
and
3,466 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,80 @@ | ||
; | ||
; Named Access Control Lists (ACLs) | ||
; | ||
; A convenient way to share acl definitions | ||
; | ||
; This configuration file is read on startup | ||
; | ||
; CLI Commands | ||
; ----------------------------------------------------------- | ||
; acl show Show all named ACLs configured | ||
; acl show <name> Show contents of a particular named ACL | ||
; reload acl Reload configuration file | ||
; | ||
; Any configuration that uses ACLs which has been made to be able to use named | ||
; ACLs will specify a named ACL with the 'acl' option in its configuration in | ||
; a similar fashion to the usual 'permit' and 'deny' options. Example: | ||
; acl=my_named_acl | ||
; | ||
; Multiple named ACLs can be applied by either comma separating the arguments or | ||
; just by adding additional ACL lines. Example: | ||
; acl=my_named_acl | ||
; acl=my_named_acl2 | ||
; | ||
; or | ||
; | ||
; acl=my_named_acl,my_named_acl2 | ||
; | ||
; ACLs specified by name are evaluated independently from the ACL specified via | ||
; permit/deny. In order for an address to pass a given ACL, it must pass both | ||
; the ACL specified by permit/deny for a given item as well as any named ACLs | ||
; that were specified. | ||
; | ||
;[example_named_acl1] | ||
;deny=0.0.0.0/0.0.0.0 | ||
;permit=209.16.236.0 | ||
;permit=209.16.236.1 | ||
; | ||
;[example_named_acl2] | ||
;permit=0.0.0.0/0.0.0.0 | ||
;deny=10.24.20.171 | ||
;deny=10.24.20.103 | ||
;deny=209.16.236.1 | ||
; | ||
; example_named_acl1 above shows an example of whitelisting. When whitelisting, the | ||
; named ACLs should follow a deny that blocks everything (like deny=0.0.0.0/0.0.0.0) | ||
; The following example explains how combining the ACLs works: | ||
; <in another configuration> | ||
; [example_item_with_acl] | ||
; acl=example_named_acl1 | ||
; acl=example_named_acl2 | ||
; | ||
; Suppose 209.16.236.0 tries to communicate and the ACL for that example is applied to it... | ||
; First, example_named_acl1 is evaluated. The address is allowed by that ACL. | ||
; Next, example_named_acl2 is evaluated. The address isn't blocked by example_named_acl2 | ||
; either, so it passes. | ||
; | ||
; Suppose instead 209.16.236.1 tries to communicate and the same ACL is applied. | ||
; First, example_named_acl1 is evaluated and the address is allowed. | ||
; However, it is blocked by example_named_acl2, so the address is blocked from the combined | ||
; ACL. | ||
; | ||
; Similarly, the permits/denies in specific configurations that make up an ACL definition | ||
; are also treated as a separate ACL for evaluation. So if we change the example above to: | ||
; <in another configuration> | ||
; [example_item_with_acl] | ||
; acl=example_named_acl1 | ||
; acl=example_named_acl2 | ||
; deny=209.16.236.0 | ||
; | ||
; Then 209.16.236.0 will be rejected by the non-named component of the combined ACL even | ||
; though it passes the two named components. | ||
; | ||
; | ||
; Named ACLs can use ipv6 addresses just like normal ACLs. | ||
;[ipv6_example_1] | ||
;deny = :: | ||
;permit = ::1/128 | ||
; | ||
;[ipv6_example_2] | ||
;permit = fe80::21d:bad:fad:2323 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,8 @@ | ||
; | ||
; Sample ADSI Configuration file | ||
; | ||
[intro] | ||
alignment = center | ||
greeting => Welcome to the | ||
greeting => Asterisk | ||
greeting => Open Source PBX |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,70 @@ | ||
; | ||
; Agent pool configuration | ||
; | ||
|
||
[general] | ||
; The general section of this config is not currently used, but reserved | ||
; for future use. | ||
|
||
;[agent-id] | ||
; Define ackcall to require the agent to give a DTMF acknowledgement | ||
; when the agent receives a call. | ||
; The channel variable AGENTACKCALL overrides on agent login. | ||
; Default is "no". | ||
;ackcall=no | ||
; | ||
; Set what DTMF key sequence the agent should use to acknowledge a call. | ||
; The channel variable AGENTACCEPTDTMF overrides on agent login. | ||
; This option is ignored unless ackcall is enabled. | ||
; Default is "#". | ||
;acceptdtmf=## | ||
; | ||
; Set how many seconds a call for the agent has to wait for the agent to | ||
; acknowledge the call before the agent is automatically logged off. If | ||
; set to zero then the call will wait forever for the agent to acknowledge. | ||
; The channel variable AGENTAUTOLOGOFF overrides on agent login. | ||
; This option is ignored unless ackcall is enabled. | ||
; Default is 0. | ||
;autologoff=15 | ||
; | ||
; Set the minimum amount of time after disconnecting a call before | ||
; the agent can receive a new call in milliseconds. | ||
; The channel variable AGENTWRAPUPTIME overrides on agent login. | ||
; Default is 0. | ||
;wrapuptime=5000 | ||
; | ||
; Set the musiconhold class for the agent. | ||
; Default is "default". | ||
;musiconhold=default | ||
; | ||
; Enable recording calls the agent takes automatically by invoking the | ||
; DTMF automixmon feature when the agent connects to a caller. | ||
; See features.conf.sample for information about the automixmon feature. | ||
; Default is "no". | ||
;recordagentcalls=yes | ||
; | ||
; The sound file played to alert the agent when a call is present. | ||
; Default is "beep". | ||
;custom_beep=beep | ||
; | ||
; A friendly name for the agent used in log messages. | ||
; Default is "". | ||
;fullname=Mark Spencer | ||
; | ||
; -------------------------------------------------- | ||
; | ||
; This section contains example agent definitions: | ||
; | ||
; Define a template called my-agents: | ||
;[my-agents](!) | ||
;autologoff=15 | ||
;ackcall=yes | ||
;acceptdtmf=## | ||
; | ||
; Define agent 1001 using the my-agents template: | ||
;[1001](my-agents) | ||
;fullname=Mark Spencer | ||
; | ||
; Define agent 1002 using the my-agents template: | ||
;[1002](my-agents) | ||
;fullname=Will Meadows |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,91 @@ | ||
; | ||
; alarmreceiver.conf | ||
; | ||
; Sample configuration file for the Asterisk alarm receiver application. | ||
; | ||
|
||
|
||
[general] | ||
|
||
; | ||
; Specify a timestamp format for the metadata section of the event files | ||
; Default is %a %b %d, %Y @ %H:%M:%S %Z | ||
|
||
timestampformat = %a %b %d, %Y @ %H:%M:%S %Z | ||
|
||
; | ||
; Specify a command to execute when the caller hangs up | ||
; | ||
; Default is none | ||
; | ||
|
||
;eventcmd = yourprogram -yourargs ... | ||
|
||
; | ||
; Specify a spool directory for the event files. This setting is required | ||
; if you want the app to be useful. Event files written to the spool | ||
; directory will be of the template event-XXXXXX, where XXXXXX is a random | ||
; and unique alphanumeric string. | ||
; | ||
; Default is none, and the events will be dropped on the floor. | ||
; | ||
|
||
eventspooldir = /tmp | ||
|
||
; | ||
; The alarmreceiver app can either log the events one-at-a-time to individual | ||
; files in the spool directory, or it can store them until the caller | ||
; disconnects and write them all to one file. | ||
; | ||
; The default setting for logindividualevents is no. | ||
; | ||
|
||
logindividualevents = no | ||
|
||
; | ||
; The timeout for receiving the first DTMF digit is adjustable from 1000 msec. | ||
; to 10000 msec. The default is 2000 msec. Note: if you wish to test the | ||
; receiver by entering digits manually, set this to a reasonable time out | ||
; like 10000 milliseconds. | ||
|
||
fdtimeout = 2000 | ||
|
||
; | ||
; The timeout for receiving subsequent DTMF digits is adjustable from | ||
; 110 msec. to 4000 msec. The default is 200 msec. Note: if you wish to test | ||
; the receiver by entering digits manually, set this to a reasonable time out | ||
; like 4000 milliseconds. | ||
; | ||
|
||
sdtimeout = 200 | ||
|
||
; | ||
; Wait for the connection to settle post-answer. Adjustable from 500 msec. to 10000 msec. | ||
; The default is 1250 msec. | ||
; | ||
|
||
answait = 1250 | ||
|
||
; When logging individual events it may be desirable to skip grouping of metadata | ||
|
||
;no_group_meta = yes | ||
|
||
; | ||
; The loudness of the ACK and Kissoff tones is adjustable from 100 to 8192. | ||
; The default is 8192. This shouldn't need to be messed with, but is included | ||
; just in case there are problems with signal levels. | ||
; | ||
|
||
loudness = 8192 | ||
|
||
; | ||
; The db-family setting allows the user to capture statistics on the number of | ||
; calls, and the errors the alarm receiver sees. The default is for no | ||
; db-family name to be defined and the database logging to be turned off. | ||
; | ||
|
||
;db-family = yourfamily: | ||
|
||
; | ||
; End of alarmreceiver.conf | ||
; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,77 @@ | ||
; | ||
; Open Sound System Console Driver Configuration File | ||
; | ||
[general] | ||
; | ||
; Automatically answer incoming calls on the console? Choose yes if | ||
; for example you want to use this as an intercom. | ||
; | ||
autoanswer=yes | ||
; | ||
; Default context (is overridden with @context syntax) | ||
; | ||
context=local | ||
; | ||
; Default extension to call | ||
; | ||
extension=s | ||
; | ||
; Default language | ||
; | ||
;language=en | ||
; | ||
; Default Music on Hold class to use when this channel is placed on hold in | ||
; the case that the music class is not set on the channel with | ||
; Set(CHANNEL(musicclass)=whatever) in the dialplan and the peer channel | ||
; putting this one on hold did not suggest a class to use. | ||
; | ||
;mohinterpret=default | ||
; | ||
; Silence suppression can be enabled when sound is over a certain threshold. | ||
; The value for the threshold should probably be between 500 and 2000 or so, | ||
; but your mileage may vary. Use the echo test to evaluate the best setting. | ||
;silencesuppression = yes | ||
;silencethreshold = 1000 | ||
; | ||
; To set which ALSA device to use, change this parameter | ||
;input_device=hw:0,0 | ||
;output_device=hw:0,0 | ||
|
||
; | ||
; Default mute state (can also be toggled via CLI) | ||
;mute=true | ||
|
||
; | ||
; If enabled, no audio capture device will be opened. This is useful on | ||
; systems where there will be no return audio path, such as overhead pagers. | ||
;noaudiocapture=true | ||
|
||
; ----------------------------- JITTER BUFFER CONFIGURATION -------------------------- | ||
; jbenable = yes ; Enables the use of a jitterbuffer on the receiving side of an | ||
; ALSA channel. Defaults to "no". An enabled jitterbuffer will | ||
; be used only if the sending side can create and the receiving | ||
; side can not accept jitter. The ALSA channel can't accept jitter, | ||
; thus an enabled jitterbuffer on the receive ALSA side will always | ||
; be used if the sending side can create jitter. | ||
|
||
; jbmaxsize = 200 ; Max length of the jitterbuffer in milliseconds. | ||
|
||
; jbresyncthreshold = 1000 ; Jump in the frame timestamps over which the jitterbuffer is | ||
; resynchronized. Useful to improve the quality of the voice, with | ||
; big jumps in/broken timestamps, usually sent from exotic devices | ||
; and programs. Defaults to 1000. | ||
|
||
; jbimpl = fixed ; Jitterbuffer implementation, used on the receiving side of a SIP | ||
; channel. Two implementations are currently available - "fixed" | ||
; (with size always equals to jbmax-size) and "adaptive" (with | ||
; variable size, actually the new jb of IAX2). Defaults to fixed. | ||
|
||
; jbtargetextra = 40 ; This option only affects the jb when 'jbimpl = adaptive' is set. | ||
; The option represents the number of milliseconds by which the new | ||
; jitter buffer will pad its size. the default is 40, so without | ||
; modification, the new jitter buffer will set its size to the jitter | ||
; value plus 40 milliseconds. increasing this value may help if your | ||
; network normally has low jitter, but occasionally has spikes. | ||
|
||
; jblog = no ; Enables jitterbuffer frame logging. Defaults to "no". | ||
; ---------------------------------------------------------------------------------- |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,27 @@ | ||
; | ||
; Answering Machine Detection Configuration | ||
; | ||
|
||
[general] | ||
total_analysis_time = 5000 ; Maximum time allowed for the algorithm to decide | ||
; on whether the audio represents a HUMAN, or a MACHINE | ||
silence_threshold = 256 ; If the average level of noise in a sample does not reach | ||
; this value, from a scale of 0 to 32767, then we will consider | ||
; it to be silence. | ||
|
||
; Greeting ; | ||
initial_silence = 2500 ; Maximum silence duration before the greeting. | ||
; If exceeded, then the result is detection as a MACHINE. | ||
after_greeting_silence = 800 ; Silence after detecting a greeting. | ||
; If exceeded, then the result is detection as a HUMAN | ||
greeting = 1500 ; Maximum length of a greeting. If exceeded, then the | ||
; result is detection as a MACHINE. | ||
|
||
; Word detection ; | ||
min_word_length = 100 ; Minimum duration of Voice to considered as a word | ||
maximum_word_length = 5000 ; Maximum duration of a single Voice utterance allowed. | ||
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 = 2 ; Maximum number of words in the greeting | ||
; If exceeded, then the result is detection as a MACHINE |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,24 @@ | ||
; Configuration file for the MYSQL app addon | ||
|
||
[general] | ||
; | ||
; Nullvalue governs how NULL values are returned from the database. In | ||
; previous versions, the special NULL value was returned as the "NULL" | ||
; string. We now provide an option for the behavior, configured globally. | ||
; nullstring - the string "NULL" | ||
; emptystring - the string "" | ||
; null - unset the variable | ||
; | ||
; WARNING: setting nullvalue=null may have undesireable consequences, in | ||
; particular if you use subroutines in AEL or the LOCAL() variable construct. | ||
; You have been warned. Don't complain if you use that setting in combination | ||
; with Gosub or AEL and get buggy behavior. | ||
; | ||
nullvalue = nullstring | ||
|
||
; If set, autoclear will destroy allocated statement and connection resources | ||
; when the channel ends. For most usage of the MYSQL app, this is what you | ||
; want, but it's conceivable that somebody is sharing MYSQL connections across | ||
; multiple channels, in which case, this should be set to 'no'. Defaults to | ||
; 'no', as this was the original behavior. | ||
autoclear=yes |
Oops, something went wrong.