NexOSS 5.11.2 - New features
This release includes a new feature for determining a fraud score for each call. The score is determined by destination dial code and greatly simplifies the process of provisioning fraud detection triggers.
Fraud risk by destination can easily be uploaded for thousands of dial codes as a two column text file. The first column is the dial code and the second column is the numeric fraud risk - which in most cases will be the termination cost for that dial code.
Each call is rated using the fraud risk for the destination dial code. Calls to high risk destination get a high fraud score, calls to low risk destinations get a low fraud score. By using this scoring technique, each customer can be assigned a single fraud score trigger threshold for all breakouts.
The new fraud scoring feature aligns fraud detection more closely with real world economic risk and simplifies fraud detection management.
Another important modification is suppression of Quality of Service packet statistics that are clearly outliers. Real Time Control Protocol (RTCP) reports from some VoIP devices report packet loss and jitter statistics that are impossible. For example, some devices consistently report packet loss greater than 100%. Another common problem is jitter reported as a value greater than call duration.
Since these statistics are reported by RTCP reports from end point devices, the data cannot be verified by the Acme Packet Session Border Controller (SBC). The bogus data is written to the SBC accounting record and forwarded to OSPrey. These bogus statistics create considerable confusion when included in NexOSS Quality of Service reports. To fix this problem, NexOSS no ignores packet loss statistics greater than 100% and jitter statistics greater than 1000 milliseconds when scoring the QoS for a call.