Freeze one DID, one direction and one timestamp
Record the dialed DID, caller, timestamp and timezone, Failover Add-on state, primary and backup SIP URIs, provider identifier, signaling source, edge receipt, selected PBX object and context, answer, SDP, RTP addresses, decoded audio and release result. Redact credentials and personal numbers.
Do not change the URI, firewall and PBX match at once. A working outbound call is only a control for source-IP-authenticated termination; it does not validate inbound DID routing or media.
Confirm the DID and primary SIP URI before the PBX
Export the affected DID configuration and compare the exact primary SIP URI with the intended public address, port and transport. Preserve the provider attempt or absence and the customer-edge packet before changing Asterisk or FreePBX.
Anveo Direct does not support SIP REGISTER, so a missing registration status is expected. Do not add registration credentials or treat an OPTIONS result as proof that this DID targets the current listener.
Identify the request from current signaling evidence
Compare the observed source with the provider’s current signaling publication and the account’s effective route. Then verify the PBX endpoint or identify match, assigned context, delivered called-number form and first dialplan route. A permitted source proves only that the request may enter; it does not prove the DID, route or caller identity is trusted.
If no INVITE reaches the edge, preserve the bounded negative capture and provider identifiers. Do not solve an unproved provider-side routing problem with a broad PBX catch-all.
Read SDP and RTP separately from SIP
Because Anveo Direct says it does not proxy RTP, the selected carrier can send media from an address different from the published signaling sources. Compare offer and answer SDP with the PBX-advertised address, observed RTP endpoints, packet counts, codec and decoded audio in each direction.
An answered SIP dialog is not proof of audio. A signaling-only firewall allowance can coexist with missing media, while an unbounded RTP rule can hide the real path and create unnecessary exposure.
Prove rather than assume backup-URI advancement
Confirm that the DID has the Failover Add-on and an exact backup URI. Under one approved bounded condition, retain the primary attempt or absence, response, elapsed time, backup attempt, edge receipt and caller result. Stop if the test threatens emergency or unrelated service.
The public FAQ confirms backup-URI support but does not publish one universal trigger, response-code matrix, timer, retry count or restoration interval. Escalate with exact call identifiers if the observed sequence cannot be reconciled.
Correct the earliest mismatch and retest restoration
Change only the demonstrated owner: DID URI, Failover Add-on, backup URI, signaling trust, PBX identification, dialplan, advertised media address or bounded media policy. Repeat the primary call, authorized failure, backup attempt, answer and two-way audio, then restore the primary path and prove the next new call returns.
Remove temporary captures and test rules. This sequence does not establish active-call survival, emergency behavior, capacity, pricing, availability, compatibility or every carrier-media source. No account, DID, add-on, PBX, firewall, packet or call was inspected or tested for this diagnostic.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- Anveo Direct FAQ ↗
- Anveo Direct inbound DID service ↗
- Anveo Direct call termination ↗
- Anveo Direct network ↗
- Anveo Direct services ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.