[Spce-user] rate-o-mat and fraud lock incoming

[Rene Krenn]

Yes, confirmed. fraud locks are to be applied to the origninator, when the
cost limit is exceeded. For a destination customer it makes no sense to lock
it if received destination costs (or balance) exceed a limit.

A solution is to consider current fraud limits as source cost limits, and
extend/duplicate the whole implementation also for destination costs. Then a
subscriber causing too much destination costs can be locked. 

Feel free to send a inquiry to sales at sipwise.com, if such feature is
required.

br

-----Ursprüngliche Nachricht-----
Von: Jon Bonilla (Manwe) [mailto:manwe at sipdoc.net] 
Gesendet: Donnerstag, 23. November 2023 13:14
An: spce-user at lists.sipwise.com
Betreff: [Spce-user] rate-o-mat and fraud lock incoming

Hi all

I'm checking rateomat and the fraud lock mechanism because I have an issue
where a customer is not being locked when the balance is reached. 

Seems like the lock is only executed if there's source_customer_cost but not
if there's destination_customer_cost

In my scenario the customer is being charged for incoming calls but it's
never locked and I'd like to confirm that rateomat won't execute fraudlock
checks when the calls are incoming and the cost to the customer are dst and
not src. 

Is it right?


thanks,

Jon


--
PekePBX, the multitenant PBX solution
https://pekepbx.com