Jim,<br><br> In my application there is only one client listening on the AMI socket, that I developed in C, so its not a problem of overloading. I've read that if the packet sending time out Asterisk will not retry transmitting it, and that is what I think it is happening. Among the solutions I saw was re-coding the AMI event sending function, thing that I don't have the time or the knolodge to do, That's why I'm seeking a way of doing this whithout the AMI interface.
<br> About the kind of event being lost theres no pattern, pointing again to the network timming out problem.<br><br>Any thoughts?<br><br>Best regards,<br>Gabriel<br><br><br><div><span class="gmail_quote">2007/12/10, Jim Capp <
<a href="mailto:jcapp@anteil.com">jcapp@anteil.com</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Gabriel,<br><br> I am working on a project where I have a single java thread reading
<br>all the events and collecting them into "channel variables" which are<br>then returned via http in xml. When processes try to read the xml data,<br>the java process will provide an immediate response and subsequent
<br>requests will block until there is a change in the data.<br><br>This technique smooths over problems with lost events and provides a<br>method for satisfying hundreds of XML requests without impacting the<br>Asterisk server.
<br><br>I am curious to know what kind of events are being lost and whether the<br>problem is one of the Asterisk manager interface being overloaded with<br>too many requests. If not, then I am also concerned about the<br>
effectiveness of my particular solution.<br><br>Can you tell me more about what is being lost?<br><br>Thanks,<br><br>Jim<br><br>Gabriel Ortiz Lour wrote:<br>> Hi all,<br>><br>> I've searched the net for info on AMI losing events and saw that
<br>> this problem persists (as I am experiencing it!). I think that should<br>> be pretty hard to fix it, so I was wondering if you guys could point<br>> me some other way to receive the Asterisk events reliably, (maybe
<br>> trought reading the console directly?). I have an application that<br>> depends on the AMI events to keep track of Agents, Queues, Links...<br>> and when I lose an event.... buuum!<br>><br>> Any help would be appreciatte.
<br>><br>> Thanks,<br>> Gabriel Ortiz<br>><br>><br>><br>> PS.: last tested on Asterisk 1.4.14, didn't tried out the 1.4.15 yet<br>> (didn't see anything related on the changelog).<br>> ------------------------------------------------------------------------
<br>><br>> _______________________________________________<br>> --Bandwidth and Colocation Provided by <a href="http://www.api-digital.com--">http://www.api-digital.com--</a><br>><br>> asterisk-dev mailing list
<br>> To UNSUBSCRIBE or update options visit:<br>> <a href="http://lists.digium.com/mailman/listinfo/asterisk-dev">http://lists.digium.com/mailman/listinfo/asterisk-dev</a><br><br><br>_______________________________________________
<br>--Bandwidth and Colocation Provided by <a href="http://www.api-digital.com--">http://www.api-digital.com--</a><br><br>asterisk-dev mailing list<br>To UNSUBSCRIBE or update options visit:<br> <a href="http://lists.digium.com/mailman/listinfo/asterisk-dev">
http://lists.digium.com/mailman/listinfo/asterisk-dev</a><br></blockquote></div><br>