Answer supervision

Answer supervision is the signal from the phone network that tells your system a call has truly been answered. It is the moment the carrier confirms the far end picked up, as opposed to still ringing or sending a recorded message from the network itself. Almost everything that happens after a connect is timed from this signal, so when it is accurate, the rest of the call behaves predictably and your reporting reflects what really happened.

This is why answer supervision matters so much for amd (Answering Machine Detection). AMD only starts listening once the call is reported answered, and beep detection and voicemail drop both key off that same start point. If the carrier reports an answer late, early, or not at all, every downstream decision drifts, and you get more misclassified calls without any obvious cause to point at. The detection logic can be perfect and still produce bad results if the signal feeding it is wrong.

On modern voice paths the answer event arrives as a specific sip response code — typically the one meaning the call has connected and media should flow. Some carriers, or some routes within a single carrier, send this signal inconsistently. That inconsistency is a common cause of weird timing problems that are hard to trace back to one root, because the symptoms show up far from the actual fault.

Answer supervision also feeds your reporting. Your answer rate is only as honest as the answer signals behind it, so a route that fakes early answers can inflate the number while real conversations are not actually happening. If your detection and timing feel off no matter how you tune them, the carrier's answer supervision is one of the first things worth checking, and choosing a reliable carrier goes a long way toward fixing it before you touch any detection settings.