User guide

Aries Reference Manual Section 3 – Admin Functions
Radio Systems Information Ltd. Page 57
‘Two samples in each direction repeated twice’ – VQ test
call
Slave Probe The slave probe must be defined for VQ test calls
Speech Sample for VQ
test call
Select the required speech sample. The speech sample is
downloaded to the active and slave probe before each
survey. New speech samples may be uploaded to the
server using the ‘Manage Audio Samples’ link.
TETRA Call Rate Enter the time in seconds between TETRA test calls. The
fields below will then display the actual ‘Call length’, ‘Gap
between calls’ and ‘Actual call rate’ based on the selected
audio file and call type. Call Rates shorter than the length of
the call + 10sec call gap are ignored.
TETRA Group Call
Number
Enter the TETRA group call number (GSSI) for the group
that should be used for the test calls
TETRA Call Duration Enter the duration in seconds for the TETRA test call –
default is 10 – only applicable to non VQ test calls
TETRA Call Slot
Number
Enter the slot number from 0 to (Rate / Duration) = 29, this
should be different for each probe allocated for this group
and provides a timeslot within which to make the test call
therefore ensuring that test calls do not overlap – only
applicable to non VQ calls
Packet Tab
TETRA Packet Data
Test Rate
Enter the time in seconds between TETRA Packet Data
tests – default is 60, minimum is 60
TETRA Packet Data ftp
access parameters
Enter the ftp parameters
<server>[,<port>]:<username>,<password>
e.g. 10.20.30.40:user,pass
TETRA Packet Data file
path
Enter the folder / file name of the test file – default is
/Aries/testfile.bin
Clicking ‘Submit’ will set the New Configuration flag for the probe so that it updates itself next time it
checks for updates. The success of this can be seen from the ‘Update State’ column which will change
from ‘Updating Configuration to ‘Finished’ once the probe has been successfully updated and informed the
server of the outcome.
4.2.4 VQ Slave Probes
VQ Slave probes are listed separately from the normal probes – click on the ‘Slave’ link to list the slave
probes.
To carry out VQ testing, a normal probe must be paired with a slave probe. The slave probe is selected on
the ‘Call’ tab for the normal probe. Once selected, the slave probe will appear linked to the normal probe
as shown below:
Figure 64: Paired slave probe
Any configuration updates applied to the normal probe will also be applied to the slave probe – this
ensures that that they are both using the same GSSI, call type and speech sample.
Note that when VQ testing is started, the normal probe will often receive a configuration update, such as
start VQ survey, more quickly than the slave probe. This is because the normal probe will usually be
sending events back to the server more frequently than the slave so has more opportunities to check for a
new update. When starting a VQ survey, the normal probe will wait for the paired slave probe to confirm it
has received the configuration updates – this may take 1 or 2 minutes.
Slave probes do not produce normal monitor events. They do however produce all other events although
slave probe events are only visible to the sysadmin user.