[asterisk-bugs] [Asterisk 0018379]: attended transfer weird behaviour
Asterisk Bug Tracker
noreply at bugs.digium.com
Mon Dec 13 22:07:14 CST 2010
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-13 22:07 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...
======================================================================
----------------------------------------------------------------------
(0129589) knkcn (reporter) - 2010-12-13 22:07
https://issues.asterisk.org/view.php?id=18379#c129589
----------------------------------------------------------------------
I think you second test lacks some exten. As my understand, if the transfer
input cann't match any exten under the dialplan, the transfer function will
think nothing was inpu. That is why there is "WARNING[31448]:
features.c:1861 builtin_atxfer: Did not read data" even you pressed some
key.
I believe if you add some exten like "exten => _X.,1,NOOP" you will get
"pbx-invalid.gsm" played
Issue History
Date Modified Username Field Change
======================================================================
2010-12-13 22:07 knkcn Note Added: 0129589
======================================================================
More information about the asterisk-bugs
mailing list