<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body 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:
<blockquote
cite="mid:CAPScuda=9QOpanxaPrrUPMJTKF9u+LktKSBsCV5Ex+ihZ4Zd0Q@mail.gmail.com"
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">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">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>
</body>
</html>