Audiocodes tunneling: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
===Basic options=== | ===Basic options=== | ||
The following options need to be enabled in the sniffer service configuration located at | The following options need to be enabled in the sniffer service configuration located at voipmonitor.conf for processing AudioCodes packets. | ||
audiocodes = yes | audiocodes = yes | ||
Latest revision as of 14:02, 29 August 2023
How to set voipmonitor
Basic options
The following options need to be enabled in the sniffer service configuration located at voipmonitor.conf for processing AudioCodes packets.
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
The following options can help you in case pure (non-encapsulated) packets are also visible to VoIPmonitor for the same call. These options specify the conditions under which RTP/RTCP packets should be assigned to the 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