Reference record for OID 1.3.6.1.4.1.351.110.5.5.5.1.3.1

parent

1.3.6.1.4.1.351.110.5.5.5.1.3 (vismXgcpPeerTable)

node code

1

node name

vismXgcpPeerEntry

dot oid

1.3.6.1.4.1.351.110.5.5.5.1.3.1

type

OBJECT-TYPE

asn1 oid

{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) stratacom(351) basis(110) basisServices(5) voice(5) vismXgcpExtensionGrp(5) vismXgcpCoreObjects(1) vismXgcpPeerTable(3) vismXgcpPeerEntry(1)}

{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) stratacom(351) basis(110) basisServices(5) voice(5) vismXgcpExtensionGrp(5) vismXgcpCoreObjects(1) vismXgcpPeerTable(3) vismXgcpPeerEntry(1)}

{iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) stratacom(351) basis(110) basisServices(5) voice(5) vismXgcpExtensionGrp(5) vismXgcpCoreObjects(1) vismXgcpPeerTable(3) vismXgcpPeerEntry(1)}

{iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) stratacom(351) basis(110) basisServices(5) voice(5) vismXgcpExtensionGrp(5) vismXgcpCoreObjects(1) vismXgcpPeerTable(3) vismXgcpPeerEntry(1)}

{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) stratacom(351) basis(110) basisServices(5) voice(5) vismXgcpExtensionGrp(5) vismXgcpCoreObjects(1) vismXgcpPeerTable(3) vismXgcpPeerEntry(1)}

{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) stratacom(351) basis(110) basisServices(5) voice(5) vismXgcpExtensionGrp(5) vismXgcpCoreObjects(1) vismXgcpPeerTable(3) vismXgcpPeerEntry(1)}

iri oid

/iso/identified-organization/dod/internet/private/enterprise/stratacom/basis/basisServices/voice/vismXgcpExtensionGrp/vismXgcpCoreObjects/vismXgcpPeerTable/vismXgcpPeerEntry

/iso/identified-organization/dod/internet/private/enterprises/stratacom/basis/basisServices/voice/vismXgcpExtensionGrp/vismXgcpCoreObjects/vismXgcpPeerTable/vismXgcpPeerEntry

/iso/org/dod/internet/private/enterprise/stratacom/basis/basisServices/voice/vismXgcpExtensionGrp/vismXgcpCoreObjects/vismXgcpPeerTable/vismXgcpPeerEntry

/iso/org/dod/internet/private/enterprises/stratacom/basis/basisServices/voice/vismXgcpExtensionGrp/vismXgcpCoreObjects/vismXgcpPeerTable/vismXgcpPeerEntry

/iso/iso-identified-organization/dod/internet/private/enterprise/stratacom/basis/basisServices/voice/vismXgcpExtensionGrp/vismXgcpCoreObjects/vismXgcpPeerTable/vismXgcpPeerEntry

/iso/iso-identified-organization/dod/internet/private/enterprises/stratacom/basis/basisServices/voice/vismXgcpExtensionGrp/vismXgcpCoreObjects/vismXgcpPeerTable/vismXgcpPeerEntry

iri by oid_info

/ISO/Identified-Organization/6/1/4/1/351/110/5/5/5/1/3/1

Description by circitor

Each row is identified by XGCP peer name and peer XGCP
protocol number combination. This means, if an MGC uses
more than one variant of XGCP (i.e MGCP, SGCP 1.0,
SGCP 1.1 etc), an entry will be maintained for each
of the protocols. mgcNumber and mgcProtocolNumber from
MGMIB are used as foreign index to this table.

Entries in this table are implicitly created by the
agent. An entry shall be created when an entry is created
in the mgcProtocolTable and when mgcProtocolNumber refers
to an XGCP variant (i.e MGCP, SGCP 1.0, SGCP 1.1 etc) as
supported protocol. An entry shall be deleted if the
corresponding entry in the mgcProtocolTable is deleted.

As both mgcProtocolTable and vismXgcpPeerTable have
mgcNumber and mgcProtocolNumber as index, referential
integrity between the two tables is automatically ensured.


