Cisco Cisco Access Registrar 5.1 發佈版本通知
5
Release Notes for Cisco Access Registrar, 5.1
OL-25654-01
Enhancements in Cisco Access Registrar 5.1.0.6
Enhancements in Cisco Access Registrar 5.1.0.6
gives the details on the enhancements made in Cisco Access Registrar 5.1.0.6.
Enhancements in Cisco Access Registrar 5.1.0.4
gives the details on the enhancements made in Cisco Access Registrar 5.1.0.4.
Table 1
Enhancements in Cisco Access Registrar 5.1.0.6
Bug
Description
CSCtn29426
Need to have a configurable option to change the NP in CDPA and CGPA.
A configure option is provided for CDPA and CGPA number plan in
SIGTRAN remote server.
SIGTRAN remote server.
Table 2
Enhancements in Cisco Access Registrar 5.1.0.4
Bug
Description
CSCty82224
Need to support diameter request routing based on the peers property.
When IsActive is set as False and MultiplePeersPolicy is Failover for
Diameter Services, failover is considered for the diameter sessions. If
IsActive is set as False and MultiplePeersPolicy is Round-robin for
Services, the new diameter sessions will not be sent to the peer; Earlier, the
peer needs to be shutdown to avoid new sessions being sent to the peer.
Diameter Services, failover is considered for the diameter sessions. If
IsActive is set as False and MultiplePeersPolicy is Round-robin for
Services, the new diameter sessions will not be sent to the peer; Earlier, the
peer needs to be shutdown to avoid new sessions being sent to the peer.
CSCtz17252
Need auto commit feature for OCI accounting.
When OCIautoCommit is set as False for an OCI accounting server and the
DataSourceConnections and OCITransactionCount are set as numeric
values, the transaction details are committed in the database based on the
OCITransactionCount set per DataSourceConnection. The remaining
transaction details will be automatically committed to the database when
Cisco Access Registrar is shutdown.
DataSourceConnections and OCITransactionCount are set as numeric
values, the transaction details are committed in the database based on the
OCITransactionCount set per DataSourceConnection. The remaining
transaction details will be automatically committed to the database when
Cisco Access Registrar is shutdown.
For example, if the DataSourceConnections is 4 and the
OCITransactionCount is 3, when the transactions between a connection
and the server reaches the OCITransactionCount, the transaction details are
committed to the database. The remaining transaction details are
committed only after reaching the OCITransactionCount or when
Cisco Access Registrar is shutdown.
OCITransactionCount is 3, when the transactions between a connection
and the server reaches the OCITransactionCount, the transaction details are
committed to the database. The remaining transaction details are
committed only after reaching the OCITransactionCount or when
Cisco Access Registrar is shutdown.