You can use Answer-State, CS_DESTROY won't happen until the call is over. On Sep 23, 2009, at 1:26 PM, Alberto Escudero wrote:
Yes, sounds the best way to go.
I assume that Unique-ID is the unique key to track the call via ESL Unique-ID: a984afd4-a865-11de-a5b4-fb5a867b002c
and Answer-State: the variable to determine if the call is successful?
Or should wait for the reason of CS_DESTROY message. I want to avoid to keep track of the whole state machine to know if a call has been completed successfully or not.
/aep
Unique-ID: 53f51090-a865-11de-a5b4-fb5a867b002c Call-Direction: inbound Presence-Call-Direction: inbound Answer-State: answered
-- Stopping junk mailers is good for the environment
make an esl script that monitors a dir for new files, and push the contents into your same db?
On Wed, Sep 23, 2009 at 10:32 AM, Alberto Escudero <aep.lists@it46.se>wrote:
I am exploring the possibility of building a Dialer that emulates the logic of Call Files in asterisk. A CallerID catcher is creating CUSTOM events that I can store in a database. I can trigger callbacks using ESL but I wonder what is the best way/nicer/geekier to do something like outgoing calls in *