N2SVCD Configuration

The n2svcd binary is installed into /usr/share/n2svcd/bin/n2svcd and executes as an init.d process. The process starts up and runs continously.

At startup, the n2svcd binary reads its static configuration from its configuration file which defaults to /etc/n2svcd/n2svcd.xml.

The /etc/n2svcd/n2svcd.xml file defines the configuration for all of the installed Applications, which can include:

Example n2svcd.xml

The following is an example /etc/n2svcd/n2svcd.xml configuration file with three Applications configured.

<?xml version="1.0" encoding="utf-8"?>
    <application name="Manage" module="ManageApp">

    <application name="SIGTRAN" module="SigtranApp">
        <parameter name="opc" value="4112"/>
        <parameter name="ossn" value="10"/>
          <connection name="Loopback" type="loopback"/>
          <connection name="telco-slc01" type="sua" sg_dpc="2058">
          <route pc="4112" connection="Loopback"/>
          <route pc="2058" connection="telco-slc01"/>

    <application name="Tester" module="TesterApp">
        <parameter name="json_host" value=""/>
        <parameter name="json_port" value="9009"/>


The following top-level elements/attributes are supported.

Element/Attribute Type Description
sccp Array Container for one or more SCCP Connections.
.connection Element A configured SCCP Connection.
routes Array Container for one or more SCCP Routes.
.route Element A route associating Point Codes with SCCP Connections.
applications Array Container for one or more Applications.
.application Element A configured application running within the Service Daemon. The Tester Application is one application. Other applications implement protocol gateways and perform other functions.

Note: The TCAP protocol is built-in to the n2svcd framework at this time. It does not require a separate protocol gateway application. All other external messaging protocols are implemented as an Application.

For further details, see the specific N2SVCD Configuration sub-topics.