Difference between revisions of "Mor authorize: Too low balance for more simultaneus calls!!!"

From Kolmisoft Wiki
Jump to navigationJump to search
Line 1: Line 1:
Reason for this is that your server or Asterisk was restarted (maybe crashed) during the active call.


Fix: issue to your database such command:
UPDATE users SET frozen_balance = 0;
<br>
----
<br>
NOTE: MOR automatically takes care of wrongly restarted Asterisk in MOR PRO 0.6 and in following versions and database corruption is fixed automatically.
<br>
----
<br>


The other reason can be that your user is PREPAID and he has not enough balance to cover more simultaneous calls.
The other reason can be that your user is PREPAID and he has not enough balance to cover more simultaneous calls.

Revision as of 17:04, 16 May 2008


The other reason can be that your user is PREPAID and he has not enough balance to cover more simultaneous calls.

MOR uses algorithm to reserve balance when call is made to be safe if user is prepaid.

That way when second, third, etc calls are made - MOR checks free - not reserved balance and decides should it allow to dial or not.

To lower security level and allow users with low balance to dial out several times, go to /etc/asterisk/mor.conf and change to: 

min_frozen = 1

That way you are taking risk that you will take loss if user talks for more then frozen_time (default 90s). E.g. if user make a call, his balance is frozen for 90s with the rate to current destination. If user talks more - you can take loss.

Retrieved from "https://wiki.kolmisoft.com/index.php?title=Mor_authorize:_Too_low_balance_for_more_simultaneus_calls!!!&oldid=1402"