OID reference

zhoneVaIfEMCfgType

1.3.6.1.4.1.5504.5.6.4.1.1.3

Description

Specifies the E&M Lead Signaling type. LEGEND: V = -48V /\/\/ = detector/resister X = normally open relay contact + = normally closed relay contact G = ground SB = Signal Battery SG = Signal Ground typeI - Leads: E (output, relay to ground) M (input, referenced to ground) The tie line equipment (switch/router/etc) gen…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.5504.5.6.4.1.1 (zhoneVaIfEMCfgEntry)
Node code
3
Node name
zhoneVaIfEMCfgType
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.5504.5.6.4.1.1.3
URN notation
urn:oid:1.3.6.1.4.1.5504.5.6.4.1.1.3
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 5504 5 6 4 1 1 3}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) zhone(5504) zhonePhysical(5) zhoneVaIfObjects(6) zhoneVaIfEMObjects(4) zhoneVaIfEMCfgTable(1) zhoneVaIfEMCfgEntry(1) zhoneVaIfEMCfgType(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) zhone(5504) zhonePhysical(5) zhoneVaIfObjects(6) zhoneVaIfEMObjects(4) zhoneVaIfEMCfgTable(1) zhoneVaIfEMCfgEntry(1) zhoneVaIfEMCfgType(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) zhone(5504) zhonePhysical(5) zhoneVaIfObjects(6) zhoneVaIfEMObjects(4) zhoneVaIfEMCfgTable(1) zhoneVaIfEMCfgEntry(1) zhoneVaIfEMCfgType(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) zhone(5504) zhonePhysical(5) zhoneVaIfObjects(6) zhoneVaIfEMObjects(4) zhoneVaIfEMCfgTable(1) zhoneVaIfEMCfgEntry(1) zhoneVaIfEMCfgType(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) zhone(5504) zhonePhysical(5) zhoneVaIfObjects(6) zhoneVaIfEMObjects(4) zhoneVaIfEMCfgTable(1) zhoneVaIfEMCfgEntry(1) zhoneVaIfEMCfgType(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) zhone(5504) zhonePhysical(5) zhoneVaIfObjects(6) zhoneVaIfEMObjects(4) zhoneVaIfEMCfgTable(1) zhoneVaIfEMCfgEntry(1) zhoneVaIfEMCfgType(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) zhone(5504) zhonePhysical(5) zhoneVaIfObjects(6) zhoneVaIfEMObjects(4) zhoneVaIfEMCfgTable(1) zhoneVaIfEMCfgEntry(1) zhoneVaIfEMCfgType(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) zhone(5504) zhonePhysical(5) zhoneVaIfObjects(6) zhoneVaIfEMObjects(4) zhoneVaIfEMCfgTable(1) zhoneVaIfEMCfgEntry(1) zhoneVaIfEMCfgType(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) zhone(5504) zhonePhysical(5) zhoneVaIfObjects(6) zhoneVaIfEMObjects(4) zhoneVaIfEMCfgTable(1) zhoneVaIfEMCfgEntry(1) zhoneVaIfEMCfgType(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) zhone(5504) zhonePhysical(5) zhoneVaIfObjects(6) zhoneVaIfEMObjects(4) zhoneVaIfEMCfgTable(1) zhoneVaIfEMCfgEntry(1) zhoneVaIfEMCfgType(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) zhone(5504) zhonePhysical(5) zhoneVaIfObjects(6) zhoneVaIfEMObjects(4) zhoneVaIfEMCfgTable(1) zhoneVaIfEMCfgEntry(1) zhoneVaIfEMCfgType(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) zhone(5504) zhonePhysical(5) zhoneVaIfObjects(6) zhoneVaIfEMObjects(4) zhoneVaIfEMCfgTable(1) zhoneVaIfEMCfgEntry(1) zhoneVaIfEMCfgType(3)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) zhone(5504) zhonePhysical(5) zhoneVaIfObjects(6) zhoneVaIfEMObjects(4) zhoneVaIfEMCfgTable(1) zhoneVaIfEMCfgEntry(1) zhoneVaIfEMCfgType(3)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) zhone(5504) zhonePhysical(5) zhoneVaIfObjects(6) zhoneVaIfEMObjects(4) zhoneVaIfEMCfgTable(1) zhoneVaIfEMCfgEntry(1) zhoneVaIfEMCfgType(3)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) zhone(5504) zhonePhysical(5) zhoneVaIfObjects(6) zhoneVaIfEMObjects(4) zhoneVaIfEMCfgTable(1) zhoneVaIfEMCfgEntry(1) zhoneVaIfEMCfgType(3)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) zhone(5504) zhonePhysical(5) zhoneVaIfObjects(6) zhoneVaIfEMObjects(4) zhoneVaIfEMCfgTable(1) zhoneVaIfEMCfgEntry(1) zhoneVaIfEMCfgType(3)}
OID-IRI notation
  • /1/3/6/1/4/1/5504/5/6/4/1/1/3
  • /ISO/Identified-Organization/6/1/4/1/5504/5/6/4/1/1/3
  • /ISO/3/6/1/4/1/5504/5/6/4/1/1/3
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/5504/zhonePhysical/zhoneVaIfObjects/zhoneVaIfEMObjects/zhoneVaIfEMCfgTable/zhoneVaIfEMCfgEntry/zhoneVaIfEMCfgType
  • /iso/identified-organization/dod/internet/private/enterprise/zhone/zhonePhysical/zhoneVaIfObjects/zhoneVaIfEMObjects/zhoneVaIfEMCfgTable/zhoneVaIfEMCfgEntry/zhoneVaIfEMCfgType
  • /iso/identified-organization/dod/internet/private/enterprise/Zhone/zhonePhysical/zhoneVaIfObjects/zhoneVaIfEMObjects/zhoneVaIfEMCfgTable/zhoneVaIfEMCfgEntry/zhoneVaIfEMCfgType
  • /iso/identified-organization/dod/internet/private/enterprises/5504/zhonePhysical/zhoneVaIfObjects/zhoneVaIfEMObjects/zhoneVaIfEMCfgTable/zhoneVaIfEMCfgEntry/zhoneVaIfEMCfgType
  • /iso/identified-organization/dod/internet/private/enterprises/zhone/zhonePhysical/zhoneVaIfObjects/zhoneVaIfEMObjects/zhoneVaIfEMCfgTable/zhoneVaIfEMCfgEntry/zhoneVaIfEMCfgType
  • /iso/identified-organization/dod/internet/private/enterprises/Zhone/zhonePhysical/zhoneVaIfObjects/zhoneVaIfEMObjects/zhoneVaIfEMCfgTable/zhoneVaIfEMCfgEntry/zhoneVaIfEMCfgType
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/5504/zhonePhysical/zhoneVaIfObjects/zhoneVaIfEMObjects/zhoneVaIfEMCfgTable/zhoneVaIfEMCfgEntry/zhoneVaIfEMCfgType
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/zhone/zhonePhysical/zhoneVaIfObjects/zhoneVaIfEMObjects/zhoneVaIfEMCfgTable/zhoneVaIfEMCfgEntry/zhoneVaIfEMCfgType
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/Zhone/zhonePhysical/zhoneVaIfObjects/zhoneVaIfEMObjects/zhoneVaIfEMCfgTable/zhoneVaIfEMCfgEntry/zhoneVaIfEMCfgType
  • /iso/identified-organization/dod/internet/private/vendor-objects/5504/zhonePhysical/zhoneVaIfObjects/zhoneVaIfEMObjects/zhoneVaIfEMCfgTable/zhoneVaIfEMCfgEntry/zhoneVaIfEMCfgType
  • /iso/identified-organization/dod/internet/private/vendor-objects/zhone/zhonePhysical/zhoneVaIfObjects/zhoneVaIfEMObjects/zhoneVaIfEMCfgTable/zhoneVaIfEMCfgEntry/zhoneVaIfEMCfgType
  • /iso/identified-organization/dod/internet/private/vendor-objects/Zhone/zhonePhysical/zhoneVaIfObjects/zhoneVaIfEMObjects/zhoneVaIfEMCfgTable/zhoneVaIfEMCfgEntry/zhoneVaIfEMCfgType
  • /iso/org/dod/internet/private/enterprise/5504/zhonePhysical/zhoneVaIfObjects/zhoneVaIfEMObjects/zhoneVaIfEMCfgTable/zhoneVaIfEMCfgEntry/zhoneVaIfEMCfgType
  • /iso/org/dod/internet/private/enterprise/zhone/zhonePhysical/zhoneVaIfObjects/zhoneVaIfEMObjects/zhoneVaIfEMCfgTable/zhoneVaIfEMCfgEntry/zhoneVaIfEMCfgType
  • /iso/org/dod/internet/private/enterprise/Zhone/zhonePhysical/zhoneVaIfObjects/zhoneVaIfEMObjects/zhoneVaIfEMCfgTable/zhoneVaIfEMCfgEntry/zhoneVaIfEMCfgType
  • /iso/org/dod/internet/private/enterprises/5504/zhonePhysical/zhoneVaIfObjects/zhoneVaIfEMObjects/zhoneVaIfEMCfgTable/zhoneVaIfEMCfgEntry/zhoneVaIfEMCfgType
  • Additional combinations skipped.

