Re: Call Consolidation

Michael Whisenant ( )
Sun, 07 Dec 1997 11:04:44 -0600

Actually what happens is that calls are consolidated for period which have
expired. For example say a user signs up on 10/1/97 and his period is thru
10/30/97, then when you run calls consolidation on 10/30 it will not
consolidate calls for this user, but will if you run calls consolidation on

>I'm trying to understand how this call consolidation works. It appears to me
>that when I do a call consolidation, it's only consolidating calls for
>customers who are paid up to date. If a customer has an open invoice, their
>calls in the call table are not updated/deleted. Is this correct?

>Also, do I really need to be putting radius into text mode in order to do a
>call consolidation (which runs about 3 hours here) or can I do it while the
>entire system is live?

This depends on your setup. If you are running radiusNT on two systems,
you will need to export your users list, and change to text mode if you
want to capture accounting packets also. Another method would be to change
one server to accounting and one to authentication during this three hour
period. Then the SQL will not lock out the accounting packet, and stop
authentication. We run multiple servers each running a unique task during
calls consolidation, which we are now running every week. It took me some
time and many days of frustration to fully grasp this process and how to
maximize the effectiveness. I have been running RADIUSNT and Emerald for
the last 18 months and last month was the first time it went smoothly. I
had to reconfigure my SQL server to allocate more locks for the process.
With 3/4 to 1 million records per month the basic setup did not work.

Oh dont' forget in your terminal server the easiest way is to remove
backup accounting and backup authentication servers, then set primary
accounting to one machine and primary authentication to the other, IF you
want to have one machine run each task during consolidation.