<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Just to add here the option of using kamailio's dialog module to
implement prepaid systems. It will be at signaling level (so no
ivr/media capabilities), which can fit very well in many scenarios.<br>
<br>
If it is the case of 1 call per user at a time, then practically can
be done from kamailio config only. When call starts, compute the max
duration for that call based on caller/destination (e.g., call a
stored procedure via sqlops) and set the dialog timeout to that
duration. When call ends (BYE in main route or timeout route) update
the credit accordingly.<br>
<br>
For many simultaneous calls, you can write a small module that uses
the dialog API, to update the timeout of ongoing calls based on the
costs for new calls.<br>
<br>
Also, dialog module can be used as a controller of the signaling,
being handled by an external billing engine. When a call starts,
inform the billing engine about it. When there is no more credit,
the billing engine can send MI/RPC command (e.g., via xmlrpc) to end
the call.<br>
<br>
Cheers,<br>
Daniel<br>
<br>
On 1/5/12 3:02 PM, Stoyan Mihaylov wrote:
<blockquote
cite="mid:CAPScudbDbnEufB86WDo6L21M1e7rottbyNRG8vBE+5BhuFA9_Q@mail.gmail.com"
type="cite">Prepaid is very simple task. User must put some money
in his account. User selects target. You calculate how long could
be the call, and you dial target.
<div>At the end of call - you calculate call, and you take money
from user.</div>
<div>Complications - recharging account. There are lot of problems
there, mainly with security.</div>
<div>If you would like to allow your users to make more then 1
simultaneous call.</div>
<div>There are couple of things, you should decide:</div>
<div>1. If you plane to offer some specific solution - then you
should select opensource project, or you even should start from
scratch.</div>
<div>2. You can look for problems with different solutions on
market.<br>
<br>
"How I can choose the right solution" - mission impossible - in
all cases you will see later that there is may be some better
solutions.</div>
<div>Best you can do is to select more or less good solution which
will do job you need.</div>
<div>Commercial products, in theory have better support. But
they rely on provider.</div>
<div>As you see with Kamailio - free products can rely on provider
and community, and you can get paid support, you also can easily
(more or less) switch supporter.</div>
<div>There are hosting solutions also, but I have no experience
with them at all.</div>
<div>My main experience is with freelance support for Asterisk
through ssh, and this is why I cant help with freeswitch. Best
advantage of Asterisk (except I know it better) is it allows any
language for AGI scripts, and with them you can do everything.</div>
<div><br>
<div class="gmail_quote">On Thu, Jan 5, 2012 at 3:42 PM, Carlo
Dimaggio <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:jaasmailing@gmail.com">jaasmailing@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"> Hi Stoyan,<br>
<br>
I prefer Freeswitch, but I know that Asterisk can do
prepaid and there are different prepaid solutions.<br>
Anyway, as the prepaid server is a mission-critical
component, I would like to have your (and the community)
opinion about the preferred architecture and experiences
about opensource/commercial solution (advantages and
drawbacks).<br>
All the billing solution are good enough for a service
provider environment? How I can choose the right solution
if all vendors say that their solution is the best one? :)<br>
<br>
Regards,<br>
<br>
<br>
<br>
Il 05/01/12 13.18, Stoyan Mihaylov ha scritto:
<div>
<div class="h5">
<blockquote type="cite">I can suggest using Asterisk
for prepaid job.
<div>I mean you can use Kamailio and couple of
Asterisk servers behind it to do prepaid. There
are lot of prepaid solutions for Asterisk. But
again, if I have to do it I will prefer my
solution, or using parts from what is available.</div>
<div>PS</div>
<div>We did prepaid things for Asterisk.<br>
<br>
<div class="gmail_quote">On Thu, Jan 5, 2012 at
1:08 PM, Carlo Dimaggio <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:jaasmailing@gmail.com"
target="_blank">jaasmailing@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0
0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"> <font
size="-1"><font face="Arial">Hi all,<br>
<br>
I'm working in a project for a service
provider in which prepaid is an
essential requirement. They have about
12000 subscribers.<br>
The core infrastructure will be
Kamailio+RTPProxy while I have some
doubts about the prepaid feature. I'm
thinking about a B2BUA (SEMS or
Freeswitch) that is called if the user
belong to a "prepaid group" and perform
authorization and accounting; in this
case the SIP flow could be: Kamailio
-> B2BUA(Prepaid) -> Kamailio. Is
a good choice?<br>
<br>
At the moment I cannot estimate the
effort needed to develop this section
(base prepaid feature) of the project...
Do you have some hints?<br>
<br>
What are the prepaid solution
implemented by you? Do you use your own
developed solution or do you think that
is better to choose a commercial
solution (that provide also calling-card
and other features)?<br>
I have seen some commercial products
(Portabilling, Jerasoft/Bilberry, ...);
what do you think about?<br>
<br>
<br>
Best Regards,<br>
<br>
</font></font> </div>
<br>
_______________________________________________<br>
SIP Express Router (SER) and Kamailio
(OpenSER) - sr-users mailing list<br>
<a moz-do-not-send="true"
href="mailto:sr-users@lists.sip-router.org"
target="_blank">sr-users@lists.sip-router.org</a><br>
<a moz-do-not-send="true"
href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users"
target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><br>
<br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
<a moz-do-not-send="true" href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-router.org</a>
<a moz-do-not-send="true" href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a>
</pre>
</blockquote>
<br>
</div>
</div>
</div>
<br>
_______________________________________________<br>
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users
mailing list<br>
<a moz-do-not-send="true"
href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a><br>
<a moz-do-not-send="true"
href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users"
target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><br>
<br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a>
<a class="moz-txt-link-freetext" href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Daniel-Constantin Mierla -- <a class="moz-txt-link-freetext" href="http://www.asipto.com">http://www.asipto.com</a>
<a class="moz-txt-link-freetext" href="http://linkedin.com/in/miconda">http://linkedin.com/in/miconda</a> -- <a class="moz-txt-link-freetext" href="http://twitter.com/miconda">http://twitter.com/miconda</a></pre>
</body>
</html>