From: Paul F. <pa...@sm...> - 2006-01-09 02:24:15
|
Hi Stefan, Thanks for your reply. I think I explained my idea poorly. What I meant to say was that in a complex app where you initiate a call using the Manager API, and then communicate back and forth with Asterisk by sending AGI commands from the dialplan -- instead of using AGI, could it be possible to instead communicate back to the Asterisk-Java app (from the DIalPlan) using this new UserEvent mechanism? So my question was not really about changing the way calls are initiated -- they would still be initiated via the Manager API -- but was whether a more event-based way of communicating back to the Java app could be accomplished by sending UserEvents instead of the calling back to the AGI server. In thinking about it more, it seems like it would probably not work too well, since AGI provides commands for doing things directly in Asterisk. Without those AGI commands it might be pointless, but I wasn't sure if the events triggered by the UserEvent could be used to call back with the Manager API and create a Java to Asterisk conversation that way. Anyway, this questions is more out of curiosity. Currently, my Manager/AGI solution works very reliably, but I am continuing to think more about building a CCXML framework on top of Asterisk-Java to provide a a higher level of abstraction for doing call control, and was wondering if the UserEvent thing might provide a more seamless way of providing the Asterisk to Java conversation that will be necessary in getting a CCXML solution to work. Any other ideas on how to go about building this? Thanks again for developing such a great framework! Best Regards, Paul Paul T. Fisher SmartPants Media, Inc. > I started playing with Asterisk 1.2.1 and noticed a new application > =20 > called UserEvent, which is supposed to be able to send arbitrary =20 > events to Asterisk. > The UserEvent is used to send arbitrary events FROM Asterisk (i.e. from the dialplan) to your Manager API based application. > My question is whether this could be used to =20 > place complex outbound (and even Call Control) and IVR > functionality =20 > without resorting to AGI. In other words, right now I used the =20 > Manager interface to trigger a call, and then communicate back and =20 > forth between the dial plan and AGI to get stuff done. WIth this > new =20 > application, could I just use the Manager, or will this be too slow? > No, you cant use it for that purpose. To originate a new call there are only two possibilities: The Manager API and .call files. The prefered way is the Manager API. =3DStefan |