132-S-916.2 · Question #143
When looking at a System Monitor trace you notice that despite activity on the system (i.e., calls) there is no information being displayed upon the System Monitor screen. Why is this happening?
The correct answer is A. You have inadvertently paused the display output. See the full explanation below for the reasoning.
Question
When looking at a System Monitor trace you notice that despite activity on the system (i.e., calls) there is no information being displayed upon the System Monitor screen. Why is this happening?
Options
- AYou have inadvertently paused the display output.
- BThe DTE port has been disabled by the system administrator.
- CThis is normal, no options are enabled by default in System Monitor.
- DYou are on a different subnet to the IP Office.
How the community answered
(24 responses)- A83% (20)
- B4% (1)
- C8% (2)
- D4% (1)
Community Discussion
4
Tomasz V.May 28, 2026The answer is A. System Monitor has a pause toggle, and if you hit it accidentally the screen freezes while the system underneath keeps processing calls just fine. This trips up a lot of candidates on the exam because the natural instinct is to blame the network or the admin, but the DTE port option (B) is a red herring from older serial-connected diagnostics that does not apply to the IP Office System Monitor application running over a LAN connection. Option C is wrong because System Monitor does display data by default once you connect, and option D would prevent you from connecting at all rather than giving you a frozen but open session. Check the toolbar for the pause indicator first before you go chasing subnet issues or calling the admin.
Bao N.May 19, 2026Caught myself on this one, pausing System Monitor is embarrassingly easy to do by accident.
Samuel O.May 23, 2026Had this exact scenario in the field years ago on a legacy PBX rollout, and the DTE port being disabled by admin is the first thing I check when System Monitor shows nothing but silence despite live call activity, because without that serial/diagnostic port enabled at the admin level the monitor literally has no path to pull trace data through, so B is the one that explains the complete blackout you are describing.
Tomasz V.May 25, 2026Samuel, appreciate the field experience, but the DTE port is a serial console path that has nothing to do with System Monitor's IP-based SAMON link, so disabling it would not black out trace capture the way option A describes.