NexOSS Release Notes

12.1.0 (20210510):

Version 12.1.0 / Build 20210510 (For UI 1.0.160 / For OSPrey v.7.00.0 STI Auth Policies - Use Reported Attestation and Use Reported OriginationId)

• Extended STI Auth Policies to include Use Reported Attestation and Use Reported OriginationId

• DID_TABLE is no longer used, removed it from table-sync

12.0.2 (20210419):

• Bug-Fix unix/utils/compress_archived_cdr_files.sh did not include routed CDRs
• Bug-Fix alerts about DiskSpace went undetected by ApplicationChangeStateMon, assigned to RouteProvision
• Also fixed alerts from threads of CDRPull, RouteProvision.* and TrafficAnalyzer.*, File Mon (web server monitoring file mon), UI memory utilization
• Added hourly heart beat messages to NexOSS-Errors.log
• Monitor NexOSS-Errors.log for periodic updates and any error other than Heart beat
• Extending SipPing
• Added option Identity token
• Added option display name (for the from header)
• Added a utility for sending HTTP STI Sign request
• delete_old_report_files.sh did not cover CDRANALYZER_REPORTS/*tab file
• Added optional ReadOnly (default false) to Table2File
• Git-Hub action build

12.0.1 (20210405):

• Continue switching dependance management to maven
• BugFix - CDR Converter treated ‘<’ as ‘<=’

12.0.0 (20210401):

• Switching dependance management to maven
• Extended Number Translation and Dial Plan configurations to support Bulk-Update

• While the CDRAnalyzer DB is down (IsCDRDBOnline=false), log files for the impacted applications may go stale.
• Added utils set_cdr_db_to_OFF|ON_line.sh to flip the flag and touch log file on ON-line

11.12.04:

• Change made to avoid false positive alerts created by the change from standard time to daylight saving time
• Improve error reporting by OSPrey SIP Monitor.

11.12.03:

• Add reports to NexOSS for Robocall Mitigation.
• Prevent user errors that might result erase and DID and Peering configuration data.

11.12.02:

• Add alerts to notify users that expected configuration updates from external sources have stopped working.

11.12.01:

• Added support for RouteLink product from Somos. NexOSS customers can now route calls by RespOrg ID.
• Improvement: Eliminate duplicate alerts. Suppress alerts when a suspension already existing.

11.12.00:

NexOSS is now integrated with the Somos RouteLink product to enable toll free routing by RespOrg. Also, new SIP headers have been added to convey the SHAKEN authentication and verification status of call.

• Adding support for Somos RouteLink product.
• Added a new account property Do RespOrgId Routing (default false)
• Added a new (DID-like) configuration By RespOrgId
• User configurable SIP response options:
  • reasonSIPheaderEnabled = true/false
  • stiASstatusHeaderName = STI-AS-Status/disabled
  • stiVSstatusHeaderName = STI-VS-Status/disabled

11.11.00:

This release enables NexOSS customers to support multiple SHAKEN certificates and adds the calling name as a Rich Call Data claim in the SHAKEN PASSporT.

• Extended KMS to support multiple operator certificates (one per OCN).
• Extended SHAKEN Authentication and Verification policies to include Certificate (OCN of the Provider) column.
• Added support for out-of-band SHAKEN and Rich Call Data (RCD).
• Extended SHAKEN Verification policies to include Certificate (OCN of the Provider) column and method in-band/in-and-out-of-band.
• Extended Authentication policies to include Use Reported Display Name for RCD. The name of the calling party is now included in the SHAKEN PASSporT as the RCD nam claim.
• Extended STI Authentication policies to include Use Reported PASSporT.
• Allow for CLI in STI Auth/Ver and CNam policies to be ANY DID NUMBER. This special value must be explicitly entered. It will not be a dropdown choice.

11.10.01:

• Add the full SIP INVITE received by OSPrey as a CDR field that can be viewed in NexOSS real time reports.
• Add option to use TrueCNAM for calling number reputation service.
• Add option to use BulkVS for CNAM lookup.
• Processed Time can be reported as an aggregated value by millisecond, 10 milliseconds or 100 milliseconds in CDRAnalyzer.

11.10.00:

• Enhance CDRConverter to be certain all CDRs have been inserted in the ArchivedRatedCDR database on a timely basis.
• Enhance report e-mail alerts to only send alerts when a periodic report has data.

11.09.01:

• Converted Billing Credit Control reports by Service Provider Id / Group Id to use OSPrey suspensions instead of BroadWorks OCI calls.

11.08.04:

• Extend CNAM configuration to NexOSS User Interface.

11.08.03:

• Extended CNAM policies to support Trust Reported Display Name property (default true).

11.08.02:

• Change error alerts to only alert on status changes.

11.08.00:

• Improve error reporting to minimize noise for intermittent errors due to transient network or system conditions.

11.07.06:

• Add option to exclude breakouts from Product Rate Plans when not rate is available for a breakout defined in the LERG.

This is a product creation feature - you can choose whether to include rows without rates / providers.

11.07.04:

• Add feature to modify CNAM display based on calling number reputation or SHAKEN Verification results.
• 10 new data columns added to CDRAnalyzer for reporting calling number reputation results, CNAM results and OSPrey performance.

11.07.03:

• Combine Robocall analytics with CNAM look-up feature. Robocall feature include warning alert thresholds and blocking or diversion thresholds.

11.07.02:

• Added feature to use the YouMail database of high-risk telephone numbers for robocall prevention and mitigation. Database is hosted on OSPrey with automated update every hour. Customer must subscribe with YouMail to get the data.
• Increased replication frequency for HA NexOSS-to-NexOSS replication from 10 minutes to 10 seconds.

11.07.00:

• Automatically create Product rate plans from LCR routing table based on profit margin and minimum required number of providers.
• Optimized CDR collection so CDRs are collected more quickly with lower CPU utilization.
• Add reports in CDRAnalyzer by 7-digit prefix for LRN, Called Number and Calling Number.

11.06.06:

• Calls blacklisted by Calling Number, Called Number, source IP address or user agent can now be diverted. The new feature is enabled by a new device property called Blacklist Action. If this feature is set to Divert, OSPrey will return the special Diversion For Blacklisted Calls Diversion Route Plan.

11.06.04:

• Enabled bulk updates and deletes for configuration files such as the Subscriber, DIDbyNumber and DIDbyOCN tables. Improved performance for large files, 1 million or more records.

11.06.01:

• Enhance fraud triggers so calls can be either blocked or diverted when a fraud trigger is activated. When diversion is configured, the first destination will be the diversion devices, such as a CAPTCHA gateway, followed by destinations for peering, direct routes and LCR. This enables CAPTCHA gateway operation for outbound calls.

First you must tag the devices for Diversion.

Destinations added here are only the destinations tagged as Captcha.

11.05.00:

• Added three new data fields in CDRAnalyzer: Calling Number Breakout, Calling Number Reported (before number translation) and Called Number Reported (different from called number used for routing which may be the Location Routing Number).

11.04.01:

• Added support for Out-of-Band SHAKEN.

11.04.00:

• Added billing rate, breakout and breakout name, for both the source and destination networks to CDRAnalyzer.

11.03.00:

• CDRAnalyzer reports may be created by call end time or call start time.

11.02.03:

• Called numbers may be blacklisted by Fraud Trigger Breakout Code Name. For example, calls to ‘Canada’ could be blacklisted.

11.01.02:

• By default, LCR tables are creating by rank ordering providers by their billing rate. A new feature enables the definition of provider routing rates. If routing rates are provisioned for a provider, then the routing rate, not the billing rate, will be used to determine LCR. This feature enables providers with higher billing rates to be ranked higher in the LCR table.

  • Page - Route-Provisioning_Least-Cost_Routes_Breakouts
  • Column - Routing Rate Multiplier
  • Example -
  • CX321 uses discounted rates for routing (billing rates x 0.1)
  • 3wv003 uses actual rates for routing (multiplier 1)

11.00.00:

• OSPrey can query an external CNAM database, and also block calls based on query to an external spam call analytics engine.

10.16.05:

• OSPrey enabled for direct API integration with iconectiv SHAKEN Policy Administrator.

10.16.02:

• Added SIP INVITE records to CDRAnalyzer.

10.16.01:

• Switched blacklists to use Called Number After Pre-Routing instead of After Routing (which may include pounds and LRN).

In the past, in order to block calls to 14045266060, you would have to block the LRN 16789495993 and the intra-state versions ##16789495993, ###16789495993,####16789495993.
That would block all calls with the same LRN. Now you block just the number itself - 14045266060

10.16.00:

• Switch from self-signed SHAKEN certificates to STI-PA authorized certificates.

10.15.07:

• New CDRAnalyzer columns added: CalledNumber After LNP, CalledLRN 7 Digit Prefix, Destination Rate Center, LERG Company Name, LERG Prefix Type.

10.15.05:

• Improved NexOSS HA operation. Added CDRAnalyzer support for AWS Redshift database.

10.15.01:

• Extended CDRAnalyzer to include call records for SIP INVITES. Enable CDRAnalyzer to create reports for SIP Analytics fraud control records.

10.15.00:

• Improved margin optimization for wholesale LCR. This replaces the need for routing-number-manipulation rules.