Browse
 
Tools
Rss Categories

aasvr.cfg

Reference Number: AA-02244 Views: 258 0 Rating/ Voters

Audio Acquisition Server (AASVR) Configuration:


The aasvr.cfg file contains the appropriate settings for the Audio Acquisition Server service. This file is located in the folder where it was installed.

[APP]

This section contains application configuration settings for the Audio Acquisition Server


listener_host

Description: This is the local IP address on the Audio Recorder server that will be used to listen for inbound call traffic and audio (typically receives traffic from port mirroring on the managed switch)

Possible Values: This must be a valid local IP address

Default Value: Needs to be set by the customer.


report_host

Description: This is the IP address of the Audio Recorder service (AAREC).

Possible Values: This must be a valid local IP address, note that the local loopback address (127.0.0.1) should not be used here, but the local IP address instead, if the Audio Recorder is located on the same machine.

Default Value: 127.0.0.1


report_port

Description: This is the network port used by the Audio Recorder service (AAREC) to connect between the AASVR and AAREC. This should match the corresponding recording_port setting specified in aarec.cfg

Possible Values: A valid port number.

Default Value: 15000


license_server_ip_addresses

Description: The IP address or host-name and (optionally) the port of the License Server to use. 

Possible Values: A string of IP addresses or host-names followed optionally by a colon and a port number, separated by semicolons. E.g. you could specify 127.0.0.1:7569;10.0.0.1:4971 to use two License Servers -- the first at 127.0.0.1 and port 7569, the second at 10.0.0.1 on port 4971.

Default Value: 127.0.0.1:7569  ( license server on local machine )


route_uac_uas

Description: Network traffic flow that is scanned for SIP messages, can be ranges of addresses and ports; uac / uas defines RTP audio to be streamed

Possible Values: A string containing the IP address of the source (client) followed by an underscore, then the IP address of the destination (server) for SIP traffic. Each IP address is followed by a colon then a port to be used (0 indicates 'any'), then the string is appended with either _uac or _uas to indicate whether client or server traffic should be parsed.

A typical value here if SIP traffic (from a SBC for instance) is coming from 172.19.1.100 (multiple ports) and going to a PBX at 172.19.1.101 (to the default SIP port 5060), and the client packets should be parsed would look like this:

172.19.1.100:0_172.19.1.101:5060_uac

Format details:

One or multiple lines specifying an IP range for UAC, an IP range for  UAS, and the RTP traffic direction to be saved. Format using to specify IP ranges in Classless Inter-Domain Routing (CIDR) notation.

route_uac_uas=CIDRuac:port_CIDRuas:port_uacs

where:
     CIDRuac/CIDRuas = A.B.C.D/nbits
     port (default 5060)
     uacs = "uac" or "uas"

where nbits in CIDR indicate how many bits from the IP address use as 
matching network mask (default nbits = 32, i.e. match IP address only)

/*
 * address format    mask                num addresses
 *
 * a.b.c.d / 32        255.255.255.255        1
 * a.b.c.d / 31        255.255.255.254        2
 * ...
 * 0.0.0.0 / 0        0.0.0.0                4,294,967,296
 */

Default Value: Needs to be set by the customer.


sip_over_tcp

Description: Configures whether SIP over IP is to be used. The default is to only support SIP over UDP

Possible Values: 

  • false  = SIP over TCP is not supported)
  • true   = SIP over TCP is supported (contact your support team to determine whether this can be enabled)

Default Value: false


sip_enabled

Description: Since Audio Collector can be used with both SIP and TDM connections, this option specifies whether SIP should be enabled (and parsed)

Possible Values: 

  • true = SIP is enabled. SIP headers will be parsed for audio and call data
  • false = SIP is not enabled. SIP header processing will not be performed.

Default Value: true


passive_enabled

Description: Enables passive mode to receive telephony events from CTI Service. Typically either this or sip_enabled would be activated, depending on system architecture.

Possible Values: 

  • true = Passive mode is enabled. Call and audio related information will come from the CTI Service, as specified by an external Telephony Adapter (TA)
  • false = Passive mode is not enabled. No call data will be generated from the CTI Service.

Default Value: false


passive_host

Description: TCP listener IP for event message protocol (from CTI manager) - required if passive enabled. It can take the machine IP where the service is installed.

Possible Values: A valid IP address of the CTI Service (this is typically installed on the same machine, so 127.0.0.1 would normally be used)

Default Value: 127.0.0.1


passive_port

Description: Network port number for event message protocol when communicating with CTI Service. This should match the corresponding port number assigned to the CTI Service

Possible Values: A valid port number.

Default Value: 15001


session_timeout

Description: Timeout value for each session being monitored (in seconds). If a session persists for more than the specified session_timeout period, it will no longer be monitored.

Possible Values: The maximum number of seconds that each session should be monitored for

Default Value: 3600   (seconds)


receive_timeout

Description: The amount of time allowed for a connection to receive a message before timing out.

Possible Values: The maximum number of seconds assigned to each message before it times out.

Default Value: 3600


thread_count


Description: The number of processing threads for internal parallel processing, depending on machine CPU.

Possible Values: Depending on machine CPU this may vary from 1 to 32. Recommend: thread_count = current number of CPU cores.

Default Value: 1