[asterisk-bugs] [Asterisk 0016856]: Blind transfers initiated from calling party aren't disconncted

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16856 
====================================================================== 
Reported By:                rsw686
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16856
Category:                   Applications/app_transfer
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           1.6.1.14 
JIRA:                       SWP-951 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-02-17 14:08 CST
Last Modified:              2010-02-23 22:52 CST
====================================================================== 
Summary:                    Blind transfers initiated from calling party aren't
disconncted
Description: 
Employee A calls a customer and talks for a few minutes. The customer asks
to talk to someone in another depart. Employee A does a blind transfer with
## to Employee B. The result is Employee B is connected to the customer.
However Employee A receives the all circuits are busy now message. What
should happen is Employee A is disconnected. I was originally using
Asterisk 1.6.1.4, but have tested Asterisk 1.6.1.14 with the same result.
====================================================================== 

---------------------------------------------------------------------- 
 (0118436) rsw686 (reporter) - 2010-02-23 22:52
 https://issues.asterisk.org/view.php?id=16856#c118436 
---------------------------------------------------------------------- 
I'm not sure if this is an Asterisk or FreePBX issue.

FreePBX 2.6.0.1 has a macro-dialout-trunk which contains

exten =>
s,n,Dial(${OUT_${DIAL_TRUNK}}/${OUTNUM},300,${DIAL_TRUNK_OPTIONS})
exten => s,n,Goto(s-${DIALSTATUS},1)

For calls when you hangup it looks like Dial falls through to the end of
the macro and runs

exten => h,1,Macro(hangupcall,)

However for transfers it returns the status ANSWER which runs

exten => _s-.,1,GotoIf($["x${OUTFAIL_${ARG1}}" = "x"]?noreport)
exten => _s-.,n,AGI(${OUTFAIL_${ARG1}})
exten => _s-.,n(noreport),Noop(TRUNK Dial failed due to ${DIALSTATUS} -
failing through to other trunks)

I added in a cause for ANSWER, which solved the issue.

exten => s-ANSWER,1,Noop(Dial completed with trunk reporting ANSWER -
hanging up)
exten => s-ANSWER,n,Macro(hangupcall,)

I posted this as a bug, before I found out the above, and was told that
they tested my scenario on Asterisk 1.4 and it was working. The ended up
closing the bug report. I am wondering if the Dial behavior changed between
Asterisk 1.4 and 1.6.1 for this case? Should I be making another bug report
to FreePBX? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-02-23 22:52 rsw686         Note Added: 0118436                          
======================================================================