CISCO-VOICE-CONNECTIVITY-MIB

        This MIB module provides connectivity related
information for devices (e.g., 'connectivity between 
voice gateway, phones, gatekeepers and call processing 
agent').  The MIB can be used by network management 
applications to collect the information regarding voice 
connectivity among the devices in the network.  The MIB 
can also be used to retrieve the status of voice 
connectivity between the devices.    
        
*** ABBREVIATIONS, ACRONYMS, AND SYMBOLS ***
        
SCCP -  Skinny Client Control Protocol
        
SGCP -  Simple Gateway Control Protocol
        
MGCP -  Media Gateway Control Protocol
        
H323 -  H.323 protocol
        
SIP  -  Session Initiation Protocol
        
        
*** DEFINITIONS ***
        
CALL AGENT
A call processing agent component of a device in IP 
telephony and VoIP network.
        
PORT
A port on the device that is associated with call 
processing agent.
        
REGISTRATION
In an IP telephony network, there are typically keep-
alive messages or expected registration refresh timers
that are used to formulate the registration status of 
devices and/or users.  
Possible values of the registration status are as 
follows:
registered:   The port has successfully registered with
              the call agent
        
unregistered: The port is no longer registered with the
              call agent
        
rejected:     Registration request from the port was 
              rejected by the call agent.
    
Source file
CISCO-VOICE-CONNECTIVITY-MIB
Last revised
Identity
ciscoVoiceConnectivityMIB
Base OID
1.3.6.1.4.1.9.9.393
Imported Objects
CISCO-SMI ciscoMgmt
IANAifType-MIB IANAifType
INET-ADDRESS-MIB InetAddress InetAddressType
SNMP-FRAMEWORK-MIB SnmpAdminString
SNMPv2-CONF MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) Unsigned32
SNMPv2-TC AutonomousType DateAndTime MacAddress RowPointer TruthValue
Net-SNMP examples using the cisco MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'CISCO-VOICE-CONNECTIVITY-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-VOICE-CONNECTIVITY-MIB::ciscoVoiceConnectivityMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-VOICE-CONNECTIVITY-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-VOICE-CONNECTIVITY-MIB::ciscoVoiceConnectivityMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (37)
.1.3.6.1.4.1.9.9.393
.1.3.6.1.4.1.9.9.393.0
.1.3.6.1.4.1.9.9.393.1
.1.3.6.1.4.1.9.9.393.1.1
.1.3.6.1.4.1.9.9.393.1.1.1
.1.3.6.1.4.1.9.9.393.1.1.1.1
Unsigned32
.1.3.6.1.4.1.9.9.393.1.1.1.1.1
OctetString
.1.3.6.1.4.1.9.9.393.1.1.1.1.2
.1.3.6.1.4.1.9.9.393.1.1.1.1.3
.1.3.6.1.4.1.9.9.393.1.1.1.1.4
.1.3.6.1.4.1.9.9.393.1.1.1.1.5
.1.3.6.1.4.1.9.9.393.1.2
.1.3.6.1.4.1.9.9.393.1.2.1
.1.3.6.1.4.1.9.9.393.1.2.1.1
Unsigned32
.1.3.6.1.4.1.9.9.393.1.2.1.1.1
.1.3.6.1.4.1.9.9.393.1.2.1.1.10
.1.3.6.1.4.1.9.9.393.1.2.1.1.2
.1.3.6.1.4.1.9.9.393.1.2.1.1.3
.1.3.6.1.4.1.9.9.393.1.2.1.1.4
.1.3.6.1.4.1.9.9.393.1.2.1.1.5
.1.3.6.1.4.1.9.9.393.1.2.1.1.6
.1.3.6.1.4.1.9.9.393.1.2.1.1.7
Enumeration
.1.3.6.1.4.1.9.9.393.1.2.1.1.8
Enumeration
.1.3.6.1.4.1.9.9.393.1.2.1.1.9
.1.3.6.1.4.1.9.9.393.1.3
.1.3.6.1.4.1.9.9.393.1.3.1
.1.3.6.1.4.1.9.9.393.1.3.1.1
.1.3.6.1.4.1.9.9.393.1.3.1.1.1
Enumeration
.1.3.6.1.4.1.9.9.393.1.3.1.1.2
Enumeration
.1.3.6.1.4.1.9.9.393.1.3.1.1.3
.1.3.6.1.4.1.9.9.393.1.3.1.1.4
.1.3.6.1.4.1.9.9.393.1.3.1.1.5
.1.3.6.1.4.1.9.9.393.1.4
.1.3.6.1.4.1.9.9.393.1.4.1
.1.3.6.1.4.1.9.9.393.2
.1.3.6.1.4.1.9.9.393.2.1
.1.3.6.1.4.1.9.9.393.2.2
Dependencies (7) 7 direct Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Conformance Groups (5)
A collection of objects which provide info like IP address and
HostName about all call agents to which the ports are
configured to register. Also it has call agent type.
.1.3.6.1.4.1.9.9.393.2.2.1
A collection of objects which provide info about all port/
interface of the device that are configured to register to
call agents. Not all objects are applicable to all type of
ports or interface. For example some port does not have
MACAddress in that case cvcPortMACAddress need not have to be
populated. Similarly for some device cvcPortAssociation is not
applicable for example phone, in that case cvcPortAssociation
object will not be populated but DeviceName, MCAAddress and
IPAddress will be populated.
.1.3.6.1.4.1.9.9.393.2.2.2
A collection of objects which provides registration status
information for the port to the call agents defined in
cvcPortTable and cvcCallAgentTable. This also provides
information about the reason why registration is failed or
rejected. It provides last time when status changes and last
registered time. In some cases, registration status is not
applicable for example H.323 gateway association with call
agent, in that case most of these object will not be populated
except cvcCallAgentPriority which can be used to find
association of port with call agent.
.1.3.6.1.4.1.9.9.393.2.2.3
A collection of objects which provide info about all the
notifications generated by the device that implement this MIB.

Implementation of this group is optional.
.1.3.6.1.4.1.9.9.393.2.2.4
A collection of notifications that are generated by
CISCO-VOICE-CONNECTIVITY-MIB. This is important information
when some management application decide not to poll but only
rely on notification.

Implementation of this group is optional.
.1.3.6.1.4.1.9.9.393.2.2.5
Compliance Statements (1)

OID .1.3.6.1.4.1.9.9.393.2.1.1
The compliance statement for entities which implement the
CISCO-VOICE-CONNECTIVITY-MIB.
Required groups
mandatory cvcCallAgentGroup
mandatory cvcPortGroup
mandatory cvcCallAgentConnectionGroup
optional cvcNotifGroup This optional group provide object to configure
notification enable or disable.
optional cvcNotificationsGroup This optional group provide notification objects.
Notifications / Traps (1)
NameOIDDescription
.1.3.6.1.4.1.9.9.393.0.1
A cvcPortRegistrationStatusChange notification is generated
when the value of cvcRegistrationStatus changes. It can be
utilized by an NMS to get current registration status change
information. cvcPortDeviceName and cvcCallAgentInetAddress can
be used by NMS to get information about the port and
call agent from cvcPortTable and cvcCallAgentTable
respectively.

An NMS should periodically check the value of
cvcLastStatusChangeTime to detect any missed
cvcPortRegistrationStatusChange notification-events due to
network problem or any other problem.