Checking the Freshness of RADIUS Session Data

WayaDesk / FreeRADIUS

An operator needs to know when a session observation was last updated. Information that was correct several minutes ago may not describe what the customer is doing now. Freshness should be part of the diagnosis, not hidden behind a single active label.

Compare timestamps before totals

Review when activity was reported and when it was received or displayed. Establish whether the installation is receiving the expected updates. A growing total and a frozen total can reflect different conditions, but neither should be interpreted without the relevant period and service state.

Treat missing information honestly

If accounting is delayed, the correct description may be unknown or stale rather than definitely connected or disconnected. LinkDesk includes stale-accounting warnings to help distinguish those cases. They are a prompt to investigate, not a substitute for observing the actual service.

• Identify the last relevant update for the affected account.
• Check the service and network path carrying accounting information.
• Compare with a fresh test session before making broad changes.

Avoid unnecessary customer actions

Do not require a new payment because an observation has stopped updating. Confirm entitlement and then investigate the reporting path. Asking the customer to repeatedly reconnect can also make the sequence harder to reconstruct.

Document the operating threshold

Agree what staff should do when observations are older than expected in your deployment. The procedure should name the evidence to collect and the responsible technician. Test that procedure during a controlled interruption rather than waiting for a busy evening outage.