comparison: asterisk/features.conf
asterisk/features.conf
- changeset 310
- 73d852a30c9a
equal
deleted
inserted
replaced
| 0:f918543a07ec | -1:000000000000 |
|---|---|
| 1 ; | |
| 2 ; Sample Call Features (parking, transfer, etc) configuration | |
| 3 ; | |
| 4 | |
| 5 ;[general] | |
| 6 ;parkext => 700 ; What extension to dial to park | |
| 7 ;parkpos => 701-720 ; What extensions to park calls on. These needs to be | |
| 8 ; numeric, as Asterisk starts from the start position | |
| 9 ; and increments with one for the next parked call. | |
| 10 ;context => parkedcalls ; Which context parked calls are in | |
| 11 ;parkingtime => 45 ; Number of seconds a call can be parked for | |
| 12 ; (default is 45 seconds) | |
| 13 ;courtesytone = beep ; Sound file to play to the parked caller | |
| 14 ; when someone dials a parked call | |
| 15 ; or the Touch Monitor is activated/deactivated. | |
| 16 ;parkedplay = caller ; Who to play the courtesy tone to when picking up a parked call | |
| 17 ; one of: parked, caller, both (default is caller) | |
| 18 ;adsipark = yes ; if you want ADSI parking announcements | |
| 19 ;findslot => next ; Continue to the 'next' free parking space. | |
| 20 ; Defaults to 'first' available | |
| 21 ;parkedmusicclass=default ; This is the MOH class to use for the parked channel | |
| 22 ; as long as the class is not set on the channel directly | |
| 23 ; using Set(CHANNEL(musicclass)=whatever) in the dialplan | |
| 24 | |
| 25 ;transferdigittimeout => 3 ; Number of seconds to wait between digits when transferring a call | |
| 26 ; (default is 3 seconds) | |
| 27 ;xfersound = beep ; to indicate an attended transfer is complete | |
| 28 ;xferfailsound = beeperr ; to indicate a failed transfer | |
| 29 ;pickupexten = *8 ; Configure the pickup extension. (default is *8) | |
| 30 ;featuredigittimeout = 500 ; Max time (ms) between digits for | |
| 31 ; feature activation (default is 500 ms) | |
| 32 ;atxfernoanswertimeout = 15 ; Timeout for answer on attended transfer default is 15 seconds. | |
| 33 | |
| 34 ; Note that the DTMF features listed below only work when two channels have answered and are bridged together. | |
| 35 ; They can not be used while the remote party is ringing or in progress. If you require this feature you can use | |
| 36 ; chan_local in combination with Answer to accomplish it. | |
| 37 | |
| 38 ;[featuremap] | |
| 39 ;blindxfer => #1 ; Blind transfer (default is #) | |
| 40 ;disconnect => *0 ; Disconnect (default is *) | |
| 41 ;automon => *1 ; One Touch Record a.k.a. Touch Monitor | |
| 42 ;atxfer => *2 ; Attended transfer | |
| 43 ;parkcall => #72 ; Park call (one step parking) | |
| 44 | |
| 45 ;[applicationmap] | |
| 46 ; Note that the DYNAMIC_FEATURES channel variable must be set to use the features | |
| 47 ; defined here. The value of DYNAMIC_FEATURES should be the names of the features | |
| 48 ; to allow the channel to use separated by '#'. For example: | |
| 49 ; | |
| 50 ; Set(DYNAMIC_FEATURES=myfeature1#myfeature2#myfeature3) | |
| 51 ; | |
| 52 ; | |
| 53 ; The syntax for declaring a dynamic feature is the following: | |
| 54 ; | |
| 55 ;<FeatureName> => <DTMF_sequence>,<ActivateOn>[/<ActivatedBy>],<Application>[,<AppArguments>[,MOH_Class]] | |
| 56 ; | |
| 57 ; FeatureName -> This is the name of the feature used in when setting the | |
| 58 ; DYNAMIC_FEATURES variable to enable usage of this feature. | |
| 59 ; DTMF_sequence -> This is the key sequence used to activate this feature. | |
| 60 ; ActivateOn -> This is the channel of the call that the application will be executed | |
| 61 ; on. Valid values are "self" and "peer". "self" means run the | |
| 62 ; application on the same channel that activated the feature. "peer" | |
| 63 ; means run the application on the opposite channel from the one that | |
| 64 ; has activated the feature. | |
| 65 ; ActivatedBy -> This is which channel is allowed to activate this feature. Valid | |
| 66 ; values are "caller", "callee", and "both". "both" is the default. | |
| 67 ; The "caller" is the channel that executed the Dial application, while | |
| 68 ; the "callee" is the channel called by the Dial application. | |
| 69 ; Application -> This is the application to execute. | |
| 70 ; AppArguments -> These are the arguments to be passed into the application. | |
| 71 ; MOH_Class -> This is the music on hold class to play while the idle | |
| 72 ; channel waits for the feature to complete. If left blank, | |
| 73 ; no music will be played. | |
| 74 ; | |
| 75 ; | |
| 76 ; IMPORTANT NOTE: The applicationmap is not intended to be used for all Asterisk | |
| 77 ; applications. When applications are used in extensions.conf, they are executed | |
| 78 ; by the PBX core. In this case, these applications are executed outside of the | |
| 79 ; PBX core, so it does *not* make sense to use any application which has any | |
| 80 ; concept of dialplan flow. Examples of this would be things like Macro, Goto, | |
| 81 ; Background, WaitExten, and many more. | |
| 82 ; | |
| 83 ; Enabling these features means that the PBX needs to stay in the media flow and | |
| 84 ; media will not be re-directed if DTMF is sent in the media stream. | |
| 85 ; | |
| 86 ; Example Usage: | |
| 87 ; | |
| 88 ;testfeature => #9,peer,Playback,tt-monkeys ;Allow both the caller and callee to play | |
| 89 ; ;tt-monkeys to the opposite channel | |
| 90 ; | |
| 91 ;pauseMonitor => #1,self/callee,Pausemonitor ;Allow the callee to pause monitoring | |
| 92 ; ;on their channel | |
| 93 ;unpauseMonitor => #3,self/callee,UnPauseMonitor ;Allow the callee to unpause monitoring | |
| 94 ; ;on their channel | |
| 95 ; |
