Once Sipwise C5 is in production, security and maintenance becomes really important. In this chapter, we’ll go through a set of best practices for any production system.
The Sipwise C5 provides SSH access to the system for Sipwise operational team for debugging and final tuning. Operational team uses user sipwise which can be logged in through SSH key only (password access is disabled) from dedicated access server jump.sipwise.com only.
To completely remove Sipwise access to your system, please execute as user root:
root@myserver:~# ngcp-support-access --disable && apt-get install ngcp-support-noaccess
you have to execute the command above on each node of your Sipwise C5 system!
please ensure that the script complete successfully:
* Support access successfully disabled.
If you need to restore Sipwise access to the system, please execute as user root:
root@myserver:~# apt-get install ngcp-support-access && ngcp-support-access --enable
please ensure that the script complete successfully:
* Support access successfully enabled.
The Sipwise C5 runs a wide range of services. In order to secure the platform while allowing access to Sipwise C5 , Sipwise C5 configuration framework provides a set of predefined network zones. Services are aggregated into appropriate zones by default. Zones are assigned to network interfaces (and VLANs if applicable) in /etc/ngcp-config/network.yml.
Though the default firewall setup provided by Sipwise C5 configuration framework provides a safe setup for Sipwise C5, security audits of the platform performed by qualified engineers before commissioning the platform into service are strongly recommended. Customization of the setup requires in-depth knowledge of firewalling principles in general and the netfilter facility in particular.
Table 16. Sipwise C5 network zones
Internal HA (High Availability) communication interface between the services
Interface for external RTP media relay between Sipwise C5 and endpoints (e.g. user agents, peers)
Interface for external SIP signalling between Sipwise C5 and endpoints (e.g. user agents, peers)
Interface for internal signalling, e.g. between load-balancers, proxies and applications servers
Interface providing external access to Sipwise C5 command line interface
Interface providing access to the customers' self-care Web panel
Interface for access to the administrative Web panel, its REST APIs and internal API communications
Additional custom zones may be configured, but will not be automatically integrated into the firewall configuration.
To facilitate firewall functionality, Sipwise C5 uses the Kernel’s netfilter facility and iptables-persistent as an interface to netfilter. Netfilter is using tables and within that chains to store rules in this hierarchy: table → chain → rule. Default firewall setups of Sipwise C5 do not use netfilter tables nat and raw, but only default table filter.
Custom nat rules for IPv4 and IPv6 may be added in file /etc/ngcp-config/config.yml in sections security→firewall→nat_rules4 and security→firewall→nat_rules6.
Each chain deploys a default policy handling packets which did not trigger and rule in a prticular chain.
Table 17. Sipwise C5 netfilter default policies
Handling all packets directly destined for a Sipwise C5 node (only packets matching a rule are allowed)
Handling all packets received by a Sipwise C5 node and destined for another, non-local IP destination (no default rules added)
Handling all packets originating on a Sipwise C5 node (no default rules added)
Container for rptengine rule to allow the rule to persist even when the Kernel module is unloaded (e.g. during upgrades)
The default firewall setup provided by Sipwise C5:
The Sipwise C5 comes with a preconfigured set of firewall rules, which can be enabled and configured in
/etc/ngcp-config/config.yml in section
security→firewall. Refer to Section 1.29, “security” for available configuration options.
Firewall configuration is applied by running
ngcpcfg apply. However, this will not activate new rules automatically to avoid inadvertent self-lockout. To finally activate new firewall rules run
iptables-apply. This will prompt for another system logon to verify access remains available. If the prompt is not confirmed, firewall rules will automatically be reverted to the previous state re-enabling access to the command line.
The Sipwise C5 firewall subsystem by default is disabled in /etc/ngcp-config/config.yml key
The following set of rules is added by the system upon activation of the firewall subsystem. Individual system rules are configured in /etc/ngcp-config/templates/etc/iptables/rules.v4.tt2 and /etc/ngcp-config/templates/etc/iptables/rules.v6.tt2
Table 18. Firewall system rules
Redirects all incoming UDP packets to chain rtpengine (putting RTPENGINE rule into a dedicated chain allows for the rule to persist even when the Kernel module gets unloaded, e.g. during upgrades)
Feeds all RTP packets to RTPENGINE Kernel module
Accept all packets received by local loopback interface
Accept all incoming packets tied to related or established connections
Accept all ICMP echo messages
Accept all ICMP echo reply messages
Accept all ICMPv6 messages
Divert all incoming packets to the cluster chain
Set of rules white-listing all IP-addresses owned by Sipwise C5 platform for incoming traffic
Set of rules for all api_int interfaces accepting all incoming packets for API port defined in /etc/ngcp-config/config.yml with key ossbss.port
+-p udp -s <snmpclient_ip> --dport 161 -j ACCEPT
Set of rules for all mon_ext interfaces based on a list of IPs for all SNMP communities configured in snmpd.communities
Set of rules for all rtp_ext interfaces accepting all incoming packets for RTP port range defined in /etc/ngcp-config/config.yml with keys rtpproxy.minport and rtpproxy.maxport (see note below for custom options)
Set of rules for all sip_ext interfaces accepting all packets on the loda balancer’s SIP signalling port defined in /etc/ngcp-config/config.yml with key kamailio.lb.port (UDP)
Set of rules for all sip_ext interfaces accepting all packets on the loda balancer’s SIP signalling port defined in /etc/ngcp-config/config.yml with key kamailio.lb.port (TCP)
Set of rules for all sip_ext interfaces accepting all packets on the loda balancer’s SIP signalling port defined in /etc/ngcp-config/config.yml with key kamailio.lb.tls.port (TCP/TLS)
Set of rules for all sip_ext interfaces accepting all packets on TCP port 5222 (XMPP client)
Set of rules for all sip_ext interfaces accepting all packets on TCP port 5269 (XMPP server)
Set of rules for all sip_ext interfaces accepting all packets incoming for the pushd server port configured in /etc/ngcp-config/config.yml with key pushd.port
List of rules to accept incoming packets for SSH on all ssh_ext interfaces from hosts configured in /etc/ngcp-config/config.yml with key sshd.permit_support_from
List of rules to accept incoming packets for the Customer Self Care interface defined in /etc/ngcp-config/config.yml with key www_admin.http_csc.port on all web_ext interfaces
List of rules to accept incoming packets for the Admin Panel interface defined in /etc/ngcp-config/config.yml with key www_admin.http_admin.port on all web_int interfaces
To function correctly, the rtpengine requires an additional iptables rule installed. This rule (with a target of
Some of the parameters used to populate the firewall rules automatically may contain hostnames instead of IP addresses. Since firewall rules need to be configured based on IP addresses by design, Sipwise C5 configuration framework will lookup such hostnames during ngcpcfg apply and expand them to the IP addresses as returned by gethostbyname. If DNS resolving changes for such hostnames due to changes to DNS the rules will not update automatically. Another run of ngcpcfg apply will be needed to reperform the lookup and update the rules to reflect changes in DNS. If this step is omitted, clients may be locked out of the system.
By default, the rules for the rtp_ext zone are created with a target of
The Sipwise C5 configuration framework makes it possible to add custom rules to the firewall setup in /etc/ngcp-config/config.yml. The custom rules are added after the system rules. Hence, they apply for packets not matched by the systems rules only.
Example custom rule to whitelist all IPv4 traffic from network interface eth1.301 effectively making VLAN 301 a trusted network:
rules4: - '-A INPUT -i eth1.301 -j ACCEPT'
Example custom rule to accept incoming traffic from monitoring station 203.0.113.93 for an optionally installed check_mk agent:
rules4: - '-A INPUT -p tcp -s 203.0.113.93 --dport 6556 -j ACCEPT'
To add hosts or networks to the SSH whitelist they can be either added to key sshd.permit_support_from in /etc/ngcp-config/config.yml or a custom rule may be used:
rules4: - '-A INPUT -s 198.51.100.0/24 --dport 22 -j ACCEPT' - '-A INPUT -s 203.0.113.93 --dport 22 -j ACCEPT'
In custom rules keys from /etc/ngcp-config/config.yml cannot be referenced. Thus, the values need to be manually looked up, hard coded, and kept in sync manually. This is by design of YAML.
An example for Sipwise C5 firewall configuration in /etc/ngcp-config/config.yml enabling both the firewall subsystem and the logging facility may look like:
security: firewall: enable: yes logging: enable: yes file: '/var/log/firewall.log' tag: 'NGCPFW' policies: input: 'DROP' forward: 'DROP' output: 'ACCEPT' rules4: - '-A INPUT -i eth0 -j ACCEPT'
The Sipwise C5 comes with some default passwords the user should change during the deployment of the system. They have been explained in the previous chapters of this handbook.
Many Sipwise C5 services use MySQL backend. Users and passwords for these services are created during the installation. These passwords are unique for each installation, and the connections are restricted to localhost. You should not change these users and passwords.
The Sipwise C5’s super-user account comes with a preconfigured password. It is imperative that this password is changed by the operator immediately after Sipwise C5 is shipped and before it is connected to any potentially unsecure public or private network using a secure password in compliance with existing password policies of the operator. The "root" password must not be shared outside of the operator’s organization including Sipwise engineers. The "root" password must not be shared in any publicly accessible communications including e-mail or ticketing systems.
To change the root password log into the freshly deployed system as "root" using the preconfigured password and execute:
Then follow the prompts to change the password.
The Vagrant/VirtualBox/VMWare Sipwise C5 images come with more default credentials which should be changed immediately:
The Sipwise C5 Web-interface comes with a preconfigured "administrator" account deployed with a default password. This account can be considered Sipwise C5 application super-user and has far-reaching access to application specific settings via the Web-interface. It is imperative that the password for this account is changed by the operator immediately after Sipwise C5 is shipped and before it is connected to any potentially unsecure public or private network using a secure password in compliance with existing password policies of the operator. The "administrator" password must not be shared outside of the operator’s organization including Sipwise engineers. The "administrator" password must not be shared in any publicly accessible communications including e-mail or ticketing systems.
The password for the "administrator" account can be changed via the Web-interface.
The login for the system account cdrexport is disabled by default. Although this is a jailed account, it has access to sensitive information, namely the Call Detail Records of all calls. SSH keys should be used to login this user, or alternatively a really strong password should be used when setting the password via passwd cdrexport.
The root user in MySQL has no default password. A password should be set using the mysqladmin password command.
Generate new password for user ngcpsoap to access the provisioning interfaces, see the details in Section 11, “Provisioning REST API Interface”.
To mitigate possible system intrusions from the outside, it is commonly held best practise to disable remote root (administrator) logins. With remote root logins disabled, it’s still possible to log into the system via SSH to a regular, non-privileged user account, and then use sudo or su to elevate account privileges to root administrator level.
For system setup purposes, the default setting on the Sipwise C5 is to permit remote root logins via SSH. It is strongly recommended to change this default setting as soon as possible.
Once you’ve created a user account for yourself that can be used to gain root privileges, remote root logins can be disabled via the config switch sshd→permit_root_login in /etc/ngcp-config/config.yml.
sshd: permit_root_login: yes
Valid options are:
It is possible to enable logging for the input and output of commands run through sudo, along other meta-information like timing, to be able to reproduce sessions.
The logs are saved in directories with a special structure, the numbers are for a so-called "session" or sequence:
and within them, several files for tty input and output, stdin/stdout/stderr, and other ancillary files.
New session use 00/00/01, 00/00/02 and so on.
This is disabled by default, but can be configured in /etc/ngcp-config/config.yml with the following options:
sudo: logging: enable: no exclude_users:  max_sessions: 0
Valid options are:
This sudo plugin saves all input and output including passwords typed in shell prompts (even when they are not echoed to the screen), and this is unencrypted, so please consider the security implications.
Even if in some versions the compression of these files is enabled (releases mr9.5 and after), some commands can use huge amounts of data and fill-up the available disk space very quickly, and full disk will cause serious problems (failures in services, or even preventing external access to the system to fix the problems). Please consider setting up monitoring of free space, or mitigating measures like setting a small amount of sessions saved, taking data out the system often for preservation and deleting sessions from previous days, etc.
Additionally, this has a performance impact (both CPU and I/O) on every command run with sudo that triggers logging, negligible for most commands but significant when the input or output is large.
The Sipwise C5 provides default, self-signed SSL certificates for SSL connections. These certificates are common for every installation. Before going to production state, the system administrator should provide SSL certificates for the web services. These certificates can either be shared by all web interfaces (provisioning, administrator interface and customer self care interface), or separate ones for each them can be used.
Set the path to the new certificates in /etc/ngcp-config/config.yml:
The Sipwise C5 also provides the self-signed SSL certificates for SIP over TLS services. The system administrator should replace them with certificates signed by a trusted certificate authority if he is going to enable it for the production usage (kamailio→lb→tls→enable (disabled by default)).
Set the path to the new certificates in /etc/ngcp-config/config.yml:
The Sipwise C5 allows you to protect your VoIP system against SIP attacks, in particular Denial of Service and brute-force attacks. Let’s go through each of those attacks and let’s see how to configure your system in order to face such situations and react against them.
As soon as you have packets arriving on your Sipwise C5 server, it will require a bit of time of your CPU. Denial of Service attacks are aimed to break down your system
by sending floods of SIP messages in a very short period of time and keep your system busy to handle such huge amount of requests.
Sipwise C5 allows you to block such kind of attacks quite easily, by configuring the following section in your
kamailio: lb: security: dos_ban_enable: yes dos_ban_time: 3600 dos_reqs_density_per_unit: 50 dos_sampling_time_unit: 2 dos_whitelisted_ips:  dos_whitelisted_subnets: 
Basically, as soon as Sipwise C5 receives more than 50 messages from the same IP in a time window of 2 seconds, that IP will be blocked for 3600 sec, and you will see in the
kamailio-lb.log a line saying:
Nov 9 00:11:53 sp1 lb: WARNING: <script>: IP '184.108.40.206' is blocked and banned - R=<null> IDemail@example.com
The banned IP will be stored in kamailio memory, you can check the list via web interface or via the following command:
# ngcp-kamctl lb fifo htable.dump ipban
Excluding SIP endpoints from banning
There may be some SIP endpoints that send a huge traffic towards Sipwise C5 from a specific IP address. A typical example is a SIP Peering Server.
Sipwise C5 supports handling such situations by excluding all defined SIP Peering Servers from DoS protection mechanism.
The Sipwise C5 platform administrator may also add whitelisted IP addresses manually in
This is a very common attack that can be checked via the /var/log/ngcp/kamailio-proxy.log file. There will be INVITE/REGISTER messages coming in with strange usernames.
Attackers are trying to spoof/guess subscriber’s credentials, which allow them to call out.
The very first protection against these attacks is: ALWAYS USE STRONG PASSWORD.
Nevertheless, Sipwise C5 allows you to detect and block such attacks quite easily by configuring the following parameters in
kamailio: lb: security: failed_auth_attempts: 3 failed_auth_ban_enable: yes failed_auth_ban_time: 3600
It may be required to increase the number of failed attempts by adjusting the ban time (e.g. some users can be banned accidentally because they are not writing the right password). If a user tries to authenticate an INVITE/REGISTER (or more in general, any request containing an Authorization or Proxy-Authorization SIP header) and if it fails more than 3 times, the user@domain (not the IP as for Denial of Service attack) will be blocked for 3600 seconds (see failed_auth_ban_time on /etc/ngcp-config/config.yml). In this case, you will see the following lines in /var/log/ngcp/kamailio-lb.log file:
Nov 9 13:31:56 sp1 lb: WARNING: <script>: Consecutive Authentication Failure for 'firstname.lastname@example.org' UA='sipvicous-client' IP='220.127.116.11' - R=<null> IDemail@example.com
Both the banned IPs and banned users will be shown in the Admin web interface by accessing the Settings→Security Bans menu. To retrieve the same information from Kamailio memory, use the following command:
# ngcp-kamctl lb fifo htable.dump auth
The term "topology hiding" in SIP is used to describe the measures taken by typically an SBC (Session Border Controller) to hide detailed information of the internal network at the border of which it is located. Pieces of information such as IP addresses and port numbers used by SIP endpoints and intermediaries within the network are considered sensitive, as these can give some hints to potential attackers about the topology of the network.
In a typical SIP session the mandatory headers may carry that sensitive information, for example: Contact, Via, Record-Route, To, From, Call-ID. An SBC applying topology hiding will mangle the content of those headers.
Concealment of sensitive information using this mechanism is achieved through encoding the original content of selected SIP headers. Then Sipwise C5 will create a new SIP URI using a preselected IP address and the encoded content as URI parameter, finally re-assembling the SIP header.
Examples for encoded SIP headers:
Record-Route: <sip:127.0.0.8;line=sr-NvaAlWtecghucEhu6WtAcu...> Contact: <sip:127.0.0.8;line=sr-NvaAli-1VeL.kRxLcbN86W...>
The load-balancer element of Sipwise C5 has an SBC role, from the SIP peers point of view. The LB offers topology masking function that can be simply activated through a configuration change. By default the function is disabled.
Activating topology masking function is possible through the modification of the
following configuration parameters in
/etc/ngcp-config/config.yml file (shown
below with default values of parameters):
kamailio: lb: security: topoh: enable: no mask_callid: no mask_ip: 127.0.0.8
Meaning of the configuration parameters:
enable: if set to
yes, the topology mask will be activated
mask_callid: if set to
yes, the SIP Call-ID header will also be encoded
mask_ip: an IP address that will be used to create valid SIP URIs, after encoding
the real/original header content.
Any valid, preferably private network address can be used. The suggestion is however to use an address that is not used by any other SIP endpoint or intermediary element in the network.
Although masking sensitive information about a VoIP provider’s network is desired, there are some potential side effects caused by topology masking.
The most common example is the consequence that SIP message size may grow when applying topology masking. The fact that SIP messages become larger may even prevent Sipwise C5 from communicating successfully with another SIP entity (a peer SBC, for example). This can be expected under following circumstances:
In such a case the IP packets carrying SIP messages with encoded headers will have a size exceeding the MTU, that will cause loss of data in some networks.
The recommended solution in such a case is to use TCP transport for SIP messages.
This mechanism achieves topology hiding by stripping the SIP routing headers that show topology details and storing those data in the associative data structure (hash) in the Redis DB so that it can look it up when a reply or in-dialog SIP message comes in. From the signaling perspective it simulates a SBC (Session Border Controller) on the LB.
This mechanism offers some benefits over the older topology masking approach:
The module uses the auto-expiration of the Redis keys so it can cause temporary spikes in the memory usage and redis keys count until produced data is cleaned up by redis.
Activation of the topology hiding function is done through the modification of the
following configuration parameters in
/etc/ngcp-config/config.yml file (shown
below with default values of parameters):
topos: enable: no redis_db: 24
In order to activate the function, you should set enable: 'yes' in /etc/ngcp-config/config.yml and leave the Redis DB number unchanged, then execute ngcpcfg apply "activated topos".
The Sipwise C5 is a very flexible system, capable of serving from hundreds to several tens of thousands of subscribers in a single node. The system comes with a default configuration, capable of serving up to 50.000 subscribers in a normal environment. But there is no such thing as a normal environment. And Sipwise C5 has sometimes to be tuned for special environments, special hardware requirements or just growing traffic.
If you have performance issues with regards to disk I/O please consider enabling the noatime mount option for the root filesystem. Sipwise recommends the usage of noatime, though remove it if you use software which conflicts with its presence.
In this section some parameters will be explained to allow Sipwise C5 administrator tune the system requirements for optimum performance.
Table 19. Requirement_options
|Option||Default value||Requirement impact|
Heavy impact on the harddisk storage needed for mysql logs. It can help to restore the database from backups or restore broken replication.
For test systems or low RAM systems, lowering this setting is one of the most effective ways of releasing RAM. The administrator can check the innodb buffer hit rate on production systems; a hit rate over 99% is desired to avoid bottlenecks.
This setting affects the amount of RAM the system will use. Each kamailio-lb worker will have this amount of RAM reserved. Lowering this setting up to 8 will help to release some memory depending on the number of kamailio-lb workers running. This can be a dangerous setting as the lb process could run out of memory. Use with caution.
1/16 * Total System RAM
The installer will set this value to 1/16 of the total system RAM. This setting does not change even if the system RAM does so it’s up to the administrator to tune it. It has been calculated that 1024 (1GB) is a good value for 50K subscriber environment. For a test environment, setting the value to 64 should be enough. "Out of memory" messages in the kamailio log can indicate that this value needs to be raised.
Number of TCP workers kamailio-lb will spawn per listening socket. The value should be fine for a mixed UDP-TCP 50K subscriber system. Lowering this setting can free some RAM as the number of kamailio processes would decrease. For a test system or a pure UDP subscriber system 2 is a good value. 1 or 2 TCP workers are always needed.
Enable or not TLS signaling on the system. Setting this value to "no" will prevent kamailio to spawn TLS listening workers and free some RAM.
See kamailio→lb→tcp_children explanation
See kamailio→lb→tcp_children explanation. In this case the proxy only listens udp so these children should be enough to handle all the traffic. It could be set to 2 for test systems to lower the requirements.
Set the default and the max and min registration interval. The lower it is more REGISTER requests will be handled by the lb and the proxy. It can impact in the network traffic, RAM and CPU usage.
Interval for the proxy to send a NAT keepalive OPTIONS message to the nated subscriber. If decreased, this setting will increase the number of OPTIONS requests the proxy needs to send and can impact in the network traffic and the number of natping processes the system needs to run. See kamailio→proxy→natping_processes explanation.
Kamailio-proxy will spawn this number of processes to send keepalive OPTIONS to the nated subscribers. Each worker can handle about 250 messages/second (depends on the hardware). Depending the number of nated subscribers and the kamailio→proxy→natping_interval parameter the number of workers may need to be adjusted. The number can be calculated like nated_subscribers/natping_interval/pings_per_second_per_process. For the default options, assuming 50K nated subscribers in the system the parameter value would be 50.000/30/250 = (6,66) 7 workers. 7 is the maximum number of processes kamailio will accept. Raising this value will cause kamailio not to start.
1/16 * Total System RAM
See kamailio→lb→shm_mem explanation.
Set this to no if the system shouldn’t perform rating on the CDRs. This will save CPU usage.
If enabled, the system will send the log messages to an external server. Depending on the rsyslog→external_loglevel parameter this can increase dramatically the network traffic.
This setting will set the number of days ngcp logs under /var/log/ngcp will be kept in disk. Lowering this setting will free a high amount of disk space.
In case of using virtualized environment with limited amount of hardware resources, you can use the script ngcp-toggle-performance-config to adjust Sipwise C5 configuration for high/low performance:
root@spce:~# /usr/sbin/ngcp-toggle-performance-config /usr/sbin/ngcp-toggle-performance-config - tool to adjust Sipwise C5 configuration for low/high performance --help Display this usage information --high-performance Adjust configuration for system with normal/high performance --low-performance Adjust configuration for system with low performance (e.g. VMs) root@spce:~#
The Sipwise C5 platform provides detailed logging and log files for each component included in the system via rsyslog. The main folder for log files is /var/log/ngcp/, it contains a list of self explanatory log files named by component name.
The Sipwise C5 is a high performance system which requires compromise between traceability (maximum amount of debug information being written to hard drive) and productivity (minimum load on IO subsystem). This is the reason why different log levels are configured for the provided components by default.
Most log files are designed for debugging Sipwise C5 by Sipwise operational team while main log files for daily routine usage are:
|Log file||Content||Estimated size|
API logs providing type and content of API requests and responses as well as potential errors
Admin Web UI logs when performing operational tasks on the ngcp-panel
mediation and rating logs, e.g. how many CDRs have been generated and potential errors in case of CDR generation or rating fails for particular accounting data
Overview of SIP requests and replies between lb, proxy and sems processes. It’s the main log file for SIP overview
Overview of SIP requests and replies along with network source and destination information flowing through the platform
Overview of SIP requests and replies between lb, proxy and sems processes
rtpengine related log, showing information about RTP communication
it is highly NOT recommended to change default log levels as it can cause system IO overloading which will affect call processing.
the exact size of log files depend on system type, system load, system health status and system configuration, so cannot be estimated with high precision. Additionally operational network parameters like ASR and ALOC may impact the log files' size significantly.
The easiest way to fetch information about a single call among the log files is the search for the SIP CallID (a unique identifier for a SIP dialog). The call ID is used as call marker in almost all the VoIP related log file, such as /var/log/ngcp/kamailio-lb.log, /var/log/ngcp/kamailio-proxy.log, /var/log/ngcp/sems.log or /var/log/ngcp/rtp.log. Example of kamailio-proxy.log line:
Nov 19 00:35:56 sp1 proxy: NOTICE: <script>: New request on proxy - M=REGISTER R=sip:sipwise.local F=sip:firstname.lastname@example.org T=sip:email@example.com IP=10.10.1.10:5060 (127.0.0.1:5060) IDfirstname.lastname@example.org UA='SIP-UA 18.104.22.168'
The above line shows the SIP information you can find in a general line contained in /var/log/ngcp/kamailio-*:
In order to collect the full log related to a single call, it’s necessary to "grep" the /var/log/ngcp/kamailio-proxy.log using the ID= string, for example:
# grep "email@example.com" /var/log/ngcp/kamailio-proxy.log
The Sipwise C5 platform provides several tools to collect SIP traces. It can be used Sipwise C5 ngrep-sip tool to collect SIP traces, for example to fetch traffic in text format from outbound and among load balancer, proxy and sems :
# ngrep-sip b
see the manual to know all the options:
# man ngrep-sip
The ngrep debian tool can be used in order to make a SIP trace and save it into a .pcap file :
# ngrep -s0 -Wbyline -d any -O /tmp/SIP_trace_file_name.pcap port 5062 or port 5060
The sngrep debian graphic tool as well can be used to visualize SIP trace and save them in a .pcap file :