OID reference

v52CChannelTable

1.3.6.1.4.1.5504.4.3.2.4

Description

Communication Channel (C-channel). C-paths (see v52CPathTable) are carried over C-channels (communications channels). In V5, there are two types of C-channels, logical and physical. Information about logical and physical C-channels is included in the provisioning data for V5.2 interfaces. A C-path associated with a lo…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.5504.4.3.2 (zhoneV52)
Node code
4
Node name
v52CChannelTable
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.5504.4.3.2.4
URN notation
urn:oid:1.3.6.1.4.1.5504.4.3.2.4
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 5504 4 3 2 4}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) zhone(5504) zhoneCommunicationProtocols(4) zhoneVoice(3) zhoneV52(2) v52CChannelTable(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) zhone(5504) zhoneCommunicationProtocols(4) zhoneVoice(3) zhoneV52(2) v52CChannelTable(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) zhone(5504) zhoneCommunicationProtocols(4) zhoneVoice(3) zhoneV52(2) v52CChannelTable(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) zhone(5504) zhoneCommunicationProtocols(4) zhoneVoice(3) zhoneV52(2) v52CChannelTable(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) zhone(5504) zhoneCommunicationProtocols(4) zhoneVoice(3) zhoneV52(2) v52CChannelTable(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) zhone(5504) zhoneCommunicationProtocols(4) zhoneVoice(3) zhoneV52(2) v52CChannelTable(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) zhone(5504) zhoneCommunicationProtocols(4) zhoneVoice(3) zhoneV52(2) v52CChannelTable(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) zhone(5504) zhoneCommunicationProtocols(4) zhoneVoice(3) zhoneV52(2) v52CChannelTable(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) zhone(5504) zhoneCommunicationProtocols(4) zhoneVoice(3) zhoneV52(2) v52CChannelTable(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) zhone(5504) zhoneCommunicationProtocols(4) zhoneVoice(3) zhoneV52(2) v52CChannelTable(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) zhone(5504) zhoneCommunicationProtocols(4) zhoneVoice(3) zhoneV52(2) v52CChannelTable(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) zhone(5504) zhoneCommunicationProtocols(4) zhoneVoice(3) zhoneV52(2) v52CChannelTable(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) zhone(5504) zhoneCommunicationProtocols(4) zhoneVoice(3) zhoneV52(2) v52CChannelTable(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) zhone(5504) zhoneCommunicationProtocols(4) zhoneVoice(3) zhoneV52(2) v52CChannelTable(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) zhone(5504) zhoneCommunicationProtocols(4) zhoneVoice(3) zhoneV52(2) v52CChannelTable(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) zhone(5504) zhoneCommunicationProtocols(4) zhoneVoice(3) zhoneV52(2) v52CChannelTable(4)}
OID-IRI notation
  • /1/3/6/1/4/1/5504/4/3/2/4
  • /ISO/Identified-Organization/6/1/4/1/5504/4/3/2/4
  • /ISO/3/6/1/4/1/5504/4/3/2/4
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/5504/zhoneCommunicationProtocols/zhoneVoice/zhoneV52/v52CChannelTable
  • /iso/identified-organization/dod/internet/private/enterprise/zhone/zhoneCommunicationProtocols/zhoneVoice/zhoneV52/v52CChannelTable
  • /iso/identified-organization/dod/internet/private/enterprise/Zhone/zhoneCommunicationProtocols/zhoneVoice/zhoneV52/v52CChannelTable
  • /iso/identified-organization/dod/internet/private/enterprises/5504/zhoneCommunicationProtocols/zhoneVoice/zhoneV52/v52CChannelTable
  • /iso/identified-organization/dod/internet/private/enterprises/zhone/zhoneCommunicationProtocols/zhoneVoice/zhoneV52/v52CChannelTable
  • /iso/identified-organization/dod/internet/private/enterprises/Zhone/zhoneCommunicationProtocols/zhoneVoice/zhoneV52/v52CChannelTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/5504/zhoneCommunicationProtocols/zhoneVoice/zhoneV52/v52CChannelTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/zhone/zhoneCommunicationProtocols/zhoneVoice/zhoneV52/v52CChannelTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/Zhone/zhoneCommunicationProtocols/zhoneVoice/zhoneV52/v52CChannelTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/5504/zhoneCommunicationProtocols/zhoneVoice/zhoneV52/v52CChannelTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/zhone/zhoneCommunicationProtocols/zhoneVoice/zhoneV52/v52CChannelTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/Zhone/zhoneCommunicationProtocols/zhoneVoice/zhoneV52/v52CChannelTable
  • /iso/org/dod/internet/private/enterprise/5504/zhoneCommunicationProtocols/zhoneVoice/zhoneV52/v52CChannelTable
  • /iso/org/dod/internet/private/enterprise/zhone/zhoneCommunicationProtocols/zhoneVoice/zhoneV52/v52CChannelTable
  • /iso/org/dod/internet/private/enterprise/Zhone/zhoneCommunicationProtocols/zhoneVoice/zhoneV52/v52CChannelTable
  • /iso/org/dod/internet/private/enterprises/5504/zhoneCommunicationProtocols/zhoneVoice/zhoneV52/v52CChannelTable
  • Additional combinations skipped.

