About Secure Recording
Connector Service (SRC)
The Mitel Secure Recording Connector (SRC) behaves as
a server, handling authenticated connections from Call Recording Equipment
(CRE) and granting access to call setup information and copies of
media streams (audio only).
The connection setup flow is as follows:
- CRE is enrolled as an authenticated call recording
endpoint, for details see. This step is only performed once.
- CRE connects to MBG on TCP port 6810 using TLS with
mutual authentication.
- CRE sends a register request
message to MBG. This message contains a list of features that
the CRE supports.
- SRC replies with a matching (or lesser) feature
list.
- SRC sends a list of all the currently connected
devices as well as a list of all the SRC nodes in the MBG cluster.
- At this point the CRE is up
to date and the following happens in real time.
- When devices connect or disconnect, events are
sent to the CRE.
- When devices start and end calls, events are
sent to the CRE.
At any point, the CRE can request a tap on calls and the
corresponding media streams will be forked and a copy sent to the
CRE.
There is no fixed limit on the number of CRE's that can
connect to a single SRC. There will be engineering limitations.
A single CRE or multiple CRE's can request multiple taps
on the same call, with engineering limitations (and for indirect recording,
a hard limit of 3).
The SRC allows a Call Recording Equipment (CRE) to record
calls in one of the following modes:
Direct Call Recording
With direct call recording, the MBG server is positioned
between the call server and the devices/trunks handling both signaling
and media. This puts the MBG in a position to send a copy of the
media streams to the CRE on request.
Direct call recording is supported on:
- Any MiNET MiVoice IP phones or softphones
connected with MBG in a MiVoice Business deployment
- Any SIP device registered with MBG
- Any SIP trunk using MBG as an outbound proxy
Note:
- Local streaming will not take effect if
a CRE is connected to MBG
- Tone
Injection can be controlled either by the CRE
or MBG
- The SRC service is not limited to recording
the prime DN of the telephone; however, the configuration
or programming of the CRE can introduce this restriction
- The CRE might impose codec
restrictions (for example, no support for G.722
or G.722.1)
- An SRC license is required for each recorded
call for each CRE request
- A transcoding license is required if the
CRE requests the recorded audio to be sent using a specific
codec (ex: G.711U)
- Internal MiNET phones can be pointed at
MBG instead of MiVoice Business either automatically using
DHCP or manually using the Teleworker setting. For details,
see Selecting
Sets to Record
Deployments
Direct call recording is supported in all MBG deployment
in any network profile.
To record internal devices, setup a MBG in a LAN network
profile.
To record both internal and teleworker devices, setup one of
the following configuration:
- An MBG on the LAN to handle internal devices
and an MBG on the edge to handle teleworker devices. The
CRE must make a connection to each MBG.
- (MiNET only) An MBG on the LAN to handle
internal devices and an MBG on the edge to handle teleworker
devices. The edge MBG is configured in a daisy-chain pointing
teleworker devices to the LAN MBG. The CRE makes a single
connection to the LAN MBG.
- MBG on the edge handling both internal and
teleworker devices. All devices must be configured to
use the external interface of MBG. This configuration
requires additional bandwidth and teleworker licenses
for all devices unless network routing allows internal
devices to reach MBG's external interface via MBG's internal
interface. The CRE makes a connection to the edge MBG.
Indirect Call Recording
With indirect call recording, the remote devices are
registered directly to MiVoice Business instead of the MBG. MBG
acts as a broker between the call recorder, platform and devices.
The device duplicates its audio stream and sends it to the CRE.
Indirect call recording is only supported on:
- MiNET 5300-series and 6900-series MiVoice
IP Phones
- MiVoice Business release 5.0 SP1 or later
- Any MiNET device registered with any MBG.
MBG adds Indirect Recording capability for all connected
MiNET devices. This is primarily used to support Indirect
Recording for teleworker sets.
Note:
- This mode is supported by a limited range
of CREs
- To record MiNET 6900-series MiVoice IP Phones,
the CRE must support the newer SRTP ciphers available
in version 1.6+ of the SRC protocol.
- Recording tones cannot be injected by either
the CRE or MBG
- A maximum of 3 CREs can request to record
a given call
- The CRE might impose codec restrictions
in the deployment of MiVoice Business
Deployments
For Indirect recording, use a LAN-based SRC with no
sets connected to give the CRE access to all the sets that are
connected to the MiVB. You can, however, use any MBG to gain this
capability so an existing deployed MBG (for Teleworker) can also
be used for indirect call recording.