[asterisk-bugs] [Asterisk 0015871]: [patch] Channels that was placed in "meetme" in dialing state do not leave application in CONGESTION case
Asterisk Bug Tracker
noreply at bugs.digium.com
Thu Sep 17 03:55:02 CDT 2009
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=15871
======================================================================
Reported By: Ivan
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 15871
Category: Applications/app_meetme
Reproducibility: always
Severity: minor
Priority: normal
Status: ready for testing
Asterisk Version: SVN
Regression: No
SVN Branch (only for SVN checkouts, not tarball releases): trunk
SVN Revision (number only!): 217595
Request Review:
======================================================================
Date Submitted: 2009-09-10 07:47 CDT
Last Modified: 2009-09-17 03:55 CDT
======================================================================
Summary: [patch] Channels that was placed in "meetme" in
dialing state do not leave application in CONGESTION case
Description:
In the case of outgoing call is not completed (CONGESTION or BUSY happens)
the channel stay in "meeme" application (no HANGUP happens). In the 1.6.1.x
and trunk is the same.
======================================================================
----------------------------------------------------------------------
(0110860) Ivan (reporter) - 2009-09-17 03:55
https://issues.asterisk.org/view.php?id=15871#c110860
----------------------------------------------------------------------
For testing please use meetme_congestion_trunk_v2.patch. The misprint
happens because of which has turned out takes place to be small memory
leak. But the logic is corrected.
Issue History
Date Modified Username Field Change
======================================================================
2009-09-17 03:55 Ivan Note Added: 0110860
======================================================================
More information about the asterisk-bugs
mailing list