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

Asterisk Bug Tracker noreply at bugs.digium.com
Thu Feb 24 11:59:34 CST 2011


A NOTE has been added to this issue. 
====================================================================== 
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:                     closed
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:59 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)
====================================================================== 

---------------------------------------------------------------------- 
 (0132371) svnbot (reporter) - 2011-02-24 11:59
 https://issues.asterisk.org/view.php?id=18168#c132371 
---------------------------------------------------------------------- 
Repository: asterisk
Revision: 308816

_U  trunk/
U   trunk/main/manager.c

------------------------------------------------------------------------
r308816 | twilson | 2011-02-24 11:59:33 -0600 (Thu, 24 Feb 2011) | 33
lines

Merged revisions 308815 via svnmerge from 
https://origsvn.digium.com/svn/asterisk/branches/1.8

................
  r308815 | twilson | 2011-02-24 11:57:18 -0600 (Thu, 24 Feb 2011) | 26
lines
  
  Merged revisions 308814 via svnmerge from 
  https://origsvn.digium.com/svn/asterisk/branches/1.6.2
  
  ................
    r308814 | twilson | 2011-02-24 11:54:49 -0600 (Thu, 24 Feb 2011) | 19
lines
    
    Merged revisions 308813 via svnmerge from 
    https://origsvn.digium.com/svn/asterisk/branches/1.4
    
    ........
      r308813 | twilson | 2011-02-24 11:42:16 -0600 (Thu, 24 Feb 2011) |
12 lines
      
      Don't broadcast FullyBooted to every AMI connection
      
      The FullyBooted event should not be sent to every AMI connection
every
      time someone connects via AMI. It should only be sent to the user
who
      just connected.
      
      (closes issue https://issues.asterisk.org/view.php?id=18168)
      Reported by: FeyFre
      Patches: 
            bug0018168.patch uploaded by FeyFre (license 1142)
      Tested by: FeyFre, twilson
    ........
  ................
................

------------------------------------------------------------------------

http://svn.digium.com/view/asterisk?view=rev&revision=308816 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-02-24 11:59 svnbot         Checkin                                      
2011-02-24 11:59 svnbot         Note Added: 0132371                          
======================================================================




More information about the asterisk-bugs mailing list