[Spce-user] Fraud Prevention

[Andreas Granig]

Hi,

The reason it doesn't work for you is quite simple and stupid on our 
end: I'm afraid we forgot to include the /usr/sbin/ngcp-fraud-daily-lock 
script in the debian package for 2.8.

I'll push an update into the 2.8 repo within the next couple of hours. 
Once done, you'll get a 
/etc/ngcp-config/templates/etc/cron.d/ngcp-fraud-daily-lock.tt2 config 
where you can adapt how often to run the daily fraud script.

Aplologies for that, and thanks for raising this issue!

Andreas

On 05/02/2013 07:10 AM, Martin Wong wrote:
> Hi, apologies for the erratic emails on this topic. Just trying to
> figure out how this works?
>
> Can someone explain what the basics are? I have created a billing
> profile, the rating works fine. Then I have under that billing profile
> an account with a few subscribers. Under that account, I've set a fraud
> daily limit of 0.50 (for example) and have made calls which have been
> rating correctly. Total of more than 0.50 worth of calls has been made.
>
> Have run the ngcp-fraud-auto-lock manually but it didn't lock it.
>
> I apologize but if I'm doing something wrong here, please let me know.
>
> Thanks
>
>
> On Thu, May 2, 2013 at 2:34 PM, Martin Wong
> <martin.wong at binaryelements.com.au
> <mailto:martin.wong at binaryelements.com.au>> wrote:
>
>     Hi,
>
>     can someone explain how this works? How does this get updated? Cash
>     $0.05 under Spent this billing interval?
>
>     And can this be done so that the fraud prevention script runs say
>     every hour or is this too much?
>
>       *
>         Spent this billing interval
>       *
>         Cash:
>         $ 0.05
>       *
>         Free time:
>         0 s
>
>
>
>
>     On Wed, May 1, 2013 at 4:44 PM, Martin Wong
>     <martin.wong at binaryelements.com.au
>     <mailto:martin.wong at binaryelements.com.au>> wrote:
>
>         Hi guys, I don't get this ....
>
>         below is a CDR record.
>
>         Clearly, this is over the limit than my daily limit but I still
>         can make outgoing calls.
>
>         Does the destination_carrier_cost need to be populated? If so,
>         I'm not sure how to get this. My billing profile has the call
>         costs uploaded correctly. I assume the regex is correct as well
>         cuz I can see the source_customer_cost to be 0.18 in this instance.
>
>         Can someone help to see what other settings need to be done for
>         the fraud lock to work?
>
>
>         call_code:200
>         call_id:ZDhlNDVkYWM5MmJhM2NkZDM5MDE0ZmNlZDY2MzUxOWQ.
>         call_status:ok
>         call_type:call
>         destination_account_id:0
>         destination_carrier_billing_fee_id:
>         destination_carrier_billing_zone_id:
>         destination_carrier_cost:0.00
>         destination_carrier_free_time:0
>         destination_customer_billing_fee_id:
>         destination_customer_billing_zone_id:
>         destination_customer_cost:0.00
>         destination_customer_free_time:0
>         destination_domain:125.213.160.145
>         destination_domain_in:49.156.17.189
>         destination_external_contract_id:
>         destination_external_subscriber_id:
>         destination_provider_id:3
>         destination_user:XXXXXXXX
>         destination_user_dialed:XXXXXXXX
>         destination_user_id:0
>         destination_user_in:XXXXXXXX
>         duration:10.400
>         id:388
>         init_time:1367390374.753
>         peer_auth_realm:
>         peer_auth_user:
>         rated_at:2013-05-01 16:40:06
>         rating_status:ok
>         source_account_id:6
>         source_carrier_billing_fee_id:69
>         source_carrier_billing_zone_id:1140
>         source_carrier_cost:0.18
>         source_carrier_free_time:0
>         source_cli:0XXXXXXXX
>         source_clir:0
>         source_customer_billing_fee_id:69
>         source_customer_billing_zone_id:1140
>         source_customer_cost:0.18
>         source_customer_free_time:0
>         source_domain:xx.xx.xx.xx
>         source_external_contract_id:
>         source_external_subscriber_id:
>         source_ip:xx.xx.xx.xx
>         source_provider_id:1
>         source_user:abcdeftest
>         source_user_id:c1f84003-cca2-42ce-b074-12ef7b765a27
>         start_time:1367390386.340
>
>
>
>
>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> http://lists.sipwise.com/listinfo/spce-user
>