When live monitoring connects but you can't hear the call

A supervisor clicks to listen in on an agent, the real-time screen says they are connected, and they hear nothing but silence. This is confusing because the system reports success while the human reports failure. The trick is to separate the question of whether the monitoring session happened from the question of whether audio flowed — and those are two different logs and two different problems.

How monitoring actually connects

When a manager uses Call monitoring from the real-time report, the dialer connects their manager phone into the agent's call as a silent listener. The session is set up over Asterisk, the manager's phone joins a conference bridge tied to the agent's channel, and audio is supposed to stream one way to the manager. If the session sets up but no audio arrives, the signalling worked and the media did not — which is a phone, conference, or codec story, not a permissions one.

Confirm the session in the monitoring log

The Real-Time Monitoring Log records which manager monitored which agent and when. It is open to level 9 users and those with Admin Utilities privileges, and it returns fields worth knowing:

• Manager, manager phone, and manager server — the phone login the manager monitored from, and the box they did it on.
• Agent monitored and agent server — who was listened to and which box their phone was on.
• Agent Status (lead status) and the Agent session at the moment monitoring started, plus the lead ID, start time, end time, and length.

If the log has a row with a real length for that attempt, the session genuinely connected. That confirms your problem is audio, not access — and it tells you which manager phone and which server to inspect next.

Chasing the silence

flowchart TD
  A[Manager hears no audio] --> B{Row in Real-Time Monitoring Log?}
  B -->|No| C[Session never started, check privilege and phone login]
  B -->|Yes with length| D[Session connected, media failed]
  D --> E{Manager phone registered and working?}
  E -->|No| F[Fix manager phone registration]
  E -->|Yes| G{Codec match across boxes?}
  G -->|No| H[Align codec on manager and agent]
  G -->|Yes| I[Check conference bridge and RTP path]

Start with the manager phone. If it is not properly registered or is on a different box, the conference may join without media. Next, check that the manager phone and the agent share a Codec — a manager on g729 listening to an agent on g711, with no transcoding in the middle, gives you exactly this silent-but-connected symptom. If both line up, the problem is in the conference bridge or the RTP media path, and that is where a packet capture earns its keep.

Where to go next

For a full field walk-through, see reading the Real-Time Monitoring Log Report. If silence is also showing up on ordinary agent calls and not just monitoring, treat it as a wider audio fault and start from the VICIdial troubleshooting playbook.

Codecs that match across boxes and a clean media path are the boring details a managed setup gets right by default. VICIfast runs hardened VICIdial that is live in under 40 seconds. See our plans and pricing.