Reference record for OID 1.3.6.1.4.1.7505.1.1.16.1.6



parent
1.3.6.1.4.1.7505.1.1.16.1 (callManagerConnectionEntry)
node code
6
node name
cmConnectionState
dot oid
1.3.6.1.4.1.7505.1.1.16.1.6
type
OBJECT-TYPE
asn1 oid
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) calista(7505) products(1) dpa(1) callManagerConnectionTable(16) callManagerConnectionEntry(1) cmConnectionState(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) calista(7505) products(1) dpa(1) callManagerConnectionTable(16) callManagerConnectionEntry(1) cmConnectionState(6)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) calista(7505) products(1) dpa(1) callManagerConnectionTable(16) callManagerConnectionEntry(1) cmConnectionState(6)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) calista(7505) products(1) dpa(1) callManagerConnectionTable(16) callManagerConnectionEntry(1) cmConnectionState(6)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) calista(7505) products(1) dpa(1) callManagerConnectionTable(16) callManagerConnectionEntry(1) cmConnectionState(6)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) calista(7505) products(1) dpa(1) callManagerConnectionTable(16) callManagerConnectionEntry(1) cmConnectionState(6)}
  • iri oid
  • /iso/identified-organization/dod/internet/private/enterprise/calista/products/dpa/callManagerConnectionTable/callManagerConnectionEntry/cmConnectionState
  • /iso/identified-organization/dod/internet/private/enterprises/calista/products/dpa/callManagerConnectionTable/callManagerConnectionEntry/cmConnectionState
  • /iso/org/dod/internet/private/enterprise/calista/products/dpa/callManagerConnectionTable/callManagerConnectionEntry/cmConnectionState
  • /iso/org/dod/internet/private/enterprises/calista/products/dpa/callManagerConnectionTable/callManagerConnectionEntry/cmConnectionState
  • /iso/iso-identified-organization/dod/internet/private/enterprise/calista/products/dpa/callManagerConnectionTable/callManagerConnectionEntry/cmConnectionState
  • /iso/iso-identified-organization/dod/internet/private/enterprises/calista/products/dpa/callManagerConnectionTable/callManagerConnectionEntry/cmConnectionState
  • iri by oid_info
    /ISO/Identified-Organization/6/1/4/1/7505/1/1/16/1/6

    Description by circitor

    The current state of this connection. The possible values have
    the following meanings:
    idle initial state of the link before a
    connection has been attempted, and the
    state to which a link changes after
    teardown

    connecting a TCP link to a Cisco CallManager system
    is in the process of being established

    retryBackOff the attempt to establish to the Cisco
    CallManager failed; the connection stays in
    this state for a short while before the DPA
    tries again

    connectPending the retry back off period has finished and
    the DPA is about to re-attempt connection
    to the Cisco CallManager

    active the connection has been successfully
    established; this state signifies that the
    connection is being used for transmission
    and reception of Skinny Station Protocol
    messages

    standby the connection has been successfully
    established but it is not currently being
    used for data traffic; however, it would
    move into the active state were the
    currently active connection to go down

    Parsed from file CALISTA-DPA-MIB.mib
    Module: CALISTA-DPA-MIB

    Description by cisco_v1

    The current state of this connection. The possible values have
    the following meanings:
    idle initial state of the link before a
    connection has been attempted, and the
    state to which a link changes after
    teardown

    connecting a TCP link to a Cisco CallManager system
    is in the process of being established

    retryBackOff the attempt to establish to the Cisco
    CallManager failed; the connection stays in
    this state for a short while before the DPA
    tries again

    connectPending the retry back off period has finished and
    the DPA is about to re-attempt connection
    to the Cisco CallManager

    active the connection has been successfully
    established; this state signifies that the
    connection is being used for transmission
    and reception of Skinny Station Protocol
    messages

    standby the connection has been successfully
    established but it is not currently being
    used for data traffic; however, it would
    move into the active state were the
    currently active connection to go down

    Description by mibdepot

    The current state of this connection. The possible values have
    the following meanings:
    idle initial state of the link before a
    connection has been attempted, and the
    state to which a link changes after
    teardown

    connecting a TCP link to a Cisco CallManager system
    is in the process of being established

    retryBackOff the attempt to establish to the Cisco
    CallManager failed; the connection stays in
    this state for a short while before the DPA
    tries again

    connectPending the retry back off period has finished and
    the DPA is about to re-attempt connection
    to the Cisco CallManager

    active the connection has been successfully
    established; this state signifies that the
    connection is being used for transmission
    and reception of Skinny Station Protocol
    messages

    standby the connection has been successfully
    established but it is not currently being
    used for data traffic; however, it would
    move into the active state were the
    currently active connection to go down

    Parsed from file CALISTA-DPA-MIB.my.txt
    Company: None
    Module: CALISTA-DPA-MIB

    Description by cisco

    The current state of this connection. The possible values have
    the following meanings:
    idle initial state of the link before a
    connection has been attempted, and the
    state to which a link changes after
    teardown

    connecting a TCP link to a Cisco CallManager system
    is in the process of being established

    retryBackOff the attempt to establish to the Cisco
    CallManager failed; the connection stays in
    this state for a short while before the DPA
    tries again

    connectPending the retry back off period has finished and
    the DPA is about to re-attempt connection
    to the Cisco CallManager

    active the connection has been successfully
    established; this state signifies that the
    connection is being used for transmission
    and reception of Skinny Station Protocol
    messages

    standby the connection has been successfully
    established but it is not currently being
    used for data traffic; however, it would
    move into the active state were the
    currently active connection to go down

    Information by circitor

    cmConnectionState OBJECT-TYPE SYNTAX INTEGER { idle(1), connecting(2), retryBackOff(3), connectPending(4), active(5), standby(6) } ACCESS read-only STATUS mandatory DESCRIPTION "The current state of this connection. The possible values have the following meanings: idle initial state of the link before a connection has been attempted, and the state to which a link changes after teardown connecting a TCP link to a Cisco CallManager system is in the process of being established retryBackOff the attempt to establish to the Cisco CallManager failed; the connection stays in this state for a short while before the DPA tries again connectPending the retry back off period has finished and the DPA is about to re-attempt connection to the Cisco CallManager active the connection has been successfully established; this state signifies that the connection is being used for transmission and reception of Skinny Station Protocol messages standby the connection has been successfully established but it is not currently being used for data traffic; however, it would move into the active state were the currently active connection to go down " ::= { callManagerConnectionEntry 6 }

    Information by cisco_v1

    cmConnectionState OBJECT-TYPE SYNTAX INTEGER { idle(1), connecting(2), retryBackOff(3), connectPending(4), active(5), standby(6) } ACCESS read-only STATUS mandatory DESCRIPTION "The current state of this connection. The possible values have the following meanings: idle initial state of the link before a connection has been attempted, and the state to which a link changes after teardown connecting a TCP link to a Cisco CallManager system is in the process of being established retryBackOff the attempt to establish to the Cisco CallManager failed; the connection stays in this state for a short while before the DPA tries again connectPending the retry back off period has finished and the DPA is about to re-attempt connection to the Cisco CallManager active the connection has been successfully established; this state signifies that the connection is being used for transmission and reception of Skinny Station Protocol messages standby the connection has been successfully established but it is not currently being used for data traffic; however, it would move into the active state were the currently active connection to go down " ::= { callManagerConnectionEntry 6 }

    Information by oid_info

    Vendor: Calista Ltd.
    Module: CALISTA-DPA-MIB

    [Automatically extracted from oidview.com]

    Information by mibdepot

    cmConnectionState OBJECT-TYPE SYNTAX INTEGER { idle(1), connecting(2), retryBackOff(3), connectPending(4), active(5), standby(6) } ACCESS read-only STATUS mandatory DESCRIPTION "The current state of this connection. The possible values have the following meanings: idle initial state of the link before a connection has been attempted, and the state to which a link changes after teardown connecting a TCP link to a Cisco CallManager system is in the process of being established retryBackOff the attempt to establish to the Cisco CallManager failed; the connection stays in this state for a short while before the DPA tries again connectPending the retry back off period has finished and the DPA is about to re-attempt connection to the Cisco CallManager active the connection has been successfully established; this state signifies that the connection is being used for transmission and reception of Skinny Station Protocol messages standby the connection has been successfully established but it is not currently being used for data traffic; however, it would move into the active state were the currently active connection to go down " ::= { callManagerConnectionEntry 6 }

    Information by cisco

    cmConnectionState OBJECT-TYPE SYNTAX INTEGER { idle(1), connecting(2), retryBackOff(3), connectPending(4), active(5), standby(6) } ACCESS read-only STATUS mandatory DESCRIPTION "The current state of this connection. The possible values have the following meanings: idle initial state of the link before a connection has been attempted, and the state to which a link changes after teardown connecting a TCP link to a Cisco CallManager system is in the process of being established retryBackOff the attempt to establish to the Cisco CallManager failed; the connection stays in this state for a short while before the DPA tries again connectPending the retry back off period has finished and the DPA is about to re-attempt connection to the Cisco CallManager active the connection has been successfully established; this state signifies that the connection is being used for transmission and reception of Skinny Station Protocol messages standby the connection has been successfully established but it is not currently being used for data traffic; however, it would move into the active state were the currently active connection to go down " ::= { callManagerConnectionEntry 6 }

    First Registration Authority (recovered by parent 1.3.6.1.4.1.7505)

    Pepperell Andy

    Brothers (5)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.4.1.7505.1.1.16.1.1 cmConnectionPortIndex 0 0 Corresponds to portIndex in PortEntry.
    1.3.6.1.4.1.7505.1.1.16.1.2 cmConnectionIndex 0 0 The index of this connection; each port can have connections
    to several Cisco CallManagers, with one active connection and
    the re…
    1.3.6.1.4.1.7505.1.1.16.1.3 cmConnectionCallManagerName 0 0 The host name, if known, of the CallManager to which this
    connection refers.
    1.3.6.1.4.1.7505.1.1.16.1.4 cmConnectionIpAddress 0 0 The IP address of the CallManager to which this connection
    refers.
    1.3.6.1.4.1.7505.1.1.16.1.5 cmConnectionIpPort 0 0 The TCP port number on the CallManager to which this connection
    has been made.