Carin recording methods comparison

Carin recording methods comparison
Choosing the right recording technology
Detailed comparison of recording methods for Cisco Unified Communications systems
Choosing the right
recording technology
Detailed comparison of recording methods in
Cisco Unified Communications systems
Table of contents
Table of contents ................................................................................................................ 1
Introduction ........................................................................................................................ 1
Passive, extension side recording ....................................................................................... 3
Passive, trunk side recording .............................................................................................. 5
Native, extension side RTP forking ..................................................................................... 7
Active, conference based (JTAPI)........................................................................................ 9
Dial-in recorder ................................................................................................................. 11
Carin recording methods comparison .............................................................................. 12
Introduction
As more and more complex networks are deployed and the demand for voice recording
is higher than ever, choosing the most appropriate recording technology can be big
headache for network engineers and solution architects and can also save significant
amount of money if the right vendor and the right solution have been chosen.
TC&C, the developer of the award-winning voice, video and telepresence recording
platform - Carin, would like to help network engineers, IT managers and decision
makers fully understand the pros and cons of the each recording method and clearly
highlight the issues regarding each solution.
All contents are Copyright © 2000-2009 TC&C Ltd. All rights reserved.
Page 1 of 13
Choosing the right recording technology
Detailed comparison of recording methods for Cisco Unified Communications systems
This guide discusses the following recording methods available for Cisco Unified
Communications systems:
 Passive, extension side recording (SIP and/or SCCP)
 Passive, trunk side recording (SIP)
 Native, extension side RTP forking
 Active, conference based (JTAPI)
 Dial-in recorder
All contents are Copyright © 2000-2009 TC&C Ltd. All rights reserved.
Page 2 of 13
Choosing the right recording technology
Detailed comparison of recording methods for Cisco Unified Communications systems
Passive, extension side recording
The Passive recording method is deployed by connecting the recorder a monitor port
on a switch (in Cisco terminology it is called SPAN/RSPAN port). The monitor port
receives all of the traffic for each of the extensions that need to be recorded The
recorder captures all the traffic, including the RTP media streams and the SCCP or SIP
signaling messages.
In a Carin system, multiple recording servers can be deployed in order to support multisite networks and/or high volume systems with or without redundancy.
All contents are Copyright © 2000-2009 TC&C Ltd. All rights reserved.
Page 3 of 13
Choosing the right recording technology
Detailed comparison of recording methods for Cisco Unified Communications systems
Advantages











Disadvantages



There is no connection to the CUCM server(s), so there is no
extra capacity requirement at all.
In case of CUCM failure, the recording system is not
affected, the recording can work continuously even in SRST
(Survivable Remote Site Telephony) mode (if a local
recording server is deployed at the remote side).
Because of the passive approach, the flow of the call is not
affected at all.
Can be easily deployed and maintained.
Using Carin multi-site deployment architecture, the system
can be adapted very well to fit a wide array of use cases.
If high-volume traffic should be recorded, the system can be
scaled easily.
All types of calls can be recorded.
Monitor port technology is widely used approach. In most
cases it can be easily configured and used.
Recording of encrypted calls can be supported by
implementing a JTAPI module, which is responsible for
querying the SRTP (secure RTP) security keys for each call
from the CUCM while capturing the SRTP media streams in a
passive way. The call detail record information is extracted
from JTAPI, since the SCCP signaling messages are also
encrypted.
Silent monitoring can be supported natively by the recorder.
Video and TelePresence calls can also be recorded.
In complex switching infrastructure, the monitor port
configuration can be a headache.
In a multi-site network, branches where a few calls have to
be recorded, requires dedicated recording server.
Automatic announcement of the recording cannot be done
by the recorder itself. An external IVR should be involved.
All contents are Copyright © 2000-2009 TC&C Ltd. All rights reserved.
Page 4 of 13
Choosing the right recording technology
Detailed comparison of recording methods for Cisco Unified Communications systems
Passive, trunk side recording
The Passive Recording method is deployed by connecting the recorder to a monitor port
on a switch (in Cisco terminology it is called SPAN/RSPAN ports), The monitor port
receives all of the traffic for each trunk that needs to be recorded. The recorder
captures all of the traffic including the RTP media streams and the SIP signaling
messages.
In a Carin system, multiple recording servers can be deployed in order to support multisite networks and/or high volume systems with or without redundancy.
Advantages




There is no connection to the CUCM server(s), so there is no
extra capacity requirement at all.
In case of CUCM failure, the recording system is not
affected, the recording can work continuously even in SRST
(Survivable Remote Site Telephony) mode (if a local
recording server is deployed at the remote side).
Because of the passive approach, the flow of the call is not
affected at all.
Can be easily deployed and maintained.
All contents are Copyright © 2000-2009 TC&C Ltd. All rights reserved.
Page 5 of 13
Choosing the right recording technology
Detailed comparison of recording methods for Cisco Unified Communications systems





Disadvantages