SNMP properties

Value type
SEQUENCE OF V52CChannelEntry
Maximum access defined by MIB
not-accessible
Status in MIB
current

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

The displayed source records contain one distinct definition. Compare its source records.

v52CChannelTable OBJECT-TYPE
            SYNTAX SEQUENCE OF V52CChannelEntry
            MAX-ACCESS not-accessible
            STATUS current
            DESCRIPTION
                "Communication Channel (C-channel).  C-paths (see 
                v52CPathTable) are carried over C-channels (communications
                channels).  In V5, there are two types of C-channels,
                logical and physical.  Information about logical and
                physical C-channels is included in the provisioning
                data for V5.2 interfaces.  A C-path associated with a
                logical C-channel is protected.  A C-path associated with
                a physical C-channel is not protected.
                
                In V5.2 only, logical C-channels carry a group of one
                or more C-paths, excluding the C-paths for the protection 
                protocol.  A logical C-channel may consist of the C-paths
                for the Control, Link Control, and BCC protocols.  Another
                logical C-channel may consist of the C-path for the PSTN 
                protocol.  A third logical C-channel may consist of the 
                C-paths for ISDN Ds-type data and ISDN p-type data. A V5.2
                interface may contain up to 44 logical C-channels and each
                logical C-channel on an interface is uniquely identified 
                in V5.2 with a 16-bit logical C-channel identifier.
                
                The goal of the protection protocol is to protect the C-paths
                for the V5 Signaling protocols (ie, BCC, Control, etc) 
                as well as the C-paths for ISDN D-channel data. However,
                the protection protocol is designed to protect logical 
                C-channels, not C-paths.  Therefore, in order to protect
                a C-path, it must be associated with a logical C-channel.
                This association is made as part of the provisioning variant.
                
                A physical C-channel consists of a time slot (64kbit/s) on
                an E1 that carries a C-channel (C-channels are used to 
                carry signaling traffic).  All physical C-channels are
                restricted to timeslots 16, 15, and 31 in accordance with
                the ETSI specification.  
                
                If logical C-channels are in use, each logical C-channel 
                is mapped to one and only one physical C-channel.  This 
                restriction is mandated by the role of the protection 
                protocol.  The protection protocol, which protects logical 
                C-channels, can only protect a single logical C-channel 
                per protection switch over.  This implies an implicit 
                limitation of one logical C-channel per physical C-channel.
                
                For a V5.2 interface, the physical C-channels are identified
                by a logical link ID and a timeslot.  Each V5.2 interface can
                support a maximum of 48 physical C-channels (timeslots 16,
                15, and 31 on up to 16 E1 links; 3 * 16 = 48).
                
                Physical C-channels are not available for bearer connections.
                The physical C-channels are identified at provisioning 
                time and when ISDN ports with D-channel signaling are 
                added."
            ::= { zhoneV52 4 }

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

