The KHOMP Quick Stats Report: Spotting a Slow Gateway

When a detection gateway slows down, you feel it before you can explain it: calls hang on a little longer, agents wait, and pacing drifts. The KHOMP Quick Stats Report exists to catch that early. It pulls quick statistics from the KHOMP processing logs and compares the last hour of activity against the same hour from a previous day, so a creeping problem stands out fast.

The two numbers that matter

The report centers on two figures. PROCESSED CALLS are the calls the KHOMP system analyzed during the window. PROC SEC is the time in seconds it took to authenticate and query the KHOMP server for each processed call. Together they tell you both how much work the gateway did and how long each piece of that work took.

Because the gateway handles answering machine detection (AMD (answering machine detection)) and call progress detection (CPD (call progress detection)) for your outbound traffic, a rising PROC SEC is an early warning. Every extra second per call multiplies across thousands of dials and drags on your whole Campaign. PROC SEC covers both authenticating to the KHOMP server and querying it, so a jump can mean the gateway itself is busy, the network path is congested, or the authentication step is stalling. The report does not tell you which, but it tells you something changed.

PROCESSED CALLS matters too. If the count is far lower than the comparison day at the same hour while your dialing volume is the same, calls may be bypassing the gateway or failing to reach it, which means machines you expected to catch are slipping through. Reading the two numbers together gives you a quick sense of whether the gateway is slow, idle, or healthy.

How to read it

flowchart TD
  A[Open KHOMP Quick Stats Report] --> B[Compare last hour to prior day]
  B --> C{Big difference}
  C -->|No| D[Gateway healthy, keep dialing]
  C -->|PROC SEC much higher| E[Gateway slowing down]
  C -->|PROCESSED CALLS much lower| F[Gateway under-processing]
  E --> G[Contact system administrator]
  F --> G

The whole point is the comparison. A single day's numbers mean little on their own, but a large gap between today and the same time on a known-good day is a signal. When you see one, contact your system administrator to check whether there is a problem with the gateway, the network path to it, or the authentication step.

What a slow gateway costs you

• Longer time before a Live answer reaches an Agent, which feels like dead air to the customer.
• Pacing that no longer matches reality, nudging up your Drop rate.
• Detection results that arrive too late to act on cleanly.

Make checking this report a habit, not a fire drill. A quick daily glance at the same hour window means you find a degrading gateway while it is still a minor slowdown rather than after agents complain. Pick a comparison day that was genuinely normal, not a holiday or an unusually light shift, or the comparison will mislead you. Comparing the same hour avoids the trap of judging a busy afternoon against a quiet morning.

When the report does flag a real gap, your job is not to fix the gateway yourself but to raise it quickly. Note the hour, the PROCESSED CALLS count, and the PROC SEC figure against the comparison day, then hand those numbers to your system administrator. Concrete figures turn a vague it feels slow complaint into something they can act on right away.

Where this fits

This report only has data once the gateway is connected, so begin with the KHOMP SIP gateway integration. For how detection feeds the rest of your dialing, see the AMD and CPD complete guide.

We monitor gateway processing times for hosted customers so a slow KHOMP server gets flagged before it touches your call quality. See VICIfast pricing to let us watch it for you.