[Spce-user] NGCP-FRAUD Protection doesn't work in 4.3.1

Kirill Solomko ksolomko at sipwise.com
Mon Apr 25 18:07:33 EDT 2016


> On 25 Apr 2016, at 19:22, Matthias Hohl <matthias.hohl at telematica.at> wrote:
> 
> 4. BUG:
> 
> The [% interval_cost %] shows the false value.
> 
> The mail i got for daily lock notification script:
> Customer # 6 has been locked due to exceeding the configured
> credit balance threshold (6.11 >= 1.00) in the customer settings.
> 
> The daily debit on the whole customer with this subscriber for today is just "1.53 EUR". I checked this my Why is there 6.11 EUR?
> 
> 
> The mail I got for monthly lock notification script:
> Customer # 6 has been locked due to exceeding the configured
> credit balance threshold (178.56 >= 2.00) in the customer settings.
> 
> The monthly debit on the whole customer with this one subscriber is just "45.11 EUR". Why is there 178.58 EUR?
> 
> I checked the interval cost values by filtering the "call details" of the subscriber from 01.04.2016 to endless for monthly call costs and 25.04.2016 to endless for todays call costs.
> 

The value is taken directly from the customer’s cdrs, therefore it can possibly differentiate from the actual balance representation on the GUI.

> BTW BUG: if I set there a "TO DATE", the filtering doesn't work..
> BTW BUG 2: In Customer Details, if I look into the "Billing Profile schedule" also the activate billing profile is strikethrough (the checkbox is enabled but the date and name is Strikethrough)
> 

We will check ngcp-panel side for those 2 reported GUI misbehaviours, thanks for reporting it. 

> 
> Sorry, but didn't you do any internal testing before releasing a new software version?
> 

We do indeed. ngcp fraud detection behaviour has been preserved in some ways to allow smooth transition for already existing customers.

Kind regards,
Kirill


More information about the Spce-user mailing list