[asterisk-bugs] [Asterisk 0018168]: Duplicated event on AMI interface
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Oct 20 04:21:39 CDT 2010
The following issue has been REOPENED.
======================================================================
https://issues.asterisk.org/view.php?id=18168
======================================================================
Reported By: FeyFre
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 18168
Category: Core/ManagerInterface
Reproducibility: always
Severity: major
Priority: normal
Status: new
Asterisk Version: 1.8.0-rc2
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-10-19 17:57 CDT
Last Modified: 2010-10-20 04:21 CDT
======================================================================
Summary: Duplicated event on AMI interface
Description:
Steps to reproduce:
1. Enable AMI in manager.conf (and configure network)
2. Start Asterisk
3. Connect to Asterisk
4. Login into AMI. We will receive FullyBooted event.
5. Do not close first connection. Connect to Asterisk again.
6. Login into AMI. We will receive FullyBooted event here also.
ISSUE: FullyBooted event in step 6 will be sent to first AMI connection
also. Such behaviour is unacceptable. Software which controls Asterisk over
AMI can misunderstood this event and broke whole system.(No good for
Asterisk either)
======================================================================
----------------------------------------------------------------------
(0128220) FeyFre (reporter) - 2010-10-20 04:21
https://issues.asterisk.org/view.php?id=18168#c128220
----------------------------------------------------------------------
But I require this event. Without it software connected to Asterisk via AMI
will be unusable. But I require it once, not thousands times per
connection(which is guaranteed because I will connect dozens of clients to
Asterisk simultaneously). Filter will no help it.
Issue History
Date Modified Username Field Change
======================================================================
2010-10-20 04:21 FeyFre Note Added: 0128220
2010-10-20 04:21 FeyFre Status closed => new
2010-10-20 04:21 FeyFre Resolution no change required =>
reopened
======================================================================
More information about the asterisk-bugs
mailing list