Billing is not so much a question of scalability, but accuracy. Inline lua can verify the PIN against the DB, but it cant accurately calculate billing. Anything making a calculation on how much money your customer just spent on minutes should not be done inline, as many tricks can happen and channels have their own state (CS_REPORTING) when the optimal information for accounting is available. For prompting the user for their calling card PIN, there is nothing wrong with lua connecting to your database. For subtracting minutes from an account while the user is on call then event socket or a module listening to events is a better method. The latter is how mod_nibblebill works. Personally, for several large projects I chose to monitor events across multiple switches via event socket and it worked out very nicely. On Thu, Dec 23, 2010 at 4:07 PM, Rafqat . <rafonline@hotmail.com> wrote:
Hi,
I could get lua to do the lookup, I was wondering i guess where does one draw the line between when to do stuff inline and when to do stuff outside of freeswitch (in terms of load and scalability of solution etc.)
Cheers
Raf
------------------------------ Date: Thu, 23 Dec 2010 12:37:26 -0800 From: msc@freeswitch.org To: freeswitch-users@lists.freeswitch.org Subject: Re: [Freeswitch-users] ESL outbound /inbound
What is wrong with having Lua do the db lookup? -MC
On Thu, Dec 23, 2010 at 9:42 AM, Rafqat . <rafonline@hotmail.com> wrote:
Hi,
I am writing a calling card app using lua and java.
As advised, Java will predominatley do all the billing side of things (via ESL) leaving lua do simple things like asking for the calling card pin number etc.
When a call comes in, my lua script answers the call and asks the user for a pin. Instead of querying the DB inline from within lua, I would like my app server to do this (please let me know if this should be done inline instead). I understand my app server (Java ESL inbound socket) can register for a pin checking custom event and I can generate such an event from within my lua script. My lua script would then wait for an appropriate repsonse event:
-- Check if pin is valid local event = freeswitch.Event("CUSTOM", "check_pin_request"); event:addHeader("pin_number", digits); event:fire();
-- wait for response con = freeswitch.EventConsumer("CUSTOM", "check_pin_reponse"); con:pop(1); print("event\n" .. e:serialize("xml"));
I was wondering if the above is the right way of doing things, or should I be using ESLOutboundSocket and have lua script do something like this instead:
session:execute("set", "pin_to_check=12345"); session:execute("socket", "192.168.0.2:8084");
Not sure how lua will be told whether the pin is valid or not in this scenario.
I appreciate FreeSWITCH is very flexible and would like to make sure I develop a scalable and performant application.
Any help will be much appreciated.
Cheers
Raf
_______________________________________________ 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