Overall Installation Steps
The high-level steps for installing and configuring N2SIP 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.
Refer to the specific Red Hat or Debian instructions for any pre-requisites as required.
Each N2SIP SVC instance requires Lua to be available at version 5.2+. Specifically, both
luac must be present
PATH for all users. Consult your operating system documentation to determine the appropriate package to
If your distribution does not support Lua at version 5.2+, N-Squared maintains a pre-packaged, separately-installable version of Lua that meets N2SIP’s requirements. Contact N-Squared Support to discuss access to this if required.
The N-Squared application framework N2SVCD must be installed. Follow the installation steps for this, noting any prerequisites.
The N2SIP SVC package also expects that the default N2SVCD configuration directory exists:
Be sure to apply any applicable N2SVCD post-installation steps once installation is complete.
Follow the appropriate installation steps depending on your installation sources. The N2SRP GUI can replicate audio files and configuration by database or file sync. If database replication is being used, the installation of n2sip-db should also be done, as noted by [*].
From N-Squared Repository
Execute the instructions specific to your operating system:
|Other RPM-based Systems
sudo dnf install n2sip-svc
sudo yum install n2sip-svc
sudo apt-get install n2sip-svc
sudo dnf install n2sip-db
sudo yum install n2sip-db
sudo apt-get install n2sip-db
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:
sudo rpm -Uvh /path/to/n2sip-svc-M.m.p-b.noarch.rpm
sudo dpkg -i /path/to/n2sip-svc_M.m.p-b_all.deb
sudo rpm -Uvh /path/to/n2sip-db-M.m.p-b.noarch.rpm
sudo dpkg -i /path/to/n2sip-db.m.p-b_all.deb
[*] Only if database replication is being used for audio file transfer.
n2sip-db is installed for database replication, refer to the database installation guide
to complete the database installation on each service node.
The N2SIP SVC packages delivers several N2SVCD applications to perform traffic handling functions. Refer to the application configuration documentation for details of the configuration required for these applications.
Non-Standard File Directories
When database replication is used, non-standard directories for SRP audio files and configuration are not required and this section can be skipped.
However, when using file-base storage for audio files, the following actions must be taken to set up the audio file and configuration directory for the N2SRP audio files synchronised from the SMS node to the service nodes.
If the standard directories generated under
/var/lib/n2sip are not used, their replacements
must be created and updated before use.
mkdir -p /path/to/n2sip/resources/live
chown -R n2in:daemon /path/to/n2sip
The SELinux permissions must also be updated:
semanage fcontext -a -t var_lib_t "/path/to/n2sip(/.*)?"
restorecon -Rv /path/to/n2sip
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.
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:
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