1-- ***************************************************************** 2-- CISCO-WAN-PERSISTENT-XGCP-EVENTS.my 3-- 4-- October 2003, George Ogagan 5-- 6-- Copyright (c) 2001-2003 by Cisco Systems, Inc. 7-- All rights reserved. 8-- 9-- ***************************************************************** 10-- 11 12CISCO-WAN-PERSISTENT-XGCP-EVENTS-MIB DEFINITIONS ::= BEGIN 13 14IMPORTS 15 MODULE-IDENTITY, 16 OBJECT-TYPE, 17 Integer32 18 FROM SNMPv2-SMI 19 RowStatus 20 FROM SNMPv2-TC 21 SnmpAdminString 22 FROM SNMP-FRAMEWORK-MIB 23 MODULE-COMPLIANCE, 24 OBJECT-GROUP 25 FROM SNMPv2-CONF 26 ciscoWan FROM CISCOWAN-SMI; 27 28 29ciscoWanPersistentXgcpEventsMIB MODULE-IDENTITY 30 LAST-UPDATED "200310200000Z" 31 ORGANIZATION "Cisco Systems, Inc." 32 CONTACT-INFO 33 " Cisco Systems 34 Customer Service 35 36 Postal: 170 W Tasman Drive 37 San Jose, CA 95134 38 USA 39 40 Tel: +1 800 553-NETS 41 42 E-mail: cs-voice@cisco.com" 43 44 DESCRIPTION 45 "The MIB module for managing CA(Call Agent) events. 46 " 47 REVISION "200310200000Z" 48 DESCRIPTION "Update descriptions in the MIB. 49 " 50 51 ::= { ciscoWan 18 } 52 53ciscoWanPersistentXgcpEventsMIBObjects 54 OBJECT IDENTIFIER ::= { ciscoWanPersistentXgcpEventsMIB 1 } 55 56persistentXgcpEvents 57 OBJECT IDENTIFIER ::= { ciscoWanPersistentXgcpEventsMIBObjects 1 } 58 59 60-- 61-- persistentXgcpEventsTable 62-- 63-- The MIB variables in this group have been defined 64-- to enable or disable sending xGCP(Media Gateway 65-- Control Protocol) events to the CA asynchronously, 66-- for example sending NTFY(Notify) when VISM receives 67-- off hook without waiting for the CA to request for it. 68-- 69 70persistentXgcpEventsTable OBJECT-TYPE 71 SYNTAX SEQUENCE OF PersistentXgcpEventsEntry 72 MAX-ACCESS not-accessible 73 STATUS current 74 DESCRIPTION 75 "The persistentXgcpEventsTable contains 76 configuration information about xGCP events 77 which involve a persistent notification request. 78 " 79 ::= { persistentXgcpEvents 1 } 80 81persistentXgcpEventsEntry OBJECT-TYPE 82 SYNTAX PersistentXgcpEventsEntry 83 MAX-ACCESS not-accessible 84 STATUS current 85 DESCRIPTION 86 "An entry in the persistentXgcpEventsTable. Each 87 entry consists of persistentXgcpEventNum - Index 88 to the persistentXgcpEventsTable. 89 90 persistentXgcpEventName - Name of the xGCP 91 event that needs persistent notification 92 to the call agent for example 't/hd'. 93 94 persistentXgcpEventRowStatus -This indicates 95 whether an xGCP event is added in this entry 96 or not. 97 98 This table is not created implicitly. The user 99 can add xGCP event or delete an xGCP event. 100 " 101 INDEX { persistentXgcpEventNum } 102 ::= { persistentXgcpEventsTable 1 } 103 104PersistentXgcpEventsEntry ::= 105 SEQUENCE 106 { 107 persistentXgcpEventNum Integer32, 108 persistentXgcpEventName SnmpAdminString, 109 persistentXgcpEventRowStatus RowStatus 110 } 111 112persistentXgcpEventNum OBJECT-TYPE 113 SYNTAX Integer32 (1..16) 114 MAX-ACCESS not-accessible 115 STATUS current 116 DESCRIPTION 117 "This object is a index to persistentXgcpEventsTable. 118 " 119 ::= { persistentXgcpEventsEntry 1 } 120 121persistentXgcpEventName OBJECT-TYPE 122 SYNTAX SnmpAdminString (SIZE(0..64)) 123 MAX-ACCESS read-write 124 STATUS current 125 DESCRIPTION 126 "This object holds the name of the event 127 for example 't/hd' or 't/hu'. 128 " 129 ::= { persistentXgcpEventsEntry 2 } 130 131persistentXgcpEventRowStatus OBJECT-TYPE 132 SYNTAX RowStatus 133 MAX-ACCESS read-write 134 STATUS current 135 DESCRIPTION 136 "This object allows to add or delete an entry. 137 Modifying an entry is not allowed. 138 139 An entry may be created using the 'createAndGo' option. 140 When the row is successfully created, the RowStatus would 141 be set to 'active' by the agent. An entry may be deleted 142 by setting the RowStatus to 'destroy'. Other options 143 such as `CreateAndWait', 'notInService', 'notReady' will 144 not be used. 145 146 For creating an entry the persistentXgcpEventNum and 147 persistentXgcpEventName must be provided. 148 149 This object tells call control whether or not a particular 150 xGCP event is added or not, based on this the call control 151 module will decide whether or not to notify (NTFY) call 152 agent when a particular xGCP event is received, 153 without waiting for CA to request for that event. 154 " 155 ::= { persistentXgcpEventsEntry 3 } 156 157-- 158-- ********************************************************************** 159-- Conformance 160-- ********************************************************************** 161 162-- 163-- conformance information 164-- 165 166persistentXgcpEventsMIBConformance 167 OBJECT IDENTIFIER ::= { ciscoWanPersistentXgcpEventsMIB 2 } 168 169persistentXgcpEventsMIBCompliances 170 OBJECT IDENTIFIER ::= { persistentXgcpEventsMIBConformance 1 } 171 172persistentXgcpEventsMIBGroups 173 OBJECT IDENTIFIER ::= { persistentXgcpEventsMIBConformance 2 } 174 175-- 176-- Conformance and compliance statements statements 177-- 178 179persistentXgcpEventsMIBCompliance MODULE-COMPLIANCE 180 STATUS current 181 DESCRIPTION 182 " The complaince statement for persistent Xgcp events 183 which implement persistentXgcpEvents MIB." 184 MODULE -- this module 185 MANDATORY-GROUPS { persistentXgcpEventsMIBGroup 186 } 187 ::= { persistentXgcpEventsMIBCompliances 1 } 188 189-- 190-- units of conformance 191-- 192-- MIB Groups 193-- 194 195persistentXgcpEventsMIBGroup OBJECT-GROUP 196 OBJECTS { 197 persistentXgcpEventName, 198 persistentXgcpEventRowStatus 199 } 200 STATUS current 201 DESCRIPTION 202 "This group contains objects related to 203 configuration of persistent xGCP events. 204 " 205 ::= { persistentXgcpEventsMIBGroups 1 } 206 207 208END 209 210