CISCO-CCM-MIB

CcmIndexThis syntax is used as the Index into a table. A positive value is used to identify a unique entry in the table. (1..4294967295) · Unsigned32 · hint d

An arbitrary integer, selected by the local CUCM which uniquely identifies a CallManager Group.

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..128) · OCTET STRING · hint 255t

The name of the CallManager Group.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

Whether this is the default TFTP server group or not.

CcmIndexThis syntax is used as the Index into a table. A positive value is used to identify a unique entry in the table. (1..4294967295) · Unsigned32 · hint d

An arbitrary integer, selected by the local CUCM, which uniquely identifies a CallManager in a call manager cluster.

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..128) · OCTET STRING · hint 255t

The host name of the CallManager.

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

The description for the CallManager.

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..24) · OCTET STRING · hint 255t

The version number of the CallManager software.

INTEGER1 = unknown2 = up3 = down · Integer32

The current status of the CallManager. A CallManager is up if the SNMP Agent received a system up event from the local CUCM unknown: Current status of the CallManager is Unknown up: CallManager is running & is able to communicate with other CallManagers down: CallManager is down or the Agent is unable to communicate with the local CallManager.

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

This object identifies IP address type of the Cisco Call Manager defined in ccmInetAddress.

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

This object identifies IP address of the Cisco Call Manager. The type of address for this is identified by ccmInetAddressType.

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..128) · OCTET STRING · hint 255t

The unique ID of the Cluster to which this CallManager belongs. At any point in time, the Cluster Id helps in associating a CallManager to any given Cluster.

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

This object identifies IP address type of the Cisco Unified Communications Manager defined in ccmInetAddress2.

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

This object identifies the additional IP(v4/v6) address details of Cisco Unified Communications Manager. The type of address for this object is identified by ccmInetAddress2Type.

Unsigned32

The priority of the CallManager in the group. Sets the order of the CallManager in the list.

CcmIndexThis syntax is used as the Index into a table. A positive value is used to identify a unique entry in the table. (1..4294967295) · Unsigned32 · hint d

An arbitrary integer, selected by the local CUCM, which uniquely identifies a Region Name in the table.

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..128) · OCTET STRING · hint 255t

The name of the CallManager region.

CcmIndexThis syntax is used as the Index into a table. A positive value is used to identify a unique entry in the table. (1..4294967295) · Unsigned32 · hint d

The index of the Source Region in the Region table.

CcmIndexThis syntax is used as the Index into a table. A positive value is used to identify a unique entry in the table. (1..4294967295) · Unsigned32 · hint d

The index of the Destination Region in the Region table.

INTEGER1 = unknown2 = other3 = bwG7234 = bwG7295 = bwG7116 = bwGSM7 = bwWideband · Integer32

The maximum available bandwidth between the two given regions. unknown: Unknown Bandwidth other: Unidentified Bandwidth bwG723: For low bandwidth using G.723 codec bwG729: For low bandwidth using G.729 codec bwG711: For high bandwidth using G.711 codec bwGSM: For GSM bandwidth 13K bwWideband: For Wideband 256K.

CcmIndexThis syntax is used as the Index into a table. A positive value is used to identify a unique entry in the table. (1..4294967295) · Unsigned32 · hint d

An arbitrary integer, selected by the local CUCM, which uniquely identifies a Time Zone group entry in the table.

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..128) · OCTET STRING · hint 255t

The name of the time zone group.

Integer32 (-12..12)

The offset of the time zone group's time zone from GMT.

Integer32 (-12..12)

The offset hours of the time zone group's time zone from GMT.

Integer32 (-59..59)

The offset minutes of the time zone group's time zone from GMT.

CcmIndexThis syntax is used as the Index into a table. A positive value is used to identify a unique entry in the table. (1..4294967295) · Unsigned32 · hint d

An arbitrary integer, selected by the local CUCM, which uniquely identifies a Device Pool entry in the table. Each entry contains Region, Date/Time Group and CallManager Group criteria that will be common among many devices, for that entry.

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..128) · OCTET STRING · hint 255t

The name of the device pool.

CcmIndexOrZeroThis textual convention is an extension of the CcmIndex convention. The latter defines a greater than zero to identify an entry of the CUCM MIB table in the managed system. This extension permits the additional value of zero. The value zero is object- specific and must be defined as part of the description of any object which uses this syntax. · Unsigned32 · hint d

A positive value of this index is used to identify the Region to which this Device Pool entry belongs. A value of 0 indicates that the index to the Region table is Unknown.

CcmIndexOrZeroThis textual convention is an extension of the CcmIndex convention. The latter defines a greater than zero to identify an entry of the CUCM MIB table in the managed system. This extension permits the additional value of zero. The value zero is object- specific and must be defined as part of the description of any object which uses this syntax. · Unsigned32 · hint d

A positive value of this index is used to identify the TimeZone to which this Device Pool entry belongs. A value of 0 indicates that the index to the TimeZone table is Unknown.

CcmIndexOrZeroThis textual convention is an extension of the CcmIndex convention. The latter defines a greater than zero to identify an entry of the CUCM MIB table in the managed system. This extension permits the additional value of zero. The value zero is object- specific and must be defined as part of the description of any object which uses this syntax. · Unsigned32 · hint d

A positive value of this index is used to identify the CallManager Group to which this Device Pool entry belongs. A value of 0 indicates that the index to the CallManager Group table is Unknown.

CcmIndexThis syntax is used as the Index into a table. A positive value is used to identify a unique entry in the table. (1..4294967295) · Unsigned32 · hint d

An arbitrary integer, selected by the local CUCM, which uniquely identifies an entry in the ccmProductTypeTable.

Unsigned32

The type of the product as defined in the CUCM database.

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..100) · OCTET STRING · hint 255t

The name of the product as defined in the CUCM database.

INTEGER-1 = unknown0 = notApplicable1 = phone2 = gateway3 = h323Device4 = ctiDevice5 = voiceMailDevice6 = mediaResourceDevice7 = huntListDevice8 = sipDevice · Integer32

The category of the product. unknown: Unknown product category notApplicable: Not Applicable phone: Phone gateway: Gateway h323Device: H323 Device ctiDevice: CTI Device voiceMailDevice: Voice Messaging Device mediaResourceDevice: Media Resource Device huntListDevice: Hunt List Device sipDevice: SIP Device.

CcmIndexThis syntax is used as the Index into a table. A positive value is used to identify a unique entry in the table. (1..4294967295) · Unsigned32 · hint d

An arbitrary integer, selected by the local CUCM, which uniquely identifies a Phone within the CallManager.

MacAddressRepresents an 802 MAC address represented in the `canonical' order defined by IEEE 802.1a, i.e., as if it were transmitted least significant bit first, even though 802.5 (in contrast to other 802.x protocols) requires MAC addresses to be transmitted most significant bit first. SIZE (6) · OCTET STRING · hint 1x:

The physical address(MAC address) of the IP phone.

INTEGER1 = unknown2 = other3 = cisco30SPplus4 = cisco12SPplus5 = cisco12SP6 = cisco12S7 = cisco30VIP8 = ciscoTeleCasterBid9 = ciscoTeleCasterMgr10 = ciscoTeleCasterBusiness11 = ciscoSoftPhone12 = ciscoConferencePhone13 = cisco790214 = cisco790515 = cisco791216 = cisco7970 · Integer32

The type of the phone device. unknown: Unknown phone type other: Unidentified phone type cisco30SPplus: IP Phone 30 SP+ cisco12SPplus: IP Phone 12 SP+ cisco12SP: IP Phone 12 SP cisco12S: IP Phone 12 S cisco30VIP: IP Phone 30 VIP ciscoTeleCasterBid: IP Phone Telecaster 7910 ciscoTeleCasterMgr: IP Phone Telecaster 7960 ciscoTeleCasterBusiness: IP Phone Telecaster 7940 ciscoSoftPhone: Softphone ciscoConferencePhone: IP Conference Station 7935 cisco7902: IP Phone 7902 cisco7905: IP Phone 7905 cisco7912: IP Phone 7912 cisco7970: IP Phone 7970.

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

The description about the phone itself.

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

The name of the user of the phone. When the phone is not in use, the name would refer to the last known user of the phone.

IpAddress SIZE (4)

The last known IP address of the phone.

CcmDeviceStatus1 = unknown2 = registered3 = unregistered4 = rejected5 = partiallyregisteredThis syntax is used to identify the registration status of a device with the local call manager. unknown: The registration status of the device is unknown registered: The device has successfully registered with the local call manager unregistered: The device is no longer registered with the local call manager rejected: Registration request from the device was rejected by the local call manager. partiallyregistered: At least one but not all of the lines are successfully registered to the local call manager. Applicable only to SIP phones. · Integer32

The status of the phone. The status of the Phone changes from Unknown to registered when it registers itself with the local CUCM.

DateAndTimeA date-time specification. field octets contents range ----- ------ -------- ----- 1 1-2 year* 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC* 0..13 10 11 minutes from UTC 0..59 * Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: 1992-5-26,13:30:15.0,-4:0 Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d

The time when the phone last registered with the CallManager.

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

The E911 location of the phone.

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..128) · OCTET STRING · hint 255t

This object identifies the configured load ID for the phone device.

Integer32 (-1..65535)

A positive value or 0 indicates the last error reported by the phone. A value of -1 indicates that the last error reported is Unknown.

DateAndTimeA date-time specification. field octets contents range ----- ------ -------- ----- 1 1-2 year* 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC* 0..13 10 11 minutes from UTC 0..59 * Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: 1992-5-26,13:30:15.0,-4:0 Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d

The amount of time elapsed since the last phone error occurred. The reference point for this time is the time the last error occurred, as reported by the local CUCM.

CcmIndexOrZeroThis textual convention is an extension of the CcmIndex convention. The latter defines a greater than zero to identify an entry of the CUCM MIB table in the managed system. This extension permits the additional value of zero. The value zero is object- specific and must be defined as part of the description of any object which uses this syntax. · Unsigned32 · hint d

A positive value of this index is used to identify the Device Pool to which this Phone entry belongs. A value of 0 indicates that the index to the Device Pool table is Unknown.

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

This object identifies the IP address type of the phone.

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

This object identifies the last known IP address of the phone. The type of address for this is identified by ccmPhoneInetAddressType.

CcmDevFailCauseCode0 = noError1 = unknown2 = noEntryInDatabase3 = databaseConfigurationError4 = deviceNameUnresolveable5 = maxDevRegReached6 = connectivityError7 = initializationError8 = deviceInitiatedReset9 = callManagerReset10 = authenticationError11 = invalidX509NameInCertificate12 = invalidTLSCipher13 = directoryNumberMismatch14 = malformedRegisterMsgThis syntax is used as means of identifying the reasons for a device communication error. noError: No Error unknown: Unknown error cause noEntryInDatabase: Device not configured properly in the CUCM database databaseConfigurationError: Device configuration error in the CUCM database deviceNameUnresolveable: The CallManager is unable to resolve the device name to an IP Address internally maxDevRegReached: Maximum number of device registrations have been reached connectivityError: CallManager is unable to establish communication with the device during registration initializationError: Indicates an error occurred when the CallManager tries to initialize the device deviceInitiatedReset: Indicates that the error was due to device initiated reset callManagerReset: Indicates that the error was due to call manager reset. authenticationError: Indicates mismatch between configured authentication mode and the authentication mode that the device is using to connect to the CallManager. invalidX509NameInCertificate: Indicates mismatch between the peer X.509 certificate subject name and what is configured for the device. invalidTLSCipher: Indicates Cipher mismatch during TLS handshake process. directoryNumberMismatch: Indicates mismatch between the directory number that the SIP device is trying to register with and the directory number configured in the CallManager for the SIP device. malformedRegisterMsg: Indicates that SIP device attempted to register with CallManager, but the REGISTER message contained formatting errors. · Integer32

The reason code associated with the phone status change.

DateAndTimeA date-time specification. field octets contents range ----- ------ -------- ----- 1 1-2 year* 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC* 0..13 10 11 minutes from UTC 0..59 * Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: 1992-5-26,13:30:15.0,-4:0 Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d

The time the status of the phone changed.

CcmIndexOrZeroThis textual convention is an extension of the CcmIndex convention. The latter defines a greater than zero to identify an entry of the CUCM MIB table in the managed system. This extension permits the additional value of zero. The value zero is object- specific and must be defined as part of the description of any object which uses this syntax. · Unsigned32 · hint d

A positive value of this index is used to identify the related product type entry in the ccmProductTypeTable. A value of 0 indicates that the index to the ccmProductTypeTable is Unknown.

CcmPhoneProtocolType1 = unknown2 = sccp3 = sipThis syntax is used to identify the protocol between phone and Cisco Call Manager. unknown: The phone protocol is unknown sccp: The phone protocol is SCCP sip: The phone protocol is SIP. · Integer32

The protocol used between the phone and Cisco Call Manager.

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..128) · OCTET STRING · hint 255t

The name of the phone. The name of the phone can be <prefix> + MAC Address, where <prefix> is SEP for Cisco SCCP and SIP Phones. In the case of other phones such as communicator (soft phone) it can be free-form name, a string which uniquely identifies the phone.

InetAddressIPv4Represents an IPv4 network address: Octets Contents Encoding 1-4 IPv4 address network-byte order The corresponding InetAddressType value is ipv4(1). This textual convention SHOULD NOT be used directly in object definitions, as it restricts addresses to a specific format. However, if it is used, it MAY be used either on its own or in conjunction with InetAddressType, as a pair. SIZE (4) · OCTET STRING · hint 1d.1d.1d.1d

This object identifies the last known primary IPv4 address of the Phone Device. This object contains value zero if IPV4 address is not available.

InetAddressIPv6Represents an IPv6 network address: Octets Contents Encoding 1-16 IPv6 address network-byte order The corresponding InetAddressType value is ipv6(2). This textual convention SHOULD NOT be used directly in object definitions, as it restricts addresses to a specific format. However, if it is used, it MAY be used either on its own or in conjunction with InetAddressType, as a pair. SIZE (16) · OCTET STRING · hint 2x:2x:2x:2x:2x:2x:2x:2x

This object identifies the last known primary IPv6 address of the Phone device. This object contains value zero if IPV6 address is not available

INTEGER0 = unknown1 = adminOnly2 = controlOnly3 = adminAndControl · Integer32

This object identifies the scope of ccmPhoneInetAddressIPv4. unknown(0): It is not known if ccmPhoneInetAddressIPv4 is used for Administration purpose or Controlling purpose. adminOnly(1): ccmPhoneInetAddressIPv4 is used for the serviceability/administrative purpose. controlOnly(2): ccmPhoneInetAddressIPv4 is used for signaling/registration purpose. adminAndControl(3): ccmPhoneInetAddressIPv4 is used for controlling as well as administrative purpose.

INTEGER0 = unknown1 = adminOnly2 = controlOnly3 = adminAndControl · Integer32

This object identifies the scope of ccmPhoneInetAddressIPv6. unknown(0): It is not known if ccmPhoneInetAddressIPv6 is used for Administration purpose or Controlling purpose. adminOnly(1): ccmPhoneInetAddressIPv6 is used for the serviceability/administrative purpose. controlOnly(2): ccmPhoneInetAddressIPv6 is used for signaling/registration purpose. adminAndControl(3):ccmPhoneInetAddressIPv6 is used for controlling as well as administrative purpose.

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 identifies the ID of actual load that is successfully loaded and running on the phone device. If the phone is successfully upgraded to the new load then ccmPhoneLoadID and ccmPhoneActiveLoadID will have same value. If the upgrade fails then the ccmPhoneLoadID has the configured load ID and ccmPhoneActiveLoadID has the actual load ID that is running on the phone.

CcmDevUnregCauseCode0 = noError1 = unknown2 = noEntryInDatabase3 = databaseConfigurationError4 = deviceNameUnresolveable5 = maxDevRegExceeded6 = connectivityError7 = initializationError8 = deviceInitiatedReset9 = callManagerReset10 = deviceUnregistered11 = malformedRegisterMsg12 = sccpDeviceThrottling13 = keepAliveTimeout14 = configurationMismatch15 = callManagerRestart16 = duplicateRegistration17 = callManagerApplyConfig18 = deviceNoResponse19 = emLoginLogout20 = emccLoginLogout21 = energywisePowerSavePlus22 = callManagerForcedRestart23 = sourceIPAddrChanged24 = sourcePortChanged25 = registrationSequenceError26 = invalidCapabilities28 = fallbackInitiated29 = deviceSwitchThis syntax is used as means of identifying the reasons for a device getting unregistered. The scope of this enumeration can expand to comply with RFC 2578. noError: No Error unknown: Unknown error cause noEntryInDatabase: Device not configured properly in the CUCM database databaseConfigurationError: Device configuration error in the CUCM database deviceNameUnresolveable: The CallManager is unable to resolve the device name to an IP Address internally maxDevRegExceeded: Maximum number of device registrations have been reached connectivityError: CallManager is unable to establish communication with the device during registration initializationError: Indicates an error occurred when the CallManager tries to initialize the device deviceInitiatedReset: Indicates that the error was due to device initiated reset callManagerReset: Indicates that the error was due to call manager reset. deviceUnregistered: DeviceUnregistered. malformedRegisterMsg: Indicates that SIP device attempted to register with CallManager, but the REGISTER message contained formatting errors. sccpDeviceThrottling: The indicated SCCP device exceeded the maximum number of events allowed per-SCCP device. keepAliveTimeout: A KeepAlive message was not received. Possible causes include device power outage, network power outage, network configuration error, network delay,packet drops, packet corruption and CUCM node experiencing high CPU usage. configurationMismatch: The configuration on the SIP device does not match the configuration in CUCM. callManagerRestart: A device restart was initiated from CUCM Administration, either due to an explicit command from an administrator or due to a configuration change such as adding, deleting or changing a directory number associated with the device. duplicateRegistration: CUCM detected that the device attempted to register to two nodes at the same time. CUCM initiated a restart to the phone to force it to re-home to a single node. callManagerApplyConfig: CUCM configuration is changed. deviceNoResponse: Device is not responding Service Control Notify from CUCM. emLoginLogout: The device has been unregistered due to an Extension Mobility login or logout. emccLoginLogout: The device has been unregistered due to an Extension Mobility Cross Cluster login or logout. powerSavePlus: The device powered off as a result of the Power Save Plus feature that is enabled for this device. When the device powers off, it remains unregistered from CUCM until the Phone On Time defined in the Product Specific Configuration for this device. callManagerForcedRestart: The device did not respond to an Apply Config request and as a result, CUCM had sent a restart request to the device. The device may be offline due to a power outage or network problem. Confirm that the device is powered-up and that network connectivity exists between the device and CUCM. This is applicable for SIP protocol only. sourceIPAddrChanged: The device has been unregistered because the IP address in the Contact header of the REGISTER message has changed. The device will be automatically re-registered. No action is necessary. This is applicable for SIP protocol only. sourcePortChanged: The device has been unregistered because the port number in the Contact header of the REGISTER message has changed. The device will be automatically re-registered. No action is necessary. This is applicable for SIP protocol only. registrationSequenceError: A device requested configuration information from the CUCM at an unexpected time. The CUCM no longer had the requested information in memory. invalidCapabilities: The CUCM detected an error in the updated media capabilities reported by the device. The device reported the capabilities in one of the StationUpdateCapabilities message variants. This is applicable for SCCP protocol only. fallbackInitiated The device has initiated a fallback and will automatically re-register to a higher-priority CUCM. No action is necessary. deviceSwitch A second instance of an endpoint with the same device name has registered and assumed control. No action is necessary. · Integer32

The reason code associated with unregistered phone.

CcmDevRegFailCauseCode0 = noError1 = unknown2 = noEntryInDatabase3 = databaseConfigurationError4 = deviceNameUnresolveable5 = maxDevRegExceeded6 = connectivityError7 = initializationError8 = deviceInitiatedReset9 = callManagerReset10 = authenticationError11 = invalidX509NameInCertificate12 = invalidTLSCipher13 = directoryNumberMismatch14 = malformedRegisterMsg15 = protocolMismatch16 = deviceNotActive17 = authenticatedDeviceAlreadyExists18 = obsoleteProtocolVersion23 = databaseTimeout25 = registrationSequenceError26 = invalidCapabilities27 = capabilityResponseTimeout28 = securityMismatch29 = autoRegisterDBError30 = dbAccessError31 = autoRegisterDBConfigTimeout32 = deviceTypeMismatch33 = addressingModeMismatchThis syntax is used as means of identifying the reasons for a device registration failure. The scope of this enumeration can expand to comply with RFC 2578. noError: No Error unknown: Unknown error cause noEntryInDatabase: Device not configured properly in the CUCM database databaseConfigurationError: Device configuration error in the CUCM database deviceNameUnresolveable: The CallManager is unable to resolve the device name to an IP Address internally maxDevRegExceeded: Maximum number of device registrations have been reached connectivityError: CallManager is unable to establish communication with the device during registration initializationError: Indicates an error occurred when the CallManager tries to initialize the device deviceInitiatedReset: Indicates that the error was due to device initiated reset callManagerReset: Indicates that the error was due to call manager reset. authenticationError: Indicates mismatch between configured authentication mode and the authentication mode that the device is using to connect to the CallManager. invalidX509NameInCertificate: Indicates mismatch between the peer X.509 certificate subject name and what is configured for the device. invalidTLSCipher: Indicates Cipher mismatch during TLS handshake process. directoryNumberMismatch: Indicates mismatch between the directory number that the SIP device is trying to register with and the directory number configured in the CallManager for the SIP device. malformedRegisterMsg: Indicates that SIP device attempted to register with CallManager, but the REGISTER message contained formatting errors. protocolMismatch: The protocol of the device (SIP or SCCP) does not match the configured protocol in CUCM. deviceNotActive: The device has not been activated. authenticatedDeviceAlreadyExists: A device with the same name is already registered with CUCM. obsoleteProtocolVersion: The SCCP device registered with an obsolete protocol version. databaseTimeout: CUCM requested device configuration data from the database but did not receive a response within 10 minutes. registrationSequenceError: A device requested configuration information from the CUCM at an unexpected time. The CUCM had not yet obtained the requested information. The device will automatically attempt to register again. If this alarm occurs again, manually reset the device. If this alarm continues to occur after the manual reset, there may be an internal firmware error. This is applicable for SCCP protocol only. invalidCapabilities: The CUCM detected an error in the media capabilities reported in the StationCapabilitiesRes message by the device during registration. The device will automatically attempt to register again. If this alarm occurs again, manually reset the device. If this alarm continues to occur after the manual reset, there may be a protocol error. This is applicable for SCCP protocol only. capabilityResponseTimeout: The CUCM timed out while waiting for the device to respond to a request to report its media capabilities. Possible causes include device power outage, network power outage, network configuration error, network delay, packet drops, and packet corruption. It is also possible to get this error if the CUCM node is experiencing high CPU usage. Verify that the device is powered up and operating. Verify that network connectivity exists between the device and CUCM, and verify that the CPU utilization is in the safe range. This is applicable for SCCP protocol only. securityMismatch: The CUCM detected a mismatch in the security settings of the device and/or the CUCM. The mismatches that can be detected are: 1) The device established a secure connection, yet reported that it does not have the ability to do authenticated signaling. 2) The device did not establish a secure connection, but the security mode configured for the device indicates that it should have done so. 3) The device established a secure connection, but the security mode configured for the device indicates that it should not have done so autoRegisterDBError: Auto-registration of a device failed for one of the following reasons: 1)Auto-registration is not allowed for the device type. 2)An error occurred while adding the auto-registering device to the database (stored procedure). dbAccessError: Device registration failed because of an error that occurred while building the station registration profile. This usually indicates a synchronization problem with the database. autoRegisterDBConfigTimeout: The CUCM timed out during auto-registration of a device. The registration profile of the device did not get inserted into the database in time. The device will automatically attempt to register again. This is applicable for SCCP protocol only. deviceTypeMismatch: The device type reported by the device does not match the device type configured on the CUCM addressingModeMismatch: The CUCM detected an error related to the addressing mode configured for the device. One of the following errors were detected: 1)The device is configured to use only IPv4 addressing, but did not specify an IPv4 address. 2)The device is configured to use only IPv6 addressing, but did not specify an IPv6 address. This is applicable for SCCP protocol only. · Integer32

The reason code associated with registration failed phone.

CcmIndexThis syntax is used as the Index into a table. A positive value is used to identify a unique entry in the table. (1..4294967295) · Unsigned32 · hint d

An arbitrary integer, selected by the local CUCM, which uniquely identifies a Phone Extension within the CallManager.

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..24) · OCTET STRING · hint 255t

The extension number of the extension.

IpAddress SIZE (4)

The IP address of the extension.

Unsigned32

The number of multiline appearances for each phone extension.

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

Represents the type of address stored in ccmPhoneExtensionInetAddress.

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 IP address of the extension.

CcmIndexThis syntax is used as the Index into a table. A positive value is used to identify a unique entry in the table. (1..4294967295) · Unsigned32 · hint d

An arbitrary integer, selected by the local CUCM, which is incremented with each new entry in the ccmPhoneFailedTable. This integer value will wrap if needed.

DateAndTimeA date-time specification. field octets contents range ----- ------ -------- ----- 1 1-2 year* 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC* 0..13 10 11 minutes from UTC 0..59 * Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: 1992-5-26,13:30:15.0,-4:0 Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d

The time when the phone failed to register with the CallManager.

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 name assigned to the phone when it is added to the CallManager. It contains an ASCII form of the phone's MAC Address.

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

This object identifies the IP address type of the phone that is experiencing communication failure. The value of this object is 'unknown(0)' if the IP address of a phone is not available.

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

This object identifies the last known IP address of the phone experiencing a communication failure. If the IP address of a device is not available then this object contains an empty string. The type of address for this is identified by ccmPhoneFailedInetAddressType

CcmDevFailCauseCode0 = noError1 = unknown2 = noEntryInDatabase3 = databaseConfigurationError4 = deviceNameUnresolveable5 = maxDevRegReached6 = connectivityError7 = initializationError8 = deviceInitiatedReset9 = callManagerReset10 = authenticationError11 = invalidX509NameInCertificate12 = invalidTLSCipher13 = directoryNumberMismatch14 = malformedRegisterMsgThis syntax is used as means of identifying the reasons for a device communication error. noError: No Error unknown: Unknown error cause noEntryInDatabase: Device not configured properly in the CUCM database databaseConfigurationError: Device configuration error in the CUCM database deviceNameUnresolveable: The CallManager is unable to resolve the device name to an IP Address internally maxDevRegReached: Maximum number of device registrations have been reached connectivityError: CallManager is unable to establish communication with the device during registration initializationError: Indicates an error occurred when the CallManager tries to initialize the device deviceInitiatedReset: Indicates that the error was due to device initiated reset callManagerReset: Indicates that the error was due to call manager reset. authenticationError: Indicates mismatch between configured authentication mode and the authentication mode that the device is using to connect to the CallManager. invalidX509NameInCertificate: Indicates mismatch between the peer X.509 certificate subject name and what is configured for the device. invalidTLSCipher: Indicates Cipher mismatch during TLS handshake process. directoryNumberMismatch: Indicates mismatch between the directory number that the SIP device is trying to register with and the directory number configured in the CallManager for the SIP device. malformedRegisterMsg: Indicates that SIP device attempted to register with CallManager, but the REGISTER message contained formatting errors. · Integer32

States the reason for the phone device communication error.

MacAddressRepresents an 802 MAC address represented in the `canonical' order defined by IEEE 802.1a, i.e., as if it were transmitted least significant bit first, even though 802.5 (in contrast to other 802.x protocols) requires MAC addresses to be transmitted most significant bit first. SIZE (6) · OCTET STRING · hint 1x:

