Navigation :

SVC Installation

Overall Installation Steps

The high-level steps for installing and configuring N2SCP SVC nodes are:

Determine the server(s) that will supply the SVC logical component, bearing in mind the supported operating systems and minimum server requirements.
Ensure the installation pre-requisites are met.
Install the SVC package.
Perform any required post-installation steps.
Update the SVC configuration as desired.

Installation Pre-requisites

OS-specific Setup

Refer to the specific Red Hat or Debian instructions for any pre-requisites as required.

Lua

Each N2SCP SVC instance requires Lua to be available at version 5.2+. Specifically, both lua and luac must be present in the PATH for all users. Consult your operating system documentation to determine the appropriate package to install.

If your distribution does not support Lua at version 5.2+, N-Squared maintains a pre-packaged, separately-installable version of Lua that meets N2SCP’s requirements. Contact N-Squared Support to discuss access to this if required.

N2SVCD

The N-Squared application framework N2SVCD must be installed. Follow the installation steps for this, noting any prerequisites.

The N2SCP SVC package also expects that the default N2SVCD configuration directory exists:

/etc/n2svcd

Be sure to apply any applicable N2SVCD post-installation steps once installation is complete.

Installation Steps

Follow the appropriate installation steps depending on your installation sources.

From N-Squared Repository

Execute the instructions specific to your operating system:

RHEL 8	Other RPM-based Systems	DEB-based Systems
`sudo dnf install n2scp-svc`	`sudo yum install n2scp-svc`	`sudo apt-get install n2scp-svc`

As Manual Installation

Transfer the provided package file to the target node, then follow the instructions specific to your operating system.

Execute (adjusting as appropriate for package location and version details) the following:

RPM-based Systems	DEB-based Systems
`sudo rpm -Uvh /path/to/n2scp-svc-M.m.p-b.noarch.rpm`	`sudo dpkg -i /path/to/n2scp-svc_M.m.p-b_all.deb`

Post-Installation Steps

N2SVCD and Database Integration

The N2SCP runtime uses the several N2SVCD applications to perform call handling functions. For N2SCP call handling, the N2SVCD configuration must include an N2SVCD-based application (e.g. the N2SCP-DSG) and, if necessary, an N2SVCD SIGTRAN application to receive call triggers.

If CUG functionality is required, a Database N2SVCD application must also be configured.

At a high level, the required configuration for these applications looks like:

        <application name="DSG" module="DsgScpApp"> <!-- or LhoScpApp -->
            ...
            <parameters>
                ...
                <parameter name="cug_db_app_name" value="DB"/>
            </parameters>
        </application>

        <application name="DB" module="DBApp">
            ...
            <parameters>
                ...
                <parameter name="connect" value="..."/>
            </parameters>
        </application>

Refer to the individual application configuration documentation for full details of the configuration required. The database application should be configured to connect to the appropriate primary or replica DB node that the SVC node will use.

Once N2SVCD is updated, restart the service:

systemctl	System V
`sudo systemctl restart n2svcd`	`sudo service n2svcd restart`

Reporting Integration

Statistics and EDRs may be disabled or sent to a data repository. Note that if EDRs are not disabled or transferred, they may eventually fill the file system.

Firewall

The firewall (if any) on the SVC node must be updated to allow:

Establishment of the inbound or outbound SIGTRAN and/or SIP/RTP connectivity to the core network.
Outbound database requests to the DB node(s).

If required, the firewall (if any) on the SVC node may also be updated to allow:

Inbound requests for the N2SVCD administrative GUI/API.

If statistics and EDRs are to be retained, the firewall must be updated to allow access for:

Outbound statistics measurements to the repository.
Outbound EDRs to the repository.

The exact commands to do this will depend both on the firewall on your platform and also which port(s) are in use. For example, to allow the default PostgreSQL port when using firewalld, the commands might be:

firewall-cmd --zone=public --add-port=5432/tcp --permanent
service firewalld restart