VoIP Mailing List Archives

[manoj.joshi.13jan at g...]

Hello,
 
If we use heartbeat option on in nibblebill.conf.xml does that mean ODBC database table will be updated every microsecond or any other interval we set?
 
If this is so and there are many users (Lets say 500 users) are connected to FS wouldn't it create locking issues in DB?
 
Regards,
 
Manoj

[mike at jerris.com]

increments are in seconds, not microseconds. In IMS for example I
think it defaults to 20 or 30 second nibbles, depending on your
tolerances and billing increments something much larger may even make
sense. Doing billing in sub second increments doesn't make a lot of
sense to me. Remember that this is just keeping track of available
credit so if there are multiple calls at the same time you won't go
over balance. Everything is still reconciled at hang up, so if you
have a bit too much reserved from your nibble the worst that could
happen is it could cut off calls a little too early when multiple
calls are in progress on the same account.

Mike

On Aug 15, 2009, at 3:33 PM, Manu wrote:

[manoj.joshi.13jan at g...]

Thank you for the reply Michael. Let me ask your opinion on another related matter also.
 
I am using a MS SQL Database (which will be there on a remote server). I wish to keep ...
 
1- User database in SQL.
2- Dialplans in SQL.
3- CDR logged in SQL.
4- I also require to cut the call in real time when credit is over.
 
I want to deply this to get good performance for 500 calls simultaneous. I see in documents that using http responses i can fetch data from my web server. I figure i can return number of gateways and other dial plan parameters this way. In the same HTTP request i can also return "call Rates" for the called destination (which i can use in nibble)
 
Is there any other efficiant apprroach you can suggest?
 
Regards,
 
Manoj
 
 


 
On Sun, Aug 16, 2009 at 2:50 AM, Michael Jerris <mike@jerris.com (mike@jerris.com)> wrote:

[mgg at giagnocavo.net]

Just an in-general performance hint: Get your setup running, then use the SQL Profiler to generate a tuning trace, and run the “Database Engine Tuning Advisor” with it. That way it’ll tell you which indexes you need (or need to drop) to optimize the database side of performance.

500 simultaneous calls isn’t much though. Even with 30 second nibblebillings, that’s only 16 updates/sec – and your calls/sec is probably lower than that. That’s not too much work for any average server these days, even doing dialplan/cdr/billing against remote SQL.

-Michael

From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Manu
Sent: Sunday, August 16, 2009 2:05 AM
To: freeswitch-users@lists.freeswitch.org
Subject: Re: [Freeswitch-users] mod nibblebill question


Thank you for the reply Michael. Let me ask your opinion on another related matter also.



I am using a MS SQL Database (which will be there on a remote server). I wish to keep ...



1- User database in SQL.

2- Dialplans in SQL.

3- CDR logged in SQL.

4- I also require to cut the call in real time when credit is over.



I want to deply this to get good performance for 500 calls simultaneous. I see in documents that using http responses i can fetch data from my web server. I figure i can return number of gateways and other dial plan parameters this way. In the same HTTP request i can also return "call Rates" for the called destination (which i can use in nibble)



Is there any other efficiant apprroach you can suggest?



Regards,



Manoj









On Sun, Aug 16, 2009 at 2:50 AM, Michael Jerris <mike@jerris.com (mike@jerris.com)> wrote:
increments are in seconds, not microseconds. In IMS for example I
think it defaults to 20 or 30 second nibbles, depending on your
tolerances and billing increments something much larger may even make
sense. Doing billing in sub second increments doesn't make a lot of
sense to me. Remember that this is just keeping track of available
credit so if there are multiple calls at the same time you won't go
over balance. Everything is still reconciled at hang up, so if you
have a bit too much reserved from your nibble the worst that could
happen is it could cut off calls a little too early when multiple
calls are in progress on the same account.

Mike

On Aug 15, 2009, at 3:33 PM, Manu wrote: