132-S-916.2 · Question #150
Calls to a local IP Hardphone have intermittent dropping issues. Which tab in System Monitor will allow you to trace these problems?
The correct answer is A. H.323. See the full explanation below for the reasoning.
Question
Calls to a local IP Hardphone have intermittent dropping issues. Which tab in System Monitor will allow you to trace these problems?
Options
- AH.323
- BKey/Lamp
- CSSI
- DDevConnect
How the community answered
(21 responses)- A71% (15)
- B5% (1)
- C5% (1)
- D19% (4)
Community Discussion
7
Lena V.Apr 7, 2026A is correct. H.323 is the tab in System Monitor that handles IP telephony signaling, so when you have intermittent call drops on a local IP Hardphone, that is exactly where you trace the problem, because it logs and displays the H.323 protocol messages governing call setup, maintenance, and teardown for IP endpoints.
Hiroshi T.Apr 1, 2026A is correct. H.323 tab traces IP Hardphone call signaling and media.
Ingrid P.Apr 3, 2026H.323 covers signaling fine but remember the tab also captures RTCP alongside RTP media, and that RTCP data is what actually tells you packet loss and jitter during the call, so it is worth a separate card from the RTP stream itself.
Toby R.Apr 18, 2026A is the right call here. H.323 is the signaling protocol that IP hardphones use to set up and tear down calls, so when you're chasing intermittent drops on a local hardphone the H.323 tab in System Monitor is where you'll actually see the registration messages, call setup sequences, and any errors or rejections happening mid-call. Key/Lamp is for button and lamp status on the phone, SSI handles the station-to-station interface for internal feature signaling, and DevConnect is for third-party application integrations, none of which are going to show you why a call is dropping. If you pull up that H.323 tab during an active call you can watch the Q.931 messages in real time and spot exactly where the disconnect is being triggered.
Mateus R.Apr 26, 2026Think of System Monitor like a doctor's office where each exam room handles a different type of patient. IP Hardphones speak H.323, so if their calls are dropping, you go to the H.323 tab the same way you send a cardiology patient to the cardiology wing, not the orthopedics wing. The tricky part here is that "Key/Lamp" sounds like it could relate to a physical phone's buttons lighting up, which might feel relevant to a hardware phone acting up, but Key/Lamp is about button states, not call signaling, so A is your answer all day.
Hiroshi T.Apr 28, 2026The analog is fine for intuition, but the cleaner way to lock in A is straight from the administration guide, which lists the H.323 tab as the view for IP Hardphone registration and signaling events, making Key/Lamp a non-starter not just by feel but by definition in the docs.
Ingrid P.Apr 19, 2026My first instinct was SSI because I associate that tab with signaling issues broadly, and "intermittent dropping" reads like a signaling fault at first glance. What snapped me out of it was remembering that IP Hardphones register and communicate over H.323, so any call-path anomaly on those devices shows up in the H.323 tab, which gives you the actual trace data to pinpoint where the drop occurs. Key/Lamp and DevConnect are not even close once you lock in that IP Hardphone equals H.323 endpoint. I have a card on this one with the cue "IP Hardphone drops, which SM tab" and the answer side also lists the other tabs with one-line dismissals, because the distractors here are worth knowing cold before exam day.