What's New in This Guide
This section introduces the documentation updates for release 25.1.2xx.
Release 25.1.204 - G25546-08, August 2026
- Updated the release version number to 25.1.204.
- Updated the Pushing the Images to Customer Docker Registry section to describe the compatible docker image versions for various Policy microservices.
- Updated the Supported Upgrade Paths in Supported Upgrade Paths.
- Updated the Supported RollBack Paths in Rolling Back Policy.
Release 25.1.203 - G25546-07, April 2026
Incorporated editorial changes.
Release 25.1.203 - G25546-06, April 2026
- Updated the release version number to 25.1.203.
- Updated the Pushing the Images to Customer Docker Registry section to describe the compatible docker image versions for various Policy microservices.
- Updated the Supported Upgrade Paths in Supported Upgrade Paths.
- Updated the Supported RollBack Paths in Rolling Back Policy.
Release 25.1.202 - G25546-05, February 2026
- Updated the release version number to 25.1.202.
- Updated the Pushing the Images to Customer Docker Registry section to describe the compatible docker image versions for various Policy microservices.
- Updated the Supported Upgrade Paths in Supported Upgrade Paths.
- Updated the Supported RollBack Paths in Rolling Back Policy.
Release 25.1.201-G25546-03, February 2026
Updated the sample annotation for two or more interfaces in the Configuring Traffic Segregation section.
Release 25.1.201-G25546-02, January 2026
- Updated the release version number to 25.1.201.
- Updated the Pushing the Images to Customer Docker Registry section to describe the compatible docker image versions for various Policy microservices.
- Removed the
diam-gateway.envSupportedIpAddressTypeparameter from the Configuration Parameters for Dual Stack section. - Removed the Configuration Parameters for IPV6 table from the Customizing Policy chapter because the parameters mentioned in the Configuration Parameters for Dual Stack table can also be considered for IPV6 single stack installations.
- Added two new helm parameters in the Diameter Gateway and Diameter Connector Configuration section:
- diam-gateway.diamResponseLatencyHistogramBucket
- diam-gateway.diamResponseLatencyHistogramPercentile
- Updated the Configuration Parameters for Dual Stack section
with the following details:
- replaced the
diameter-gateway.dualStackPreferredDnsResolutionIpAddressTypeparameter with theglobal.dgwRoutingModeparameter. - updated the default value from "both" to IPv4_IPv6 for
the
global.dgwRoutingModeparameter. - updated the possible values from 'IPv4', 'IPv6', 'both' to
IPv6, IPv4, IPv6_IPv4, IPv4_IPv6 for the
global.dgwRoutingModeparameter. - updated the added in release value from 25.1.200 to 25.1.201.
- replaced the
- Updated the Supported Upgrade Paths in Supported Upgrade Paths.
- Updated the Supported RollBack Paths in Rolling Back Policy.
Release 25.1.200 - G25546-01, July 2025
- Updated the release version number to 25.1.200.
- Added the following parameter to Binding Service Configurations section to support for stale requests cleanup for Binding Service:
enableLateArrivalenableLateProcessing
- Added the
egress-gateway.globalRemoveRequestHeader.oc-message-priorityparameter to Basic Configurations in Egress Gateway section to communicate message priority value toward other NFs. - Added the following parameters to Configuration Parameters for Dual Stack to configure dual stack:
global.deploymentModeglobal.egressRoutingModediameter-gateway.dualStackPreferredDnsResolutionIpAddressType
- Added the following parameters to LDAP Configurations to configure LDAP:
LDAP_CONNECTION_CONNECT_ALL_SERVERSLDAP_CONNECTION_DATASOURCE_RETRY_COUNT
- Added configurable parameters to enable or disable the stale request
cleanup functionality for User service to Enabling/Disabling Services Configurations:
CHF.enableLateArrivalCHF.enableLateProcessingCHF.skipLateProcessingForTerminateUDR.enableLateArrivalUDR.enableLateProcessingUDR.skipLateProcessingForTerminate
- Added configurable parameters to enable or disable the stale request
cleanup functionality for UE service to Enabling/Disabling Services Configurations:
enableLateArrivalenableLateProcessingskipLateProcessingForTerminatelate.arrival.max.resp.time
- Added SIGNALING_DB_HISTOGRAM_METRIC_ENABLED parameter to Binding Service Configurations , which is used to enable or disable the histogram metrics for Binding service database.
- Added the following parameters to Basic Configurations in Ingress Gateway, which are used to configure pod protection by rate limiting:
- podProtectionByRateLimiting.enabled
- podProtectionByRateLimiting.fillRate
- podProtectionByRateLimiting.bucketAllocation
- podProtectionByRateLimiting.routes.routeId
- podProtectionByRateLimiting.routes.percentage
- podProtectionByRateLimiting.errorCodeProfile
- podProtectionByRateLimiting.deniedRequestActions.congestionLevel
- podProtectionByRateLimiting.deniedRequestActions.priority
- podProtectionByRateLimiting.deniedRequestActions.action
- podProtectionByRateLimiting.priorityHeaderName
- podProtectionByRateLimiting.defaultPriority
- Added the following parameters to Enabling/Disabling Services Configurations, which are used to configure the partition based search on PolicyDS database:
- enablePdsPartitionBasedSchema
- primaryKeyCombination
- Added Scaling Down of Pods During Shutdown and Restoring System Backup section with the steps to scale down and scale up the pods in Policy.
- Updated Preupgrade Tasks section with a step to check the required databases before proceeding with the upgrade procedure.
- Added the following parameters to Database Name Configuration, which are used to configure AppInfo to handle cnDBTier DB cluster disconnect
functionality:
- database.clusterEventTracking.enabled
- database.clusterEventTracking.url
- database.clusterEventTracking.pollIntervalMs
- database.clusterEventTracking.funcionalEventList
- database.clusterEventTracking.initialEvent
- database.clusterEventTracking.blockReadiness
- database.clusterEventTracking.autoTransition
- database.clusterEventTracking.assumePositive.enabled
- database.clusterEventTracking.assumePositive.code
- database.clusterEventTracking.assumePositive.exceptions
- database.clusterEventTracking.retry.enabled
- database.clusterEventTracking.retry.attempts
- database.clusterEventTracking.retry.delayMs
- database.clusterEventTracking.retry.code
- database.clusterEventTracking.retry.exceptions
- realtimeDbStatusWithClusterEvent
- infraCategoryWithRealTimeDb
- Updated the following sections for adding the details of new audit
occnp_timer_servicedatabase in Configuring Database, Creating Users, and Granting Permissions section.- Updated the Database Single Site section with details of
occnp_timer_servicedatabase creation, and grant commands. - Updated the Database Multisite section with details of
occnp_timer_servicedatabase creation, and grant commands.
- Updated the Database Single Site section with details of
- Updated Configuring Database, Creating Users, and Granting Permissions with details of configuring occnp_query database.
- Updated the Pushing the Images to Customer Docker Registry section to describe the compatible docker image versions for various Policy microservices.
- Updated Configuring Database, Creating Users, and Granting Permissions section to include details of 'occnp_query' database used for Query Service.
- Updated Single Site section to describe the creation of 'occnp_query' database, creating users and granting permissions in a single site deployment mode.
- Updated Multisite section to describe the creation of 'occnp_query' database, creating users and granting permissions in a multisite deployment mode.
- Updated the Supported Upgrade Paths in Supported Upgrade Paths.
- Updated the Supported RollBack Paths in Rolling Back Policy.
- Updated Preupgrade Tasks with the details to manually install
occnp_timer_serviceandoccnp_querydatabases while upgrading Policy from any of the previous versions to 25.1.200. - Updated Preupgrade Tasks with the details to add and drop indexes.
Added When AppInfo Pod Does Not Restart After Upgrade to Scenario: Session Database Corruption to describe the case when AppInfo pod does not restart after upgrade even if there are changes in config map.