[asterisk-bugs] [Asterisk 0018379]: attended transfer weird behaviour

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18379 
====================================================================== 
Reported By:                gincantalupo
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18379
Category:                   Applications/app_dial
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.8.1-rc1 
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-25 11:35 CST
Last Modified:              2010-12-14 04:43 CST
====================================================================== 
Summary:                    attended transfer weird behaviour
Description: 
Just installed 1.8.1-rc1 and tried the attended transfer function with 3
snoms (firmware 8.x), A,B and C. When A calls B and B transfers to C but C
is busy or does not answer, 'pbx-invalid.gsm' sound is played...but the
called number is right!

Another test: when I try to transfer the call to a wrong number I get this
message:
WARNING[31448]: features.c:1861 builtin_atxfer: Did not read data
and after that the call is bounced back to the transferrer (shouldn't
Asterisk say invalid extension???)

My test extensions:
exten => 12,1,Dial(SIP/81,5,tT)
exten => 12,2,NoOp(${DIALSTATUS})
exten => 12,3,Hangup

exten => 14,1,Dial(SIP/8,5,tT)
exten => 14,2,NoOp(${DIALSTATUS})
exten => 14,3,Hangup

exten => 17,1,Dial(SIP/70,5,tT)
exten => 17,2,NoOp(${DIALSTATUS})
exten => 17,3,Hangup

======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0018254 Attended transfer failure
related to          0017999 Issues with DTMF triggered attended tra...
====================================================================== 

---------------------------------------------------------------------- 
 (0129591) gincantalupo (reporter) - 2010-12-14 04:43
 https://issues.asterisk.org/view.php?id=18379#c129591 
---------------------------------------------------------------------- 
Yes, knkcn, you are right, it works as you say but if you call a
non-existent exten, Asterisk prints out a NOTICE while if you make a
transfer, you have a different behaviour: you need to have _X. extension in
your dialplan to get a pbx-invalid message. Isn't it weird? Isn't
transferring a call a sort of "second call"? Shouldn't it pass thru the
same dialplan (the context is the same)? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-12-14 04:43 gincantalupo   Note Added: 0129591                          
======================================================================