After the installation went through successfully, you are ready to adapt the system parameters to your needs to make the system work properly.
If you have only one network card inside your system, its device name is eth0, it’s configured and only IPV4 is important to you then there should be nothing to do for you at this stage. If multiple network cards are present, your network card does not use eth0 for its device name or you need IPv6 then the only parameter you need to change at this moment is the listening address for your SIP services.
To do this, you have to specify the interface where your listening address is configured, which you can do with the following command (assuming your public interface is eth0):
ngcp-network --set-interface=eth0 --ip=auto --netmask=auto --hwaddr=auto ngcp-network --move-from=lo --move-to=eth0 --type=web_ext --type=sip_ext --type=rtp_ext --type=ssh_ext --type=web_int
If you want to enable IPv6 as well, you have to set the address on the proper interface as well, like this (assuming you have an IPv6 address fdda:5cc1:23:4:0:0:0:1f on interface eth0):
ngcp-network --set-interface=eth0 --ipv6='FDDA:5CC1:23:4:0:0:0:1F'
Always use a full IPv6 address with 8 octets. Leaving out zero octets (e.g.
You should use the IPv6 address in upper-case because LB (kamailio) handles the IPv6 addresses internally in upper-case format.
If you haven’t fully configured your network interfaces, do this by adapting also the file /etc/network/interfaces:
Add or adapt your interface configuration accordingly. For example, if you just want to use the system in your internal network 192.168.0.0/24, it could look something like this:
auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 192.168.0.10 netmask 255.255.255.0 gateway 192.168.0.1 dns-nameservers 188.8.131.52 dns-search yourdomain.com
In order to apply the changes you made to /etc/ngcp-config/config.yml, you need to execute the following command to re-generate your configuration files and to automatically restart the services:
ngcpcfg apply 'added network interface'
At this point, your system is ready to serve.
During installation, the system user cdrexport is created. This jailed system account is supposed to be used to export CDR files via sftp/scp. Set a password for this user by executing the following command:
The installer has set up a MySQL database on your server. You need to set a password for the MySQL root user to protect it from unauthorized access by executing this command:
mysqladmin password <your mysql root password>
For the Administrative Web Panel located at https://<your-server-ip>:1443/login/admin, a default user administrator with password administrator has been created. Connect to the panel (accept the SSL certificate for now) using those credentials and change the password of this user by going to Settings→Administrators and click the Edit when hovering over the row.
The NGCP installer will install mailx (which has Exim4 as MTA as a default dependency) on the system, however the MTA is not configured by the installer. If you want to use the Voicemail-to-Email feature of the Voicebox, you need to configure your MTA properly. If you are fine to use the default MTA Exim4, execute the following command:
Depending on your mail setup in your environment (whether to use a smarthost or not), configure Exim accordingly. In the most simple setup, apply the following options when prompted for it:
internet site; mail is sent and received directly using SMTP
mbox format in /var/mail/
You are free to install and configure any other MTA (e.g. postfix) on the system, if you are more comfortable with that.
You have a typical test deployment now and you are good to go, however you may need to do extra configuration depending on the devices you are using and functionality you want to achieve.
As reported by many users, Audiocodes devices suffer from a problem where they replace
127.0.0.1 address in Record-Route headers (added by the sip:provider CE’s internal components) with its own IP address. The problem has been reported to Audiocodes but as of end 2012 the fixed firmware is not available yet so supposedly the whole range of Audiocodes devices, including but not limited to the MP202, MP252 CPEs as well as Audiocodes media gateways, is malfunctioning. As a workaround, you may change the internal IP address from
127.0.0.1 to some dummy network interface. Please execute the following command (in this example
192.168.2.2 is a new internal IP address):
Enable module dummy at /etc/ngcp-config/config.yml:
modules: - enable: yes name: dummy options: numdummies=2
ifconfig dummy0 192.168.2.2 netmask 255.255.255.0
Adapt your /etc/network/interfaces file accordingly:
auto dummy0 iface dummy0 inet static address 192.168.2.2 netmask 255.255.255.0
Update the network configuration in the sip:provider CE:
ngcp-network --set-interface=dummy0 --ip=auto --netmask=auto ngcp-network --move-from=lo --move-to=dummy0 --type=sip_int --type=web_int
Refer to the Network Configuration chapter for more details about the
ngcpcfg apply 'audiocodes devs workaround'
To test and use your installation, you need to follow these steps now:
Please read the next chapter for instructions on how to do this.