The MAC address of the failed phone.

InetAddressIPv4Represents an IPv4 network address: Octets Contents Encoding 1-4 IPv4 address network-byte order The corresponding InetAddressType value is ipv4(1). This textual convention SHOULD NOT be used directly in object definitions, as it restricts addresses to a specific format. However, if it is used, it MAY be used either on its own or in conjunction with InetAddressType, as a pair. SIZE (4) · OCTET STRING · hint 1d.1d.1d.1d

This object identifies the last known primary IPv4 address of the phone experiencing a communication failure. This object contains value zero if IPV4 address is not available.

InetAddressIPv6Represents an IPv6 network address: Octets Contents Encoding 1-16 IPv6 address network-byte order The corresponding InetAddressType value is ipv6(2). This textual convention SHOULD NOT be used directly in object definitions, as it restricts addresses to a specific format. However, if it is used, it MAY be used either on its own or in conjunction with InetAddressType, as a pair. SIZE (16) · OCTET STRING · hint 2x:2x:2x:2x:2x:2x:2x:2x

This object identifies the last known primary IPv6 address of the phone experiencing a communication failure. This object contains value zero if IPV6 address is not available.

INTEGER0 = unknown1 = adminOnly2 = controlOnly3 = adminAndControl · Integer32

This object identifies the scope of ccmPhoneFailedInetAddressIPv4. unknown(0):It is not known if ccmPhoneFailedInetAddressIPv4 is used for Administration purpose or Controlling purpose. adminOnly(1): ccmPhoneFailedInetAddressIPv4 is used for the serviceability/administrative purpose. controlOnly(2): ccmPhoneFailedInetAddressIPv4 is used for signaling/registration purpose. adminAndControl(3): ccmPhoneFailedInetAddressIPv4 is used for controlling as well as administrative purpose.

INTEGER0 = unknown1 = adminOnly2 = controlOnly3 = adminAndControl · Integer32

This object identifies the scope of ccmPhoneFailedInetAddressIPv6. unknown(0):It is not known if ccmPhoneFailedInetAddressIPv6 is used for Administration purpose or Controlling purpose. adminOnly(1): ccmPhoneFailedInetAddressIPv6 is used for the serviceability/administrative purpose. controlOnly(2): ccmPhoneFailedInetAddressIPv6 is used for signaling/registration purpose. adminAndControl(3): ccmPhoneFailedInetAddressIPv6 is used for controlling as well as administrative purpose.

CcmDevRegFailCauseCode0 = noError1 = unknown2 = noEntryInDatabase3 = databaseConfigurationError4 = deviceNameUnresolveable5 = maxDevRegExceeded6 = connectivityError7 = initializationError8 = deviceInitiatedReset9 = callManagerReset10 = authenticationError11 = invalidX509NameInCertificate12 = invalidTLSCipher13 = directoryNumberMismatch14 = malformedRegisterMsg15 = protocolMismatch16 = deviceNotActive17 = authenticatedDeviceAlreadyExists18 = obsoleteProtocolVersion23 = databaseTimeout25 = registrationSequenceError26 = invalidCapabilities27 = capabilityResponseTimeout28 = securityMismatch29 = autoRegisterDBError30 = dbAccessError31 = autoRegisterDBConfigTimeout32 = deviceTypeMismatch33 = addressingModeMismatchThis syntax is used as means of identifying the reasons for a device registration failure. The scope of this enumeration can expand to comply with RFC 2578. noError: No Error unknown: Unknown error cause noEntryInDatabase: Device not configured properly in the CUCM database databaseConfigurationError: Device configuration error in the CUCM database deviceNameUnresolveable: The CallManager is unable to resolve the device name to an IP Address internally maxDevRegExceeded: Maximum number of device registrations have been reached connectivityError: CallManager is unable to establish communication with the device during registration initializationError: Indicates an error occurred when the CallManager tries to initialize the device deviceInitiatedReset: Indicates that the error was due to device initiated reset callManagerReset: Indicates that the error was due to call manager reset. authenticationError: Indicates mismatch between configured authentication mode and the authentication mode that the device is using to connect to the CallManager. invalidX509NameInCertificate: Indicates mismatch between the peer X.509 certificate subject name and what is configured for the device. invalidTLSCipher: Indicates Cipher mismatch during TLS handshake process. directoryNumberMismatch: Indicates mismatch between the directory number that the SIP device is trying to register with and the directory number configured in the CallManager for the SIP device. malformedRegisterMsg: Indicates that SIP device attempted to register with CallManager, but the REGISTER message contained formatting errors. protocolMismatch: The protocol of the device (SIP or SCCP) does not match the configured protocol in CUCM. deviceNotActive: The device has not been activated. authenticatedDeviceAlreadyExists: A device with the same name is already registered with CUCM. obsoleteProtocolVersion: The SCCP device registered with an obsolete protocol version. databaseTimeout: CUCM requested device configuration data from the database but did not receive a response within 10 minutes. registrationSequenceError: A device requested configuration information from the CUCM at an unexpected time. The CUCM had not yet obtained the requested information. The device will automatically attempt to register again. If this alarm occurs again, manually reset the device. If this alarm continues to occur after the manual reset, there may be an internal firmware error. This is applicable for SCCP protocol only. invalidCapabilities: The CUCM detected an error in the media capabilities reported in the StationCapabilitiesRes message by the device during registration. The device will automatically attempt to register again. If this alarm occurs again, manually reset the device. If this alarm continues to occur after the manual reset, there may be a protocol error. This is applicable for SCCP protocol only. capabilityResponseTimeout: The CUCM timed out while waiting for the device to respond to a request to report its media capabilities. Possible causes include device power outage, network power outage, network configuration error, network delay, packet drops, and packet corruption. It is also possible to get this error if the CUCM node is experiencing high CPU usage. Verify that the device is powered up and operating. Verify that network connectivity exists between the device and CUCM, and verify that the CPU utilization is in the safe range. This is applicable for SCCP protocol only. securityMismatch: The CUCM detected a mismatch in the security settings of the device and/or the CUCM. The mismatches that can be detected are: 1) The device established a secure connection, yet reported that it does not have the ability to do authenticated signaling. 2) The device did not establish a secure connection, but the security mode configured for the device indicates that it should have done so. 3) The device established a secure connection, but the security mode configured for the device indicates that it should not have done so autoRegisterDBError: Auto-registration of a device failed for one of the following reasons: 1)Auto-registration is not allowed for the device type. 2)An error occurred while adding the auto-registering device to the database (stored procedure). dbAccessError: Device registration failed because of an error that occurred while building the station registration profile. This usually indicates a synchronization problem with the database. autoRegisterDBConfigTimeout: The CUCM timed out during auto-registration of a device. The registration profile of the device did not get inserted into the database in time. The device will automatically attempt to register again. This is applicable for SCCP protocol only. deviceTypeMismatch: The device type reported by the device does not match the device type configured on the CUCM addressingModeMismatch: The CUCM detected an error related to the addressing mode configured for the device. One of the following errors were detected: 1)The device is configured to use only IPv4 addressing, but did not specify an IPv4 address. 2)The device is configured to use only IPv6 addressing, but did not specify an IPv6 address. This is applicable for SCCP protocol only. · Integer32

The reason code associated with registration failed phone.

CcmIndexThis syntax is used as the Index into a table. A positive value is used to identify a unique entry in the table. (1..4294967295) · Unsigned32 · hint d

An arbitrary integer, selected by the local CUCM, which is incremented with each new entry in the ccmPhoneStatusUpdateTable. This integer value will wrap if needed.

CcmIndexOrZeroThis textual convention is an extension of the CcmIndex convention. The latter defines a greater than zero to identify an entry of the CUCM MIB table in the managed system. This extension permits the additional value of zero. The value zero is object- specific and must be defined as part of the description of any object which uses this syntax. · Unsigned32 · hint d

A positive value of this index is used to identify an entry in the ccmPhoneTable. A value of 0 indicates that the index to the ccmPhoneTable is Unknown.

DateAndTimeA date-time specification. field octets contents range ----- ------ -------- ----- 1 1-2 year* 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC* 0..13 10 11 minutes from UTC 0..59 * Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: 1992-5-26,13:30:15.0,-4:0 Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d

The time of the phone's registration status change.

INTEGER1 = unknown2 = phoneRegistered3 = phoneUnregistered4 = phonePartiallyregistered · Integer32

States the type of phone status change. unknown: Unknown status phoneRegistered: Phone has registered with the Callmanager phoneUnregistered: Phone is no longer registered with the callmanager phonePartiallyregistered: Phone is partially registered with the callmanager.

CcmDevFailCauseCode0 = noError1 = unknown2 = noEntryInDatabase3 = databaseConfigurationError4 = deviceNameUnresolveable5 = maxDevRegReached6 = connectivityError7 = initializationError8 = deviceInitiatedReset9 = callManagerReset10 = authenticationError11 = invalidX509NameInCertificate12 = invalidTLSCipher13 = directoryNumberMismatch14 = malformedRegisterMsgThis syntax is used as means of identifying the reasons for a device communication error. noError: No Error unknown: Unknown error cause noEntryInDatabase: Device not configured properly in the CUCM database databaseConfigurationError: Device configuration error in the CUCM database deviceNameUnresolveable: The CallManager is unable to resolve the device name to an IP Address internally maxDevRegReached: Maximum number of device registrations have been reached connectivityError: CallManager is unable to establish communication with the device during registration initializationError: Indicates an error occurred when the CallManager tries to initialize the device deviceInitiatedReset: Indicates that the error was due to device initiated reset callManagerReset: Indicates that the error was due to call manager reset. authenticationError: Indicates mismatch between configured authentication mode and the authentication mode that the device is using to connect to the CallManager. invalidX509NameInCertificate: Indicates mismatch between the peer X.509 certificate subject name and what is configured for the device. invalidTLSCipher: Indicates Cipher mismatch during TLS handshake process. directoryNumberMismatch: Indicates mismatch between the directory number that the SIP device is trying to register with and the directory number configured in the CallManager for the SIP device. malformedRegisterMsg: Indicates that SIP device attempted to register with CallManager, but the REGISTER message contained formatting errors. · Integer32

The reason code associated with the phone status change.