Communication Channel (C-channel). C-paths (see v52CPathTable) are carried over C-channels (communications channels). In V5, there are two types of C-channels, logical and physical. Information about logical and physical C-channels is included in the provisioning data for V5.2 interfaces. A C-path associated with a logical C-channel is protected. A C-path associated with a physical C-channel is not protected. In V5.2 only, logical C-channels carry a group of one or more C-paths, excluding the C-paths for the protection protocol. A logical C-channel may consist of the C-paths for the Control, Link Control, and BCC protocols. Another logical C-channel may consist of the C-path for the PSTN protocol. A third logical C-channel may consist of the C-paths for ISDN Ds-type data and ISDN p-type data. A V5.2 interface may contain up to 44 logical C-channels and each logical C-channel on an interface is uniquely identified in V5.2 with a 16-bit logical C-channel identifier. The goal of the protection protocol is to protect the C-paths for the V5 Signaling protocols (ie, BCC, Control, etc) as well as the C-paths for ISDN D-channel data. However, the protection protocol is designed to protect logical C-channels, not C-paths. Therefore, in order to protect a C-path, it must be associated with a logical C-channel. This association is made as part of the provisioning variant. A physical C-channel consists of a time slot (64kbit/s) on an E1 that carries a C-channel (C-channels are used to carry signaling traffic). All physical C-channels are restricted to timeslots 16, 15, and 31 in accordance with the ETSI specification. If logical C-channels are in use, each logical C-channel is mapped to one and only one physical C-channel. This restriction is mandated by the role of the protection protocol. The protection protocol, which protects logical C-channels, can only protect a single logical C-channel per protection switch over. This implies an implicit limitation of one logical C-channel per physical C-channel. For a V5.2 interface, the physical C-channels are identified by a logical link ID and a timeslot. Each V5.2 interface can support a maximum of 48 physical C-channels (timeslots 16, 15, and 31 on up to 16 E1 links; 3 * 16 = 48). Physical C-channels are not available for bearer connections. The physical C-channels are identified at provisioning time and when ISDN ports with D-channel signaling are added.

Sources for this description

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)

See 1 matching source record

Evidence

Source records

1 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 1

v52CChannelTable · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 source

Status in source: current.

