cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
713
Views
1
Helpful
2
Replies

What does SNMP dial do?

hfakoor222
Spotlight
Spotlight

I've looked around a few places, and hard for me to get a clearer understanding. Is it used for VOIP calls?

 

 

Under this link I found:

https://www.cisco.com/c/en/us/support/docs/ip/simple-network-management-protocol-snmp/45362-SNMPTrapsInImages.html

dial

Sends notification whenever

  • a successful call clears
  • a failed call attempt is determined to have ultimately failed
  • whenever a call setup message is received or sent

/

/

DIAL-CONTROL-MIB

1.3.6.1.2.1.10.21.2.0.1 1.3.6.1.2.1.10.21.2.0.2

dialCtlPeerCallInformation dialCtlPeerCallSetu

 

 

 

 voice

Sends poor quality of voice notification.                   

/

/

CISCO-VOICE-DIAL-CONTROL-MIB

1.3.6.1.4.1.9.9.63.2.0.1

cvdcPoorQoVNotification

1 Accepted Solution

Accepted Solutions

pieterh
VIP
VIP

in short: it is a request for change to RFC 2128., to improve the use of indices
for the time that the RFC's MIB is not changed, it is provided as a separate MIB.

using the links in your post Cisco SNMP Object Navigator

-- *****************************************************************
-- The CISCO dial control mib. This is an extension to the RFC 2128.
--
-- Bibek Das, January, 1998
--
-- Copyright (c) 1998 by cisco Systems, Inc.
-- All rights reserved.
-- *****************************************************************
--
-- This mib is an extension to the RFC 2128
-- 
-- The RFC 2128 (Dial Control Mib) defines callHistoryTable, which is
-- the table that stores past call information. Unfortunately, the indices
-- to this table (callActiveSetupTime, callActiveIndex) are not appropriate
-- for the NMS to retrieve information on regular intervals. 

-- The following changes in the RFC2128 will fix the INDEX of the
-- callHistoryTable. This will also make the mib useful for various types 
-- of calls, including ISDN data, voice, modem. VoIP etc. Right now, the 
-- NMS needs to poll three different mibs (CISCO-CALL-HISTORY-MIB.my, 
-- CISCO-POP-MGMT-MIB.my and the DIAL-CONTROL-MIB.my) for these calls.
--
-- We'll attempt to forward these changes to the ISDN working group
-- so that it may be discussed and approved for the next draft of the
-- RFC 2128.

you can find  RFC 2128 here: RFC 2128: Dial Control Management Information Base using SMIv2 (rfc-editor.org)

View solution in original post

2 Replies 2

pieterh
VIP
VIP

in short: it is a request for change to RFC 2128., to improve the use of indices
for the time that the RFC's MIB is not changed, it is provided as a separate MIB.

using the links in your post Cisco SNMP Object Navigator

-- *****************************************************************
-- The CISCO dial control mib. This is an extension to the RFC 2128.
--
-- Bibek Das, January, 1998
--
-- Copyright (c) 1998 by cisco Systems, Inc.
-- All rights reserved.
-- *****************************************************************
--
-- This mib is an extension to the RFC 2128
-- 
-- The RFC 2128 (Dial Control Mib) defines callHistoryTable, which is
-- the table that stores past call information. Unfortunately, the indices
-- to this table (callActiveSetupTime, callActiveIndex) are not appropriate
-- for the NMS to retrieve information on regular intervals. 

-- The following changes in the RFC2128 will fix the INDEX of the
-- callHistoryTable. This will also make the mib useful for various types 
-- of calls, including ISDN data, voice, modem. VoIP etc. Right now, the 
-- NMS needs to poll three different mibs (CISCO-CALL-HISTORY-MIB.my, 
-- CISCO-POP-MGMT-MIB.my and the DIAL-CONTROL-MIB.my) for these calls.
--
-- We'll attempt to forward these changes to the ISDN working group
-- so that it may be discussed and approved for the next draft of the
-- RFC 2128.

you can find  RFC 2128 here: RFC 2128: Dial Control Management Information Base using SMIv2 (rfc-editor.org)

Thank you