Introduction

Customers using dedicated hardware have the ability to monitor Active Calls and Connected Calls via SNMP. Refer to the SIPPY-MIB.txt file to see specifically what can be monitored.

In order to enable SNMP, the following steps are required.

1. Enable SNMP agent for SSP MIB tree.

Make sure /usr/local/etc/snmp/snmpd.conf -> /home/ssp/etc/snmpd.conf file contains the following:

pass .1.3.6.1.4.1.36523  /home/ssp/scripts/snmp_statsd.py  

By default snmpd conf allows monitoring only from the local host. In order to enable remote monitoring of snmp statistics, you need to add the following line to your snmpd.conf file

rocommunity  <YOUR_SNMP_COMMUNITY_STRING> <IP_ADDRESS>

You must restart the SNMP daemon and rc.firewall script for changes to the snmpd.conf configuration file to take effect.

# /usr/local/etc/rc.d/snmpd restart
# screen
# /home/ssp/scripts/rc.firewall.sh

2. Download and place MIB file.

The MIB file should be available on any SSP installation on the following path:

  /usr/home/ssp/etc/SIPPY-MIB.txt


You must copy the SIPPY-MIB.txt file and place it in your SNMP client host to the MIB storage path, for example:

  cp /usr/home/ssp/etc/SIPPY-MIB.txt /usr/local/share/snmp/mibs/SIPPY-MIB.txt

If you are monitoring from a remote SNMP client, you must copy the SIPPY-MIB.txt file to the MIB storage path on the SNMP client host.

3. Access live SSP SNMP data.

At this point you should be able to query SSP with SNMP. The following example command:

  snmpwalk    -v2c  -m SIPPY-MIB -c <YOUR_SNMP_COMMUNITY_STRING> <YOUR_SSP_HOST> sippyStatus

Should provide you with all the data available:

SIPPY-MIB::SippyEnvIdEntry.1 = STRING: "1/Primary/"
SIPPY-MIB::SippyEnvIdEntry.12 = STRING: "12/Test .5/"
SIPPY-MIB::SippyEnvIdEntry.13 = STRING: "13/Second/"
SIPPY-MIB::SippyEnvActiveCallsEntry.1 = INTEGER: 0
SIPPY-MIB::SippyEnvActiveCallsEntry.12 = INTEGER: 0
SIPPY-MIB::SippyEnvActiveCallsEntry.13 = INTEGER: 0
SIPPY-MIB::SippyEnvConnectedCallsEntry.1 = INTEGER: 0
SIPPY-MIB::SippyEnvConnectedCallsEntry.12 = INTEGER: 0
SIPPY-MIB::SippyEnvConnectedCallsEntry.13 = INTEGER: 0

To query certain SNMP parameter, for example Connected calls in environment 12 you should issue command:

snmpget -v2c  -m SIPPY-MIB -c <YOUR_SNMP_COMMUNITY_STRING> <YOUR_SSP_HOST> SippyEnvConnectedCallsEntry.12
SIPPY-MIB::SippyEnvConnectedCallsEntry.12 = INTEGER: 0

Additional details per each available method:

SippyAccountConnectedCallsEntry.<i_environment>.<i_account>
SippyAccountActiveCallsEntry.<i_environment>.<i_account>

SippyEnvIdEntry.<i_environment> - name of the environment
SippyEnvActiveCallsEntry.<i_environment>
SippyEnvConnectedCallsEntry.<i_environment>
SippyEnvPtimeEntry.<i_environment> - average ptime value from the environment
SippyEnvAAPtimeEntry.<i_environment> - average aa_ptime value from the environment
SippyEnvAuthorizedCallsAvgEntry.<i_environment> - average number of authorized calls in the environment
SippyEnvRoutedCallsAvgEntry.<i_environment> - average number of routed calls in the environment
SippyEnvConnectedCallsAvgEntry.<i_environment> - average number of connected calls in the environment

SippyVendorActiveCallsEntry.<i_environment>.<i_vendor>
SippyVendorConnectedCallsEntry.<i_environment>.<i_vendor>

SippyConnectionActiveCallsEntry.<i_environment>.<i_connection>
SippyConnectionConnectedCallsEntry.<i_environment>.<i_connection>

SippyCustomerActiveCallsEntry.<i_environment>.<i_customer>
SippyCustomerConnectedCallsEntry.<i_environment>.<i_customer>