CcmDevUnregCauseCode0 = noError1 = unknown2 = noEntryInDatabase3 = databaseConfigurationError4 = deviceNameUnresolveable5 = maxDevRegExceeded6 = connectivityError7 = initializationError8 = deviceInitiatedReset9 = callManagerReset10 = deviceUnregistered11 = malformedRegisterMsg12 = sccpDeviceThrottling13 = keepAliveTimeout14 = configurationMismatch15 = callManagerRestart16 = duplicateRegistration17 = callManagerApplyConfig18 = deviceNoResponse19 = emLoginLogout20 = emccLoginLogout21 = energywisePowerSavePlus22 = callManagerForcedRestart23 = sourceIPAddrChanged24 = sourcePortChanged25 = registrationSequenceError26 = invalidCapabilities28 = fallbackInitiated29 = deviceSwitchThis syntax is used as means of identifying the reasons for a device getting unregistered. The scope of this enumeration can expand to comply with RFC 2578. noError: No Error unknown: Unknown error cause noEntryInDatabase: Device not configured properly in the CUCM database databaseConfigurationError: Device configuration error in the CUCM database deviceNameUnresolveable: The CallManager is unable to resolve the device name to an IP Address internally maxDevRegExceeded: Maximum number of device registrations have been reached connectivityError: CallManager is unable to establish communication with the device during registration initializationError: Indicates an error occurred when the CallManager tries to initialize the device deviceInitiatedReset: Indicates that the error was due to device initiated reset callManagerReset: Indicates that the error was due to call manager reset. deviceUnregistered: DeviceUnregistered. malformedRegisterMsg: Indicates that SIP device attempted to register with CallManager, but the REGISTER message contained formatting errors. sccpDeviceThrottling: The indicated SCCP device exceeded the maximum number of events allowed per-SCCP device. keepAliveTimeout: A KeepAlive message was not received. Possible causes include device power outage, network power outage, network configuration error, network delay,packet drops, packet corruption and CUCM node experiencing high CPU usage. configurationMismatch: The configuration on the SIP device does not match the configuration in CUCM. callManagerRestart: A device restart was initiated from CUCM Administration, either due to an explicit command from an administrator or due to a configuration change such as adding, deleting or changing a directory number associated with the device. duplicateRegistration: CUCM detected that the device attempted to register to two nodes at the same time. CUCM initiated a restart to the phone to force it to re-home to a single node. callManagerApplyConfig: CUCM configuration is changed. deviceNoResponse: Device is not responding Service Control Notify from CUCM. emLoginLogout: The device has been unregistered due to an Extension Mobility login or logout. emccLoginLogout: The device has been unregistered due to an Extension Mobility Cross Cluster login or logout. powerSavePlus: The device powered off as a result of the Power Save Plus feature that is enabled for this device. When the device powers off, it remains unregistered from CUCM until the Phone On Time defined in the Product Specific Configuration for this device. callManagerForcedRestart: The device did not respond to an Apply Config request and as a result, CUCM had sent a restart request to the device. The device may be offline due to a power outage or network problem. Confirm that the device is powered-up and that network connectivity exists between the device and CUCM. This is applicable for SIP protocol only. sourceIPAddrChanged: The device has been unregistered because the IP address in the Contact header of the REGISTER message has changed. The device will be automatically re-registered. No action is necessary. This is applicable for SIP protocol only. sourcePortChanged: The device has been unregistered because the port number in the Contact header of the REGISTER message has changed. The device will be automatically re-registered. No action is necessary. This is applicable for SIP protocol only. registrationSequenceError: A device requested configuration information from the CUCM at an unexpected time. The CUCM no longer had the requested information in memory. invalidCapabilities: The CUCM detected an error in the updated media capabilities reported by the device. The device reported the capabilities in one of the StationUpdateCapabilities message variants. This is applicable for SCCP protocol only. fallbackInitiated The device has initiated a fallback and will automatically re-register to a higher-priority CUCM. No action is necessary. deviceSwitch A second instance of an endpoint with the same device name has registered and assumed control. No action is necessary. · Integer32

The reason code associated with unregistered phone.

CcmDevRegFailCauseCode0 = noError1 = unknown2 = noEntryInDatabase3 = databaseConfigurationError4 = deviceNameUnresolveable5 = maxDevRegExceeded6 = connectivityError7 = initializationError8 = deviceInitiatedReset9 = callManagerReset10 = authenticationError11 = invalidX509NameInCertificate12 = invalidTLSCipher13 = directoryNumberMismatch14 = malformedRegisterMsg15 = protocolMismatch16 = deviceNotActive17 = authenticatedDeviceAlreadyExists18 = obsoleteProtocolVersion23 = databaseTimeout25 = registrationSequenceError26 = invalidCapabilities27 = capabilityResponseTimeout28 = securityMismatch29 = autoRegisterDBError30 = dbAccessError31 = autoRegisterDBConfigTimeout32 = deviceTypeMismatch33 = addressingModeMismatchThis syntax is used as means of identifying the reasons for a device registration failure. The scope of this enumeration can expand to comply with RFC 2578. noError: No Error unknown: Unknown error cause noEntryInDatabase: Device not configured properly in the CUCM database databaseConfigurationError: Device configuration error in the CUCM database deviceNameUnresolveable: The CallManager is unable to resolve the device name to an IP Address internally maxDevRegExceeded: Maximum number of device registrations have been reached connectivityError: CallManager is unable to establish communication with the device during registration initializationError: Indicates an error occurred when the CallManager tries to initialize the device deviceInitiatedReset: Indicates that the error was due to device initiated reset callManagerReset: Indicates that the error was due to call manager reset. authenticationError: Indicates mismatch between configured authentication mode and the authentication mode that the device is using to connect to the CallManager. invalidX509NameInCertificate: Indicates mismatch between the peer X.509 certificate subject name and what is configured for the device. invalidTLSCipher: Indicates Cipher mismatch during TLS handshake process. directoryNumberMismatch: Indicates mismatch between the directory number that the SIP device is trying to register with and the directory number configured in the CallManager for the SIP device. malformedRegisterMsg: Indicates that SIP device attempted to register with CallManager, but the REGISTER message contained formatting errors. protocolMismatch: The protocol of the device (SIP or SCCP) does not match the configured protocol in CUCM. deviceNotActive: The device has not been activated. authenticatedDeviceAlreadyExists: A device with the same name is already registered with CUCM. obsoleteProtocolVersion: The SCCP device registered with an obsolete protocol version. databaseTimeout: CUCM requested device configuration data from the database but did not receive a response within 10 minutes. registrationSequenceError: A device requested configuration information from the CUCM at an unexpected time. The CUCM had not yet obtained the requested information. The device will automatically attempt to register again. If this alarm occurs again, manually reset the device. If this alarm continues to occur after the manual reset, there may be an internal firmware error. This is applicable for SCCP protocol only. invalidCapabilities: The CUCM detected an error in the media capabilities reported in the StationCapabilitiesRes message by the device during registration. The device will automatically attempt to register again. If this alarm occurs again, manually reset the device. If this alarm continues to occur after the manual reset, there may be a protocol error. This is applicable for SCCP protocol only. capabilityResponseTimeout: The CUCM timed out while waiting for the device to respond to a request to report its media capabilities. Possible causes include device power outage, network power outage, network configuration error, network delay, packet drops, and packet corruption. It is also possible to get this error if the CUCM node is experiencing high CPU usage. Verify that the device is powered up and operating. Verify that network connectivity exists between the device and CUCM, and verify that the CPU utilization is in the safe range. This is applicable for SCCP protocol only. securityMismatch: The CUCM detected a mismatch in the security settings of the device and/or the CUCM. The mismatches that can be detected are: 1) The device established a secure connection, yet reported that it does not have the ability to do authenticated signaling. 2) The device did not establish a secure connection, but the security mode configured for the device indicates that it should have done so. 3) The device established a secure connection, but the security mode configured for the device indicates that it should not have done so autoRegisterDBError: Auto-registration of a device failed for one of the following reasons: 1)Auto-registration is not allowed for the device type. 2)An error occurred while adding the auto-registering device to the database (stored procedure). dbAccessError: Device registration failed because of an error that occurred while building the station registration profile. This usually indicates a synchronization problem with the database. autoRegisterDBConfigTimeout: The CUCM timed out during auto-registration of a device. The registration profile of the device did not get inserted into the database in time. The device will automatically attempt to register again. This is applicable for SCCP protocol only. deviceTypeMismatch: The device type reported by the device does not match the device type configured on the CUCM addressingModeMismatch: The CUCM detected an error related to the addressing mode configured for the device. One of the following errors were detected: 1)The device is configured to use only IPv4 addressing, but did not specify an IPv4 address. 2)The device is configured to use only IPv6 addressing, but did not specify an IPv6 address. This is applicable for SCCP protocol only. · Integer32

The reason code associated with registration failed phone.

CcmIndexThis syntax is used as the Index into a table. A positive value is used to identify a unique entry in the table. (1..4294967295) · Unsigned32 · hint d

An arbitrary integer, selected by the local CUCM, which uniquely identifies a Phone Extension within the CallManager.

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..24) · OCTET STRING · hint 255t

The extension number of the extension.

Unsigned32

The number of multiline appearances for each phone extension.

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

This object identifies the IP address type of the phone extension.

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

This object identifies the IP address of the phone extension. The type of address for this is identified by ccmPhoneExtnInetAddressType.

CcmDeviceLineStatus1 = unknown2 = registered3 = unregistered4 = rejectedThis syntax is used to identify the registration status of a line of the device with the local call manager. unknown: The registration status of the device line is unknown registered: The device line has successfully registered with the local call manager unregistered: The device line is no longer registered with the local call manager rejected: Registration request from the device line was rejected by the local call manager. · Integer32

Represents the status of this phone line.

CcmIndexThis syntax is used as the Index into a table. A positive value is used to identify a unique entry in the table. (1..4294967295) · Unsigned32 · hint d

An arbitrary integer, selected by the local CUCM, which uniquely identifies a Gateway within the scope of the local call manager.

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..128) · OCTET STRING · hint 255t

This is the Gateway name assigned to the Gateway in the CallManager. This name is assigned when a new device of type Gateway is added to the CallManager.

INTEGER1 = unknown2 = other3 = ciscoAnalogAccess4 = ciscoDigitalAccessPRI5 = ciscoDigitalAccessT16 = ciscoDigitalAccessPRIPlus7 = ciscoDigitalAccessWSX6608E18 = ciscoDigitalAccessWSX6608T19 = ciscoAnalogAccessWSX662410 = ciscoMGCPStation11 = ciscoDigitalAccessE1Plus12 = ciscoDigitalAccessT1Plus13 = ciscoDigitalAccessWSX6608PRI14 = ciscoAnalogAccessWSX661215 = ciscoMGCPTrunk16 = ciscoVG20017 = cisco26XX18 = cisco362X19 = cisco364X20 = cisco366X21 = ciscoCat4224VoiceGatewaySwitch22 = ciscoCat4000AccessGatewayModule23 = ciscoIAD240024 = ciscoVGCEndPoint25 = ciscoVG224VG248Gateway26 = ciscoVGCBox27 = ciscoATA18628 = ciscoICS77XXMRP2XX29 = ciscoICS77XXASI8130 = ciscoICS77XXASI16031 = ciscoSlotVGCPort32 = ciscoCat6000AVVIDServModule33 = ciscoWSX660034 = ciscoWSSVCCMMMS35 = cisco374536 = cisco372537 = ciscoICS77XXMRP3XX38 = ciscoICS77XXMRP38FXS39 = ciscoICS77XXMRP316FXS40 = ciscoICS77XXMRP38FXOM141 = cisco269X42 = cisco176043 = cisco175144 = ciscoMGCPBRIPort · Integer32

The type of the gateway device. unknown(1): Unknown Gateway type other(2): Unidentified Gateway type ciscoAnalogAccess(3): Analog Access ciscoDigitalAccessPRI(4): Digital Access PRI ciscoDigitalAccessT1(5): Digital Access T1 ciscoDigitalAccessPRIPlus(6): Digital Access PRI Plus ciscoDigitalAccessWSX6608E1(7): Cat 6000 Digital Access E1 ciscoDigitalAccessWSX6608T1(8): Cat 6000 Digital Access T1 ciscoAnalogAccessWSX6624(9): Cat 6000 Analog Access FXS ciscoMGCPStation(10): MGCP Gateway ciscoDigitalAccessE1Plus(11): Digital Access E1 Plus ciscoDigitalAccessT1Plus(12): Digital Access T1 Plus ciscoDigitalAccessWSX6608PRI(13): Cat 6000 Digital Access PRI ciscoAnalogAccessWSX6612(14): Cat 6000 Analog Access FXO ciscoMGCPTrunk(15): MGCP Trunk ciscoVG200(16): VG200 cisco26XX(17): 26XX cisco362X(18): 362X cisco364X(19): 364X cisco366X(20): 366X ciscoCat4224VoiceGatewaySwitch(21): Cisco Catalyst 4224 Voice Gateway Switch ciscoCat4000AccessGatewayModule(22): Cisco Catalyst 4000 Access Gateway Module ciscoIAD2400(23): Cisco IAD2400 ciscoVGCEndPoint(24): Cisco VGC Phone ciscoVG224VG248Gateway(25): Cisco VGC Gateway ciscoVGCBox(26): Cisco VGC Box ciscoATA186(27): Cisco ATA 186 ciscoICS77XXMRP2XX(28): Cisco ICS77XX-MRP2XX ciscoICS77XXASI81(29): Cisco ICS77XX-ASI81 ciscoICS77XXASI160(30): Cisco ICS77XX-ASI160 ciscoSlotVGCPort(31): Cisco VGC Port ciscoCat6000AVVIDServModule(32): Cisco Catalyst 6000 AVVID Services Module ciscoWSX6600(33): WS-X6600 ciscoWSSVCCMMMS(34): Cisco WS-SVC-CMM-MS cisco3745(35): Cisco 3745 cisco3725(36): Cisco 3725 ciscoICS77XXMRP3XX(37): Cisco ICS77XX MRP3XX ciscoICS77XXMRP38FXS(38): Cisco ICS77XX MRP3 8FXS ciscoICS77XXMRP316FXS(39): Cisco ICS77XX MRP3 16FXS ciscoICS77XXMRP38FXOM1(40): Cisco ICS77XX MRP3 8FXO M1 cisco269X(41): Cisco 269X cisco1760(42): Cisco 1760 cisco1751(43): Cisco 1751 ciscoMGCPBRIPort(44) Cisco MGCP BRI Port.

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

The description attached to the gateway device.

CcmDeviceStatus1 = unknown2 = registered3 = unregistered4 = rejected5 = partiallyregisteredThis syntax is used to identify the registration status of a device with the local call manager. unknown: The registration status of the device is unknown registered: The device has successfully registered with the local call manager unregistered: The device is no longer registered with the local call manager rejected: Registration request from the device was rejected by the local call manager. partiallyregistered: At least one but not all of the lines are successfully registered to the local call manager. Applicable only to SIP phones. · Integer32

The status of the gateway. The Gateway status changes from Unknown to Registered when the Gateway registers itself with the local CUCM.

CcmIndexOrZeroThis textual convention is an extension of the CcmIndex convention. The latter defines a greater than zero to identify an entry of the CUCM MIB table in the managed system. This extension permits the additional value of zero. The value zero is object- specific and must be defined as part of the description of any object which uses this syntax. · Unsigned32 · hint d

A positive value of this index is used to identify the Device Pool to which this Gateway entry belongs. A value of 0 indicates that the index to the Device Pool table is Unknown.

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

This object identifies the IP address type of the Gateway device. The value of this object is 'unknown(0)' if the IP address of a Gateway device is not available.

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

This object identifies last known IP Address of the gateway. If the IP address is not available then this object contains an empty string. The type of address for this is identified by ccmGatewayInetAddressType.

CcmDeviceProductId-2 = other-1 = unknown1 = gwyCiscoCat6KT12 = gwyCiscoCat6KE13 = gwyCiscoCat6KFXS4 = gwyCiscoCat6KFXO7 = gwyCiscoDT24Plus8 = gwyCiscoDT30Plus9 = gwyCiscoDT2410 = gwyCiscoAT211 = gwyCiscoAT412 = gwyCiscoAT813 = gwyCiscoAS214 = gwyCiscoAS415 = gwyCiscoAS816 = h323Phone17 = h323Trunk18 = gwyCiscoMGCPFXOPort19 = gwyCiscoMGCPFXSPort27 = voiceMailUOnePort43 = gwyCiscoVG20044 = gwyCisco26XX45 = gwyCisco362X46 = gwyCisco364X47 = gwyCisco366X49 = h323AnonymousGatewy52 = gwyCiscoMGCPT1Port55 = gwyCiscoMGCPE1Port58 = gwyCiscoCat4224VoiceGwySwitch59 = gwyCiscoCat4000AccessGwyModule62 = gwyCiscoIAD240065 = gwyCiscoVGCEndPoint66 = gwyCiscoVG224AndV24867 = gwyCiscoSlotVGCPort68 = gwyCiscoVGCBox69 = gwyCiscoATA18670 = gwyCiscoICS77XXMRP2XX71 = gwyCiscoICS77XXASI8172 = gwyCiscoICS77XXASI16075 = h323H225GKControlledTrunk76 = h323ICTGKControlled77 = h323ICTNonGKControlled80 = gwyCiscoCat6000AVVIDServModule81 = gwyCiscoWSX660090 = gwyCiscoMGCPBRIPort95 = sipTrunk10001 = gwyCiscoWSSVCCMMMS20000 = gwyCisco374520002 = gwyCisco372530004 = gwyCiscoICS77XXMRP3XX30005 = gwyCiscoICS77XXMRP38FXS30006 = gwyCiscoICS77XXMRP316FXS30007 = gwyCiscoICS77XXMRP38FXOM130011 = gwyCisco269X30019 = gwyCisco176030020 = gwyCisco1751This syntax is used to identify the product id of a device. gwyCiscoCat6KT1(1): Cisco Catalyst 6000 T1 VoIP Gateway gwyCiscoCat6KE1(2): Cisco Catalyst 6000 E1 VoIP Gateway gwyCiscoCat6KFXS(3): Cisco Catalyst 6000 24 Port FXS Gateway gwyCiscoCat6KFXO(4): Cisco Catalyst 6000 12 Port FXO Gateway gwyCiscoDT24Plus(7): Cisco DT-24+ Gateway gwyCiscoDT30Plus(8): Cisco DT-30+ Gateway gwyCiscoDT24(9): Cisco DT-24 Gateway gwyCiscoAT2(10): Cisco AT2 Gateway gwyCiscoAT4(11): Cisco AT4 Gateway gwyCiscoAT8(12): Cisco AT8 Gateway gwyCiscoAS2(13): Cisco AS2 Gateway gwyCiscoAS4(14): Cisco AS4 Gateway gwyCiscoAS8(15): Cisco AS8 Gateway gwyCiscoMGCPFXOPort(18): Cisco MGCP FXO Port gwyCiscoMGCPFXSPort(19): Cisco MGCP FXS Port gwyCiscoVG200(43): Cisco VG200 gwyCisco26XX(44): Cisco 26XX gwyCisco362X(45): Cisco 362X gwyCisco364X(46): Cisco 364X gwyCisco366X(47): Cisco 366X gwyCiscoMGCPT1Port(52): Cisco MGCP T1 Port gwyCiscoMGCPE1Port(55): Cisco MGCP E1 Port gwyCiscoCat4224VoiceGwySwitch(58): Cisco CAT 4224 Voice Gateway Switch gwyCiscoCat4000AccessGwyModule(59): Cisco CAT 4000 Access Gateway Module gwyCiscoIAD2400(62): Cisco IAD2400 gwyCiscoVGCEndPoint(65): Cisco VGC PHONE gwyCiscoVG224AndV248(66): Cisco VGC Gateway gwyCiscoSlotVGCPort(67): Cisco VGC Port gwyciscoVGCBox(68): Cisco VGC Box gwyCiscoATA186(69): Cisco ATA 186 gwyCiscoICS77XXMRP2XX(70): Cisco ICS77XX-MRP2XX gwyCiscoICS77XXASI81(71): Cisco ICS77XX-ASI81 gwyCiscoICS77XXASI160(72): Cisco ICS77XX-ASI160 gwyCiscoCat6000AVVIDServModule(80): Cisco Catalyst 6000 AVVID Services Module gwyCiscoWSX6600(81): Cisco WS-X6600 gwyCiscoMGCPBRIPort(90): Cisco MGCP BRI Port gwyCiscoWSSVCCMMMS(10001): Cisco WS-SVC-CMM-MS gwyCisco3745(20000): Cisco 3745 gwyCisco3725(20002): Cisco 3725 gwyCiscoICS77XXMRP3XX(30004): Cisco ICS77XX MRP3XX gwyCiscoICS77XXMRP38FXS(30005): Cisco ICS77XX MRP3 8FXS gwyCiscoICS77XXMRP316FXS(30006): Cisco ICS77XX MRP3 16FXS gwyCiscoICS77XXMRP38FXOM1(30007): Cisco ICS77XX MRP3 8FXO M1 gwyCisco269X(30011): Cisco 269X gwyCisco1760(30019): Cisco 1760 gwyCisco1751(30020): Cisco 1751 h323Phone(16): H323 Phone h323Trunk(17): H323 Trunk h323AnonymousGateway(49): H323 Anonymous Gateway h323H225GKControlledTrunk(75): H225 Trunk Gatekeeper Controlled h323ICTGKControlled(76): Inter-Cluster Trunk Gatekeeper Controlled h323ICTNonGKControlled(77): Inter-Cluster Trunk Non-Gatekeeper Controlled voiceMailUOnePort(27): Uone Port sipTrunk(95): SIP Trunk unknown(-1): Unknown Device Product Id other(-2): Unidentified Device Product Id. · Integer32

