[asterisk-bugs] [JIRA] (ASTERISK-24738) Disconnect option in features.conf not functioning in Asterisk 13.1.0
Richard Mudgett (JIRA)
noreply at issues.asterisk.org
Fri Jan 30 11:25:34 CST 2015
[ https://issues.asterisk.org/jira/browse/ASTERISK-24738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Richard Mudgett closed ASTERISK-24738.
--------------------------------------
Resolution: Not A Bug
The DTMF attended transfer feature was completely reworked in v12 and later.
The disconnect option no longer does double duty as a call disconnect and transfer abort. The replacement option is atxferabort.
>From {{features.conf.sample}}:
{noformat}
;atxfernoanswertimeout = 15 ; Timeout for answer on attended transfer default is 15 seconds.
;atxferdropcall = no ; If someone does an attended transfer, then hangs up before the transfer
; target answers, then by default, the system will try to call back the
; person that did the transfer. If this is set to "yes", the ringing
; transfer target is immediately transferred to the transferee.
;atxferloopdelay = 10 ; Number of seconds to sleep between retries (if atxferdropcall = no)
;atxfercallbackretries = 2 ; Number of times to attempt to send the call back to the transferer.
; By default, this is 2.
;transferdialattempts = 3 ; Number of times that a transferer may attempt to dial an extension before
; being kicked back to the original call.
;transferretrysound = "beep" ; Sound to play when a transferer fails to dial a valid extension.
;transferinvalidsound = "beeperr" ; Sound to play when a transferer fails to dial a valid extension and is out of retries.
;atxferabort = *1 ; cancel the attended transfer
;atxfercomplete = *2 ; complete the attended transfer, dropping out of the call
;atxferthreeway = *3 ; complete the attended transfer, but stay in the call. This will turn the call into a multi-party bridge
;atxferswap = *4 ; swap to the other party. Once an attended transfer has begun, this options may be used multiple times
{noformat}
>From the {{CHANGES}} file in the {{Functionality changes from Asterisk 11 to Asterisk 12}} section:
{noformat}
Features
-------------------
* Core attended transfers now have several new options. While performing an
attended transfer, the transferer now has the following options:
- *1 - cancel the attended transfer (configurable via atxferabort)
- *2 - complete the attended transfer, dropping out of the call
(configurable via atxfercomplete)
- *3 - complete the attended transfer, but stay in the call. This will turn
the call into a multi-party bridge (configurable via atxferthreeway)
- *4 - swap to the other party. Once an attended transfer has begun, this
options may be used multiple times (configurable via atxferswap)
{noformat}
> Disconnect option in features.conf not functioning in Asterisk 13.1.0
> ---------------------------------------------------------------------
>
> Key: ASTERISK-24738
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-24738
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Affects Versions: 13.1.1
> Reporter: Josh Adams
> Severity: Minor
>
> I recently upgraded from Asterisk 1.8 to Asterisk 13.1.0. Since the upgrade I can no longer return to the original call during an attended transfer. In the previous version of Asterisk I was able to do this with the disconnect option specified in features.conf.
> I have pasted in the featuremap section of features.conf below. I have enabled verbosity in the CLI to verify that the DTMF tones are being received. I can not see anything happening in the CLI after ** is pressed to initiate the disconnect and return of the original call. Other than this, attended transfer works flawlessly.
> [featuremap]
> blindxfer => #1 ; Blind transfer (default is #)
> disconnect => ** ; Disconnect (default is *)
> ;automon => *1 ; One Touch Record a.k.a. Touch Monitor
> atxfer => ## ; Attended transfer
> parkcall => #0 ; Park call (one step parking)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list