On Mon, Dec 1, 2008 at 7:57 PM, Philipp Kempgen <[EMAIL PROTECTED]> wrote: > JD schrieb: > >> As to the idea of piping to a deamon via socket or dbus: how would >> asterisk behave if the daemon froze or worse, it lagged?
I have implemented something similar with the Dial command. We had a customer that required real-time call control where every 60s a new request had to be made to reserve quota to allow the call to continue. Part of that involved sending a Curl request from app_dial.c as soon as the call answered and as soon as the call hungup. It works well and is loosely coupled with Asterisk so that in the worst case the Curl request times out after 2s and Asterisk could take alternative action if necessary. A nice side effect of this approach is that it's possible to get a realtime display of calls in progress from the database rather than having to use MAPI. Ultimatley I think CEL is going to be the approach for tracking call flow. Hopefully the CEL hooks will be two way so I don't have to keep updating my real-time call control patch for each version of Asterisk :-(. Regards, Greyman. _______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users