mpsSysChargeProtocol

FEC-MPS-MIB · .0.53.1.3.1
Commands MIB view Table view

Object

scalar r/w Enumeration 
This value determine the charging protocol on the internal isdn 
ports. You have three options here: KEYPAD protocol - Charge data 
is transferred such that it can be displayed directly by the 
terminal device.
Functional protocol - Charge data is transferred with binary 
encoding and must be decoded by the terminal device. 
Both - Both of these protocols are recognized (default settings 
for the PBX system.

Context

MIB
FEC-MPS-MIB
OID
.0.53.1.3.1
Type
scalar
Access
readwrite
Status
current
Parent
mpsSysCharge

Net-SNMP examples

How SNMP and these commands work

Scalars have one instance, identified by the .0 suffix.

Read the scalar instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'FEC-MPS-MIB' -M '/opt/observium/mibs/bintec:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'FEC-MPS-MIB::mpsSysChargeProtocol.0'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'FEC-MPS-MIB' -M '/opt/observium/mibs/bintec:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'FEC-MPS-MIB::mpsSysChargeProtocol'

Syntax

Enumeration

Values & Constraints

Enumerated Values
1keypad-and-functional
2no-keypad
3no-functional