VoIP Mailing List Archives

[odermann at googlemail...]

Hi,

I am new to freeswitch and found out quite a lot of things the past
days. But there are still many questions left, which I can't figure
out without some help.

I want to use freeswitch for a project, where freeswitch should
communicate with PHP-scripts and receive the messages to different
events.
I was told to use socket and found some quite helpful PHP-scripts in
this mailing list. One was for using socket outbound, one was for
socket inbound.

I would like to ask, which direction is the best oder most reliable?

When using socket outbound, freeswitch connects to the PHP-script, the
PHP-script forks and is registered to "myevents" (events all seems to
give me all events from all connections).
One of the problems I have with "outbound" is, that I won't get all
events. For example I do not get "hangup", because the socket
connection seems to die, before freeswitch sends the last command when
hanging up. With "ringing" the problem seems to be the same.
I only get a "hangup", when I register to "events all" and have to
active calls. When one of the two calls hangs up, i can see it by
printing out all events in the PHP-script.

When using socket inbound, the PHP-script does not fork and seems to
handle all events for all calls. What, if a request hangs for one
call? Do all the other calls have to wait, till the other call is
killed?

Another thing ist the events "heartbeat". Will I get the "heartbeat"
for every single call or just one heartbeat for all calls?

I feel that I am missing some basic knowledge about sockets and
freeswitch. Could someone help to find the right way, please?

Thanks and kind regards
Dennis

_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org

[ivan at myrvold.org]

Den 17. okt.. 2008 kl. 14:45 skrev Dennis:

[gilbertandrew at mac.com]

Big caveat on fs inexperience here, but from doc my guess is:

Outbound is likely a good choice for dialplan application scenarios,
for example a call out to external app for a specific route or route
set. And Inbound is perhaps better at driving the switch through an
external application, say to do origination. But I have no history, so
am not an authority.

As for not hanging/blocking using Inbound the documentation/wiki seems
to address this in the BGAPI section:

http://wiki.freeswitch.org/wiki/Event_Socket#Inbound

And I believe there have been threads on the list about it before.

The netcat examples also look quite promising, you may want to work
scenarios through with that before diving into your PHP app.

Andy



On Oct 17, 2008, at 11:41 AM, Ivan C Myrvold wrote:

[anthony.minessale at g...]

On Fri, Oct 17, 2008 at 7:45 AM, Dennis <odermann@googlemail.com (odermann@googlemail.com)> wrote:

[odermann at googlemail...]

[odermann at googlemail...]

[anthony.minessale at g...]

On Sat, Oct 18, 2008 at 3:50 AM, Dennis <odermann@googlemail.com (odermann@googlemail.com)> wrote:

[odermann at googlemail...]

2008/10/20 Anthony Minessale <anthony.minessale@gmail.com>:

[anthony.minessale at g...]

once you are controlling both sessions individually use api to send the uuid_bridge command:

api uuid_bridge <uuid of leg a> <uuid of leg b>



On Tue, Oct 21, 2008 at 9:37 AM, Dennis <odermann@googlemail.com (odermann@googlemail.com)> wrote:

[odermann at googlemail...]

I think I have problems to understand what is happening in detail.

Just a short explaination, of what we are doing. We use socket
outbound and have a PHP script, which is listening to "myevents". If a
new call is coming in, we fork the PHP script in a new process to
handle this call. Now we have a new "inbound", which we can handle
with fs and the PHP script.
In example, we play a file for the caller. After we have played the
file, we want to call to the dialed number. But we do not want to
connect both call immediately. We originate to the target number,
because we want to play a file, before we connect, perhaps. A "bridge"
would connect both legs immediately. Therefore we need to originate.

If we originate, the originated call will run in a new child process
in PHP (this does not happen with "bridge").

How could our PHP "inbound"-process know, what the "outbound"-process
is doing? They have nothing to do with each other.

We have an inbound and then we play a file. The current process
"knows", that we have to make an originate, play a file and then
bridge. But the "current" process does not know, when the playfile is
done and the bridge can be executed.

So how could we "control both sessions individually"?

Sorry for all these questions, but we have serious problems, because
we can not find the answers.

Thanks
Dennis


2008/10/21 Anthony Minessale <anthony.minessale@gmail.com>:

[msc at freeswitch.org]

So you need to create a second call leg that is somewhat independent of the first leg, so that you can play a file, and *then* bridge the new leg to the "current" leg?

I just want to make sure that I grok what you are trying to accomplish. Also, if you haven't put your dialplan and script in pastebin then it would be good to do so for the sake of everyone being on the same page. (pastebin.freeswitch.org)

-MC

On Tue, Oct 21, 2008 at 9:26 AM, Dennis <odermann@googlemail.com (odermann@googlemail.com)> wrote:

[dave at 3c.co.uk]

Hi Dennis

[anthony.minessale at g...]

like i said, the inbound socket just needs to know the uuid of each leg
and it can send the command to bridge them:

api uuid_bridge <uuid of leg a> <uuid of leg b>

as soon as you do this the legs will be bridged.





On Tue, Oct 21, 2008 at 11:26 AM, Dennis <odermann@googlemail.com (odermann@googlemail.com)> wrote:

[odermann at googlemail...]

2008/10/21 Michael Collins <msc@freeswitch.org>:

[odermann at googlemail...]

Ahh, help, I found something out about my question and would like to
know, if I am really in trouble...
The problem is, when one does not read every single word.

Till now I always worked with socket outbound and a PHP script, which
forks the different processes. Everything seemed to work great (in my
little test environment) and I am at the point, where I could do most
if not all of the things I wanted to do with fs.

Today I made an originate over api, passed the inbound uuid to the
outbound and could control different things - I also could bridge both
calls. Great, I thought. Then I wanted to start the next little test:
Start a playfile from the outbound, so that the inbound can hear it...
Negative!
It seems to be impossible to send a playfile or hangup (and more) over
api. Both command seem only to be available with sendmsg. But sendmsg
<uuid> does not work with socket outbound, at least not from the
outbound to the inbound.

show application and show api tell a lot and I do know, when I stopped
thinking Perhaps my mistakes came up, because I started to use fs
one and a half week ago - I don't know.

So do I have to switch completely to socket inbound or is there a way
to continue using socket outbound? Or will I perhaps find out, that I
can not do some things with socket inbound, which I could do with
socket outbound?

In the moment I just do not know which way to go...

Dennis

_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org