The product identifier of the gateway device.

CcmDevFailCauseCode0 = noError1 = unknown2 = noEntryInDatabase3 = databaseConfigurationError4 = deviceNameUnresolveable5 = maxDevRegReached6 = connectivityError7 = initializationError8 = deviceInitiatedReset9 = callManagerReset10 = authenticationError11 = invalidX509NameInCertificate12 = invalidTLSCipher13 = directoryNumberMismatch14 = malformedRegisterMsgThis syntax is used as means of identifying the reasons for a device communication error. noError: No Error unknown: Unknown error cause noEntryInDatabase: Device not configured properly in the CUCM database databaseConfigurationError: Device configuration error in the CUCM database deviceNameUnresolveable: The CallManager is unable to resolve the device name to an IP Address internally maxDevRegReached: Maximum number of device registrations have been reached connectivityError: CallManager is unable to establish communication with the device during registration initializationError: Indicates an error occurred when the CallManager tries to initialize the device deviceInitiatedReset: Indicates that the error was due to device initiated reset callManagerReset: Indicates that the error was due to call manager reset. authenticationError: Indicates mismatch between configured authentication mode and the authentication mode that the device is using to connect to the CallManager. invalidX509NameInCertificate: Indicates mismatch between the peer X.509 certificate subject name and what is configured for the device. invalidTLSCipher: Indicates Cipher mismatch during TLS handshake process. directoryNumberMismatch: Indicates mismatch between the directory number that the SIP device is trying to register with and the directory number configured in the CallManager for the SIP device. malformedRegisterMsg: Indicates that SIP device attempted to register with CallManager, but the REGISTER message contained formatting errors. · Integer32

The reason code associated with the gateway status change.

DateAndTimeA date-time specification. field octets contents range ----- ------ -------- ----- 1 1-2 year* 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC* 0..13 10 11 minutes from UTC 0..59 * Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: 1992-5-26,13:30:15.0,-4:0 Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d

The time the status of the gateway changed.

DateAndTimeA date-time specification. field octets contents range ----- ------ -------- ----- 1 1-2 year* 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC* 0..13 10 11 minutes from UTC 0..59 * Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: 1992-5-26,13:30:15.0,-4:0 Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d

The time the gateway last registered with the call manager.

INTEGER1 = active2 = inActive3 = unknown4 = notApplicable · Integer32

The D-Channel status of the gateway. active(1): The D-Channel is up inActive(1): The D-Channel is down unknown(3): The D-Channel status is unknown notApplicable(4): The D-channel status is not applicable for this gateway.

Integer32 (-1..24)

The D-Channel number of the gateway. A value of -1 in this field indicates that the DChannel number is not applicable for this gateway.

CcmIndexOrZeroThis textual convention is an extension of the CcmIndex convention. The latter defines a greater than zero to identify an entry of the CUCM MIB table in the managed system. This extension permits the additional value of zero. The value zero is object- specific and must be defined as part of the description of any object which uses this syntax. · Unsigned32 · hint d

A positive value of this index is used to identify the related product type entry in the ccmProductTypeTable. A value of 0 indicates that the index to the ccmProductTypeTable is Unknown.

CcmDevUnregCauseCode0 = noError1 = unknown2 = noEntryInDatabase3 = databaseConfigurationError4 = deviceNameUnresolveable5 = maxDevRegExceeded6 = connectivityError7 = initializationError8 = deviceInitiatedReset9 = callManagerReset10 = deviceUnregistered11 = malformedRegisterMsg12 = sccpDeviceThrottling13 = keepAliveTimeout14 = configurationMismatch15 = callManagerRestart16 = duplicateRegistration17 = callManagerApplyConfig18 = deviceNoResponse19 = emLoginLogout20 = emccLoginLogout21 = energywisePowerSavePlus22 = callManagerForcedRestart23 = sourceIPAddrChanged24 = sourcePortChanged25 = registrationSequenceError26 = invalidCapabilities28 = fallbackInitiated29 = deviceSwitchThis syntax is used as means of identifying the reasons for a device getting unregistered. The scope of this enumeration can expand to comply with RFC 2578. noError: No Error unknown: Unknown error cause noEntryInDatabase: Device not configured properly in the CUCM database databaseConfigurationError: Device configuration error in the CUCM database deviceNameUnresolveable: The CallManager is unable to resolve the device name to an IP Address internally maxDevRegExceeded: Maximum number of device registrations have been reached connectivityError: CallManager is unable to establish communication with the device during registration initializationError: Indicates an error occurred when the CallManager tries to initialize the device deviceInitiatedReset: Indicates that the error was due to device initiated reset callManagerReset: Indicates that the error was due to call manager reset. deviceUnregistered: DeviceUnregistered. malformedRegisterMsg: Indicates that SIP device attempted to register with CallManager, but the REGISTER message contained formatting errors. sccpDeviceThrottling: The indicated SCCP device exceeded the maximum number of events allowed per-SCCP device. keepAliveTimeout: A KeepAlive message was not received. Possible causes include device power outage, network power outage, network configuration error, network delay,packet drops, packet corruption and CUCM node experiencing high CPU usage. configurationMismatch: The configuration on the SIP device does not match the configuration in CUCM. callManagerRestart: A device restart was initiated from CUCM Administration, either due to an explicit command from an administrator or due to a configuration change such as adding, deleting or changing a directory number associated with the device. duplicateRegistration: CUCM detected that the device attempted to register to two nodes at the same time. CUCM initiated a restart to the phone to force it to re-home to a single node. callManagerApplyConfig: CUCM configuration is changed. deviceNoResponse: Device is not responding Service Control Notify from CUCM. emLoginLogout: The device has been unregistered due to an Extension Mobility login or logout. emccLoginLogout: The device has been unregistered due to an Extension Mobility Cross Cluster login or logout. powerSavePlus: The device powered off as a result of the Power Save Plus feature that is enabled for this device. When the device powers off, it remains unregistered from CUCM until the Phone On Time defined in the Product Specific Configuration for this device. callManagerForcedRestart: The device did not respond to an Apply Config request and as a result, CUCM had sent a restart request to the device. The device may be offline due to a power outage or network problem. Confirm that the device is powered-up and that network connectivity exists between the device and CUCM. This is applicable for SIP protocol only. sourceIPAddrChanged: The device has been unregistered because the IP address in the Contact header of the REGISTER message has changed. The device will be automatically re-registered. No action is necessary. This is applicable for SIP protocol only. sourcePortChanged: The device has been unregistered because the port number in the Contact header of the REGISTER message has changed. The device will be automatically re-registered. No action is necessary. This is applicable for SIP protocol only. registrationSequenceError: A device requested configuration information from the CUCM at an unexpected time. The CUCM no longer had the requested information in memory. invalidCapabilities: The CUCM detected an error in the updated media capabilities reported by the device. The device reported the capabilities in one of the StationUpdateCapabilities message variants. This is applicable for SCCP protocol only. fallbackInitiated The device has initiated a fallback and will automatically re-register to a higher-priority CUCM. No action is necessary. deviceSwitch A second instance of an endpoint with the same device name has registered and assumed control. No action is necessary. · Integer32

The reason code associated with unregistered gateway.

CcmDevRegFailCauseCode0 = noError1 = unknown2 = noEntryInDatabase3 = databaseConfigurationError4 = deviceNameUnresolveable5 = maxDevRegExceeded6 = connectivityError7 = initializationError8 = deviceInitiatedReset9 = callManagerReset10 = authenticationError11 = invalidX509NameInCertificate12 = invalidTLSCipher13 = directoryNumberMismatch14 = malformedRegisterMsg15 = protocolMismatch16 = deviceNotActive17 = authenticatedDeviceAlreadyExists18 = obsoleteProtocolVersion23 = databaseTimeout25 = registrationSequenceError26 = invalidCapabilities27 = capabilityResponseTimeout28 = securityMismatch29 = autoRegisterDBError30 = dbAccessError31 = autoRegisterDBConfigTimeout32 = deviceTypeMismatch33 = addressingModeMismatchThis syntax is used as means of identifying the reasons for a device registration failure. The scope of this enumeration can expand to comply with RFC 2578. noError: No Error unknown: Unknown error cause noEntryInDatabase: Device not configured properly in the CUCM database databaseConfigurationError: Device configuration error in the CUCM database deviceNameUnresolveable: The CallManager is unable to resolve the device name to an IP Address internally maxDevRegExceeded: Maximum number of device registrations have been reached connectivityError: CallManager is unable to establish communication with the device during registration initializationError: Indicates an error occurred when the CallManager tries to initialize the device deviceInitiatedReset: Indicates that the error was due to device initiated reset callManagerReset: Indicates that the error was due to call manager reset. authenticationError: Indicates mismatch between configured authentication mode and the authentication mode that the device is using to connect to the CallManager. invalidX509NameInCertificate: Indicates mismatch between the peer X.509 certificate subject name and what is configured for the device. invalidTLSCipher: Indicates Cipher mismatch during TLS handshake process. directoryNumberMismatch: Indicates mismatch between the directory number that the SIP device is trying to register with and the directory number configured in the CallManager for the SIP device. malformedRegisterMsg: Indicates that SIP device attempted to register with CallManager, but the REGISTER message contained formatting errors. protocolMismatch: The protocol of the device (SIP or SCCP) does not match the configured protocol in CUCM. deviceNotActive: The device has not been activated. authenticatedDeviceAlreadyExists: A device with the same name is already registered with CUCM. obsoleteProtocolVersion: The SCCP device registered with an obsolete protocol version. databaseTimeout: CUCM requested device configuration data from the database but did not receive a response within 10 minutes. registrationSequenceError: A device requested configuration information from the CUCM at an unexpected time. The CUCM had not yet obtained the requested information. The device will automatically attempt to register again. If this alarm occurs again, manually reset the device. If this alarm continues to occur after the manual reset, there may be an internal firmware error. This is applicable for SCCP protocol only. invalidCapabilities: The CUCM detected an error in the media capabilities reported in the StationCapabilitiesRes message by the device during registration. The device will automatically attempt to register again. If this alarm occurs again, manually reset the device. If this alarm continues to occur after the manual reset, there may be a protocol error. This is applicable for SCCP protocol only. capabilityResponseTimeout: The CUCM timed out while waiting for the device to respond to a request to report its media capabilities. Possible causes include device power outage, network power outage, network configuration error, network delay, packet drops, and packet corruption. It is also possible to get this error if the CUCM node is experiencing high CPU usage. Verify that the device is powered up and operating. Verify that network connectivity exists between the device and CUCM, and verify that the CPU utilization is in the safe range. This is applicable for SCCP protocol only. securityMismatch: The CUCM detected a mismatch in the security settings of the device and/or the CUCM. The mismatches that can be detected are: 1) The device established a secure connection, yet reported that it does not have the ability to do authenticated signaling. 2) The device did not establish a secure connection, but the security mode configured for the device indicates that it should have done so. 3) The device established a secure connection, but the security mode configured for the device indicates that it should not have done so autoRegisterDBError: Auto-registration of a device failed for one of the following reasons: 1)Auto-registration is not allowed for the device type. 2)An error occurred while adding the auto-registering device to the database (stored procedure). dbAccessError: Device registration failed because of an error that occurred while building the station registration profile. This usually indicates a synchronization problem with the database. autoRegisterDBConfigTimeout: The CUCM timed out during auto-registration of a device. The registration profile of the device did not get inserted into the database in time. The device will automatically attempt to register again. This is applicable for SCCP protocol only. deviceTypeMismatch: The device type reported by the device does not match the device type configured on the CUCM addressingModeMismatch: The CUCM detected an error related to the addressing mode configured for the device. One of the following errors were detected: 1)The device is configured to use only IPv4 addressing, but did not specify an IPv4 address. 2)The device is configured to use only IPv6 addressing, but did not specify an IPv6 address. This is applicable for SCCP protocol only. · Integer32

The reason code associated with registration failed gateway.

CcmIndexThis syntax is used as the Index into a table. A positive value is used to identify a unique entry in the table. (1..4294967295) · Unsigned32 · hint d

An arbitrary integer, selected by the local CUCM, which uniquely identifies a Gateway trunk within the scope of a CallManager.

INTEGER1 = unknown2 = other3 = trunkGroundStart4 = trunkLoopStart5 = trunkDID6 = trunkPOTS7 = trunkEM18 = trunkEM29 = trunkEM310 = trunkEM411 = trunkEM512 = analog13 = pri14 = bri · Integer32

The type of the gateway Trunk. unknown: Unknown Trunk other: Unidentified Trunk type trunkGroundStart: Provides Far-End Disconnect Supervision trunkLoopStart: Provides No Far-End Disconnect Supervision trunkDID: Direct Inward Dial trunkPOTS: Plain Old Telephone Service trunkEM1: E&M Type 1 trunkEM2: E&M Type 2 trunkEM3: E&M Type 3 trunkEM4: E&M Type 4 trunkEM5: E&M Type 5 analog: Analog pri: PRI bri: BRI.

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..128) · OCTET STRING · hint 255t

The name of the trunk.

CcmIndexOrZeroThis textual convention is an extension of the CcmIndex convention. The latter defines a greater than zero to identify an entry of the CUCM MIB table in the managed system. This extension permits the additional value of zero. The value zero is object- specific and must be defined as part of the description of any object which uses this syntax. · Unsigned32 · hint d

A positive value of this index is used to identify the Gateway to which this Trunk entry belongs. A value of 0 indicates that the index to the Gateway table is Unknown.

INTEGER1 = unknown2 = up3 = busy4 = down · Integer32

The state of the trunk. The Trunk status changes from Unknown to Up when it registers itself with the local CUCM. unknown: Unknown state of Trunk up: Up and running, and is Idle with no calls busy: The trunk is in a Busy state down: The trunk is Down.

CcmIndexThis syntax is used as the Index into a table. A positive value is used to identify a unique entry in the table. (1..4294967295) · Unsigned32 · hint d

An arbitrary integer, selected by the local CUCM, which identifies a Media Device entry in the table.

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..128) · OCTET STRING · hint 255t

This is the device name assigned to the Media Device. This name is assigned when a new device of this type is added to the CallManager.

INTEGER1 = unknown2 = ciscoMediaTerminPointWSX66083 = ciscoConfBridgeWSX66084 = ciscoSwMediaTerminationPoint5 = ciscoSwConfBridge6 = ciscoMusicOnHold7 = ciscoToneAnnouncementPlayer8 = ciscoConfBridgeWSSVCCMM9 = ciscoMediaServerWSSVCCMMMS10 = ciscoMTPWSSVCCMM11 = ciscoIOSSWMTPHDV212 = ciscoIOSConfBridgeHDV213 = ciscoIOSMTPHDV214 = ciscoVCBIPVC35XX · Integer32

The type of Media Device. unknown(1): Unknown Media Device ciscoMediaTerminPointWSX6608(2): Hardware based Media Termination Point WSX6608 ciscoConfBridgeWSX6608(3): Hardware based Conference Bridge WSX6608 ciscoSwMediaTerminationPoint(4): Software based Media Termination Point ciscoSwConfBridge(5): Software based Conference Bridge ciscoMusicOnHold(6): Music on Hold Server ciscoToneAnnouncementPlayer(7): Tone Announcement Player ciscoConfBridgeWSSVCCMM(8): Conference Bridge WS-SVC-CMM ciscoMediaServerWSSVCCMMMS(9): Media Server WS-SVC-CMM-MS ciscoMTPWSSVCCMM(10): Media Termination Point WS-SVC-CMM ciscoIOSSWMTPHDV2(11): IOS Software Media Termination Point HDV2 ciscoIOSConfBridgeHDV2(12): IOS Conference Bridge HDV2 ciscoIOSMTPHDV2(13): IOS Media Termination Point HDV2 ciscoVCBIPVC35XX(14): Video Conference Bridge IPVC 35XX.

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..128) · OCTET STRING · hint 255t

A description of the Media Device. This description is given when the device is configured in the CUCM.

CcmDeviceStatus1 = unknown2 = registered3 = unregistered4 = rejected5 = partiallyregisteredThis syntax is used to identify the registration status of a device with the local call manager. unknown: The registration status of the device is unknown registered: The device has successfully registered with the local call manager unregistered: The device is no longer registered with the local call manager rejected: Registration request from the device was rejected by the local call manager. partiallyregistered: At least one but not all of the lines are successfully registered to the local call manager. Applicable only to SIP phones. · Integer32

The status of the Media Device. The status changes from unknown to registered when it registers itself with the local CUCM.

CcmIndexOrZeroThis textual convention is an extension of the CcmIndex convention. The latter defines a greater than zero to identify an entry of the CUCM MIB table in the managed system. This extension permits the additional value of zero. The value zero is object- specific and must be defined as part of the description of any object which uses this syntax. · Unsigned32 · hint d

