The existing RTP packet/octet atomics are not tied to an inspectable per-call record and do not distinguish non-empty voice frames from logical RFC 4733 digit detections. Add per-call TX/RX non-empty voice-frame counters and logical TX/RX DTMF digit counters, retain a bounded completed-call history, and expose an authenticated AMI RTPStats action keyed by Channel or Uniqueid. The receiver counter must increment once per detected digit after RFC 4733 repeated-end deduplication. Add a real UDP RTP regression that asserts both directions and verifies the AMI response remains queryable after teardown. RFC 3550 section 6.4 defines RTP sender/receiver packet and octet accounting; RFC 4733 section 2.5.1.4 requires repeated end events.
The existing RTP packet/octet atomics are not tied to an inspectable per-call record and do not distinguish non-empty voice frames from logical RFC 4733 digit detections. Add per-call TX/RX non-empty voice-frame counters and logical TX/RX DTMF digit counters, retain a bounded completed-call history, and expose an authenticated AMI RTPStats action keyed by Channel or Uniqueid. The receiver counter must increment once per detected digit after RFC 4733 repeated-end deduplication. Add a real UDP RTP regression that asserts both directions and verifies the AMI response remains queryable after teardown. RFC 3550 section 6.4 defines RTP sender/receiver packet and octet accounting; RFC 4733 section 2.5.1.4 requires repeated end events.