CISCO-MEGACO-EXT-MIB

CMgcGroupIndexA unique value, greater than zero which is used to identify index of MGC group. (1..12) · Integer32 · hint d

This object specifies the MGC group parameters associated with MGC group index. Those parameters are for the communication between this media gateway and the MGCs in the group. The value of this object is the same as cMgcGrpIndex of cMgcGrpParamTable.

Unsigned32 (1..64)

This object specifies the media gateway IP address. It is the index of the entry in cMediaGwIpConfigTable which defines the media gateway address over control type PVC.

Unsigned32 (1..65535)

This object indicates the unique identification of the H.248 association assigned by the H.248 Stack.

Unsigned32 (1..4294967295)

Maximum number of contexts is allowed in this media gateway link.

Unsigned32 (1..100)

Maximum number of terminations per context in this media gateway link.

Unsigned32 (0..65535) · milliseconds

This object specifies the interval within which the MGC expects a response to any transaction from the MG (exclusive of network delay specified by the object cmedxGatewayInitialRtt). ⓘ

Unsigned32 (0..65535) · milliseconds

This object specifies the interval within which the MG should expects a response to any transaction from the MGC (exclusive of network delay specified by the object cmedxGatewayInitalRtt). ⓘ

Unsigned32 (0..65535) · milliseconds

This object specifies the time within which to expect a Pending Response if a transaction cannot be completed in the media gateway and in the MGCs of the media gateway link. The value of this object should be less than the value of cmedxGatewayMgExecTime and the value of cmedxGatewayMgcExecTime. This object is depricated due to the object name, default value and description are wrong. This object is replaced by 'cmedxGatewayMgProvisionRspTime'.

Unsigned32 (0..100) · times

The number of times the media gateway retries to connect to MGC before it sends out disconnect command.

Unsigned32 (0..600000) · milliseconds

When a media gateway is powered on, it should initiate a restart timer to a random value, uniformly distributed between 0 and the value specified in this object (the maximum waiting delay, MWD). After restart timer timeout, the media gateway can initiate the ServiceChange transaction. This is a way to prevent the MGC is swamped by many gateways powered up at the same time.

Unsigned32 (0..600) · milliseconds

This object specifies The time delay before the media gateway accept any call from MGC after it sends the command 'ServiceChange' with a 'Restart'.

Unsigned32 (0..65535) · seconds

This object specifies the time till which the responses should be retained before they are sent if they receive a repetition of a transaction that is still being executed.

Unsigned32 (0..65535) · milliseconds

Initial round-trip time for the H.248 transaction to be responded. It reflects the network delay time.

Unsigned32 (0..65535) · 10 milliseconds

This object specifies the the period of silence between messages from MGC. If the period of silence exceeds the value of this object, then a Notify command with inactive MGC event is generated from the media gateway. The value of 0 is to disable the inactivity detection on the media gateway. ⓘ

InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address. unknown(0) An unknown address type. This value MUST be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below. ipv4(1) An IPv4 address as defined by the InetAddressIPv4 textual convention. ipv6(2) An IPv6 address as defined by the InetAddressIPv6 textual convention. ipv4z(3) A non-global IPv4 address including a zone index as defined by the InetAddressIPv4z textual convention. ipv6z(4) A non-global IPv6 address including a zone index as defined by the InetAddressIPv6z textual convention. dns(16) A DNS domain name as defined by the InetAddressDNS textual convention. Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType. To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation. Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32

The address type in the H.248 message header.

Integer32 (-1..65535) · milliseconds

This object specifies the grace period before the media gateway link to be taken out of service. The value of 0 means to take the media gateway link out of service forcefully without any delay. The value of -1 means not to take the media gateway link out of service until all currently active contexts have been cleared.

InetAddressDenotes a generic Internet address. An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row. The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error. When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING

The address of the currently active MGC in this media gateway link.

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..64) · OCTET STRING · hint 255t

The domain name of the currently active MGC in this media gateway link.

CiscoPortThe TCP or UDP port number range.Reference: Transmission Control Protocol. J. Postel. RFC793, User Datagram Protocol. J. Postel. RFC768 (0..65535) · Integer32

The transport layer port number of the currently active MGC in this media gateway link.

INTEGER1 = mgcDirected2 = mgDirected3 = mgcNotReachable4 = numRetriesExpired · Integer32

This object indicates the reason for the operational state change (cmedGatewayOperStatus) in the media gateway link. mgcDirected (1) - The state change is directed from MGC. mgDirected (2) - The state change is directed from MG. mgcNotReachable (3) - The transport address of MGC is not reachable. numRetriesExpired (4) - The number of retires for connecting MGC has exhausted (cmedxGatewayNumConnRetries).

INTEGER1 = other2 = graceful3 = forced4 = handoff5 = failover6 = restart7 = disconnect8 = cancelGraceful · Integer32

This object indicates the method for the operational state change (cmedGatewayOperStatus) in the media gateway link. other (1) - None of the methods listed below. graceful (2) - The state change to 'down(2)' is by the way of graceful out of service. forced (3) - The state change to 'down(2)' is by the way of forced out of service. handoff (4) - The state change is by the way that the MGC hands off to another MGC. failover (5) - The state change is by the way that MG reconnects to current MGC because of the failure of previous MGC. restart (6) - The state change is by the way that MG or MGC restarts. disconnect (7) - The state change is by the way that MG brings down the service because of the MG port has been modified, the number of retries has exhausted, or the inactivity timer has expired. cancelGraceful (8) - After issuing graceful out of service with a delay (cmedxGatewayDownServiceDelay>0), MG then sends an in-service command before the delay has been expired.

INTEGER1 = up2 = downForceful3 = downGraceful4 = cancelGraceful · Integer32

This object specifies the action that users used to change the service state of the media gateway link. This object can be modified while the entry is active. up (1) - Bring the service state up. The value of cmedxGatewayDownServiceDelay will be ignored. downForceful (2) - Bring the service state down without any delay. All current active calls will be torn down forcefully. The value of cmedxGatewayDownServiceDelay must be 0. downGraceful (3) - Bring the service state down but wait until currently active calls are terminated by users. The value of cmedxGatewayDownServiceDelay must be greater than 0. cancelGraceful(4) - While waiting for all currently active calls to be terminated by users during the downGraceful action, this value can be used to cancel the previous action 'downGraceful(3)'. The value of cmedxGatewayDownServiceDelay will be ignored.

INTEGER1 = inService2 = pendingIs3 = outOfService4 = pendingFoos5 = pendingGoos6 = mgcDirectOos · Integer32

This object indicates current operation status of the media gateway link. inService (1) - The media gateway link is in-service. pendingIs (2) - The media gateway link is in the process of establishing the service between MG and MGC. outOfService (3) - The service of the media gateway link is completely down due to the action of setting cmedxGAtewayAdminAction to 'downForceful(2)' or to 'downGraceful(3)'. pendingFoos (4) - The media gateway link is in the process of bringing down the service in response to the action of setting object cmedxGAtewayAdminAction to 'downForceful(2)'. pendingGoos (5) - The media gateway link is in the process of bringing down the service in response to the action of setting object cmedxGAtewayAdminAction to 'downGraceful(3)'. mgcDirectOos (6) - The media gateway link is out-of-service due to MGC disable the link. This state should occur very rarely, the way to recover from this state is to set cmedxGAtewayAdminAction to 'up(1)' or 'downForceful(2)'

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object specifies the TPKT header version that is dynamically assigned based on the size of the packet presented to TCP layer. The TPKT header version is set to 3 when the size of packet is represented by 2 octets of packet length field for the message (TPDU) sizes less than or equal to 65531 octets. If this object is set to 'true': - The TPKT header version is set to 4 when the size of packet is represented by 4 octets of packet length field for the message (TPDU) sizes greater than 65531 octets. If this object is set to 'false': - An error in message is sent to MGC if the TPDU size exceeds 65531 octets indicating that response size exceeded maximum PDU size. ⓘ

Unsigned32 (1..4096) · Kbyte

