Frequently Asked Question

Uitleg features.conf en dialplan settings - Voor timeouts en dergelijke met doorverbinden en terugkomen
Last Updated 9 years ago

Tijden instellen voor o.a.:

  • terugkomen na doorverbinden met ruggespraak
  • tijd tussen het intoetsen van een nummer
Toevoegingen in freepbx dienen gedaan te worden in het volgende bestand:  
features_general_custom.conf
featuredigittimeout = 3000
atxfernoanswertimeout = 30
atxferdropcall = no
atxfercallbackretries = 3
transferdigittimeout = 2
4Allbusiness settings met uitleg:

  • featuredigittimeout = 3000  #(std=1sec) 3 secondes de tijd tussen in te toetsen nrs voordat ze automatisch doorgaan
  • atxfernoanswertimeout = 30 #(std=15sec) pas na 30 seconden niet oppaken van doorgeschakeld gesprek, komt deze terug naar de verstuurder
  • atxferdropcall = yes       #(std = no) Of een attended transfer doorgaat als de beller te vroeg ophangt.
  • atxfercallbackretries = 3  #(std = 2) Hoe vaak een gesprek probeert opnieuw door te schakelen voordat er helemaal opgehangen wordt.
  • transferdigittimeout=10  #(maximale tijd tussen ingaves na een transfer commando)
here are several features common to most modern PBXs that Asterisk also provides. Many of these features have optional parameters. The features.conf file is where you can adjust or define the various feature parameters in Asterisk.
DTMF-Based Features
Many of the parameters in features.conf only apply when invoked on calls that have been bridged by the dialplan applications Dial() or Queue(), with one or more of the options KkHhTtWwX, or x specified. Features accessed in this way are DTMF-based (meaning they can’t be accessed via SIP messaging, but only through touch-tone signals in the audio channel triggered by the users dialing the required digits on their dialpads).[97]
Transfers on SIP channels (for example from a SIP telephone) can be handled using the capabilities of the phone itself, and won’t be affected by anything in the features.conf file.

The [general] section

