1-- **************************************************************** 2-- ciscoVismDsx0MIB 3-- The MIB for DS0 interface configuration and 4-- Alarm Configuration for VISM(Voice Interface Module) 5-- in MGX products. 6-- 7-- March 2004, Rashmi Purandare 8-- 9-- Copyright (c) 2003,2004 by Cisco Systems, Inc. 10-- All rights reserved. 11-- **************************************************************** 12 13CISCO-VISM-DSX0-MIB DEFINITIONS ::= BEGIN 14IMPORTS 15 MODULE-IDENTITY, 16 OBJECT-TYPE, 17 Integer32 18 FROM SNMPv2-SMI 19 MODULE-COMPLIANCE, 20 OBJECT-GROUP FROM SNMPv2-CONF 21 DisplayString, 22 TruthValue FROM SNMPv2-TC 23 dsx0Vism, 24 cardSpecific FROM BASIS-MIB 25 ciscoWan FROM CISCOWAN-SMI; 26 27ciscoVismDsx0MIB MODULE-IDENTITY 28 LAST-UPDATED "200403110000Z" 29 ORGANIZATION "Cisco Systems, Inc." 30 CONTACT-INFO 31 " Cisco Systems 32 Customer Service 33 34 Postal: 170 W Tasman Drive 35 San Jose, CA 95134 36 USA 37 38 Tel: +1 800 553-NETS 39 40 E-mail: cs-wanatm@cisco.com" 41 DESCRIPTION 42 "This MIB module contains ds0 configuration, 43 Status and DS0 related information on a 44 DS1 interface supported in VISM module. 45 46 VISM is a Voice Interworking Service Module supported 47 in MGX8250 and MGX8850 and other MGX products. 48 49 Terminologies used: 50 line : Same as the Physical Interface. 51 DS1 line signifies DS1 interface." 52 53 REVISION "200403110000Z" 54 DESCRIPTION 55 "Added 56 - ds0Companding 57 - ds0RxCasTransTblName 58 - ds0TxCasTransTblName 59 - ds0TxRxCasConfig 60 - ciscoVismDsx0Compliance2 61 - ciscoVismDsx0ConfGroup2 62 Deprecated 63 - ciscoVismDsx0Compliance 64 - ciscoVismDsx0ConfGroup 65 " 66 REVISION "200308030000Z" 67 DESCRIPTION 68 "Added following tables: 69 dsx0VismCnfTable 70 dsx0VismChanMapTable 71 72 These tables were defined in CISCO-WAN-AXIPOP-MIB 73 (an unrelated mib) earlier. The relevant contents 74 from CISCO-WAN-AXIPOP-MIB are moved and converted 75 to SMIv2 and defined here." 76 77 REVISION "200306170000Z" 78 DESCRIPTION 79 "Initial version of the MIB. 80 81 The content of this MIB was originally available 82 in SMIv1 version. The MIB has been converted to 83 SMIv2 version and descriptions of some of the objects 84 have been modified." 85 ::= { ciscoWan 81 } 86 87vismDs0CardStats OBJECT IDENTIFIER ::= { cardSpecific 24 } 88 89-- ----------------------------------------------------------------- 90-- 91-- dsx0Vism group: 92-- 93-- This group contains the tables/objects necessary to configure 94-- the DS0s on DS1/E1 interfaces of VISM. 95-- ----------------------------------------------------------------- 96 97dsx0VismCnfTable OBJECT-TYPE 98 SYNTAX SEQUENCE OF Dsx0VismCnfEntry 99 MAX-ACCESS not-accessible 100 STATUS current 101 DESCRIPTION 102 "The entries in this table are created and deleted 103 implicitly at the time of adding and deleting the line. 104 For every DS0 on a line, one row will be created." 105 ::= { dsx0Vism 1 } 106 107dsx0VismCnfEntry OBJECT-TYPE 108 SYNTAX Dsx0VismCnfEntry 109 MAX-ACCESS not-accessible 110 STATUS current 111 DESCRIPTION 112 "This ds0 table contains both cas related 113 and non cas related parameters. 114 115 The non cas related parameters are applicable 116 accross all line signaling types, while the 117 following cas related parameters 118 are applicable only if the signaling type 119 of the line(DS1/E1 Interface) to which this ds0 belongs 120 is cas. 121 122 ds0IdleCode 123 ds0SeizedCode 124 ds0ReceivedCode 125 ds0CasVariantName 126 ds0CasCadenceOnTime 127 ds0CasCadenceOffTime 128 ds0InsertLocalCas 129 ds0LocalCasPattern 130 ds0CasParameterSource 131 ds0CasOnHookMinMakeTime 132 ds0CasOffHookMinMakeTime 133 ds0CasWinkMinMakeTime 134 ds0CasWinkMaxMakeTime 135 ds0CasWinkBreakTime 136 ds0CasGlareTime 137 ds0CasGaurdTime 138 ds0CasDelayImmedStart 139 ds0CasMinDelayDialTime 140 ds0CasMinStartDialTime 141 ds0CasFlashMinMakeTime 142 ds0CasFlashMaxMakeTime 143 ds0CasDirectionality 144 ds0CasGlarePolicy 145 ds0CasIncomingMgcpPackage 146 ds0CasOutgoingMgcpPackage 147 148 When the line signaling type changes from cas to non-cas 149 and vice versa, then the user will be forced to delete 150 endpoint/ccs channels associated with any ds0 on that line 151 When an endpoint is deleted the ds0CasVariantName associated 152 with that endpoint will also be implicitly deleted. 153 Other than that none of the above cas related parameters are 154 modified across line signaling type changes." 155 INDEX { ds0IfIndex } 156 ::= { dsx0VismCnfTable 1 } 157 158Dsx0VismCnfEntry ::= 159 SEQUENCE { 160 ds0IfIndex Integer32, 161 ds0RobbedBitSignalling TruthValue, 162 ds0IdleCode Integer32, 163 ds0SeizedCode Integer32, 164 ds0ReceivedCode Integer32, 165 ds0TransmitCodesEnable TruthValue, 166 ds0BundleMapped Integer32, 167 ds0IfType INTEGER, 168 ds0CasVariantName DisplayString, 169 ds0CasCadenceOnTime Integer32, 170 ds0CasCadenceOffTime Integer32, 171 ds0InsertLocalCas TruthValue, 172 ds0LocalCasPattern Integer32, 173 ds0LoopbackCommand INTEGER, 174 ds0CasParameterSource INTEGER, 175 ds0CasOnHookMinMakeTime Integer32, 176 ds0CasOffHookMinMakeTime Integer32, 177 ds0CasWinkMinMakeTime Integer32, 178 ds0CasWinkMaxMakeTime Integer32, 179 ds0CasWinkBreakTime Integer32, 180 ds0CasGlareTime Integer32, 181 ds0CasGaurdTime Integer32, 182 ds0CasDelayImmedStart Integer32, 183 ds0SignalingType INTEGER, 184 ds0CasMinDelayDialTime Integer32, 185 ds0CasMinStartDialTime Integer32, 186 ds0CasFlashMinMakeTime Integer32, 187 ds0CasFlashMaxMakeTime Integer32, 188 ds0CasDirectionality INTEGER, 189 ds0CasGlarePolicy INTEGER, 190 ds0CasIncomingMgcpPackage DisplayString, 191 ds0CasOutgoingMgcpPackage DisplayString, 192 ds0InputGain Integer32, 193 ds0OutputAttenuation Integer32, 194 ds0MusicThreshold Integer32, 195 ds0SidPacket TruthValue, 196 ds0ExecDiag TruthValue, 197 ds0Companding INTEGER, 198 ds0RxCasTransTblName DisplayString, 199 ds0TxCasTransTblName DisplayString, 200 ds0TxRxCasConfig INTEGER 201} 202 203ds0IfIndex OBJECT-TYPE 204 SYNTAX Integer32 (1..248) 205 MAX-ACCESS read-only 206 STATUS current 207 DESCRIPTION 208 "This attribute defines the index for this table. 209 This is derived from the following formula: 210 index = 31 * (Ds1# - 1) + ds0# 211 212 where : Ds1# - The T1/E1 line number in the range 1 - 8. 213 ds0# - The ds0 channel number ranging from 214 1 to 24 for T1 215 and 1 to 31 for E1." 216 ::= {dsx0VismCnfEntry 1} 217 218ds0RobbedBitSignalling OBJECT-TYPE 219 SYNTAX TruthValue 220 MAX-ACCESS read-write 221 STATUS current 222 DESCRIPTION 223 "This object indicates if Robbed Bit Signalling is 224 turned on or off for a given ds0. This only 225 applies to DS0s on a DS1 link. For E1 links the 226 value is always off (false). For T1 links, the default 227 value is true if the line is configured for CAS signaling, 228 the default value is false if the line is configured for 229 CCS signaling or no signaling." 230 ::= { dsx0VismCnfEntry 2 } 231 232ds0IdleCode OBJECT-TYPE 233 SYNTAX Integer32(0..15) 234 MAX-ACCESS read-write 235 STATUS current 236 DESCRIPTION 237 "This object contains the code transmitted in the 238 ABCD bits when the ds0 is not connected and 239 ds0TransmitCodesEnable is enabled. The object is 240 a bitmap and the various bit positions are: 241 Bit 0 (value 1) D bit 242 Bit 1 (value 2) C bit 243 Bit 2 (value 4) B bit 244 Bit 3 (value 8) A bit 245 This object is useful for ds0 conditioning to be 246 done if an alarm condition is detected from the 247 network side. DS0 conditioning is implemented in 248 the trunking application only. 249 250 This object is not applicable in the CAS backhaul 251 application. 252 253 From vism 2.0.3 release onwards this object can 254 be configured in any mode, but will be applicable 255 only in trunking application and will be ignored 256 in other applications." 257 DEFVAL { 0 } 258 ::= { dsx0VismCnfEntry 3 } 259 260ds0SeizedCode OBJECT-TYPE 261 SYNTAX Integer32(0..15) 262 MAX-ACCESS read-write 263 STATUS current 264 DESCRIPTION 265 "This object contains the code transmitted in the 266 ABCD bits when the ds0 is connected and 267 ds0TransmitCodesEnable is enabled. The object is 268 a bitmap and the various bit positions are: 269 Bit 0 (value 1) D bit 270 Bit 1 (value 2) C bit 271 Bit 2 (value 4) B bit 272 Bit 3 (value 8) A bit 273 This object is useful for ds0 conditioning to be 274 done if an alarm condition is detected from the 275 network side. DS0 conditioning is implemented in 276 the trunking application only. 277 278 This object is not applicable in the CAS backhaul 279 application. 280 281 From vism 2.0.3 release onwards this object can 282 be configured in any mode, but will be applicable 283 only in trunking application and will be ignored 284 in other applications." 285 DEFVAL { 15 } 286 ::= { dsx0VismCnfEntry 4 } 287 288ds0ReceivedCode OBJECT-TYPE 289 SYNTAX Integer32(0..15) 290 MAX-ACCESS read-only 291 STATUS current 292 DESCRIPTION 293 "This object contains the code being received in 294 the ABCD bits. The object is a bitmap and the 295 various bit positions are: 296 Bit 0 (value 1) D bit 297 Bit 1 (value 2) C bit 298 Bit 2 (value 4) B bit 299 Bit 3 (value 8) A bit" 300 ::= { dsx0VismCnfEntry 5 } 301 302ds0TransmitCodesEnable OBJECT-TYPE 303 SYNTAX TruthValue 304 MAX-ACCESS read-only 305 STATUS deprecated 306 DESCRIPTION 307 "This object determines if the idle and seized 308 codes are transmitted. If the value of this object 309 is true then the codes are transmitted. 310 This object is not applicable in the CAS backhaul 311 application." 312 DEFVAL { true } 313 ::= { dsx0VismCnfEntry 6 } 314 315ds0BundleMapped OBJECT-TYPE 316 SYNTAX Integer32(-1..2147483647) 317 MAX-ACCESS read-only 318 STATUS current 319 DESCRIPTION 320 "This object indicates endpoint number as specified 321 by mgEndpointNumber of endpoint table. 322 If it is not associated with any endpoint, then it 323 is set to -1. 324 It should be noted that the endpoint is associated 325 with bearer DS0s only. For signaling channel or DS0 326 as in the case of CCS channel, there is no endpoint 327 number associated with it and the value is set to -1." 328 ::= { dsx0VismCnfEntry 7 } 329 330ds0IfType OBJECT-TYPE 331 SYNTAX INTEGER { 332 bearer (81), 333 ccs-signaling (63), 334 unknown (1) 335 } 336 MAX-ACCESS read-only 337 STATUS current 338 DESCRIPTION 339 "This object indicates the interface type associated 340 with the ds0. 341 bearer(81) : ds0 ifType is considered as bearer if 342 the DS0 is used for carrying voice traffic. 343 ccs-signaling(63): ds0 ifType is considered as ccs-signaling, 344 if the DS0 is configured as the D-channel." 345 ::= { dsx0VismCnfEntry 8 } 346 347ds0CasVariantName OBJECT-TYPE 348 SYNTAX DisplayString (SIZE(0..255)) 349 MAX-ACCESS read-write 350 STATUS current 351 DESCRIPTION 352 "This object indicates the index to the CAS variant 353 table. This parameter can be configured after configuring 354 this ds0 as an endpoint. This object cannot be modified 355 while connections exist on this endpoint. The CAS variant 356 table is used for configuring the system parameters associated 357 with various types of CAS signaling methods supported." 358 ::= { dsx0VismCnfEntry 9 } 359 360ds0CasCadenceOnTime OBJECT-TYPE 361 SYNTAX Integer32(2..9999) 362 MAX-ACCESS read-write 363 STATUS current 364 DESCRIPTION 365 "This attribute describes the duration during which the digit 366 tone is generated. 367 This object is applicable only for CAS backhaul applications. 368 For trunking application it is not applicable. 369 The value is expresssed in units of milliseconds. 370 From vism2.0.3 release onwards this object can 371 configured in any application, but will be applicable 372 only in non-trunking applications and will be ignored 373 in other applications." 374 DEFVAL {75} 375 ::= {dsx0VismCnfEntry 10 } 376 377ds0CasCadenceOffTime OBJECT-TYPE 378 SYNTAX Integer32(0..9999) 379 MAX-ACCESS read-write 380 STATUS current 381 DESCRIPTION 382 "This attribute corresponds to the silence between the 383 digit tones. 384 This object is applicable only for CAS backhaul applications. 385 For trunking application it is not applicable. 386 The value is expresssed in units of milliseconds. 387 388 From vism2.0.3 release onwards this object can 389 configured in any application, but will be applicable 390 only in non-trunking applications and will be ignored 391 in other applications." 392 DEFVAL {75} 393 ::= {dsx0VismCnfEntry 11} 394 395ds0InsertLocalCas OBJECT-TYPE 396 SYNTAX TruthValue 397 MAX-ACCESS read-write 398 STATUS current 399 DESCRIPTION 400 "This object tells the framer whether to force the cas bits 401 to a value defined by ds0LocalCasPattern or not. 402 403 If this is enabled the framer will force the cas (ABCD) bits 404 to a value defined in ds0LocalCasPattern by ignorning the 405 cas bits sent by DSP. Else the framer will transmit the cas 406 bits sent by DSP. 407 408 Setting of this object is not allowed when the signaling type 409 of this line is cas. 410 411 Also setting of this object is not allowed when the 412 ds0LoopbackCommand is set to RemoteLoop, because in this 413 situation we are suppose to loopback whatever comes from 414 the TDM side and not force the cas bits to something else. 415 416 This object can be set only if the line type is T1." 417 DEFVAL {false} 418 ::= {dsx0VismCnfEntry 12} 419 420ds0LocalCasPattern OBJECT-TYPE 421 SYNTAX Integer32(0..15) 422 MAX-ACCESS read-write 423 STATUS current 424 DESCRIPTION 425 "This object contains the pattern that the cas (ABCD) bits will have 426 when ds0InsertLocalCas is enabled." 427 DEFVAL{0} 428 ::={dsx0VismCnfEntry 13} 429 430ds0LoopbackCommand OBJECT-TYPE 431 SYNTAX INTEGER { 432 noLoop (1), 433 remoteLoop (2), 434 localLoop (3) 435 } 436 MAX-ACCESS read-write 437 STATUS current 438 DESCRIPTION 439 "This object represents the loopback type at the ds0 level.The 440 ds0 configuration overrides the line level configuration. 441 442 NoLoop 443 There is no loopback on this ds0. 444 445 LocalLoop 446 The data received from the ATM side is loopedback 447 to the ATM side. 448 449 RemoteLoop 450 The data from the TDM side is looped back to the 451 TDM side. 452 453 Setting of this object to RemoteLoop will not be allowed when 454 insert local cas for this ds0 (ds0InsertLocalCas object) is 455 enabled as we are suppose to force the cas bits to the pattern 456 configured in ds0LocalCasPattern, and not do loopback on the 457 TDM side." 458 DEFVAL{noLoop} 459 ::= {dsx0VismCnfEntry 14} 460 461ds0CasParameterSource OBJECT-TYPE 462 SYNTAX INTEGER 463 { 464 casAppl (1), 465 mibValue (2) 466 } 467 MAX-ACCESS read-write 468 STATUS current 469 DESCRIPTION 470 "This object indicates VISM whether to read the cas related 471 timer parameters from the casAppl file downloaded for that 472 endpoint or to read from this mib. 473 474 This gives the flexibility of configuring 475 different cas related timer values for different 476 endpoints associated with the same cas variant. 477 478 This object cannot be configured if the signaling 479 type for the line to which this ds0 belongs is non cas. 480 For a cas line this object CAN only be configured 481 only after associating this ds0 with an endpoint." 482 DEFVAL{casAppl} 483 ::= { dsx0VismCnfEntry 15 } 484 485ds0CasOnHookMinMakeTime OBJECT-TYPE 486 SYNTAX Integer32 (0..65535) 487 UNITS "milliseconds" 488 MAX-ACCESS read-write 489 STATUS current 490 DESCRIPTION 491 "This indicates the the minimum time in msecs 492 for which the on hook pattern should be present in order for it 493 to be recognised else the signal will be considered to be a 494 spurious signal and will be ignored. 495 496 This object cannot be configured if the signaling 497 type for the line to which this ds0 belongs is non cas. 498 For a cas line this object CAN only be configured 499 only after associating this ds0 with an endpoint. 500 501 This object will be applicable if ds0CasParameterSource 502 has a value of mibValue (2). 503 The allowed range for this object is 10..1000" 504 DEFVAL {300} 505 ::= { dsx0VismCnfEntry 16 } 506 507ds0CasOffHookMinMakeTime OBJECT-TYPE 508 SYNTAX Integer32 (0..65535) 509 UNITS "milliseconds" 510 MAX-ACCESS read-write 511 STATUS current 512 DESCRIPTION 513 "This indicates the minimum time in msecs for 514 which the off hook pattern should be present in order for it to be 515 recognised else the signal will be considered to be a spurious signal 516 and will be ignored. 517 518 This object cannot be configured if the signaling 519 type for the line to which this ds0 belongs is non cas. 520 521 For a cas line this object CAN only be configured 522 only after associating this ds0 with an endpoint 523 This object will be applicable if ds0CasParameterSource 524 has a value of mibValue (2). 525 The allowed range for this object is 10..1000" 526 DEFVAL {20} 527 ::= { dsx0VismCnfEntry 17 } 528 529ds0CasWinkMinMakeTime OBJECT-TYPE 530 SYNTAX Integer32 (0..65535) 531 UNITS "milliseconds" 532 MAX-ACCESS read-write 533 STATUS current 534 DESCRIPTION 535 "The wink consists of off-hook A-B bit pattern, followed 536 by on-hook A-B bit pattern in timed sequence. 537 This object indicates the minimum duration for which 538 the off-hook part of wink signal should persist. 539 540 This object cannot be configured if the signaling 541 type for the line to which this ds0 belongs is non cas. 542 For a cas line this object CAN only be configured 543 only after associating this ds0 with an endpoint 544 545 This object will be applicable if ds0CasParameterSource 546 has a value of mibValue (2). 547 The allowed range for this object is 10..1000." 548 DEFVAL {100} 549 ::= { dsx0VismCnfEntry 18 } 550 551ds0CasWinkMaxMakeTime OBJECT-TYPE 552 SYNTAX Integer32 (0..65535) 553 UNITS "millisesconds" 554 MAX-ACCESS read-write 555 STATUS current 556 DESCRIPTION 557 "The wink consists of off-hook A-B bit pattern, followed 558 by on-hook A-B bit pattern in timed sequence. 559 This object indicates the maximum duration for which the 560 off-hook part of the wink signal should persist, if it 561 exceeds this time limit the signal will be considered to 562 be spurious and will be ignored. 563 564 This object cannot be configured if the signaling 565 type for the line to which this ds0 belongs is non cas. 566 For a cas line this object CAN only be configured 567 only after associating this ds0 with an endpoint 568 569 This object will be applicable if ds0CasParameterSource 570 has a value of mibValue (2). 571 572 The allowed range for this object is 10..3000. 573 574 The value for this object should be greater than or equal to 575 ds0CasWinkMinMakeTime" 576 DEFVAL {350} 577 ::= { dsx0VismCnfEntry 19 } 578 579ds0CasWinkBreakTime OBJECT-TYPE 580 SYNTAX Integer32 (0..65535) 581 UNITS "milliseconds" 582 MAX-ACCESS read-write 583 STATUS current 584 DESCRIPTION 585 "The wink consists of off-hook A-B bit pattern, 586 followed by on-hook A-B bit pattern in timed sequence. 587 This object indicates the minimum duration for which 588 the on-hook part of wink signal should persist. 589 590 This object cannot be configured if the signaling 591 type for the line to which this ds0 belongs is non cas. 592 For a cas line this object CAN only be configured 593 only after associating this ds0 with an endpoint 594 595 This object will be applicable if ds0CasParameterSource 596 has a value of mibValue (2). 597 The allowed range for this object is 10..1000." 598 DEFVAL {70} 599 ::= { dsx0VismCnfEntry 20 } 600 601ds0CasGlareTime OBJECT-TYPE 602 SYNTAX Integer32 (0..65535) 603 UNITS "milliseconds" 604 MAX-ACCESS read-write 605 STATUS current 606 DESCRIPTION 607 "When the terminating gateway receives off Hook event 608 from the Call Agent it starts the timer specified in 609 this object to see if the terminating side is also 610 trying to originate a call. If this is true, we have 611 a 'glare' condition. The way glare is resolved is 612 thru this user programmable timer, we will not honor 613 any off hook events from the originating PBX during 614 this time. 615 616 This object cannot be configured if the signaling 617 type for the line to which this ds0 belongs is non CAS. 618 For a CAS line this object can only be configured 619 only after associating this ds0 with an endpoint 620 621 This object will be applicable if ds0CasParameterSource 622 has a value of mibValue (2). 623 624 The allowed range for this object is 10..10000." 625 DEFVAL {100} 626 ::= { dsx0VismCnfEntry 21 } 627 628ds0CasGaurdTime OBJECT-TYPE 629 SYNTAX Integer32 (0..65535) 630 UNITS "milliseconds" 631 MAX-ACCESS read-write 632 STATUS current 633 DESCRIPTION 634 "The gaurd time is the duration between the end of one call 635 and the start of next call. This object specifies what should 636 be such a duration. All state changes from the PBX are ignored 637 for this duration. After receiving DLCX, this timer will be 638 started for a period as configured in this object, and will 639 not honor any off-hook events before the expiration of this timer. 640 641 This object cannot be configured if the signaling 642 type for the line to which this ds0 belongs is non cas. 643 644 For a cas line this object CAN only be configured 645 only after associating this ds0 with an endpoint 646 This object will be applicable if ds0CasParameterSource 647 has a value of mibValue (2). 648 649 The allowed range for this object is 10..1000." 650 DEFVAL {800} 651 ::= { dsx0VismCnfEntry 22 } 652 653ds0CasDelayImmedStart OBJECT-TYPE 654 SYNTAX Integer32 (0..65535) 655 UNITS "milliseconds" 656 MAX-ACCESS read-write 657 STATUS current 658 DESCRIPTION 659 "This timer indicates the time that VISM should wait before 660 outpulsing digits to the PBX after sending an off hook event. 661 This applies only to immediate start protocol. 662 663 This object cannot be configured if the signaling 664 type for the line to which this ds0 belongs is non cas. 665 For a cas line this object CAN only be configured 666 only after associating this ds0 with an endpoint. 667 668 This object will be applicable if ds0CasParameterSource 669 has a value of mibValue (2). 670 671 The allowed range for this object is 10..1000." 672 DEFVAL {500} 673 ::= { dsx0VismCnfEntry 23 } 674 675ds0SignalingType OBJECT-TYPE 676 SYNTAX INTEGER { 677 cas (1), 678 ccs (2), 679 none (3) 680 } 681 MAX-ACCESS read-only 682 STATUS current 683 DESCRIPTION 684 "This attribute indicates the type of signaling on the line 685 to which this ds0 belongs. 686 687 CAS - Channel Associated Signaling 688 CCS - Common Channel Signaling 689 none - no signaling used. 690 691 This object will be implicitly set to line signaling 692 type every time it changes." 693 DEFVAL { none } 694 ::= {dsx0VismCnfEntry 24} 695 696ds0CasMinDelayDialTime OBJECT-TYPE 697 SYNTAX Integer32 698 UNITS "milliseconds" 699 MAX-ACCESS read-write 700 STATUS current 701 DESCRIPTION 702 "This is an object for an E & M signaling protocol like 703 wink-start for this ds0. The difference is that the 704 address-control signal is different from wink. 705 The originating VISM, on receiving a seize (AB=11) from the 706 PBX, responds by sending the delay-dial (AB=11) signal back 707 to the PBX. When the originating VISM is ready to collect 708 the digits, it sends a start-dial (AB=00) signal. 709 This operation is symmetric. So the terminating VISM, on 710 seizing a trunk, should receive AB=11 711 (as an ack that the trunk is operational). Subsequently, 712 when it receives the start signal (AB=00) from the connected PBX, 713 it should outpulse the digits. The rest of the operation 714 is similiar to wink-start. 715 716 The allowed range for this object is 100..1000 with 717 units in milliseconds. 718 719 In delay-dial operation, the outgoing interface (this interface), 720 after sending a seize signal (AB = 11), waits for the delay-dial 721 signal (AB = 11). The delay-dial signal, apart from 722 acknowledging the seize signal, tells this interface that 723 the connected equipment is not ready for the digits yet. 724 This object specifies the time in milliseconds, after which 725 incoming AB=11 will be interpreted by this interface as the 726 delay-dial signal." 727 REFERENCE 728 "1. Generic Requirements, GR-506-CORE, Issue 1, June 1996, 729 Revision 1, November 1996, 730 2. LSSGR: Signaling for Analog Interfaces 731 Section 11.2.3 is about 'Delay-Dial Operation' (in general) 732 In particular, section 11.2.3.1 ([R11-21] is about these 733 timing requirements." 734 DEFVAL {100} 735 ::= {dsx0VismCnfEntry 25} 736 737ds0CasMinStartDialTime OBJECT-TYPE 738 SYNTAX Integer32 739 UNITS "milliseconds" 740 MAX-ACCESS read-write 741 STATUS current 742 DESCRIPTION 743 "This is an object for an E & M signaling protocol like 744 wink-start for this ds0. The difference is that the 745 address-control signal is different from wink. The originating 746 VISM, on receiving a seize (AB=11) from the PBX, 747 responds by sending the delay-dial (AB=11) signal back 748 to the PBX. When the originating VISM is ready to collect 749 the digits, it sends a start-dial (AB=00) signal. 750 This operation is symmetric. So the terminating VISM, on 751 seizing a trunk, should receive AB=11 752 (as an ack that the trunk is operational). Subsequently, 753 when it receives the start signal (AB=00) from 754 the connected PBX, it should outpulse the digits. 755 The rest of the operation is similiar to wink-start. 756 757 The allowed range for this object is 70..1000. 758 759 In delay-dial operation, the outgoing interface (this interface), 760 after receiving a delay-dial signal (AB=11) from the connected 761 equipment, waits for the start-dial signal (AB = 00) before 762 sending the digits to the connected equipment. 763 The start-dial signal tells this interface that the 764 connected equipment is ready for the digits. 765 This object specifies the time in milliseconds, after which 766 incoming AB=00 will be interpreted by this interface as the 767 start dial signal." 768 REFERENCE 769 "1. Generic Requirements, GR-506-CORE, Issue 1, June 1996, 770 Revision 1, November 1996, 771 2. LSSGR: Signaling for Analog Interfaces 772 Section 11.2.3 is about 'Delay-Dial Operation' (in general) 773 In particular, section 11.2.3.1 ([R11-22] and [R11-23]) is 774 about these timing requirements." 775 DEFVAL {70} 776 ::= {dsx0VismCnfEntry 26} 777 778ds0CasFlashMinMakeTime OBJECT-TYPE 779 SYNTAX Integer32 780 UNITS "milliseconds" 781 MAX-ACCESS read-write 782 STATUS current 783 DESCRIPTION 784 "Flash is a CAS signal generated by users to request 785 special services. The interpretation of the flash 786 depends on the protocol in use. The signal itself 787 is an on-hook followed by an off-hook. This object 788 specifies the minimum duration for the signal to be 789 recognized as a flash by VISM. This duration, 790 expressed in milliseconds, is defined as the elapsed 791 time between the off-to-on-hook transition followed by 792 the on-to-off-hook transition. 793 If the on-hook duration is shorter than the value of 794 this object, the signal will be ignored. 795 796 This object cannot be configured if the signaling type 797 for the line to which this ds0 belongs is non-CAS. 798 For a CAS line, this object can only be configured 799 after associating this ds0 with an endpoint. 800 If no endpoint was added for this Ds0, any configuration 801 attempt will be rejected. 802 803 This object will be applicable if ds0CasParameterSource 804 has a value of mibvalue (2). 805 806 The allowed range for this object is 50..1550." 807 DEFVAL {300} 808 ::= {dsx0VismCnfEntry 27} 809 810ds0CasFlashMaxMakeTime OBJECT-TYPE 811 SYNTAX Integer32 812 UNITS "milliseconds" 813 MAX-ACCESS read-write 814 STATUS current 815 DESCRIPTION 816 "Flash is a CAS signal generated by users to request 817 special services. The interpretation of the flash 818 depends on the protocol in use. The signal itself is 819 an on-hook followed by an off-hook. This object specifies 820 the maximum duration for the signal to be recognized as a 821 flash by VISM. This duration, expressed in milliseconds, 822 is defined as the elapsed time between the off-to-on-hook 823 transition followed by the on-to-off-hook transition. 824 If the on-hook duration is longer than the value of this object, 825 the signal will be ignored. 826 827 This object cannot be configured if the signaling type 828 for the line to which this ds0 belongs is non-CAS. 829 830 For a CAS line, this object can only be configured after 831 associating this ds0 with an endpoint. This means that 832 if no endpoint was added for this Ds0, any configuration 833 set attempt will be rejected, but any get will be allowed. 834 835 This object will be applicable if ds0CasParameterSource 836 has a value of 'mibvalue'(2). 837 838 The allowed range for this object is 50..1550. 839 The value of this object should be greater than 840 or equal to ds0CasFlashMinMakeTime." 841 DEFVAL {1400} 842 ::= {dsx0VismCnfEntry 28} 843 844ds0CasDirectionality OBJECT-TYPE 845 SYNTAX INTEGER { 846 bidirectional (1), 847 incoming (2), 848 outgoing (3) 849 } 850 MAX-ACCESS read-write 851 STATUS current 852 DESCRIPTION 853 "This object specifies the direction in which CAS calls 854 will be accepted on this endpoint. If this object is set to 855 856 bidirectional(1): VISM can send and receive calls on this 857 endpoint 858 incoming(2) : calls from the connected PBX will be 859 accepted by VISM on this endpoint. 860 outgoing(3) : VISM will send calls towards the connected PBX and 861 not accept calls from the PBX. 862 863 The main difference between bidirectional and one-way trunks 864 is the occurrence of glare. On bidirectional trunks, since both 865 VISM and the connected PBX can seize the endpoint at 866 approximately the same time, glare (dual seizure) is likely to occur. 867 The protocol assigned to a bidirectional endpoint should be 868 capable of detecting and resolving glare. 869 Wink-start and delay-dial are examples of protocols capable of 870 glare handling and immediate-start, ground-start and loop-start, 871 of those that cannot. 872 873 This object cannot be configured if the signaling type for 874 the DS1 line to which this ds0 belongs is non-CAS. 875 876 For a CAS line, this object can only be configured after 877 associating this ds0 with an endpoint. This means that if 878 no endpoint was added for this Ds0, any configuration set 879 attempt will be rejected, but any get will be allowed." 880 DEFVAL {bidirectional} 881 ::= {dsx0VismCnfEntry 29} 882 883ds0CasGlarePolicy OBJECT-TYPE 884 SYNTAX INTEGER { 885 controlling (1), 886 releasing (2) 887 } 888 MAX-ACCESS read-write 889 STATUS current 890 DESCRIPTION 891 "This object specifies how a bidirectional endpoint should 892 resolve glare. This object will be used only if 893 dsx0VismDirectionality of the endpoint is 'bidirectional'. 894 When glare is detected, if this object is set to controlling, 895 VISM will wait for the connected PBX to assert on-hook. 896 When the connected PBX goes on-hook, VISM proceeds to dial 897 the numbers out waits for answer. 898 899 If this object is set to releasing(2), VISM indicates the 900 glare situation to the Call Agent 901 (as specified by the control protocol), prepares to collect 902 digits from the PBX and asserts on hook. The incoming call 903 should go through. 904 If the CAS protocol assigned to the endpoint cannot detect 905 glare or if it cannot resolve glare according to the policy 906 provisioned via this object, this object will not be used. 907 908 This object cannot be configured if the signaling type 909 for the DS1 line to which this ds0 belongs is non-CAS. 910 911 For a CAS line, this object can only be configured after 912 associating this ds0 with an endpoint. This means that if no 913 endpoint was added for this Ds0, any configuration set 914 attempt will be rejected, but any get will be allowed." 915 DEFVAL {controlling} 916 ::= {dsx0VismCnfEntry 30} 917 918ds0CasIncomingMgcpPackage OBJECT-TYPE 919 SYNTAX DisplayString (SIZE(0..255)) 920 MAX-ACCESS read-write 921 STATUS current 922 DESCRIPTION 923 "This object, in conjunction with the card level 924 persistentXgcpEventsTable, controls how persistent 925 CAS events (like seize, disconnect, etc) related 926 to an incoming call observed on this DS0 are notified to 927 the Media Gateway Controller (MGC). 928 929 At the card level, the persistentXgcpEventsTable allows 930 MGCP package-event combinations to be configured as persistent. 931 For example, when L/hd is added to the persistentXgcpEventsTable, 932 the hook-down event in line package will be notified to the MGC 933 every time it is observed without the MGC requesting for that event. 934 935 Since the same CAS event can map to different MGCP events under 936 different packages (eg. the CAS event 'seize' can be 'sup' in 937 'MS' package and 'hd' in 'BL' package) and different lines could 938 be running different packages at a given time, there needs to be 939 a per-DS0 object indicating what package should be used while 940 notifying CAS events observed on that DS0. This object, 941 ds0CasIncomingMgcpPackage specifies the package that will be 942 used while notifying CAS events observed on an incoming call 943 on this DS0. 944 945 This object can be set to a package name from 946 xgcpCapabilityPackageTable whose 947 xgcpCapabilityPackageEnable is true or the string 'basic' 948 indicating that one of the basic packages in that table 949 (G, T, L, H, R, D or M) to which the observed event belongs 950 can be used. 951 952 This object is used only if the protocol is MGCP. 953 If the notification is in response to an RQNT, VISM 954 uses the package (and event name) that the MGC used 955 to request the event regardless what this object is set to. 956 957 In the absence of an RQNT, the observed CAS event is 958 encoded according to the package that this object specifies. 959 A 'seize' observed on the CAS signaling channel on this DS0, 960 for example is encoded as 'ms/sup' if this object is 961 set to 'ms', 'bl/hd' if this object is set to 'bl' or 962 as 'L/hd' if this object is set to 'basic'. 963 If this package/event is present in persistentXgcpEventsTable, 964 a notification is generated, otherwise this event is discarded. 965 966 An attempt to set this object to a package name whose 967 xgcpCapabilityPackageEnable is false in 968 xgcpCapabilityPackageTable will fail. 969 970 This object is used only if the ds0CasDirectionality is set 971 to 'bidirectional' or 'incoming'." 972 ::= {dsx0VismCnfEntry 31} 973 974ds0CasOutgoingMgcpPackage OBJECT-TYPE 975 SYNTAX DisplayString (SIZE(0..255)) 976 MAX-ACCESS read-write 977 STATUS current 978 DESCRIPTION 979 "This object, in conjunction with the card level 980 persistentXgcpEventsTable, controls how persistent 981 CAS events (like answer, disconnect, etc) related 982 to an outgoing call observed on this DS0 are notified to the 983 Media Gateway Controller (MGC). 984 985 At the card level, the persistentXgcpEventsTable allows 986 MGCP package-event combinations to be configured as persistent. 987 For example, when L/hd is added to the persistentXgcpEventsTable, 988 the hook-down event in line package will be notified to the MGC 989 every time it is observed without the MGC requesting for that event. 990 991 Since the same CAS event can map to different MGCP events 992 under different packages (eg. the CAS event 'answer' can be 993 'ans' in 'MS' package and 'hd' in 'BL' package) and different 994 lines could be running different packages at a given time, 995 there needs to be a per-DS0 object indicating what package 996 should be used while notifying CAS events observed on that DS0. 997 This object, ds0CasOutgoingMgcpPackage specifies the package 998 that will be used while notifying CAS events observed on an 999 outgoing call on this DS0. 1000 1001 This object can be set to a package name from 1002 xgcpCapabilityPackageTable whose xgcpCapabilityPackageEnable 1003 is true or the string 'basic' indicating that one 1004 of the basic packages in that table (G, T, L, H, R, D or M) 1005 to which the observed event belongs can be used. 1006 1007 This object is used only if the protocol is MGCP. 1008 If the notification is in response to an RQNT, 1009 VISM uses the package (and event name) that the MGC used 1010 to request the event regardless what this object is set to. 1011 1012 In the absence of an RQNT, the observed CAS event is encoded 1013 according to the package that this object specifies. 1014 An answer observed on the CAS signaling channel on this DS0, 1015 for example is encoded as 'ms/ans' if this object is set to 'ms', 1016 'bl/hd' if this object is set to 'bl' or as 'L/hd' if this object is 1017 set to 'basic'. If this package/event is present in 1018 persistentXgcpEventsTable, a notification is generated, 1019 otherwise this event is discarded. 1020 1021 An attempt to set this object to a package name whose 1022 xgcpCapabilityPackageEnable is false in 1023 xgcpCapabilityPackageTable will fail. 1024 1025 This object is used only if the ds0CasDirectionality is set 1026 to 'bidirectional' or 'outgoing'." 1027 ::= {dsx0VismCnfEntry 32} 1028 1029ds0InputGain OBJECT-TYPE 1030 SYNTAX Integer32 (-6..14) 1031 UNITS "dB - decibel" 1032 MAX-ACCESS read-write 1033 STATUS current 1034 DESCRIPTION 1035 "This object indicates the amount of gain inserted at the 1036 receiver side of a ds0 channel, in dB (decibel) units. 1037 The default value of this object is 0 dB. 1038 1039 The input gain settings only define a gain/loss relative 1040 to the 0 dB setting. The absolute loss at the 0 dB setting 1041 could be implementation dependent based on the desired network 1042 loss plan. 1043 1044 This object can be set when there are active call going on, 1045 and in this case the new gain will take effective immediately. 1046 It can also be set at both unbound endpoints and bound but 1047 non-active endpoints." 1048 DEFVAL { 0 } 1049 ::= {dsx0VismCnfEntry 33} 1050 1051ds0OutputAttenuation OBJECT-TYPE 1052 SYNTAX Integer32 (0..14) 1053 UNITS "dB - decibel" 1054 MAX-ACCESS read-write 1055 STATUS current 1056 DESCRIPTION 1057 "This object contains the amount of attenuation inserted 1058 at the transmit side of a ds0 channel, in dB (decibel) units. 1059 1060 The output attenuation settings only define a loss relative to 1061 0 dB setting. The absolute loss at the 0 dB setting could be 1062 implementation dependent based on the desired network loss plan. 1063 1064 This object can be set when there are active call going on, 1065 and in this case the new gain will take effective immediately. 1066 It can also be set at both unbound endpoints and bound but 1067 non-active endpoints. 1068 " 1069 DEFVAL { 0 } 1070 ::= {dsx0VismCnfEntry 34} 1071 1072ds0MusicThreshold OBJECT-TYPE 1073 SYNTAX Integer32 (-70..-30) 1074 MAX-ACCESS read-write 1075 STATUS current 1076 DESCRIPTION 1077 "The indicates Music On Hold Threshold in dBm. Based on this 1078 value, VISM DSP will interprete the incoming signal from TDM side 1079 as either silence or voice, and consequently turn on or off VAD. 1080 1081 This object can be set when there is active call going on at the 1082 ds0 channel, and at both unbound endpoints and bound non-active 1083 endpoints. 1084 " 1085 DEFVAL { -38 } 1086 ::= {dsx0VismCnfEntry 35} 1087 1088ds0SidPacket OBJECT-TYPE 1089 SYNTAX TruthValue 1090 MAX-ACCESS read-write 1091 STATUS current 1092 DESCRIPTION 1093 "This object specifies whether the Silence Indication 1094 Detection (SID) packet should be generated when silence 1095 suppression is in active mode. The SID packet indicates 1096 the noise level during silence, which is used as a reference 1097 to generate comfort noise on the other side of the gateway. 1098 This object is used for VoIP only." 1099 DEFVAL {true} 1100 ::= {dsx0VismCnfEntry 36} 1101 1102ds0ExecDiag OBJECT-TYPE 1103 SYNTAX TruthValue 1104 MAX-ACCESS read-write 1105 STATUS current 1106 DESCRIPTION 1107 "This object indicates the status of DSP channel level 1108 RAS on the VISM. When it is enable VISM will configure 1109 the DSP through HOST-DSP message on the individual channel." 1110 DEFVAL{true} 1111 ::= { dsx0VismCnfEntry 37 } 1112 1113ds0Companding OBJECT-TYPE 1114 SYNTAX INTEGER 1115 { 1116 uLaw (1), 1117 aLaw (2) 1118 } 1119 MAX-ACCESS read-write 1120 STATUS current 1121 DESCRIPTION 1122 "This object indicates whether input from / output 1123 to the TDM side of DS0 is u-law or a-law stream. 1124 The setting of this object will not take effect 1125 unless the corresponding DSP channel is closed and 1126 re-opened." 1127 ::= { dsx0VismCnfEntry 38 } 1128 1129ds0RxCasTransTblName OBJECT-TYPE 1130 SYNTAX DisplayString 1131 MAX-ACCESS read-write 1132 STATUS current 1133 DESCRIPTION 1134 "This object identifies the template name 'cvcmCasTemplateName' 1135 in the CISCO-VOICE-CAS-MODULE-MIB associated with the receive 1136 signaling channel on a DS0." 1137 ::= { dsx0VismCnfEntry 39 } 1138 1139ds0TxCasTransTblName OBJECT-TYPE 1140 SYNTAX DisplayString 1141 MAX-ACCESS read-write 1142 STATUS current 1143 DESCRIPTION 1144 "This object identifies the template name 1145 'cvcmCasTemplateName' in the CISCO-VOICE-CAS-MODULE-MIB 1146 associated with the transmit signaling channel 1147 on a DS0." 1148 ::= { dsx0VismCnfEntry 40 } 1149 1150ds0TxRxCasConfig OBJECT-TYPE 1151 SYNTAX INTEGER { 1152 transmit (1), 1153 receive (2), 1154 bidirectional (3), 1155 none (4) 1156 } 1157 MAX-ACCESS read-write 1158 STATUS current 1159 DESCRIPTION 1160 "This object indicates configuration on a DS0. 1161 'transmit'- Configure transmit signaling channel 1162 on the DSP with user defined CAS 1163 pattern to translate incoming ABCD 1164 CAS bits from the TDM 1165 'receive'- Configure receive signaling channel 1166 on the DSP with user defined CAS 1167 pattern to translate the outgoing 1168 ABCD CAS bits on the TDM 1169 'bidirectional'- Configure transmit and receive 1170 signaling channel on the DSP with 1171 user defined CAS pattern to translate 1172 incoming and outgoing ABCD CAS bits 1173 on the TDM 1174 'none'- Signaling channel is using default 1175 ABCD CAS pattern specified by the DSP." 1176 ::= { dsx0VismCnfEntry 41 } 1177------------------------------------------------------------------- 1178-- 1179-- dsx0VismChanMapTable 1180-- This table defines the mapping between the Ds0 and the ifIndex 1181-- used to index the table dsx0VismCnfTable. 1182------------------------------------------------------------------- 1183 1184dsx0VismChanMapTable OBJECT-TYPE 1185 SYNTAX SEQUENCE OF Dsx0VismChanMapEntry 1186 MAX-ACCESS not-accessible 1187 STATUS current 1188 DESCRIPTION 1189 "This table is created implicitly at the time of 1190 creating and deleting the endpoints. 1191 This table provides the mapping information from a line 1192 and channel to obtain an index for that channel." 1193 ::= { dsx0Vism 2 } 1194 1195dsx0VismChanMapEntry OBJECT-TYPE 1196 SYNTAX Dsx0VismChanMapEntry 1197 MAX-ACCESS not-accessible 1198 STATUS current 1199 DESCRIPTION 1200 "Each entry represents the mapping from dsx1Line number 1201 to ds0 channel Number and provides the ifIndex mapping." 1202 INDEX { dsx1LineNum, ds0ChanNum } 1203 ::= { dsx0VismChanMapTable 1 } 1204 1205Dsx0VismChanMapEntry ::= 1206 SEQUENCE { 1207 dsx1LineNum Integer32, 1208 ds0ChanNum Integer32, 1209 ds0ChanMapIfIndex Integer32 1210} 1211 1212dsx1LineNum OBJECT-TYPE 1213 SYNTAX Integer32 (1..8) 1214 MAX-ACCESS read-only 1215 STATUS current 1216 DESCRIPTION 1217 "This object describes the physical line number on 1218 VISM card." 1219 ::= { dsx0VismChanMapEntry 1 } 1220 1221ds0ChanNum OBJECT-TYPE 1222 SYNTAX Integer32 (1..31) 1223 MAX-ACCESS read-only 1224 STATUS current 1225 DESCRIPTION 1226 "This object describes the ds0 number or channel number 1227 within a T1 or E1 line. 1228 The valid channel numbers are 1 to 24 for T1 line 1229 and 1 - 31 for E1 line." 1230 ::= { dsx0VismChanMapEntry 2 } 1231 1232ds0ChanMapIfIndex OBJECT-TYPE 1233 SYNTAX Integer32(1..2147483647) 1234 MAX-ACCESS read-only 1235 STATUS current 1236 DESCRIPTION 1237 "This object describes the ifIndex derived based on the 1238 line number and the channel number within the line according 1239 to the formula: 1240 IfIndex = 31 * (Ds1# - 1) + ds0# 1241 1242 where : Ds1# - The T1/E1 line number in the range 1 - 8. 1243 ds0# - The ds0 channel number ranging from 1244 1 to 24 for T1 1245 and 1 to 31 for E1." 1246 ::= { dsx0VismChanMapEntry 3 } 1247 1248 1249vismTotalDs0Count OBJECT-TYPE 1250 SYNTAX Integer32(0..2147483647) 1251 MAX-ACCESS read-only 1252 STATUS current 1253 DESCRIPTION 1254 "This is the total number of ds0s configured the card." 1255 DEFVAL { 0 } 1256 ::= { vismDs0CardStats 1 } 1257 1258vismFreeDs0Count OBJECT-TYPE 1259 SYNTAX Integer32(0..2147483647) 1260 MAX-ACCESS read-only 1261 STATUS current 1262 DESCRIPTION 1263 "This is the number of free ds0s on the card." 1264 DEFVAL { 0 } 1265 ::= { vismDs0CardStats 2 } 1266 1267vismActiveDs0Count OBJECT-TYPE 1268 SYNTAX Integer32 (0..2147483647) 1269 MAX-ACCESS read-only 1270 STATUS current 1271 DESCRIPTION 1272 "This is the number of active ds0s on the card." 1273 ::= { vismDs0CardStats 3 } 1274 1275vismBlockDs0Count OBJECT-TYPE 1276 SYNTAX Integer32 (0..2147483647) 1277 MAX-ACCESS read-only 1278 STATUS current 1279 DESCRIPTION 1280 "This is the number of blocked ds0s on the card." 1281 DEFVAL { 0 } 1282 ::= { vismDs0CardStats 4 } 1283 1284vismActiveHighWaterMark OBJECT-TYPE 1285 SYNTAX Integer32 (0..2147483647) 1286 MAX-ACCESS read-only 1287 STATUS current 1288 DESCRIPTION 1289 "This is the high water mark number of ds0s that were 1290 active simultaneously on the card." 1291 DEFVAL { 0 } 1292 ::= { vismDs0CardStats 5 } 1293 1294vismDs0CardStatsClrButton OBJECT-TYPE 1295 SYNTAX INTEGER { 1296 noaction (1), 1297 clear (2) 1298 } 1299 MAX-ACCESS read-write 1300 STATUS current 1301 DESCRIPTION 1302 "This variable is used to clear all the vism Ds0 1303 card stats. 1 = No action, 2 = Clear alarm" 1304 ::= { vismDs0CardStats 6 } 1305 1306-- 1307-- VISM DS0 Line Stats table 1308-- 1309 1310vismDs0LineStatsTable OBJECT-TYPE 1311 SYNTAX SEQUENCE OF VismDs0LineStatsEntry 1312 MAX-ACCESS not-accessible 1313 STATUS current 1314 DESCRIPTION 1315 "This table contains information on DS0s configured 1316 on DS1 interface." 1317 ::= { dsx0Vism 3 } 1318 1319vismDs0LineStatsEntry OBJECT-TYPE 1320 SYNTAX VismDs0LineStatsEntry 1321 MAX-ACCESS not-accessible 1322 STATUS current 1323 DESCRIPTION 1324 "An entry in the vismDs0LineStatsTable. 1325 Each entry contains following information 1326 applicable for each DS1 interface: 1327 Total DS0s 1328 Free DS0s 1329 Active DS0s 1330 Blocked DS0s." 1331 INDEX { ds0LineNum } 1332 ::= { vismDs0LineStatsTable 1 } 1333 1334VismDs0LineStatsEntry ::= 1335 SEQUENCE { 1336 ds0LineNum Integer32, 1337 lineTotalDs0Count Integer32, 1338 lineFreeDs0Count Integer32, 1339 lineActiveDs0Count Integer32, 1340 lineBlockDs0Count Integer32, 1341 lineActiveHighWaterMark Integer32, 1342 lineStatsClrButton INTEGER 1343 } 1344 1345ds0LineNum OBJECT-TYPE 1346 SYNTAX Integer32 (1..8) 1347 MAX-ACCESS read-only 1348 STATUS current 1349 DESCRIPTION 1350 "This object is the identifier of a DS1/E1 Interface on 1351 a managed device. The number of entries is 8 in a VISM 1352 and VISM-PR card." 1353 ::= { vismDs0LineStatsEntry 1 } 1354 1355lineTotalDs0Count OBJECT-TYPE 1356 SYNTAX Integer32(0..31) 1357 MAX-ACCESS read-only 1358 STATUS current 1359 DESCRIPTION 1360 "This is the total number of ds0s configured on this 1361 DS1 line." 1362 DEFVAL { 0 } 1363 ::= { vismDs0LineStatsEntry 2 } 1364 1365lineFreeDs0Count OBJECT-TYPE 1366 SYNTAX Integer32(0..31) 1367 MAX-ACCESS read-only 1368 STATUS current 1369 DESCRIPTION 1370 "This is the total number of free ds0s on this 1371 DS1 line." 1372 DEFVAL { 0 } 1373 ::= { vismDs0LineStatsEntry 3 } 1374 1375lineActiveDs0Count OBJECT-TYPE 1376 SYNTAX Integer32(0..31) 1377 MAX-ACCESS read-only 1378 STATUS current 1379 DESCRIPTION 1380 "This is the number of active ds0s on this line." 1381 DEFVAL { 0 } 1382 ::= { vismDs0LineStatsEntry 4 } 1383 1384lineBlockDs0Count OBJECT-TYPE 1385 SYNTAX Integer32(0..31) 1386 MAX-ACCESS read-only 1387 STATUS current 1388 DESCRIPTION 1389 "This is the number of blocked ds0s on this line." 1390 DEFVAL { 0 } 1391 ::= { vismDs0LineStatsEntry 5 } 1392 1393lineActiveHighWaterMark OBJECT-TYPE 1394 SYNTAX Integer32(0..31) 1395 MAX-ACCESS read-only 1396 STATUS current 1397 DESCRIPTION 1398 "This is the high water mark number of ds0s that 1399 were active simultaneously on the line." 1400 DEFVAL { 0 } 1401 ::= { vismDs0LineStatsEntry 6 } 1402 1403lineStatsClrButton OBJECT-TYPE 1404 SYNTAX INTEGER { 1405 noaction (1), 1406 clear (2) 1407 } 1408 MAX-ACCESS read-write 1409 STATUS current 1410 DESCRIPTION 1411 "This variable is used to clear the vism Ds0 line 1412 status entry. 1 = No action, 2 = Clear alarm." 1413 ::= { vismDs0LineStatsEntry 7 } 1414 1415-- 1416-- VISM DS0 Status table 1417-- 1418 1419vismDs0StatusTable OBJECT-TYPE 1420 SYNTAX SEQUENCE OF VismDs0StatusEntry 1421 MAX-ACCESS not-accessible 1422 STATUS current 1423 DESCRIPTION 1424 "This table contains ds0 status information on a 1425 DS1 interface." 1426 ::= { dsx0Vism 4 } 1427 1428 vismDs0StatusEntry OBJECT-TYPE 1429 SYNTAX VismDs0StatusEntry 1430 MAX-ACCESS not-accessible 1431 STATUS current 1432 DESCRIPTION 1433 "An entry in the Ds0 Status Table." 1434 INDEX { ds0LineNumber, ds0Number } 1435 ::= { vismDs0StatusTable 1 } 1436 1437VismDs0StatusEntry ::= 1438 SEQUENCE { 1439 ds0LineNumber Integer32, 1440 ds0Number Integer32, 1441 ds0Status INTEGER, 1442 ds0StatusClrButton INTEGER 1443 } 1444 1445ds0LineNumber OBJECT-TYPE 1446 SYNTAX Integer32 (1..8) 1447 MAX-ACCESS read-only 1448 STATUS current 1449 DESCRIPTION 1450 "This object is the identifier of a DS1/E1 Interface 1451 on a managed device. The number of entries is 8 in a 1452 VISM and VISM-PR card." 1453 ::= { vismDs0StatusEntry 1 } 1454 1455ds0Number OBJECT-TYPE 1456 SYNTAX Integer32 (1..31) 1457 MAX-ACCESS read-only 1458 STATUS current 1459 DESCRIPTION 1460 "This object identifies the ds0 number on a 1461 DS1 interface." 1462 ::= { vismDs0StatusEntry 2 } 1463 1464ds0Status OBJECT-TYPE 1465 SYNTAX INTEGER { 1466 idle (1), 1467 busy (2), 1468 fault (3), 1469 block (4), 1470 unknown (5) 1471 } 1472 MAX-ACCESS read-only 1473 STATUS current 1474 DESCRIPTION 1475 "This object is the status of the ds0. idle - This ds0 1476 is in idle state. busy - This ds0 is in busy state. 1477 Ds0 enters this state when it is in the process of 1478 being setup for a call. fault - This ds0 is in fault(alarm) 1479 state. block - This ds0 is in block state. 1480 Ds0 can enter this state when the line or 1481 gateway is commissioned out of service." 1482 DEFVAL { unknown } 1483 ::= { vismDs0StatusEntry 3 } 1484 1485ds0StatusClrButton OBJECT-TYPE 1486 SYNTAX INTEGER { 1487 noaction (1), 1488 clear (2) 1489 } 1490 MAX-ACCESS read-write 1491 STATUS current 1492 DESCRIPTION 1493 "This variable is used to clear the vism Ds0 1494 status. 1 = No action, 2 = Clear alarm" 1495 ::= { vismDs0StatusEntry 4 } 1496 1497-- conformance information 1498 1499ciscoVismDsx0MIBConformance OBJECT IDENTIFIER ::= { ciscoVismDsx0MIB 2 } 1500 1501ciscoVismDsx0MIBGroups OBJECT IDENTIFIER ::= 1502 { ciscoVismDsx0MIBConformance 1 } 1503 1504ciscoVismDsx0MIBCompliances OBJECT IDENTIFIER ::= 1505 { ciscoVismDsx0MIBConformance 2 } 1506 1507-- compliance statements 1508 1509ciscoVismDsx0Compliance MODULE-COMPLIANCE 1510 STATUS deprecated 1511 DESCRIPTION 1512 "The compliance statement for objects related 1513 to DS0 mib objects." 1514 MODULE -- this module 1515 MANDATORY-GROUPS { 1516 ciscoVismDsx0LineStatsGroup, 1517 ciscoVismDsx0StatusGroup, 1518 ciscoVismDsx0ConfGroup, 1519 ciscoVismDsx0ChanMapGroup, 1520 ciscoVismCardStatsGroup 1521 } 1522 ::= { ciscoVismDsx0MIBCompliances 1 } 1523 1524ciscoVismDsx0Compliance2 MODULE-COMPLIANCE 1525 STATUS current 1526 DESCRIPTION 1527 "The compliance statement for objects related 1528 to DS0 mib objects." 1529 MODULE -- this module 1530 MANDATORY-GROUPS { 1531 ciscoVismDsx0LineStatsGroup, 1532 ciscoVismDsx0StatusGroup, 1533 ciscoVismDsx0ConfGroup2, 1534 ciscoVismDsx0ChanMapGroup, 1535 ciscoVismCardStatsGroup 1536 } 1537 ::= { ciscoVismDsx0MIBCompliances 2 } 1538 1539ciscoVismCardStatsGroup OBJECT-GROUP 1540 OBJECTS { 1541 vismTotalDs0Count, 1542 vismFreeDs0Count, 1543 vismActiveDs0Count, 1544 vismBlockDs0Count, 1545 vismActiveHighWaterMark, 1546 vismDs0CardStatsClrButton 1547 } 1548 STATUS current 1549 DESCRIPTION 1550 "The collection of objects used for 1551 DS0 Statistics applicable to VISM Module." 1552 ::= { ciscoVismDsx0MIBGroups 1 } 1553 1554ciscoVismDsx0LineStatsGroup OBJECT-GROUP 1555 OBJECTS { 1556 ds0LineNum, 1557 lineTotalDs0Count, 1558 lineFreeDs0Count, 1559 lineActiveDs0Count, 1560 lineBlockDs0Count, 1561 lineActiveHighWaterMark, 1562 lineStatsClrButton 1563 } 1564 STATUS current 1565 DESCRIPTION 1566 "The collection of objects used for 1567 DS0 Line statistics." 1568 ::= { ciscoVismDsx0MIBGroups 2 } 1569 1570ciscoVismDsx0StatusGroup OBJECT-GROUP 1571 OBJECTS { 1572 ds0LineNumber, 1573 ds0Number, 1574 ds0Status, 1575 ds0StatusClrButton 1576 } 1577 STATUS current 1578 DESCRIPTION 1579 "The collection of objects used for 1580 DS0 status." 1581 ::= { ciscoVismDsx0MIBGroups 3 } 1582 1583ciscoVismDsx0ConfGroup OBJECT-GROUP 1584 OBJECTS { 1585 ds0IfIndex, 1586 ds0RobbedBitSignalling, 1587 ds0IdleCode, 1588 ds0SeizedCode, 1589 ds0ReceivedCode, 1590 ds0BundleMapped, 1591 ds0IfType, 1592 ds0CasVariantName, 1593 ds0CasCadenceOnTime , 1594 ds0CasCadenceOffTime, 1595 ds0InsertLocalCas, 1596 ds0LocalCasPattern, 1597 ds0LoopbackCommand, 1598 ds0CasParameterSource, 1599 ds0CasOnHookMinMakeTime, 1600 ds0CasOffHookMinMakeTime, 1601 ds0CasWinkMinMakeTime, 1602 ds0CasWinkMaxMakeTime, 1603 ds0CasWinkBreakTime, 1604 ds0CasGlareTime, 1605 ds0CasGaurdTime, 1606 ds0CasDelayImmedStart, 1607 ds0SignalingType, 1608 ds0CasMinDelayDialTime, 1609 ds0CasMinStartDialTime , 1610 ds0CasFlashMinMakeTime, 1611 ds0CasFlashMaxMakeTime, 1612 ds0CasDirectionality, 1613 ds0CasGlarePolicy, 1614 ds0CasIncomingMgcpPackage, 1615 ds0CasOutgoingMgcpPackage, 1616 ds0InputGain, 1617 ds0OutputAttenuation, 1618 ds0MusicThreshold, 1619 ds0SidPacket, 1620 ds0ExecDiag 1621 } 1622 STATUS deprecated 1623 DESCRIPTION 1624 "The collection of objects used for 1625 DS0 configuration in VISM module." 1626 ::= { ciscoVismDsx0MIBGroups 4 } 1627 1628ciscoVismDsx0ConfGroup2 OBJECT-GROUP 1629 OBJECTS { 1630 ds0IfIndex, 1631 ds0RobbedBitSignalling, 1632 ds0IdleCode, 1633 ds0SeizedCode, 1634 ds0ReceivedCode, 1635 ds0BundleMapped, 1636 ds0IfType, 1637 ds0CasVariantName, 1638 ds0CasCadenceOnTime , 1639 ds0CasCadenceOffTime, 1640 ds0InsertLocalCas, 1641 ds0LocalCasPattern, 1642 ds0LoopbackCommand, 1643 ds0CasParameterSource, 1644 ds0CasOnHookMinMakeTime, 1645 ds0CasOffHookMinMakeTime, 1646 ds0CasWinkMinMakeTime, 1647 ds0CasWinkMaxMakeTime, 1648 ds0CasWinkBreakTime, 1649 ds0CasGlareTime, 1650 ds0CasGaurdTime, 1651 ds0CasDelayImmedStart, 1652 ds0SignalingType, 1653 ds0CasMinDelayDialTime, 1654 ds0CasMinStartDialTime , 1655 ds0CasFlashMinMakeTime, 1656 ds0CasFlashMaxMakeTime, 1657 ds0CasDirectionality, 1658 ds0CasGlarePolicy, 1659 ds0CasIncomingMgcpPackage, 1660 ds0CasOutgoingMgcpPackage, 1661 ds0InputGain, 1662 ds0OutputAttenuation, 1663 ds0MusicThreshold, 1664 ds0SidPacket, 1665 ds0ExecDiag, 1666 ds0Companding, 1667 ds0RxCasTransTblName, 1668 ds0TxCasTransTblName, 1669 ds0TxRxCasConfig 1670 } 1671 STATUS current 1672 DESCRIPTION 1673 "The collection of objects used for 1674 DS0 configuration in VISM module." 1675 ::= { ciscoVismDsx0MIBGroups 7 } 1676 1677ciscoVismDsx0ChanMapGroup OBJECT-GROUP 1678 OBJECTS { 1679 dsx1LineNum, 1680 ds0ChanNum , 1681 ds0ChanMapIfIndex 1682 } 1683 STATUS current 1684 DESCRIPTION 1685 "The collection of objects used for 1686 mapping DS0 to ifIndex." 1687 ::= { ciscoVismDsx0MIBGroups 5 } 1688 1689ciscoVismDsx0ConfDeprecatedGroup OBJECT-GROUP 1690 OBJECTS { 1691 ds0TransmitCodesEnable 1692 } 1693 STATUS deprecated 1694 DESCRIPTION 1695 "The collection of objects that were 1696 supported earlier but deprecated now." 1697 ::= { ciscoVismDsx0MIBGroups 6 } 1698 1699END 1700 1701