[asterisk-bugs] [Asterisk 0013747]: Indications are not passed from old peer to new peer during masquerade
Asterisk Bug Tracker
noreply at bugs.digium.com
Fri Oct 24 10:01:49 CDT 2008
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=13747
======================================================================
Reported By: davidw
Assigned To: putnopvut
======================================================================
Project: Asterisk
Issue ID: 13747
Category: Core/Channels
Reproducibility: always
Severity: major
Priority: normal
Status: acknowledged
Asterisk Version: 1.6.0
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 2008-10-20 13:04 CDT
Last Modified: 2008-10-24 10:01 CDT
======================================================================
Summary: Indications are not passed from old peer to new peer
during masquerade
Description:
We want to transfer a channel that is already indicating (typically
ringing) to a parked channel, which we do with AMI Originate. When we do
this, the person on the parked channel has MOH changed to silence until the
ringing channel answers, or otherwise changes indication.
It looks to me as though there may have been some attempt to support this,
but it looks like it copies the indications at the wrong end of the
masquerade.
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0012548 SIP channel protocol illegally reverses...
======================================================================
----------------------------------------------------------------------
(0094237) davidw (reporter) - 2008-10-24 10:01
http://bugs.digium.com/view.php?id=13747#c94237
----------------------------------------------------------------------
Would it be safe to treat RINGING like hold, here, in ast_generic_bridge??
4264 switch (f->subclass) {
4265 case AST_CONTROL_HOLD:
4266 case AST_CONTROL_UNHOLD:
4267 case AST_CONTROL_VIDUPDATE:
4268 case AST_CONTROL_SRCUPDATE:
4269 ast_indicate_data(other,
f->subclass, f-
Issue History
Date Modified Username Field Change
======================================================================
2008-10-24 10:01 davidw Note Added: 0094237
======================================================================
More information about the asterisk-bugs
mailing list