Support for Dial Peer Information on Cisco SBCs/CUBEs

Please add support for monitoring dial peers on Cisco SBCs/CUBEs. 

Part of the info is tied to an IF-MIB interface:

IF-MIB::ifIndex.14 = INTEGER: 14
IF-MIB::ifDescr.14 = STRING: Voice Over IP Peer: 300
IF-MIB::ifType.14 = INTEGER: voiceOverIp(104)
IF-MIB::ifSpeed.14 = Gauge32: 0
IF-MIB::ifPhysAddress.14 = STRING:
IF-MIB::ifAdminStatus.14 = INTEGER: up(1)
IF-MIB::ifOperStatus.14 = INTEGER: up(1)

IF-MIB::ifAlias.14 = STRING: External Calls
IF-MIB::ifLastChange.14 = Timeticks: (2747) 0:00:27.47

The rest is in DIAL-CONTROL-MIB: 

DIAL-CONTROL-MIB::dialCtlPeerCfgIfType.300.14 = INTEGER: voiceOverIp(104)
DIAL-CONTROL-MIB::dialCtlPeerCfgLowerIf.300.14 = INTEGER: 0
DIAL-CONTROL-MIB::dialCtlPeerCfgOriginateAddress.300.14 = STRING: 123456[7-8]...
DIAL-CONTROL-MIB::dialCtlPeerCfgAnswerAddress.300.14 = STRING:
DIAL-CONTROL-MIB::dialCtlPeerCfgSubAddress.300.14 = STRING:
DIAL-CONTROL-MIB::dialCtlPeerCfgSpeed.300.14 = INTEGER: 0
DIAL-CONTROL-MIB::dialCtlPeerCfgInfoType.300.14 = INTEGER: speech(2)
DIAL-CONTROL-MIB::dialCtlPeerCfgPermission.300.14 = INTEGER: both(3)
DIAL-CONTROL-MIB::dialCtlPeerCfgStatus.300.14 = INTEGER: active(1)
DIAL-CONTROL-MIB::dialCtlPeerStatsConnectTime.300.14 = Gauge32: 2509227154 seconds
DIAL-CONTROL-MIB::dialCtlPeerStatsChargedUnits.300.14 = Gauge32: 0
DIAL-CONTROL-MIB::dialCtlPeerStatsSuccessCalls.300.14 = Gauge32: 0
DIAL-CONTROL-MIB::dialCtlPeerStatsFailCalls.300.14 = Gauge32: 0
DIAL-CONTROL-MIB::dialCtlPeerStatsAcceptCalls.300.14 = Gauge32: 646568
DIAL-CONTROL-MIB::dialCtlPeerStatsRefuseCalls.300.14 = Gauge32: 204121
DIAL-CONTROL-MIB::dialCtlPeerStatsLastDisconnectCause.300.14 = STRING: "10 "
DIAL-CONTROL-MIB::dialCtlPeerStatsLastDisconnectText.300.14 = STRING: normal call clearing (16)
DIAL-CONTROL-MIB::dialCtlPeerStatsLastSetupTime.300.14 = Timeticks: (3348060079) 387 days, 12:10:00.79

Useful things to graph would be:

ConnectTime (like uptime)

[Accept, Failed, Refuse] Calls

It would also be useful to show the CfgStatus, OriginateAddress, Interface description/alias and admin/oper status.

In terms of alerting (suspect this would be a later part), it'd be good to be able to alert if a peer goes down but should be up, if there's a spike in any of the three calls metrics and if the connect time resets. 

Thanks in advance.