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: > > Den 17. okt.. 2008 kl. 14:45 skrev Dennis: > >> 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. > > Yes, this is true, I also have the same issue. But I am using the > time the connection died as the event to set the hangup time in my own > application. > But you of course do not get the hangup cause here. > > I haven't had any problem with "ringing", though. > > Ivan > > _______________________________________________ > 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 _______________________________________________ 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