Recently the API behaviour changed for Erlang such that when you initiate a call, the routine immediately returns with a UUID of the launched call, rather than waiting for the call to be answered. I've been able to program for this behaviour in the call-connected case, but I'm at a loss as to what to do for detecting calls that go unanswered, time out, or which cannot be placed for various technical reasons. As a result, my call queue is filling up and choking -- I only launch so many calls at a time, and only the connected calls are getting properly processed. Unanswered and timed out calls are getting "stuck" because I don't know what events to catch and how to evaluate them. The old behaviour wasn't event-based and thereby easier to program -- but I can definitely see the advantages of shifting to a pure event-driven model. I just need to learn how to _use_ it. Thanks for any assistance you can provide.