<[email protected]> writes: > 3) Hook into the AMI and parse the ExtensionStatusEvent which I think gives > me what I want.
This is the "traditional" way, I believe. The challenge with AMI is that it is becoming a high-bandwidth channel. If you're only interested in one event type, you will spend quite a bit of CPU time just discarding uninteresting events. Perhaps it would be possible to make events more granular, instead of just on/off? Apart from that AMI works fine. /Benny _______________________________________________ -- 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