Using Carin multi-site deployment architecture, the system
can be adapted very well to fit a wide array of use cases.
If high-volume traffic should be recorded, the system can be
scaled easily.
Monitor port technology is widely used approach. In most
cases it can be easily configured and used.
Silent monitoring can be supported natively by the recorder.
Mobile phones can be recorded if the calls are routed
through a SIP mobile adapter (makes sense for transferred
or forwarded calls only).
Encrypted calls cannot be recorded.
Internal calls between IP phones cannot be recorded.
Only SIP trunks are supported by Carin. (MGCP and H.323
are not supported)
Automatic announcement of the recording cannot be done
by the recorder itself. An external IVR should be involved.
Since SIP Trunks only support voice calls - only voice calls
can be recorded using this method.
All contents are Copyright © 2000-2009 TC&C Ltd. All rights reserved.
Page 6 of 13
Choosing the right recording technology
Detailed comparison of recording methods for Cisco Unified Communications systems
Native, extension side RTP forking
This recording method utilizes special features of the Cisco Communication Manager
introduced in version 6.0. It integrates call recording and silent monitoring features into
CUCM. If an extension is configured for recording (the configuration is available in the
CUCM), the CUCM instructs the phone to send the RTP streams related to a given call,
directly to the recording server utilizing the built-in bridge of the phone. The recording
system is connected to the CUCM via a SIP trunk to capture the signaling messages.
Additional call detail information is obtained by using a JTAPI interface.
Advantages


In a multi-site network, branches where few calls have to be
recorded, the deployment of a recorder does not require a
dedicated recording server for each remote site.
Theoretically this recorder eliminates the complexity of the
switching infrastructure compared to the passive recording
All contents are Copyright © 2000-2009 TC&C Ltd. All rights reserved.
Page 7 of 13
Choosing the right recording technology
Detailed comparison of recording methods for Cisco Unified Communications systems



Disadvantages







method, because the RTP streams are sent directly to the
recording server automatically.
Can be easily scaled by adding new recorders to the system
if more capacity is required.
Does not require extra DSP resources from the network
compared to the active (conference based) method.
Recording tone can be added by the phone.
Requires additional bandwidth on the network to the
recording server(s).
Since the recording functionality is controlled by the CUCM,
in case of a WAN link failure, the recording will not work at
all in the branch offices (if the CUCM is in the central site).
Cisco SRST (Survivable Remote Site Telephony) does not
support native recording.
Requires at least CUCM version 6.0.
Requires 3rd generation Cisco IP phones (7906G, 7911G,
7921G with Aug 2008 maintenance update, 7925G, 7931G,
7941G, 7941G-GE, 7942G, 7945G, 7961G, 7961G-GE, 7962G,
7965G, 7970G, 7971G-GE, 7975G, and IP Communicator
7.0(1)).
Requires extra capacity from the CUCM server(s) (each
recording session adds 2 calls to BHCC).
Does not support encrypted calls (will be available in CUCM
8.0).
Only voice calls are supported.
All contents are Copyright © 2000-2009 TC&C Ltd. All rights reserved.
Page 8 of 13
Choosing the right recording technology
Detailed comparison of recording methods for Cisco Unified Communications systems
Active, conference based (JTAPI)
An active recorder utilizes CTI by joining each caller via a conference bridge and records
the conference call. Cisco UCM supports TAPI and JTAPI for CTI (Cisco ICM has another,
powerful CTI server, called CTI OS). Because of the major limitations of this recording
method, we do not recommend using this solution, unless there is no other way to
record the calls.
Advantages








Disadvantages




In a multi-site network, branches where few calls have to be
recorded, the deployment of an active recorder does not
require dedicated recording server on the remote site.
An active recorder eliminates the complexity of the
switching infrastructure compared to the passive recording
method, because the conference calls are set up
automatically by the CUCM itself.
Can be easily scaled by adding new active recorders to the
system if more capacity is required.
Recording of encrypted calls can be supported (not
supported by Carin).
Recording tone can be played in by the recorder (not
supported by Carin).
Silent monitoring can be supported (not supported by
Carin).
Traditional on-demand recording, which only records from
when a user initiates the recording, can be supported.
Automatic announcement of the recording can be done by
the recorder.
In a multi-site environment, active recording is not a
preferred method, because each call will have an addition
call leg (RTP stream) to the conferencing resource,
depending on the IP telephony infrastructure, this can also
add overhead onthe WAN as well.
The IP telephony system has to support the increased
conference resource requirement (e.g. by adding additional
DSP resources).
Since every call is put into a conference by TAPI/JTAPI, in
case of WAN link failure, the recording will not work at all in
the branch office (if the CUCM is in the central site). Cisco
SRST (Survivable Remote Site Telephony) does not support
active recording.
Using TAPI/JTAPI will generate extra load on the CUCM
All contents are Copyright © 2000-2009 TC&C Ltd. All rights reserved.
Page 9 of 13
Choosing the right recording technology
Detailed comparison of recording methods for Cisco Unified Communications systems







