Audiocodes tunneling: Difference between revisions

From VoIPmonitor.org
Jump to navigation Jump to search
(Created page with "==How to set voipmonitor== ===Basic options=== Following options needs to be enabled in the sniffer service configuration in /etc/voipmonitor.conf for audiocodes packets proc...")
 
No edit summary
 
(6 intermediate revisions by 2 users not shown)
Line 1: Line 1:
==How to set voipmonitor==
== 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 options===
=== Basic Tunneling Options ===
Following options needs to be enabled in the sniffer service configuration in /etc/voipmonitor.conf for audiocodes packets procssing
To enable the processing of data from an Audiocodes tunnel, the following options must be enabled in the sniffer's configuration file (<code>voipmonitor.conf</code>).


  audiocodes=yes  
  audiocodes           = yes  
  #choose which transport protocol will be used for audiocodes and enabled the option
  # The main switch that activates the Audiocodes tunnel processing feature.
udp_port_audiocodes=925
tcp_port_audiocodes=925


===Special options===
# Next, define the ports on which the sniffer will listen for incoming tunneled data.
Following options helps you in case that also the pure (non-encapsulated) packets are visible to voipmonitor (of a same call - where are also packets encapsulated w audiocodes).
# Choose the transport protocol (UDP/TCP) used by your Audiocodes SBC and enable the corresponding option.
The options specifies conditions which rtp/rtcp packets should be assigned to CDR.
udp_port_audiocodes  = 925
tcp_port_audiocodes  = 925


audiocodes_rtp = no/YES/only/only_for_audiocodes_sip
=== Special Options for RTP/RTCP Handling ===
audiocodes_rtcp = no/YES/only/only_for_audiocodes_sip
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.


where the values means:
audiocodes_rtp  = no/yes/only/only_for_audiocodes_sip
no - means no process rtp/rtcp encapsulated by audiocodes
audiocodes_rtcp = no/yes/only/only_for_audiocodes_sip
yes - means process rtp/rtcp encapsulated by audiocodes - default YES
 
only - assigns only RTP/RTCP packets encapsulated by audiocodes to SIP sessions/CDRs (will not assigns pure RTP packets if observed as well, no matter if SIP arrived via audiocodes or not)
 
only_for_audiocodes_sip - means that RTP/RTCP packets encapsulated in audiocodes will be assigned only in case that SIP packets for this call were audiocodes encapsulated as well.
The values for these options mean:
* <code>no</code> - Disables processing of RTP/RTCP packets that arrive encapsulated in the Audiocodes tunnel.
* <code>yes</code> - Enables processing of RTP/RTCP packets from the tunnel. This is the '''default''' value.
* <code>only</code> - 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.
* <code>only_for_audiocodes_sip</code> - Tunneled RTP/RTCP packets are assigned to a CDR '''only if''' the SIP signaling for that call was also delivered through the Audiocodes tunnel.

Latest revision as of 23:39, 22 June 2025

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.
Retrieved from "https://www.voipmonitor.org//doc/index.php?title=Audiocodes_tunneling&oldid=5284"