A positive value of this index is used to identify the Device Pool to which this MediaDevice entry belongs. A value of 0 indicates that the index to the Device Pool table is Unknown.

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

This object identifies the IP address type of the Media Device. The value of this object is 'unknown(0)' if the IP address of a Media Device is not available.

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

This object identifies last known IP Address of the Media Device. If the IP Address is not available then this object contains an empty string. The type of address for this is identified by ccmMediaDeviceInetAddressType.

CcmDevFailCauseCode0 = noError1 = unknown2 = noEntryInDatabase3 = databaseConfigurationError4 = deviceNameUnresolveable5 = maxDevRegReached6 = connectivityError7 = initializationError8 = deviceInitiatedReset9 = callManagerReset10 = authenticationError11 = invalidX509NameInCertificate12 = invalidTLSCipher13 = directoryNumberMismatch14 = malformedRegisterMsgThis syntax is used as means of identifying the reasons for a device communication error. noError: No Error unknown: Unknown error cause noEntryInDatabase: Device not configured properly in the CUCM database databaseConfigurationError: Device configuration error in the CUCM database deviceNameUnresolveable: The CallManager is unable to resolve the device name to an IP Address internally maxDevRegReached: Maximum number of device registrations have been reached connectivityError: CallManager is unable to establish communication with the device during registration initializationError: Indicates an error occurred when the CallManager tries to initialize the device deviceInitiatedReset: Indicates that the error was due to device initiated reset callManagerReset: Indicates that the error was due to call manager reset. authenticationError: Indicates mismatch between configured authentication mode and the authentication mode that the device is using to connect to the CallManager. invalidX509NameInCertificate: Indicates mismatch between the peer X.509 certificate subject name and what is configured for the device. invalidTLSCipher: Indicates Cipher mismatch during TLS handshake process. directoryNumberMismatch: Indicates mismatch between the directory number that the SIP device is trying to register with and the directory number configured in the CallManager for the SIP device. malformedRegisterMsg: Indicates that SIP device attempted to register with CallManager, but the REGISTER message contained formatting errors. · Integer32

The reason code associated with the media device status change.

DateAndTimeA date-time specification. field octets contents range ----- ------ -------- ----- 1 1-2 year* 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC* 0..13 10 11 minutes from UTC 0..59 * Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: 1992-5-26,13:30:15.0,-4:0 Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d

The time the status of the media device changed.

DateAndTimeA date-time specification. field octets contents range ----- ------ -------- ----- 1 1-2 year* 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC* 0..13 10 11 minutes from UTC 0..59 * Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: 1992-5-26,13:30:15.0,-4:0 Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d

The time the media device last registered with the call manager.

CcmIndexOrZeroThis textual convention is an extension of the CcmIndex convention. The latter defines a greater than zero to identify an entry of the CUCM MIB table in the managed system. This extension permits the additional value of zero. The value zero is object- specific and must be defined as part of the description of any object which uses this syntax. · Unsigned32 · hint d

A positive value of this index is used to identify the related product type entry in the ccmProductTypeTable. A value of 0 indicates that the index to the ccmProductTypeTable is Unknown.

InetAddressIPv4Represents an IPv4 network address: Octets Contents Encoding 1-4 IPv4 address network-byte order The corresponding InetAddressType value is ipv4(1). This textual convention SHOULD NOT be used directly in object definitions, as it restricts addresses to a specific format. However, if it is used, it MAY be used either on its own or in conjunction with InetAddressType, as a pair. SIZE (4) · OCTET STRING · hint 1d.1d.1d.1d

This object identifies the last known primary IPv4 address of the Media Device. This object contains value zero if IPV4 address is not available

InetAddressIPv6Represents an IPv6 network address: Octets Contents Encoding 1-16 IPv6 address network-byte order The corresponding InetAddressType value is ipv6(2). This textual convention SHOULD NOT be used directly in object definitions, as it restricts addresses to a specific format. However, if it is used, it MAY be used either on its own or in conjunction with InetAddressType, as a pair. SIZE (16) · OCTET STRING · hint 2x:2x:2x:2x:2x:2x:2x:2x

This object identifies the last known primary IPv6 address of the Media Device. This object contains value zero if IPV6 address is not available.

CcmDevUnregCauseCode0 = noError1 = unknown2 = noEntryInDatabase3 = databaseConfigurationError4 = deviceNameUnresolveable5 = maxDevRegExceeded6 = connectivityError7 = initializationError8 = deviceInitiatedReset9 = callManagerReset10 = deviceUnregistered11 = malformedRegisterMsg12 = sccpDeviceThrottling13 = keepAliveTimeout14 = configurationMismatch15 = callManagerRestart16 = duplicateRegistration17 = callManagerApplyConfig18 = deviceNoResponse19 = emLoginLogout20 = emccLoginLogout21 = energywisePowerSavePlus22 = callManagerForcedRestart23 = sourceIPAddrChanged24 = sourcePortChanged25 = registrationSequenceError26 = invalidCapabilities28 = fallbackInitiated29 = deviceSwitchThis syntax is used as means of identifying the reasons for a device getting unregistered. The scope of this enumeration can expand to comply with RFC 2578. noError: No Error unknown: Unknown error cause noEntryInDatabase: Device not configured properly in the CUCM database databaseConfigurationError: Device configuration error in the CUCM database deviceNameUnresolveable: The CallManager is unable to resolve the device name to an IP Address internally maxDevRegExceeded: Maximum number of device registrations have been reached connectivityError: CallManager is unable to establish communication with the device during registration initializationError: Indicates an error occurred when the CallManager tries to initialize the device deviceInitiatedReset: Indicates that the error was due to device initiated reset callManagerReset: Indicates that the error was due to call manager reset. deviceUnregistered: DeviceUnregistered. malformedRegisterMsg: Indicates that SIP device attempted to register with CallManager, but the REGISTER message contained formatting errors. sccpDeviceThrottling: The indicated SCCP device exceeded the maximum number of events allowed per-SCCP device. keepAliveTimeout: A KeepAlive message was not received. Possible causes include device power outage, network power outage, network configuration error, network delay,packet drops, packet corruption and CUCM node experiencing high CPU usage. configurationMismatch: The configuration on the SIP device does not match the configuration in CUCM. callManagerRestart: A device restart was initiated from CUCM Administration, either due to an explicit command from an administrator or due to a configuration change such as adding, deleting or changing a directory number associated with the device. duplicateRegistration: CUCM detected that the device attempted to register to two nodes at the same time. CUCM initiated a restart to the phone to force it to re-home to a single node. callManagerApplyConfig: CUCM configuration is changed. deviceNoResponse: Device is not responding Service Control Notify from CUCM. emLoginLogout: The device has been unregistered due to an Extension Mobility login or logout. emccLoginLogout: The device has been unregistered due to an Extension Mobility Cross Cluster login or logout. powerSavePlus: The device powered off as a result of the Power Save Plus feature that is enabled for this device. When the device powers off, it remains unregistered from CUCM until the Phone On Time defined in the Product Specific Configuration for this device. callManagerForcedRestart: The device did not respond to an Apply Config request and as a result, CUCM had sent a restart request to the device. The device may be offline due to a power outage or network problem. Confirm that the device is powered-up and that network connectivity exists between the device and CUCM. This is applicable for SIP protocol only. sourceIPAddrChanged: The device has been unregistered because the IP address in the Contact header of the REGISTER message has changed. The device will be automatically re-registered. No action is necessary. This is applicable for SIP protocol only. sourcePortChanged: The device has been unregistered because the port number in the Contact header of the REGISTER message has changed. The device will be automatically re-registered. No action is necessary. This is applicable for SIP protocol only. registrationSequenceError: A device requested configuration information from the CUCM at an unexpected time. The CUCM no longer had the requested information in memory. invalidCapabilities: The CUCM detected an error in the updated media capabilities reported by the device. The device reported the capabilities in one of the StationUpdateCapabilities message variants. This is applicable for SCCP protocol only. fallbackInitiated The device has initiated a fallback and will automatically re-register to a higher-priority CUCM. No action is necessary. deviceSwitch A second instance of an endpoint with the same device name has registered and assumed control. No action is necessary. · Integer32

The reason code associated with unregistered Media Device.

CcmDevRegFailCauseCode0 = noError1 = unknown2 = noEntryInDatabase3 = databaseConfigurationError4 = deviceNameUnresolveable5 = maxDevRegExceeded6 = connectivityError7 = initializationError8 = deviceInitiatedReset9 = callManagerReset10 = authenticationError11 = invalidX509NameInCertificate12 = invalidTLSCipher13 = directoryNumberMismatch14 = malformedRegisterMsg15 = protocolMismatch16 = deviceNotActive17 = authenticatedDeviceAlreadyExists18 = obsoleteProtocolVersion23 = databaseTimeout25 = registrationSequenceError26 = invalidCapabilities27 = capabilityResponseTimeout28 = securityMismatch29 = autoRegisterDBError30 = dbAccessError31 = autoRegisterDBConfigTimeout32 = deviceTypeMismatch33 = addressingModeMismatchThis syntax is used as means of identifying the reasons for a device registration failure. The scope of this enumeration can expand to comply with RFC 2578. noError: No Error unknown: Unknown error cause noEntryInDatabase: Device not configured properly in the CUCM database databaseConfigurationError: Device configuration error in the CUCM database deviceNameUnresolveable: The CallManager is unable to resolve the device name to an IP Address internally maxDevRegExceeded: Maximum number of device registrations have been reached connectivityError: CallManager is unable to establish communication with the device during registration initializationError: Indicates an error occurred when the CallManager tries to initialize the device deviceInitiatedReset: Indicates that the error was due to device initiated reset callManagerReset: Indicates that the error was due to call manager reset. authenticationError: Indicates mismatch between configured authentication mode and the authentication mode that the device is using to connect to the CallManager. invalidX509NameInCertificate: Indicates mismatch between the peer X.509 certificate subject name and what is configured for the device. invalidTLSCipher: Indicates Cipher mismatch during TLS handshake process. directoryNumberMismatch: Indicates mismatch between the directory number that the SIP device is trying to register with and the directory number configured in the CallManager for the SIP device. malformedRegisterMsg: Indicates that SIP device attempted to register with CallManager, but the REGISTER message contained formatting errors. protocolMismatch: The protocol of the device (SIP or SCCP) does not match the configured protocol in CUCM. deviceNotActive: The device has not been activated. authenticatedDeviceAlreadyExists: A device with the same name is already registered with CUCM. obsoleteProtocolVersion: The SCCP device registered with an obsolete protocol version. databaseTimeout: CUCM requested device configuration data from the database but did not receive a response within 10 minutes. registrationSequenceError: A device requested configuration information from the CUCM at an unexpected time. The CUCM had not yet obtained the requested information. The device will automatically attempt to register again. If this alarm occurs again, manually reset the device. If this alarm continues to occur after the manual reset, there may be an internal firmware error. This is applicable for SCCP protocol only. invalidCapabilities: The CUCM detected an error in the media capabilities reported in the StationCapabilitiesRes message by the device during registration. The device will automatically attempt to register again. If this alarm occurs again, manually reset the device. If this alarm continues to occur after the manual reset, there may be a protocol error. This is applicable for SCCP protocol only. capabilityResponseTimeout: The CUCM timed out while waiting for the device to respond to a request to report its media capabilities. Possible causes include device power outage, network power outage, network configuration error, network delay, packet drops, and packet corruption. It is also possible to get this error if the CUCM node is experiencing high CPU usage. Verify that the device is powered up and operating. Verify that network connectivity exists between the device and CUCM, and verify that the CPU utilization is in the safe range. This is applicable for SCCP protocol only. securityMismatch: The CUCM detected a mismatch in the security settings of the device and/or the CUCM. The mismatches that can be detected are: 1) The device established a secure connection, yet reported that it does not have the ability to do authenticated signaling. 2) The device did not establish a secure connection, but the security mode configured for the device indicates that it should have done so. 3) The device established a secure connection, but the security mode configured for the device indicates that it should not have done so autoRegisterDBError: Auto-registration of a device failed for one of the following reasons: 1)Auto-registration is not allowed for the device type. 2)An error occurred while adding the auto-registering device to the database (stored procedure). dbAccessError: Device registration failed because of an error that occurred while building the station registration profile. This usually indicates a synchronization problem with the database. autoRegisterDBConfigTimeout: The CUCM timed out during auto-registration of a device. The registration profile of the device did not get inserted into the database in time. The device will automatically attempt to register again. This is applicable for SCCP protocol only. deviceTypeMismatch: The device type reported by the device does not match the device type configured on the CUCM addressingModeMismatch: The CUCM detected an error related to the addressing mode configured for the device. One of the following errors were detected: 1)The device is configured to use only IPv4 addressing, but did not specify an IPv4 address. 2)The device is configured to use only IPv6 addressing, but did not specify an IPv6 address. This is applicable for SCCP protocol only. · Integer32

The reason code associated with registration failed Media Device.

CcmIndexThis syntax is used as the Index into a table. A positive value is used to identify a unique entry in the table. (1..4294967295) · Unsigned32 · hint d

An arbitrary integer, selected by the local CUCM, which identifies a Gatekeeper entry in the table.

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..128) · OCTET STRING · hint 255t

This is the Gatekeeper name assigned to the Gatekeeper. This name is assigned when a new device of type Gatekeeper is added to the CallManager.

INTEGER1 = unknown2 = other3 = terminal4 = gateway · Integer32

The type of Gatekeeper. unknown: Unknown Gatekeeper other: Unidentified Gatekeeper terminal: Terminal gateway: Gateway.

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..128) · OCTET STRING · hint 255t

A description of the Gatekeeper. This description is given when the Gatekeeper is configured in the CUCM.

INTEGER1 = unknown2 = registered3 = unregistered4 = rejected · Integer32

The local call manager registration status with the Gatekeeper. The status changes from unknown to registered when the local call manager successfully registers itself with the gatekeeper. unknown: The registration status of the call manager with the gatekeeper is unknown registered: The local call manager has registered with the gatekeeper successfully unregistered: The local call manager is no longer registered with the gatekeeper rejected: Registration request from the local call manager was rejected by the gatekeeper.

CcmIndexOrZeroThis textual convention is an extension of the CcmIndex convention. The latter defines a greater than zero to identify an entry of the CUCM MIB table in the managed system. This extension permits the additional value of zero. The value zero is object- specific and must be defined as part of the description of any object which uses this syntax. · Unsigned32 · hint d

A positive value of this index is used to identify the Device Pool to which this Gatekeeper entry belongs. A value of 0 indicates that the index to the Device Pool table is Unknown.

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

This object identifies the IP address type of the Gatekeeper. The value of this object is 'unknown(0)' if the IP address of a Gatekeeper is not available.

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

This object identifies last known IP Address of the gatekeeper. If the IP address is not available then this object contains an empty string. The type of address for this is identified by ccmGatekeeperInetAddressType.

CcmIndexThis syntax is used as the Index into a table. A positive value is used to identify a unique entry in the table. (1..4294967295) · Unsigned32 · hint d

An arbitrary integer, selected by the local CUCM, which identifies a CTI Device entry in the table.

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 name of the CTI Device. This name is assigned to the CTI Device when it is added to the CallManager.

INTEGER1 = unknown2 = other3 = ctiRoutePoint4 = ctiPort · Integer32

The type of CTI Device. unknown: Unknown CTI Device other: Unidentified CTI Device ctiRoutePoint: A CTI Route Point ctiPort: A CTI Port.

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..128) · OCTET STRING · hint 255t

A description of the CTI Device. This description is given when the CTI Device is configured in the CUCM.

CcmDeviceStatus1 = unknown2 = registered3 = unregistered4 = rejected5 = partiallyregisteredThis syntax is used to identify the registration status of a device with the local call manager. unknown: The registration status of the device is unknown registered: The device has successfully registered with the local call manager unregistered: The device is no longer registered with the local call manager rejected: Registration request from the device was rejected by the local call manager. partiallyregistered: At least one but not all of the lines are successfully registered to the local call manager. Applicable only to SIP phones. · Integer32

The status of the CTI Device. The CTI Device status changes from unknown to registered when it registers itself with the local CUCM.

CcmIndexOrZeroThis textual convention is an extension of the CcmIndex convention. The latter defines a greater than zero to identify an entry of the CUCM MIB table in the managed system. This extension permits the additional value of zero. The value zero is object- specific and must be defined as part of the description of any object which uses this syntax. · Unsigned32 · hint d

A positive value of this index is used to identify the Device Pool to which this CTI Device entry belongs. A value of 0 indicates that the index to the Device Pool table is Unknown.

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

This object identifies the IP address type of the CTIDevice. The value of this object is 'unknown(0)' if the IP address of a CTIDevice is not available.

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

This object identifies IP Address of the host where this CTI Device is running. If the IP address is not available then this object contains an empty string. The type of address for this is identified by ccmCTIDeviceInetAddressType.

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 appinfo string indicates the application name/ type that uses this CTI Device.

CcmDevFailCauseCode0 = noError1 = unknown2 = noEntryInDatabase3 = databaseConfigurationError4 = deviceNameUnresolveable5 = maxDevRegReached6 = connectivityError7 = initializationError8 = deviceInitiatedReset9 = callManagerReset10 = authenticationError11 = invalidX509NameInCertificate12 = invalidTLSCipher13 = directoryNumberMismatch14 = malformedRegisterMsgThis syntax is used as means of identifying the reasons for a device communication error. noError: No Error unknown: Unknown error cause noEntryInDatabase: Device not configured properly in the CUCM database databaseConfigurationError: Device configuration error in the CUCM database deviceNameUnresolveable: The CallManager is unable to resolve the device name to an IP Address internally maxDevRegReached: Maximum number of device registrations have been reached connectivityError: CallManager is unable to establish communication with the device during registration initializationError: Indicates an error occurred when the CallManager tries to initialize the device deviceInitiatedReset: Indicates that the error was due to device initiated reset callManagerReset: Indicates that the error was due to call manager reset. authenticationError: Indicates mismatch between configured authentication mode and the authentication mode that the device is using to connect to the CallManager. invalidX509NameInCertificate: Indicates mismatch between the peer X.509 certificate subject name and what is configured for the device. invalidTLSCipher: Indicates Cipher mismatch during TLS handshake process. directoryNumberMismatch: Indicates mismatch between the directory number that the SIP device is trying to register with and the directory number configured in the CallManager for the SIP device. malformedRegisterMsg: Indicates that SIP device attempted to register with CallManager, but the REGISTER message contained formatting errors. · Integer32

The reason code associated with the CTI Device status change.

DateAndTimeA date-time specification. field octets contents range ----- ------ -------- ----- 1 1-2 year* 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC* 0..13 10 11 minutes from UTC 0..59 * Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: 1992-5-26,13:30:15.0,-4:0 Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d

The time the status of the CTI device changed.

DateAndTimeA date-time specification. field octets contents range ----- ------ -------- ----- 1 1-2 year* 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC* 0..13 10 11 minutes from UTC 0..59 * Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: 1992-5-26,13:30:15.0,-4:0 Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d