This object specifies the maximum message size on this gateway link for a H248 transaction containing the media gateway initiated commands. For example, this object would limit the size of a H248 transaction containing the media gateway initiated ServiceChange command message. The value of the object cannot be modified if the entry is active.

Unsigned32 (1..4096) · Kbyte

This object specifies the maximum message size on this gateway link for a H248 transaction containing the media gateway reply messages to MGC. For example, this object would limit the size of a H248 transaction containing the media gateway reply message to the MGC initiated AuditValue command. The value of the object cannot be modified if the entry is active.

Unsigned32 (0..255)

This object specifies the SCTP association ID associated with the H.248 association. This SCTP association ID is the index (cSctpAssocId) of the entry in cSctpAssocTable. If the SCTP ID value is 0, it indicates no SCTP association.

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (1..16) · OCTET STRING · hint 255t

This object specifies the profile name used in the profile parameter of ServiceChange message to specify the attributes and behaviors of the media gateway.

Unsigned32 (1..99)

This object specifies the version of the profile indicated in cmedxGatewaySrvChgProfile.

INTEGER1 = shortFormat2 = longFormat · Integer32

This object specifies the H248 message is in short formatted PDU or long formatted PDU. ⓘ

Unsigned32 (0..65535) · milliseconds

This object specifies the time within which to expect a Pending Response if a transaction cannot be completed in the media gateway and in the MGCs of the media gateway link. The value of this object should be greater than the value of cmedxGatewayMgExecTime. ⓘ

Unsigned32 (0..65535) · milliseconds

This object specifies the time within which to expect a Pending Response from the MGC if a transaction cannot be completed. The value of this object should be greater than the value of cmedxGatewayMgcExecTime. ⓘ

Unsigned32 (0..65535)

This object specifies the number of TransactionPendings that MG will send. Once this limit is exceeded, MG will send a TransactionReply with Error 506. ⓘ

Unsigned32 (0..65535)

This object specifies the number of TransactionPendings that MG expects to receive. Once this limit is exceeded, MG will assume a TransactionReply with Error 506. ⓘ

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t

This object specifies the unique domain name to be used for each gateway link. This object is relevant only if cmedxGatewayHeaderAddrType is set to 'dns'. The agent won't allow any attempt to set this value for other address types. This domain name is expected to be resolved to a valid IP address through the use of a DNS located in the network. The default value of this object is NULL string.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object specifies whether the MID should be a combination of the transport port number and the domain name represented by cmedGatewayPort and cmedxGatewayDomainName respectively, when cmedxGatewayHeaderAddrType is 'dns' . A value of 'true' indicates that the MID will be a combination of the domain name and the transport port number. A value of 'false' indicates that MID will contain only the domain name and not the port number. The agent won't allow any attempt to set this object for other address types. ⓘ

Unsigned32 (1..65535)

An unique identification number that is assigned to the termination type by the manager

INTEGER1 = unknown2 = scn3 = pdnRtp4 = pdnAtmAal15 = pdnAtmAal2 · Integer32

This object specifies the type of a group of ephemeral terminations. unknown (1) - none of the types listed below. scn (2) - SCN/DS terminations pdnRtp (3) - PDN terminations of RTP type. pdnAtmAal1 (4) - PDN terminations of ATM type with AAL1 adaptation layer. pdnAtmAal2 (5) - PDN terminations of ATM type with AAL2 adaptation layer. If the value of this object is set to scn(2) or pdnRtp(3), the value of cmedxProfileAtmAalType for the profile of this termination type should be other(1). If the value of this object is set to pdnAtmAal1(4), the value of cmedxProfileAtmAalType for the profile of this termination type should be aal1(2), aal1Sdt(3), or aal1Udt(4). If the value of this object is set to pdnAtmAal2(5), the value of cmedxProfileAtmAalType for the profile of this termination type should be aal2(5).

CCallControlProfileIndexOrZeroThis textual convention is an extension of the CCallControlProfileIndex convention. The latter defines a greater than zero value used to identify a call control profile in a media gateway. This extension permits the additional value of zero. The value of '0' means the default call control profile of the media gateway. (0..65535) · Unsigned32

The property profile identifier with which the terminations within this termination type will be associated.

CH248PackagesThis textual convention defines all possible packages in H.248 protocol. · BITS

The H.248 packages applied to this termination type.

