Here are 3 ways:<br><br>1) subscribe to the BACKGROUND_JOB event and find the one with the same job-uuid<br>    then the body of that message is the output from your backgrounded FSAPI call which in the case<br>    of an originate will contain the uuid of the actual channel.<br>
<br>2) You can do as suggested and add {myvar=myval} prefix to the dialstring and look for <br>    myvar in the channel_originate event.<br><br>3) Finally you can choose the uuid in advance providing it&#39;s actually unique using:<br>
<br>    {origination_uuid=XYZ}<br><br>    You can use your own code to generate uuid (make sure they are unique) or <br>    ask the core to give you a new uuid with the create_uuid FSAPI call.<br><br><br><br><br><div class="gmail_quote">
On Wed, May 27, 2009 at 4:46 AM, Peter P GMX <span dir="ltr">&lt;<a href="mailto:Prometheus001@gmx.net">Prometheus001@gmx.net</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I want to do the following:<br>
Originate a call via event_socket, I get back a job_uuid. Then I want to<br>
control the call when it&#39;s established (2 call legs).<br>
Scanning the variables of the 2 call legs I currentyl cannot see any<br>
relation between the job_uuid and the uuid of the resulting call legs.<br>
I may set a variable with my own unique id while originating a call, but<br>
finding the calls later on and dumping the variables fo all channels is<br>
very time consuming in terms of CPU.<br>
<br>
A workaround I tried, is to set caller-id or caller-id-number with a<br>
unique id. This works, but has the known side effects of not having a<br>
valid caller-id or caller-id-number.<br>
<br>
So my question is: Has anybody an idea how to build a relationship<br>
between job_uuid and the resulting call legs which does not require<br>
dumping the variables of all channels?<br>
<br>
Best regards<br>
Peter<br>
<br>
<br>
<br>
_______________________________________________<br>
Freeswitch-users mailing list<br>
<a href="mailto:Freeswitch-users@lists.freeswitch.org">Freeswitch-users@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Anthony Minessale II<br><br>FreeSWITCH <a href="http://www.freeswitch.org/">http://www.freeswitch.org/</a><br>ClueCon <a href="http://www.cluecon.com/">http://www.cluecon.com/</a><br>
<br>AIM: anthm<br><a href="mailto:MSN%3Aanthony_minessale@hotmail.com">MSN:anthony_minessale@hotmail.com</a><br>GTALK/JABBER/<a href="mailto:PAYPAL%3Aanthony.minessale@gmail.com">PAYPAL:anthony.minessale@gmail.com</a><br>
IRC: <a href="http://irc.freenode.net">irc.freenode.net</a> #freeswitch<br><br>FreeSWITCH Developer Conference<br><a href="mailto:sip%3A888@conference.freeswitch.org">sip:888@conference.freeswitch.org</a><br><a href="http://iax:guest@conference.freeswitch.org/888">iax:guest@conference.freeswitch.org/888</a><br>
<a href="mailto:googletalk%3Aconf%2B888@conference.freeswitch.org">googletalk:conf+888@conference.freeswitch.org</a><br>pstn:213-799-1400<br>