Names: v52CChannelTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "v52CChannelTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "V52CChannelEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"Communication Channel (C-channel). C-paths (see v52CPathTable) are carried over C-channels (communications channels). In V5, there are two types of C-channels, logical and physical. Information about logical and physical C-channels is included in the provisioning data for V5.2 interfaces. A C-path associated with a logical C-channel is protected. A C-path associated with a physical C-channel is not protected. In V5.2 only, logical C-channels carry a group of one or more C-paths, excluding the C-paths for the protection protocol. A logical C-channel may consist of the C-paths for the Control, Link Control, and BCC protocols. Another logical C-channel may consist of the C-path for the PSTN protocol. A third logical C-channel may consist of the C-paths for ISDN Ds-type data and ISDN p-type data. A V5.2 interface may contain up to 44 logical C-channels and each logical C-channel on an interface is uniquely identified in V5.2 with a 16-bit logical C-channel identifier. The goal of the protection protocol is to protect the C-paths for the V5 Signaling protocols (ie, BCC, Control, etc) as well as the C-paths for ISDN D-channel data. However, the protection protocol is designed to protect logical C-channels, not C-paths. Therefore, in order to protect a C-path, it must be associated with a logical C-channel. This association is made as part of the provisioning variant. A physical C-channel consists of a time slot (64kbit/s) on an E1 that carries a C-channel (C-channels are used to carry signaling traffic). All physical C-channels are restricted to timeslots 16, 15, and 31 in accordance with the ETSI specification. If logical C-channels are in use, each logical C-channel is mapped to one and only one physical C-channel. This restriction is mandated by the role of the protection protocol. The protection protocol, which protects logical C-channels, can only protect a single logical C-channel per protection switch over. This implies an implicit limitation of one logical C-channel per physical C-channel. For a V5.2 interface, the physical C-channels are identified by a logical link ID and a timeslot. Each V5.2 interface can support a maximum of 48 physical C-channels (timeslots 16, 15, and 31 on up to 16 E1 links; 3 * 16 = 48). Physical C-channels are not available for bearer connections. The physical C-channels are identified at provisioning time and when ISDN ports with D-channel signaling are added.\"",
    "::=",
    "{",
    "zhoneV52",
    "4",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "V52CChannelEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "Communication Channel (C-channel). C-paths (see v52CPathTable) are carried over C-channels (communications channels). In V5, there are two types of C-channels, logical and physical. Information about logical and physical C-channels is included in the provisioning data for V5.2 interfaces. A C-path associated with a logical C-channel is protected. A C-path associated with a physical C-channel is not protected. In V5.2 only, logical C-channels carry a group of one or more C-paths, excluding the C-paths for the protection protocol. A logical C-channel may consist of the C-paths for the Control, Link Control, and BCC protocols. Another logical C-channel may consist of the C-path for the PSTN protocol. A third logical C-channel may consist of the C-paths for ISDN Ds-type data and ISDN p-type data. A V5.2 interface may contain up to 44 logical C-channels and each logical C-channel on an interface is uniquely identified in V5.2 with a 16-bit logical C-channel identifier. The goal of the protection protocol is to protect the C-paths for the V5 Signaling protocols (ie, BCC, Control, etc) as well as the C-paths for ISDN D-channel data. However, the protection protocol is designed to protect logical C-channels, not C-paths. Therefore, in order to protect a C-path, it must be associated with a logical C-channel. This association is made as part of the provisioning variant. A physical C-channel consists of a time slot (64kbit/s) on an E1 that carries a C-channel (C-channels are used to carry signaling traffic). All physical C-channels are restricted to timeslots 16, 15, and 31 in accordance with the ETSI specification. If logical C-channels are in use, each logical C-channel is mapped to one and only one physical C-channel. This restriction is mandated by the role of the protection protocol. The protection protocol, which protects logical C-channels, can only protect a single logical C-channel per protection switch over. This implies an implicit limitation of one logical C-channel per physical C-channel. For a V5.2 interface, the physical C-channels are identified by a logical link ID and a timeslot. Each V5.2 interface can support a maximum of 48 physical C-channels (timeslots 16, 15, and 31 on up to 16 E1 links; 3 * 16 = 48). Physical C-channels are not available for bearer connections. The physical C-channels are identified at provisioning time and when ISDN ports with D-channel signaling are added."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.5504)

Goldberg Allen

Direct children (1)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.5504.4.3.2.4.1 v52CChannelEntry88

Siblings (11)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.5504.4.3.2.1 v52InterfaceGroupTable129
1.3.6.1.4.1.5504.4.3.2.2 v52InterfaceGroupLapvTable16
1.3.6.1.4.1.5504.4.3.2.3 v52LinkTable110
1.3.6.1.4.1.5504.4.3.2.5 v52CPathTable17
1.3.6.1.4.1.5504.4.3.2.6 v52UserPortTable112
1.3.6.1.4.1.5504.4.3.2.7 v52StatsCurrentTable19
1.3.6.1.4.1.5504.4.3.2.8 v52StatsIntervalTable110
1.3.6.1.4.1.5504.4.3.2.9 v52StatsTotalTable19
1.3.6.1.4.1.5504.4.3.2.10 v52Traps19
1.3.6.1.4.1.5504.4.3.2.11 v52IgExtensionTable15
1.3.6.1.4.1.5504.4.3.2.12 v52ProtectionCPathTable14