This feature implements the re-registration procedures for ESRVCC.
Related Features
-
ESRVCCRegistration handles the initial registration procedures for ESRVCC.
Session Input Variables
| Variable name | Type | Description |
|---|---|---|
PreviousRegistrationData |
List<RegistrationRecord> |
The list of active registration records for the current subscriber and call ID. |
Session Output Variables
| Variable name | Type | Description |
|---|---|---|
ESRVCCReRegistrationNeeded |
Boolean |
Whether the ESRVCCRegistration feature will need to be run on this REGISTER |
CurrentATUSTI |
String |
ATU-STI to be stored in the third-party registrar database. |
AtcfMgmtUri |
String |
ATCF Management URI to be stored in the third-party registrar database. |
AtcfPathUri |
String |
ATCF Path URI to be stored in the third-party registrar database. |
StnSr |
String |
STN-SR to be stored in the third-party registrar database. |
Statistics
ESRVCCReregistration statistics are tracked by the sentinel.registrar SBB
and can be found under the following parameter set in REM:
SLEE-Usage → sentinel.registrar service → sentinel.volte.sip SBB → feature → ESRVCCReregistration
or with rhino-stats:
"SLEE-Usage.Services.ServiceID[name=sentinel.registrar,vendor=OpenCloud,version=4.0.0].SbbID[name=sentinel.registrar,vendor=OpenCloud,version=4.0.0].feature.ESRVCCReregistration"
| Name | Incremented when… |
|---|---|
Started |
The feature is invoked (initial invocation only, not subsequent event triggers). |
FailedDuringExecution |
The feature fails during execution due to an internal |
IssuedWarning |
The feature issues a warning message. |
FailedToStart |
A fatal error occurs before feature execution |
TimedOut |
Feature execution does not complete within a reasonable time frame |
NoPreviousRegistration |
No previous registration records found |
PreviousRegistrationMissingATUSTI |
A previous record is missing the ATU-STI |
PreviousRegistrationMissingATCFManagementURI |
A previous record is missing the ATCF management URI |
PreviousRegistrationMissingCMSISDN |
A previous record is missing the C-MSISDN |
PreviousRegistrationMissingSTNSR |
A previous record is missing the STN-SR |
PreviousRegistrationInvalidATCFManagementURI |
A previous record has an invalid ATCF management URI |
PreviousRegistrationInvalidATCFPathURI |
A previous record has an invalid ATCF management URI |
Configuration
The ESRVCCReregistration feature does not have its own configuration, however it does depend on the Registrar Configuration Table to determine the currently configured value for the ATU-STI.
Behaviour
The primary function of this feature is to ensure the correct ATCF will trigger the correct SCC-AS during ESRVCC access transfer. This may be necessary if re-registrations are sent to an SCC-AS node with a different ATU-STI than the initial (or previous) registration’s ATU-STI, or if the re-registration has a different ATCF URI (e.g. having come from a different registrar).
This feature does not initiate any SIP messaging or change any registration details; if it detects a change, it will set a flag that will cause the normal ESRVCCRegistration feature to perform the full registration process on the new REGISTER request.
REGISTER trigger
The feature is triggered when the registration session type is determined to be ESRVCCRegistration and the registration action
type is determined to be re_register.
The feature first checks the previous registration data provided by the FetchPreviousRegistrationData feature, searching for a registration record that includes all required ESRVCC registration information. If a record is found, the feature will load the ESRVCC specific data from the record and compare the ATU-STI value in that data to the currently configured ATU-STI for the SCC AS. If no previous ESRVCC registration data can be found, or only partial information can be found, the feature behaves as though data was read, but there was a mismatch between the currently configured and previously registered ATU-STI.
If there is no difference in the ATU-STI, then the feature will next extract the ATCF Management and Path URIs from the first party register, and compare them to the URIs currently stored in the previously loaded registration record. If the management or path uris cannot be extracted from the first party register, then the feature will take no other actions and terminate.
If the currently configured ATU-STI matches the one in the previous registration record, and the previous ATCF Management and Path URIs match what the new REGISTER request contains, then the feature will take no other actions and terminate.
If there is a mismatch in the ATU-STI or in the ATCF URIs, then the feature will set the ESRVCCReRegistrationNeeded session state flag to True, indicating that the ESRVCCRegistration feature should perform the full registration process on this request.
