<div>I would advise against some of those though. Asterisk has a habbit of creating Zombie and Masq channels all the time. It becomes hard to figure out which ones are which. I've had enough problems trying to match the Channel information from NewCallerID with the channel name from LINK as a channel gets bridged. For me NEWSTATE ends up providing me too much information and it's hard for me to parse. LINK does great for my needs.
</div>
<div> </div>
<div>I still get the impression though that the Manager interface isn't needed in your case if the NewCallerID is the only state information you need. But just checking the LINK event infromation, it does include CID information and from there you can load the data on your GUI. Clean package.
</div>
<div> </div>
<div>Finally, what I did during the development of my application was to dump all EVENT logs to disk and then go through them to figure out what events I needed to act on. Someone should make a nice CLI based application to view all events flowing through as a list, but be able to select them to see the RAW data. And some filtering.
<br><br> </div>
<div><span class="gmail_quote">On 9/10/07, <b class="gmail_sendername">Richard Lyman</b> <<a href="mailto:pchammer@dynx.net">pchammer@dynx.net</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">TP'n to follow flow.<br><br>there are a few things you can look at<br><br>Newstate<br>Newchannel<br>Newcallerid
<br>Newexten<br><br>i agree with Nicholas, that you can look at Link/Unlink for bridging<br>info, but when you can also trigger off of things like 'AgentCalled' if<br>you use queues.<br><br>there are a few examples of Event triggers i use in this
<br><a href="http://dynx.net/ASTERISK/gnudialer/display4/">http://dynx.net/ASTERISK/gnudialer/display4/</a><br><a href="http://dynx.net/ASTERISK/gnudialer/display4/AstDisplay.java">http://dynx.net/ASTERISK/gnudialer/display4/AstDisplay.java
</a><br><br>this is just some java app to display channel state changes. (it was<br>originally designed for Zap (only) channels, but was mod'd for others,<br>the 'others' part is not pretty)<br><br>as with what Nicholas stated, you could easily do a 'UserEvent' from the
<br>dialplan and use that Event as a trigger in your app to make sure 'what<br>you want, when you want it' is there for the taking.<br><br></blockquote></div>