cisco-call-application-mib.mib object
Introduction
Most network devices and programs ship with so-called MIB files to describe the parameters and meanings (i.e.: friendly names) which are available for monitoring via SNMP.
ActiveXperts Network Monitor 2025 can import vendor-specific MIB files, so it can be used to monitor specific OID's (Object Identifiers).
This way, you can monitor your devices, computers, etc. by selecting your relevant OID's by name.
ActiveXperts Network Monitor 2025 can import MIB file cisco-call-application-mib and use it to monitor vendor specific OID's.
cisco-call-application-mib file content
Object view of cisco-call-application-mib:
  
    
      | Scalar Object | 
    
  
  
    
      | ccapApplicationEntry | 
      .1.3.6.1.4.1.9.9.146.1.1.1.1 | 
    
    
      | 
        Information about a call application.
       | 
    
  
  
    
      | Tabular Object | 
    
  
  
    
      | ccapAppName | 
      .1.3.6.1.4.1.9.9.146.1.1.1.1.1 | 
    
    
      | 
        The name of this call application.
       | 
    
    
      | ccapAppLocation | 
      .1.3.6.1.4.1.9.9.146.1.1.1.1.2 | 
    
    
      | 
        Identifies the location from where this application is
        loaded.
        For built-in applications, the value will always
        be an empty string.
        If the location is not specified or not known, the value is
        an empty string.
        Note that a particular agent may support only certain types
        of URLs (e.g., only tftp://...). Thus, the valid values of
        this object are implementation dependent. An agent may
        respond with an error (e.g., 'wrongValue') to a management
        SET operation which attempts to modify the value of this
        object to one which is not supported by the managed device.
        The value of this object may be changed at any time. However,
        note that setting this value for an active row will cause the
        old application to be deleted, and the new application (i.e.
        the program at the newly-specified URL) to be loaded.
        
       | 
    
    
      | ccapAppLoadState | 
      .1.3.6.1.4.1.9.9.146.1.1.1.1.3 | 
    
    
      | 
        The state of this application.
        For built-in applications, the value read is always
        'builtIn'.
        When this row is made active, the agent attempts to
        load the application from the URL specified by
        ccapAppLocation. While loading is in progress, the value of
        this object reads 'loading'. If the application is
        successfully loaded, the value changes to 'loaded',
        otherwise the value changes to 'loadFailed'.
        
       | 
    
    
      | ccapAppLoadFailReason | 
      .1.3.6.1.4.1.9.9.146.1.1.1.1.4 | 
    
    
      | 
        The reason the last attempted load failed. The possible
        values are:
        none - there was no failure
        other - failure reason is other than those listed
        below
        notFound - application was not found
        timedOut - timed out while loading
        noPermission - was denied permission
        badSignature - the application did not have the
        proper signature. An agent may use an
        authentication scheme to protect itself. This
        error indicates that the authentication check
        failed, hence the application was not loaded.
        noSpace - lack of memory space.
        The value is updated after a load attempt.
        
       | 
    
    
      | ccapAppDescr | 
      .1.3.6.1.4.1.9.9.146.1.1.1.1.5 | 
    
    
      | 
        A description of this application.
        
       | 
    
    
      | ccapAppCallType | 
      .1.3.6.1.4.1.9.9.146.1.1.1.1.6 | 
    
    
      | 
        Indicates the types of call that this application can handle.
        
       | 
    
    
      | ccapAppRowStatus | 
      .1.3.6.1.4.1.9.9.146.1.1.1.1.7 | 
    
    
      | 
        The status of this conceptual row.
        Note that rows corresponding to built-in applications can
        not be modified. Thus, this object is read-only for such
        rows.
        This object can not be set to 'active' until a value has
        been assigned to the corresponding instance of
        ccapAppLocation. When a row becomes active, the agent
        attempts to load the application from the location
        specified by ccapAppLocation. The result of the loading
        operation can be monitored by the objects ccapAppLoadState
        and ccapAppLoadError.
        Deleting a row will cause the agent to unload the
        corresponding application.
        
       | 
    
  
  
    
      | Table | 
    
  
  
    
      | ccapApplicationTable | 
      .1.3.6.1.4.1.9.9.146.1.1.1 | 
    
    
      | 
        Information about call applications on this managed device.
        There is an entry in this table for each call application.
        
       | 
    
  
  
    
      | Object Identifier | 
    
  
  
    
      | ciscoCallApplicationMIB | 
      .1.3.6.1.4.1.9.9.146 | 
    
    
      | 
        This MIB allows management of call applications on a
        network device. A 'call application' is a software module
        that processes calls, such as data, voice, video, or fax
        calls.
        
       | 
    
    
      | ciscoCallApplicationMIBObjects | 
      .1.3.6.1.4.1.9.9.146.1 | 
    
    
      | ccapConf | 
      .1.3.6.1.4.1.9.9.146.1.1 | 
    
    
      | ciscoCallApplicationMIBConformance | 
      .1.3.6.1.4.1.9.9.146.3 | 
    
    
      | ciscoCallApplicationMIBCompliances | 
      .1.3.6.1.4.1.9.9.146.3.1 | 
    
    
      | ciscoCallApplicationMIBGroups | 
      .1.3.6.1.4.1.9.9.146.3.2 | 
    
  
  
    
      | Group | 
    
  
  
    
      | ccapGeneralCfgGroup | 
      .1.3.6.1.4.1.9.9.146.3.2.1 | 
    
    
      | 
        A collection of objects for general configuration of call
        applications.
       |