[asterisk-bugs] [Asterisk 0014066]: Calls parked fail to return to the correct phone after timeout
Asterisk Bug Tracker
noreply at bugs.digium.com
Mon Jan 19 16:01:37 CST 2009
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=14066
======================================================================
Reported By: bluefox
Assigned To: otherwiseguy
======================================================================
Project: Asterisk
Issue ID: 14066
Category: Features/Parking
Reproducibility: sometimes
Severity: block
Priority: normal
Status: acknowledged
Target Version: 1.4.23
Asterisk Version: 1.4.22
Regression: No
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2008-12-11 20:01 CST
Last Modified: 2009-01-19 16:01 CST
======================================================================
Summary: Calls parked fail to return to the correct phone
after timeout
Description:
Calls put in park (parkedcalls feature) are put in park and can be picked
up correctly.
BUT when timeout occurs, instead of the phone that put the call on park
ringing back, the phone that was put in the parking extension rings back.
(i.e. the caller phone rings itself). This happens about 20% of the time.
(this describes a SIP Phone - Asterisk - SIP phone call, but failure is
also seen on an external call being put in park. But the result is a weird
hangup instead of a phone calling itself back)
======================================================================
----------------------------------------------------------------------
(0098159) otherwiseguy (administrator) - 2009-01-19 16:01
http://bugs.digium.com/view.php?id=14066#c98159
----------------------------------------------------------------------
Yes, blind transfers worked. Doing an attended transfer where you don't
wait to hear the number and just go ahead and complete it (like you
mentioned doing in your previous message) were what was broken. That is
fixed in the referenced patch. We have started calling that kind of
transfer a "blonde transfer" because it is a complete misuse of the
attended transfer function that causes all kinds of problems for us.
Unfortunately, telling people that it is dumb to use an attended transfer
like a blind transfer isn't a solution.
So, yes, please test the patch and see if it fixes your issues.
Issue History
Date Modified Username Field Change
======================================================================
2009-01-19 16:01 otherwiseguy Note Added: 0098159
======================================================================
More information about the asterisk-bugs
mailing list