SNMP properties

Value type
INTEGER
Maximum access defined by MIB
read-write
Status in MIB
current

Enumerated values

ValueName
1typeI
2typeII
3typeIII
4typeIV
5typeV
6typeIIE
7typeIIM
8typeTO

Using this OID with SNMP

At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition. The index encoding is not inferred here.

Published row index: ifIndex.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.5504.5.6.4.1.1.3

Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.

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.

zhoneVaIfEMCfgType OBJECT-TYPE
            SYNTAX INTEGER
                {
                typeI(1),
                typeII(2),
                typeIII(3),
                typeIV(4),
                typeV(5),
                typeIIE(6),
                typeIIM(7),
                typeTO(8)
                }
            MAX-ACCESS read-write
            STATUS current
            DESCRIPTION
                "Specifies the E&M Lead Signaling type.
                LEGEND: V     = -48V
                /\/\/ = detector/resister
                X     = normally open relay contact
                +     = normally closed relay contact
                G     = ground
                SB    = Signal Battery
                SG    = Signal Ground
                
                typeI -
                     Leads:  E (output, relay to ground)
                             M (input, referenced to ground)
                
                     The tie line equipment (switch/router/etc) generates the
                     E-signal to the PBX type grounding the E-lead.  
                     The tie line equipment detects the M-signal by detecting
                     current flow to ground.  A common ground must exist 
                     between the line equipment and the PBX.
                
                              PBX    |  TIE LINE
                                     |
                     E:   V--/\/\/---|-----X----G
                                     |
                     M:   V----X-----|---/\/\/--G
                
                typeII -
                     Leads: E (output, relay to SG)
                     M (input, referenced to ground)
                     SB (feed for M, connected to -48V)
                     SG (return for E, galvanically isolated from ground)
                
                     This interface requires no common ground between the
                     equipment, thus avoiding ground loop noise problems.
                     E-signal is generated toward the PBX by connecting it
                     to SG.  M-signal is indicated by the PBX connecting
                     it to SB.  While this interface does NOT require a
                     common ground, it does have the tendency to inject
                     noise into the audio paths since it is asymmetrical
                     with respect to current flow between devices.
                
                              PBX    |  TIE LINE
                                     |
                     E:   V--/\/\/---|-----X----
                                     |          |
                     SG:  G----------|----------
                                     |
                     M:    ----X-----|---/\/\/--G
                                     |          |
                     SB:   ----------|----------V
                
                typeIII -
                     Leads: E (output, relay to ground)
                     M (input, referenced to ground)
                     SB (connected to -48V)
                     SG (connected to ground) 
                
                     This interface operates similar to type I with respect
                     to the E-signal. The M-signal, however, is indicated by
                     the PBX connecting it to SB on assertion, and alternately
                     connecting it to SG during inactivity. Unfortunately, a 
                     common ground must be shared between the equipment.
                
                              PBX    |  TIE LINE
                                     |
                     E:   V--/\/\/---|-----X----G
                                     |          
                     SG:   ----------|----------G
                              +      |
                     M:    ----------|---/\/\/--G
                          X          |
                     SB:   ----------|----------V
                
                typeIV -
                     Leads: E (output, relay to SG)
                     M (input, referenced to -48V)
                     SB (feed for M, connected to ground)
                     SG (return for E, galvanically isolated from ground)
                
                     This interface is fully symmetrical; it does not require
                     a common ground, does not inject noise into audio paths,
                     and can be connected back to back by swapping E/SG for 
                     M/SB.  E-signal is indicated to the PBX by connecting it
                     to SG.  M-signal is provided by the PBX connecting it to
                     SB.
                
                              PBX    |  TIE LINE
                                     |
                     E:   V--/\/\/---|-----X----
                                     |          |
                     SG:  G----------|----------
                                     |
                     M:    ----------|---/\/\/--V
                          X          |
                     SB:   ----------|----------G
                
                typeV -
                     Leads: E (output, relay to ground)
                            M (input, referenced to -48V)
                
                     Type V line equipment indicates E-signal to the PBX by
                     grounding the E-lead. The PBX indicates M-signal by 
                     grounding the M-lead.  This interface does require a
                     common ground, but does allow back to back connections
                     by swapping E for M.  This interface is quasi-symmetric
                     in that while the line is up, current flow is more or
                                      less equal between the PBX and line equipment. But noise
                                      injection is still a problem.
                
                                               PBX    |  TIE LINE
                                                      |
                                      E:   V--/\/\/---|-----X----G
                                                      |          
                                      M:   G-----X----|---/\/\/--V
                                                      |
                                 The default value of this object is typeI(1).
                "
            REFERENCE
                "EIA/TIA-464B: Sections 4.2.3 E&M Lead Signaling. 
                "
            ::= { zhoneVaIfEMCfgEntry 3 }