server(s).
The installation and ongoing maintenance requires extra
tasks on CUCM (configuring CTI ports, JTAPI user, media
resources, etc.).
The user experience will change quite dramatically, because
every call will be a conference call actually (there is no
support in CUCM to secretly set up a conference in the
background). Most annoying issues:
Calling or called party numbers are hidden, “To Conference”
is displayed on the phones.
Call logs will include the automatic conference set up call
legs for each call.
Because of documented CUCM bugs/caveats/features,
certain complex call scenarios cannot be fully recorded (e.g.
the consultancy part of a call transfer cannot be recorded).
In Cisco UCC environment the historical call logs will be
changed/deferred.
Only voice calls are supported.
All contents are Copyright © 2000-2009 TC&C Ltd. All rights reserved.
Page 10 of 13
Choosing the right recording technology
Detailed comparison of recording methods for Cisco Unified Communications systems
Dial-in recorder
The dial-in recording method is designed to support special recording requirements,
where the cal which has to be recorded, is outside of the enterprise telephony system.
The users are manually conferencing in to a publicly available IVR, which can
authenticate the callers and offer recording capabilities. The mentioned IVR is
connected to the CUCM via a standard SIP trunk.
Advantages



Disadvantages


Any phone call can be recorded; even mobile phone calls are
supported.
Call playback on any phone device.
Supports silent monitoring.
No support for automatic recording, the conference has to
be manually set up on the phone device by the user.
In order to record multiple people – the recording port must
be confereced in manually by the user Only voice calls are
supported.
All contents are Copyright © 2000-2009 TC&C Ltd. All rights reserved.
Page 11 of 13
Choosing the right recording technology
Detailed comparison of recording methods for Cisco Unified Communications systems
Carin recording methods comparison
Feature
Passive,
extension
side
Passive,
trunk side
Native,
extension
side RTP
forking
Active,
conference
based
(JTAPI)
Dial-in
recorder
Recording internal calls
Yes
No
Yes
Yes
Yes
Recording
inbound/outbound calls
Yes
Yes
Yes
Yes
Yes
Automatic call recording
Yes
Yes
Yes
Yes
No
On demand call recording
Yes
Yes
Yes
Yes
Yes
Recording only a part of
the call
No
No
No
Yes
No
Recording encrypted calls
Yes
No
No
No
No
User experience is effected
No
No
No
Yes
Yes
Extra load on the CUCM
No
No
Yes
Yes
Yes
Extra DSP resource
requirement
No
No
No
Yes
No
Recording announcement
No
No
No
Yes
Yes
SRST support
Yes
Yes
No
No
Yes
Video call support
Yes
No
No
No
No
TelePresence support
Yes
No
No
No
No
Recording mobile phones
No
Yes
No
No
Yes
Silent monitoring support
Yes
Yes
Yes
No
Yes
Recorders can be placed
anywhere on the network
No
No
Yes
Yes
Yes
CUCM 3.x
or above
CUCM 4.x
or above
CUCM 6.x
or above
CUCM 3.x
or above
CUCM 5.x
or above
Cisco UCM requirement
All contents are Copyright © 2000-2009 TC&C Ltd. All rights reserved.
Page 12 of 13
Choosing the right recording technology
Detailed comparison of recording methods for Cisco Unified Communications systems
Headquarters
TC&C Ltd.
Wesselényi u. 35.
Budapest
H-1155, Hungary
T: +36 1 414 3069
F: +36 1 414 3079
info@tcandc.com
USA & Canada
TC&C U.S.A., Inc.
180 Main Street, Suite 2100
Hackensack,
New Jersey 07601, USA
T: 1-888-76-CARIN
F: 1-888-221-6684
info-usa@tcandc.com
EU Nordic
TC&C Nordic AB
Cylindervägen 18 plan 8
Nacka Strand,
Stockholm SE-13126, Sweden
T: +46 8 55 11 7000
F: +46 8 55 11 7001
info-nordic@tcandc.com
Romania
TC&C SRL
str. Crivatului nr. 60
Oradea
410136, Romania
T: +40 744 765611
F: +40 359 459418
info-ro@tcandc.com
www.tcandc.com
Unauthorized use, duplication, or modification of this document in whole or in part without the written consent of TC&C is strictly prohibited. By
providing this document, TC&C is not making any representations regarding the correctness or completeness of its contents and reserves the right to alter
this document at any time without notice. Due to continuous product improvements, features listed in this document are subject to change without
notice. Please contact TC&C for current product features and specifications. Cisco is a registered trademark of Cisco Systems Inc. Intel and the Intel logo
are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. All other trademarks mentioned
in this document are the property of their respective owners. Copyright © 2000-2009 TC&C Ltd. All rights reserved.
 Please consider the environment before printing this document.
Document ID: MB-CARINRTCOMP-EN-2009_1
All contents are Copyright © 2000-2009 TC&C Ltd. All rights reserved.
Page 13 of 13
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