1-- ***************************************************************** 2-- CISCO-WAN-VISM-TONE-PLAN-MIB 3-- 4-- 5-- December 2003, George Ogagan 6-- 7-- Copyright (c) 2001-2003 by Cisco Systems, Inc. 8-- All rights reserved. 9-- 10-- ***************************************************************** 11 12CISCO-WAN-VISM-TONE-PLAN-MIB DEFINITIONS ::= BEGIN 13 14IMPORTS 15 MODULE-IDENTITY, 16 OBJECT-TYPE, 17 Integer32 18 FROM SNMPv2-SMI 19 MODULE-COMPLIANCE, 20 OBJECT-GROUP 21 FROM SNMPv2-CONF 22 DisplayString, 23 RowStatus 24 FROM SNMPv2-TC 25 ciscoWan FROM CISCOWAN-SMI; 26 27 28 29vismTonePlanGrpMIB MODULE-IDENTITY 30 LAST-UPDATED "200312170000Z" 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 is defined to configure the programmable 46 Tone Plan feature on VISM. 47 " 48 49 REVISION "200312170000Z" 50 DESCRIPTION 51 "1. Remove default value from vismEventCode object. 52 2. Change default value of vismFreqMaxDelay object 53 from 3 to 10. 54 3. Change default value of vismMinOnCadence object 55 from 3 to 20. 56 4. Change default value of vismMaxOffCadence object 57 from 5 to 450. 58 5. Remove default value from vismFrequency1 object. 59 6. Remove default value from vismFrequency2 object. 60 7. Remove default value from vismFreqOnCadence object. 61 8. Change default value of seqToneMaximumGapDuration 62 object from 10 to 15. 63 9. Change SYNTAX INTEGER to Integer32 except for 64 enumerated integers in vismConfigToneDetectEntry. 65 10. Clarify description of object. 66 " 67 68 REVISION "200304230000Z" 69 DESCRIPTION " 70 Added Object vismConfigToneDetect (Programmable Tone) 71 under vismTonePlan 72 " 73 REVISION "200207190000Z" 74 DESCRIPTION 75 "Give tonePlanIndex a range (1..1000) to be 76 compiled in new SMICNG compiler (ver2.2.11-beta). 77 " 78 79 REVISION "200112260000Z" 80 DESCRIPTION 81 "Description changes for tonePlanEntryStatus, 82 tonePlanProvisionFlag, vismTonePlanEntry. 83 " 84 85 REVISION "200108050000Z" 86 DESCRIPTION 87 "Results from MIB external interfaces review. 88 " 89 90 REVISION "200104030000Z" 91 DESCRIPTION 92 "Initial draft. Created new VISM Tone Plan Group. 93 " 94 95 ::= { ciscoWan 24 } 96 97 98vismTonePlanGrpMIBObjects OBJECT IDENTIFIER ::= 99 { vismTonePlanGrpMIB 1} 100vismTonePlan OBJECT IDENTIFIER ::= 101 { vismTonePlanGrpMIBObjects 1 } 102vismTonePlanControlGrp OBJECT IDENTIFIER ::= { vismTonePlan 1 } 103vismTonePlanTableGrp OBJECT IDENTIFIER ::= { vismTonePlan 2 } 104 105vismConfigToneDetectGrp OBJECT IDENTIFIER ::= { vismTonePlan 3 } 106vismSequentialToneDetectGrp OBJECT IDENTIFIER ::= { vismTonePlan 4 } 107 108-- ------------------------------------------------------------------ 109-- 110-- vismTonePlan Control group 111-- 112-- 113-- The MIB variables in this group have been defined to report 114-- the size of the programmable Tone Plan table on VISM and 115-- any other high level controls of the Tone Plan Feature. 116-- 117-- ------------------------------------------------------------------ 118 119tonePlanCurrentSize OBJECT-TYPE 120 SYNTAX Integer32 121 MAX-ACCESS read-only 122 STATUS current 123 DESCRIPTION 124 "This object specifies the number of entries 125 in vismTonePlanTable. 126 " 127 ::= { vismTonePlanControlGrp 1 } 128 129-- ------------------------------------------------------------------ 130-- 131-- vismTonePlan group 132-- 133-- 134-- The MIB variables in this group have been defined to configure 135-- the programmable Tone Plan feature on VISM. VISM card can be 136-- configured with different Tone Plans by downloading the different 137-- files which contains the various Tone Plans from the PXM. 138-- 139-- ------------------------------------------------------------------ 140 141 142vismTonePlanTable OBJECT-TYPE 143 SYNTAX SEQUENCE OF VismTonePlanEntry 144 MAX-ACCESS not-accessible 145 STATUS current 146 DESCRIPTION 147 "This table contains configuration information about different 148 Tone Plans. 149 150 The first 32 entries of the table are 'provisionable' 151 followed by an implementation specific number 152 of 'builtIn' entries. 153 " 154 ::= { vismTonePlanTableGrp 1 } 155 156 157vismTonePlanEntry OBJECT-TYPE 158 SYNTAX VismTonePlanEntry 159 MAX-ACCESS not-accessible 160 STATUS current 161 DESCRIPTION 162 "An entry in the vismTonePlanTable. Each entry consists of 163 configuration information for a specific Tone Plan. 164 165 The vismTonePlanTable is of fixed size with a predefined 166 number of entries, where each entry contains usable 167 information or not depending upon the value of the 168 tonePlanEntryStatus MIB object. 169 170 The configuration is retained after VISM card reboots. 171 172 tonePlanRegionName, tonePlanVersionNumber, and 173 tonePlanFileName can be modified only if the 174 tonePlanProvisionFlag is 'provisionable' and 175 tonePlanEntryStatus is 'configured' when loading a new 176 tone plan (see MIB object tonePlanEntryStatus below). After 177 the new tone plan is loaded, these three MIB objects may 178 not be modified. To change these objects, the entry in 179 this table must be deleted, and all objects re-added 180 with new corrected values. 181 182 The rest of the entries of this table, (the 'builtIn' ones) 183 cannot be modified after the table is build at reload time. 184 " 185 INDEX { tonePlanIndex } 186 ::= { vismTonePlanTable 1 } 187 188 189VismTonePlanEntry ::= 190 SEQUENCE { 191 tonePlanIndex Integer32, 192 tonePlanEntryStatus INTEGER, 193 tonePlanProvisionFlag INTEGER, 194 tonePlanRegionName DisplayString, 195 tonePlanVersionNumber Integer32, 196 tonePlanFileName DisplayString 197 } 198 199 200tonePlanIndex OBJECT-TYPE 201 SYNTAX Integer32 (1..1000) 202 MAX-ACCESS not-accessible 203 STATUS current 204 DESCRIPTION 205 " Serves as index to this table. However, the maximum 206 entry allowed is specify in tonePlanCurrentSize. 207 " 208 ::= { vismTonePlanEntry 1 } 209 210 211tonePlanEntryStatus OBJECT-TYPE 212 SYNTAX INTEGER 213 { 214 unused (1), 215 configured (2), 216 reloading (3), 217 lostFile (4) 218 } 219 MAX-ACCESS read-write 220 STATUS current 221 DESCRIPTION 222 " This attribute specifies the status of this entry as to 223 whether this entry (row) contains usable Tone Plan 224 configuration information (object is set to 'configured'), 225 or if it is empty (object is set to 'unused'), or if is 226 temporarily (object is set to 'reloading') or 227 permanently (object is set to 'lostFile') unusable. 228 229 230 This tone plan information for this row can be used 231 by a DS-1 line only if this object has a value of 232 'configured (2)'. 233 234 To add a configured entry in the vismTonePlanTable 235 table, there must be an existing empty row with its 236 entry status set to 'unused(1)'. 237 238 Then before this empty row in the vismTonePlanTable 239 table can be changed to 'configured', it must, in 240 one single operation, be given all the usable 241 values necessary to be stored in the 242 tonePlanRegionName, tonePlanVersionNumber and 243 tonePlanFileName MIB objects for this row. In addition, 244 those values for the tonePlanRegionName and 245 tonePlanVersionNumber MIB objects pair must be 246 unique with respect to every other row of the 247 vismTonePlanTable. Then, as this existing empty row 248 is set with all three valid entries for the 249 tonePlanRegionName, tonePlanVersionNumber, 250 and tonePlanFileName MIB objects, the Entry Status 251 MIB object for this row will be finally, internally, 252 set to 'configured(2)'. This final 'configured' status 253 is the direct result of correctly setting these three 254 MIB objects with valid data. 255 256 In no case will an external manager be able to directly 257 set this MIB object to 'configured(2)' by a SNMP set 258 command, for such a single stand alone command will 259 be rejected. 260 261 Once a table entry is set to 'configured(2)' with 262 valid tonePlanRegionName, tonePlanVersionNumber, and 263 tonePlanFileName MIB objects for this row, then these 264 MIB objects may not be modified by any subsequent 265 SNMP set command. In the case where a row needs to 266 have these objects changed, this entry must be cleared 267 from the table (paragraph below) and a new entry added 268 by the add process above. 269 270 Once an entry exists in the vismTonePlanTable table it 271 may be cleared and set to unused by setting this MIB 272 object to 'unused(1)'. But before the entry status of 273 any entry in this table can be set to 'unused(1)', 274 there is a check to make sure there is no 275 vismDsx1TonePlanRegion MIB object and 276 vismDsx1TonePlanVersion MIB object pair in the 277 dsx1VismCnfGrpTable MIB table that may point to or 278 refer to this table entry (row) with its unique 279 tonePlanRegionName and tonePlanVersionNumber. 280 281 Once the entry status of an entry in this table is set 282 to 'unused(1)', all the other MIB objects for this 283 table row are set to defaults or to NULL. 284 285 286 Once an entry is 'configured', if a subsequent card 287 reset occurs the VISM card will attempt to restore 288 all of the configuration information by doing the 289 normal download of the latest MIB database, set all 290 'configured (2)' MIB objects to 'reloading (3)', and 291 then do an automatic background process to retrieve 292 all of the tone plan files from the server since they 293 were not downloaded by the PXM. If this retrieval of 294 the tone plan files succeeds then this MIB object 295 will be set back to 'configured (2)'. If this file 296 retrieval does not succeed, then this MIB object will 297 be set to 'lostFile (4)'. In no way will an external 298 manager be able to directly set this MIB object 299 to 'reloading (3)' or 'lostFile (4)' by a SNMP set 300 command. 301 " 302 DEFVAL { unused } 303 ::= { vismTonePlanEntry 2 } 304 305 306tonePlanProvisionFlag OBJECT-TYPE 307 SYNTAX INTEGER 308 { 309 builtIn (1), 310 provisionable (2) 311 } 312 MAX-ACCESS read-only 313 STATUS current 314 DESCRIPTION 315 " This attribute specifies whether this entry contains 316 predefined Tone Plan configuration information from 317 internal firmware code (object is set to 'builtIn') or 318 if it has been configured with tone plan configuration 319 information that has been downloaded from the PXM 320 (object is set to unused). 321 322 Only entries that are provisionable may have their 323 tonePlanEntryStatus MIB object marked as unused in 324 this table. BuiltIn entries may not be marked as unused. 325 " 326 ::= { vismTonePlanEntry 3 } 327 328tonePlanRegionName OBJECT-TYPE 329 SYNTAX DisplayString (SIZE(1..64)) 330 MAX-ACCESS read-write 331 STATUS current 332 DESCRIPTION 333 " The region (or country) for which this tone plan is 334 defined. Any other entry in this table may have an 335 identical name, but the combination of tonePlanRegionName 336 and tonePlanVersionNumber must be unique. 337 338 This field may be from 1 to 64 alphabetic, numeric, or 339 underscore characters long, with no embedded spaces. 340 A NULL entry will consist of a single space character 341 of length one. 342 " 343 ::= { vismTonePlanEntry 4 } 344 345 346tonePlanVersionNumber OBJECT-TYPE 347 SYNTAX Integer32 (0..65535) 348 MAX-ACCESS read-write 349 STATUS current 350 DESCRIPTION 351 " This attribute specifies this entry's version number 352 for a tone plan for a region. Multiple tone plans may 353 be defined for each region, but each of these tone 354 plans must have a unique tonePlanRegionName and 355 tonePlanVersionNumber. When a new tone plan is added 356 for a region, it should be added with a newer(larger) 357 version number. 358 359 Allowed values are in range (1..65535) but a value of 360 zero being set in this object means that this object 361 is a NULL entry. 362 " 363 ::= { vismTonePlanEntry 5 } 364 365 366tonePlanFileName OBJECT-TYPE 367 SYNTAX DisplayString (SIZE(1..32)) 368 MAX-ACCESS read-write 369 STATUS current 370 DESCRIPTION 371 " This is the name of a valid file stored on the TFTP 372 server which contains the tone definitions. A missing 373 or invalid file name will cause a failure in the 374 configuration of this entry. 375 376 If this entry points to a build-in tone plan predefined 377 in firmware, then this name will be: 'BUILTIN'. 378 Provisionable file names are not allowed to have the 379 string 'BUILTIN' as their names. 380 381 This field may be from 1 to 32 alphabetic, numeric, or 382 underscore characters (no embedded spaces) long for a 383 valid entry. A NULL entry will consist of a single 384 space character of length one. 385 " 386 ::= { vismTonePlanEntry 6 } 387 388-- ------------------------------------------------------------------ 389-- 390-- vismConfigToneDetectGrp group 391-- 392-- 393-- The MIB variables in this group have been defined to configure 394-- the programmable CallProgress Tone Plan feature on VISM. 395-- VISM card can be configured with different tones by 396-- configuring the different rows of this table, and assigning 397-- an eventID against it. Then this eventID can be requested 398-- from the CallAgent as a telephone-event. 399-- 400-- ------------------------------------------------------------------ 401 402vismConfigToneDetectTable OBJECT-TYPE 403 SYNTAX SEQUENCE OF VismConfigToneDetectEntry 404 MAX-ACCESS not-accessible 405 STATUS current 406 DESCRIPTION 407 "This table contains the list of user configurable dual 408 frequency tones that can be detected on VISM. The call 409 agent can request the VISM to detect any of the tones 410 defined in this table. 411 412 Entries to this table can only be added or deleted, 413 not modified. Individual parameters within a row 414 cannot be changed without deleting and re-adding 415 the entry. 416 " 417 ::= { vismConfigToneDetectGrp 1 } 418 419 420vismConfigToneDetectEntry OBJECT-TYPE 421 SYNTAX VismConfigToneDetectEntry 422 MAX-ACCESS not-accessible 423 STATUS current 424 DESCRIPTION 425 "This is the primary entry in the vismConfigToneDetectTable. 426 Each entry references a User configurable dual 427 frequency tones that can be detected on VISM. 428 " 429 430 INDEX { vismConfigToneDetectNum } 431 ::= { vismConfigToneDetectTable 1 } 432 433VismConfigToneDetectEntry ::= 434 SEQUENCE { 435 vismConfigToneDetectNum Integer32, 436 vismEventCode Integer32, 437 vismConfigToneDetectRowStatus RowStatus, 438 vismFreqMaxDeviation Integer32, 439 vismFreqMaxPower Integer32, 440 vismFreqMinPower Integer32, 441 vismFreqPowerTwist Integer32, 442 vismFreqMaxDelay Integer32, 443 vismMinOnCadence Integer32, 444 vismMaxOffCadence Integer32, 445 vismFreqNumOfCadenceMatch Integer32, 446 vismFrequency1 Integer32, 447 vismFrequency2 Integer32, 448 vismFreqOnCadence Integer32, 449 vismFreqOffCadence Integer32 450 } 451 452vismConfigToneDetectNum OBJECT-TYPE 453 SYNTAX Integer32 (1..10) 454 MAX-ACCESS read-only 455 STATUS current 456 DESCRIPTION 457 "This is the index of this table. Currently only 458 tones 1 to 10 are used and call agent can request up to 459 ten tones to be detected on different endpoints at 460 any point in time. 461 " 462 ::= { vismConfigToneDetectEntry 1 } 463 464vismEventCode OBJECT-TYPE 465 SYNTAX Integer32 (0..255) 466 MAX-ACCESS read-create 467 STATUS current 468 DESCRIPTION 469 "This is the secondary index of this table. Call agent can 470 request supervision tone detection indexed by this field. 471 The values of event code are mapped from the subscriber 472 line event codes defined in RFC2833. Currently VISM supports 473 detection of only a handful of supervision tones like 474 Ringing, Busy, Dial-Tone and SIT tones. 475 " 476 ::= { vismConfigToneDetectEntry 2 } 477 478vismConfigToneDetectRowStatus OBJECT-TYPE 479 SYNTAX RowStatus 480 MAX-ACCESS read-create 481 STATUS current 482 DESCRIPTION 483 "Controls the creation and deletion of a Config Tone. 484 485 An entry may be created using the 'createAndGo' option. 486 When the row is successfully created, the 487 vismConfigToneDetectRowStatus would be set to 'active' 488 by the agent. An entry may be deleted by setting the 489 vismConfigToneDetectRowStatus to 'destroy'. 490 " 491 ::= { vismConfigToneDetectEntry 3 } 492 493vismFreqMaxDeviation OBJECT-TYPE 494 SYNTAX Integer32 (10..125) 495 UNITS "Hz" 496 MAX-ACCESS read-create 497 STATUS current 498 DESCRIPTION 499 "Specifies the maximum frequency deviation to be 500 used by VISM when detecting a specific dual 501 frequency tone. 502 503 Please refer the VISM configuration guide for standard 504 values to be used for this field. 505 " 506 DEFVAL { 30 } 507 ::= { vismConfigToneDetectEntry 4 } 508 509 510vismFreqMaxPower OBJECT-TYPE 511 SYNTAX Integer32 (0..30) 512 UNITS "dB" 513 MAX-ACCESS read-create 514 STATUS current 515 DESCRIPTION 516 "Specifies the maximum frequency power to be 517 used by VISM when detecting a specific dual 518 frequency tone. 519 520 Please refer the VISM configuration guide for standard 521 values to be used for this field. 522 " 523 DEFVAL { 0 } 524 ::= { vismConfigToneDetectEntry 5 } 525 526vismFreqMinPower OBJECT-TYPE 527 SYNTAX Integer32 (10..35) 528 UNITS "dB" 529 MAX-ACCESS read-create 530 STATUS current 531 DESCRIPTION 532 "Specifies the minimum frequency power to be 533 used by VISM when detecting a specific dual 534 frequency tone. 535 536 Please refer the VISM configuration guide for standard 537 values to be used for this field. 538 " 539 DEFVAL { 35 } 540 ::= { vismConfigToneDetectEntry 6 } 541 542vismFreqPowerTwist OBJECT-TYPE 543 SYNTAX Integer32 (0..15) 544 UNITS "dB" 545 MAX-ACCESS read-create 546 STATUS current 547 DESCRIPTION 548 "Specifies the maximum frequency power twist permitted 549 between the two frequencies used by VISM when 550 detecting a dual frequency tone. 551 552 Please refer the VISM configuration guide for standard 553 values to be used for this field. 554 " 555 DEFVAL { 10 } 556 ::= { vismConfigToneDetectEntry 7 } 557 558vismFreqMaxDelay OBJECT-TYPE 559 SYNTAX Integer32 (0..100) 560 UNITS "milliseconds" 561 MAX-ACCESS read-create 562 STATUS current 563 DESCRIPTION 564 "Specifies the maximum frequency delay to be 565 used by VISM when detecting a dual frequency tone. 566 567 Please refer the VISM configuration guide for standard 568 values to be used for this field. 569 570 It is measured in units of 10ms. 571 " 572 DEFVAL { 10 } 573 ::= { vismConfigToneDetectEntry 8 } 574 575vismMinOnCadence OBJECT-TYPE 576 SYNTAX Integer32 (3..100) 577 UNITS "milliseconds" 578 MAX-ACCESS read-create 579 STATUS current 580 DESCRIPTION 581 "Specifies the minimum tone cycle ON time that is 582 necessary for the VISM to detect the dual frequency 583 tone. The vismMinOnCadence has to be less than 584 vismFreqOnCadence value. 585 586 Please refer the VISM configuration guide for standard 587 values to be used for this field. 588 " 589 DEFVAL { 20 } 590 ::= { vismConfigToneDetectEntry 9 } 591 592vismMaxOffCadence OBJECT-TYPE 593 SYNTAX Integer32 (5..5000) 594 MAX-ACCESS read-create 595 STATUS current 596 DESCRIPTION 597 "Specifies the maximum tone cycle OFF time that 598 is necessary for the VISM to detect the dual 599 frequency tone. The vismMaxOffCadence should be 600 greater than vismFreqOffCadence value. 601 602 Please refer the VISM configuration guide for standard 603 values to be used for this field. 604 " 605 DEFVAL { 450 } 606 ::= { vismConfigToneDetectEntry 10 } 607 608 609vismFreqNumOfCadenceMatch OBJECT-TYPE 610 SYNTAX Integer32 (0..6) 611 MAX-ACCESS read-create 612 STATUS current 613 DESCRIPTION 614 "Specifies the number of pairs of the dual frequency that 615 needs to be detected. Currently ten pairs of frequency can 616 be detected by the DSP. 617 " 618 DEFVAL { 1 } 619 ::= { vismConfigToneDetectEntry 11 } 620 621vismFrequency1 OBJECT-TYPE 622 SYNTAX Integer32 (280..3800) 623 UNITS "Hz" 624 MAX-ACCESS read-create 625 STATUS current 626 DESCRIPTION 627 "Specifies the 1st frequency component of the dual 628 frequency to be detected by the VISM. 629 " 630 ::= { vismConfigToneDetectEntry 12 } 631 632vismFrequency2 OBJECT-TYPE 633 SYNTAX Integer32 (0..3800) 634 UNITS "Hz" 635 MAX-ACCESS read-create 636 STATUS current 637 DESCRIPTION 638 "Specifies the 2nd frequency component of the dual 639 frequency to be detected by the DSP. A value of 0 640 means this is a single frequency. The range of 641 1 to 279 is not a valid range in the DSP. 642 " 643 ::= { vismConfigToneDetectEntry 13 } 644 645vismFreqOnCadence OBJECT-TYPE 646 SYNTAX Integer32 (3..5000) 647 UNITS "milliseconds" 648 MAX-ACCESS read-create 649 STATUS current 650 DESCRIPTION 651 "The On time in each cycle of the dual frequency 652 to be detected by the DSP. The vismFreqOnCadence 653 has to be less than vismMinOnCadence value. 654 655 It is measured in units of 10ms. 656 " 657 ::= { vismConfigToneDetectEntry 14 } 658 659vismFreqOffCadence OBJECT-TYPE 660 SYNTAX Integer32 (5..5000) 661 UNITS "milliseconds" 662 MAX-ACCESS read-create 663 STATUS current 664 DESCRIPTION 665 "The Off time in each cycle of the dual frequency 666 to be detected by the DSP. The vismFreqOffCadence 667 should be lesser than the vismMaxOffCadence value. 668 669 It is measured in units of 10ms. 670 " 671 ::= { vismConfigToneDetectEntry 15 } 672 673 674 675-- ------------------------------------------------------------------ 676-- 677-- vismSequentialToneDetectGrp group 678-- 679-- This group holds the values needed to use the Sequential tone 680-- detector on the VISM DSP. It is used to be able to specify 681-- the frequencies, cadence, etc parameters to the DSP. This 682-- event can be requested by call agent. 683-- 684-- the MIB variable values within this group will be saved over 685-- a card reset the objects in this group are only valid in 686-- VoIP switching mode. 687-- 688-- ------------------------------------------------------------------ 689seqToneNumOfFrequencies OBJECT-TYPE 690 SYNTAX Integer32 (1..10) 691 MAX-ACCESS read-write 692 STATUS current 693 DESCRIPTION 694 " The number of single frequencies which have to be detected 695 by the sequential tone detector command on VISM. The 696 frequencies should specified below (seqToneFrequency1 to 697 seqToneFrequency10). This number should correspond to the 698 non-zero frequency values seqToneFrequency1 to 699 seqToneFrequency10. 700 " 701 DEFVAL { 3 } 702 ::= { vismSequentialToneDetectGrp 1 } 703 704seqToneEventID OBJECT-TYPE 705 SYNTAX Integer32 (0..255) 706 MAX-ACCESS read-write 707 STATUS current 708 DESCRIPTION 709 " The eventID corresponding to the sequential frequency. 710 Currently only supports Event 74 (SIT tone) 711 " 712 DEFVAL { 74 } 713 ::= { vismSequentialToneDetectGrp 2 } 714 715seqToneDurationOfEachTone OBJECT-TYPE 716 SYNTAX Integer32 (1..65534) 717 MAX-ACCESS read-write 718 STATUS current 719 DESCRIPTION 720 " Nominal tone duration of each single tone in counts of 10ms 721 used with sequential tone detector on VISM DSP. 722 " 723 DEFVAL { 33 } 724 ::= { vismSequentialToneDetectGrp 3 } 725 726seqToneGapBetweenEachTone OBJECT-TYPE 727 SYNTAX Integer32 (1..65534) 728 MAX-ACCESS read-write 729 STATUS current 730 DESCRIPTION 731 " Nominal silence gap duration between each tone in 10ms 732 used with sequential tone detector on VISM DSP. 733 " 734 DEFVAL { 1 } 735 ::= { vismSequentialToneDetectGrp 4 } 736 737seqToneDurationDeviation OBJECT-TYPE 738 SYNTAX Integer32 (1..4095) 739 MAX-ACCESS read-write 740 STATUS current 741 DESCRIPTION 742 " Tone duration deviation allowed in 10ms 743 used with sequential tone detector on VISM DSP. 744 " 745 DEFVAL { 2 } 746 ::= { vismSequentialToneDetectGrp 5 } 747 748seqToneMaximumGapDuration OBJECT-TYPE 749 SYNTAX Integer32 (1..4095) 750 MAX-ACCESS read-write 751 STATUS current 752 DESCRIPTION 753 " Maximum tone duration allowed in 10ms 754 used with sequential tone detector on VISM DSP. 755 " 756 DEFVAL { 15 } 757 ::= { vismSequentialToneDetectGrp 6 } 758 759seqToneGapDurationDeviation OBJECT-TYPE 760 SYNTAX Integer32 (1..4095) 761 MAX-ACCESS read-write 762 STATUS current 763 DESCRIPTION 764 " Tone duration deviation allowed in 10ms 765 used with sequential tone detector on VISM DSP. 766 " 767 DEFVAL { 20 } 768 ::= { vismSequentialToneDetectGrp 7 } 769 770seqToneFreqDeviation OBJECT-TYPE 771 SYNTAX Integer32 (1..1000) 772 MAX-ACCESS read-write 773 STATUS current 774 DESCRIPTION 775 " Frequency deviation allowed (1 - 1000 Hz) 776 used with sequential tone detector on VISM DSP. 777 " 778 DEFVAL { 40 } 779 ::= { vismSequentialToneDetectGrp 8 } 780 781seqTonePowerLevelCeiling OBJECT-TYPE 782 SYNTAX Integer32 (0..40) 783 MAX-ACCESS read-write 784 STATUS current 785 DESCRIPTION 786 " Maximum ceiling power level of the sequential 787 frequency tone (absolute value in dBm) 788 used with sequential tone detector on VISM DSP. 789 Range from 0 to 40 (0 to -40dB) 790 " 791 DEFVAL { 3 } 792 ::= { vismSequentialToneDetectGrp 9 } 793 794seqTonePowerLevelFloor OBJECT-TYPE 795 SYNTAX Integer32 (0..40) 796 MAX-ACCESS read-write 797 STATUS current 798 DESCRIPTION 799 " Lowest (floor) power level of the sequential 800 frequency tone (absolute value in dBm) 801 used with sequential tone detector on VISM DSP. 802 Range from 0 to 40 (0 to -40dB) 803 " 804 DEFVAL { 40 } 805 ::= { vismSequentialToneDetectGrp 10 } 806 807seqToneFrequency1 OBJECT-TYPE 808 SYNTAX Integer32 (280..3800) 809 MAX-ACCESS read-write 810 STATUS current 811 DESCRIPTION 812 " 1st frequency in the SequentialTone to detect (280 - 3800), 813 used with sequential tone detector on VISM DSP. 814 " 815 DEFVAL { 950 } 816 ::= { vismSequentialToneDetectGrp 11 } 817 818seqToneFrequency2 OBJECT-TYPE 819 SYNTAX Integer32 (280..3800) 820 MAX-ACCESS read-write 821 STATUS current 822 DESCRIPTION 823 " 2nd frequency in the SequentialTone to detect (280 - 3800), 824 used with sequential tone detector on VISM DSP. 825 " 826 DEFVAL { 1400 } 827 ::= { vismSequentialToneDetectGrp 12 } 828 829seqToneFrequency3 OBJECT-TYPE 830 SYNTAX Integer32 (280..3800) 831 MAX-ACCESS read-write 832 STATUS current 833 DESCRIPTION 834 " 3rd frequency in the SequentialTone to detect (280 - 3800), 835 used with sequential tone detector on VISM DSP. 836 " 837 DEFVAL { 1800 } 838 ::= { vismSequentialToneDetectGrp 13 } 839 840seqToneFrequency4 OBJECT-TYPE 841 SYNTAX Integer32 (280..3800) 842 MAX-ACCESS read-write 843 STATUS current 844 DESCRIPTION 845 " 4th frequency in the SequentialTone to detect (280 - 3800), 846 used with sequential tone detector on VISM DSP. 847 " 848 DEFVAL { 280 } 849 ::= { vismSequentialToneDetectGrp 14 } 850 851seqToneFrequency5 OBJECT-TYPE 852 SYNTAX Integer32 (280..3800) 853 MAX-ACCESS read-write 854 STATUS current 855 DESCRIPTION 856 " 5th frequency in the SequentialTone to detect (280 - 3800), 857 used with sequential tone detector on VISM DSP. 858 " 859 DEFVAL { 280 } 860 ::= { vismSequentialToneDetectGrp 15 } 861 862seqToneFrequency6 OBJECT-TYPE 863 SYNTAX Integer32 (280..3800) 864 MAX-ACCESS read-write 865 STATUS current 866 DESCRIPTION 867 " 6th frequency in the SequentialTone to detect (280 - 3800), 868 used with sequential tone detector on VISM DSP. 869 " 870 DEFVAL { 280 } 871 ::= { vismSequentialToneDetectGrp 16 } 872 873seqToneFrequency7 OBJECT-TYPE 874 SYNTAX Integer32 (280..3800) 875 MAX-ACCESS read-write 876 STATUS current 877 DESCRIPTION 878 " 7th frequency in the SequentialTone to detect (280 - 3800), 879 used with sequential tone detector on VISM DSP. 880 " 881 DEFVAL { 280 } 882 ::= { vismSequentialToneDetectGrp 17 } 883 884seqToneFrequency8 OBJECT-TYPE 885 SYNTAX Integer32 (280..3800) 886 MAX-ACCESS read-write 887 STATUS current 888 DESCRIPTION 889 " 8th frequency in the SequentialTone to detect (280 - 3800), 890 used with sequential tone detector on VISM DSP. 891 " 892 DEFVAL { 280 } 893 ::= { vismSequentialToneDetectGrp 18 } 894 895seqToneFrequency9 OBJECT-TYPE 896 SYNTAX Integer32 (280..3800) 897 MAX-ACCESS read-write 898 STATUS current 899 DESCRIPTION 900 " 9th frequency in the SequentialTone to detect (280 - 3800), 901 used with sequential tone detector on VISM DSP. 902 " 903 DEFVAL { 280 } 904 ::= { vismSequentialToneDetectGrp 19 } 905 906seqToneFrequency10 OBJECT-TYPE 907 SYNTAX Integer32 (280..3800) 908 MAX-ACCESS read-write 909 STATUS current 910 DESCRIPTION 911 " 10th frequency in the SequentialTone to detect (280 - 3800), 912 used with sequential tone detector on VISM DSP. 913 " 914 DEFVAL { 280 } 915 ::= { vismSequentialToneDetectGrp 20 } 916 917 918 919-- ***************************************************************** 920-- vism Tone Plan group notification 921-- ***************************************************************** 922-- ***************************************************************** 923 924vismToneNotificationPrefix OBJECT IDENTIFIER ::= 925 { vismTonePlanGrpMIB 2 } 926 927vismToneNotifications OBJECT IDENTIFIER ::= 928 { vismToneNotificationPrefix 0 } 929 930 931-- ********************************************************************** 932-- Conformance 933-- ********************************************************************** 934 935-- 936-- conformance information 937-- 938 939vismTonePlanMIBConformance OBJECT IDENTIFIER ::= 940 { vismTonePlanGrpMIB 3 } 941 942vismTonePlanMIBCompliances OBJECT IDENTIFIER ::= 943 { vismTonePlanMIBConformance 1 } 944vismTonePlanMIBGroups OBJECT IDENTIFIER ::= 945 { vismTonePlanMIBConformance 2 } 946 947 948-- 949-- Conformance and compliance statements statements 950-- 951 952vismTonePlanMIBCompliance MODULE-COMPLIANCE 953 STATUS current 954 DESCRIPTION 955 " The complaince statement for VISM Tone Plan group 956 which implements vismTonePlanGrp MIB." 957 MODULE -- this module 958 MANDATORY-GROUPS { vismTonePlanControlGroup, 959 vismTonePlanTableGroup, 960 vismConfigToneDetectTableGroup, 961 vismSequentialToneDetectGroup 962 } 963 964 OBJECT vismConfigToneDetectRowStatus 965 SYNTAX INTEGER { 966 active(1), 967 createAndGo(4), 968 destroy(6) 969 } 970 971 DESCRIPTION 972 "Only three values 'createAndGo', 'destroy' and 973 'active' out of the six enumerated values need to 974 be supported. 975 " 976 977 ::= { vismTonePlanMIBCompliances 1 } 978 979 980-- 981-- units of conformance 982-- 983-- MIB Groups 984-- 985 986 987vismTonePlanControlGroup OBJECT-GROUP 988 OBJECTS { 989 tonePlanCurrentSize 990 } 991 STATUS current 992 DESCRIPTION 993 "This group contains objects related to control of 994 VISM Tone Plan Table. 995 " 996 ::= { vismTonePlanMIBGroups 1 } 997 998 999vismTonePlanTableGroup OBJECT-GROUP 1000 OBJECTS { 1001 tonePlanEntryStatus, 1002 tonePlanProvisionFlag, 1003 tonePlanRegionName, 1004 tonePlanVersionNumber, 1005 tonePlanFileName 1006 } 1007 STATUS current 1008 DESCRIPTION 1009 "This group contains objects related to configuration 1010 of VISM Tone Plan. 1011 " 1012 ::= { vismTonePlanMIBGroups 2 } 1013 1014vismConfigToneDetectTableGroup OBJECT-GROUP 1015 OBJECTS { 1016 vismConfigToneDetectNum, 1017 vismEventCode , 1018 vismConfigToneDetectRowStatus, 1019 vismFreqMaxDeviation, 1020 vismFreqMaxPower, 1021 vismFreqMinPower, 1022 vismFreqPowerTwist, 1023 vismFreqMaxDelay, 1024 vismMinOnCadence, 1025 vismMaxOffCadence, 1026 vismFreqNumOfCadenceMatch, 1027 vismFrequency1, 1028 vismFrequency2, 1029 vismFreqOnCadence, 1030 vismFreqOffCadence 1031 } 1032 STATUS current 1033 DESCRIPTION 1034 "This group contains objects related to configuration 1035 of VISM dual frequency detect tones. 1036 " 1037 ::= { vismTonePlanMIBGroups 3 } 1038 1039vismSequentialToneDetectGroup OBJECT-GROUP 1040 OBJECTS { 1041 seqToneNumOfFrequencies, 1042 seqToneEventID, 1043 seqToneDurationOfEachTone, 1044 seqToneGapBetweenEachTone, 1045 seqToneDurationDeviation, 1046 seqToneMaximumGapDuration, 1047 seqToneGapDurationDeviation, 1048 seqToneFreqDeviation, 1049 seqTonePowerLevelCeiling, 1050 seqTonePowerLevelFloor, 1051 seqToneFrequency1, 1052 seqToneFrequency2, 1053 seqToneFrequency3, 1054 seqToneFrequency4, 1055 seqToneFrequency5, 1056 seqToneFrequency6, 1057 seqToneFrequency7, 1058 seqToneFrequency8, 1059 seqToneFrequency9, 1060 seqToneFrequency10 1061 } 1062 STATUS current 1063 DESCRIPTION 1064 "This group contains objects related to configuration 1065 of VISM sequential single frequency tone detection. 1066 " 1067 ::= { vismTonePlanMIBGroups 4 } 1068 1069 1070 1071END 1072