In the [general] section of features.conf, you can define options that fine-tune the behavior of the park and transfer features in Asterisk. These options are listed in Table 11.1, “features.conf [general] section”.
Table 11.1. features.conf [general] section
OptionValue/ExampleNotes
parkext<a style="color: blue; text-decoration: underline"></a>700Sets the default extension used to park calls.
parkpos<a style="color: blue; text-decoration: underline"></a>701-720Sets the range of extensions used as the parking lot. Parked calls may be retrieved by dialing the numbers in this range.
context<a style="color: blue; text-decoration: underline"></a>parkedcallsSets the default dialplan context where the parking extension and the parking lot extensions are created.
parkinghints<a style="color: blue; text-decoration: underline"></a>noEnables/disables automatic creation of dialplan hints for the parking lot extensions so that phones can subscribe to the state of extensions in the parking lot. The default is no.
parkingtime<a style="color: blue; text-decoration: underline"></a>45Specifies the number of seconds a call will wait in the parking lot before timing out.
comebacktoorigin<a style="color: blue; text-decoration: underline"></a>yesConfigures the handling of timed-out parked calls. For more information on the behavior of this option, see the sidebar titled Handling Timed-Out Parked Calls with the comebacktoorigin Option.
courtesytone<a style="color: blue; text-decoration: underline"></a>beepSpecifies the sound file to be played to the parked caller when the parked call is retrieved from the parking lot.
parkedplay<a style="color: blue; text-decoration: underline"></a>callerIndicates which side of the call to play the courtesytone to when a parked call is picked up. Valid options include calleecallerboth, or no. The default is no.
parkedcalltransfers<a style="color: blue; text-decoration: underline"></a>callerControls which side of a call has the ability to execute a DTMF-based transfer in the call that results from picking up a parked call. Valid options include calleecallerboth, or no. The default is no.
parkedcallreparking<a style="color: blue; text-decoration: underline"></a>callerControls which side of a call has the ability to execute a DTMF-based park in the call that results from picking up a parked call.[a] Valid options include calleecallerboth, or no. The default is no.
parkedcallhangup<a style="color: blue; text-decoration: underline"></a>callerControls which side of a call has the ability to execute a DTMF-based hangup in the call that results from picking up a parked call. Valid options include calleecallerboth, or no. The default is no.
parkedcallrecording<a style="color: blue; text-decoration: underline"></a>callerControls which side of a call has the ability to initiate a DTMF-based one-touch recording in the call that results from picking up a parked call. Valid options include calleecallerboth, or no. The default is no.
parkeddynamic<a style="color: blue; text-decoration: underline"></a>yesEnables the dynamic creation of parking lots in the dialplan. The channel variables PARKINGDYNAMICPARKINGDYNCONTEXT, and PARKINGDYNPOS need to be set.
adsipark<a style="color: blue; text-decoration: underline"></a>yesPasses ADSI information regarding the parked call back to the originating set.
findslot<a style="color: blue; text-decoration: underline"></a>nextConfigures the parking slot selection behavior. See Parking Lots for more details.
parkedmusicclass<a style="color: blue; text-decoration: underline"></a>defaultSpecifies the class to be used for the music on hold played to a parked caller. A music class set in the dialplan using the CHANNEL(musicclass) dialplan function will override this setting.
transferdigittimeout<a style="color: blue; text-decoration: underline"></a>3Sets the number of seconds to wait for each digit from the caller executing a transfer.
xfersound<a style="color: blue; text-decoration: underline"></a>beepSpecifies the sound to be played to indicate that an attended transfer is complete.
xferfailsound<a style="color: blue; text-decoration: underline"></a>beeperrSpecifies the sound to be played to indicate that an attended transfer has failed to complete.
pickupexten<a style="color: blue; text-decoration: underline"></a>*8Configures the extension used for call pickup.
pickupsound<a style="color: blue; text-decoration: underline"></a>beepSpecifies the sound to be played to indicate a successful call pickup attempt. No sound is played by default.
pickupfailsound<a style="color: blue; text-decoration: underline"></a>beeperrSpecifies the sound to be played to indicate a failed call pickup attempt. No sound is played by default.
featuredigittimeout<a style="color: blue; text-decoration: underline"></a>1000Sets the number of milliseconds to wait in between digits pressed during a bridged call when matching against DTMF activated call features.
atxfernoanswertimeout<a style="color: blue; text-decoration: underline"></a>15Configures the number of seconds to wait for the target of an attended transfer to answer before considering the attempt timed out.
atxferdropcall<a style="color: blue; text-decoration: underline"></a>noConfigures behavior of attended transfer call handling when the transferer hangs up before the transfer is complete and the transfer fails. By default, this option is set to no and a call will be originated to attempt to connect the transferee back to the caller that initiated the transfer. If set to yes, the call will be dropped after the transfer fails.
atxferloopdelay<a style="color: blue; text-decoration: underline"></a>10Sets the number of seconds to wait in between callback retries if atxferdropcall is set to no.
atxfercallbackretries<a style="color: blue; text-decoration: underline"></a>2Sets the number of callback attempts to make if atxferdropcall is set to no. By default, this is set to 2 callback attempts.
[aRead that again. It makes sense.

Handling Timed-Out Parked Calls with the comebacktoorigin Option
This option configures the behavior of call parking when the parked call times out (see the parkingtime option). comebacktoorigin can have one of two values:
yes (default)
When the parked call timeout is exceeded, Asterisk will attempt to send the call back to the peer that parked this call. If the channel is no longer available to Asterisk, the caller will be disconnected.
no
This option would be used when you want to perform custom dialplan functionality on parked calls that have exceeded their timeouts. The caller will be sent into a specific area of the dialplan where logic can be applied to gracefully handle the remainder of the call (this may involve simply returning the call to a different extension, or performing a lookup of some sort).
You also may need to take into account calls where the originating channel cannot handle a returned parked call. If, for example, the call was parked by a channel that is also a trunk to another system, there would not be enough information to send the call back to the correct person on that other system. The actions following a timeout would be more complex than comebacktoorigin=yes could handle gracefully.
Parked calls that time out with comebacktoorigin=no will always be sent into the parkedcallstimeout context.
The dialplan (and contexts) were discussed in detail in Chapter 6, Dialplan Basics.
The extension they will be sent to will be built from the name of the channel that parked the call. For example, if a SIP peer named 0004F2040808 parked this call, the extension will be SIP_0004F2040808.
If this extension does not exist, the call will be sent to the s extension in the parkedcallstimeout context instead. Finally, if the s extension of parkedcallstimeout does not exist, the call will be sent to the s extension of the default context.
Additionally, for any calls where comebacktoorigin=no, there will be an extension of SIP_0004F2040808 created in the park-dial context. This extension will be set up to do a Dial() to SIP/0004F2040808.[98]

The [featuremap] Section

This section allows you to define specific DTMF sequences, which will trigger various features on channels that have been bridged via options in the Dial() or Queue() application. The options are detailed in Table 11.2, “features.conf [featuremap] section”.
Table 11.2. features.conf [featuremap] section
OptionValue/ExampleNotesDial()/Queue() Flags
blindxfer<a style="color: blue; text-decoration: underline"></a>#1Invokes a blind (unsupervised) transferT, t
disconnect<a style="color: blue; text-decoration: underline"></a>*0Hangs up the callH, h
automon<a style="color: blue; text-decoration: underline"></a>*1Starts recording of the current call using the Monitor() application (pressing this key sequence a second time stops the recording)W, w
atxfer<a style="color: blue; text-decoration: underline"></a>*2Performs an automated transferT, t
parkcall<a style="color: blue; text-decoration: underline"></a>#72Parks a callK, k
automixmon<a style="color: blue; text-decoration: underline"></a>*3Starts recording of the current call using the MixMonitor() application (pressing this key sequence again stops the recording)X, x<br /><br />

Loading ...