Audiocodes tunneling

VoIPmonitor Configuration for Audiocodes Tunneling

This guide explains how to configure VoIPmonitor to process packets that are tunneled from an Audiocodes Session Border Controller (SBC). This specific setup is for capturing data sent through the Audiocodes tunnel and differs from the standard configuration for capturing direct network traffic.

Basic Tunneling Options

To enable the processing of data from an Audiocodes tunnel, the following options must be enabled in the sniffer's configuration file (voipmonitor.conf).

audiocodes           = yes 
# The main switch that activates the Audiocodes tunnel processing feature.

# Next, define the ports on which the sniffer will listen for incoming tunneled data.
# Choose the transport protocol (UDP/TCP) used by your Audiocodes SBC and enable the corresponding option.
udp_port_audiocodes  = 925
tcp_port_audiocodes  = 925

Special Options for RTP/RTCP Handling

These options address scenarios where VoIPmonitor can see both 'pure' (non-encapsulated) network packets and packets encapsulated within the Audiocodes tunnel for the same call. They allow you to specify which packets should be assigned to the final CDR, preventing data duplication.

audiocodes_rtp  = no/yes/only/only_for_audiocodes_sip
audiocodes_rtcp = no/yes/only/only_for_audiocodes_sip

The values for these options mean:

• no - Disables processing of RTP/RTCP packets that arrive encapsulated in the Audiocodes tunnel.
• yes - Enables processing of RTP/RTCP packets from the tunnel. This is the default value.
• only - Assigns only RTP/RTCP packets that are encapsulated in the Audiocodes tunnel to the call/CDR. Any pure (non-encapsulated) packets for the same call, if also seen by the sniffer, will be ignored.
• only_for_audiocodes_sip - Tunneled RTP/RTCP packets are assigned to a CDR only if the SIP signaling for that call was also delivered through the Audiocodes tunnel.