Diameter Rf Charging Buffering and Storage
About Buffering
Diameter Rf Charging, Buffering, and Storage enables the SBC to buffer all accounting requests (ACR) in memory for a configurable number of ACRs. The buffer holds a minimum of 15 minutes of ACRs under busy-hour load conditions. For example, based on intended traffic, the buffer would hold 54 calls-per-second which equals approximately 150,000 records. The SBC sends an SNMP trap when accounting records begin to drop from the buffer due to an overflow condition. Subsequently, a clearing SNMP trap is sent once the fault condition is removed.
About Storage
The SBC maintains storage to temporarily store accounting records to a charging collection function (CCF) link, in case of a failure or congestion exists on the SBC. In this scenario, the SBC can store a minimum of 3 days-worth of accounting records. All ACRs can be remain in storage for a configurable amount of time, and for a minimum of 3 days under normal traffic-load conditions.
There are two configurable options for storing ACRs:
- Store all ACRs generated by the SBC
- No ACRs in storage
SNMP
SNMP traps will be sent to the configured management system(s) when accounting records begin to drop due to an overflow condition and when this fault condition is removed:
- apAcctMsgQueueFullTrap will be sent when accounting records begin to drop due to an overflow condition and all accounting servers are down
- apAcctMsgQueueFullClearTrap will be sent when the apAcctMsgQueueFullTrap fault condition is cleared
The following varbinds are defined for the above traps
- apAcctMsgQueueCurrent
The current measured percentage value of space available
- apAcctMsgQueueMinorThreshold
The current configured minor threshold value
- apAcctMsgQueueMajorThreshold
The current configured major threshold value
- apAcctMsgQueueCriticalThreshold
The current configured critical threshold value.