A company deploys a U1981 and CDRServer. The administrator runs the following command on the U1981: config billpoolfuil billdiscard no When the CDR pool usage reaches 100%, the earliest CDRs will be…

Question

Options

• ATRUE
• BFALSE

• A
  80% (41)
• B
  20% (10)

Explanation

Option A is correct because the command config billpoolfuil billdiscard no sets the "bill discard" behavior to no, meaning the system will not discard incoming CDRs when the pool is full - instead, it overwrites the earliest stored CDRs in a circular/ring-buffer fashion to make room for new ones. This is a deliberate configuration choice on the U1981 to ensure continuous CDR capture at the cost of losing the oldest records.

Option B (FALSE) would only be correct if billdiscard were set to yes, which would cause new CDRs to be dropped/discarded when the pool hits capacity, leaving the existing records intact and untouched.

Memory tip: Think of billdiscard no as "I refuse to discard new calls" - so instead of dropping incoming records, the system recycles storage by overwriting the oldest ones first, like a surveillance camera loop. The word "no" means new CDRs survive by evicting the oldest.

No community discussion yet for this question.