[asterisk-bugs] [Asterisk 0018395]: C should not receive request call again after C cancel if B blind transfer using atxfer call C

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18395 
====================================================================== 
Reported By:                shihchuan
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18395
Category:                   Features
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.8.0 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-11-29 04:31 CST
Last Modified:              2010-12-02 21:53 CST
====================================================================== 
Summary:                    C should not receive request call again after C
cancel if B blind transfer using atxfer call C
Description: 
call limit of B is 2
1. A call B, B answered
2. B *97(atxfer) call C, C rining (no aswer)
3. B hangup 
4. C cancel 
5. B receive request call (It's ok)

call limit of B is 1
1. A call B, B answered
2. B *97(atxfer) call C, C rining (no aswer)
3. B hangup 
4. C cancel call
5. C receive request call again, C ringing (behavior isn't reasonable)
6. C cancel call again 
7. C receive request call again, C ringing (behavior isn't reasonable)

Because B reached call limit, C receive request call again.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0017273 atxfer *2 channel dahdi FXS no hangup
====================================================================== 

---------------------------------------------------------------------- 
 (0129289) rmudgett (administrator) - 2010-12-02 21:53
 https://issues.asterisk.org/view.php?id=18395#c129289 
---------------------------------------------------------------------- 
It is intended for Party B to be called back if Party C does not answer if
atxferdropcall is no.  It is also intended to bounce back and forth between
Party B and Party C for atxfercallbackretries times to try to get someone
to take the Party A call.

However, the call linked to Party B is not completely hung up yet during
the transfer.  This is why Party B has reached its call limit and is a bug. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-12-02 21:53 rmudgett       Note Added: 0129289                          
======================================================================