[asterisk-bugs] [Asterisk 0018168]: [patch] Duplicated event on AMI interface

[Asterisk Bug Tracker]

The following issue has been RESOLVED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18168 
====================================================================== 
Reported By:                FeyFre
Assigned To:                twilson
====================================================================== 
Project:                    Asterisk
Issue ID:                   18168
Category:                   Core/ManagerInterface
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     resolved
Asterisk Version:           1.8.0-rc2 
JIRA:                       SWP-2880 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             2010-10-19 17:57 CDT
Last Modified:              2011-02-24 11:42 CST
====================================================================== 
Summary:                    [patch] 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)
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-02-24 11:42 svnbot         Status                   assigned => resolved
2011-02-24 11:42 svnbot         Resolution               reopened => fixed   
======================================================================