Reference record for OID 1.3.6.1.4.1.9.9.63.1.2.1.1



parent
1.3.6.1.4.1.9.9.63.1.2.1 (cvPeerCfgTable)
node code
1
node name
cvPeerCfgEntry
dot oid
1.3.6.1.4.1.9.9.63.1.2.1.1
type
OBJECT-TYPE
asn1 oid
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoVoiceDialControlMIB(63) cvdcMIBObjects(1) cvPeer(2) cvPeerCfgTable(1) cvPeerCfgEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoVoiceDialControlMIB(63) cvdcMIBObjects(1) cvPeer(2) cvPeerCfgTable(1) cvPeerCfgEntry(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoVoiceDialControlMIB(63) cvdcMIBObjects(1) cvPeer(2) cvPeerCfgTable(1) cvPeerCfgEntry(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoVoiceDialControlMIB(63) cvdcMIBObjects(1) cvPeer(2) cvPeerCfgTable(1) cvPeerCfgEntry(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoVoiceDialControlMIB(63) cvdcMIBObjects(1) cvPeer(2) cvPeerCfgTable(1) cvPeerCfgEntry(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoVoiceDialControlMIB(63) cvdcMIBObjects(1) cvPeer(2) cvPeerCfgTable(1) cvPeerCfgEntry(1)}
    • iri oid
  • /iso/identified-organization/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoVoiceDialControlMIB/cvdcMIBObjects/cvPeer/cvPeerCfgTable/cvPeerCfgEntry
  • /iso/identified-organization/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoVoiceDialControlMIB/cvdcMIBObjects/cvPeer/cvPeerCfgTable/cvPeerCfgEntry
  • /iso/org/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoVoiceDialControlMIB/cvdcMIBObjects/cvPeer/cvPeerCfgTable/cvPeerCfgEntry
  • /iso/org/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoVoiceDialControlMIB/cvdcMIBObjects/cvPeer/cvPeerCfgTable/cvPeerCfgEntry
  • /iso/iso-identified-organization/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoVoiceDialControlMIB/cvdcMIBObjects/cvPeer/cvPeerCfgTable/cvPeerCfgEntry
  • /iso/iso-identified-organization/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoVoiceDialControlMIB/cvdcMIBObjects/cvPeer/cvPeerCfgTable/cvPeerCfgEntry
    • iri by oid_info
    /ISO/Identified-Organization/6/1/4/1/9/9/63/1/2/1/1

    Description by circitor

    A single voice generic Peer. The creation of this
    entry will create an associated ifEntry with an ifType
    that is associated with cvPeerCfgType, i.e., for
    'voiceEncap' encapsulation, an ifEntry will contain an
    ifType voiceEncap(103); for 'voiceOverIp' encapsulation,
    an ifEntry will contain an ifType voiceOverIp(104). The
    ifAdminStatus of the newly created ifEntry is set to 'up'
    and ifOperStatus is set to 'down'. In addition, an
    associated voiceEncap/voiceOverIp Peer configuration
    entry is created after the successful ifEntry creation.
    Then ifIndex of the newly created ifEntry must be used by
    the network manager to create a peer configuration entry
    of IETF Dial Control MIB (Refer to RFC 2128 section
    2.2.3.1 and the description of dialCtlPeerCfgEntry for the
    detailed information).
    In summary, the voice dial peer creation steps are as
    follows:
    [1] create this entry (voice/data generic peer entry).
    [2] read the cvPeerCfgIfIndex of this entry for the
    ifIndex of newly created voice/data generic peer.
    [3] create the dialCtlPeerCfgEntry of RFC 2128 with the
    indices of dialCtlPeerCfgId and the ifIndex of newly
    created voice generic peer.

    For each VoIP peer, it uses IP address and UDP port with
    RTP protocol to transfer voice packet. Therefore, it does
    not have its lower layer interface. The
    dialCtlPeerCfgIfType object of IETF Dial Control MIB must
    set to 'other' and the dialCtlPeerCfgLowerIf must set to
    '0'.

    After the successful creation of peer configuration entry
    of IETF Dial Control MIB, the dial plan software in
    managed device will set the ifOperStatus of the newly
    created voiceEncap/voiceOverIp ifEntry to 'up' for
    enabling the peer function if the peer configuration is
    completed.
    When this entry is deleted, its associated ifEntry,
    voiceEncap/voiceOverIp specific peer entry and the peer
    entry of IETF Dial Control MIB are deleted.

    Parsed from file CISCO-VOICE-DIAL-CONTROL-MIB.mib
    Module: CISCO-VOICE-DIAL-CONTROL-MIB

    Description by cisco_v1

    A single voice generic Peer. The creation of this
    entry will create an associated ifEntry with an ifType
    that is associated with cvPeerCfgType, i.e., for
    'voiceEncap' encapsulation, an ifEntry will contain an
    ifType voiceEncap(103); for 'voiceOverIp' encapsulation,
    an ifEntry will contain an ifType voiceOverIp(104). The
    ifAdminStatus of the newly created ifEntry is set to 'up'
    and ifOperStatus is set to 'down'. In addition, an
    associated voiceEncap/voiceOverIp Peer configuration
    entry is created after the successful ifEntry creation.
    Then ifIndex of the newly created ifEntry must be used by
    the network manager to create a peer configuration entry
    of IETF Dial Control MIB (Refer to RFC 2128 section
    2.2.3.1 and the description of dialCtlPeerCfgEntry for the
    detailed information).
    In summary, the voice dial peer creation steps are as
    follows:
    [1] create this entry (voice/data generic peer entry).
    [2] read the cvPeerCfgIfIndex of this entry for the
    ifIndex of newly created voice/data generic peer.
    [3] create the dialCtlPeerCfgEntry of RFC 2128 with the
    indices of dialCtlPeerCfgId and the ifIndex of newly
    created voice generic peer.

    For each VoIP peer, it uses IP address and UDP port with
    RTP protocol to transfer voice packet. Therefore, it does
    not have its lower layer interface. The
    dialCtlPeerCfgIfType object of IETF Dial Control MIB must
    set to 'other' and the dialCtlPeerCfgLowerIf must set to
    '0'.

    After the successful creation of peer configuration entry
    of IETF Dial Control MIB, the dial plan software in
    managed device will set the ifOperStatus of the newly
    created voiceEncap/voiceOverIp ifEntry to 'up' for
    enabling the peer function if the peer configuration is
    completed.
    When this entry is deleted, its associated ifEntry,
    voiceEncap/voiceOverIp specific peer entry and the peer
    entry of IETF Dial Control MIB are deleted.

    Description by mibdepot

    A single voice generic Peer. The creation of this
    entry will create an associated ifEntry with an ifType
    that is associated with cvPeerCfgType, i.e., for
    'voiceEncap' encapsulation, an ifEntry will contain an
    ifType voiceEncap(103); for 'voiceOverIp' encapsulation,
    an ifEntry will contain an ifType voiceOverIp(104). The
    ifAdminStatus of the newly created ifEntry is set to 'up'
    and ifOperStatus is set to 'down'. In addition, an
    associated voiceEncap/voiceOverIp Peer configuration
    entry is created after the successful ifEntry creation.
    Then ifIndex of the newly created ifEntry must be used by
    the network manager to create a peer configuration entry
    of IETF Dial Control MIB (Refer to RFC 2128 section
    2.2.3.1 and the description of dialCtlPeerCfgEntry for the
    detailed information).
    In summary, the voice dial peer creation steps are as
    follows:
    [1] create this entry (voice/data generic peer entry).
    [2] read the cvPeerCfgIfIndex of this entry for the
    ifIndex of newly created voice/data generic peer.
    [3] create the dialCtlPeerCfgEntry of RFC 2128 with the
    indices of dialCtlPeerCfgId and the ifIndex of newly
    created voice generic peer.

    For each VoIP peer, it uses IP address and UDP port with
    RTP protocol to transfer voice packet. Therefore, it does
    not have its lower layer interface. The
    dialCtlPeerCfgIfType object of IETF Dial Control MIB must
    set to 'other' and the dialCtlPeerCfgLowerIf must set to
    '0'.

    After the successful creation of peer configuration entry
    of IETF Dial Control MIB, the dial plan software in
    managed device will set the ifOperStatus of the newly
    created voiceEncap/voiceOverIp ifEntry to 'up' for
    enabling the peer function if the peer configuration is
    completed.
    When this entry is deleted, its associated ifEntry,
    voiceEncap/voiceOverIp specific peer entry and the peer
    entry of IETF Dial Control MIB are deleted.

    Parsed from file CISCO-VOICE-DIAL-CONTROL-MIB.my.txt
    Company: None
    Module: CISCO-VOICE-DIAL-CONTROL-MIB

    Description by cisco

    A single voice generic Peer. The creation of this
    entry will create an associated ifEntry with an ifType
    that is associated with cvPeerCfgType, i.e., for
    'voiceEncap' encapsulation, an ifEntry will contain an
    ifType voiceEncap(103); for 'voiceOverIp' encapsulation,
    an ifEntry will contain an ifType voiceOverIp(104). The
    ifAdminStatus of the newly created ifEntry is set to 'up'
    and ifOperStatus is set to 'down'. In addition, an
    associated voiceEncap/voiceOverIp Peer configuration
    entry is created after the successful ifEntry creation.
    Then ifIndex of the newly created ifEntry must be used by
    the network manager to create a peer configuration entry
    of IETF Dial Control MIB (Refer to RFC 2128 section
    2.2.3.1 and the description of dialCtlPeerCfgEntry for the
    detailed information).
    In summary, the voice dial peer creation steps are as
    follows:
    [1] create this entry (voice/data generic peer entry).
    [2] read the cvPeerCfgIfIndex of this entry for the
    ifIndex of newly created voice/data generic peer.
    [3] create the dialCtlPeerCfgEntry of RFC 2128 with the
    indices of dialCtlPeerCfgId and the ifIndex of newly
    created voice generic peer.

    For each VoIP peer, it uses IP address and UDP port with
    RTP protocol to transfer voice packet. Therefore, it does
    not have its lower layer interface. The
    dialCtlPeerCfgIfType object of IETF Dial Control MIB must
    set to 'other' and the dialCtlPeerCfgLowerIf must set to
    '0'.

    After the successful creation of peer configuration entry
    of IETF Dial Control MIB, the dial plan software in
    managed device will set the ifOperStatus of the newly
    created voiceEncap/voiceOverIp ifEntry to 'up' for
    enabling the peer function if the peer configuration is
    completed.
    When this entry is deleted, its associated ifEntry,
    voiceEncap/voiceOverIp specific peer entry and the peer
    entry of IETF Dial Control MIB are deleted.

    Information by circitor

    cvPeerCfgEntry OBJECT-TYPE
    SYNTAX          CvPeerCfgEntry
    MAX-ACCESS      not-accessible
    STATUS          current
    DESCRIPTION
        "A single voice generic Peer. The creation of this
        entry will create an associated ifEntry with an ifType
        that is associated with cvPeerCfgType, i.e., for
        'voiceEncap' encapsulation, an ifEntry will contain an
        ifType voiceEncap(103); for 'voiceOverIp' encapsulation,
        an ifEntry will contain an ifType voiceOverIp(104). The
        ifAdminStatus of the newly created ifEntry is set to 'up'
        and ifOperStatus is set to 'down'. In addition, an
        associated voiceEncap/voiceOverIp Peer configuration
        entry is created after the successful ifEntry creation.
        Then ifIndex of the newly created ifEntry must be used by
        the network manager to create a peer configuration entry
        of IETF Dial Control MIB (Refer to RFC 2128 section
        2.2.3.1 and the description of dialCtlPeerCfgEntry for the
        detailed information).
        In summary, the voice dial peer creation steps are as
        follows:
        [1] create this entry (voice/data generic peer entry).
        [2] read the cvPeerCfgIfIndex of this entry for the
            ifIndex of newly created voice/data generic peer.
        [3] create the dialCtlPeerCfgEntry of RFC 2128 with the
            indices of dialCtlPeerCfgId and the ifIndex of newly
            created voice generic peer.

        For each VoIP peer, it uses IP address and UDP port with
        RTP protocol to transfer voice packet. Therefore, it does
        not have its lower layer interface. The
        dialCtlPeerCfgIfType object of IETF Dial Control MIB must
        set to 'other' and the dialCtlPeerCfgLowerIf must set to
        '0'.

        After the successful creation of peer configuration entry
        of IETF Dial Control MIB, the dial plan software in
        managed device will set the ifOperStatus of the newly
        created voiceEncap/voiceOverIp ifEntry to 'up' for
        enabling the peer function if the peer configuration is
        completed.
        When this entry is deleted, its associated ifEntry,
        voiceEncap/voiceOverIp specific peer entry and the peer
        entry of IETF Dial Control MIB are deleted."
    INDEX           { cvPeerCfgIndex } 
    ::= { cvPeerCfgTable 1 }

    Information by cisco_v1

    cvPeerCfgEntry OBJECT-TYPE
    SYNTAX CvPeerCfgEntry
    ACCESS not-accessible
    STATUS mandatory
    DESCRIPTION
        "A single voice generic Peer. The creation of this
        entry will create an associated ifEntry with an ifType
        that is associated with cvPeerCfgType, i.e., for
        'voiceEncap' encapsulation, an ifEntry will contain an
        ifType voiceEncap(103); for 'voiceOverIp' encapsulation,
        an ifEntry will contain an ifType voiceOverIp(104). The
        ifAdminStatus of the newly created ifEntry is set to 'up'
        and ifOperStatus is set to 'down'. In addition, an
        associated voiceEncap/voiceOverIp Peer configuration
        entry is created after the successful ifEntry creation.
        Then ifIndex of the newly created ifEntry must be used by
        the network manager to create a peer configuration entry
        of IETF Dial Control MIB (Refer to RFC 2128 section
        2.2.3.1 and the description of dialCtlPeerCfgEntry for the
        detailed information).
        In summary, the voice dial peer creation steps are as
        follows:
        [1] create this entry (voice/data generic peer entry).
        [2] read the cvPeerCfgIfIndex of this entry for the
            ifIndex of newly created voice/data generic peer.
        [3] create the dialCtlPeerCfgEntry of RFC 2128 with the
            indices of dialCtlPeerCfgId and the ifIndex of newly
            created voice generic peer.
        
        For each VoIP peer, it uses IP address and UDP port with
        RTP protocol to transfer voice packet. Therefore, it does
        not have its lower layer interface. The
        dialCtlPeerCfgIfType object of IETF Dial Control MIB must
        set to 'other' and the dialCtlPeerCfgLowerIf must set to
        '0'.
        
        After the successful creation of peer configuration entry
        of IETF Dial Control MIB, the dial plan software in
        managed device will set the ifOperStatus of the newly
        created voiceEncap/voiceOverIp ifEntry to 'up' for
        enabling the peer function if the peer configuration is
        completed.
        When this entry is deleted, its associated ifEntry,
        voiceEncap/voiceOverIp specific peer entry and the peer
        entry of IETF Dial Control MIB are deleted."
    INDEX { cvPeerCfgIndex }
    ::= { cvPeerCfgTable 1 }

    Information by oid_info

    Vendor: Cisco
    Module: CISCO-VOICE-DIAL-CONTROL-MIB

    [Automatically extracted from oidview.com]

    Information by mibdepot

    cvPeerCfgEntry OBJECT-TYPE
    SYNTAX          CvPeerCfgEntry
    MAX-ACCESS      not-accessible
    STATUS          current
    DESCRIPTION
        "A single voice generic Peer. The creation of this
        entry will create an associated ifEntry with an ifType
        that is associated with cvPeerCfgType, i.e., for
        'voiceEncap' encapsulation, an ifEntry will contain an
        ifType voiceEncap(103); for 'voiceOverIp' encapsulation,
        an ifEntry will contain an ifType voiceOverIp(104). The
        ifAdminStatus of the newly created ifEntry is set to 'up'
        and ifOperStatus is set to 'down'. In addition, an
        associated voiceEncap/voiceOverIp Peer configuration
        entry is created after the successful ifEntry creation.
        Then ifIndex of the newly created ifEntry must be used by
        the network manager to create a peer configuration entry
        of IETF Dial Control MIB (Refer to RFC 2128 section
        2.2.3.1 and the description of dialCtlPeerCfgEntry for the
        detailed information).
        In summary, the voice dial peer creation steps are as
        follows:
        [1] create this entry (voice/data generic peer entry).
        [2] read the cvPeerCfgIfIndex of this entry for the
            ifIndex of newly created voice/data generic peer.
        [3] create the dialCtlPeerCfgEntry of RFC 2128 with the
            indices of dialCtlPeerCfgId and the ifIndex of newly
            created voice generic peer.

        For each VoIP peer, it uses IP address and UDP port with
        RTP protocol to transfer voice packet. Therefore, it does
        not have its lower layer interface. The
        dialCtlPeerCfgIfType object of IETF Dial Control MIB must
        set to 'other' and the dialCtlPeerCfgLowerIf must set to
        '0'.

        After the successful creation of peer configuration entry
        of IETF Dial Control MIB, the dial plan software in
        managed device will set the ifOperStatus of the newly
        created voiceEncap/voiceOverIp ifEntry to 'up' for
        enabling the peer function if the peer configuration is
        completed.
        When this entry is deleted, its associated ifEntry,
        voiceEncap/voiceOverIp specific peer entry and the peer
        entry of IETF Dial Control MIB are deleted."
    INDEX           { cvPeerCfgIndex } 
    ::= { cvPeerCfgTable 1 }

    Information by cisco

    cvPeerCfgEntry OBJECT-TYPE
    SYNTAX          CvPeerCfgEntry
    MAX-ACCESS      not-accessible
    STATUS          current
    DESCRIPTION
        "A single voice generic Peer. The creation of this
        entry will create an associated ifEntry with an ifType
        that is associated with cvPeerCfgType, i.e., for
        'voiceEncap' encapsulation, an ifEntry will contain an
        ifType voiceEncap(103); for 'voiceOverIp' encapsulation,
        an ifEntry will contain an ifType voiceOverIp(104). The
        ifAdminStatus of the newly created ifEntry is set to 'up'
        and ifOperStatus is set to 'down'. In addition, an
        associated voiceEncap/voiceOverIp Peer configuration
        entry is created after the successful ifEntry creation.
        Then ifIndex of the newly created ifEntry must be used by
        the network manager to create a peer configuration entry
        of IETF Dial Control MIB (Refer to RFC 2128 section
        2.2.3.1 and the description of dialCtlPeerCfgEntry for the
        detailed information).
        In summary, the voice dial peer creation steps are as
        follows:
        [1] create this entry (voice/data generic peer entry).
        [2] read the cvPeerCfgIfIndex of this entry for the
            ifIndex of newly created voice/data generic peer.
        [3] create the dialCtlPeerCfgEntry of RFC 2128 with the
            indices of dialCtlPeerCfgId and the ifIndex of newly
            created voice generic peer.

        For each VoIP peer, it uses IP address and UDP port with
        RTP protocol to transfer voice packet. Therefore, it does
        not have its lower layer interface. The
        dialCtlPeerCfgIfType object of IETF Dial Control MIB must
        set to 'other' and the dialCtlPeerCfgLowerIf must set to
        '0'.

        After the successful creation of peer configuration entry
        of IETF Dial Control MIB, the dial plan software in
        managed device will set the ifOperStatus of the newly
        created voiceEncap/voiceOverIp ifEntry to 'up' for
        enabling the peer function if the peer configuration is
        completed.
        When this entry is deleted, its associated ifEntry,
        voiceEncap/voiceOverIp specific peer entry and the peer
        entry of IETF Dial Control MIB are deleted."
    INDEX           { cvPeerCfgIndex } 
    ::= { cvPeerCfgTable 1 }

    First Registration Authority (recovered by parent 1.3.6.1.4.1.9)

    Greg Satz

    Current Registration Authority (recovered by parent 1.3.6.1.4.1.9)

    Cisco Systems, Inc.

    Children (5)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.4.1.9.9.63.1.2.1.1.1 cvPeerCfgIndex 0 0 An arbitrary index that uniquely identifies a generic
    voice peer.
    1.3.6.1.4.1.9.9.63.1.2.1.1.2 cvPeerCfgIfIndex 0 0 The ifIndex of the peer associated ifEntry. The ifIndex
    appears after the associated ifEntry is created
    successfully.
    This ifIndex…
    1.3.6.1.4.1.9.9.63.1.2.1.1.3 cvPeerCfgType 0 0 Specifies the type of voice related encapsulation.
    voice - voice encapsulation (voiceEncap ifType) on the
    telephony network.
    voip …
    1.3.6.1.4.1.9.9.63.1.2.1.1.4 cvPeerCfgRowStatus 0 0 This object is used to create a new row or modify or
    delete an existing row in this table.
    1.3.6.1.4.1.9.9.63.1.2.1.1.5 cvPeerCfgPeerType 0 0 Specifies the type of a peer.
    voice - peer in voice type to be defined in a voice
    gateway for voice calls.
    data - peer in data ty…