The time the CTI Device last registered with the call manager.

CcmIndexOrZeroThis textual convention is an extension of the CcmIndex convention. The latter defines a greater than zero to identify an entry of the CUCM MIB table in the managed system. This extension permits the additional value of zero. The value zero is object- specific and must be defined as part of the description of any object which uses this syntax. · Unsigned32 · hint d

A positive value of this index is used to identify the related product type entry in the ccmProductTypeTable. A value of 0 indicates that the index to the ccmProductTypeTable is Unknown.

InetAddressIPv4Represents an IPv4 network address: Octets Contents Encoding 1-4 IPv4 address network-byte order The corresponding InetAddressType value is ipv4(1). This textual convention SHOULD NOT be used directly in object definitions, as it restricts addresses to a specific format. However, if it is used, it MAY be used either on its own or in conjunction with InetAddressType, as a pair. SIZE (4) · OCTET STRING · hint 1d.1d.1d.1d

This object identifies IPv4 Address of the host where this CTI Device is running. If the IPv4 address is not available then this object contains an empty string.

InetAddressIPv6Represents an IPv6 network address: Octets Contents Encoding 1-16 IPv6 address network-byte order The corresponding InetAddressType value is ipv6(2). This textual convention SHOULD NOT be used directly in object definitions, as it restricts addresses to a specific format. However, if it is used, it MAY be used either on its own or in conjunction with InetAddressType, as a pair. SIZE (16) · OCTET STRING · hint 2x:2x:2x:2x:2x:2x:2x:2x

This object identifies IPv6 Address of the host where this CTI Device is running. If the IPv6 address is not available then this object contains an empty string.

CcmDevUnregCauseCode0 = noError1 = unknown2 = noEntryInDatabase3 = databaseConfigurationError4 = deviceNameUnresolveable5 = maxDevRegExceeded6 = connectivityError7 = initializationError8 = deviceInitiatedReset9 = callManagerReset10 = deviceUnregistered11 = malformedRegisterMsg12 = sccpDeviceThrottling13 = keepAliveTimeout14 = configurationMismatch15 = callManagerRestart16 = duplicateRegistration17 = callManagerApplyConfig18 = deviceNoResponse19 = emLoginLogout20 = emccLoginLogout21 = energywisePowerSavePlus22 = callManagerForcedRestart23 = sourceIPAddrChanged24 = sourcePortChanged25 = registrationSequenceError26 = invalidCapabilities28 = fallbackInitiated29 = deviceSwitchThis syntax is used as means of identifying the reasons for a device getting unregistered. The scope of this enumeration can expand to comply with RFC 2578. noError: No Error unknown: Unknown error cause noEntryInDatabase: Device not configured properly in the CUCM database databaseConfigurationError: Device configuration error in the CUCM database deviceNameUnresolveable: The CallManager is unable to resolve the device name to an IP Address internally maxDevRegExceeded: Maximum number of device registrations have been reached connectivityError: CallManager is unable to establish communication with the device during registration initializationError: Indicates an error occurred when the CallManager tries to initialize the device deviceInitiatedReset: Indicates that the error was due to device initiated reset callManagerReset: Indicates that the error was due to call manager reset. deviceUnregistered: DeviceUnregistered. malformedRegisterMsg: Indicates that SIP device attempted to register with CallManager, but the REGISTER message contained formatting errors. sccpDeviceThrottling: The indicated SCCP device exceeded the maximum number of events allowed per-SCCP device. keepAliveTimeout: A KeepAlive message was not received. Possible causes include device power outage, network power outage, network configuration error, network delay,packet drops, packet corruption and CUCM node experiencing high CPU usage. configurationMismatch: The configuration on the SIP device does not match the configuration in CUCM. callManagerRestart: A device restart was initiated from CUCM Administration, either due to an explicit command from an administrator or due to a configuration change such as adding, deleting or changing a directory number associated with the device. duplicateRegistration: CUCM detected that the device attempted to register to two nodes at the same time. CUCM initiated a restart to the phone to force it to re-home to a single node. callManagerApplyConfig: CUCM configuration is changed. deviceNoResponse: Device is not responding Service Control Notify from CUCM. emLoginLogout: The device has been unregistered due to an Extension Mobility login or logout. emccLoginLogout: The device has been unregistered due to an Extension Mobility Cross Cluster login or logout. powerSavePlus: The device powered off as a result of the Power Save Plus feature that is enabled for this device. When the device powers off, it remains unregistered from CUCM until the Phone On Time defined in the Product Specific Configuration for this device. callManagerForcedRestart: The device did not respond to an Apply Config request and as a result, CUCM had sent a restart request to the device. The device may be offline due to a power outage or network problem. Confirm that the device is powered-up and that network connectivity exists between the device and CUCM. This is applicable for SIP protocol only. sourceIPAddrChanged: The device has been unregistered because the IP address in the Contact header of the REGISTER message has changed. The device will be automatically re-registered. No action is necessary. This is applicable for SIP protocol only. sourcePortChanged: The device has been unregistered because the port number in the Contact header of the REGISTER message has changed. The device will be automatically re-registered. No action is necessary. This is applicable for SIP protocol only. registrationSequenceError: A device requested configuration information from the CUCM at an unexpected time. The CUCM no longer had the requested information in memory. invalidCapabilities: The CUCM detected an error in the updated media capabilities reported by the device. The device reported the capabilities in one of the StationUpdateCapabilities message variants. This is applicable for SCCP protocol only. fallbackInitiated The device has initiated a fallback and will automatically re-register to a higher-priority CUCM. No action is necessary. deviceSwitch A second instance of an endpoint with the same device name has registered and assumed control. No action is necessary. · Integer32

The reason code associated with unregistered CTI Device.

CcmDevRegFailCauseCode0 = noError1 = unknown2 = noEntryInDatabase3 = databaseConfigurationError4 = deviceNameUnresolveable5 = maxDevRegExceeded6 = connectivityError7 = initializationError8 = deviceInitiatedReset9 = callManagerReset10 = authenticationError11 = invalidX509NameInCertificate12 = invalidTLSCipher13 = directoryNumberMismatch14 = malformedRegisterMsg15 = protocolMismatch16 = deviceNotActive17 = authenticatedDeviceAlreadyExists18 = obsoleteProtocolVersion23 = databaseTimeout25 = registrationSequenceError26 = invalidCapabilities27 = capabilityResponseTimeout28 = securityMismatch29 = autoRegisterDBError30 = dbAccessError31 = autoRegisterDBConfigTimeout32 = deviceTypeMismatch33 = addressingModeMismatchThis syntax is used as means of identifying the reasons for a device registration failure. The scope of this enumeration can expand to comply with RFC 2578. noError: No Error unknown: Unknown error cause noEntryInDatabase: Device not configured properly in the CUCM database databaseConfigurationError: Device configuration error in the CUCM database deviceNameUnresolveable: The CallManager is unable to resolve the device name to an IP Address internally maxDevRegExceeded: Maximum number of device registrations have been reached connectivityError: CallManager is unable to establish communication with the device during registration initializationError: Indicates an error occurred when the CallManager tries to initialize the device deviceInitiatedReset: Indicates that the error was due to device initiated reset callManagerReset: Indicates that the error was due to call manager reset. authenticationError: Indicates mismatch between configured authentication mode and the authentication mode that the device is using to connect to the CallManager. invalidX509NameInCertificate: Indicates mismatch between the peer X.509 certificate subject name and what is configured for the device. invalidTLSCipher: Indicates Cipher mismatch during TLS handshake process. directoryNumberMismatch: Indicates mismatch between the directory number that the SIP device is trying to register with and the directory number configured in the CallManager for the SIP device. malformedRegisterMsg: Indicates that SIP device attempted to register with CallManager, but the REGISTER message contained formatting errors. protocolMismatch: The protocol of the device (SIP or SCCP) does not match the configured protocol in CUCM. deviceNotActive: The device has not been activated. authenticatedDeviceAlreadyExists: A device with the same name is already registered with CUCM. obsoleteProtocolVersion: The SCCP device registered with an obsolete protocol version. databaseTimeout: CUCM requested device configuration data from the database but did not receive a response within 10 minutes. registrationSequenceError: A device requested configuration information from the CUCM at an unexpected time. The CUCM had not yet obtained the requested information. The device will automatically attempt to register again. If this alarm occurs again, manually reset the device. If this alarm continues to occur after the manual reset, there may be an internal firmware error. This is applicable for SCCP protocol only. invalidCapabilities: The CUCM detected an error in the media capabilities reported in the StationCapabilitiesRes message by the device during registration. The device will automatically attempt to register again. If this alarm occurs again, manually reset the device. If this alarm continues to occur after the manual reset, there may be a protocol error. This is applicable for SCCP protocol only. capabilityResponseTimeout: The CUCM timed out while waiting for the device to respond to a request to report its media capabilities. Possible causes include device power outage, network power outage, network configuration error, network delay, packet drops, and packet corruption. It is also possible to get this error if the CUCM node is experiencing high CPU usage. Verify that the device is powered up and operating. Verify that network connectivity exists between the device and CUCM, and verify that the CPU utilization is in the safe range. This is applicable for SCCP protocol only. securityMismatch: The CUCM detected a mismatch in the security settings of the device and/or the CUCM. The mismatches that can be detected are: 1) The device established a secure connection, yet reported that it does not have the ability to do authenticated signaling. 2) The device did not establish a secure connection, but the security mode configured for the device indicates that it should have done so. 3) The device established a secure connection, but the security mode configured for the device indicates that it should not have done so autoRegisterDBError: Auto-registration of a device failed for one of the following reasons: 1)Auto-registration is not allowed for the device type. 2)An error occurred while adding the auto-registering device to the database (stored procedure). dbAccessError: Device registration failed because of an error that occurred while building the station registration profile. This usually indicates a synchronization problem with the database. autoRegisterDBConfigTimeout: The CUCM timed out during auto-registration of a device. The registration profile of the device did not get inserted into the database in time. The device will automatically attempt to register again. This is applicable for SCCP protocol only. deviceTypeMismatch: The device type reported by the device does not match the device type configured on the CUCM addressingModeMismatch: The CUCM detected an error related to the addressing mode configured for the device. One of the following errors were detected: 1)The device is configured to use only IPv4 addressing, but did not specify an IPv4 address. 2)The device is configured to use only IPv6 addressing, but did not specify an IPv6 address. This is applicable for SCCP protocol only. · Integer32

The reason code associated with registration failed CTI Device.

CcmIndexThis syntax is used as the Index into a table. A positive value is used to identify a unique entry in the table. (1..4294967295) · Unsigned32 · hint d

An arbitrary integer, selected by the local system, which identifies a Directory Number of a CTI Device.

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..24) · OCTET STRING · hint 255t

A Directory Number of the CTI Device.

CcmIndexThis syntax is used as the Index into a table. A positive value is used to identify a unique entry in the table. (1..4294967295) · Unsigned32 · hint d

An arbitrary integer, selected by the local CUCM, which identifies a H323 Device entry in the table.

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..128) · OCTET STRING · hint 255t

The device name assigned to the H323 Device. This name is assigned when a new H323 device is added to the CallManager.

CcmDeviceProductId-2 = other-1 = unknown1 = gwyCiscoCat6KT12 = gwyCiscoCat6KE13 = gwyCiscoCat6KFXS4 = gwyCiscoCat6KFXO7 = gwyCiscoDT24Plus8 = gwyCiscoDT30Plus9 = gwyCiscoDT2410 = gwyCiscoAT211 = gwyCiscoAT412 = gwyCiscoAT813 = gwyCiscoAS214 = gwyCiscoAS415 = gwyCiscoAS816 = h323Phone17 = h323Trunk18 = gwyCiscoMGCPFXOPort19 = gwyCiscoMGCPFXSPort27 = voiceMailUOnePort43 = gwyCiscoVG20044 = gwyCisco26XX45 = gwyCisco362X46 = gwyCisco364X47 = gwyCisco366X49 = h323AnonymousGatewy52 = gwyCiscoMGCPT1Port55 = gwyCiscoMGCPE1Port58 = gwyCiscoCat4224VoiceGwySwitch59 = gwyCiscoCat4000AccessGwyModule62 = gwyCiscoIAD240065 = gwyCiscoVGCEndPoint66 = gwyCiscoVG224AndV24867 = gwyCiscoSlotVGCPort68 = gwyCiscoVGCBox69 = gwyCiscoATA18670 = gwyCiscoICS77XXMRP2XX71 = gwyCiscoICS77XXASI8172 = gwyCiscoICS77XXASI16075 = h323H225GKControlledTrunk76 = h323ICTGKControlled77 = h323ICTNonGKControlled80 = gwyCiscoCat6000AVVIDServModule81 = gwyCiscoWSX660090 = gwyCiscoMGCPBRIPort95 = sipTrunk10001 = gwyCiscoWSSVCCMMMS20000 = gwyCisco374520002 = gwyCisco372530004 = gwyCiscoICS77XXMRP3XX30005 = gwyCiscoICS77XXMRP38FXS30006 = gwyCiscoICS77XXMRP316FXS30007 = gwyCiscoICS77XXMRP38FXOM130011 = gwyCisco269X30019 = gwyCisco176030020 = gwyCisco1751This syntax is used to identify the product id of a device. gwyCiscoCat6KT1(1): Cisco Catalyst 6000 T1 VoIP Gateway gwyCiscoCat6KE1(2): Cisco Catalyst 6000 E1 VoIP Gateway gwyCiscoCat6KFXS(3): Cisco Catalyst 6000 24 Port FXS Gateway gwyCiscoCat6KFXO(4): Cisco Catalyst 6000 12 Port FXO Gateway gwyCiscoDT24Plus(7): Cisco DT-24+ Gateway gwyCiscoDT30Plus(8): Cisco DT-30+ Gateway gwyCiscoDT24(9): Cisco DT-24 Gateway gwyCiscoAT2(10): Cisco AT2 Gateway gwyCiscoAT4(11): Cisco AT4 Gateway gwyCiscoAT8(12): Cisco AT8 Gateway gwyCiscoAS2(13): Cisco AS2 Gateway gwyCiscoAS4(14): Cisco AS4 Gateway gwyCiscoAS8(15): Cisco AS8 Gateway gwyCiscoMGCPFXOPort(18): Cisco MGCP FXO Port gwyCiscoMGCPFXSPort(19): Cisco MGCP FXS Port gwyCiscoVG200(43): Cisco VG200 gwyCisco26XX(44): Cisco 26XX gwyCisco362X(45): Cisco 362X gwyCisco364X(46): Cisco 364X gwyCisco366X(47): Cisco 366X gwyCiscoMGCPT1Port(52): Cisco MGCP T1 Port gwyCiscoMGCPE1Port(55): Cisco MGCP E1 Port gwyCiscoCat4224VoiceGwySwitch(58): Cisco CAT 4224 Voice Gateway Switch gwyCiscoCat4000AccessGwyModule(59): Cisco CAT 4000 Access Gateway Module gwyCiscoIAD2400(62): Cisco IAD2400 gwyCiscoVGCEndPoint(65): Cisco VGC PHONE gwyCiscoVG224AndV248(66): Cisco VGC Gateway gwyCiscoSlotVGCPort(67): Cisco VGC Port gwyciscoVGCBox(68): Cisco VGC Box gwyCiscoATA186(69): Cisco ATA 186 gwyCiscoICS77XXMRP2XX(70): Cisco ICS77XX-MRP2XX gwyCiscoICS77XXASI81(71): Cisco ICS77XX-ASI81 gwyCiscoICS77XXASI160(72): Cisco ICS77XX-ASI160 gwyCiscoCat6000AVVIDServModule(80): Cisco Catalyst 6000 AVVID Services Module gwyCiscoWSX6600(81): Cisco WS-X6600 gwyCiscoMGCPBRIPort(90): Cisco MGCP BRI Port gwyCiscoWSSVCCMMMS(10001): Cisco WS-SVC-CMM-MS gwyCisco3745(20000): Cisco 3745 gwyCisco3725(20002): Cisco 3725 gwyCiscoICS77XXMRP3XX(30004): Cisco ICS77XX MRP3XX gwyCiscoICS77XXMRP38FXS(30005): Cisco ICS77XX MRP3 8FXS gwyCiscoICS77XXMRP316FXS(30006): Cisco ICS77XX MRP3 16FXS gwyCiscoICS77XXMRP38FXOM1(30007): Cisco ICS77XX MRP3 8FXO M1 gwyCisco269X(30011): Cisco 269X gwyCisco1760(30019): Cisco 1760 gwyCisco1751(30020): Cisco 1751 h323Phone(16): H323 Phone h323Trunk(17): H323 Trunk h323AnonymousGateway(49): H323 Anonymous Gateway h323H225GKControlledTrunk(75): H225 Trunk Gatekeeper Controlled h323ICTGKControlled(76): Inter-Cluster Trunk Gatekeeper Controlled h323ICTNonGKControlled(77): Inter-Cluster Trunk Non-Gatekeeper Controlled voiceMailUOnePort(27): Uone Port sipTrunk(95): SIP Trunk unknown(-1): Unknown Device Product Id other(-2): Unidentified Device Product Id. · Integer32

The product identifier of the H323 device.

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

A description of the H323 device. This description is given when the H323 device is configured in the CUCM.

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

This object identifies the IP address type of the H323 device. The value of this object is 'unknown(0)' if the IP address of a H323 device is not available.

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

This object identifies last known IP Address of the H323 device. If the IP address is not available then this object contains an empty string. The type of address for this is identified by ccmH323DevInetAddressType.

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

This object identifies the IP address type of the gatekeeper device. The value of this object is 'unknown(0)' if the IP address of a H323 gatekeeper is not available.

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

This object represents configured gatekeeper DNS name or IP address for this H323 device. This is applicable only for H323 devices with gatekeepers configured. When there is no H323 gatekeeper configured, this object contains an empty string. The type of address for this is identified by ccmH323DevCnfgGKInetAddressType.

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

This object identifies the IP address type of the first alternate gatekeeper. The value of this object is 'unknown(0)' if the IP address of a H323 gatekeeper is not available.

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

This object identifies the first alternate gatekeeper DNS name or IP address for this H323 device. This is applicable only for H323 devices with gatekeepers configured. When there is no first alternate H323 gatekeeper, this object contains an empty string. The type of address for this is identified by ccmH323DevAltGK1InetAddressType.

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

This object identifies the IP address type of the second alternate gatekeeper. The value of this object is 'unknown(0)' if the IP address of a H323 gatekeeper is not available.

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

This object identifies the second alternate gatekeeper DNS name or IP address for this H323 device. This is applicable only for H323 devices with gatekeepers configured. When there is no second alternate H323 gatekeeper, this object contains an empty string. The type of address for this is identified by ccmH323DevAltGK2InetAddressType.

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

This object identifies the IP address type of the third alternate gatekeeper. The value of this object is 'unknown(0)' if the IP address of a H323 gatekeeper is not available.

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

This object identifies the third alternate gatekeeper DNS name or IP address for this H323 device. This is applicable only for H323 devices with gatekeepers configured. When there is no third alternate H323 gatekeeper, this object contains an empty string. The type of address for this is identified by ccmH323DevAltGK3InetAddressType.

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

