<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'>
<br>Thanks for your advice. I will take it onboard.<br><br>Cheers<br><br>Raf<br><br>> From: chris@cloudtel.com<br>> To: freeswitch-users@lists.freeswitch.org<br>> Date: Wed, 22 Dec 2010 09:50:37 -0500<br>> Subject: Re: [Freeswitch-users] calling card app design decision<br>> <br>> Keep your app server and call server separate is my opinion. I would recommend <br>> inline scripting the small stuff with lua instead of loading the JVM into <br>> your switch<br>> <br>> Anything for billing should be done through events and not inline. Run the JVM <br>> outside the switch and connect to the event socket. If you design it right, <br>> you can scale out multiple switches and have your code in a single JVM <br>> monitor them all<br>> <br>> On December 22, 2010 10:29:16 am Rafqat . wrote:<br>> > Hi,<br>> ><br>> > I am wanting to develop a calling card service using FreeSWITCH. It's<br>> > seems FreeSWITCH is very flexible in terms of how one could go about<br>> > implementing this service. I am intending to use mod_nibblebill and<br>> > mod_lcr to do the core stuff. I would like to use Java for any programming<br>> > (as it's the language I am most familiar with) however, I am unsure whether<br>> > to take an event socket based approach to the application or to use<br>> > something like mod_java.<br>> ><br>> > Any advice/suggestions will be most welcome.<br>> ><br>> > Cheers<br>> ><br>> > Raf<br>> <br>> <br>> <br>> _______________________________________________<br>> FreeSWITCH-users mailing list<br>> FreeSWITCH-users@lists.freeswitch.org<br>> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users<br>> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users<br>> http://www.freeswitch.org<br> </body>
</html>