Cisco Cisco Prime Access Registrar 6.0

Prime Access Registrar sends a MAP_SEND_AUTH_INFO request to HLR on receiving EAP-SIM / 
EAP-AKA authentication request and fetches the authentication vectors in 
MAP_SEND_AUTH_INFO_RES message. Prime Access Registrar checks the IMSI and if it is 
authentic, sends a MAP_RESTORE_DATA_REQUEST to fetch the profile information from the HLR. 
HLR then responds with MAP_INSERT_SUBSCRIBER_DATA request to Prime Access Registrar. The 
request contains the circuit switched (CS) profile information for a subscriber. 

Prime Access Registrar server stores the profile information based on the ProfileInfo configuration and 
sends a MAP_INSERT_SUBSCRIBER_DATA_RESPONSE to HLR. HLR responds with 
MAP_RESTORE_DATA_RESPONSE to Prime Access Registrar. After successful acknowledgment of 
MAP_RESTORE_DATA, Prime Access Registrar server maps the fetched profile through 
RestoreDataMappings to any of the environment variables configured by the user. The CS profile used 
to authorize WI-FI access which is fetched from HLR can be transported to access point in any of the 
radius attribute. 

The mapping of the values in the response to a profile is possible based on the configuration in the 
profilemappings configuration.

You can configure an M3UA service to fetch MSISDN from IMSI or vice versa (IMSI from MSISDN) 
through RADIUS packets. Set the AuthorizationInfoLookUp parameter in the CLI to one of the 
following:

MSISDN-IMSI—To fetch MSISDN in the request and send IMSI in the response to the HLR. 

IMSI-MSISDN—To fetch IMSI in the request and send MSISDN in the response to the HLR.

The GUI is also updated with the parameter to support this functionality.

Multihoming feature of Stream Control Transmission Protocol (SCTP) provides the ability for a single 
SCTP endpoint to support multiple IP addresses. With this feature, each of the two endpoints during an 
SCTP association can specify multiple points of attachment. Each endpoint will be able to receive 
messages from any of the addresses associated with the other endpoint. With the use of multiple 
interfaces, data can be sent to alternate addresses when failures occur and thus Prime Access Registrar 
runs successfully even during network failures.

Prime Access Registrar allows you to configure multiple source and destination addresses on the remote 
server using the CLI. The GUI is also updated with an option to provide additional source and destination 
IP addresses for the remote server.

Prime Access Registrar supports multiple remote servers with the protocol type, SIGTRAN-M3UA. 
However, Prime Access Registrar validates and ensures the following when multiple remote servers are 
available:

The source port is different for all the remote servers.

If Origin Point Code (OPC) is different, the routing context is also different for all the remote 
servers.