Trace operational commands

Open the action log

Open Administration → Operational action log. It records supported queue pause, resume and removal commands, plus live listen, whisper and barge requests. Use it when a member’s state changed unexpectedly or when a supervisor needs to reconstruct an intervention from Obelisk.

Read who, when and where together

Narrow the period and action, then examine the user, source page, queue, extension and result shown for the same event. Share the relevant context with the authorized team leader, security manager or privacy officer rather than drawing conclusions from the command name alone.

Distinguish request and completion
For live supervision, an accepted originate request means the PBX accepted the request. It does not prove that the supervisor answered or heard the conversation.
Read rejected outcomes
A permission or target-visibility rejection needs an access review; a PBX failure needs the corresponding connection or command investigation.

Recognize the command and its outcome

If an agent was paused or removed from a queue, filter the log around that time and action. Compare the user, source screen, queue, extension and outcome. This helps the team leader, security manager or authorized privacy staff reconstruct a supported operation without assuming that every state change came from Obelisk.

Action	How to interpret it
Pause / resume in queue	Connect the selected member and queue to the recorded command outcome; compare with the current live view.
Remove from queue	Identify the specific queue and member. Removing a queue member is different from hiding a resource in Operational views.
Listen / whisper / barge	A PBX-accepted live supervision request records acceptance of the command. It does not prove that the supervisor answered or heard audio, and it is not a log of historical recording playback.
Click-to-call from Monitor	The log also records monitor.call: selected extension, requesting user, source and PBX command outcome. Request accepted means the PBX accepted the origination request. It does not prove that the destination answered or that a conversation completed.

Check the resulting state

Compare the recorded result with the live queue or extension state. For a supported test, use an authorized non-disruptive action and confirm its entry. Check the separate Access log if the question is who authenticated rather than who sent the operational command.

Retention and coverage

Review the log-retention setting before changing it. Increasing the retention period does not recover entries already removed. This log is not an audit of historical recording playback and does not capture every action performed directly in FreePBX, a telephone or another application.

Use the controls, understand what changes

Connect action, user, source screen and target to the recorded outcome. Click-to-call and live supervision can be accepted by the PBX without the receiving phone answering. Use the log to verify the supported command, not to infer a completed conversation or historical recording playback.

Complete product screenshots

Illustrative data. Open the screenshot to enlarge it and match the controls to the instructions in this chapter.