In some installations, where external sites are connected, the telephony can work remotely. This has the advantage that voice data is processed locally at the location, but requires - if the bandwidth is narrow - that the files for operating the telephony server are also partly located locally.

The synchronization of the files is done by an rsync client, preferably the product "Acrosync". 

Furthermore, the usual alias acd-store is changed to point to the local machine. A new alias real-acd-store is set up, so that the access to the central, for rsync and also other reasons, can take place.

The only thing to note is that call logs (8-server logs) are no longer stored at the central office. This is done for performance reasons. This means that if a .r5 call log analysis is to be performed, it must be retrieved by hand.

File synchronization

Files are synchronized as follows:

Setup

Set up aliases

The hosts file in c:\windows\system32\drivers\etc\hosts is edited.

The following aliases are changed or adapted. This is done per remote Windows server, and must also be done per server individually.

Example entries:

192.168.114.82          acd-tel6 acd-store
10.200.21.98            real-acd-store

Set up Share

Via Windows Explorer, set up the share.

Right click on the C: drive: , then click "Give access to", "Advanced Sharing", and then again "Advanced Sharing".

Image Added

Enter "shared" as the share name:

Image Added

Then go to Permissions, and set "Full Control" for administrators. "Jeder" (everyone) can be removed. The final result will look like this. Attention: in this example the "administrator" was not available. Make sure to remove "jeder" and only have the administrators left with full control.

Image Added

Click on Apply.

Enable access to share via alias

This is not enough to access the share with the aliases \\acd-store\shared. This requires an additional command to make the alias known to the computer. 

First determine the Windows computer name with ipconfig.

Then, in a .CMD as administrator, type the following command:

Example:

Then, RESTART. It cannot continue without a restart.

For example, with:

Note: after the restart, the server applications will certainly not work properly, as there is currently no access to the portal software.

Installing Acrosync

Unfortunately, the service version of Acrosync cannot run a "permanent" job unless it is started as an application. For this reason Acrosync is not installed as a service. 

However, the application is installed for "All Users".

Note: the option "Install as Service" appears late in the installation. Under no circumstances tick it off!

Licensing Acrosync

The license can be installed as a trial. 

Attention: if a proxy server is available, the following registry keys must be created first:

Key: ProxyServer

Value: http://NameProxyServer:port

Example: http://kadprx.ad.kmoad.com:3128

Image Added

Note: this procedure is only verified with a proxy server without username / password.

The application can be installed as a trial first, and the license can be installed later.

Create profiles

The profiles that are created synchronize the data in both directions. To speed up this process, the following registry file can be used. 

ATTENTION: If profiles are exported from another computer, please DO NOT export the license, this will fail. It is best to use just the profiles and the corresponding entries from AcrosyncClient.

Acrosync.reg

Then, the Acrosync Client must be started and the password must be entered for each profile.

Then press start on each job. It may be that people complain because certain directories do not exist. Then create them using Windows Explorer.

First Sync

Close the Acrosync client with Quit (via the context menu in the system tray).

Initiate the first sync from the command line with the following commands :

"C:\Program Files (x86)\Acrosync\AcrosyncClient64.exe" -p JTEL
"C:\Program Files (x86)\Acrosync\AcrosyncClient64.exe" -p JTELCarrierPortal
"C:\Program Files (x86)\Acrosync\AcrosyncClient64.exe" -p system
"C:\Program Files (x86)\Acrosync\AcrosyncClient64.exe" -p resellers
"C:\Program Files (x86)\Acrosync\AcrosyncClient64.exe" -p voicemail
"C:\Program Files (x86)\Acrosync\AcrosyncClient64.exe" -p recordings
"C:\Program Files (x86)\Acrosync\AcrosyncClient64.exe" -p waves
"C:\Program Files (x86)\Acrosync\AcrosyncClient64.exe" -p LogFilesCall

Modify Startup

When the first sync is over, modify the startup.cmd for the 8 server and enter the following command:

start "" "C:\Program Files (x86)\Acrosync\AcrosyncClient64.exe" -a

Final inspection

Then reboot system, and check if after a few seconds:

• The Acrosync Client is visible in the system tray
• The jobs are all on green (running)
• The sync from local to remote also occurs immediately. For this, copy a few files into c:\Data\system\clients\1\recordings, c:\Data\system\clients\1\voicemail and c:\LogFilesCall, and see if the ones on \\real-acd-store\shared also exist in the target directory after a short time.

Cleaner Set up

Set up the following batch file:

Attention - /d -10 specifies the number of days before a file is deleted. It must be ensured that the number of days is adjusted according to the local disk, especially for c:\logfiles, since this can also grow accordingly depending on the call volume.

ForFiles /p "C:\LogFiles" /s /d -10 /c "cmd /c del /q @file"
ForFiles /p "C:\LogFilesCall" /s /d -10 /c "cmd /c del /q @file"
ForFiles /p "c:\Data\clients\1\recordings" /s /d -10 /c "cmd /c del /q @file"
ForFiles /p "c:\Data\clients\1\voicemails" /s /d -10 /c "cmd /c del /q @file"
c:
cd \LogFiles
for /f "delims=" %%d in ('dir /s /b /ad ^| sort /r') do rd "%%d"
cd \LogFilesCall
for /f "delims=" %%d in ('dir /s /b /ad ^| sort /r') do rd "%%d"
set errorlevel=0

Then set up this file with the scheduler for 00:00 at night, run with elevated privileges (as administrator).

Operations

If files need to be fetched from the central server because, for example, a patch has been applied, then proceed as follows:

• End Acrosync Client with Quit

• From the command line:

  "c:\Program Files (x86)\Acrosync\AcrosyncClient64.exe" -p JOB_NAME

  For example:

  "c:\Program Files (x86)\Acrosync\AcrosyncClient64.exe" -p JTELCarrierPortal

  
  

• Then restart the Acrosync Client with :
  

  "c:\Program Files (x86)\Acrosync\AcrosyncClient64.exe" -a

  
  

ATTENTION: if the client is not started with -a, the jobs are not started automatically, this must be done manually!

In manchen Installationen, bei den Außenstandorte angebunden werden, kann die Telefonie abgesetzt arbeiten. Dies hat den Vorteil, dass Sprachdaten lokal am Standort abgearbeitet werden, bedingt jedoch - wenn die Bandbreite schmal ist - dass die Dateien für den Betrieb des Telefonieservers auch teils lokal liegen.

Das Abgleichen der Dateien erfolgt durch ein rsync client, vorzugsweise das Produkt "Acrosync". 

Weiterhin, wird der übliche Alias acd-store so umgestellt, dass es auf den lokalen Rechner zeigt. Ein neuer Alias real-acd-store wird eingerichtet, sodass der Zugriff auf die Zentrale, für den rsync und auch sonstige Gründe, erfolgen kann.

Einzig was zu beachten ist, ist dass Call-Logs (8-Server Logs) nicht mehr an der Zentrale gespeichert werden. Dies erfolgt aus Performance-Gründe. D.h. soll eine .r5 Call-Log Analyse erfolgen, muss dies händisch geholt werden.

Dateiabgleich

Dateien werden wie folgt abgeglichen: