Status in source: current.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"mpsSysChargeProtocol",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"keypad-and-functional",
"(",
"1",
")",
",",
"no-keypad",
"(",
"2",
")",
",",
"no-functional",
"(",
"3",
")",
"}",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"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.\"",
"DEFVAL",
"{",
"keypad-and-functional",
"}",
"::=",
"{",
"mpsSysCharge",
"1",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"keypad-and-functional",
1
],
[
"no-keypad",
2
],
[
"no-functional",
3
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"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."
],
null,
null,
null,
[
"DEFVAL",
"keypad-and-functional"
]
]
}