| 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. |