A customer reports that when they receive a call over analog trunks, it takes 5 seconds to ring on the target. What is causing this problem?

Sunita R.Dec 4, 2025

The correct answer is D. On analog trunks, IP Office holds the call before routing it because it is waiting to collect ICLID, which the PSTN delivers between the first and second ring. If ICLID is not coming through, the system sits there waiting out its detection window before it gives up and routes the call anyway, which is exactly where that 5-second delay comes from. You will see this constantly on older analog lines where the telco either is not sending CLID or the signal is too weak for the port to detect it. The fix is to verify with the carrier that CLID is provisioned on the trunk, and on the IP Office side check the analog line card settings to make sure ICLID detection is enabled and the port sensitivity is appropriate for your line levels.

Dervla O.Dec 12, 2025

The stem tells you two things worth locking onto: analog trunks specifically, and a consistent 5-second delay before the target rings. That combination is your filter. Locale misconfiguration from A would affect digit translation or tone cadence, not a clean pre-ring pause. B is a trap because "high level" sounds vaguely relevant, but incoming call route settings do not insert that kind of upstream timing gap. C would be the right territory if the question were about post-answer ring or a configured delay feature, but ring delay settings are something you deliberately turn on, not something that appears as a symptom. D fits because the system is sitting and waiting for ICLID data sent by the PSTN between the first and second ring burst, and when that data does not arrive cleanly, the IP Office waits out its detection window, which lands right around that 5-second mark, then routes without it. I saw a question almost identical to this wording on my 7893X sitting, and I almost circled C because "ring delay on telephony settings" sounds like exactly what is described. Read the stem a second time and ask yourself whether this is a symptom or a feature. A 5-second delay the customer did not ask for is a symptom, not a configured feature, and that single reframe pointed me straight to D.

Carlos M.Dec 29, 2025

So D makes sense because analog trunks send ICLID between the first and second ring, and if IP Office never gets it, the system stalls waiting on that signal before it routes the call. Does that mean if you just disable ICLID collection on the trunk settings it would route immediately, or do you have to configure a shorter timeout somewhere specific in the system?