The Simple Network Management Protocol (SNMP) enables the parameters and functions of servers and applications to be monitored remotely.
Call Recording uses SNMP v2 messaging with an installed agent module, that supports SNMP GET (SNMP SET is not supported). This module is installed during Genesys Quality Management Suite installation in a default configuration, that can be modified via the /etc/snmp/snmpd.conf configuration file.
The Call Recording Message Information Block (MIB) defines the variables that are available to SNMP clients. The following data is available from the Call Recording SNMP Agent:
- Decoder: number of registered decoders, decoder communicator status, pending requests in decoder queue
- Recorder: number of registered recorders, recorder communicator status, SPAN port check (port-up/port-down)
Structure of the Call Recording SNMP MIB
Call Recording defines the SNMP Management Information Base (MIB) as follows:
| Node Object ID (OID) Pattern | Explanation |
|---|---|
.1.3.6.1.4.1.16321 | This root node is used by GQM software |
.1.3.6.1.4.1.16321.1 | The next node is reserved for GQM software |
.1.3.6.1.4.1.16321.1.10 | This OID identifies Call Recording modules |
.1.3.6.1.4.1.16321.1.10.1 | This covers variables with versions of modules |
.1.3.6.1.4.1.16321.1.10.1.0 | The value of the Master (0) module version |
.1.3.6.1.4.1.16321.1.10.1.1 | The value of the Core reporter (1) module |
The following table contains a summary of the main Call Recording nodes (all Object IDs are prefixed by .1.3.6.1.4.1.16321.):
| Node OID | Module Name |
|---|---|
1.10.1 | Core |
1.10.2 | Redlines |
1.10.4 | Observable Naming |
1.10.5 | Prerecording Server |
1.10.6 | Decoder Master Communicator |
1.10.7 | Config Manager Communicator |
1.10.8 | SRS Communicator |
1.10.9 | Remote NS |
1.10.10 | User Interface |
1.10.11 | Remote JTAPI |
1.10.13 | Mixer |
1.10.15 | Genesys Adapter |
To display specific Object IDs and values within the Call Recording system MIB, use the Linux command snmpwalk, as described in the next section. For a complete list of defined OIDs, please contact Genesys Tech Support.
Configuring the SNMP Agent for Oracle
Navigate to Settings > Configuration > CallREC Core > Database and scroll down to the oracle pool settings.

Read the parameters from the pool configuration for oracle, in the example the pool name is oracle where the SQL map is Callstorage (Oracle).
Using an SSH Client such as PuTTy log in to the Call Recording server. Log in as admin. Enter su - to log in as the root user. Enter the password, the default is zoomcallrec.
Using vim or a similar editor modify the SNMP configuration file for example:
vim /opt/callrec/SNMP/src/deployment.cfg

Press the i key to go into --INSERT--mode . Use the cursor keys to position the cursor over the values.
- Change dbtype value to oracle.
- Change the parameters database, hostname, user (login name), password and port to values found on the configuration page.
- Note that the editor is in --INSERT -- mode.

Press Esc to go into command mode. The -- INSERT -- message at the bottom of the screen disappears indicating the exit of editing mode. Enter the command :wto save the configuration. A message displays to confirm that the config is written, for example:

To exit from vim type :q!.
It should not be necessary to restart Call Recording.
Testing SNMP Functionality
The following test procedures assume the default configuration.
To test the functionality of SNMP from the command line, when logged in with root level permissions, use the Linux shell command snmpwalk with the following syntax:
snmpwalk -v 1 -c public localhost .1.3.6.1.4.1.16321.1
If SNMP is functioning properly, the following confirmation appears:
SNMPv2-SMI::enterprises.16321.1.10.0.1.0 = STRING: "ZOOM Call Recording - Master module, Copyright (C) 2002-2011 ZOOM International, All Rights Reserved" SNMPv2-SMI::enterprises.16321.1.10.0.2.0 = INTEGER: 1 SNMPv2-SMI::enterprises.16321.1.10.0.3.0 = STRING: "WARNING" SNMPv2-SMI::enterprises.16321.1.10.0.6.1.0 = INTEGER: 10 <-- More Output Lines --> End of MIB
Before testing a new installation and configuration of SNMP, wait 5-7 minutes to enable SNMP to gather information.
Each object in the system listed in the Management Information Base (MIB) has its own error and information codes, to track the status of the system. Consult the SNMP documentation for further information.