RowStatus1 = active2 = notInService3 = notReady4 = createAndGo5 = createAndWait6 = destroyThe RowStatus textual convention is used to manage the creation and deletion of conceptual rows, and is used as the value of the SYNTAX clause for the status column of a conceptual row (as described in Section 7.7.1 of [2].) The status column has six defined values: - `active', which indicates that the conceptual row is available for use by the managed device; - `notInService', which indicates that the conceptual row exists in the agent, but is unavailable for use by the managed device (see NOTE below); 'notInService' has no implication regarding the internal consistency of the row, availability of resources, or consistency with the current state of the managed device; - `notReady', which indicates that the conceptual row exists in the agent, but is missing information necessary in order to be available for use by the managed device (i.e., one or more required columns in the conceptual row have not been instanciated); - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device; - `createAndWait', which is supplied by a management station wishing to create a new instance of a conceptual row (but not make it available for use by the managed device); and, - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Whereas five of the six values (all except `notReady') may be specified in a management protocol set operation, only three values will be returned in response to a management protocol retrieval operation: `notReady', `notInService' or `active'. That is, when queried, an existing conceptual row has only three states: it is either available for use by the managed device (the status column has value `active'); it is not available for use by the managed device, though the agent has sufficient information to attempt to make it so (the status column has value `notInService'); or, it is not available for use by the managed device, and an attempt to make it so would fail because the agent has insufficient information (the state column has value `notReady'). NOTE WELL This textual convention may be used for a MIB table, irrespective of whether the values of that table's conceptual rows are able to be modified while it is active, or whether its conceptual rows must be taken out of service in order to be modified. That is, it is the responsibility of the DESCRIPTION clause of the status column to specify whether the status column must not be `active' in order for the value of some other column of the same conceptual row to be modified. If such a specification is made, affected columns may be changed by an SNMP set PDU if the RowStatus would not be equal to `active' either immediately before or after processing the PDU. In other words, if the PDU also contained a varbind that would change the RowStatus value, the column in question may be changed if the RowStatus was not equal to `active' as the PDU was received, or if the varbind sets the status to a value other than 'active'. Also note that whenever any elements of a row exist, the RowStatus column must also exist. To summarize the effect of having a conceptual row with a status column having a SYNTAX clause value of RowStatus, consider the following state diagram: STATE +--------------+-----------+-------------+------------- | A | B | C | D | |status col.|status column| |status column | is | is |status column ACTION |does not exist| notReady | notInService| is active --------------+--------------+-----------+-------------+------------- set status |noError ->D|inconsist- |inconsistent-|inconsistent- column to | or | entValue| Value| Value createAndGo |inconsistent- | | | | Value| | | --------------+--------------+-----------+-------------+------------- set status |noError see 1|inconsist- |inconsistent-|inconsistent- column to | or | entValue| Value| Value createAndWait |wrongValue | | | --------------+--------------+-----------+-------------+------------- set status |inconsistent- |inconsist- |noError |noError column to | Value| entValue| | active | | | | | | or | | | | | | | |see 2 ->D|see 8 ->D| ->D --------------+--------------+-----------+-------------+------------- set status |inconsistent- |inconsist- |noError |noError ->C column to | Value| entValue| | notInService | | | | | | or | | or | | | | | |see 3 ->C| ->C|see 6 --------------+--------------+-----------+-------------+------------- set status |noError |noError |noError |noError ->A column to | | | | or destroy | ->A| ->A| ->A|see 7 --------------+--------------+-----------+-------------+------------- set any other |see 4 |noError |noError |see 5 column to some| | | | value | | see 1| ->C| ->D --------------+--------------+-----------+-------------+------------- (1) goto B or C, depending on information available to the agent. (2) if other variable bindings included in the same PDU, provide values for all columns which are missing but required, and all columns have acceptable values, then return noError and goto D. (3) if other variable bindings included in the same PDU, provide legal values for all columns which are missing but required, then return noError and goto C. (4) at the discretion of the agent, the return value may be either: inconsistentName: because the agent does not choose to create such an instance when the corresponding RowStatus instance does not exist, or inconsistentValue: if the supplied value is inconsistent with the state of some other MIB object's value, or noError: because the agent chooses to create the instance. If noError is returned, then the instance of the status column must also be created, and the new state is B or C, depending on the information available to the agent. If inconsistentName or inconsistentValue is returned, the row remains in state A. (5) depending on the MIB definition for the column/table, either noError or inconsistentValue may be returned. (6) the return value can indicate one of the following errors: wrongValue: because the agent does not support notInService (e.g., an agent which does not support createAndWait), or inconsistentValue: because the agent is unable to take the row out of service at this time, perhaps because it is in use and cannot be de-activated. (7) the return value can indicate the following error: inconsistentValue: because the agent is unable to remove the row at this time, perhaps because it is in use and cannot be de-activated. (8) the transition to D can fail, e.g., if the values of the conceptual row are inconsistent, then the error code would be inconsistentValue. NOTE: Other processing of (this and other varbinds of) the set request may result in a response other than noError being returned, e.g., wrongValue, noCreation, etc. Conceptual Row Creation There are four potential interactions when creating a conceptual row: selecting an instance-identifier which is not in use; creating the conceptual row; initializing any objects for which the agent does not supply a default; and, making the conceptual row available for use by the managed device. Interaction 1: Selecting an Instance-Identifier The algorithm used to select an instance-identifier varies for each conceptual row. In some cases, the instance- identifier is semantically significant, e.g., the destination address of a route, and a management station selects the instance-identifier according to the semantics. In other cases, the instance-identifier is used solely to distinguish conceptual rows, and a management station without specific knowledge of the conceptual row might examine the instances present in order to determine an unused instance-identifier. (This approach may be used, but it is often highly sub-optimal; however, it is also a questionable practice for a naive management station to attempt conceptual row creation.) Alternately, the MIB module which defines the conceptual row might provide one or more objects which provide assistance in determining an unused instance-identifier. For example, if the conceptual row is indexed by an integer-value, then an object having an integer-valued SYNTAX clause might be defined for such a purpose, allowing a management station to issue a management protocol retrieval operation. In order to avoid unnecessary collisions between competing management stations, `adjacent' retrievals of this object should be different. Finally, the management station could select a pseudo-random number to use as the index. In the event that this index was already in use and an inconsistentValue was returned in response to the management protocol set operation, the management station should simply select a new pseudo-random number and retry the operation. A MIB designer should choose between the two latter algorithms based on the size of the table (and therefore the efficiency of each algorithm). For tables in which a large number of entries are expected, it is recommended that a MIB object be defined that returns an acceptable index for creation. For tables with small numbers of entries, it is recommended that the latter pseudo-random index mechanism be used. Interaction 2: Creating the Conceptual Row Once an unused instance-identifier has been selected, the management station determines if it wishes to create and activate the conceptual row in one transaction or in a negotiated set of interactions. Interaction 2a: Creating and Activating the Conceptual Row The management station must first determine the column requirements, i.e., it must determine those columns for which it must or must not provide values. Depending on the complexity of the table and the management station's knowledge of the agent's capabilities, this determination can be made locally by the management station. Alternately, the management station issues a management protocol get operation to examine all columns in the conceptual row that it wishes to create. In response, for each column, there are three possible outcomes: - a value is returned, indicating that some other management station has already created this conceptual row. We return to interaction 1. - the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it should supply a value for this column when the conceptual row is to be created. - the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column. Once the column requirements have been determined, a management protocol set operation is accordingly issued. This operation also sets the new instance of the status column to `createAndGo'. When the agent processes the set operation, it verifies that it has sufficient information to make the conceptual row available for use by the managed device. The information available to the agent is provided by two sources: the management protocol set operation which creates the conceptual row, and, implementation-specific defaults supplied by the agent (note that an agent must provide implementation-specific defaults for at least those objects which it implements as read-only). If there is sufficient information available, then the conceptual row is created, a `noError' response is returned, the status column is set to `active', and no further interactions are necessary (i.e., interactions 3 and 4 are skipped). If there is insufficient information, then the conceptual row is not created, and the set operation fails with an error of `inconsistentValue'. On this error, the management station can issue a management protocol retrieval operation to determine if this was because it failed to specify a value for a required column, or, because the selected instance of the status column already existed. In the latter case, we return to interaction 1. In the former case, the management station can re-issue the set operation with the additional information, or begin interaction 2 again using `createAndWait' in order to negotiate creation of the conceptual row. NOTE WELL Regardless of the method used to determine the column requirements, it is possible that the management station might deem a column necessary when, in fact, the agent will not allow that particular columnar instance to be created or written. In this case, the management protocol set operation will fail with an error such as `noCreation' or `notWritable'. In this case, the management station decides whether it needs to be able to set a value for that particular columnar instance. If not, the management station re-issues the management protocol set operation, but without setting a value for that particular columnar instance; otherwise, the management station aborts the row creation algorithm. Interaction 2b: Negotiating the Creation of the Conceptual Row The management station issues a management protocol set operation which sets the desired instance of the status column to `createAndWait'. If the agent is unwilling to process a request of this sort, the set operation fails with an error of `wrongValue'. (As a consequence, such an agent must be prepared to accept a single management protocol set operation, i.e., interaction 2a above, containing all of the columns indicated by its column requirements.) Otherwise, the conceptual row is created, a `noError' response is returned, and the status column is immediately set to either `notInService' or `notReady', depending on whether it has sufficient information to (attempt to) make the conceptual row available for use by the managed device. If there is sufficient information available, then the status column is set to `notInService'; otherwise, if there is insufficient information, then the status column is set to `notReady'. Regardless, we proceed to interaction 3. Interaction 3: Initializing non-defaulted Objects The management station must now determine the column requirements. It issues a management protocol get operation to examine all columns in the created conceptual row. In the response, for each column, there are three possible outcomes: - a value is returned, indicating that the agent implements the object-type associated with this column and had sufficient information to provide a value. For those columns to which the agent provides read-create access (and for which the agent allows their values to be changed after their creation), a value return tells the management station that it may issue additional management protocol set operations, if it desires, in order to change the value associated with this column. - the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. However, the agent does not have sufficient information to provide a value, and until a value is provided, the conceptual row may not be made available for use by the managed device. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it must issue additional management protocol set operations, in order to provide a value associated with this column. - the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column. If the value associated with the status column is `notReady', then the management station must first deal with all `noSuchInstance' columns, if any. Having done so, the value of the status column becomes `notInService', and we proceed to interaction 4. Interaction 4: Making the Conceptual Row Available Once the management station is satisfied with the values associated with the columns of the conceptual row, it issues a management protocol set operation to set the status column to `active'. If the agent has sufficient information to make the conceptual row available for use by the managed device, the management protocol set operation succeeds (a `noError' response is returned). Otherwise, the management protocol set operation fails with an error of `inconsistentValue'. NOTE WELL A conceptual row having a status column with value `notInService' or `notReady' is unavailable to the managed device. As such, it is possible for the managed device to create its own instances during the time between the management protocol set operation which sets the status column to `createAndWait' and the management protocol set operation which sets the status column to `active'. In this case, when the management protocol set operation is issued to set the status column to `active', the values held in the agent supersede those used by the managed device. If the management station is prevented from setting the status column to `active' (e.g., due to management station or network failure) the conceptual row will be left in the `notInService' or `notReady' state, consuming resources indefinitely. The agent must detect conceptual rows that have been in either state for an abnormally long period of time and remove them. It is the responsibility of the DESCRIPTION clause of the status column to indicate what an abnormally long period of time would be. This period of time should be long enough to allow for human response time (including `think time') between the creation of the conceptual row and the setting of the status to `active'. In the absence of such information in the DESCRIPTION clause, it is suggested that this period be approximately 5 minutes in length. This removal action applies not only to newly-created rows, but also to previously active rows which are set to, and left in, the notInService state for a prolonged period exceeding that which is considered normal for such a conceptual row. Conceptual Row Suspension When a conceptual row is `active', the management station may issue a management protocol set operation which sets the instance of the status column to `notInService'. If the agent is unwilling to do so, the set operation fails with an error of `wrongValue' or `inconsistentValue'. Otherwise, the conceptual row is taken out of service, and a `noError' response is returned. It is the responsibility of the DESCRIPTION clause of the status column to indicate under what circumstances the status column should be taken out of service (e.g., in order for the value of some other column of the same conceptual row to be modified). Conceptual Row Deletion For deletion of conceptual rows, a management protocol set operation is issued which sets the instance of the status column to `destroy'. This request may be made regardless of the current value of the status column (e.g., it is possible to delete conceptual rows which are either `notReady', `notInService' or `active'.) If the operation succeeds, then all instances associated with the conceptual row are immediately removed. · Integer32

This object is used to create new rows, modify existing rows and to delete existing rows.

CCallControlProfileIndexThis textual convention defines the type of index that is used for identifying a call control profile of XGCP and H.248 protocol. (1..65535) · Unsigned32

This object uniquely identifies the H.248 profile.

Unsigned32 · milliseconds

This object specifies the duration for playing a list of call progressing tones between two call progressing signals. The value of 0 indicates there is no wait between two call progressing signals. ⓘ

Unsigned32 (40..4294967295) · milliseconds

This object specifies the duration of the active DTMF digit during DTMF playout from the gateway. A complete DTMF digit is characterized by DTMF on with duration specified by this object followed by a pause (signal off) duration specified by the object cmedxProfileDtmfPauseDuration. ⓘ

Unsigned32 (40..4294967295) · milliseconds

This object specifies the duration of the pause after an active DTMF digit during DTMF playout from the gateway. For playout of multiple DTMF digits, the sum of the digit-on and pause (signaling velocity) should not be shorter than the time specified in Q.23, Q.24 and EIA/TIA-464. For example, 93ms/digit for AT&T, 120ms/digit for NTT, 100ms/digit for Danish Administration. ⓘ

Unsigned32 (1..4000) · Hz

This object specifies the tone frequency to be transmit between gateways in the continuity test.

Unsigned32 (1..4000) · Hz

This object specifies the tone frequency to be received between gateways in the continuity test.

Unsigned32 · milliseconds

This object specifies the duration for the continuity test tone to be played when the gateway initiates a COT. The value of 0 indicates that the tone will be played infinitely unless interrupted. ⓘ

INTEGER1 = loopback2 = transponder · Integer32

This object specifies the method for responding to COT (Continuity Test Tone) when the gateway detects a the continuity test signal. loopback (1) - The gateway loops back the received continuity test signal. transponder (2) - The gateway responds with another continuity test signal upon detecting a continuity test signal. When this object is set to loopback(1), the originating gateway transmits the frequency specified in the value of cmedxProfileCot1Frequency, the terminating gateway loops back whatever it receives. When this object is set to transponder(2), the originating gateway transmit the frequency specified in the value of cmedxProfileCot1Frequency, and the terminating gateway responds the frequency specified in the value of cmedxProfileCot2Frequency. ⓘ

Unsigned32 · milliseconds

This object specifies the duration for detecting a long call progressing tone. ⓘ

Unsigned32 · milliseconds

This object specifies the duration for detecting a long digit tone signal. ⓘ

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object specifies whether or not the Echo Cancellation is enabled or not. ⓘ

INTEGER1 = echoCanceller8ms2 = echoCanceller16ms3 = echoCanceller24ms4 = echoCanceller32ms5 = echoCanceller64ms6 = echoCanceller128ms · Integer32

This object specifies the Echo Canceler coverage. This object is valid if the cmedxProfileEchoCancelEnabled object is 'true'. echoCanceller8ms - 8 ms echo canceler coverage. echoCanceller16ms - 16 ms echo canceler coverage. echoCanceller24ms - 24 ms echo canceler coverage. echoCanceller32ms - 32 ms echo canceler coverage. echoCanceller64ms - 64 ms echo canceler coverage. echoCanceller128ms- 128 ms echo canceler coverage.

Integer32 (-6..14) · dB

This object contains the amount of gain inserted at the receiver side of the interface. The input gain settings only define a gain/loss relative to the 0 dB setting. The absolute loss at the 0 dB setting could be implementation dependent based on the desired network loss plan. ⓘ

Unsigned32 (0..14) · dB

This object contains the amount of attenuation inserted at the transmit side of the interface. The output attenuation settings only define a loss relative to the 0 dB setting. The absolute loss at the 0 dB setting could be implementation dependent based on the desired network loss plan.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object specifies VAD (Voice Activity Detection) is enabled for the compression DSPs of this interface when the application is VoIP.

Unsigned32 · milliseconds

This object specifies the hangover time for VAD in the VoIP application. Once the voice inactivity is detected, the media gateway waits for the duration of this value before activating silence suppression. This object is not applicable if cmedxProfileVoIpVadEnabled is set to 'false'.

Unsigned32 · milliseconds

This object specifies the hangover time for VAD in the VoATM over AAL2 application. Once the voice inactivity is detected, the media gateway waits for the duration of this value before activating silence suppression. This object is not applicable if cvapAal2ProfVad is set to 'vadOff'.

INTEGER1 = bearerSvc2 = bearerPvc · Integer32

This object specifies ATM bearer type. bearerSvc (1) - the ATM bearer type is SVC (Switched Virtual Circuit). bearerPvc (1) - the ATM bearer type is PVC (Permanent Virtual Circuit).

Unsigned32 (1..48)

This object specifies the fill level of cells in case of AAL adaptation . The value of this object will be used if the MGC does not specify partial fill in the commands. ATM cell size is 53 bytes, 5 bytes for header, 48 bytes for data. If the data are not enough to fill 48 bytes of one ATM cell, the system can fill in the value of this object to the padding bytes.

INTEGER1 = other2 = aal13 = aal1Sdt4 = aal1Udt5 = aal2 · Integer32

This object specifies the adaptation layer of ATM. other (1) - None of the types listed below. aal1 (2) - ATM AAL1 adaptation layer aal1Sdt (3) - ATM AAL1 with SDT (Structured Data Transfer) aal1Udt (4) - ATM AAL1 with UDT (Unstructured Data Transfer). aal2 (5) - ATM AAL2 adaptation layer.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object controls if the digits should be suppressed from voice media stream. When MGC has requested digits, if this object is set to 'true', the digits will be reported to MGC only, the digits will not be sent as regular voice or peer-to-peer packets in the bearer. When MGC has requested digits, if this object is set to 'false', the digits will be reported to MGC as well as be sent in the bearer according to the value of cvapCodecConfigDtmfRelay in cvapCodecConfigTable. When MGC has not requested digits, this object will be ignored. The digits will be sent in the bearer according to the value of cvapCodecConfigDtmfRelay in cvapCodecConfigTable.

RowStatus1 = active2 = notInService3 = notReady4 = createAndGo5 = createAndWait6 = destroyThe RowStatus textual convention is used to manage the creation and deletion of conceptual rows, and is used as the value of the SYNTAX clause for the status column of a conceptual row (as described in Section 7.7.1 of [2].) The status column has six defined values: - `active', which indicates that the conceptual row is available for use by the managed device; - `notInService', which indicates that the conceptual row exists in the agent, but is unavailable for use by the managed device (see NOTE below); 'notInService' has no implication regarding the internal consistency of the row, availability of resources, or consistency with the current state of the managed device; - `notReady', which indicates that the conceptual row exists in the agent, but is missing information necessary in order to be available for use by the managed device (i.e., one or more required columns in the conceptual row have not been instanciated); - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device; - `createAndWait', which is supplied by a management station wishing to create a new instance of a conceptual row (but not make it available for use by the managed device); and, - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Whereas five of the six values (all except `notReady') may be specified in a management protocol set operation, only three values will be returned in response to a management protocol retrieval operation: `notReady', `notInService' or `active'. That is, when queried, an existing conceptual row has only three states: it is either available for use by the managed device (the status column has value `active'); it is not available for use by the managed device, though the agent has sufficient information to attempt to make it so (the status column has value `notInService'); or, it is not available for use by the managed device, and an attempt to make it so would fail because the agent has insufficient information (the state column has value `notReady'). NOTE WELL This textual convention may be used for a MIB table, irrespective of whether the values of that table's conceptual rows are able to be modified while it is active, or whether its conceptual rows must be taken out of service in order to be modified. That is, it is the responsibility of the DESCRIPTION clause of the status column to specify whether the status column must not be `active' in order for the value of some other column of the same conceptual row to be modified. If such a specification is made, affected columns may be changed by an SNMP set PDU if the RowStatus would not be equal to `active' either immediately before or after processing the PDU. In other words, if the PDU also contained a varbind that would change the RowStatus value, the column in question may be changed if the RowStatus was not equal to `active' as the PDU was received, or if the varbind sets the status to a value other than 'active'. Also note that whenever any elements of a row exist, the RowStatus column must also exist. To summarize the effect of having a conceptual row with a status column having a SYNTAX clause value of RowStatus, consider the following state diagram: STATE +--------------+-----------+-------------+------------- | A | B | C | D | |status col.|status column| |status column | is | is |status column ACTION |does not exist| notReady | notInService| is active --------------+--------------+-----------+-------------+------------- set status |noError ->D|inconsist- |inconsistent-|inconsistent- column to | or | entValue| Value| Value createAndGo |inconsistent- | | | | Value| | | --------------+--------------+-----------+-------------+------------- set status |noError see 1|inconsist- |inconsistent-|inconsistent- column to | or | entValue| Value| Value createAndWait |wrongValue | | | --------------+--------------+-----------+-------------+------------- set status |inconsistent- |inconsist- |noError |noError column to | Value| entValue| | active | | | | | | or | | | | | | | |see 2 ->D|see 8 ->D| ->D --------------+--------------+-----------+-------------+------------- set status |inconsistent- |inconsist- |noError |noError ->C column to | Value| entValue| | notInService | | | | | | or | | or | | | | | |see 3 ->C| ->C|see 6 --------------+--------------+-----------+-------------+------------- set status |noError |noError |noError |noError ->A column to | | | | or destroy | ->A| ->A| ->A|see 7 --------------+--------------+-----------+-------------+------------- set any other |see 4 |noError |noError |see 5 column to some| | | | value | | see 1| ->C| ->D --------------+--------------+-----------+-------------+------------- (1) goto B or C, depending on information available to the agent. (2) if other variable bindings included in the same PDU, provide values for all columns which are missing but required, and all columns have acceptable values, then return noError and goto D. (3) if other variable bindings included in the same PDU, provide legal values for all columns which are missing but required, then return noError and goto C. (4) at the discretion of the agent, the return value may be either: inconsistentName: because the agent does not choose to create such an instance when the corresponding RowStatus instance does not exist, or inconsistentValue: if the supplied value is inconsistent with the state of some other MIB object's value, or noError: because the agent chooses to create the instance. If noError is returned, then the instance of the status column must also be created, and the new state is B or C, depending on the information available to the agent. If inconsistentName or inconsistentValue is returned, the row remains in state A. (5) depending on the MIB definition for the column/table, either noError or inconsistentValue may be returned. (6) the return value can indicate one of the following errors: wrongValue: because the agent does not support notInService (e.g., an agent which does not support createAndWait), or inconsistentValue: because the agent is unable to take the row out of service at this time, perhaps because it is in use and cannot be de-activated. (7) the return value can indicate the following error: inconsistentValue: because the agent is unable to remove the row at this time, perhaps because it is in use and cannot be de-activated. (8) the transition to D can fail, e.g., if the values of the conceptual row are inconsistent, then the error code would be inconsistentValue. NOTE: Other processing of (this and other varbinds of) the set request may result in a response other than noError being returned, e.g., wrongValue, noCreation, etc. Conceptual Row Creation There are four potential interactions when creating a conceptual row: selecting an instance-identifier which is not in use; creating the conceptual row; initializing any objects for which the agent does not supply a default; and, making the conceptual row available for use by the managed device. Interaction 1: Selecting an Instance-Identifier The algorithm used to select an instance-identifier varies for each conceptual row. In some cases, the instance- identifier is semantically significant, e.g., the destination address of a route, and a management station selects the instance-identifier according to the semantics. In other cases, the instance-identifier is used solely to distinguish conceptual rows, and a management station without specific knowledge of the conceptual row might examine the instances present in order to determine an unused instance-identifier. (This approach may be used, but it is often highly sub-optimal; however, it is also a questionable practice for a naive management station to attempt conceptual row creation.) Alternately, the MIB module which defines the conceptual row might provide one or more objects which provide assistance in determining an unused instance-identifier. For example, if the conceptual row is indexed by an integer-value, then an object having an integer-valued SYNTAX clause might be defined for such a purpose, allowing a management station to issue a management protocol retrieval operation. In order to avoid unnecessary collisions between competing management stations, `adjacent' retrievals of this object should be different. Finally, the management station could select a pseudo-random number to use as the index. In the event that this index was already in use and an inconsistentValue was returned in response to the management protocol set operation, the management station should simply select a new pseudo-random number and retry the operation. A MIB designer should choose between the two latter algorithms based on the size of the table (and therefore the efficiency of each algorithm). For tables in which a large number of entries are expected, it is recommended that a MIB object be defined that returns an acceptable index for creation. For tables with small numbers of entries, it is recommended that the latter pseudo-random index mechanism be used. Interaction 2: Creating the Conceptual Row Once an unused instance-identifier has been selected, the management station determines if it wishes to create and activate the conceptual row in one transaction or in a negotiated set of interactions. Interaction 2a: Creating and Activating the Conceptual Row The management station must first determine the column requirements, i.e., it must determine those columns for which it must or must not provide values. Depending on the complexity of the table and the management station's knowledge of the agent's capabilities, this determination can be made locally by the management station. Alternately, the management station issues a management protocol get operation to examine all columns in the conceptual row that it wishes to create. In response, for each column, there are three possible outcomes: - a value is returned, indicating that some other management station has already created this conceptual row. We return to interaction 1. - the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it should supply a value for this column when the conceptual row is to be created. - the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column. Once the column requirements have been determined, a management protocol set operation is accordingly issued. This operation also sets the new instance of the status column to `createAndGo'. When the agent processes the set operation, it verifies that it has sufficient information to make the conceptual row available for use by the managed device. The information available to the agent is provided by two sources: the management protocol set operation which creates the conceptual row, and, implementation-specific defaults supplied by the agent (note that an agent must provide implementation-specific defaults for at least those objects which it implements as read-only). If there is sufficient information available, then the conceptual row is created, a `noError' response is returned, the status column is set to `active', and no further interactions are necessary (i.e., interactions 3 and 4 are skipped). If there is insufficient information, then the conceptual row is not created, and the set operation fails with an error of `inconsistentValue'. On this error, the management station can issue a management protocol retrieval operation to determine if this was because it failed to specify a value for a required column, or, because the selected instance of the status column already existed. In the latter case, we return to interaction 1. In the former case, the management station can re-issue the set operation with the additional information, or begin interaction 2 again using `createAndWait' in order to negotiate creation of the conceptual row. NOTE WELL Regardless of the method used to determine the column requirements, it is possible that the management station might deem a column necessary when, in fact, the agent will not allow that particular columnar instance to be created or written. In this case, the management protocol set operation will fail with an error such as `noCreation' or `notWritable'. In this case, the management station decides whether it needs to be able to set a value for that particular columnar instance. If not, the management station re-issues the management protocol set operation, but without setting a value for that particular columnar instance; otherwise, the management station aborts the row creation algorithm. Interaction 2b: Negotiating the Creation of the Conceptual Row The management station issues a management protocol set operation which sets the desired instance of the status column to `createAndWait'. If the agent is unwilling to process a request of this sort, the set operation fails with an error of `wrongValue'. (As a consequence, such an agent must be prepared to accept a single management protocol set operation, i.e., interaction 2a above, containing all of the columns indicated by its column requirements.) Otherwise, the conceptual row is created, a `noError' response is returned, and the status column is immediately set to either `notInService' or `notReady', depending on whether it has sufficient information to (attempt to) make the conceptual row available for use by the managed device. If there is sufficient information available, then the status column is set to `notInService'; otherwise, if there is insufficient information, then the status column is set to `notReady'. Regardless, we proceed to interaction 3. Interaction 3: Initializing non-defaulted Objects The management station must now determine the column requirements. It issues a management protocol get operation to examine all columns in the created conceptual row. In the response, for each column, there are three possible outcomes: - a value is returned, indicating that the agent implements the object-type associated with this column and had sufficient information to provide a value. For those columns to which the agent provides read-create access (and for which the agent allows their values to be changed after their creation), a value return tells the management station that it may issue additional management protocol set operations, if it desires, in order to change the value associated with this column. - the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. However, the agent does not have sufficient information to provide a value, and until a value is provided, the conceptual row may not be made available for use by the managed device. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it must issue additional management protocol set operations, in order to provide a value associated with this column. - the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column. If the value associated with the status column is `notReady', then the management station must first deal with all `noSuchInstance' columns, if any. Having done so, the value of the status column becomes `notInService', and we proceed to interaction 4. Interaction 4: Making the Conceptual Row Available Once the management station is satisfied with the values associated with the columns of the conceptual row, it issues a management protocol set operation to set the status column to `active'. If the agent has sufficient information to make the conceptual row available for use by the managed device, the management protocol set operation succeeds (a `noError' response is returned). Otherwise, the management protocol set operation fails with an error of `inconsistentValue'. NOTE WELL A conceptual row having a status column with value `notInService' or `notReady' is unavailable to the managed device. As such, it is possible for the managed device to create its own instances during the time between the management protocol set operation which sets the status column to `createAndWait' and the management protocol set operation which sets the status column to `active'. In this case, when the management protocol set operation is issued to set the status column to `active', the values held in the agent supersede those used by the managed device. If the management station is prevented from setting the status column to `active' (e.g., due to management station or network failure) the conceptual row will be left in the `notInService' or `notReady' state, consuming resources indefinitely. The agent must detect conceptual rows that have been in either state for an abnormally long period of time and remove them. It is the responsibility of the DESCRIPTION clause of the status column to indicate what an abnormally long period of time would be. This period of time should be long enough to allow for human response time (including `think time') between the creation of the conceptual row and the setting of the status to `active'. In the absence of such information in the DESCRIPTION clause, it is suggested that this period be approximately 5 minutes in length. This removal action applies not only to newly-created rows, but also to previously active rows which are set to, and left in, the notInService state for a prolonged period exceeding that which is considered normal for such a conceptual row. Conceptual Row Suspension When a conceptual row is `active', the management station may issue a management protocol set operation which sets the instance of the status column to `notInService'. If the agent is unwilling to do so, the set operation fails with an error of `wrongValue' or `inconsistentValue'. Otherwise, the conceptual row is taken out of service, and a `noError' response is returned. It is the responsibility of the DESCRIPTION clause of the status column to indicate under what circumstances the status column should be taken out of service (e.g., in order for the value of some other column of the same conceptual row to be modified). Conceptual Row Deletion For deletion of conceptual rows, a management protocol set operation is issued which sets the instance of the status column to `destroy'. This request may be made regardless of the current value of the status column (e.g., it is possible to delete conceptual rows which are either `notReady', `notInService' or `active'.) If the operation succeeds, then all instances associated with the conceptual row are immediately removed. · Integer32

When an entry is created, at least one of the objects in the entry has to be provided and the default value will be assigned to the rest of the objects.

CMedxCotTones1 = co12 = co2This textual convention defines the tones to be used between originating gateway and terminating gateway in the COT (Continuity Test). co1 (1) - CO1 is either 2000Hz or 2010Hz depending on the region/country regulation. co2 (2) - CO2 is always 1780Hz. · Integer32

This object specifies the COT tone to be transmitted from originating gateway in the continuity test.

CMedxCotTones1 = co12 = co2This textual convention defines the tones to be used between originating gateway and terminating gateway in the COT (Continuity Test). co1 (1) - CO1 is either 2000Hz or 2010Hz depending on the region/country regulation. co2 (2) - CO2 is always 1780Hz. · Integer32

This object specifies the COT tone to be received in originating gateway in the continuity test.

CMedxCotTones1 = co12 = co2This textual convention defines the tones to be used between originating gateway and terminating gateway in the COT (Continuity Test). co1 (1) - CO1 is either 2000Hz or 2010Hz depending on the region/country regulation. co2 (2) - CO2 is always 1780Hz. · Integer32

This object specifies the COT tone to be transmitted from terminating gateway in the continuity test.

CMedxCotTones1 = co12 = co2This textual convention defines the tones to be used between originating gateway and terminating gateway in the COT (Continuity Test). co1 (1) - CO1 is either 2000Hz or 2010Hz depending on the region/country regulation. co2 (2) - CO2 is always 1780Hz. · Integer32

This object specifies the COT tone to be received in terminating gateway in the continuity test.

INTEGER1 = none2 = simple3 = g711A2 · Integer32

This object specifies the type of comfort noise generation: (1) none: No comfort noise generation applied (2) simple: Cisco Proprietary comfort noise generation (3) g711A2: ITU G.711 Appendix II compliant

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object controls if the H.248 congestion package (H.248.10) and its associated features should be enabled for the media gateway. If this object is set to 'false', then the following MIB objects and MIB table will be ignored: cmedxCallRenotifInterval cmedxCRRNumOfLevel cmedxCurrentCRR cmedxCrrNotifyState cmedxCrrNotifyEnabled cmedxCallReduceLevelTable.

Unsigned32 (0..100) · seconds

This object specifies the interval of the congestion renotification from the media gateway to the MGC. In the event of congestion on the Media Gateway, gateway generates an event towards MGC. Using this message, MG requests percentage reduction in the rate of calls that MGC is attempting towards MG. After sending this indication, MG starts a timer based on 'cmedxCallRenotifInterval'. At this timer expires, MG will re-send the message to MGC indicating that it is still in congested state. If MGC does not receive another notification, MGC will resume to the original call rate. If MGC requires re-notifications, it is user's responsibility to set the value of this MIB object on MG appropriately. The value of this object should be set such that it factors into the network delay and re-notification timer (similar to this MIB object) configured on MGC. The zero means MGC does not require re-notifications, MGC will keep CallReduceRate until receive another notification from the Media Gateway.

Unsigned32 (1..16)

This objects specifies the number of level corresponding to which a different call reduction rate notification is generated towards MGC. Each level has a different call reduction rate, the CRR information is stored on cmedxCallReduceLevelTabl. And The table size equals to the value of 'cmedxCRRNumOfLevel'.

Unsigned32 (0..100) · percent

This object indicates the current percentage reduction in the rate of calls that MGC is attempting towards MG.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object indicates the current gateway congestion notification state. The value of 'true' means the gateway will notify MGC when the gateway is congested. The value of 'false' means the gateway won't notify MGC when the gateway is congested. This object is 'true' when cmedxCallCongEnabled is set to 'true' and at least one of MGCs enabled the CRR notification (cmedxCrrNotifyEnabled is not 0).

OCTET STRING SIZE (4)

This object indicates the bit map of the H248 association index (cmedGatewayLinkId) in which the gateway congestion notification is enabled. The MSB (most significant bit) is the association index 1. A 1-bit indicates the gateway congestion notification is enabled in this H248 association. A 0-bit indicates it is disabled.

INTEGER1 = acceptCall2 = dropCall · Integer32

This object indicates the state of the gateway in accepting the incoming new call. acceptCall - the incoming new call will be processed. dropCall - the incoming new call will be droped due to the resources congested.

Unsigned32 (1..16)

The index starts from 1, and the maximum index equals to 'cmedxCRRNumOfLevel'.

Unsigned32 (1..100) · percent

This object indicates call reduction rate (CRR) for a given call reduce rate level. The default value of this object is based on the formula: level 1: 100 other level: 100 - ((80/(nol - 1)) * (level - 1)) Here: nol : number of level(cmedxCRRNumOfLevel) level: specific level (cmedxCallReduceLevelNum) User can configure this object, the rule is: level x > level x+1

CvcSpeechCoderRate1 = g729r80002 = g729Ar80003 = g726r160004 = g726r240005 = g726r320006 = g711ulawr640007 = g711Alawr640008 = g728r160009 = g723r630010 = g723r530011 = gsmr1320012 = g729Br800013 = g729ABr800014 = g723Ar630015 = g723Ar530016 = g729IETFr800017 = gsmeEr1220018 = clearChannel19 = g726r4000020 = llcc21 = gsmAmrNb22 = iLBC23 = iLBCr1520024 = iLBCr1333025 = g722r480026 = g722r560027 = g722r640028 = iSAC29 = aaclc30 = aacldThis object specifies the most desirable codec of speech for the VoIP, VoATM or VoFR peer. g729r8000 - pre-IETF G.729 8000 bps g729Ar8000 - G.729 ANNEX-A 8000 bps g726r16000 - G.726 16000 bps g726r24000 - G.726 24000 bps g726r32000 - G.726 32000 bps g711ulawr64000 - G.711 u-Law 64000 bps g711Alawr64000 - G.711 A-Law 64000 bps g728r16000 - G.728 16000 bps g723r6300 - G.723.1 6300 bps g723r5300 - G.723.1 5300 bps gsmr13200 - GSM Full rate 13200 bps g729Br8000 - G.729 ANNEX-B 8000 bps g729ABr8000 - G.729 ANNEX-A & B 8000 bps g723Ar6300 - G723.1 Annex A 6300 bps g723Ar5300 - G723.1 Annex A 5300 bps g729IETFr8000 - IETF G.729 8000 bps gsmeEr12200 - GSM Enhanced Full Rate 12200 bps clearChannel - CLEAR Channel codec g726r40000 - G.726 40000 bps llcc - Lossless compression codec gsmAmrNb - GSM AMR-NB 4750 - 12200 bps iLBC - iILBC 13330 or 15200 bps iLBCr15200 - iLBC 15200 bps iLBCr13330 - iLBC 13330 bps g722r4800 - G.722 (modes 1, 2, 3) g722r5600 - G.722 (modes 1, 2) g722r6400 - G.722 (mode 1) iSAC - iSAC (10 to 32 kbps) aaclc - AAC-LC Advanced Audio Coding Low Complexity aacld - AAC-LD MPEG-4 Low Delay Audio CoderReference: [1] RFC 3267: For introduction about GSM AMR-NB codec, section 3.1 [2] RFC 3952: For introduction about iLBC codec, section 2 · Integer32

This object specifies the CODEC to be used in this profile.

Unsigned32 (0..255)

This object specified the preference configured by the user for each CODEC. Lower the number, higher the preference of the CODEC. If this object is set to 0, the corresponding CODEC will not be used in coded negotiation procedure. Initially, if the value of cmedxCodecNegotiationCodec is g711u, this object is set to 1, else this object is set to 0. For CODECs having the same preference, the entry with the lower index has higher precedence.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object controls if the H.248 overload package (H.248.11) and its associated features should be enabled for the media gateway. If this object is set to 'false', then the following MIB objects and MIB table will be ignored: cmedxOverloadNotifyState cmedxOverloadNotifyEnabled.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object indicates the current gateway overload notification state. The value of 'true' means the gateway will notify MGC when the gateway is overloaded. The value of 'false' means the gateway won't notify MGC when the gateway is overloaded. This object is 'true' when cmedxOverloadControlEnabled is set to 'true' and at least one of MGCs enabled gateway overload notification (cmedxOverloadNotifyEnabled is not 0).

OCTET STRING SIZE (4)

This object indicates the bit map of the H248 association index (cmedGatewayLinkId) in which the gateway overload notification is enabled. The MSB (most significant bit) is the association index 1. A 1-bit indicates the gateway overload notification is enabled in this H248 association. A 0-bit indicates it is disabled.

Unsigned32 (1..1000)

The event code of the last event occurred on the link.

Counter32

Total number of cumulative ADD commands failed in the media gateway link.

Counter32

Total number of cumulative ADD command succeeded in the media gateway link.

Counter32

Total number of cumulative SUBTRACT commands failed in the media gateway link.

Counter32

Total number of cumulative SUBTRACT commands succeeded in the media gateway link.

Counter32

Total number of cumulative MOVE commands failed in the media gateway link.

Counter32

Total number of cumulative MOVE commands succeeded in the media gateway link.

Counter32

Total number of cumulative MODIFY commands failed in the media gateway link.

Counter32

Total number of cumulative MODIFY commands succeeded in the media gateway link.

Counter32

Total number of cumulative AUDIT VALUE commands failed in the media gateway link.

Counter32

Total number of cumulative AUDIT VALUE commands succeeded in the media gateway link.

Counter32

Total number of cumulative AUDIT CAPABILITY commands failed in the media gateway link.

Counter32

Total number of cumulative AUDIT CAPABILITY commands succeeded in the media gateway link.

Counter32

Total number of cumulative NOTIFY commands failed to respond from MGC.

Counter32

Total number of cumulative NOTIFY commands successfully responded from the MGC.

Counter32

Total number of cumulative ServiceChange commands from MGC to MG failed in the media gateway link.

Counter32

Total number of cumulative ServiceChange commands from MGC to MG succeeded in the media gateway link.

Counter32

Total number of cumulative ServiceChange commands from MG to MGC failed in MGC.

Counter32

Total number of cumulative ServiceChange commands from MG to MGC succeeded in MGC.

Counter32

Total number of commands failed in the media gateway link.

Counter32

Total number of commands succeeded in the media gateway link.

Counter32

Total number of failed and successful commands in the media gateway link.

Counter32

Total number of cumulative ADD commands remain pending in the media gateway link.

Counter32

Total number of cumulative SUBTRACT commands remain pending in the media gateway link.

Counter32

Total number of cumulative MOVE commands remain pending in the media gateway link.

Counter32

Total number of cumulative MODIFY commands remain pending in the media gateway link.

Counter32

Total number of cumulative AUDIT VALUE commands remain pending in the media gateway link.

Counter32

Total number of cumulative AUDIT CAPABILITY commands remain pending in the media gateway link.

Counter32

Total number of cumulative NOTIFY commands remain pending in response from MGC.

Counter32

Total number of cumulative ServiceChange commands from MGC to MG remain pending in the media gateway link.

Counter32

Total number of cumulative ServiceChange commands from MG to MGC remain pending in MGC.

Counter32

Total number of commands remain pending in the media gateway link.

Gauge32

The current number of active contexts in the media gateway link.

Gauge32

Peak number of active contexts in the media gateway link.

Counter32

Total number of contexts has been allocated in the media gateway link.

Counter32

Total number of contexts has been freed in the media gateway link.

TimeTicks

The shortest life span for the contexts in the media gateway link.

TimeTicks

The average life span for the contexts in the media gateway link.

TimeTicks

The longest life span for the contexts in the media gateway link.

Gauge32

The number of contexts having more than 2 terminations in the media gateway link.

Counter32

Number of total ADD commands on this physical termination.

Counter32

Number of total command failures on this physical termination.

Counter32

Number of total out of service initiated from MGC on this physical termination.

Counter32

Number of total out of service initiated from OAM (Operation Administration Management, either MG or NMS) on this physical termination.

INTEGER1 = all2 = scn3 = pdnRtp4 = pdnAtmAal15 = pdnAtmAal2 · Integer32

This object specifies the statistics of the termination type to be retrieved. all (1) - Statistics for all ephemeral termination types. scn (2) - Statistics for SCN/DS terminations pdnRtp (3) - Statistics for PDN terminations of RTP type. pdnAtmAal1 (4) - Statistics for PDN terminations of ATM type with AAL1 adaptation layer. pdnAtmAal2 (5) - Statistics for PDN terminations of ATM type with AAL2 adaptation layer.

Counter32

Number of total ADD commands has been initiated on this termination type.

Counter32

Number of total command failures on this termination type.

Gauge32 · ms

The minimum add response time (ms) for physical terminations on a media gateway link.

Gauge32 · ms

The maximum add response time (ms) for physical terminations on a media gateway link.

Gauge32 · ms

The average add response time (ms) for physical terminations on a media gateway link.

Gauge32

The number of add responses for physical terminations which have been sent during the statistics interval on a media gateway link.

Gauge32 · ms

The minimum modify response time (ms) for physical terminations on a media gateway link.

Gauge32 · ms

The maximum modify response time (ms) for physical terminations on a media gateway link.

Gauge32 · ms

The average modify response time (ms) for physical terminations on a media gateway link.

Gauge32

The number of modify responses for physical terminations which have been sent during the statistics interval on a media gateway link.

Gauge32 · ms

The minimum subtract response time (ms) for physical terminations on a media gateway link.

Gauge32 · ms

The maximum subtract response time (ms) for physical terminations on a media gateway link.

Gauge32 · ms

The average subtract response time (ms) for physical terminations on a media gateway link.

Gauge32

The number of subtract responses for physical terminations which have been sent during the statistics interval on a media gateway link.

Gauge32 · ms

The minimum add response time (ms) for ephemeral terminations on a media gateway link.

Gauge32 · ms

The maximum add response time (ms) for ephemeral terminations on a media gateway link.

Gauge32 · ms

The average add response time (ms) for ephemeral terminations on a media gateway link.

Gauge32

The number of add responses for ephemeral terminations which have been sent during the statistics interval on a media gateway link.

Gauge32 · ms

The minimum modify response time (ms) for ephemeral terminations on a media gateway link.

Gauge32 · ms

The maximum modify response time (ms) for ephemeral terminations on a media gateway link.

Gauge32 · ms

The average modify response time (ms) for ephemeral terminations on a media gateway link.

Gauge32

The number of modify responses for ephemeral terminations which have been sent during the statistics interval on a media gateway link.

Gauge32 · ms

The minimum subtract response time (ms) for ephemeral terminations on a media gateway link.

Gauge32 · ms

The maximum subtract response time (ms) for ephemeral terminations on a media gateway link.

Gauge32 · ms

The average subtract response time (ms) for ephemeral terminations on a media gateway link.

Gauge32

The number of subtract responses for ephemeral terminations which have been sent during the statistics interval on a media gateway link.

Gauge32

The number of in-progress commands on a media gateway link.

Gauge32

The maximum number of in-progress commands on a media gateway link.

Unsigned32 · seconds

The elapsed time (in seconds) from the last periodic reset. All (non-accumulator) statistic objects were zeroed on the last reset.

Counter32SinceResetThis textual convention defines a counter type that is similar to Counter32 but can be reset. The value of the objects of this type indicates the statistics since last counter reset. Once the value of the counter object of this type reaches its maximum, it will restart from zero again. (0..2147483647) · Unsigned32

The number of times that the gateway enters the overload condition because of any of CAC monitoring resources has exceeded the medium threshold specified by the value of ccacSysRpMedThreshold since the last counter reset.

Counter32SinceResetThis textual convention defines a counter type that is similar to Counter32 but can be reset. The value of the objects of this type indicates the statistics since last counter reset. Once the value of the counter object of this type reaches its maximum, it will restart from zero again. (0..2147483647) · Unsigned32

The number of times that the gateway exits the overload condition when all of CAC monitoring resources have fallen below the low threshold specified by the value of ccacSysRpLowThreshold since the last counter reset.

INTEGER1 = normal2 = overload · Integer32

This object indicates the current overload state of the gateway. normal - In normal condition. overload - In overload condition.

TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks

This object contains the value of sysUpTime when the last counter reset occurred by setting cmedxOverloadCountersClear to 'true'. If no counter reset has occurred since the last time the media gateway reboot, this object will contain value of zero.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

When this object is to set value of true(1), all statistics counters in the table cmedxOverloadStatsTable will be reset to zero. Setting this object to a value of false(2) has no implication. This object will always return 'false' upon any SNMP get operation.

Unsigned32 (0..1000)

This object uniquely identifies the utilization of the resource is monitored for the gateway overload. The value of 0 is to sum the individual statistical counter for all the monitored resources.

Counter32SinceResetThis textual convention defines a counter type that is similar to Counter32 but can be reset. The value of the objects of this type indicates the statistics since last counter reset. Once the value of the counter object of this type reaches its maximum, it will restart from zero again. (0..2147483647) · Unsigned32

The accumulated number of times that the utilization of the resource is above the high threshold specified by ccacSysRpHighThreshold when the gateway enters the overload condition since the last counter reset.

Counter32SinceResetThis textual convention defines a counter type that is similar to Counter32 but can be reset. The value of the objects of this type indicates the statistics since last counter reset. Once the value of the counter object of this type reaches its maximum, it will restart from zero again. (0..2147483647) · Unsigned32

The accumulated number of times that the utilization of the resource is above the medium threshold specified by ccacSysRpMedThreshold when the gateway enters the overload condition since the last counter reset.

Counter32SinceResetThis textual convention defines a counter type that is similar to Counter32 but can be reset. The value of the objects of this type indicates the statistics since last counter reset. Once the value of the counter object of this type reaches its maximum, it will restart from zero again. (0..2147483647) · Unsigned32

The accumulated number of times that the utilization of the resource is above the low threshold specified by ccacSysRpLowThreshold when the gateway enters the overload condition since the last counter reset.

Counter32SinceResetThis textual convention defines a counter type that is similar to Counter32 but can be reset. The value of the objects of this type indicates the statistics since last counter reset. Once the value of the counter object of this type reaches its maximum, it will restart from zero again. (0..2147483647) · Unsigned32

The accumulated number of times the CAC monitoring resource causes the gateway entering the overload condition since the last counter reset.

TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks

This object contains the value of sysUpTime when the last counter reset occurred by setting cmedxOverloadRsCountersClear to 'true'. If no counter reset has occurred since the last time the media gateway reboot, this object will contain value of zero.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

When this object is to set value of true(1), all statistics counters in the table cmedxOverloadResourceStatsTable will be reset to zero. Setting this object to a value of false(2) has no implication. This object will always return 'false' upon any SNMP get operation.

Unsigned32 (1..2147483647)

This object uniquely identifies the entry to store ephemeral termination statistics information.

INTEGER1 = bpvc2 = gw3 = vgw · Integer32

This object is used to indicate index ('cmedxEphTermInfoStatsIndex') type.

Counter32SinceResetThis textual convention defines a counter type that is similar to Counter32 but can be reset. The value of the objects of this type indicates the statistics since last counter reset. Once the value of the counter object of this type reaches its maximum, it will restart from zero again. (0..2147483647) · Unsigned32

The accumulated number of ephemeral termination.

Gauge32

The number of ephemeral termination currently in use.

Gauge32

The high watermark of number of ephemeral termination in use.

Gauge32 · ms

The minimum duration of ephemeral termination.

Gauge32 · ms

The maximum duration of ephemeral termination.

Gauge32 · ms

The average duration of ephemeral termination.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

When this object is set to value of true(1), all statistics counters with type of Counter32SinceReset in this table will be reset to zero. Setting this object to a value of false(2) has no implication. This object will always return 'false' upon any SNMP get operation.

Unsigned32 · minutes

The elapsed time from the last counter clear. The following objects are set to zero on the last counter clear: 'cmedxEphTermInfoNumTerm'

Unsigned32 · seconds

The elapsed time from the last reset. The following objects are set to zero on the last reset: 'cmedxEphTermInfoNumInUsed' 'cmedxEphTermInfoMaxNumInUsed' 'cmedxEphTermInfoMinDuration' 'cmedxEphTermInfoMaxDuration' 'cmedxEphTermInfoNumFreed'

Unsigned32 (0..2147483647)

This object is used to store the index ('cmedxEphTermInfoStatsIndex') related information. Example: for bpvc ('cmedxEphTermInfoStatsIndexType'), the vpi and vci are stored in this object. The value zero means this object should be ignored.

Unsigned32

Total number of ephemeral terminations that have been freed.