Details
-
Type:
New Feature
-
Status:
Open
-
Priority:
Minor
-
Resolution: Unresolved
-
Affects Version/s: 1.0.7
-
Fix Version/s: None
-
Component/s: mod_dptools
-
Labels:None
-
Environment:
-
Platform:Linux x86/gcc
-
FreeSWITCH GIT Revision:Merge: 5cebbd4 49f3884
-
Reproduced with GIT HEAD?:3cdb6c98ddcf3b8adbe2e7c9c1bb85f436819341
-
lsb_release:
Description
Create a folowing option/feature to att_xfer call transfer
If someone does an attended transfer, then hangs up before the transferred caller is connected, then by default, the system will try to call back the person that did the transfer.
This option exists in Asterisk
atxferdropcall = no ; If someone does an attended transfer, then hangs up before
; the transferred caller is connected, then by default, the
; system will try to call back the person that did the transfer.
; If this is set to "yes", the callback will
; not be attempted and the transfer will just fail.
; For atxferdropcall=no to work properly, you also need to
; define ATXFER_NULL_TECH in main/features.c. The reason the
; code is not enabled by default is spelled out in the comment
; block near the top of main/features.c describing
; ATXFER_NULL_TECH.
If someone does an attended transfer, then hangs up before the transferred caller is connected, then by default, the system will try to call back the person that did the transfer.
This option exists in Asterisk
atxferdropcall = no ; If someone does an attended transfer, then hangs up before
; the transferred caller is connected, then by default, the
; system will try to call back the person that did the transfer.
; If this is set to "yes", the callback will
; not be attempted and the transfer will just fail.
; For atxferdropcall=no to work properly, you also need to
; define ATXFER_NULL_TECH in main/features.c. The reason the
; code is not enabled by default is spelled out in the comment
; block near the top of main/features.c describing
; ATXFER_NULL_TECH.