OVERVIEW AUDIO FILE TRANSFER


•  The task of the transfer-script is to move the audio file to an external storage (and remove it from the anSwitch server).

• The Call Recording creates a WAV-formatted audio file

• When the call recording is finished then automatically the defined transfer-script is started which transfers the audio file to
the desired call recording storage.

• The transfer-script is usually created by the customer.

OVERVIEW AUDIO FILE TRANSFER

ENVIRONMENT VARIABLES FOR THE TRANSFER-SCRIPT


EXAMPLE OF A TRANSFER-SCRIPT


ATTRIBUTE PARAMETERS FOR THE TRANSFER-SCRIPT


• In addition to the environment variables, it is also possible to create and use customer defined variables as OrgUnit attributes. These will be passed to the transfer-script as well.
- For example, this can be used to insert a server name or the login credentials for the remote server into the transfer-script.


• Create a customer defined variable:
- Define an OrgUnit attribute that starts with "record." . Example:
Attribute : record.call_repository Value : call_rep.yupi.com


- In the transfer-script use the OrgUnit in the normalized form
Example:
record.call_repository  Normalized: RECORD_CALL_REPOSITORY

EXAMPLE OF A TRANSFER-SCRIPT CUSTOMER ATTRIBUTE


The previous simple example now by using the defined customer
attribute :
record.call_repository  Normalized: RECORD_CALL_REPOSITORY


INSTALLATION OF THE TRANSFER-SCRIPT

• The transfer-script must be installed on all MediaControl components of the anSwitch by an Aarenet system engineer.
• The transfer-script runs on the MediaControl component where the audio file was created.
• To make the transfer-script accessible from the host and from within the MediaControl container it should be placed in the host directory:
/etc/aareswitch/mediacontrol/
• Don't forget to make the file permissions executable e.g., for PBX Yupi