2 New Features in Communications Broker Release 5.0.0

The Communications Broker Release 5.0.0 delivers the following enhancements and new features to improve the functionality, look, and behavior of the software.

Table 2-1 New Features

Feature Description
Egress Policy applied on Calling Number You can now apply policies on a calling number, in addition to the existing facility to apply policies on a called number. Applying routing policies to the calling number, and the called number, enables both the origin and destination of a call to be evaluated against their respective policies in the user table. During the configuration of a policy, a new parameter named userdb-lookup-mode controls the application of policies to both TO and FROM calls. For more information, on this see Define a Policy
Sync refactoring This is an enhancement of the current synchronization feature, and fixes legacy issues. Enhancement includes:
  • Implementation of subscription expiry management.
  • UNSUBSCRIBE requests are handled correctly when synchronization is disabled,
  • Synchronized data is removed when the synchronization feature is turned off,.
  • Peer status reporting is accurately done
  • Improved synchronization timer statistics and error handling,
Support for Google Cloud Platform (GCP) Communications Broker Release 5.0.0 supports deployment on Google Cloud Platform (GCP).
Data Integrity Entitlement introduced to enable or disable Data Integrity with advanced cryptographic modules (FIPS 140-3 certification is currently pending).
Marketplace Availability on public clouds Communications Broker Release 5.0.0 is available for deployment on OCI and Azure cloud platforms.
OJET 17.1.0 uplift The Communications Broker Release 5.0.0 user interface has been upgraded to OJET version 17.1.0 to provide an interactive and seamless user experience.
Enhanced security features Starting with PCz500p3, these enhancements have been added building on the existing security features:
  • Addition of local accounts
  • Option to disable the factory account
For more information, see the section User Accounts in the Enterprise Session Border Controller Configuration Guide.
AP-3950 support Starting with PCz500P3, support for AP-3950 has been enabled. Acme Packet platforms are prepared for operation, including having the software pre-installed. For more information, see the section Acme Packet 3950/4900 Physical Interfaces in the SBC Platform Preparation and Installation Guide - for Service Provider and Enterprise.