How to configure the card recording applications

[Belinda Frick]

AMTPRIServer
In the ini file there is some setting up to do.

eg.
[NETWORK]
SERVERIP=gem //Amethyst server
SERVERPORT=27000 //Port on Amethyst server
CLASSC=001 //Added to reference number
LOCALUDPPORT=27002 //Port to listen for UDP messages
STATUSIP= //Where to send status, Amethyst server
STATUSPORT=0 //Port to send on

[CHANNELS]
;CHANNEL=1,on; CHANNEL=0,off
0=0
1=1
[TRUNKS]
;TRUNK=CHANNEL
150=0
151=1
[CONFIG]
WORKPATH=.\work\ //Where live files will be worked on
AGC=0 //To enable AGC on the card
WRITELOG=0 //Writes extra info to log file
LICENSES=237 //Internal setting, do not change
MIN_LENGTH=2 //Minimum length in seconds
MASTER=1 //If termserver and pri on same PC,
//PRIServer will receive the Topaz info from TermServer
CLIENT_INT=0 //True for client integration
SEND_CLIENT_INFO=0 //True for client integration
TERMSRV_NAME= //If integration is used, enter termserver host name

[EXTENSIONS]
;EXTENSIONS=1,on; EXTENSIONS=0,off
;if 0, all calls for that extension will be deleted.
;if 1, will use one license.

4099=1
4501=1

[BOARD_NUMBERS]
;BOARD=1,on; BOARD=0,off
;Refere to the section below names "Board_Numbers".

0=1
1=1



In the CHANNELS section all the channels need to be listed.
This list will build the leds on the display of the program.
If you want to disable curtain channels, write "=0" for false.
Each channel needs to be assighned to a channel for mapping
purposes.
This is done in the TRUNKS section.
The monitored extensions are the only recordings that will be
processed, the rest will be deleted. This is configured
in the EXTENSIONS section. If you want the extention to be
in the list, but not monitored, add the extension with "=0".

The PRIServer needs to know which boards it needs to connect
to. This is done in the BOARD_NUMBERS section. 1 will be
enable and 0 is disable.

AmtSmartSrv

[NETWORK]
SERVERIP=192.168.15.1 //IP of Termserver
CLASSC=001 //Added to reference number
LOCALUDPPORT=27020 //Internal setting, do not change
SERVERPORT=27002 //Port on Term server
[CHANNELS]
2=1
3=1

[CONFIG]
WORKPATH=E:\Datatex\AmethystShared\ //Where GSM file will be written
MAXSILENCE=3000 //If in noise mode, this is how long
//the silence will be to stop recording
BEEP=1 //Disables beep in background of recording

[BOARD_NUMBERS]
2=1

CLASSC is used for when there is more than one card server.
This value will be added to the beginning of the reference
number of all recordings on this PC.
Same as the PRIServer, all channels need to be configured. It
uses this list to build the display of leds. 0 is disabled and
1 is enabled.
The AmtSmartSrv needs to know which boards it needs to connect
to. This is done in the BOARD_NUMBERS section. 1 will be
enable and 0 is disable.

Note
Channel numbers on one pc is concurrent. This meens that if the
first card has 8 channels (0-7) and the second card has 4 (8-11),
you will configure 0-7 with card 0 on the one program and 8-11 with
card 1 on the second program.

AmtTermSrv
The Termserver - Smartworks solution can record analog extensions or
lines.
Extension side setup
eg.
[NETWORK]
SERVERIP=gem //Amethyst server
SERVERPORT=27000 //Port on Amethyst server
LOCALTCPPORT=27009 //TCP port to listen on
BaseVoicePort=27030 //Port where agents start to listen
LOCALSERVRE=192.168.15.1 //Term Server IP
TOPAZPORT=25000
TopazServer=192.168.15.1 //Topaz IP

[SETUP]
UPDATEAMT=1 //Send status to amethyst server
USETHREAD=0 //Use thread to process messages
USESTREAMS=0 //For live streaming
//DT files get written
CALLINFOPATH=C:\Program Files\Datatex\Amethyst\Shared\
SENDCALLSTATUS=1 //Must Term server update amt live
RECORDEXTSIDE=1 //Ext side recordings
MASTER=1 //Set master-slave status
PRI=1 //Being used for PRI client integration

[FTP]
FTPLOGIN=AMTCLIENT //FTP settings
FTPPASSWORD=AMTCLIENT
FTPSERVER=192.168.15.3
FTPONLINE=0

[USERS]
207=004|192.168.15.198|
105=003|192.168.15.198|

This needs to be done in the term servers ini file.
ext=channel|IP|
The RECORDEXTSIDE field is new and may not be present. This field is
only needed for line side recording.
Line side setup
eg.
[NETWORK]
SERVERIP=gem //Amethyst server
SERVERPORT=27000 //Port on Amethyst server
LOCALTCPPORT=27009 //TCP port to listen on
BaseVoicePort=27030 //Port where agents start to listen
LOCALSERVRE=192.168.15.1 //Term Server IP
TOPAZPORT=25000
TopazServer=192.168.15.1 //Topaz IP

[SETUP]
UPDATEAMT=1 //Send status to amethyst server
USETHREAD=0 //Use thread to process messages
USESTREAMS=0 //For live streaming
//DT files get written
CALLINFOPATH=C:\Program Files\Datatex\Amethyst\Shared\
SENDCALLSTATUS=1 //Must Term server update amt live
RECORDEXTSIDE=0 //Line side recordings
MASTER=1 //Set master-slave status
PRI=1 //Being used for PRI client integration

[FTP]
FTPLOGIN=AMTCLIENT //FTP settings
FTPPASSWORD=AMTCLIENT
FTPSERVER=192.168.15.3
FTPONLINE=0

[USERS]
001=004|192.168.15.198| //Setup users
003=003|192.168.15.198| //Must be IP address of term server

Ext-side vs Line-side
Instead of mapping the ext to the device like with ext side recording,
now you will map line number to device number. Also change the
RECORDEXTSIDE field to 0. If this field does not exist in the [SETUP]
section, just add it before you start the Term server.

All the other information can be changed when the program is started up
and you double click on the agent.

AmtFileMan
This application archives the files that gets written by the smartworks
recorder and the term server into ZLB format. Just configure the
source and target directories and the file age. The file age is how
old the files must be before it will archive to ZLB.

DFM
This program can FTP or move a file to a certain location for the sweeper
to sweep.

Please Note
Because the PRIServer and the Term server both listens for Topaz data you
will have a problem if both of them run on the same PC. You can fix this
by looking in the ini files of both programs. In the Term Server's ini file
the section will be [SETUP] and in the PRIServer it will be [CONFIG]. The
field is Master. Change the PRIServer to Master=0 and leave
the Term server on Master=1. The Term Server will now send all
messages that it receives on to the PRIServer.

TOPAZ
Topaz gives the call data for the card servers to map correctly. If you are
runnig a Term server witch is set to record extension side. The Amethyst IP
must be set per extension in Topaz. If the solution is line side, the
lines that are being tapped must be configured in Topaz with the IP of the
PRIServer or TermServer.