- Active Server
server is a primary server or secondary server with one instance of the API
service, configuration service, call control service, media service, database
service, and the SM agent. A MediaSense cluster must have one or two active
servers. Replication is available in both active servers. To ensure high
availability, if one active server goes down, the other active server can
handle the complete load for both servers.
- API Service
application programming interface (API) service is a feature service. Each
MediaSense cluster can only have two instances of the API service. One instance
is in the primary server and another instance is in the secondary server. Each
API service must have a corresponding configuration service. If a MediaSense
cluster has more than two servers, the additional servers do not have an API
service or configuration service. Each instance of the API service corresponds
directly to one instance of the meta database.
- Call Control
uses the session initiation protocol (SIP) to control new calls, transferred
calls, and calls that are placed on hold.
- Call Control
control service communicates with the network layer, media service, and API
service to provide key recording functions for MediaSense. One instance of the
call control service is present in each server in a cluster.
servers are deployed in a cluster. A cluster can contain from one to five
servers. Each cluster can provide basic media recording, database storage, and
scalable recording capacity.
configuration database is often referred to as the 'config' database. It stores
log level and trace mask information. Each instance of the configuration
database corresponds directly to one instance of the configuration service.
Although the configuration database is not directly exposed to end users, you
can indirectly configure functions such as service activation in the MediaSense
Serviceability web portal.
Configuration service is a feature service. Each instance corresponds directly
to one instance of the configuration database. Each MediaSense cluster can only
have two instances of the configuration service. One instance is in the primary
server and the other instance is in the secondary server. When one
configuration service does not function, data can continue to be written to the
other configuration service because MediaSense uses a peer-to-peer database
configuration service on the primary server and secondary server must have a
corresponding instance of an API service. If a MediaSense cluster has more than
two servers, the additional servers do not have a configuration service or an
has two databases: the configuration database and the meta database. The
general term "database" is used to refer to both of them.
service controls the configuration database and the meta database. Each
MediaSense cluster can only have two instances of the database service. One
instance is in the primary server and the other instance is in the secondary
is a physical entity such as an end point or a personal computer that can be
use to make recordings. Each device is identified by a unique deviceRef or
reference is called a deviceRef in the API service and a device ref in the
administration service. It refers to the phone number, IP address, or the
URI/URL of each device. One or more participants can be associated with
multiple device references.
diagnostics is a network service. This service is present in all MediaSense
servers for debugging and troubleshooting purposes.
MediaSense deployment can have a maximum of three expansion servers. Each
expansion server has one instance of the call control service and one instance
of the media Service. Expansion servers have no instances of the API service or
the database service.
services enable you to configure and monitor all servers in a MediaSense
availability means that if one server fails, the other server can handle the
complete load for both servers in a MediaSense cluster. The data is load
balanced between both servers and data replication is available in both
- Live (active)
session is a call in progress and can be monitored and recorded at the same
time. When it is finished, it becomes a recorded session that can be played
back at any time.
- Media Service
service is a feature service. It terminates media streams for storage on a
local disk. One instance of the media service is present in every server in a
- Media Stream
stream refers to the packets going through an audio channel or video channel in
a live or recorded session. It refers only to a live session. It does not refer
to a recorded session. A recorded media stream is called a track.
- Meta Database
database stores call history and metadata information associated with each
recording. Each instance of the API service corresponds directly to one
instance of the meta database.
services enable you to configure and monitor overall system functions. After
you have installed MediaSense and rebooted your server, network services are
enabled by default on all servers in a cluster.
participant refers to people or end points involved in a session. Participants
use a device to conduct a session. Participants are identified by a unique
device reference, which is a phone number, IP address, or URL. During the same
session, each track is associated with only one participant, the participant
who is generating the media for that track. During different sessions, each
track can have one or more participants.
- Perfmon Agent
network service controls the performance monitoring infrastructure. It has no
separate user interface and operates seamlessly within MediaSense
configuration service in the first main server in any deployment is called the
primary database. The configuration service in the second main server in any
deployment is called the secondary database.
MediaSense cluster, configuration requests are sent to the primary database and
the secondary database. If the primary database is functional, data is written
to the primary database and then replicated to the secondary database. If the
primary database is not functional, data is not written to ensure data
integrity. If the primary database is not functional for a substantial period
of time, you can manually promote the secondary database to be the new primary
database so that data can be written to it. When the original primary database
begins functioning again, it becomes the new secondary database.
server is the first server in the cluster. After you install MediaSense and
reboot the primary server, all MediaSense feature services are enabled by
MediaSense clusters, the primary and secondary servers are publishers
session has been completed and can be played back at any time.
makes two types of recordings:
Forked media recordings are made from IP phones. These recordings have two
Direct call recordings are made to and from MediaSense to any phone. These
recordings have one audio channel and one optional video channel. (They are
often called blog recordings in this document.)
configuration database in the secondary server in a cluster is called the
cluster can have only one secondary server. After you access the administration
service and enable all feature services, you can assign that server as the
secondary server. It is paired with a primary server to ensure high
is a recorded monologue call, dialog call, or conference call. A session is
identified by a sessionID (or Session ID) and contains one or more tracks.
A MediaSense session has the same meaning as a recording
Unified Communications Manager. For more information
about its recording sessions, see the
Cisco Unified Communications Manager Features
and Services Guide.
- Session ID
unique identifier for a session.
- SM Agent
management agent (SM agent) monitors the overall storage in each server in a
cluster and generates threshold events based on disk usage. It is available in
all servers in the cluster.
network service controls service operations. It does not have a separate user
interface and operates seamlessly within the MediaSense administration service
and MediaSense serviceability administration.
System-defined tags are brief, arbitrary text strings that
associate individual sessions using the Web 2.0 APIs. MediaSense stores tags
with each session. MediaSense uses tags to mark certain actions which occurred
during the session (such as , pause and resume) or to mark when the media
inactivity state changes (as reported by the SIP signaling). While most tags
are associated only with a session, media inactivity state change tags are
associated with a session and with a specific track in the session.
identifies each media stream and quantifies it with additional data such as
participants, duration, start date, and track number. Each track is specific to
one audio stream or one video stream. Each track can be associated with
multiple device references. Each session contains one or more tracks.
- Track ID
unique identifier for a track.