Parsed from file CISCO-VISM-XGCP-EXT.mib
Module: CISCO-VISM-XGCP-EXT

Description by cisco_v1

Each row is identified by XGCP peer name and peer XGCP
protocol number combination. This means, if an MGC uses
more than one variant of XGCP (i.e MGCP, SGCP 1.0,
SGCP 1.1 etc), an entry will be maintained for each
of the protocols. mgcNumber and mgcProtocolNumber from
MGMIB are used as foreign index to this table.

Entries in this table are implicitly created by the
agent. An entry shall be created when an entry is created
in the mgcProtocolTable and when mgcProtocolNumber refers
to an XGCP variant (i.e MGCP, SGCP 1.0, SGCP 1.1 etc) as
supported protocol. An entry shall be deleted if the
corresponding entry in the mgcProtocolTable is deleted.

As both mgcProtocolTable and vismXgcpPeerTable have
mgcNumber and mgcProtocolNumber as index, referential
integrity between the two tables is automatically ensured.

Description by mibdepot

Each row is identified by XGCP peer name and peer XGCP
protocol number combination. This means, if an MGC uses
more than one variant of XGCP (i.e MGCP, SGCP 1.0,
SGCP 1.1 etc), an entry will be maintained for each
of the protocols. mgcNumber and mgcProtocolNumber from
MGMIB are used as foreign index to this table.

Entries in this table are implicitly created by the
agent. An entry shall be created when an entry is created
in the mgcProtocolTable and when mgcProtocolNumber refers
to an XGCP variant (i.e MGCP, SGCP 1.0, SGCP 1.1 etc) as
supported protocol. An entry shall be deleted if the
corresponding entry in the mgcProtocolTable is deleted.

As both mgcProtocolTable and vismXgcpPeerTable have
mgcNumber and mgcProtocolNumber as index, referential
integrity between the two tables is automatically ensured.


Parsed from file CISCO-VISM-XGCP-EXT.my.txt
Company: None
Module: CISCO-VISM-XGCP-EXT

Description by cisco

Each row is identified by XGCP peer name and peer XGCP
protocol number combination. This means, if an MGC uses
more than one variant of XGCP (i.e MGCP, SGCP 1.0,
SGCP 1.1 etc), an entry will be maintained for each
of the protocols. mgcNumber and mgcProtocolNumber from
MGMIB are used as foreign index to this table.

Entries in this table are implicitly created by the
agent. An entry shall be created when an entry is created
in the mgcProtocolTable and when mgcProtocolNumber refers
to an XGCP variant (i.e MGCP, SGCP 1.0, SGCP 1.1 etc) as
supported protocol. An entry shall be deleted if the
corresponding entry in the mgcProtocolTable is deleted.

As both mgcProtocolTable and vismXgcpPeerTable have
mgcNumber and mgcProtocolNumber as index, referential
integrity between the two tables is automatically ensured.

Information by circitor

vismXgcpPeerEntry OBJECT-TYPE
    SYNTAX      VismXgcpPeerEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
         "Each row is identified by XGCP peer name and peer XGCP 
          protocol number combination. This means, if an MGC uses
          more than one variant of XGCP (i.e MGCP, SGCP 1.0, 
          SGCP 1.1 etc), an entry will be maintained for each
          of the protocols. mgcNumber and mgcProtocolNumber from
          MGMIB are used as foreign index to this table. 

          Entries in this table are implicitly created by the 
          agent. An entry shall be created when an entry is created 
          in the mgcProtocolTable and when mgcProtocolNumber refers 
          to an XGCP variant (i.e MGCP, SGCP 1.0, SGCP 1.1 etc) as 
          supported protocol. An entry shall be deleted if the 
          corresponding entry in the mgcProtocolTable is deleted.

          As both mgcProtocolTable and vismXgcpPeerTable have 
          mgcNumber and mgcProtocolNumber as index, referential 
          integrity between the two tables is automatically ensured. 
	"
    INDEX   { vismXgcpPeerNumber, vismXgcpPeerProtocolNumber }
    ::= { vismXgcpPeerTable 1 }

