Rating in real time involves many database and other operations depending on the complexity of the rating tables. Pushing 60 calls per second in a residential scenario will yield a lot of simultaneous calls. You can handle the traffic of many residential subscribers at 60 cps. I am personally surprised you were able to do this on one machine.
You are trying to use the application in a high density trunking scenario and is no wonder you hit a limit, the application was not designed for being used in such scenario. The idea was to be able to handle 2/3 calls for discrete SIP devices belongs to one SIP account, where each SIP account corresponds to a SIP device like a cable modem used by residential subscribers. You are pushing it to do things beyond its design envelope. You should better use the quota system with postpaid rather than real time prepaid for what you describe as it makes little sense to have prepaid balance calculated in real time for high density trunks that generate lots of traffic and associated costs. Adrian On 30 Sep 2014, at 09:57, Pavel Eremin <[email protected]> wrote: > Thanks, i read all of docs and have question about performance. (I Did > describe it in another email to community) > > 30.09.2014 4:56 пользователь "Adrian Georgescu" <[email protected]> > написал: > If you want to dive this deep into CDRTool, it would be a good start to read > the documentation, that is all *.txt files in docs/ folder. > > -- > Adrian > > > > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -- Adrian
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
