Where did you read all of that because it's out of date.
All of the above is deprecated in favor of ESL and the perl module for ESL.
That should have been much easier to find than the stuff you are referencing since ESL was even mentioned
in this very thread.

What threading issues are you having in perl?  Are you actually going to use perl for a threaded app?


On Tue, May 25, 2010 at 10:03 AM, Phone <phone.bytes@gmail.com> wrote:
Sorry to revive this already long thread...but I think the history is
relevant as I am still stuck on the approach.

I came across the perl POE "POE::Filter::FSSocket" and thought I might
learn and use it.  Thought it might be nice to help with the
socket/threading issues...and avoid having to get down and dirty with
them.  However, in looking closer it appeared that nothing had really
happened on it for about 4 years...then I read a post  indicating that
it was out of date and that Anthony's FreeSWITCH::CLient would be a
better choice.  I have been able to try out the perl FreeSWITCH Client
example on the wiki and  send out some calls using "bgapi"...but I am
not sure how to handle the multiple threads.  Would I just deal with all
events in a loop similar to what is in the wiki client example?

Now I am really confused as to how to tackle this.  Not an expert with
any particular language...but it seems that scripting may be nice from a
maintenance point of view??

Any further thoughts or examples to get me on my way?  I am really open
as to the approach to take.

Thanks

So now I don't know what direction to go to get this started.
Jan Berger wrote:
> You don't need to pull a db these day's, you can use triggers to signal your
> application - a bit depending on what db you use and what scripting they
> offer beyond SQL.
>
> -----Original Message-----
> From: freeswitch-users-bounces@lists.freeswitch.org
> [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Phone
> Sent: 13. mai 2010 01:46
> To: freeswitch-users@lists.freeswitch.org
> Subject: Re: [Freeswitch-users] Questions on Building an application for
> FreeSWITCH
>
> Thanks for sharing your experience.
>
> We would like to get over to linux with this.
>
> I am still trying to get my head around how this generally works.  I
> guess we would write a client to sit and run on the linux box where it
> could periodically check the DB and then talk sockets to FS to make the
> calls?
>
> Can you point me to examples of talking sockets?
>
>
>
>
>
> Kristian Kielhofner wrote:
>
>> Glad to hear.
>>
>> I still say to build the app and logic completely separately and connect
>>
> it
>
>> to FreeSWITCH over the socket using ESL.
>>
>>
>> --
>> Kristian Kielhofner
>> http://blog.krisk.org
>>
>> ----- Original Message -----
>> From: freeswitch-users-bounces@lists.freeswitch.org
>> <freeswitch-users-bounces@lists.freeswitch.org>
>> To: freeswitch-users@lists.freeswitch.org
>> <freeswitch-users@lists.freeswitch.org>
>> Sent: Wed May 12 18:28:13 2010
>> Subject: Re: [Freeswitch-users] Questions on Building an application
>> forFreeSWITCHThis is legit.  We are not into harassing anyone.  There
>> are too many
>> people doing that already.
>>
>> We currently have this working on a Windows/Dialogic platform, but would
>> like to get it over to FreeSWITCH for a number of reasons.  It is always
>> nice to avoid spending alot of time developing using a method that you
>> later find has serious issues or limitations and then having to change
>> horses and start over.  I just thought I would tap on someone else's
>> wisdom in regards to a good way to talk to FS that works well.  I did
>> notice that the wiki talks like LUA is the preferred way to go.
>>
>> Thanks
>>
>>
>>
>> Michael Collins wrote:
>>
>>
>>> On Wed, May 12, 2010 at 2:50 PM, Kristian Kielhofner
>>> <kris@kriskinc.com <mailto:kris@kriskinc.com>> wrote:
>>>
>>>     Are you going to be calling my cell phone to ask if I owe $10,000
>>>     or more to
>>>     the IRS?
>>>
>>>     Seriously, the world does not need another robodialer to harass
>>>     people...
>>>
>>> Agreed, however there are legitimate use cases for this, like a
>>> retailer calling to say an order is in, or reminder calls sent out by
>>> a doctor's office. But yes, if it's dialing for dollars then I'm with
>>> you: Por favor! No mas!
>>> -MC
>>>
>>>
>>>
>>>     With that being said, write your app in whatever you want using
>>>     ESL and
>>>     connect to the socket to originate calls and listen for events.
>>>
>>>
>>>     --
>>>     Kristian Kielhofner
>>>     http://blog.krisk.org
>>>
>>>     ----- Original Message -----
>>>     From: freeswitch-users-bounces@lists.freeswitch.org
>>>     <mailto:freeswitch-users-bounces@lists.freeswitch.org>
>>>     <freeswitch-users-bounces@lists.freeswitch.org
>>>     <mailto:freeswitch-users-bounces@lists.freeswitch.org>>
>>>     To: freeswitch-users@lists.freeswitch.org
>>>     <mailto:freeswitch-users@lists.freeswitch.org>
>>>     <freeswitch-users@lists.freeswitch.org
>>>     <mailto:freeswitch-users@lists.freeswitch.org>>
>>>     Sent: Wed May 12 15:40:58 2010
>>>     Subject: [Freeswitch-users] Questions on Building an application
>>>     forFreeSWITCHI am looking for a boot in the right direction on the
>>>     following project.
>>>
>>>     I am looking to build an "application" with FS where it will
>>>     frequently
>>>     check a database and then make an outbound call when a record with
>>>     certain conditions is found in the DB.  It needs to determine if the
>>>     call was then answered by a machine/vm, busy, or answered by a
>>>
> person,
>
>>>     play a message and get a response back to be recorded in the db.
>>>      It may
>>>     find many calls that need to be made at the same time.  It will be
>>>     running on a PRI.
>>>
>>>     I am confused as to what approach to use to accomplish this.
>>>
>>>     Lua Script, Perl Script, Javascript, Phython, PHP, Ruby....etc.
>>>     Liverpie, ESL....etc.
>>>     Or a totally different approach.
>>>
>>>     I realize that there is not only one "correct" way to build this,
>>>     but I
>>>     am looking for advise from those who have done this type of thing
>>>     before.  I value the opinion of those who have gone down this road
>>>
> and
>
>>>     would be willing to share their thoughts on a recommended path to
>>>
> take
>
>>>     to accomplish this.
>>>
>>>     Thanks
>>>
>>>
>>>     _______________________________________________
>>>     FreeSWITCH-users mailing list
>>>     FreeSWITCH-users@lists.freeswitch.org
>>>     <mailto: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
>>>     <mailto: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
>>>
>>>
>>>
>> _______________________________________________
>> 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
>>
>>
>
>
> _______________________________________________
> 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
>


_______________________________________________
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



--
Anthony Minessale II

FreeSWITCH http://www.freeswitch.org/
ClueCon http://www.cluecon.com/
Twitter: http://twitter.com/FreeSWITCH_wire

AIM: anthm
MSN:anthony_minessale@hotmail.com
GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com
IRC: irc.freenode.net #freeswitch

FreeSWITCH Developer Conference
sip:888@conference.freeswitch.org
googletalk:conf+888@conference.freeswitch.org
pstn:+19193869900