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.

Imported Objects

ciscoMgmtCISCO-SMI
IANAifTypeIANAifType-MIB
InetAddress, InetAddressTypeINET-ADDRESS-MIB
SnmpAdminStringSNMP-FRAMEWORK-MIB
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUPSNMPv2-CONF
OBJECT-TYPE, Unsigned32, NOTIFICATION-TYPE, MODULE-IDENTITYSNMPv2-SMI
MacAddress, AutonomousType, RowPointer, TruthValue, DateAndTimeSNMPv2-TC

Objects

ciscoVoiceConnectivityMIB .1.3.6.1.4.1.9.9.393
ciscoVoiceConnectivityMIBNotifs .1.3.6.1.4.1.9.9.393.0
ciscoVoiceConnectivityMIBObjects .1.3.6.1.4.1.9.9.393.1
cvcCallAgent .1.3.6.1.4.1.9.9.393.1.1
cvcCallAgentTable .1.3.6.1.4.1.9.9.393.1.1.1
cvcCallAgentEntry .1.3.6.1.4.1.9.9.393.1.1.1.1
cvcCallAgentIndex .1.3.6.1.4.1.9.9.393.1.1.1.1.1
cvcCallAgentName .1.3.6.1.4.1.9.9.393.1.1.1.1.2
cvcCallAgentInetAddressType
.1.3.6.1.4.1.9.9.393.1.1.1.1.3
cvcCallAgentInetAddress
.1.3.6.1.4.1.9.9.393.1.1.1.1.4
cvcCallAgentType
.1.3.6.1.4.1.9.9.393.1.1.1.1.5
cvcPort .1.3.6.1.4.1.9.9.393.1.2
cvcPortTable .1.3.6.1.4.1.9.9.393.1.2.1
cvcPortEntry .1.3.6.1.4.1.9.9.393.1.2.1.1
cvcPortIndex .1.3.6.1.4.1.9.9.393.1.2.1.1.1
cvcVirtualInterfaceDN
.1.3.6.1.4.1.9.9.393.1.2.1.1.10
cvcPortAssociation
.1.3.6.1.4.1.9.9.393.1.2.1.1.2
cvcPortDeviceName
.1.3.6.1.4.1.9.9.393.1.2.1.1.3
cvcPortInetAddressType
.1.3.6.1.4.1.9.9.393.1.2.1.1.4
cvcPortInetAddress
.1.3.6.1.4.1.9.9.393.1.2.1.1.5
cvcPortMACAddress
.1.3.6.1.4.1.9.9.393.1.2.1.1.6
cvcPortType
.1.3.6.1.4.1.9.9.393.1.2.1.1.7
cvcProductCategory .1.3.6.1.4.1.9.9.393.1.2.1.1.8
cvcProtocol .1.3.6.1.4.1.9.9.393.1.2.1.1.9
cvcCallAgentConnection .1.3.6.1.4.1.9.9.393.1.3
cvcCallAgentConnectionTable .1.3.6.1.4.1.9.9.393.1.3.1
cvcCallAgentConnectionEntry .1.3.6.1.4.1.9.9.393.1.3.1.1
cvcCallAgentPriority .1.3.6.1.4.1.9.9.393.1.3.1.1.1
cvcRegistrationStatus .1.3.6.1.4.1.9.9.393.1.3.1.1.2
cvcStatusReason .1.3.6.1.4.1.9.9.393.1.3.1.1.3
cvcLastStatusChangeTime
.1.3.6.1.4.1.9.9.393.1.3.1.1.4
cvcLastRegisteredTime
.1.3.6.1.4.1.9.9.393.1.3.1.1.5
cvcNotif .1.3.6.1.4.1.9.9.393.1.4
cvcNotifEnable
.1.3.6.1.4.1.9.9.393.1.4.1
ciscoVoiceConnectivityMIBConform .1.3.6.1.4.1.9.9.393.2
cvcMIBCompliances .1.3.6.1.4.1.9.9.393.2.1
cvcMIBGroups .1.3.6.1.4.1.9.9.393.2.2

Notifications/Traps

NameOIDDescription
cvcPortRegistrationStatusChange







.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.