| bearerEndptNum |
.1.3.6.1.4.1.351.110.5.5.9.1.1.1 |
|
This attribute defines the index for the Bearer
Connection Table. This refers to the same value
as the index to the mgEndpointTable ie. mgEndpointNumber.
This is define in CISCO-WAN-MG-MIB MIB.
|
| bearerCid |
.1.3.6.1.4.1.351.110.5.5.9.1.1.2 |
|
This attribute defines the CID associated with this
bearer connection. This refers to the same value as
vismAal2CidNum in the vismAal2CidCnfTable.
|
| bearerLcn |
.1.3.6.1.4.1.351.110.5.5.9.1.1.3 |
|
This attribute defines the PVC or LCN(Logical Channel Number)
number to which this bearer connection is associated with.
This refers to the same value as in vismCnfChanNum in
vismChanCnfGrp table. This is define in CISCO-VISM-CONN-MIB
MIB.
|
| bearerSentPkts |
.1.3.6.1.4.1.351.110.5.5.9.1.1.4 |
|
This attribute defines the count of packets sent towards the
network since this connection setup.
|
| bearerRcvdPkts |
.1.3.6.1.4.1.351.110.5.5.9.1.1.5 |
|
This attribute defines the count of packets received from the
network since this connection setup.
|
| bearerSentOctets |
.1.3.6.1.4.1.351.110.5.5.9.1.1.6 |
|
This attribute defines the count of bytes sent towards the
network since this connection setup.
|
| bearerRcvdOctets |
.1.3.6.1.4.1.351.110.5.5.9.1.1.7 |
|
This attribute defines the count of bytes received from the
network since this connection setup.
|
| bearerLostPkts |
.1.3.6.1.4.1.351.110.5.5.9.1.1.8 |
|
This attribute defines the count of packets lost in the
egress direction (from the network). This is a computed
number based on the expected number of packets and the
actual number of packets arrived from the network.
|
| bearerJitter |
.1.3.6.1.4.1.351.110.5.5.9.1.1.9 |
|
This attribute defines the jitter (a.k.a interarrival jitter)
This value is determined by the DSP(Digital Signal
Processing) and obtained by the HOST processor
upon querying the DSP on a periodic basis.
|
| bearerLatency |
.1.3.6.1.4.1.351.110.5.5.9.1.1.10 |
|
This attribute defines the latency (a.k.a end-to-end average
transmission delay for a voice packet).
|
| bearerAal2ExtAISCnts |
.1.3.6.1.4.1.351.110.5.5.9.1.1.11 |
|
This object contains the number of external AIS
(Alarm Indication Signal) AAL2 Type3 packets received.
External AIS - is associated with a maintenance alarm
detected on a defective maintenance span, that is
transmitted in the direction of the defect as a substitute
for normal signal. The purpose is to show the downstream
entities that a defect has been identified and to prevent
other maintenance alrams consequent to this first defect.
External AIS bit stream is represented by an all 1's
signal.
|
| bearerAal2ExtRAICnts |
.1.3.6.1.4.1.351.110.5.5.9.1.1.12 |
|
This object contains the number of external RAI
(Remote Alarm Indication) AAL2 Type3 packets received.
External RAI - is a signal that is transmitted
upstream from an entity that has detected defects
persisting long enough to constitute a received
signal failure. Its purpose is to report in the backward
direction that there is an interruption of service in the
forward direction.
|
| bearerAal2ConnAISCnts |
.1.3.6.1.4.1.351.110.5.5.9.1.1.13 |
|
This object contains the number of external Conn
AIS AAL2 Type2 packets received.
External Conn AIS - is transmitted in the downstream
direction from the AAL Type 2 connecting point that first
detects a defect affecting the AAL Type 2 connection;
this includes defects indicated by lower layers.
|
| bearerAal2ConnRDICnts |
.1.3.6.1.4.1.351.110.5.5.9.1.1.14 |
|
This object contains the number of external Conn
RDI(Remote Defect Indication) AAL2 Type2 packets
received.
External Conn RDI - is a signal transmitted upstream
by an AAL Type 2 endpoint that is in an alarm state as
the result of having received an AAL Type2 connection
AIS or having detected a defect that affects
the AAL Type2 connection.
|
| bearerCntClrButton |
.1.3.6.1.4.1.351.110.5.5.9.1.1.15 |
|
This object is used to clear bearerSentPkts, bearerRcvdPkts,
bearerSentOctets, and bearerRcvdOctets.
|
| bearerPeakXmtCellRate |
.1.3.6.1.4.1.351.110.5.5.9.1.1.16 |
|
Peak transmit ATM cell rate is the ATM cells
required to transmit peak AAL2 packets on a
CID per second since midnight as per system time;
the peak cell rate gets cleared every 24 hours
at midnight as per system time.
|
| bearerCurrentXmtCellRate |
.1.3.6.1.4.1.351.110.5.5.9.1.1.17 |
|
Current transmit ATM cell rate is the ATM cells
required to transmit current AAL2 packets on a
CID per second.
|
| bearerPeakRcvCellRate |
.1.3.6.1.4.1.351.110.5.5.9.1.1.18 |
|
Peak receive ATM cell rate is the ATM cells
required to receive peak AAL2 packets on a
CID per second since midnight as per system time;
the peak cell rate gets cleared every 24 hours
at midnight as per system time.
|
| bearerCurrentRcvCellRate |
.1.3.6.1.4.1.351.110.5.5.9.1.1.19 |
|
Current receive ATM cell rate is the ATM cells
required to receive current AAL2 packets on a
CID per second.
|
| bearerCurrentExtAISRcvCnts |
.1.3.6.1.4.1.351.110.5.5.9.1.1.20 |
|
This object contains the count of external
AIS AAL2 (Type 2) received on this
bearerEndptNum since its creation.
|
| bearerCurrentExtRAIRcvCnts |
.1.3.6.1.4.1.351.110.5.5.9.1.1.21 |
|
This object contains the number of external
RAI AAL2 (Type 2) received in this bearerEndptNum
since its creation.
|
| bearerCurrentConnAISCnts |
.1.3.6.1.4.1.351.110.5.5.9.1.1.22 |
|
This object contains count of external Connection
AIS AAL2 (Type 2) received in this bearerEndptNum
since its creation.
|
| bearerCurrentConnRDICnts |
.1.3.6.1.4.1.351.110.5.5.9.1.1.23 |
|
This object contains the count of external Connection
RDI (Remote Defect Indication) AAL2 (Type 2) received
in this bearerEndptNum since its creation.
|
| bearerCurrentExtAISXmtCnts |
.1.3.6.1.4.1.351.110.5.5.9.1.1.24 |
|
This object contains the count of external AIS
AAL2 (Type 2) transmitted in this bearerEndptNum
since its creation.
|
| bearerCurrentExtRAIXmtCnts |
.1.3.6.1.4.1.351.110.5.5.9.1.1.25 |
|
This object contains the count of external
RAI AAL2 (Type 2) transmitted in this bearerEndptNum
since its creation.
|
| vismAal2CidLcn |
.1.3.6.1.4.1.351.110.5.5.3.4.1.1.2 |
|
This attribute defines part of the index for the
vismAal2CidCnfTable. Since CID is unique to a PVC,
a combination of LCN and CID uniquely identifies
a voice connection. This field refers to
vismCnfChanNum defined in vismChanCnfGrp of
CISCO-VISM-CONN-MIB MIB.
|
| vismAal2CidNum |
.1.3.6.1.4.1.351.110.5.5.3.4.1.1.1 |
|
This attribute defines part of the index for this table.
vismAal2CidNum is the CID of a voice channel. CID has to be
the same at both endpoints for a connection. CID is
unique only within the context of a Virtual
Circuit (PVC or SVC).
|
| vismAal2EndptNum |
.1.3.6.1.4.1.351.110.5.5.3.4.1.1.3 |
|
This attribute defines the endpoint number to which this
CID is associated. It is the same as mgEndpointNumber
defined in mgEndpointTable of CISCO-WAN-MG-MIB MIB.
|
| vismAal2CidRowStatus |
.1.3.6.1.4.1.351.110.5.5.3.4.1.1.4 |
|
This variable allows to add or delete a CID. A CID can
only be added or deleted. Once added, modifying an
entry is not allowed.
'createAndGo': Use this to add an entry in this table.
'active': This values is returned, once the row is created.
'destroy': Use this to delete an entry from this table.
|
| vismAal2CidType3Redundancy |
.1.3.6.1.4.1.351.110.5.5.3.4.1.1.5 |
|
This attribute defines whether the triple redundancy is
supported for type 3 packets in AAL2 for this channel.
When Triple redundancy is enabled for a channel, the
Type 3 packets (CAS bits, dialled digits and user state
control packets) are transmitted in triplicates with an
interval defined as per the standards I.366.2. For
channels which are quite reliable, triple redundancy
can be disabled in order to save the bandwidth and the
processing overheads.
The default value of this object is 'true(1)' if either
vismAal2CidCasTransport or vismAal2CidDtmfTransport is
'true(1)', otherwise the default value is 'false(2)'.
|
| vismAal2CidVad |
.1.3.6.1.4.1.351.110.5.5.3.4.1.1.6 |
|
This attribute defines whether the VAD (Voice Activity
Detection) has to be applied on this channel, upon
detection of silence. For algorithms that do not
have VAD standards, Cisco-proprietary VAD can be
applied and the generic SID(Silence Information
Descriptor) packet as specified in I.366.2 standards
can be sent to the other end.
When the codec specify in vismAal2CidCodecType is
'clearChannel' VAD has to be off.
|
| vismAal2CidProfileType |
.1.3.6.1.4.1.351.110.5.5.3.4.1.1.7 |
|
This attribute defines the profile type. The profile
type defines which group of the profile tables the
profile number should correspond to. There are three
possible groups:
'itu' - corresponding to the tables in ITU
format in the profile is being used.
'atm' - This is not supported
'custom' - VISM specific custom profiles.
|
| vismAal2CidProfileNum |
.1.3.6.1.4.1.351.110.5.5.3.4.1.1.8 |
|
This attribute defines the profile number. A profile
is a set of entries, where each entry specifies an
encoding format with a UUI(User-to-User Indication)
range and length. This set defines a mapping that
informs the receiver of a Type 1 packet how to
interpret the packet contents, i.e. which encoding
format in the profile is being used.
|
| vismAal2CidCodecType |
.1.3.6.1.4.1.351.110.5.5.3.4.1.1.9 |
|
This attribute defines the codec Type used for the
connection.
'g711u' represents PCMU with 64 kbps.
'g711a' represents PCMA with 64 kbps.
'g726r32000' represents G.726 at rate 32 kbps
'g726r16000' represents G.726 at rate 16 kbps
'g726r24000' represents G.726 at rate 24 kbps
'g726r40000' represents G.726 at rate 40 kbps
'g729a' represents G.729 Annex A algorithm.
'g729ab' represents G.729 Annex A and Annex B algorithm.
'clearChannel' represents CCD with 64 kbps.
'g723h' represents G.723.1-H at rate 6.3kbps.
'g723ah' represents G.723.1-H at rate 6.3kbps
with Silence Supression ON.
'g723l' represents G.723.1-L at rate 5.3kbps.
'g723al' represents G.723.1-L at rate 5.3kbps
with Silence Supression ON.
'lossless' represents Lossless
Note :
1. When codec type is 'clearChannel', vismAal2CidProfileType
and vismAal2CidProfileNum are not applicable and
will be ignored.
2. Value 10 is RESERVED.
|
| vismAal2CidDtmfTransport |
.1.3.6.1.4.1.351.110.5.5.3.4.1.1.10 |
|
This attribute defines whether the DTMF (Dual Tone Multi
Frequency) digits need to be transported to the other
end-point.
|
| vismAal2CidCasTransport |
.1.3.6.1.4.1.351.110.5.5.3.4.1.1.11 |
|
This attribute defines whether the CAS(Channel
Associated Signaling) bits need to be transported
to the other endpoint. In the case of switching
application, the CAS bits are backhauled to the call agent
through xGCP(Gateway Control Protocol)-CAS protocol.
Note that if the line signaling type is CAS the
default value is 'true(1)', else the default value
is 'false(2)'.
|
| vismAal2CidEcanEnable |
.1.3.6.1.4.1.351.110.5.5.3.4.1.1.12 |
|
This attribute defines whether Echo Cancellation has to
be enabled on this connection. If it is set to 'true(1)',
echo cancellation is enabled. If it is set to 'false(2)',
echo cancellation is disabled.
|
| vismAal2InitVadTimer |
.1.3.6.1.4.1.351.110.5.5.3.4.1.1.13 |
|
This attribute defines the hangover time for VAD.
Once the voice inactivity is detected, the gateway
will wait for this duration before activating
silence suppression.
|
| vismAal2CnfPktPeriod |
.1.3.6.1.4.1.351.110.5.5.3.4.1.1.14 |
|
This object is used to configure the packetization
period for a given codec. This packetization period
has to be a valid entry in the profile table. Profile
type and number identify a unique profile table and one codec
type in this table might have one or more packetization
period. This is applicable only if the vismAal2CidCodecType
is 'g729a'.
The configurable values for 'g729a' are 10,20,30 & 40.
If a CID entry is configured with a codec other than
'g729a' then the user cannot configure the pkt period
for that codec and the pkt period is picked from the
profile table.
Hence when we do get/walk on this entry/table any one of
the above values could be returned.
|
| vismAal2CidICSEnable |
.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.
|
| vismAal2CidState |
.1.3.6.1.4.1.351.110.5.5.3.4.1.1.16 |
|
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.
|
| vismAal2CidFailReason |
.1.3.6.1.4.1.351.110.5.5.3.4.1.1.17 |
|
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
|
| vismAal2CidAdminState |
.1.3.6.1.4.1.351.110.5.5.3.4.1.1.18 |
|
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.
|
