Release Notes

2
Cisco Prime Access Registrar 7.1 Release Notes
Co-Existence With Other Network Management Applications
Co-Existence With Other Network Management Applications
To achieve optimal performance, Prime Access Registrar should be the only application running on a
given server. In certain cases, when you choose to run collaborative applications such as a SNMP agent,
you must configure Prime Access Registrar to avoid UDP port conflicts. The most common conflicts
occur when other applications also use ports 2785 and 2786. For more information on SNMP
configuration, see the Configuring SNMP section, in the Cisco Prime Access Registrar 7.1 Installation
and Configuration Guide.
Enhanced Feature in Cisco Prime Access Registrar 7.1.0.1
This section contains the following topic:
• Fetching EPSUserState in UDA for VoWiFi, page 2
Fetching EPSUserState in UDA for VoWiFi
This feature allows you to fetch EPSUserState from a User-Data-Answer (UDA) message on an Sh
interface.
A user equipment (UE) can be bocked or allowed for voice over Wi-Fi (VoWiFi) call based on the
EPSUserState value fetched from the UDA on an Sh interface.
To fetch EPSUserState, a User-Data-Request (UDR) message is sent with Current-Location =
InitiateActiveLocationRetrieval, Data-Reference =UserState, Requested-Domain = PS-Domain, and
Requested-Nodes = 1(MME).
The UDA contains a User-Data (or Sh-Data) AVP, which in turn contains the EPSUserState tag.
EPSUserState can have one of the following values:
• 0—Detached
• 1—AttachedNotReachableForPaging
• 2—AttachedReachableForPaging
• 3—ConnectedNotReachableForPaging
Table 1 Minimum Hardware and Software Requirements for Prime Access Registrar Server
OS version RHEL 6.4/6.6/7.0
CentOS 6.5
Model X86
CPU type Intel Xeon CPU 2.30 GHz
CPU Number 4
CPU speed 2.30 GHz
Memory (RAM) 8 GB
Swap space 10 GB
Disk space 1*146 GB