Logging Recorder Capability Guide

Logging Recorder Capability Guide
March 2017
Release 4.4
Logging Recorder Interface
Capability Guide
Introduction
Scout provides a seamless interface to a solution for capturing
audio with an analog or Internet Protocol (IP) logging recorder for
conversations. Scout has the capability to capture per endpoint or
per console audio.
To keep a record of audio for archival purposes, a dispatching center frequently captures incoming and
outgoing audio on a logging recorder which can record audio on radio channels or telephone lines
continuously. The source of the recorded audio can be an endpoint or the console, and the recorder can
be a dedicated recorder or a computer using audio recording software.
For IP-based recorders, Scout uses the Real-time Transport Protocol (RTP) — as described in IETF RFC 3350
— to send voice packets. Also for IP-based recorders, Scout can be configured on a per-console or perendpoint basis to provide metadata with each recorded conversation. The metadata provides additional
information that is not available when listening to the recording. For example, the metadata can identify
the date and time of the call, the endpoint or the console involved in the call, and more. In some cases, the
metadata also allows the logging recorder to find recorded conversations easier during searches.
NOTE
A logging recorder is not the same as Scout's Instant Recall Recorder (IRR) feature. IRR is intended for
recording conversations that are retained for a limited period of time and then deleted automatically
by the Scout system.
Phone: 1-803.358.3600 • Fax: 1-803.358.3636
100 Innovation Place • Lexington SC 29072 USA
avtecinc.com • sales@avtecinc.com
1
Logging Recorder Interface | March 2017 | Release 4.4
Capabilities-at-a-Glance
Scout can record audio from multiple sources. The following table describes the different combinations of
sources and methods available for recording audio. The Network columns identify how the audio is
captured (IP Audio Capture Method), how the RTP streams are handled for each source (RTP Streams), and
how many IP recorders can be attached to a single endpoint (Simultaneous IP Recorders).
Network
Analog Audio
Capture Method
Audio Source
for Recording
Console Select audio
(including microphone and E911
NENA deskset audio when in use)
Note: Starting with version 2.5,
multiple logging recorders can be
used.
Console Unselect audio
Note: Starting with version 2.5,
multiple logging recorders can be
used.
Outpost audio
(Conventional radio or telephone
circuits)
Non-Avtec Endpoint audio
(For example: SIP, P25 or
MOTOTRBO)
IP Audio Capture
Method
RT
Streams
Yes – through media
Yes – through media
workstation audio
workstation AP Port
forwarding
One, mixed
Up to 2
One, mixed
Up to 2
Separate
transmit and
receive
Up to 4
Separate
transmit and
receive
Up to 4
Yes – through media
Yes – through media workstation audio
workstation AP Port forwarding
Yes – through
second Radio Port
One, mixed RTP
stream
N/A
Yes – through
VPGate audio
forwarding
Yes – through
VPGate audio
forwarding
Simultaneous
IP Records
The Scout System Administrator can configure the Scout Console to send metadata to an IP Logging
Recorder on a per-console or per-endpoint basis. The following table describes basic console metadata
features.
Metadata Origination
Scout Console
Endpoint/VPGate
Logging Frequency
Each conversational
talkspurt
Each conversational
talkspurt
Where Configured
Console Configuration
webpage
Endpoint's Audio
Forwarding driver
Audio Type
Digital - YES
Analog - NO
Digital - YES
Analog - NO
Recorder Type
Select - YES
Unselect - YES
Audio transmitted
toward the
endpoint
Audio received
from the endpoint
Phone: 1-803.358.3600 • Fax: 1-803.358.3636
100 Innovation Place • Lexington SC 29072 USA
avtecinc.com • sales@avtecinc.com
2
Logging Recorder Interface | March 2017 | Release 4.4
Recording Options
The first step in archival recording is deciding what to record. Scout provides the option to record all of the
following audio sources:
l
Scout Console Select audio, incoming only, or incoming and outgoing audio
l
Scout Console Unselect audio
l
Per endpoint (line) audio
These sources can be configured for recording using the Scout Manager software or the Outpost
Configuration page.
The next step is deciding whether to record the audio in analog mode or IP mode. The source of the audio
— console, Outpost, or other endpoint — can dictate the method used for recording (analog or IP) as
shown in the Capabilities-at-a-Glance table. In short, all Scout Console audio can be recorded with either
the analog or IP method.
NOTE
Endpoints such as SIP telephony devices, Project 25 (P25) endpoints, and other non-Avtec endpoints
must be recorded using the IP method.
Analog Recording
Scout Console and Outpost Audio
Analog recording for Scout Console and Outpost audio is accomplished by connecting the logging recorder
to the appropriate AP Port on the Scout media workstation. For Outpost audio, connect the recorder to the
second radio port on the Outpost device. Because Scout is an IP-based console, the primary recording
method is through an IP recorder. However, the analog recording method provides an interim solution
until you are ready to take advantage of the flexibility of an IP recording solution.
Scout Console Analog Audio
Recording devices connected to the Scout media workstation can capture Scout Console audio from the
Select and Unselect channels. The Scout Manager software provides options for configuring both the Scout
media workstation AP port used to capture the recorder's output and the audio to be recorded.
Configuration options include the following:
l
The AP port (destination) where the audio should be routed
l
A user-defined level of the audio
l
For Select audio, a choice to include the console microphone audio with the Select channel audio
For both Select and Unselect analog audio, the electrical interface is 600 ohms balanced.
Phone: 1-803.358.3600 • Fax: 1-803.358.3636
100 Innovation Place • Lexington SC 29072 USA
avtecinc.com • sales@avtecinc.com
3
Logging Recorder Interface | March 2017 | Release 4.4
Scout Console Analog Audio Recording
The diagram above illustrates analog Select and Unselect audio being captured for recording. Two
different AP Ports send the Select audio and Unselect audio to separate channels in the logging
recorder. If E911 (NENA-compliant) audio is included in the Select audio, it is included in the recording.
Phone: 1-803.358.3600 • Fax: 1-803.358.3636
100 Innovation Place • Lexington SC 29072 USA
avtecinc.com • sales@avtecinc.com
4
Logging Recorder Interface | March 2017 | Release 4.4
Outpost Analog Audio
For recorders connected to an Outpost device, the Outpost Configuration webpage provides several
options for configuring the audio source to the recorder. After setting the Service State for the Outpost
radio port to RECORD, configure options such as:
l
Audio Source – Receive audio from the field, transmit audio from the Scout Console, or both
receive and transmit audio
NOTE
The audio that is recorded is voice only. Paging tones and keying tones are not included.
l
Output Level – User-defined output level
l
Output Impedance – 600 Ohm Balanced or Single Ended
Outpost Analog Audio Recording
You can record audio from an Outpost connection using either the Radio Port or the Phone Port. Audio is
processed by VPGate for the console without any changes.
The diagram above shows a recorder connected to the Outpost Radio Port 2 recording audio from Radio
Port 1. The green lines indicate the audio that the Outpost device can send to the recorder. When
recording in this mode, Outpost only supports a single radio
Phone: 1-803.358.3600 • Fax: 1-803.358.3636
100 Innovation Place • Lexington SC 29072 USA
avtecinc.com • sales@avtecinc.com
5
Logging Recorder Interface | March 2017 | Release 4.4
The diagram above shows a recorder connected to the Outpost Radio Port 2 recording audio from the
Phone Port connection. The green line indicates the audio that the Outpost device can send to the
recorder. When recording Phone Port audio, Outpost does not support recording audio from Radio
Port 1.
IP Recording
Scout Console, Outpost, and Endpoint Audio
For Voice Over Internet Protocol (VoIP) recording (IP recording), Scout can handle all audio from the Scout
Console which includes Select and Unselect audio, plus all endpoint audio (Outpost endpoints and all
others). The audio packets sent to the recorder are standard RTP packets. When using IP recording, verify
that the network includes enough bandwidth to support IP recording. The required bandwidth can vary
from 30 kilobits per second (kbps) to 85 kbps, depending upon the audio codec in use.
Avtec tests the recording systems in its testing lab to verify recorders as compatible with VPGate and
Scout. The test criteria covers the following:
l
Capture of dedicated console audio IP streams (single combined RTP stream)
l
Capture of dedicated endpoint audio IP streams (separate receive and transmit RTP streams)
l
Playback of console audio streams
l
Playback of endpoint audio streams (must combine receive and transmit audio)
l
Capture of metadata as part of endpoint and console audio IP streams and metadata availability as
search tags and descriptors for playback.
Phone: 1-803.358.3600 • Fax: 1-803.358.3636
100 Innovation Place • Lexington SC 29072 USA
avtecinc.com • sales@avtecinc.com
6
Logging Recorder Interface | March 2017 | Release 4.4
The following table details the capability levels for recorders that proved compatible with Scout and
VPGate. Table information includes:
l
Audio Capture – Recorder can capture audio from a Scout system and play it back
l
Console Metadata – Recorder can capture and display metadata originating from a Scout console
l
Endpoint Metadata – Recorder can capture and display metadata originating from an endpoint
l
Metadata Search – Recorder can filter and find recording using metadata search tags
l
Configuration Guide – The vendor provides a guide for configuring the recorder with a Scout
system
Vendor
Audio
Capture/Playback
Console
Metadata
Endpoint
Metadata
Metadata
Search
Configuration
Guide
Accurate Always
YES
Eventide Inc.
YES
YES
YES
YES
YES
EXACOM, Inc.
YES
YES
YES
YES
YES
HigherGround, Inc.
YES
YES
YES
YES
YES
NICE
YES
YES
YES
YES
YES
Verint®
YES
YES
YES
YES
YES
Voice Print International,
YES
Inc. (VPI)
Other recorders have been connected with Scout at customer locations without being tested in the Avtec
laboratory for proven compatibility. These manufacturers include: CVDS, JEI, Redbox, Revcord, Stancil,
Uptivity, and DSS Equature.
Scout Console Audio
Just as an analog recording device connected to Scout media workstation can capture Select and Unselect
channel audio, a recording device connected to the Scout System through a LAN or WAN can capture VoIP
audio from the Select and Unselect channels. The Scout Console Configuration webpage provides options
for configuring the interface that connects the logging recorder to Scout.
For IP recording, the recorder connection is a network IP address instead of a physical AP port. The
configuration for a network-based recorder includes identifying the IP address for the recording device,
identifying a port number for each stream to be recorded, choosing whether a console microphone audio
should be included with Select channel audio, and selecting the codec used in the RTP stream sent from
the console to the recorder.
The codec is selected on a per console basis. Scout supports the following audio codecs: G.711, G.729a,
and G.726 (16K, 24K, 32K, and 40K).
Phone: 1-803.358.3600 • Fax: 1-803.358.3636
100 Innovation Place • Lexington SC 29072 USA
avtecinc.com • sales@avtecinc.com
7
Logging Recorder Interface | March 2017 | Release 4.4
Scout Console IP Audio Recording
The diagram above shows Scout Console IP audio and metadata being sent from the audio streams,
through the Ethernet port, over the network to the logging recorder. If E911 (NENA-compliant) audio is
included in the Select audio, it is included in the recording.
Endpoint Audio
Configuration for IP-based recording of Outpost (or any other endpoint) is done through the VPGate
Endpoint Configuration webpage by including an Audio Forwarding driver for the endpoint being
recorded. The Audio Forwarding driver sends RTP streams associated with the endpoint to the logging
recorder's network IP address. Scout supports up to four separate logging recorder addresses for each
endpoint. The Audio Forwarding Driver uses the same codec as the one selected for the endpoint driver.
NOTE
The codec is configured for the endpoint driver itself, not for the Audio Forwarding driver. However
for endpoints that use a proprietary codec, such as P25 endpoints, Scout translates the proprietary
codec to G.711.
Phone: 1-803.358.3600 • Fax: 1-803.358.3636
100 Innovation Place • Lexington SC 29072 USA
avtecinc.com • sales@avtecinc.com
8
Logging Recorder Interface | March 2017 | Release 4.4
Endpoint IP Audio Recording
When recording IP endpoint audio, VPGate's Audio Forwarding driver sends packets of receive audio and
transmit audio to up to four recorders. The recorders must have the capability to mix the audio
streams. The Audio Forwarding driver also captures and sends metadata, if configured.
Logging Recorder Requirements
For IP recording, a logging recorder must have the following capabilities for it to accept and record packet
streams, on a per endpoint basis, from the Scout System:
l
l
l
Record RTP audio streams (no call setup/teardown) using one of the codecs supported by the Scout
Console System (G.711, G.729a, or G.726).
Use VOX or silence suppression techniques to avoid recording long periods of no audio or low
audio. Scout does not send update messages for active audio.
Record audio channels comprised of either single or dual-channel RTP streams. Dual-channel RTP
streams include one stream for transmit audio and another for receive audio for a single
conversation. The recorder must combine the two streams either at record-time or playback-time
to provide a single audio stream.
Phone: 1-803.358.3600 • Fax: 1-803.358.3636
100 Innovation Place • Lexington SC 29072 USA
avtecinc.com • sales@avtecinc.com
9
Logging Recorder Interface | March 2017 | Release 4.4
Logging Console and/or Endpoint Metadata
The Scout Project Administrator can configure each console and endpoint to send and log metadata. This
lets the Scout Project Administrator identify the audio of individual conversation talkspurts with the
console's endpoints.
NOTE
Console-to-console intercom audio is also tagged with metadata.
Console and endpoint metadata is the contextual information attached to individual talkspurt conversations
captured on logging recorders. When a talkspurt conversation is recorded, its identifying metadata is also
recorded and attached to it.
The metadata provides additional information. Depending on the endpoint type, the metadata can include
the name of the endpoint, the current frequency, and the ANI or Caller ID. Scout System Administrators
can configure the capturing and sending of metadata on a per-console and per-endpoint basis.
The exact console and endpoint metadata elements recorded depends on the capabilities of each logging
recorder. The following table provides a sample of the elements available for the Scout Console. The
elements apply to both console and endpoint metadata, except where noted.
NOTE
For a complete list of metadata captured by Scout, see the Metadata Protocol Specification
document.
Element
Console ID
Description
Two 32 bit IDs. ID1 is the IP address of the Scout Console. ID2 is not needed for
Scout and should be set to zero.
User Login Name (console only) Login name of the user who has logged on to the console
Endpoint Name
Name of an audio endpoint such as a radio base station or a telephone line
Talker List (endpoint only)
The list of talkers on the endpoint (e.g., console ID, patch number, or system
bridge list)
Frequency
Frequency on which transmission takes place
ANI or Caller ID
ANI of the caller
Endpoint State (console only)
The state in which the endpoint is placed, on the console by the dispatcher (e.g.,
Select, Unselect, Mute)
VOX (console only)
The VOX presence for the endpoint
Unit ID (Dialed Number or
Telephone Number)
The dialed number from the dialer, when an outbound call is made
Talkgroup
Talkgroup of the radio
Call Type (console only)
Whether it is a unit call or a group call
Emergency State
Emergency state of the endpoint
P25 NAC
P25 Network Access Code of the endpoint (radio)
Phone: 1-803.358.3600 • Fax: 1-803.358.3636
100 Innovation Place • Lexington SC 29072 USA
avtecinc.com • sales@avtecinc.com
10
Logging Recorder Interface | March 2017 | Release 4.4
Element
Recording Notification
Description
Transmit Encryption Key
Encrypt Key ID of the endpoint transmitting audio
Receive Encryption Key
Encrypt Key ID of the endpoint receiving audio
Audio Direction (console only)
Whether the audio is inbound or outbound
Transmit Analog/ Digital Mode
Transmit audio type - whether analog or digital
Receive Analog/ Digital Mode
Receive audio type- whether analog or digital
Transmit Clear/ Encrypt Mode
Transmit audio mode - whether clear or encrypted
Receive Clear/ Encrypt Mode
Receive audio mode- whether clear or encrypted
Patch Number
Indicates which patch the endpoint is present
KEY State
Endpoint’s transmit key state
When configuring an endpoint for logging (archival) recording, the endpoint configuration in VPGate
provides an option to generate a beep tone to alert the dispatcher, the caller, or both that the conversation
is being recorded. The Scout Console media workstation generates the beep tone during the conversation.
For full duplex lines, the media workstation mixes the beeps toward the caller into the transmit audio
stream. For duplex or simplex lines, the media workstation generates the beep when the dispatcher
presses the push-to-talk button. The Scout system administrator configures the beep tone frequency,
duration and interval on a system-wide basis.
NOTE
The notification beep tone is required by law in some jurisdictions when recording certain types of
conversations.
Licensing
Avtec does not charge a separate licensing fee for the logging recorder capability. Third-party logging
recorder vendors may require licensing for use with Scout.
The material in this document is for information only and is subject to change without notice.
While reasonable efforts have been made in the preparation of this document to assure its
accuracy, Avtec, Inc. assumes no liability resulting from errors or omissions in this document,
or from the use of the information contained herein. Avtec, Inc. reserves the right to make
changes in the product design without reservation and without notification to its users. Avtec
updates capability guides as changes occur. A capability guide could be the most current yet
reflect a prior Scout release number if changes were not necessary at each release.
Scout™, VPGate™, Frontier™, Avtec SIP Proxy™, ScoutLink™, CommScape™, and Outpost™
are trademarks of Avtec, Inc.
© Avtec, Inc. 2017.
Phone: 1-803.358.3600 • Fax: 1-803.358.3636
100 Innovation Place • Lexington SC 29072 USA
avtecinc.com • sales@avtecinc.com
11
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising