like i said, the inbound socket just needs to know the uuid of each leg <br>and it can send the command to bridge them:<br><br>api uuid_bridge <uuid of leg a> <uuid of leg b><br><br>as soon as you do this the legs will be bridged.<br>
<br><br><br><br><br><div class="gmail_quote">On Tue, Oct 21, 2008 at 11:26 AM, Dennis <span dir="ltr"><<a href="mailto:odermann@googlemail.com">odermann@googlemail.com</a>></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 think I have problems to understand what is happening in detail.<br>
<br>
Just a short explaination, of what we are doing. We use socket<br>
outbound and have a PHP script, which is listening to "myevents". If a<br>
new call is coming in, we fork the PHP script in a new process to<br>
handle this call. Now we have a new "inbound", which we can handle<br>
with fs and the PHP script.<br>
In example, we play a file for the caller. After we have played the<br>
file, we want to call to the dialed number. But we do not want to<br>
connect both call immediately. We originate to the target number,<br>
because we want to play a file, before we connect, perhaps. A "bridge"<br>
would connect both legs immediately. Therefore we need to originate.<br>
<br>
If we originate, the originated call will run in a new child process<br>
in PHP (this does not happen with "bridge").<br>
<br>
How could our PHP "inbound"-process know, what the "outbound"-process<br>
is doing? They have nothing to do with each other.<br>
<br>
We have an inbound and then we play a file. The current process<br>
"knows", that we have to make an originate, play a file and then<br>
bridge. But the "current" process does not know, when the playfile is<br>
done and the bridge can be executed.<br>
<br>
So how could we "control both sessions individually"?<br>
<br>
Sorry for all these questions, but we have serious problems, because<br>
we can not find the answers.<br>
<br>
Thanks<br>
Dennis<br>
<br>
<br>
2008/10/21 Anthony Minessale <<a href="mailto:anthony.minessale@gmail.com">anthony.minessale@gmail.com</a>>:<br>
<div><div></div><div class="Wj3C7c">> once you are controlling both sessions individually use api to send the<br>
> uuid_bridge command:<br>
><br>
> api uuid_bridge <uuid of leg a> <uuid of leg b><br>
><br>
><br>
><br>
> On Tue, Oct 21, 2008 at 9:37 AM, Dennis <<a href="mailto:odermann@googlemail.com">odermann@googlemail.com</a>> wrote:<br>
>><br>
>> 2008/10/20 Anthony Minessale <<a href="mailto:anthony.minessale@gmail.com">anthony.minessale@gmail.com</a>>:<br>
>><br>
>> >> A more precise question about inbound/outbound: I want to read out the<br>
>> >> events from freeswitch with my PHP-script and then tell freeswitch,<br>
>> >> what to do next. I have the feeling, that "outbound" is the way to go.<br>
>> >> But of course I also want to be able to start calls. Can I do this by<br>
>> >> using "outbound"?<br>
>> ><br>
>> > yes<br>
>><br>
>> But what is the difference between "bridge" and "originate" in<br>
>> handling dials? "bridge" connects two calls together, but "originate"<br>
>> seems to be a part of "bridge".<br>
>> If we make a "bridge", both legs seem to bee in the same session, when<br>
>> using socked outbound.<br>
>><br>
>> We make a "bridge" as follows:<br>
>> $this->invokeMessage("bridge", "sofia/internal/<a href="mailto:1001@192.168.1.5">1001@192.168.1.5</a>");<br>
>><br>
>> When we use "originate" (which we prefer, because we do not want to<br>
>> connect both call with each other immediately), we use the following<br>
>> command:<br>
>> $this->invokeCommand("API originate<br>
>> {origination_caller_id_number=123455}sofia/internal/<a href="mailto:1001@192.168.1.5">1001@192.168.1.5</a><br>
>> 123");<br>
>><br>
>> The problem is, that the new call is now in another call-session and<br>
>> we do not know how to bring the calls together.<br>
>><br>
>> Does it have something to do with "API"? If yes, is there a way to use<br>
>> "originate" with "sendmsg"?<br>
<br>
</div></div><div><div></div><div class="Wj3C7c">_______________________________________________<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>
</div></div></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>