This object identifies the IP address type of the fourth alternate gatekeeper. The value of this object is 'unknown(0)' if the IP address of a H323 gatekeeper is not available.

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

This object identifies the fourth alternate gatekeeper DNS name or IP address for this H323 device. This is applicable only for H323 devices with gatekeepers configured. When there is no fourth H323 alternate gatekeeper, this object contains an empty string. The type of address for this is identified by ccmH323DevAltGK4InetAddressType.

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

This object identifies the IP address type of the fifth alternate gatekeeper. The value of this object is 'unknown(0)' if the IP address of a H323 gatekeeper is not available.

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

This object identifies the fifth alternate gatekeeper DNS name or IP address for this H323 device. This is applicable only for H323 devices with gatekeepers configured. When there is no fifth H323 alternate gatekeeper, this object contains an empty string. The type of address for this is identified by ccmH323DevAltGK5InetAddressType.

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

This object identifies the IP address type of the active gatekeeper. The value of this object is 'unknown(0)' if the IP address of a gatekeeper is not available.

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

This object identifies the active alternate gatekeeper DNS name or IP address for this H323 device. This is applicable only for H323 devices with gatekeepers configured. When there is no active alternate H323 gatekeeper, this object contains an empty string. The type of address for this is identified by ccmH323DevActGKInetAddressType.

INTEGER0 = notApplicable1 = unknown2 = registered3 = unregistered4 = rejected · Integer32

The H323 device registration status with the gatekeeper. The status changes from unknown to registered when the H323 device successfully registers itself with the gatekeeper. notApplicable: The registration status is not applicable for this H323 device unknown: The registration status of the H323 device with the gatekeeper is unknown registered: The H323 device has registered with the gatekeeper successfully unregistered: The H323 device is no longer registered with the gatekeeper rejected: Registration request from the H323 device was rejected by the gatekeeper.

CcmDevFailCauseCode0 = noError1 = unknown2 = noEntryInDatabase3 = databaseConfigurationError4 = deviceNameUnresolveable5 = maxDevRegReached6 = connectivityError7 = initializationError8 = deviceInitiatedReset9 = callManagerReset10 = authenticationError11 = invalidX509NameInCertificate12 = invalidTLSCipher13 = directoryNumberMismatch14 = malformedRegisterMsgThis syntax is used as means of identifying the reasons for a device communication error. noError: No Error unknown: Unknown error cause noEntryInDatabase: Device not configured properly in the CUCM database databaseConfigurationError: Device configuration error in the CUCM database deviceNameUnresolveable: The CallManager is unable to resolve the device name to an IP Address internally maxDevRegReached: Maximum number of device registrations have been reached connectivityError: CallManager is unable to establish communication with the device during registration initializationError: Indicates an error occurred when the CallManager tries to initialize the device deviceInitiatedReset: Indicates that the error was due to device initiated reset callManagerReset: Indicates that the error was due to call manager reset. authenticationError: Indicates mismatch between configured authentication mode and the authentication mode that the device is using to connect to the CallManager. invalidX509NameInCertificate: Indicates mismatch between the peer X.509 certificate subject name and what is configured for the device. invalidTLSCipher: Indicates Cipher mismatch during TLS handshake process. directoryNumberMismatch: Indicates mismatch between the directory number that the SIP device is trying to register with and the directory number configured in the CallManager for the SIP device. malformedRegisterMsg: Indicates that SIP device attempted to register with CallManager, but the REGISTER message contained formatting errors. · Integer32

The reason code associated with ccmH233DevStatus change. This is applicable only for H323 devices with gatekeepers configured.

DateAndTimeA date-time specification. field octets contents range ----- ------ -------- ----- 1 1-2 year* 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC* 0..13 10 11 minutes from UTC 0..59 * Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: 1992-5-26,13:30:15.0,-4:0 Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d

The time the registration status with the gatekeeper changed. This is applicable only for H323 devices with gatekeepers configured.

DateAndTimeA date-time specification. field octets contents range ----- ------ -------- ----- 1 1-2 year* 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC* 0..13 10 11 minutes from UTC 0..59 * Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: 1992-5-26,13:30:15.0,-4:0 Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d

The time when the H323 device last registered with the gatekeeper. This is applicable only for H323 devices with gatekeepers configured.

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

This object identifies the IP address type of the first remote call manager. The value of this object is 'unknown(0)' if the first remote call manager is not configured.

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

This object identifies the first remote call manager DNS name or IP address configured for this H323 device. When there is no first remote call manager configured, this object contains an empty string. The type of address for this is identified by ccmH323DevRmtCM1InetAddressType.

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

This object identifies the IP address type of the second remote call manager. The value of this object is 'unknown(0)' if the second remote call manager is not configured.

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

This object identifies the second remote call manager DNS name or IP address configured for this H323 device. When there is no second remote call manager configured, this object contains an empty string. The type of address for this is identified by ccmH323DevRmtCM2InetAddressType.

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

This object identifies the IP address type of the third remote call manager. The value of this object is 'unknown(0)' if the third remote call manager is not configured.

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

This object identifies the third remote call manager DNS name or IP address configured for this H323 device. When there is no third remote call manager configured, this object contains an empty string. The type of address for this is identified by ccmH323DevRmtCM3InetAddressType.

CcmIndexOrZeroThis textual convention is an extension of the CcmIndex convention. The latter defines a greater than zero to identify an entry of the CUCM MIB table in the managed system. This extension permits the additional value of zero. The value zero is object- specific and must be defined as part of the description of any object which uses this syntax. · Unsigned32 · hint d

A positive value of this index is used to identify the related product type entry in the ccmProductTypeTable. A value of 0 indicates that the index to the ccmProductTypeTable is Unknown.

CcmDevUnregCauseCode0 = noError1 = unknown2 = noEntryInDatabase3 = databaseConfigurationError4 = deviceNameUnresolveable5 = maxDevRegExceeded6 = connectivityError7 = initializationError8 = deviceInitiatedReset9 = callManagerReset10 = deviceUnregistered11 = malformedRegisterMsg12 = sccpDeviceThrottling13 = keepAliveTimeout14 = configurationMismatch15 = callManagerRestart16 = duplicateRegistration17 = callManagerApplyConfig18 = deviceNoResponse19 = emLoginLogout20 = emccLoginLogout21 = energywisePowerSavePlus22 = callManagerForcedRestart23 = sourceIPAddrChanged24 = sourcePortChanged25 = registrationSequenceError26 = invalidCapabilities28 = fallbackInitiated29 = deviceSwitchThis syntax is used as means of identifying the reasons for a device getting unregistered. The scope of this enumeration can expand to comply with RFC 2578. noError: No Error unknown: Unknown error cause noEntryInDatabase: Device not configured properly in the CUCM database databaseConfigurationError: Device configuration error in the CUCM database deviceNameUnresolveable: The CallManager is unable to resolve the device name to an IP Address internally maxDevRegExceeded: Maximum number of device registrations have been reached connectivityError: CallManager is unable to establish communication with the device during registration initializationError: Indicates an error occurred when the CallManager tries to initialize the device deviceInitiatedReset: Indicates that the error was due to device initiated reset callManagerReset: Indicates that the error was due to call manager reset. deviceUnregistered: DeviceUnregistered. malformedRegisterMsg: Indicates that SIP device attempted to register with CallManager, but the REGISTER message contained formatting errors. sccpDeviceThrottling: The indicated SCCP device exceeded the maximum number of events allowed per-SCCP device. keepAliveTimeout: A KeepAlive message was not received. Possible causes include device power outage, network power outage, network configuration error, network delay,packet drops, packet corruption and CUCM node experiencing high CPU usage. configurationMismatch: The configuration on the SIP device does not match the configuration in CUCM. callManagerRestart: A device restart was initiated from CUCM Administration, either due to an explicit command from an administrator or due to a configuration change such as adding, deleting or changing a directory number associated with the device. duplicateRegistration: CUCM detected that the device attempted to register to two nodes at the same time. CUCM initiated a restart to the phone to force it to re-home to a single node. callManagerApplyConfig: CUCM configuration is changed. deviceNoResponse: Device is not responding Service Control Notify from CUCM. emLoginLogout: The device has been unregistered due to an Extension Mobility login or logout. emccLoginLogout: The device has been unregistered due to an Extension Mobility Cross Cluster login or logout. powerSavePlus: The device powered off as a result of the Power Save Plus feature that is enabled for this device. When the device powers off, it remains unregistered from CUCM until the Phone On Time defined in the Product Specific Configuration for this device. callManagerForcedRestart: The device did not respond to an Apply Config request and as a result, CUCM had sent a restart request to the device. The device may be offline due to a power outage or network problem. Confirm that the device is powered-up and that network connectivity exists between the device and CUCM. This is applicable for SIP protocol only. sourceIPAddrChanged: The device has been unregistered because the IP address in the Contact header of the REGISTER message has changed. The device will be automatically re-registered. No action is necessary. This is applicable for SIP protocol only. sourcePortChanged: The device has been unregistered because the port number in the Contact header of the REGISTER message has changed. The device will be automatically re-registered. No action is necessary. This is applicable for SIP protocol only. registrationSequenceError: A device requested configuration information from the CUCM at an unexpected time. The CUCM no longer had the requested information in memory. invalidCapabilities: The CUCM detected an error in the updated media capabilities reported by the device. The device reported the capabilities in one of the StationUpdateCapabilities message variants. This is applicable for SCCP protocol only. fallbackInitiated The device has initiated a fallback and will automatically re-register to a higher-priority CUCM. No action is necessary. deviceSwitch A second instance of an endpoint with the same device name has registered and assumed control. No action is necessary. · Integer32

The reason code associated with unregistered H323 Device. This is applicable only for H323 devices with gatekeepers configured.

CcmDevRegFailCauseCode0 = noError1 = unknown2 = noEntryInDatabase3 = databaseConfigurationError4 = deviceNameUnresolveable5 = maxDevRegExceeded6 = connectivityError7 = initializationError8 = deviceInitiatedReset9 = callManagerReset10 = authenticationError11 = invalidX509NameInCertificate12 = invalidTLSCipher13 = directoryNumberMismatch14 = malformedRegisterMsg15 = protocolMismatch16 = deviceNotActive17 = authenticatedDeviceAlreadyExists18 = obsoleteProtocolVersion23 = databaseTimeout25 = registrationSequenceError26 = invalidCapabilities27 = capabilityResponseTimeout28 = securityMismatch29 = autoRegisterDBError30 = dbAccessError31 = autoRegisterDBConfigTimeout32 = deviceTypeMismatch33 = addressingModeMismatchThis syntax is used as means of identifying the reasons for a device registration failure. The scope of this enumeration can expand to comply with RFC 2578. noError: No Error unknown: Unknown error cause noEntryInDatabase: Device not configured properly in the CUCM database databaseConfigurationError: Device configuration error in the CUCM database deviceNameUnresolveable: The CallManager is unable to resolve the device name to an IP Address internally maxDevRegExceeded: Maximum number of device registrations have been reached connectivityError: CallManager is unable to establish communication with the device during registration initializationError: Indicates an error occurred when the CallManager tries to initialize the device deviceInitiatedReset: Indicates that the error was due to device initiated reset callManagerReset: Indicates that the error was due to call manager reset. authenticationError: Indicates mismatch between configured authentication mode and the authentication mode that the device is using to connect to the CallManager. invalidX509NameInCertificate: Indicates mismatch between the peer X.509 certificate subject name and what is configured for the device. invalidTLSCipher: Indicates Cipher mismatch during TLS handshake process. directoryNumberMismatch: Indicates mismatch between the directory number that the SIP device is trying to register with and the directory number configured in the CallManager for the SIP device. malformedRegisterMsg: Indicates that SIP device attempted to register with CallManager, but the REGISTER message contained formatting errors. protocolMismatch: The protocol of the device (SIP or SCCP) does not match the configured protocol in CUCM. deviceNotActive: The device has not been activated. authenticatedDeviceAlreadyExists: A device with the same name is already registered with CUCM. obsoleteProtocolVersion: The SCCP device registered with an obsolete protocol version. databaseTimeout: CUCM requested device configuration data from the database but did not receive a response within 10 minutes. registrationSequenceError: A device requested configuration information from the CUCM at an unexpected time. The CUCM had not yet obtained the requested information. The device will automatically attempt to register again. If this alarm occurs again, manually reset the device. If this alarm continues to occur after the manual reset, there may be an internal firmware error. This is applicable for SCCP protocol only. invalidCapabilities: The CUCM detected an error in the media capabilities reported in the StationCapabilitiesRes message by the device during registration. The device will automatically attempt to register again. If this alarm occurs again, manually reset the device. If this alarm continues to occur after the manual reset, there may be a protocol error. This is applicable for SCCP protocol only. capabilityResponseTimeout: The CUCM timed out while waiting for the device to respond to a request to report its media capabilities. Possible causes include device power outage, network power outage, network configuration error, network delay, packet drops, and packet corruption. It is also possible to get this error if the CUCM node is experiencing high CPU usage. Verify that the device is powered up and operating. Verify that network connectivity exists between the device and CUCM, and verify that the CPU utilization is in the safe range. This is applicable for SCCP protocol only. securityMismatch: The CUCM detected a mismatch in the security settings of the device and/or the CUCM. The mismatches that can be detected are: 1) The device established a secure connection, yet reported that it does not have the ability to do authenticated signaling. 2) The device did not establish a secure connection, but the security mode configured for the device indicates that it should have done so. 3) The device established a secure connection, but the security mode configured for the device indicates that it should not have done so autoRegisterDBError: Auto-registration of a device failed for one of the following reasons: 1)Auto-registration is not allowed for the device type. 2)An error occurred while adding the auto-registering device to the database (stored procedure). dbAccessError: Device registration failed because of an error that occurred while building the station registration profile. This usually indicates a synchronization problem with the database. autoRegisterDBConfigTimeout: The CUCM timed out during auto-registration of a device. The registration profile of the device did not get inserted into the database in time. The device will automatically attempt to register again. This is applicable for SCCP protocol only. deviceTypeMismatch: The device type reported by the device does not match the device type configured on the CUCM addressingModeMismatch: The CUCM detected an error related to the addressing mode configured for the device. One of the following errors were detected: 1)The device is configured to use only IPv4 addressing, but did not specify an IPv4 address. 2)The device is configured to use only IPv6 addressing, but did not specify an IPv6 address. This is applicable for SCCP protocol only. · Integer32

The reason code associated with registration failed H323 Device. This is applicable only for H323 devices with gatekeepers configured.

CcmIndexThis syntax is used as the Index into a table. A positive value is used to identify a unique entry in the table. (1..4294967295) · Unsigned32 · hint d

An arbitrary integer, selected by the local CUCM, which identifies a voice messaging device entry in the table.

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..128) · OCTET STRING · hint 255t

The name of the Voice Messaging Device. This name is assigned to the Voice Messaging Device when it is added to the CallManager.

CcmDeviceProductId-2 = other-1 = unknown1 = gwyCiscoCat6KT12 = gwyCiscoCat6KE13 = gwyCiscoCat6KFXS4 = gwyCiscoCat6KFXO7 = gwyCiscoDT24Plus8 = gwyCiscoDT30Plus9 = gwyCiscoDT2410 = gwyCiscoAT211 = gwyCiscoAT412 = gwyCiscoAT813 = gwyCiscoAS214 = gwyCiscoAS415 = gwyCiscoAS816 = h323Phone17 = h323Trunk18 = gwyCiscoMGCPFXOPort19 = gwyCiscoMGCPFXSPort27 = voiceMailUOnePort43 = gwyCiscoVG20044 = gwyCisco26XX45 = gwyCisco362X46 = gwyCisco364X47 = gwyCisco366X49 = h323AnonymousGatewy52 = gwyCiscoMGCPT1Port55 = gwyCiscoMGCPE1Port58 = gwyCiscoCat4224VoiceGwySwitch59 = gwyCiscoCat4000AccessGwyModule62 = gwyCiscoIAD240065 = gwyCiscoVGCEndPoint66 = gwyCiscoVG224AndV24867 = gwyCiscoSlotVGCPort68 = gwyCiscoVGCBox69 = gwyCiscoATA18670 = gwyCiscoICS77XXMRP2XX71 = gwyCiscoICS77XXASI8172 = gwyCiscoICS77XXASI16075 = h323H225GKControlledTrunk76 = h323ICTGKControlled77 = h323ICTNonGKControlled80 = gwyCiscoCat6000AVVIDServModule81 = gwyCiscoWSX660090 = gwyCiscoMGCPBRIPort95 = sipTrunk10001 = gwyCiscoWSSVCCMMMS20000 = gwyCisco374520002 = gwyCisco372530004 = gwyCiscoICS77XXMRP3XX30005 = gwyCiscoICS77XXMRP38FXS30006 = gwyCiscoICS77XXMRP316FXS30007 = gwyCiscoICS77XXMRP38FXOM130011 = gwyCisco269X30019 = gwyCisco176030020 = gwyCisco1751This syntax is used to identify the product id of a device. gwyCiscoCat6KT1(1): Cisco Catalyst 6000 T1 VoIP Gateway gwyCiscoCat6KE1(2): Cisco Catalyst 6000 E1 VoIP Gateway gwyCiscoCat6KFXS(3): Cisco Catalyst 6000 24 Port FXS Gateway gwyCiscoCat6KFXO(4): Cisco Catalyst 6000 12 Port FXO Gateway gwyCiscoDT24Plus(7): Cisco DT-24+ Gateway gwyCiscoDT30Plus(8): Cisco DT-30+ Gateway gwyCiscoDT24(9): Cisco DT-24 Gateway gwyCiscoAT2(10): Cisco AT2 Gateway gwyCiscoAT4(11): Cisco AT4 Gateway gwyCiscoAT8(12): Cisco AT8 Gateway gwyCiscoAS2(13): Cisco AS2 Gateway gwyCiscoAS4(14): Cisco AS4 Gateway gwyCiscoAS8(15): Cisco AS8 Gateway gwyCiscoMGCPFXOPort(18): Cisco MGCP FXO Port gwyCiscoMGCPFXSPort(19): Cisco MGCP FXS Port gwyCiscoVG200(43): Cisco VG200 gwyCisco26XX(44): Cisco 26XX gwyCisco362X(45): Cisco 362X gwyCisco364X(46): Cisco 364X gwyCisco366X(47): Cisco 366X gwyCiscoMGCPT1Port(52): Cisco MGCP T1 Port gwyCiscoMGCPE1Port(55): Cisco MGCP E1 Port gwyCiscoCat4224VoiceGwySwitch(58): Cisco CAT 4224 Voice Gateway Switch gwyCiscoCat4000AccessGwyModule(59): Cisco CAT 4000 Access Gateway Module gwyCiscoIAD2400(62): Cisco IAD2400 gwyCiscoVGCEndPoint(65): Cisco VGC PHONE gwyCiscoVG224AndV248(66): Cisco VGC Gateway gwyCiscoSlotVGCPort(67): Cisco VGC Port gwyciscoVGCBox(68): Cisco VGC Box gwyCiscoATA186(69): Cisco ATA 186 gwyCiscoICS77XXMRP2XX(70): Cisco ICS77XX-MRP2XX gwyCiscoICS77XXASI81(71): Cisco ICS77XX-ASI81 gwyCiscoICS77XXASI160(72): Cisco ICS77XX-ASI160 gwyCiscoCat6000AVVIDServModule(80): Cisco Catalyst 6000 AVVID Services Module gwyCiscoWSX6600(81): Cisco WS-X6600 gwyCiscoMGCPBRIPort(90): Cisco MGCP BRI Port gwyCiscoWSSVCCMMMS(10001): Cisco WS-SVC-CMM-MS gwyCisco3745(20000): Cisco 3745 gwyCisco3725(20002): Cisco 3725 gwyCiscoICS77XXMRP3XX(30004): Cisco ICS77XX MRP3XX gwyCiscoICS77XXMRP38FXS(30005): Cisco ICS77XX MRP3 8FXS gwyCiscoICS77XXMRP316FXS(30006): Cisco ICS77XX MRP3 16FXS gwyCiscoICS77XXMRP38FXOM1(30007): Cisco ICS77XX MRP3 8FXO M1 gwyCisco269X(30011): Cisco 269X gwyCisco1760(30019): Cisco 1760 gwyCisco1751(30020): Cisco 1751 h323Phone(16): H323 Phone h323Trunk(17): H323 Trunk h323AnonymousGateway(49): H323 Anonymous Gateway h323H225GKControlledTrunk(75): H225 Trunk Gatekeeper Controlled h323ICTGKControlled(76): Inter-Cluster Trunk Gatekeeper Controlled h323ICTNonGKControlled(77): Inter-Cluster Trunk Non-Gatekeeper Controlled voiceMailUOnePort(27): Uone Port sipTrunk(95): SIP Trunk unknown(-1): Unknown Device Product Id other(-2): Unidentified Device Product Id. · Integer32

