...
Code Block |
---|
|
<audio>
<obfuscation>
<dtmfStart>**</dtmfStart>
<dtmfStop>##</dtmfStop>
<dtmfTimeout>2000</dtmfTimeout>
<stopTimeout>5000<<stopTimeout>50000</stopTimeout>
<toneFile>
<default>{app}/tones/alaw.wav</default>
<codec id="0">{app}/tones/ulaw.wav</codec>
<codec id="8">{app}/tones/alaw.wav</codec>
</toneFile>
</obfuscation>
</audio>
|
...
Additionally, an obfuscation timeout can be specified to automatically stop the obfuscation after a specified period of time, to prevent the entire remaining call from being obfuscated in case the user forgets to manually stop the obfuscation. This timeout period can be specified (in milliseconds) using the
element.
Info |
---|
For the changes to take effect, access the Windows Services and restart the Echo service. |
Custom tones
Custom tones can be added to the call recorder in order to obfuscate part of a call recording. Since the tones are raw byte data that replace portions of the original WAV audio, they must respect the codec of the original file, e.g. a-law, u-law, etc., and use the same sample size and rate, e.g. 16-bit, 8 KHz.
Once the files have been encoded accordingly, they should be copied to the following location:
Referencemacro |
---|
Label | {app}\ProgramData\Tri-Line\Echo\tones |
---|
|
.To enable the system to use these custom tones during the obfuscation, open the
file, located in Referencemacro |
---|
Label | {app}\PrgramData\Tri-Line\Echo |
---|
|
and add the following snippet, specifying the filename of the custom tone using the element. The attribute determines the codec type, e.g. "0" = u-law, "8" = a-law, as per RFC3551 (page 32). A element can also be added as the fall-back tone to use. Code Block |
---|
|
<audio>
<obfuscation>
<toneFile>
<default>{app}/tones/alaw.wav</default>
<codec id="0">{app}/tones/ulaw.wav</codec>
<codec id="8">{app}/tones/alaw.wav</codec>
</toneFile>
</obfuscation>
</audio> |
Info |
---|
A <default> element can be added as the fall-back tone to use. |