Tools > Export & Import > Multiple Apresa servers

Recordings from one Apresa server can be exported to another Apresa over a secure channel.

Finished call recordings are sent using SFTP, which uses SSH on TCP port 22.

Active call information is sent over TLS on TCP port 9005.

A public key authentication mechanism is used. No passwords need to be shared between the two recorders.

This export/import function needs to be set up once, and then is a continuous background process (transfer can lag behind 1 to 15 minutes). The export includes meta data and recordings. It is expected to have little performance impact, compared to actual recording. It will use network bandwidth to transfer recordings. For the central Apresa you only need the base license, if you do not want it to do any recording itself.

Configuration of the sending Apresa

The Apresa can send recordings to another Apresa. To configure this feature, in the Tools menu, select Export & Import, then click the Export to Apresa server button. This will take you to the screen called Export recordings to another Apresa server.

To add an export target, click the Add button.

•Enabled: If an export target is not enabled, it is not processed

•Description: This description will be used to refer to this export target, for example in error reports

•IP Name of IP Address: The connection address of the Apresa to which the recordings must be sent

•Delay export: A recording will not be exported until the specified number of minutes have passed since the end of the call. Use this option to allow a time frame in which a finished recording can be edited (such as adding notes, or adding a screen recording), before it is exported. After a recording has been exported, new changes to the recording will not be synchronized.

•Send after / Send before: Specify after and/or before which time of day recordings should be exported (including call listing entries). For example, export after 02:00 before 04:00. The time period may cross midnight, for example after 22:00, before 05:00. The format 00:00 to 23:59 must be used. Both settings are optional and can be left blank to apply no restriction.

•Filter: When the filter is empty, all recordings will be exported. Otherwise, only the recordings of the phones of the specified user or group are exported.

•Restart from the beginning: Enable this option, to start again exporting from the first and oldest record.

•Restart from date: Start again exporting from the selected date. (The receiving side will reject records it already has.)

•Export active calls: Export real-time active call information to the other (central) Apresa. These calls will then also be visible in the other Apresa as active calls.

•Accept call actions: Accept and perform call actions, such as starting recording on demand, coming from the other recorder.

•Import recording configuration: Retrieve the recording configuration from the other (central) Apresa. The recording configuration includes the VoIP number lists, and the recording, delete, and silence on demand lists. This is done periodically. After receiving an updated configuration, it is applied to the recording engine automatically.

In this same screen, the public key of this Apresa can be viewed. We will need this information to configure the receiving Apresa to accept our recordings.

When exporting active calls to a central center, the certificate of the receiving server needs to be trusted by the sending server.

Configuration of the receiving Apresa

To allow another Apresa to upload recordings to our Apresa, this has to be specifically allowed first. To do so, in the Tools menu, select Export & Import, then click the Import from Apresa server button. Then click the Add button.

•Name: A descriptive name to remember which server we have given permission

•Public key: The public key of the Apresa that will be allowed to connect and upload recordings. The key starts with ssh-rsa.

•Import active calls: Allow the sub-Apresa to add calls to our active call list. These active calls can then be seen by web and PC clients, and used, for example, to initiate recording on demand, or to start screen recording.

•Export recording configuration: Send the recording configuration to the sub-Apresa. The recording configuration includes the VoIP number lists, and the recording, delete, and silence on demand lists.

•Certificate: A certificate is needed when importing active calls (it is currently not needed for importing finished calls). A certificate can be created or imported on the Certificates page. This certificates needs to be trusted by the sending Apresa.

For this feature to work, it is needed that Remote shell is enabled in the System settings. For safety, it is essential that the default password is changed.

Error diagnostic

Error status = SFTP error code 255. ... No route to host

Cause = The destination Apresa server is down or unreachable.

Error status = SFTP error code 255. ... Connection timed out

Cause = Possibly incorrect network routing.

Error status = SFTP error code 255. ... Connection refused

Cause = Remote shell is disabled.

Error status = SFTP error code 255. Permission denied (publickey, password).

Cause = The public key of the sending Apresa has not yet been added to the allow list at the destination Apresa (Tools, Export & Import, Import from Apresa server).

Error status = OK (incomplete)

Cause = Not an error, the receiving Apresa might not yet be finished with importing the uploaded recordings.

Error status = Send completed

Cause = Not an error, status is OK.