The product identifier of the Voice Messaging device.

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

The description of the Voice Messaging Device. This description is given when the Voice Messaging Device is configured in the CUCM.

CcmDeviceStatus1 = unknown2 = registered3 = unregistered4 = rejected5 = partiallyregisteredThis syntax is used to identify the registration status of a device with the local call manager. unknown: The registration status of the device is unknown registered: The device has successfully registered with the local call manager unregistered: The device is no longer registered with the local call manager rejected: Registration request from the device was rejected by the local call manager. partiallyregistered: At least one but not all of the lines are successfully registered to the local call manager. Applicable only to SIP phones. · Integer32

The status of the Voice Messaging Device. The Voice Messaging Device status changes from unknown to registered when it registers itself with the local CUCM.

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

This object identifies the IP address type of the Voice Messaging device. The value of this object is 'unknown(0)'if the IP address of the Voice Messaging device is not available.

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

This object identifies the IP Address of the Voice Messaging Device. If the IP Address is not available then this object contains an empty string. The type of address for this is identified by ccmVMailDevInetAddressType.

CcmDevFailCauseCode0 = noError1 = unknown2 = noEntryInDatabase3 = databaseConfigurationError4 = deviceNameUnresolveable5 = maxDevRegReached6 = connectivityError7 = initializationError8 = deviceInitiatedReset9 = callManagerReset10 = authenticationError11 = invalidX509NameInCertificate12 = invalidTLSCipher13 = directoryNumberMismatch14 = malformedRegisterMsgThis syntax is used as means of identifying the reasons for a device communication error. noError: No Error unknown: Unknown error cause noEntryInDatabase: Device not configured properly in the CUCM database databaseConfigurationError: Device configuration error in the CUCM database deviceNameUnresolveable: The CallManager is unable to resolve the device name to an IP Address internally maxDevRegReached: Maximum number of device registrations have been reached connectivityError: CallManager is unable to establish communication with the device during registration initializationError: Indicates an error occurred when the CallManager tries to initialize the device deviceInitiatedReset: Indicates that the error was due to device initiated reset callManagerReset: Indicates that the error was due to call manager reset. authenticationError: Indicates mismatch between configured authentication mode and the authentication mode that the device is using to connect to the CallManager. invalidX509NameInCertificate: Indicates mismatch between the peer X.509 certificate subject name and what is configured for the device. invalidTLSCipher: Indicates Cipher mismatch during TLS handshake process. directoryNumberMismatch: Indicates mismatch between the directory number that the SIP device is trying to register with and the directory number configured in the CallManager for the SIP device. malformedRegisterMsg: Indicates that SIP device attempted to register with CallManager, but the REGISTER message contained formatting errors. · Integer32

The reason code associated with the Voice Messaging Device status change.

DateAndTimeA date-time specification. field octets contents range ----- ------ -------- ----- 1 1-2 year* 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC* 0..13 10 11 minutes from UTC 0..59 * Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: 1992-5-26,13:30:15.0,-4:0 Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d

The time the status of the voice messaging device changed.

DateAndTimeA date-time specification. field octets contents range ----- ------ -------- ----- 1 1-2 year* 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC* 0..13 10 11 minutes from UTC 0..59 * Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: 1992-5-26,13:30:15.0,-4:0 Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d

The time the Voice Messaging Device has last registered with the call manager.

CcmIndexOrZeroThis textual convention is an extension of the CcmIndex convention. The latter defines a greater than zero to identify an entry of the CUCM MIB table in the managed system. This extension permits the additional value of zero. The value zero is object- specific and must be defined as part of the description of any object which uses this syntax. · Unsigned32 · hint d

A positive value of this index is used to identify the related product type entry in the ccmProductTypeTable. A value of 0 indicates that the index to the ccmProductTypeTable is Unknown.

CcmDevUnregCauseCode0 = noError1 = unknown2 = noEntryInDatabase3 = databaseConfigurationError4 = deviceNameUnresolveable5 = maxDevRegExceeded6 = connectivityError7 = initializationError8 = deviceInitiatedReset9 = callManagerReset10 = deviceUnregistered11 = malformedRegisterMsg12 = sccpDeviceThrottling13 = keepAliveTimeout14 = configurationMismatch15 = callManagerRestart16 = duplicateRegistration17 = callManagerApplyConfig18 = deviceNoResponse19 = emLoginLogout20 = emccLoginLogout21 = energywisePowerSavePlus22 = callManagerForcedRestart23 = sourceIPAddrChanged24 = sourcePortChanged25 = registrationSequenceError26 = invalidCapabilities28 = fallbackInitiated29 = deviceSwitchThis syntax is used as means of identifying the reasons for a device getting unregistered. The scope of this enumeration can expand to comply with RFC 2578. noError: No Error unknown: Unknown error cause noEntryInDatabase: Device not configured properly in the CUCM database databaseConfigurationError: Device configuration error in the CUCM database deviceNameUnresolveable: The CallManager is unable to resolve the device name to an IP Address internally maxDevRegExceeded: Maximum number of device registrations have been reached connectivityError: CallManager is unable to establish communication with the device during registration initializationError: Indicates an error occurred when the CallManager tries to initialize the device deviceInitiatedReset: Indicates that the error was due to device initiated reset callManagerReset: Indicates that the error was due to call manager reset. deviceUnregistered: DeviceUnregistered. malformedRegisterMsg: Indicates that SIP device attempted to register with CallManager, but the REGISTER message contained formatting errors. sccpDeviceThrottling: The indicated SCCP device exceeded the maximum number of events allowed per-SCCP device. keepAliveTimeout: A KeepAlive message was not received. Possible causes include device power outage, network power outage, network configuration error, network delay,packet drops, packet corruption and CUCM node experiencing high CPU usage. configurationMismatch: The configuration on the SIP device does not match the configuration in CUCM. callManagerRestart: A device restart was initiated from CUCM Administration, either due to an explicit command from an administrator or due to a configuration change such as adding, deleting or changing a directory number associated with the device. duplicateRegistration: CUCM detected that the device attempted to register to two nodes at the same time. CUCM initiated a restart to the phone to force it to re-home to a single node. callManagerApplyConfig: CUCM configuration is changed. deviceNoResponse: Device is not responding Service Control Notify from CUCM. emLoginLogout: The device has been unregistered due to an Extension Mobility login or logout. emccLoginLogout: The device has been unregistered due to an Extension Mobility Cross Cluster login or logout. powerSavePlus: The device powered off as a result of the Power Save Plus feature that is enabled for this device. When the device powers off, it remains unregistered from CUCM until the Phone On Time defined in the Product Specific Configuration for this device. callManagerForcedRestart: The device did not respond to an Apply Config request and as a result, CUCM had sent a restart request to the device. The device may be offline due to a power outage or network problem. Confirm that the device is powered-up and that network connectivity exists between the device and CUCM. This is applicable for SIP protocol only. sourceIPAddrChanged: The device has been unregistered because the IP address in the Contact header of the REGISTER message has changed. The device will be automatically re-registered. No action is necessary. This is applicable for SIP protocol only. sourcePortChanged: The device has been unregistered because the port number in the Contact header of the REGISTER message has changed. The device will be automatically re-registered. No action is necessary. This is applicable for SIP protocol only. registrationSequenceError: A device requested configuration information from the CUCM at an unexpected time. The CUCM no longer had the requested information in memory. invalidCapabilities: The CUCM detected an error in the updated media capabilities reported by the device. The device reported the capabilities in one of the StationUpdateCapabilities message variants. This is applicable for SCCP protocol only. fallbackInitiated The device has initiated a fallback and will automatically re-register to a higher-priority CUCM. No action is necessary. deviceSwitch A second instance of an endpoint with the same device name has registered and assumed control. No action is necessary. · Integer32

The reason code associated with unregistered Voice Messaging Device.

CcmDevRegFailCauseCode0 = noError1 = unknown2 = noEntryInDatabase3 = databaseConfigurationError4 = deviceNameUnresolveable5 = maxDevRegExceeded6 = connectivityError7 = initializationError8 = deviceInitiatedReset9 = callManagerReset10 = authenticationError11 = invalidX509NameInCertificate12 = invalidTLSCipher13 = directoryNumberMismatch14 = malformedRegisterMsg15 = protocolMismatch16 = deviceNotActive17 = authenticatedDeviceAlreadyExists18 = obsoleteProtocolVersion23 = databaseTimeout25 = registrationSequenceError26 = invalidCapabilities27 = capabilityResponseTimeout28 = securityMismatch29 = autoRegisterDBError30 = dbAccessError31 = autoRegisterDBConfigTimeout32 = deviceTypeMismatch33 = addressingModeMismatchThis syntax is used as means of identifying the reasons for a device registration failure. The scope of this enumeration can expand to comply with RFC 2578. noError: No Error unknown: Unknown error cause noEntryInDatabase: Device not configured properly in the CUCM database databaseConfigurationError: Device configuration error in the CUCM database deviceNameUnresolveable: The CallManager is unable to resolve the device name to an IP Address internally maxDevRegExceeded: Maximum number of device registrations have been reached connectivityError: CallManager is unable to establish communication with the device during registration initializationError: Indicates an error occurred when the CallManager tries to initialize the device deviceInitiatedReset: Indicates that the error was due to device initiated reset callManagerReset: Indicates that the error was due to call manager reset. authenticationError: Indicates mismatch between configured authentication mode and the authentication mode that the device is using to connect to the CallManager. invalidX509NameInCertificate: Indicates mismatch between the peer X.509 certificate subject name and what is configured for the device. invalidTLSCipher: Indicates Cipher mismatch during TLS handshake process. directoryNumberMismatch: Indicates mismatch between the directory number that the SIP device is trying to register with and the directory number configured in the CallManager for the SIP device. malformedRegisterMsg: Indicates that SIP device attempted to register with CallManager, but the REGISTER message contained formatting errors. protocolMismatch: The protocol of the device (SIP or SCCP) does not match the configured protocol in CUCM. deviceNotActive: The device has not been activated. authenticatedDeviceAlreadyExists: A device with the same name is already registered with CUCM. obsoleteProtocolVersion: The SCCP device registered with an obsolete protocol version. databaseTimeout: CUCM requested device configuration data from the database but did not receive a response within 10 minutes. registrationSequenceError: A device requested configuration information from the CUCM at an unexpected time. The CUCM had not yet obtained the requested information. The device will automatically attempt to register again. If this alarm occurs again, manually reset the device. If this alarm continues to occur after the manual reset, there may be an internal firmware error. This is applicable for SCCP protocol only. invalidCapabilities: The CUCM detected an error in the media capabilities reported in the StationCapabilitiesRes message by the device during registration. The device will automatically attempt to register again. If this alarm occurs again, manually reset the device. If this alarm continues to occur after the manual reset, there may be a protocol error. This is applicable for SCCP protocol only. capabilityResponseTimeout: The CUCM timed out while waiting for the device to respond to a request to report its media capabilities. Possible causes include device power outage, network power outage, network configuration error, network delay, packet drops, and packet corruption. It is also possible to get this error if the CUCM node is experiencing high CPU usage. Verify that the device is powered up and operating. Verify that network connectivity exists between the device and CUCM, and verify that the CPU utilization is in the safe range. This is applicable for SCCP protocol only. securityMismatch: The CUCM detected a mismatch in the security settings of the device and/or the CUCM. The mismatches that can be detected are: 1) The device established a secure connection, yet reported that it does not have the ability to do authenticated signaling. 2) The device did not establish a secure connection, but the security mode configured for the device indicates that it should have done so. 3) The device established a secure connection, but the security mode configured for the device indicates that it should not have done so autoRegisterDBError: Auto-registration of a device failed for one of the following reasons: 1)Auto-registration is not allowed for the device type. 2)An error occurred while adding the auto-registering device to the database (stored procedure). dbAccessError: Device registration failed because of an error that occurred while building the station registration profile. This usually indicates a synchronization problem with the database. autoRegisterDBConfigTimeout: The CUCM timed out during auto-registration of a device. The registration profile of the device did not get inserted into the database in time. The device will automatically attempt to register again. This is applicable for SCCP protocol only. deviceTypeMismatch: The device type reported by the device does not match the device type configured on the CUCM addressingModeMismatch: The CUCM detected an error related to the addressing mode configured for the device. One of the following errors were detected: 1)The device is configured to use only IPv4 addressing, but did not specify an IPv4 address. 2)The device is configured to use only IPv6 addressing, but did not specify an IPv6 address. This is applicable for SCCP protocol only. · Integer32

The reason code associated with registration failed Voice Messaging Device.

CcmIndexThis syntax is used as the Index into a table. A positive value is used to identify a unique entry in the table. (1..4294967295) · Unsigned32 · hint d

An arbitrary integer, selected by the local system, which identifies a Directory Number of a Voice Messaging Device.

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..24) · OCTET STRING · hint 255t

The Directory Number of the Voice Messaging Device.

CcmIndexThis syntax is used as the Index into a table. A positive value is used to identify a unique entry in the table. (1..4294967295) · Unsigned32 · hint d

An arbitrary integer, selected by the local CUCM, which identifies a SIP Trunk Device entry in the table.

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..128) · OCTET STRING · hint 255t

The device name assigned to the SIP Trunk Device. This name is assigned when a new SIP Trunk device is added to the CallManager.

CcmIndexOrZeroThis textual convention is an extension of the CcmIndex convention. The latter defines a greater than zero to identify an entry of the CUCM MIB table in the managed system. This extension permits the additional value of zero. The value zero is object- specific and must be defined as part of the description of any object which uses this syntax. · Unsigned32 · hint d

A positive value of this index is used to identify the related product type entry in the ccmProductTypeTable. A value of 0 indicates that the index to the ccmProductTypeTable is Unknown.

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

A description of the SIP Trunk device. This description is given when the SIP Trunk device is configured in the CUCM.

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

Identifies the IP address type of the SIP Trunk Device.

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

Identifies last known IP Address of the SIP Trunk device. The type of address for this is identified by ccmSIPDevInetAddressType.

CcmSIPTransportProtocolType1 = unknown2 = tcp3 = udp4 = tcpAndUdp5 = tlsThis textual convention defines the possible transport protocol types which are used for setting up SIP calls unknown: The SIP Trunk transport type is unknown tcp: The SIP Trunk transport type is tcp udp: The SIP Trunk transport type is udp tcpAndUdp: The SIP Trunk transport type is tcp and udp. Applicable only for InTransportProtocolType. tls: The SIP Trunk transport type is tls. · Integer32

Specifies the transport protocol type used by CallManager for setting up incoming SIP call.

InetPortNumberRepresents a 16 bit port number of an Internet transport layer protocol. Port numbers are assigned by IANA. A current list of all assignments is available from <http://www.iana.org/>. The value zero is object-specific and must be defined as part of the description of any object that uses this syntax. Examples of the usage of zero might include situations where a port number is unknown, or when the value zero is used as a wildcard in a filter.Reference: STD 6 (RFC 768), STD 7 (RFC 793) and RFC 2960 (0..65535) · Unsigned32 · hint d

Specifies the port number used by CallManager for setting up incoming SIP call.

CcmSIPTransportProtocolType1 = unknown2 = tcp3 = udp4 = tcpAndUdp5 = tlsThis textual convention defines the possible transport protocol types which are used for setting up SIP calls unknown: The SIP Trunk transport type is unknown tcp: The SIP Trunk transport type is tcp udp: The SIP Trunk transport type is udp tcpAndUdp: The SIP Trunk transport type is tcp and udp. Applicable only for InTransportProtocolType. tls: The SIP Trunk transport type is tls. · Integer32

Specifies the transport protocol type used by CallManager for setting up outgoing SIP call.

InetPortNumberRepresents a 16 bit port number of an Internet transport layer protocol. Port numbers are assigned by IANA. A current list of all assignments is available from <http://www.iana.org/>. The value zero is object-specific and must be defined as part of the description of any object that uses this syntax. Examples of the usage of zero might include situations where a port number is unknown, or when the value zero is used as a wildcard in a filter.Reference: STD 6 (RFC 768), STD 7 (RFC 793) and RFC 2960 (0..65535) · Unsigned32 · hint d

Specifies the port number used by CallManager for setting up outgoing SIP call.

InetAddressIPv4Represents an IPv4 network address: Octets Contents Encoding 1-4 IPv4 address network-byte order The corresponding InetAddressType value is ipv4(1). This textual convention SHOULD NOT be used directly in object definitions, as it restricts addresses to a specific format. However, if it is used, it MAY be used either on its own or in conjunction with InetAddressType, as a pair. SIZE (4) · OCTET STRING · hint 1d.1d.1d.1d

This object identifies the last known primary IPv4 address of the SIP Trunk Device. This object contains value zero if IPV4 address is not available

InetAddressIPv6Represents an IPv6 network address: Octets Contents Encoding 1-16 IPv6 address network-byte order The corresponding InetAddressType value is ipv6(2). This textual convention SHOULD NOT be used directly in object definitions, as it restricts addresses to a specific format. However, if it is used, it MAY be used either on its own or in conjunction with InetAddressType, as a pair. SIZE (16) · OCTET STRING · hint 2x:2x:2x:2x:2x:2x:2x:2x

This object identifies the last known primary IPv6 address of the SIP Trunk Device. This object contains value zero if IPV6 address is not available