Keep your app server and call server separate is my opinion. I would recommend inline scripting the small stuff with lua instead of loading the JVM into your switch Anything for billing should be done through events and not inline. Run the JVM outside the switch and connect to the event socket. If you design it right, you can scale out multiple switches and have your code in a single JVM monitor them all On December 22, 2010 10:29:16 am Rafqat . wrote:

Hi,

I am wanting to develop a calling card service using FreeSWITCH. It's seems FreeSWITCH is very flexible in terms of how one could go about implementing this service. I am intending to use mod_nibblebill and mod_lcr to do the core stuff. I would like to use Java for any programming (as it's the language I am most familiar with) however, I am unsure whether to take an event socket based approach to the application or to use something like mod_java.

Any advice/suggestions will be most welcome.

Cheers

Raf

Did you check, if ASTPP can satisfy your needs? There is support for calling cards with FreeSwitch in beta state. BR Jan BR Jan Am 22.12.2010 16:29, schrieb Rafqat .:

Hi,

I am wanting to develop a calling card service using FreeSWITCH. It's seems FreeSWITCH is very flexible in terms of how one could go about implementing this service. I am intending to use mod_nibblebill and mod_lcr to do the core stuff. I would like to use Java for any programming (as it's the language I am most familiar with) however, I am unsure whether to take an event socket based approach to the application or to use something like mod_java.

Any advice/suggestions will be most welcome.

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