vism Aal2 Cid ICS Enable

1.3.6.1.4.1.351.110.5.5.3.4.1.1.15

This object is used to enable or disable the ICS(Idle Channel Suppression) for a CID. This can be specified while adding the CID and cannot be modified. When the Idle Channel Suppression is enabled the DSP will look for the idle CAS (ABCD bits) pattern specified in ds0IdleCode in CISCO-VISM-DSX0-MIB MIB. If the idle pattern is present the DSP stops generating voice packets towards ATM side. By default the ds0IdleCode will be zero unless the user has configured it before adding the CID. If the ds0IdleCode is changed after the CID is added it will have no affect unless the card is reset. ICS is applicable only for trunking application, in case of switching there is no need for ICS as the calls are teared down and set up dynamically. DEFVAL { false } ::= { vismAal2CidEntry 15 } SYNTAX INTEGER { cidStateActive (1), cidStateFailed (2) } MAX-ACCESS read-only STATUS current DESCRIPTION Indicates the state of the CID. 'cidStateActive' : The CID is in service and operational. 'cidStateFailed' : The CID is in service but not operational, e.g. because the PVC that the CID belongs to is receiving F5(Operation, Administration and Maintenance Flow) level alarm. When VISM sees alarm on a CID (network side) sets this object to 'cidStateFailed', and an AIS will be sent on the ds0(Time Division Multiplexed voice channel) that this CID corresponds to. If the whole PVC is in alarm then all the CIDs on that PVC will be set to 'cidStateFailed', trapVismChanFailed trap will be sent and all the ds0's that corresponds to each of the CIDs on this PVC will be in alarm. If VISM sees an alarm on a ds0 in a line then an RAI(Remote Alarm Indication) will be sent on the CID that corresponds to this ds0, however the CID will not be put in failed state. ::= { vismAal2CidEntry 16 } SYNTAX INTEGER { self (1), highLevel (2), both (3), notFail (4) } MAX-ACCESS read-only STATUS current DESCRIPTION This object is used to indicate the CID failure reason. 'self': fail because of non-PVC alarm 'highLevel': fail because of PVC alarm 'both': fail because of both PVC and non-PVC alarm 'notFail': not fail DEFVAL { notFail } ::= { vismAal2CidEntry 17 } SYNTAX INTEGER { cidPendingInService (1), cidInService (2), cidCommandedOutOfService (3), cidPendingOutOfService (4), cidUnknownState (5) } MAX-ACCESS read-write STATUS current DESCRIPTION This attribute defines the operational administrative state of the bearer connection. cidInService: This is an operational state of the bearer connection where it is ready to transmit/receive data/voice packets. The user can take the bearer connection into cidInService. cidCommandedOutOfService: This is an operational state of the bearer connection where it is not ready to transmit/receive data/voice packets. The user can take the bearer connection into cidPendingOutOfService. cidPendingInService: It is a transient state. In this state the bearer connection is waiting for the user to transition it to the cidInService state. This value cannot be specified in a management protocol set operation. cidPendingOutOfService: It is a transient state. In this state the bearer connection is waiting for the user to transition it to the cidOutOfService state. This value cannot be specified in a management protocol set operation. cidUnknownState: This is an abnormal state of the bearer connection. This state would indicate to the user that there is some data integrity issue on the bearer administrative state. DEFVAL { cidPendingInService } ::= { vismAal2CidEntry 18 } -- conformance information cvismAtmTrunkMIBConformance OBJECT IDENTIFIER ::= { ciscoVismAtmTrunkMIB 2 } cvismAtmTrunkMIBGroups OBJECT IDENTIFIER ::= { cvismAtmTrunkMIBConformance 1 } cvismAtmTrunkMIBCompliances OBJECT IDENTIFIER ::= { cvismAtmTrunkMIBConformance 2 } -- compliance statements cvismAtmTrunkCompliance MODULE-COMPLIANCE STATUS deprecated DESCRIPTION The compliance statement for objects related to VISM Bearer and CID Connection.