Changing configuration post-installation

The following values are written to sdk.properties, based on the answers given to their respective questions:

These values are used in various places throughout the remainder of the installer (e.g. when determining profile names). It is therefore not recommended to change any of these values.

The following values are written to sdk.properties:

These values can be changed after installation.

If using the Sentinel VoLTE SDK installer to install Rhino automatically, Rhino uses the supplied license file.

The Rhino node setup is used later during the installation.

Many, see notes.

This question determines which features are deployed (this always includes the core features, and can include MMTel and SCC features) and whether the GSM or CDMA features are deployed. Only the chosen features, with their configurations, are deployed. This setting cannot be changed without a reinstall of the Sentinel VoLTE SDK.

The installer create two profiles, one named DEFAULT and one named after the home network MCC, in:

These profiles are initialised using the configured home network prefix and home network MCC.

Furthermore, it sets the following values in the SipSentinelConfigurationTable profile table:

Finally, the NormalizationFeatureConfigProfileTable is updated as follows:

All values can be changed after installation. Furthermore, more profiles can be added to ${platform.operator.name}_DetermineInternationalAndRoamingStatus_AddressListEntryTable and ${platform.operator.name}_DetermineInternationalAndRoamingStatus_AddressListConfigurationTable, using the installer-created profiles as a prototype.

The installer sets MediaServerURI in the SipAnnouncementResourceProfileTable to the supplied media server URI.

The media server URI can be changed after installation.

If using Diameter Ro online charging, the DestinationRealm in the DiameterMediationOcsConfigurationTable is set to the value chosen for the destination realm during the Diameter configuration.

If not using Diameter Ro online charging, the diameterro-0 resource adaptor is deactivated.

The online charging mode can be changed after installation, if the new charging mode is manually configured as detailed below.

The installer sets Host in the DiameterConfig profile table to the supplied host.

If using the installer to set up a simple configuration, all profiles in the DiameterConfig profile table, except the default profile (the nameless profile), are updated as follows:

If setting up a simple configuration, and deploying against a production Rhino (as configured in the Rhino step), we additionally set in the same profiles:

Finally, the installer sets DisableCharging in the DetermineChargingConfigProfileTable to false exactly if Diameter Ro online charging was selected in the Online charging step.

The field 3GPPVersion in the diameterro-0 resource adaptor configuration is set to the configured version.

The configuration can be changed after installation.

The installer sets host in the client profile of the RfControlDiameterConfiguration table to the supplied host.

If using the installer to set up a simple configuration, all profiles in the RfControlDiameterConfiguration profile table are updated as follows:

The rf-control-ra resource adaptor configuration is updated as followed:

Additionally, if using the installer to set up a simple configuration:

Finally, if not using Diameter Rf, the rf-control-ra resource adaptor is deactivated.

The configuration can be changed after installation. If enabling Diameter Rf after installation, please also make the required changes in the Call detail records (CDRs) step.

The installer makes the following changes in the DetermineChargingConfigProfileTable profile table:

Similarly, the installer makes the following changes to all profiles in the SipInterimCdrProfileTable profile table:

These values can be changed after installation, keeping in mind that interim CDRs should be enabled if Diameter Rf is enabled.

The properties file imssf-install.properties is updated as follows:

These values can be changed after installation as detailed in the IM-SSF documentation.

The installer sets host in the client profile of the ShCacheDiameterConfiguration table to the supplied host.

If using the installer to set up a simple configuration, the same profile is updated as follows:

If setting up a simple configuration, and deploying against a production Rhino (as configured in the Rhino step), we additionally update the same profile as follows:

If using the installer to set up a simple configuration, the following values are set in the sh-cache-ra resource adaptor configuration:

DestinationRealm can be changed after installation, but changing DestinationHost is not recommended.

The installer sets the following values in the RegistrarConfigurationTable profile table:

Furthermore, a prototype profile ${platform.operator.name}:::::101 is created in the same profile table, with a single entry:

If Cassandra has been chosen for the registration data storage, the installer enables the cassandra resource adaptor, and sets the following values in the cassandra-third-party-reg resource adaptor configuration:

If Cassandra has not been chosen for the registration data storage, the installer disables the cassandra-third-party-reg resource adaptor.

It is not recommended to change the data storage type after installation. However, the details for the chosen storage type can be altered. Furthermore, the ${platform.operator.name}:::::101 profile can be used as a prototype for adding additional nodes.

The following values are recorded in the ${platform.operator.name}:::::101 profile of the VoLTESharedConfigProfileTable profile table:

These values can be changed after installation.

The installer sets the following values in the cassandra-general resource adaptor configuration:

These values can be changed after installation.

The installer records the configured SIP SIS RA host in the IPAddress property in sentinel-volte-base-services-components/config.ant.xml.

Please see the SIP Resource Adaptor documentation for more information about changing this value.

The installer sets the following values in the MMTelCONFConfigProfileTable profile table:

Furthermore, it sets the following values in the MMTelECTConfigProfileTable profile table:

It also sets the following values in the SccConfHandlingConfigProfileTable profile table:

Finally, it updates the SentinelMapperSetEntryTable to use the mappers corresponding to the configured MSML vendor.

These values cannot be changed after installation.

In the IMS-ODB-Information profile of the ${platform.operator.name}_SubscriberDataLookupFromHss2ServiceIndicationProfileTable profile table, DisableQuery is set to true exactly if the HSS query for IMS-ODB-Information has been disabled.

These values can be changed after installation.

This step only makes any changes if Cassandra was chosen in the Sentinel registrar step.

If the deployment includes SCC, the installer makes the following changes to the ${platform.operator.name_FeatureExecutionPointTable profile table:

If the deployment includes MMTel, the installer makes the following changes to the ${platform.operator.name_FeatureExecutionPointTable profile table:

As changing the deployment type after installation is not possible, these values cannot be changed.

The default profiles (i.e. the profiles without a name) in both the ReoriginationCorrelationIdPools and EtcAriCorrelationIdPools tables are updated in the following way:

These values can be changed after installation.

This step only makes any changes if installing a CDMA deploy, and using TLDN for SCC TADS routing. If so, the installer first makes the following changes in ${platform.operator.name}_FeatureExecutionPointTable:

Next the installer sets the following values in the CDMAHLRConfigProfileTable profile table:

The values in CDMAHLRConfigProfileTable can be changed after installation.

This step only makes any changes if installing a GSM deploy, and using either the MSRN from the HLR for SCC TADS routing, or determining roaming from HLR.

If using the MSRN from the HLR, the installer first makes the following changes in ${platform.operator.name}_FeatureExecutionPointTable:

If determining roaming from HLR, the installer makes the following changes in ${platform.operator.name}_FeatureExecutionPointTable:

Next the installer sets the following values in the HLRConfigProfileTable profile table:

The values in HLRConfigProfileTable can be changed after installation.

If configured to allow WLAN access, the following profiles are added to the SCCTADSNetworkTypeConfigProfileTable:

This setting can be changed after installation by adding or removing the profiles.