[asterisk-bugs] [Asterisk 0018168]: Duplicated event on AMI interface
Asterisk Bug Tracker
noreply at bugs.digium.com
Tue Oct 19 18:20:24 CDT 2010
The following issue has been CLOSED
======================================================================
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: closed
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:
Resolution: open
Fixed in Version:
======================================================================
Date Submitted: 2010-10-19 17:57 CDT
Last Modified: 2010-10-19 18:20 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)
======================================================================
----------------------------------------------------------------------
(0128215) pabelanger (manager) - 2010-10-19 18:20
https://issues.asterisk.org/view.php?id=18168#c128215
----------------------------------------------------------------------
If you don't want the event, create an event filter for your manager user:
eventfilter=!Event: FullyBooted
---
Thanks for your comments. This does not appear to be a bug report and we
are closing it. We appreciate the difficulties you are facing, but it would
make more sense to raise your question in the support tracker,
http://www.asterisk.org/support
Issue History
Date Modified Username Field Change
======================================================================
2010-10-19 18:20 pabelanger Note Added: 0128215
2010-10-19 18:20 pabelanger Status new => closed
======================================================================
More information about the asterisk-bugs
mailing list