Meaning

Descriptions

1 unique

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

Specifies the E&M Lead Signaling type. LEGEND: V = -48V /\/\/ = detector/resister X = normally open relay contact + = normally closed relay contact G = ground SB = Signal Battery SG = Signal Ground typeI - Leads: E (output, relay to ground) M (input, referenced to ground) The tie line equipment (switch/router/etc) generates the E-signal to the PBX type grounding the E-lead. The tie line equipment detects the M-signal by detecting current flow to ground. A common ground must exist between the line equipment and the PBX. PBX | TIE LINE | E: V--/\/\/---|-----X----G | M: V----X-----|---/\/\/--G typeII - Leads: E (output, relay to SG) M (input, referenced to ground) SB (feed for M, connected to -48V) SG (return for E, galvanically isolated from ground) This interface requires no common ground between the equipment, thus avoiding ground loop noise problems. E-signal is generated toward the PBX by connecting it to SG. M-signal is indicated by the PBX connecting it to SB. While this interface does NOT require a common ground, it does have the tendency to inject noise into the audio paths since it is asymmetrical with respect to current flow between devices. PBX | TIE LINE | E: V--/\/\/---|-----X---- | | SG: G----------|---------- | M: ----X-----|---/\/\/--G | | SB: ----------|----------V typeIII - Leads: E (output, relay to ground) M (input, referenced to ground) SB (connected to -48V) SG (connected to ground) This interface operates similar to type I with respect to the E-signal. The M-signal, however, is indicated by the PBX connecting it to SB on assertion, and alternately connecting it to SG during inactivity. Unfortunately, a common ground must be shared between the equipment. PBX | TIE LINE | E: V--/\/\/---|-----X----G | SG: ----------|----------G + | M: ----------|---/\/\/--G X | SB: ----------|----------V typeIV - Leads: E (output, relay to SG) M (input, referenced to -48V) SB (feed for M, connected to ground) SG (return for E, galvanically isolated from ground) This interface is fully symmetrical; it does not require a common ground, does not inject noise into audio paths, and can be connected back to back by swapping E/SG for M/SB. E-signal is indicated to the PBX by connecting it to SG. M-signal is provided by the PBX connecting it to SB. PBX | TIE LINE | E: V--/\/\/---|-----X---- | | SG: G----------|---------- | M: ----------|---/\/\/--V X | SB: ----------|----------G typeV - Leads: E (output, relay to ground) M (input, referenced to -48V) Type V line equipment indicates E-signal to the PBX by grounding the E-lead. The PBX indicates M-signal by grounding the M-lead. This interface does require a common ground, but does allow back to back connections by swapping E for M. This interface is quasi-symmetric in that while the line is up, current flow is more or less equal between the PBX and line equipment. But noise injection is still a problem. PBX | TIE LINE | E: V--/\/\/---|-----X----G | M: G-----X----|---/\/\/--V | The default value of this object is typeI(1).

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

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

