I’m trying to write an application to dialout something then forward the
call to a context/exten depending on some parameters.
These questions may be trivial, not for me 😉
You have two items to “join with” in the example you provided; #1
local/00001@internal-99fd,1 is call 99fd on local/00001. If you started 10
calls from local/00001, they would all have differing -xxxx (99fd). #2
UniqueID – part 1 is a constant. Part 2 is a sequence so you can join
events using the constant part 1 and order them with the sequence part 2.
unfortunately this doesn’t add much because only generate another event
but nothing will propagate to Originate child events.
Also the event is fired in asynchronous mode… usually reported later
in the middle of other events when almost of the call flow was already
Which is exactly what I’m doing but I tried to figure out if there was
something more reliable … I refer to the logic not the data structure.
Ignoring for a moment the relationship between events, my conclusion is
still that there is nothing that ensures that very first event that I
will receive after /Response/ to my /Originate/ for that channel is
really fired from my application, I can only guess it is.
The easiest thing to do is to create userevents in your dialplan to passed to AMI details you want to key off of. In the original originate you can set so variable that you pass to various macros and what have you. These then generate userevents that AMI can use to track the flow of the call.