[asterisk-bugs] [Asterisk 0012854]: Unparked caller has ability to transfer
Asterisk Bug Tracker
noreply at bugs.digium.com
Fri Oct 10 09:37:31 CDT 2008
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=12854
======================================================================
Reported By: davidw
Assigned To: otherwiseguy
======================================================================
Project: Asterisk
Issue ID: 12854
Category: Resources/res_features
Reproducibility: always
Severity: major
Priority: normal
Status: feedback
Asterisk Version: SVN
SVN Branch (only for SVN checkouts, not tarball releases): 1.4
SVN Revision (number only!): 122589
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 2008-06-13 13:12 CDT
Last Modified: 2008-10-10 09:37 CDT
======================================================================
Summary: Unparked caller has ability to transfer
Description:
Please re-open http://bugs.digium.com/view.php?id=9565. It was closed in favour
of http://bugs.digium.com/view.php?id=11898, but the fix for
that did not actually address the issue in
http://bugs.digium.com/view.php?id=9565.
======================================================================
----------------------------------------------------------------------
(0093473) davidw (reporter) - 2008-10-10 09:37
http://bugs.digium.com/view.php?id=12854#c93473
----------------------------------------------------------------------
It won't build against 1.4.21.2, so I tried 1.4.22 (which is probably going
to be our fallback, if we fail to port to 1.6) and got:
-- Channel SIP/djw-messenger-092c98b8 connected to parked call 701
[Oct 10 15:26:42] NOTICE[32256]: res_features.c:2077 park_exec: Couldn't
find di
alfeatures!
when doing the simple case with 700 and 701.
There was no re-invite.
With the actual application use, there was no warning, but still no
re-invite.
This whole dialfeatures thing seems to be new, but, speculating, could we
have a situation where, because we use Originate, to an application,
Asterisk has dial features left over from a Dial command earlier in the
call. We did experiment with enabling transfer at one point in the call to
support a secondary requirement. I.E. should dial features maybe be
cleared on entering the dial plan?
I assume the failure in the simple case is because no Dial command has
ever been issued.
Issue History
Date Modified Username Field Change
======================================================================
2008-10-10 09:37 davidw Note Added: 0093473
======================================================================
More information about the asterisk-bugs
mailing list