Set the platform operator name
Within common-config.yaml, in the common section, set your platform operator name:
platform-operator-name: MetaswitchConfigure session replication
Session replication allows established calls to continue if the node that previously processed the call becomes unavailable.
Within either sentinel-volte-gsm-config.yaml or sentinel-volte-cdma-config, in the sentinel-volte section, set session-replication-enabled
session-replication-enabled: trueIf enabling on a system where session replication was previously disabled, please contact Metaswitch support.
Review the SIP session settings
Within either sentinel-volte-gsm-config.yaml or sentinel-volte-cdma-config,
in the session-refresh section,
check that these values are appropriate and change if necessary.
# Configuration for the Session Refresh feature.
session-refresh:
# The interval of the periodic timer (in seconds).
timer-interval-seconds: 30
# Period of no activity for leg tp refresh (in seconds).
refresh-period-seconds: 570
# Whether the session should be refreshed using UPDATE requests,
# as long as the endpoint allows UPDATE requests.
refresh-with-update-if-allowed: true
# Maximum allowed duration of a call (in seconds).
max-call-duration-seconds: 86400Configuring integration within the system
For each node type deployed, you need to configure the names of the cluster and individual virtual machines using data from the node type’s site definition files (SDF) which were created as part of the VM Install process. In some cases you also need to configure user access and node specific integration parameters.
Parameters
This table cross references the node types and which parameters need configuring.
Parameter |
Applicable node types |
|||||
|---|---|---|---|---|---|---|
MAG |
MMT GSM |
MMT CDMA |
SHCM |
TSN |
SMO |
|
✔ |
✔ |
✔ |
✔ |
✔ |
✔ |
|
✔ |
✔ |
✔ |
✔ |
✔ |
✔ |
|
✔ |
✔ |
✔ |
✔ |
✔ |
✔ |
|
✔ |
✔ |
✔ |
✔ |
✔ |
||
✔ |
✔ |
✔ |
✔ |
✔ |
||
✔ |
✔ |
✔ |
✔ |
✔ |
||
✔ |
✔ |
✔ |
✔ |
✔ |
||
✔ |
||||||
Per node parameters |
||||||
✔ |
✔ |
✔ |
✔ |
✔ |
✔ |
|
✔ |
✔ |
✔ |
✔ |
|||
✔ |
✔ |
✔ |
✔ |
✔ |
||
✔ |
✔ |
|||||
✔ |
✔ |
✔ |
||||
✔ |
||||||
✔ |
||||||
✔ |
||||||
deployment-id and site-id
deployment-id and site-id must be set to match the parameters of the same name in the SDFs created as part of the VM Installation process.
cassandra-contact-points
Leave the cassandra-contact-points blank unless directed otherwise by Metaswitch support.
additional-rhino-jvm-options
Leave the additional-rhino-jvm-options blank unless directed otherwise by Metaswitch support.
rhino-auth and rem-auth
Some node types have lists of rhino-auth and/or rem-auth authentication data.
These are used to access rhino and rem respectively. See the appropriate reference for details.
Per node parameters
These parameters are in a list called virtual-machines, with one entry per VM.
vm-id
The vm-id values under virtual-machines must be the same as the name values under instances in the SDF.
rhino-node-id
For nodes supporting a Rhino cluster, specify the node-id for the Rhino rhino-node-id on each VM.
scheduled-rhino-restarts
For nodes that run Rhino, you can optionally specify that Rhino should be automatically restarted on a regular schedule. This can be useful if you observe resource leaks (memory, file handles, activities, and so on) in Rhino which require a restart to clean up the leftover resources.
The available options for scheduled restarts are daily, weekly, or monthly schedules. The following shows example configuration for each:
# a daily schedule
scheduled-rhino-restarts:
time-of-day: "02:00"
# or, a weekly schedule
scheduled-rhino-restarts:
time-of-day: "02:00"
day-of-week: "Wednesday"
# or, a monthly schedule
scheduled-rhino-restarts:
time-of-day: "02:00"
day-of-month: 9
|
|
To disable automatic Rhino restarts, omit the scheduled-rhino-restarts section from the configuration.
By default, restarts are disabled.
per-node-diameter-rf and per-node-diameter-ro
To set the origin-host value for Diameter Rf per-node-diameter-rf and Diameter Ro per-node-diameter-ro protocols, see Charging.
diameter-zh-origin-host
To set the origin-host value for Diameter Zh protocol diameter-zh-origin-host, see Diameter Zh interface.
diameter-sh-origin-host
To set the origin-host value for Diameter diameter-sh-origin-host Sh protocol, see
Diameter Sh interface.
