Hello again,
My installation is on a P4 2.4GHz with 2GB RAM. Initially, I thought reduction of the RAM can illustrates the system limitation. Therefore, I reduced the RAM to 500MB but I am not seeing any change in the delay. I also have a total of 100 pin numbers (Phantom Users) in the database of the test setup.
Here is the two different setup which I use for testing and I am seeing a similar waiting time on the both setups.
Test Setup One:
A2Billing 1.4
Asterisk 1.4
The A2Billing and Asterisk are installed on the same machine which is a P4 2.4GHz with 2GB RAM.
Test setup Two:
OpenSIPS 1.5
A2Billing 1.4
Asterisk 1.4
DRBD 8.3
HeartBeat 2
mon 1.2
The entire system is installed on total of 6 machines which are P4 2.4GHz with 2GB RAM.
1 x OpenSIPS 1.5
2 x A2Billing 1.4 - with DRBD 8.3, Heartbeat 2, and mon 1.2
3 x Asterisk 1.4
The OpenSIPS is used to load-balance the traffic between the 3 Asterisk boxes. The billing is done with two separate boxes which both runs the A2Billing. The DRBD, heartbeat, and mon are used to create the High-Avalibity testing and at any given time only one A2Billing box does the billing.
Would you be able to guesstimate the delay I should expect from the time the user finishes dialing the last digit of their pin to the time the A2Billing/Asterisk announces back the credit via the IVR?
Quote:
I am not getting any notable delay on any of my installations, so I can only assume there is an issue with either your installation or your hardware.
Does this means once the user enters the last digit of their pin number, they get the credit announced back immediately (less say with less than one second waiting)?
Can I ask others to share their waiting time with their hardware to create some guidelines?
Thanks,
Avestan