MgcRedundancyGrpEntry |
|
SEQUENCE |
|
|
|
|
mgcRedundancyGrpNum |
Integer32 |
|
|
mgcRedundancyGrpPref |
Integer32 |
|
|
mgcRedundancyGrpActState |
INTEGER |
|
|
mgcRedundancyGrpRowStatus |
RowStatus |
|
MgcRedundancyGrpParamEntry |
|
SEQUENCE |
|
|
|
|
mgcRedundancyGrpStateChangeNtfy |
TruthValue |
|
|
mgcRedundancyGrpCommState |
INTEGER |
|
|
mgcRedundancyGrpPriority |
Integer32 |
|
MgcRedundancyGrpProtocolEntry |
|
SEQUENCE |
|
|
|
|
mgcRedundancyGrpProtocolRowStatus |
RowStatus |
|
|
mgcRedGrpProtPersistEvtPolicy |
INTEGER |
|
|
mgcRedGrpProtQuarantinePolicy |
INTEGER |
|
|
mgcRedGrpProtSigEvtOnOffPolicy |
INTEGER |
|
|
mgcRedGrpProtProvisionalResponse |
INTEGER |
|
|
mgcRedGrpProtResponseAckAttr |
INTEGER |
|
|
mgcRedGrpProtDisconnectProcedure |
INTEGER |
|
|
mgcRedGrpProtCancelGraceful |
INTEGER |
|
mgcRedundancyGrpEntry |
1.3.6.1.4.1.351.150.22.1.1.1 |
Each row in the table is identified by an
mgcRedundancyGrpNum and mgcNumber. Before adding an
entry into this table the MGC has to be added in
mgcTable defined in CISCO-WAN-MG-MIB.
A single mgcRedundancyGrp can have multiple MGCs. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
MgcRedundancyGrpEntry |
|
|
mgcRedundancyGrpParamEntry |
1.3.6.1.4.1.351.150.22.1.2.1 |
Represents an individual entry in the
mgcRedundancyGrpParamTable. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
MgcRedundancyGrpParamEntry |
|
|
mgcRedundancyGrpProtocolEntry |
1.3.6.1.4.1.351.150.22.1.3.1 |
Represents an individual table entry in
mgcRedundancyGrpProtocolTable.
When active, it is expected that mgcRedundancyGrpNum and
mgProtocolNumber contain valid values that maintain
referential integrity into mgcRedundancyGrpTable and
mgSupportedProtocolTable respectively. The attempt to
create a row that would violate referential integrity
shall be rejected. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
MgcRedundancyGrpProtocolEntry |
|
|
mgcRedGrpProtPersistEvtPolicy |
1.3.6.1.4.1.351.150.22.1.3.1.2 |
This object determines how the persistent events
will be notified.
Persistent events are events that call
agent wants to be notified without explicitly
requesting for it. A set of events can be
provisioned on the Gateway as persistent
events.
Every event will have an action associated
with it, which will determine, whether to
be notified, ignored, accumulated etc..
MGC will specify the action when
requesting the GW to notify the event.
For persistent events the Action will be
Notify. Call agent can change this by
explicitly requesting the event associating
an action with it.
During the period where the Gateway has
received a notification acknowledgement,
and waiting for the next Request Notification,
events could be observed. The Quarantine
procedure determines what should be done with
these events.
This object is used to supercede the quarantine
procedure, by enforcing loop, process as the
quarantine procedure only for persistent events.
During the period the Gateway has sent a
Notification, and waiting for the acknowledgement
all events including the persistent events will
'quarantinePersistEvts' - Quarantine Persistent
events as in the case of non persistent
events as determined by quarantine method.
'notQuarantinePersistEvts' - Don't quarantine
Persistent events, and notify them.
During the period the Gateway has sent a Notify
and waiting for the acknowledgement, every
event including persistent event will be
quarantined. This value does not supercede
that behaviour. This applies only during
the period, where a Notify is acknowledged
and waiting for the next RQNT where the
quarantine method is 'step,process' or
'step,discard'.
This object has no relevance when the protocol
is SRCP. |
Status: current |
Access: read-create |
OBJECT-TYPE |
|
|
|
|
INTEGER |
quarantinePersistEvts(1), notQuarantinePersistEvts(2) |
|
mgcRedGrpProtQuarantinePolicy |
1.3.6.1.4.1.351.150.22.1.3.1.3 |
This object determines the quarantine policy
when MGC doesn't explicitly specify
one.
When a Request Notification is received
from the MGC, the Gateway on observing
the first event that qualifies to be notified
will generate a Notify message with the list
of observed events including the event which
triggered the Notify.
After the MGC acknowledges the Notify,
if further events are observed and an event
which qualifies to be notified, the Gateway
may notify the event, or quarantine it until
the next Request Notification, based on the
quarantine policy set by the MGC.
When the MGC doesn't explicitly
specify the quarantine policy, the protocol
defines the default behaviour. The default
behaviour varies with different versions of
the protocol.
This object allows the user to configure
the default quarantine policy per protocol
per redundancy group. The default value
for this object will be set based on the
protocol.
'stepProcess' - Process the events in the
quarantine list, and after one Notify
quarantine events until next Request
Notification
'stepDiscard' - Discard the events in the
quarantine list, and after one Notify
quarantine events until next Request
Notification
'loopProcess' - Process the events in the
quarantine list, and notify observed
events as and when need arises
'loopDiscard' - Discard the events in the
quarantine list, and notify observed
events as and when need arises
The default value for MGCP 1.0 will be
stepProcess and stepDiscard for the rest.
This object has no relevance when the protocol
is SRCP. |
Status: current |
Access: read-create |
OBJECT-TYPE |
|
|
|
|
INTEGER |
stepProcess(1), stepDiscard(2), loopProcess(3), loopDiscard(4) |
|
mgcRedGrpProtSigEvtOnOffPolicy |
1.3.6.1.4.1.351.150.22.1.3.1.4 |
This object enables the user to provision the
way signaled events from CA are handled
by the gateway. This is configurable on
a per MGC redundancy group, per protocol basis.
If the protocol is MGCP 1.0 the default of this
object is 'deleteOnlyNegatedEvent', else it is set
to 'deleteEventNotPresent'.
If this object is set to 'deleteOnlyNegatedEvent',
then the signal currently active on a
endpoint/connection can be turned OFF only by
parameterizing it with a (-)
for eg: S: T/co1(-)
will turn off co1 event on an endpoint.
And can be turned ON by just
providing the signal name or by parameterizing
the signal name with a (+)
for eg: S:T/co1(+), L/hd
will turn on co1 and hd events on the endpoint.
If this object is set to 'deleteEventNotPresent',
then the signal/s can be turned OFF by
providing empty S: list.
The signal can be turned ON by simply
providing the signal name.
for eg: S:
will turn OFF all active signals on the endpoint
S: T/co1
will turn ON co1 signal.
The configuration of this object only applies to
on/off signals and not for brief or timeout signals.
MGCP 0.1 specification says if an empty signaled
list is provided it is meant to turn off all the
currently turned on signaled events. However
in MGCP 1.0 specification, it says that unless
specifically requested by the CA to turn off
(signal is parameterized by a (-)) the signal
cannot be turned off, in other words an
empty signal list does imply that the currently
active signals should be turned off.
Although the behavior of the gateway is
specified in the specs, some MGC
may not follow the MGCP 1.0 spec. Hence
this MIB serves as an interop knob.
This object has no relevance when the protocol
is SRCP. |
Status: current |
Access: read-create |
OBJECT-TYPE |
|
|
|
|
INTEGER |
deleteEventNotPresent(1), deleteOnlyNegatedEvent(2) |
|
mgcRedGrpProtProvisionalResponse |
1.3.6.1.4.1.351.150.22.1.3.1.5 |
This object enables or disables sending provisional
response to the CA when processing a request received
from the CA. The provisional response to the CA
indicates that the GW is processing the request and
will send a final response once the processing is
complete.
For example, if a CRCX request from the CA using MGCP
protocol, requires that resources be reserved along the
bearer path using RSVP, GW would send a provisional
response if this parameter was set to true. It would
then wait for the RSVP procedure to complete before
sending the final response. On the other hand, if the
value of this parameter was set to false, the final
response will be sent out without waiting for the
RSVP procedure to complete. When the RSVP procedure
does complete, a NTFY will be sent from the GW
indicating if the RSVP procedure was successful or not.
The GW will receive provisional responses from the CA.
These messages will be parsed and ignored regardless
of this object.
If the protocol supported by the CA is MGCP1.0, the
default value for this object is 'sendProvisionalResponse'.
In all other cases, it is 'notSendProvisionalResponse'.
This object has no relevance when the protocol
is SRCP. |
Status: current |
Access: read-create |
OBJECT-TYPE |
|
|
|
|
INTEGER |
sendProvisionalResponse(1), notSendProvisionalResponse(2) |
|