Completing the transfer with a DTMF sequence is functionally equivalent to hanging up the transferrer channel during an attended transfer. The result is that the transfer target and transferees are bridged. Pressing this DTMF sequence will result in the transferrer, the transferees, and the transfer target all being in a single bridge together.
Pressing this DTMF sequence will result in the transferrer swapping which party he is bridged with. For instance, if the transferrer is currently bridged with the transfer target, then pressing this DTMF sequence will cause the transferrer to be bridged with the transferees. In order for the pickup attempt to be successful, the party attempting to pick up the call must either have a namedpickupgroup in common with a ringing party's namedcallgroup or must have a pickupgroup in common with a ringing party's callgroup.
The transferee parties will be placed on hold and the transferrer may dial an extension to reach a transfer target. During an attended transfer, the transferrer may consult with the transfer target before completing the transfer. Once the transferrer has hung up or pressed the atxfercomplete DTMF sequence, then the transferees and transfer target will be bridged. During a blind transfer, as soon as the transfer target is dialed, the transferrer is hung up. Entering this DTMF sequence will cause the bridge to end, no matter the number of parties present.
If no configured value on the channel is present, then "default" is used. The call is parked in the next available space in the parking lot. This will cause the channel that pressed the DTMF sequence to be monitored by the Monitor application.
If this variable is not specified, then wav is the default. The filename is constructed in the following manner:. The timestamp is a UNIX timestamp. If you are using parking, you are probably also going to need a way to announce the parked calls so that the intended parties know how to retrieve them. Parking and Paging Next. The [general] section. Table Parked calls may be retrieved by dialing the numbers in this range.
The default is no. For more information on the behavior of this option, see the sidebar titled Handling Timed-Out Parked Calls with the comebacktoorigin Option. Valid options include callee , caller , both , or no. See Parking Lots for more details. No sound is played by default. 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. By default, this is set to 2 callback attempts. Note The dialplan and contexts were discussed in detail in Chapter 6, Dialplan Basics. The [featuremap] Section. The [applicationmap] Section. Note Since applications spawned from the application map are run outside the PBX core, you cannot execute any applications that trigger the dial plan such as Goto , Macro , Background , etc. Inheriting Channel Variables.
Application Map Grouping. Parking Lots. Prev Up Next Chapter Public Address. Sets the range of extensions used as the parking lot. Sets the default dialplan context where the parking extension and the parking lot extensions are created. Specifies the number of seconds a call will wait in the parking lot before timing out. Configures the handling of timed-out parked calls. Specifies the sound file to be played to the parked caller when the parked call is retrieved from the parking lot.
Indicates which side of the call to play the courtesytone to when a parked call is picked up. Controls 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.
Controls 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.
Controls 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. Controls 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. Enables the dynamic creation of parking lots in the dialplan. Configures the parking slot selection behavior.
Specifies the class to be used for the music on hold played to a parked caller. Sets the number of seconds to wait for each digit from the caller executing a transfer. When applications are used in extensions. In this case, these applications are executed outside of the ; PBX core, so it does not make sense to use any application which has any ; concept of dialplan flow.
Help me with features. I mean, can i define the in the SIP. CONF for each phone in sip. I fixed!! I just set the var in the sip. As noted elsewhere, Macro is officially unsupported in featuremap.
0コメント