Cisco Cisco Prime Access Registrar 6.0
2
Cisco Prime Access Registrar 6.0.2 Release Notes
OL-29762-01
Enhanced Features in Cisco Prime Access Registrar 6.0.2
•
•
•
•
•
•
•
•
•
Enhanced Features in Cisco Prime Access Registrar 6.0.2
Prime Access Registrar has the following enhancements for 6.0.2:
•
•
HLR GT Caching
The Home Location Registry (HLR) Global Title address (GT address in calling party address (CgPA))
from the SendAuthenticationInfo (SAI) response is cached and used for subsequent authorization
request. This cached HLR GT is added to the environment dictionary of the packet to be available for
the authorization flow.
from the SendAuthenticationInfo (SAI) response is cached and used for subsequent authorization
request. This cached HLR GT is added to the environment dictionary of the packet to be available for
the authorization flow.
The following environment dictionary variables are added to hold the cached HLR GT:
•
HLR-GlobalTitle-Cached—Set as TRUE to indicate the HLR GT is cached
•
Cached-HLR-GlobalTitle-Digits
•
Cached-HLR-Translation-Type
•
Cached-HLR-Numbering-Plan
•
Cached-HLR-Encoding-Scheme
•
Cached-HLR-Nature-Of-Address
•
Cached-HLR-GT-Format
The cached HLR GT overrides both the configured destination GT values and GT script provided GT
values. The HLR GT caching works by default for RTE_GT. The cached HLR GT can be overridden by
updating the environment variable HLR-GlobalTitle-Cached to FALSE (or anything other than TRUE)
in the GT script.
values. The HLR GT caching works by default for RTE_GT. The cached HLR GT can be overridden by
updating the environment variable HLR-GlobalTitle-Cached to FALSE (or anything other than TRUE)
in the GT script.
The HLR GT will not be cached for:
•
reauthentication flow
•
authorize only flow, when authentication vectors are already available in cache, as SAI request will
not be available.
not be available.