SippyEnvNAuthorizedCallsEntry.<i_environment> - the number of authorized calls
SippyEnvNRoutedCallsEntry.<i_environment> - the number of routes which has been tried for calls,
SippyEnvNConnectedCallsEntry.<i_environment>, - the number of connected calls
SippyEnvACDEntry.<i_environment>, - the Average Call Duration (ACD) in minutes
SippyEnvReceivedASREntry.<i_environment> - the Ingress traffic after successful authentication
SippyEnvAuthorizedASREntry.<i_environment> - the ASR on all ingress traffic
SippyEnvOriginatedASREntry.<i_environment> - the ASR on all egress traffic
SippyRtpProxyOneWayEntry - the percentage calls that had SDP for both legs, but RTP only seen on one leg.
SippyRtpProxyIncompleteEntry - the percentage of calls that got media description for only one leg.
SippyRtpProxyNoRtpEntry - the percentage calls that had SDP for both legs, but RTP not seen on either leg. And
SippyRtpProxyDiscardEntry - the percentage of number of RTP/RTPC packets discarded. This is typically caused from packets from an unknown source or packets received on a good leg of incomplete sessions.



For most monitoring systems you must know the OID of the parameter to be monitored without possibility to access its MIB name. To see all of the available OID issue the following command:

snmpwalk  -On  -v2c  -m SIPPY-MIB -c <YOUR_SNMP_COMMUNITY_STRING> <YOUR_SSP_HOST> .1.3.6.1.4.1.36523

.1.3.6.1.4.1.36523.1.1.1.1.1.1 = STRING: "1/Primary/"
.1.3.6.1.4.1.36523.1.1.1.1.1.12 = STRING: "12/Test .5/"
.1.3.6.1.4.1.36523.1.1.1.1.1.13 = STRING: "13/Second/"
.1.3.6.1.4.1.36523.1.1.1.2.1.1 = INTEGER: 0
.1.3.6.1.4.1.36523.1.1.1.2.1.12 = INTEGER: 0
.1.3.6.1.4.1.36523.1.1.1.2.1.13 = INTEGER: 0
.1.3.6.1.4.1.36523.1.1.1.3.1.1 = INTEGER: 0
.1.3.6.1.4.1.36523.1.1.1.3.1.12 = INTEGER: 0
.1.3.6.1.4.1.36523.1.1.1.3.1.13 = INTEGER: 0
Example for Connection calls using MIB for env 1 connection 64

Active calls (routing +connected):
snmpget -O n -v2c -m /home/ssp/etc/SIPPY-MIB.txt -c public 127.0.0.1
SippyConnectionActiveCallsEntry.1.64 =
INTEGER: 52

New features;
  • The seven enrironment attributes have been added;
    The SippyEnvNAuthorizedCallsEntry attribute represents the number of authorized calls,
    The SippyEnvNRoutedCallsEntry attribute represent the number of routes which has been tried for calls,
    The SippyEnvNConnectedCallsEntry shows the number of connected calls,
    The SippyEnvACDEntry attribute shows Average Call Duration (ACD) in minutes,
    The SippyEnvReceivedASREntry attribute shows the Ingress traffic after successful authentication,
    The SippyEnvAuthorizedASREntry attribute shows the ASR on all ingress traffic,
    And the SippyEnvOriginatedASREntry attribute shows the ASR on all egress traffic.

  • Four main attributes of every RTP Proxy instance are also available.
    The SippyRtpProxyOneWayEntry attribute shows the percentage calls that had SDP for both legs, but RTP only seen on one leg.
    The SippyRtpProxyIncompleteEntry attribute shows the percentage of calls that got media description for only one leg.
    The SippyRtpProxyNoRtpEntry attribute shows the percentage calls that had SDP for both legs, but RTP not seen on either leg. And
    The SippyRtpProxyDiscardEntry attribute shows the percentage of number of RTP/RTPC packets discarded. This is typically caused from packets from an unknown source or packets received on a good leg of incomplete sessions.

    Those RTP Proxy attributes can be fetched by snmpwalk command like this:
    $ snmpwalk -v 2c -m SIPPY-MIB -c <YOUR_SNMP_COMMUNITY_STRING> <IP_ADDRESS> sippyStatus.SippyRtpProxyParameter

    In case of interest for individual attribute, that can be fetch by the snmpget command:
    $ snmpget -v 2c -m SIPPY-MIB -c <YOUR_SNMP_COMMUNITY_STRING> <IP_ADDRESS> sippyStatus.SippyRtpProxyParameter

    The latest version of SNMP monitoring tree has been shown in the following picture

All the green attributes can be discover by snmpwalk. The other attributes can be fetched with the 'snmpget' command.