Audiocodes tunneling: Difference between revisions

From VoIPmonitor.org
Jump to navigation Jump to search
Line 10: Line 10:


===Special options===
===Special options===
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).
Following options helps you in case that also the pure (non-encapsulated) packets are visible to voipmonitor (of a same call):
The options specifies conditions which rtp/rtcp packets should be assigned to CDR.
The options specifies conditions - which rtp/rtcp packets should be assigned to CDR.


  audiocodes_rtp  = no/YES/only/only_for_audiocodes_sip
  audiocodes_rtp  = no/YES/only/only_for_audiocodes_sip

Revision as of 12:30, 3 May 2023

How to set voipmonitor

Basic options

Following options needs to be enabled in the sniffer service configuration in /etc/voipmonitor.conf for audiocodes packets procssing

audiocodes           = yes 
#choose which transport protocol will be used for audiocodes and enabled the option
udp_port_audiocodes  = 925
tcp_port_audiocodes  = 925

Special options

Following options helps you in case that also the pure (non-encapsulated) packets are visible to voipmonitor (of a same call): The options specifies conditions - which rtp/rtcp packets should be assigned to CDR.

audiocodes_rtp  = no/YES/only/only_for_audiocodes_sip
audiocodes_rtcp = no/YES/only/only_for_audiocodes_sip


where the values means:

no                      - means no process rtp/rtcp encapsulated by audiocodes
yes                     - means process rtp/rtcp encapsulated by audiocodes - default YES
only                    - assigns only RTP/RTCP encapsulated by audiocodes to SIP sessions/CDRs (pure RTP packets if observed as well will be skipped)
only_for_audiocodes_sip - means that RTP/RTCP encapsulated will be assigned to a CDR only in case that SIP packets for this call were encapsulated by audiocodes as well