Post
Why a secondary DID rings briefly, then reaches carrier voicemail
If a secondary DID reaches the correct phone, rings briefly and then lands in unexpected voicemail, determine which system answered or cancelled the call. The ringtone proves that an inbound route was found. It does not prove that the PBX retained control until the caller was answered.
DID means Direct Inward Dialling: a number delivered through a trunk and routed to a user, queue or other destination. The main trunk number working correctly does not guarantee that every secondary DID has the same carrier treatment or number format.
Follow the call, not the ringtone
| What the trace shows | Likely ownership | Next check |
|---|---|---|
| No INVITE reaches the PBX | Carrier or upstream routing | Carrier destination and DID activation |
| INVITE arrives for an unexpected number format | Trunk matching or inbound parameters | Request-URI, To and provider documentation |
| PBX returns an error immediately | PBX route, source identification or policy | Final SIP response and PBX log |
| PBX sends 180 Ringing, then the carrier sends CANCEL | Something upstream stopped this call leg | Carrier voicemail, timeout or parallel routing |
| PBX answers with 200 OK and plays voicemail | PBX or endpoint voicemail | Call handling and no-answer timer |
Build a short timeline
Record the INVITE arrival, first provisional response, CANCEL or final response, and any BYE. A result such as “180 Ringing at 10:14:03; carrier CANCEL at 10:14:06” is more useful than “it rang one and a half times”. It gives the carrier a timer and transaction to find.
If the caller hears voicemail but the PBX never sends a 200 OK, that PBX did not answer the call. The voicemail may be on the carrier account, a parallel destination or another service controlling the number.
Compare the working and failing numbers
Place calls to the main number and affected DID from the same external phone. Compare:
- the Request-URI user part;
- the To header;
- the trunk or source-identification match;
- the selected inbound destination;
- the first final response; and
- the time before cancellation or answer.
On 3CX, the selected “CalledNum” field and exact DID format affect inbound matching and routing. Other PBXs use different names for the same decision. The principle is portable: inspect the value actually received before reformatting the number in the administration screen.
Do not lengthen every timer first
A longer no-answer timer may only make the wrong voicemail arrive later. First establish whether the cancelling or answering system is the carrier, PBX, queue, user or endpoint. Change the timer owned by that system after confirming the intended call treatment.
The decisive question is who sent the first 200 OK or who cancelled the ringing leg. Once that is known, the investigation becomes a routing or timer change instead of an argument between providers.
Related reading: SIP methods and call flow, SIP headers and SIP trunking fundamentals.
Technical references
Scheduled for 19 August 2026. Menu names vary by PBX and carrier.