The Sentinel VoLTE provisioning module is distributed as a Rhino Element Manager (REM) plugin.

It requires REM 2.6.1 or compatible. REM can be installed with Jetty or Apache Tomcat. For Sentinel VoLTE, the Apache Tomcat method is required.

To install the Sentinel VoLTE Provisioning module you will need:

Below are the procedures to:

Important
REM restart required

After installing and configuring the plugin, you will need to restart REM, for example by restarting the Tomcat webapp it is running in:

${CATALINA_BASE}/bin/catalina.sh stop
${CATALINA_BASE}/bin/catalina.sh start

Set up Tomcat

To set up Apache Tomcat for the Sentinel VoLTE Provisioning module:

1

Follow the instructions for running REM on Apache Tomcat in the REM Guide.

2

Create the rem_home/plugins directory.

cd apache-tomcat-<version>
mkdir -p rem_home/plugins

3

If running Apache Tomcat using Java 1.7, you will need to increase the PermGen size.

Add JAVA_OPTS to bin/setenv.sh.

JAVA_OPTS="-XX:PermSize=512m -XX:MaxPermSize=512m"

This step should be skipped if running Apache Tomcat on Java 1.8 or higher.

Install the REM plugin

To install the REM plugin for the Sentinel VoLTE Provisioning Module:

1

Copy sentinel-volte-element-manager-<version>.em.jar into rem_home/plugins.

cd apache-tomcat-<version>
cp /full/path/to/sentinel-volte-element-manager-<version>.em.jar rem_home/plugins/

2

(Optional) Copy sis-em-<version>.em.jar into rem_home/plugins.

cd apache-tomcat-<version>
cp /full/path/to/sis-em-<version>.em.jar rem_home/plugins/

Customize plugin logging

1

Edit log4j2.properties and append the following content:

# additional lines to add to the rem.war log4j2.properties file

# the XCAP server only logs when user traffic arrives
# per-request logging is at debug level
logger.xcapserver.name=xcapserver
logger.xcapserver.level=DEBUG

# the diameter stack in the XCAP Server - logs regardless of user traffic
logger.xcapdiameter.name=xcapserver.diameter
logger.xcapdiameter.level=INFO

# transport level logging from the XCAP Server's diameter stack
# set to DEBUG for interoperability diagnostics
logger.xcapdiametertransport.name=xcapserver.diameter.transport
logger.xcapdiametertransport.level=INFO

# part of the XCAP server logging
logger.remxcap.name=rem.server.sentinel.xcap
logger.remxcap.level=DEBUG

# a rolling audit file of Sentinel EM plugin audit logging
appender.sentinelaudit.type=RollingFile
appender.sentinelaudit.name=AUDIT
appender.sentinelaudit.fileName=${sys:catalina.base}/logs/sentinel-audit.log
appender.sentinelaudit.filePattern = ${sys:catalina.base}/logs/sentinel-audit.log.%i
appender.sentinelaudit.policies.type = Policies
appender.sentinelaudit.policies.size.type = SizeBasedTriggeringPolicy
appender.sentinelaudit.policies.size.size=10MB
appender.sentinelaudit.strategy.type = DefaultRolloverStrategy
appender.sentinelaudit.strategy.max = 10
appender.sentinelaudit.layout.type=PatternLayout
appender.sentinelaudit.layout.pattern="%d{yyyy-MM-dd HH:mm:ss,SSS}", "%c{1}", %m{nolookups}%n

# send Sentinel EM plugin audit logging to the AUDIT appender, only
logger.sentinelaudit.name=sentinel.audit
logger.sentinelaudit.level=INFO
logger.sentinelaudit.appenderRef.file.ref=AUDIT
logger.sentinelaudit.additivity=false

Import Rhino trust certificate

This can also be done using the REM web UI.

1

Import a Rhino Trust Certificate into REM:

"${JAVA_HOME}/bin/keytool" -importcert -file ${RHINO_HOME}/rhino-trust.cert -keystore "${TOMCAT_HOME}/rem_home/rhino-ems.ks" -storepass changeit -noprompt

Security considerations

Below are recommendations for securely running the Sentinel VoLTE Provisioning Module.

Use https

Be aware that the Sentinel VoLTE machine API uses HTTP BASIC authentication. This passes the username and password with every request.

To prevent your credentials going over the network unencrypted, run REM over https.

Set up SSL

See the Tomcat 7 - SSL How-To docs for help setting up SSL in Apache Tomcat 7.

Previous page Next page
Sentinel VoLTE Version 2.9.0