Reference record for OID 0.0.17.823.0.3.1

parent

0.0.17.823.0.3 (managedObjectClass)

node code

1

node name

acc

dot oid

0.0.17.823.0.3.1

asn1 oid

{itu-t(0) recommendation(0) q(17) q823(823) informationModel(0) managedObjectClass(3) acc(1)}

{itu-t(0) null(0) q(17) q823(823) informationModel(0) managedObjectClass(3) acc(1)}

{ccitt(0) recommendation(0) q(17) q823(823) informationModel(0) managedObjectClass(3) acc(1)}

{ccitt(0) null(0) q(17) q823(823) informationModel(0) managedObjectClass(3) acc(1)}

iri oid

/itu-t/recommendation/q/q823/informationModel/managedObjectClass/acc

/itu-t/null/q/q823/informationModel/managedObjectClass/acc

/ccitt/recommendation/q/q823/informationModel/managedObjectClass/acc

/ccitt/null/q/q823/informationModel/managedObjectClass/acc

iri by oid_info

/ITU-T/Recommendation/Q/823/0/3/1

Description by oid_info

acc MANAGED OBJECT CLASS
DERIVED FROM trafficControl;
CHARACTERIZED BY
"Rec. ITU-T M.3100":stateChangeNotificationPackage,
accPackage PACKAGE
BEHAVIOUR
accBehaviour BEHAVIOUR
DEFINED AS
"The automatic congestion control is a preassigned control which is automatically activated when a congestion trigger is received from the adjacent exchange. It is defined in 4.1/E.412. At the receiving exchanges, all circuit subgroups that terminate to the congested exchange should be subjected to traffic controls which will limit the amount of traffic sent to the congested exchange. Disposition of calls that may be used to throttle traffic are typically cancel or skip. This control relies on an automatic timer set internally by the NE. When the congestion indicator is received, a timer is started in the receivingexchange. Subsequently received congestion indicators restart the timer. If no subsequent congestion indicator is received within the timer, the control is automatically deactivated. The selection of the timer value is vendor specific and is not manageable by an OS. The timer aspects for ACC are described in 5.5.2 b)/Q.542. If a different dispositionOfCalls for each congestion level is desired, a separate acc control object should be instantiated. Furthermore, instances of acc having the same congestion level and tmCircuitEndPointSubgroup must use the same dispositionOfCall.
The origination aspect, destination aspect, routing aspect and additional criteria, are all keys in that order.
An instance of accAffectedTraffic pointed to by assocAccAffectedTraffic must exist before an acc object class is instantiated.
This is a protective control. It is a subclass of trafficControl object class.";;
ATTRIBUTES
controlTmCircuitEndPointSubgroup GET,
dispositionOfCalls GET-REPLACE,
"CCITT Rec. X.721:1992":administrativeState
DEFAULT VALUE Q823-TM-ASN1Module.defaultAdministrativeState
PERMITTED VALUES Q823-TM-ASN1Module.PermittedState
GET-REPLACE,
autoActivated GET,
assocAccAffectedTraffic GET-REPLACE;
;;
View at oid-info.com

Information by oid_info

Automatically extracted from Rec. ITU-T Q.823

First Registration Authority (recovered by parent 0.0.17)

ITU-T

Current Registration Authority (recovered by parent 0)

ITU-T Study Group 17

Brothers (32)