Information by cisco_v1

vismXgcpPeerEntry OBJECT-TYPE
    SYNTAX VismXgcpPeerEntry
    ACCESS not-accessible
    STATUS mandatory
    DESCRIPTION
        "Each row is identified by XGCP peer name and peer XGCP  
         protocol number combination. This means, if an MGC uses 
         more than one variant of XGCP (i.e MGCP, SGCP 1.0,  
         SGCP 1.1 etc), an entry will be maintained for each 
         of the protocols. mgcNumber and mgcProtocolNumber from 
         MGMIB are used as foreign index to this table.  
        
         Entries in this table are implicitly created by the  
         agent. An entry shall be created when an entry is created  
         in the mgcProtocolTable and when mgcProtocolNumber refers  
         to an XGCP variant (i.e MGCP, SGCP 1.0, SGCP 1.1 etc) as  
         supported protocol. An entry shall be deleted if the  
         corresponding entry in the mgcProtocolTable is deleted. 
        
         As both mgcProtocolTable and vismXgcpPeerTable have  
         mgcNumber and mgcProtocolNumber as index, referential  
         integrity between the two tables is automatically ensured.  "
    INDEX { vismXgcpPeerNumber, vismXgcpPeerProtocolNumber }
    ::= { vismXgcpPeerTable 1 }

Information by oid_info

Vendor: Stratacom
Module: VISM-XGCP-EXTENSION-MIB

[Automatically extracted from oidview.com]

Information by mibdepot

vismXgcpPeerEntry OBJECT-TYPE
    SYNTAX      VismXgcpPeerEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
         "Each row is identified by XGCP peer name and peer XGCP 
          protocol number combination. This means, if an MGC uses
          more than one variant of XGCP (i.e MGCP, SGCP 1.0, 
          SGCP 1.1 etc), an entry will be maintained for each
          of the protocols. mgcNumber and mgcProtocolNumber from
          MGMIB are used as foreign index to this table. 

          Entries in this table are implicitly created by the 
          agent. An entry shall be created when an entry is created 
          in the mgcProtocolTable and when mgcProtocolNumber refers 
          to an XGCP variant (i.e MGCP, SGCP 1.0, SGCP 1.1 etc) as 
          supported protocol. An entry shall be deleted if the 
          corresponding entry in the mgcProtocolTable is deleted.

          As both mgcProtocolTable and vismXgcpPeerTable have 
          mgcNumber and mgcProtocolNumber as index, referential 
          integrity between the two tables is automatically ensured. 
	"
    INDEX   { vismXgcpPeerNumber, vismXgcpPeerProtocolNumber }
    ::= { vismXgcpPeerTable 1 }

Information by cisco

vismXgcpPeerEntry OBJECT-TYPE
    SYNTAX      VismXgcpPeerEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
         "Each row is identified by XGCP peer name and peer XGCP 
          protocol number combination. This means, if an MGC uses
          more than one variant of XGCP (i.e MGCP, SGCP 1.0, 
          SGCP 1.1 etc), an entry will be maintained for each
          of the protocols. mgcNumber and mgcProtocolNumber from
          MGMIB are used as foreign index to this table. 

          Entries in this table are implicitly created by the 
          agent. An entry shall be created when an entry is created 
          in the mgcProtocolTable and when mgcProtocolNumber refers 
          to an XGCP variant (i.e MGCP, SGCP 1.0, SGCP 1.1 etc) as 
          supported protocol. An entry shall be deleted if the 
          corresponding entry in the mgcProtocolTable is deleted.

          As both mgcProtocolTable and vismXgcpPeerTable have 
          mgcNumber and mgcProtocolNumber as index, referential 
          integrity between the two tables is automatically ensured. 
	"
    INDEX   { vismXgcpPeerNumber, vismXgcpPeerProtocolNumber }
    ::= { vismXgcpPeerTable 1 }

First Registration Authority (recovered by parent 1.3.6.1.4.1.351)

Clyde Iwamoto

Children (3)