Status in source: current.

Names: zhoneVaIfEMCfgType

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "zhoneVaIfEMCfgType",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "typeI",
    "(",
    "1",
    ")",
    ",",
    "typeII",
    "(",
    "2",
    ")",
    ",",
    "typeIII",
    "(",
    "3",
    ")",
    ",",
    "typeIV",
    "(",
    "4",
    ")",
    ",",
    "typeV",
    "(",
    "5",
    ")",
    ",",
    "typeIIE",
    "(",
    "6",
    ")",
    ",",
    "typeIIM",
    "(",
    "7",
    ")",
    ",",
    "typeTO",
    "(",
    "8",
    ")",
    "}",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"Specifies the E&M Lead Signaling type. LEGEND: V = -48V /\\/\\/ = detector/resister X = normally open relay contact + = normally closed relay contact G = ground SB = Signal Battery SG = Signal Ground typeI - Leads: E (output, relay to ground) M (input, referenced to ground) The tie line equipment (switch/router/etc) generates the E-signal to the PBX type grounding the E-lead. The tie line equipment detects the M-signal by detecting current flow to ground. A common ground must exist between the line equipment and the PBX. PBX | TIE LINE | E: V--/\\/\\/---|-----X----G | M: V----X-----|---/\\/\\/--G typeII - Leads: E (output, relay to SG) M (input, referenced to ground) SB (feed for M, connected to -48V) SG (return for E, galvanically isolated from ground) This interface requires no common ground between the equipment, thus avoiding ground loop noise problems. E-signal is generated toward the PBX by connecting it to SG. M-signal is indicated by the PBX connecting it to SB. While this interface does NOT require a common ground, it does have the tendency to inject noise into the audio paths since it is asymmetrical with respect to current flow between devices. PBX | TIE LINE | E: V--/\\/\\/---|-----X---- | | SG: G----------|---------- | M: ----X-----|---/\\/\\/--G | | SB: ----------|----------V typeIII - Leads: E (output, relay to ground) M (input, referenced to ground) SB (connected to -48V) SG (connected to ground) This interface operates similar to type I with respect to the E-signal. The M-signal, however, is indicated by the PBX connecting it to SB on assertion, and alternately connecting it to SG during inactivity. Unfortunately, a common ground must be shared between the equipment. PBX | TIE LINE | E: V--/\\/\\/---|-----X----G | SG: ----------|----------G + | M: ----------|---/\\/\\/--G X | SB: ----------|----------V typeIV - Leads: E (output, relay to SG) M (input, referenced to -48V) SB (feed for M, connected to ground) SG (return for E, galvanically isolated from ground) This interface is fully symmetrical; it does not require a common ground, does not inject noise into audio paths, and can be connected back to back by swapping E/SG for M/SB. E-signal is indicated to the PBX by connecting it to SG. M-signal is provided by the PBX connecting it to SB. PBX | TIE LINE | E: V--/\\/\\/---|-----X---- | | SG: G----------|---------- | M: ----------|---/\\/\\/--V X | SB: ----------|----------G typeV - Leads: E (output, relay to ground) M (input, referenced to -48V) Type V line equipment indicates E-signal to the PBX by grounding the E-lead. The PBX indicates M-signal by grounding the M-lead. This interface does require a common ground, but does allow back to back connections by swapping E for M. This interface is quasi-symmetric in that while the line is up, current flow is more or less equal between the PBX and line equipment. But noise injection is still a problem. PBX | TIE LINE | E: V--/\\/\\/---|-----X----G | M: G-----X----|---/\\/\\/--V | The default value of this object is typeI(1). \"",
    "REFERENCE",
    "\"EIA/TIA-464B: Sections 4.2.3 E&M Lead Signaling. \"",
    "::=",
    "{",
    "zhoneVaIfEMCfgEntry",
    "3",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "typeI",
            1
          ],
          [
            "typeII",
            2
          ],
          [
            "typeIII",
            3
          ],
          [
            "typeIV",
            4
          ],
          [
            "typeV",
            5
          ],
          [
            "typeIIE",
            6
          ],
          [
            "typeIIM",
            7
          ],
          [
            "typeTO",
            8
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "Specifies the E&M Lead Signaling type. LEGEND: V = -48V /\\/\\/ = detector/resister X = normally open relay contact + = normally closed relay contact G = ground SB = Signal Battery SG = Signal Ground typeI - Leads: E (output, relay to ground) M (input, referenced to ground) The tie line equipment (switch/router/etc) generates the E-signal to the PBX type grounding the E-lead. The tie line equipment detects the M-signal by detecting current flow to ground. A common ground must exist between the line equipment and the PBX. PBX | TIE LINE | E: V--/\\/\\/---|-----X----G | M: V----X-----|---/\\/\\/--G typeII - Leads: E (output, relay to SG) M (input, referenced to ground) SB (feed for M, connected to -48V) SG (return for E, galvanically isolated from ground) This interface requires no common ground between the equipment, thus avoiding ground loop noise problems. E-signal is generated toward the PBX by connecting it to SG. M-signal is indicated by the PBX connecting it to SB. While this interface does NOT require a common ground, it does have the tendency to inject noise into the audio paths since it is asymmetrical with respect to current flow between devices. PBX | TIE LINE | E: V--/\\/\\/---|-----X---- | | SG: G----------|---------- | M: ----X-----|---/\\/\\/--G | | SB: ----------|----------V typeIII - Leads: E (output, relay to ground) M (input, referenced to ground) SB (connected to -48V) SG (connected to ground) This interface operates similar to type I with respect to the E-signal. The M-signal, however, is indicated by the PBX connecting it to SB on assertion, and alternately connecting it to SG during inactivity. Unfortunately, a common ground must be shared between the equipment. PBX | TIE LINE | E: V--/\\/\\/---|-----X----G | SG: ----------|----------G + | M: ----------|---/\\/\\/--G X | SB: ----------|----------V typeIV - Leads: E (output, relay to SG) M (input, referenced to -48V) SB (feed for M, connected to ground) SG (return for E, galvanically isolated from ground) This interface is fully symmetrical; it does not require a common ground, does not inject noise into audio paths, and can be connected back to back by swapping E/SG for M/SB. E-signal is indicated to the PBX by connecting it to SG. M-signal is provided by the PBX connecting it to SB. PBX | TIE LINE | E: V--/\\/\\/---|-----X---- | | SG: G----------|---------- | M: ----------|---/\\/\\/--V X | SB: ----------|----------G typeV - Leads: E (output, relay to ground) M (input, referenced to -48V) Type V line equipment indicates E-signal to the PBX by grounding the E-lead. The PBX indicates M-signal by grounding the M-lead. This interface does require a common ground, but does allow back to back connections by swapping E for M. This interface is quasi-symmetric in that while the line is up, current flow is more or less equal between the PBX and line equipment. But noise injection is still a problem. PBX | TIE LINE | E: V--/\\/\\/---|-----X----G | M: G-----X----|---/\\/\\/--V | The default value of this object is typeI(1)."
    ],
    [
      "REFERENCE",
      "EIA/TIA-464B: Sections 4.2.3 E&M Lead Signaling."
    ],
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.5504)

Goldberg Allen

Siblings (3)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.5504.5.6.4.1.1.1 zhoneVaIfEMCfgSignalType00
1.3.6.1.4.1.5504.5.6.4.1.1.2 zhoneVaIfEMCfgOperation00
1.3.6.1.4.1.5504.5.6.4.1.1.4 zhoneVaIfEMCfgDialType00