SAS integration
The Rhino VoLTE TAS supports Metaswitch’s SAS (Service Assurance Service) integration.
What you need
-
❏ To chose whether or not to activate SAS tracing.
-
❏ The IP addresses or DNS hostnames of SAS servers to connect the Rhino VoLTE TAS to.
Setting up the SAS interface
The configuration for the SAS to Rhino VoLTE TAS interface is in the sas-config.yaml
file.
In the sas
section, configure the servers list
.
The example configuration given here indicates input for what is needed for integrating the Rhino VoLTE TAS with SAS servers in a network.
sas:
# Whether SAS is enabled ('true') or disabled ('false')
enabled: true
# Parameters for connecting to SAS
sas-connection:
# List of SAS servers. Either IP addresess or DNS hostnames.
# Needs to be specified in a non-MDM deployment.
servers:
- 10.10.10.10
- 10.10.10.11
- sas.example.com
SNMP integration
The Rhino VoLTE TAS supports integration with SNMP based systems.
What you need
-
❏ The version of SNMP to be used.
-
❏ If using SNMP v2c, the SNMP community value.
-
❏ The SNMP agent details such as location and contact address.
-
❏ If using SNMP notifications, each notification target’s host, port, and specifc SNMP version.
Setting up the SNMP interface
The configuration for the SNMP to Rhino VoLTE TAS interface is in the snmp-config.yaml
file.
In the snmp
section, configure the targets list
.
The example configuration given here indicates input for what is needed for integrating the Rhino VoLTE TAS with SNMP services in the network.
snmp:
# Enable SNMP v1 (not recommended)
v1-enabled: false
# Enable SNMP v2c
v2c-enabled: true
# Enable SNMP v3
v3-enabled: false
# SNMP Community. Required for SNMP v2c
community: clearwater
# SNMP agent details
agent-details:
location: Unknown location
contact: support.contact@invalid.com
# SNMP Notifications
notifications:
# Enable SNMP Notifications
enabled: true
# SNMP notification targets. Normally this is the address of your MVS
targets:
- version: v2c
host: 127.0.0.1
port: 162